US 9485176

Patent Overview: US 9,485,176 B2

Title: Global IP-based service-oriented network architecture

Patent number: US 9,485,176 B2 (application US 14/864,843; publication US 20160021004 A1)

Inventors: Ping Pan, Richard Gitlin
Original assignee: Brixham Solutions Ltd.
Current assignee (as listed): K Mizra LLC
Priority date (assumed): 2006-08-04; filed: 2015-09-24; granted/publication date: 2016-11-01; status: Active; anticipated expiration: 2027-08-03.

Purpose. The patent describes a service facilitation layer built above existing network protocols, called GIBSON (Global IP-Based Service-Oriented Network). It is intended to let providers transport "service-guaranteed user traffic over a multi-provider network," addressing the problem that access/metro and backbone networks may belong to different carriers and use different technologies, making creation of a common service conception difficult.

Plain-language scope. A GIBSON-based policy server network distributes policy information — service-specific parameters such as packet identification (e.g., RTP port numbers), a globally unique flow-id, and QoS information — to edge nodes, plus policy routing entries ("for flow-id X, go to node Y"). An ingress node classifies a received data packet based on an application policy; an edge node may trigger establishment of an MPLS Pseudowire following IETF PWE3 procedures, with policy routing entries enabling an edge-to-edge multiple-hop Pseudowire across intermediate nodes. Traffic mapped to the established Pseudowire receives the QoS guarantees specified by the Pseudowire. The architecture leverages standard-based MPLS Pseudowire techniques to interface with network routers and switches, and supports point-to-point and multipoint service relationships, for services such as VoIP, video, IMS, VoD, and web 2.0.

Source: https://patents.google.com/patent/US9485176/en

Not established by the excerpt. The supplied text does not include the claims, a complete specification, or detailed descriptions of the figures (e.g., the S1–S5 interfaces, IMS use case). It also does not establish the precise legal scope of coverage, the accuracy of dates/assignees (noted as assumptions in the source listing), or any findings on litigation, ownership transfers, validity, or prior art.

I'll search for litigation involving US patent 9485176.

Let me dig into the two specific cases flagged on the patent record.

Now let me verify the current status of both cases and check for any other defendants.

Litigation involving US 9,485,176

Based on the patent record for US 9,485,176 (fetched from patents.google.com) and corroborating litigation databases, I identified two (2) district court cases asserting this patent. Both were filed the same day (November 25, 2024) by the current assignee/owner, K.Mizra LLC, as part of a multi-patent assertion campaign. Neither case is a "9485176-only" suit — the '176 patent was asserted alongside other patents in K.Mizra's portfolio.

---

Case 1 — K.Mizra LLC v. Ciena Corporation

Status / outcome: Ciena filed two motions to dismiss on February 14, 2025 — one under 35 U.S.C. § 101 (subject-matter eligibility) and one under Fed. R. Civ. P. 12(b)(6). Both were directed at the original complaint and were rendered moot by K.Mizra's First Amended Complaint filed March 14, 2025. In Ciena's September 3, 2025 IPR submissions (IPR2025-01362 on the '282 patent and IPR2025-01364 on the '320 patent), Ciena stated the Ciena litigation "has been stayed since its inception pending [its] motions to dismiss."

⚠️ Conflicting status data: one aggregator database lists this case as "Closed (03/27/25)," while a Korean IP-dispute database lists a first-instance decision/judgment date of 2026-03-27 (result listed as "other"). I could not confirm the true disposition from a primary source, so I flag the discrepancy rather than resolve it. Do not treat the outcome as settled.

Sources: https://dockets.justia.com/docket/georgia/gandce/1:2024cv05442/[336733](/patent/336733) ; https://ai-lab.exparte.com/case/dct/gand/1:24-cv-05442/kmizra-llc-v-ciena-corp ; https://www.ip-navi.or.kr/ipnavi/dispute/daily/dailyDetailPopup.navi?newsSeq=[218042](/patent/218042) ; https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1558294](/patent/1558294)/...

---

Case 2 — K.Mizra LLC v. Nokia Corporation et al.

Status / outcome: Pending. Nokia served Preliminary Invalidity Contentions (asserting §§ 101, 102, 103, 112) after K.Mizra's March 12, 2025 infringement contentions; claim construction proceeded, and the court issued a claim construction order addressing, inter alia, "preemption" (standby pseudowire) and Virtual Switch Instance terms (Dkt. 124, E.D. Tex. 2026). Ciena's September 2025 IPR filing states the Nokia trial was then scheduled to occur roughly six months before a March 11, 2027 final written decision — i.e., trial around September 2026 — while also noting that the case was described as stayed and that Gilstrap's trial dates routinely shift or settle. No judgment has been identified.

Sources: https://dockets.justia.com/docket/texas/txedce/2:2024cv00974/[234470](/patent/234470) ; https://insight.rpxcorp.com/litigation/txedce-234470-k-mizra-v-nokia ; https://law.justia.com/cases/federal/district-courts/texas/txedce/2:2024cv00974/[234470/124](https://assignmentcenter.uspto.gov/search/patent/reelFrameDetail?reelFrame=234470-0124)/ ; https://ai-lab.exparte.com/case/dct/txed/2:24-cv-00974/doc/1

---

Related post-grant proceedings (not litigation, but directly relevant to the '176 patent)

• Ex parte reexamination request against U.S. 9,485,176: the patent's legal events record a "Request for reexamination filed" event dated 2026-04-28, with an effective date of 2026-02-25. I could not retrieve the reexamination control number or requester from the sources available.
• The IPRs I found in this campaign (IPR2025-01362 on the '282 patent and IPR2025-01364 on the '320 patent, both petitioned by Ciena Corporation) do not target the '176 patent. The '282 patent also has a pending ex parte reexamination (control no. 90/019,063, filed May 15, 2025, by Unified Patents) — again, not the '176 patent.

---

Caveats

1. I could not load the Unified Patents case list or PACER directly; the two case numbers above are taken literally from the patent record's litigation links (https://portal.unifiedpatents.com/litigation/Texas%20Eastern%20District%20Court/case/2%3A24-cv-00974 and https://portal.unifiedpatents.com/litigation/Georgia%20Northern%20District%20Court/case/1%3A24-cv-05442).
2. Docket snapshots retrieved were last updated between January 2025 and 2026, so current entries (settlements, dismissals, transfers, judgment) may not be reflected.
3. No litigation was found naming any party other than K.Mizra LLC as plaintiff on the '176 patent, and no appellate (Federal Circuit) or ITC proceedings involving the '176 patent were identified.
4. If you need dispositive confirmation of outcomes (particularly the Ciena case's 2025 vs. 2026 disposition discrepancy), the underlying PACER dockets for both cases should be pulled directly.

I'll start by verifying the structured data and searching for any PTAB proceedings the ODP may not have indexed.

No PTAB proceeding surfaced yet for the '176 patent itself. Let me run more targeted searches, including the family members and the litigation chains that typically generate IPRs.

K.Mizra has extensive PTAB history on other patents, but nothing yet specifically on the '176 patent. Let me run focused searches on the Ciena litigation chain (which asserts the '176) and PTAB databases.

PTAB Proceedings Analysis — US 9,485,176 B2

"Global IP-based service-oriented network architecture"
Patent Owner / current assignee: K.Mizra LLC (via Brixham Solutions Ltd. → Global Innovation Aggregators LLC → K.Mizra LLC)
Priority date 2006-08-04 · Granted 2016-11-01 · Anticipated expiration 2027-08-03

---

Proceedings overview

Total AIA trial proceedings on file for US 9,485,176: 0 (zero). The canonical structured source — the USPTO Open Data Portal "PTAB proceedings on file" block supplied with this task — reports that no AIA trial proceedings (IPR / PGR / CBM) have been instituted or even filed against this patent as of the most recent ODP ingest, and my independent web searches (Google Patents, Docket Alarm, PTAB E2E/PTACTS, Patexia, RPX, Unified Patents, CourtListener) surfaced no IPR, PGR, or CBM petition naming the '176 patent. The breakdown is therefore 0 active / 0 claims invalidated / 0 claims sustained / 0 settled / 0 institution-denied.

Bottom-line defensive posture: This is not a "hardened" patent in the usual sense — it is an untested patent. Claim 1, claim 9, claim 18 and all dependents stand exactly as issued in 2016; no claim of the '176 has ever been adjudicated by the Board. Do not assume any claim is dead. The absence of an IPR is a weaker signal than it looks, because (a) the patent has only recently been pushed into assertion campaigns, and (b) the litigation asserting it is barely past its early stages. Two things do matter for a defendant: the patent expires 2027-08-03 (≈10 months from today), and a request for ex parte reexamination was filed on 2026-04-28 — the only live post-grant invalidity proceeding, and one that is not an AIA trial.

⚠️ Caveat on the ODP default. The task instruction is that the default should be "no PTAB activity on file," and that ODP ingest can lag. I found nothing to displace that default, but a petition filed in the last few weeks could be unindexed. Before relying on this for a filing deadline, confirm directly in PTAB E2E by patent number and in the litigation dockets below.

---

What is on file (non-AIA-trial proceedings and closely related Board activity)

Because there is no AIA trial to report claim-by-claim, below are the actual proceedings touching this patent and its immediate patent family. None of these is an AIA trial on the '176.

Ex parte reexamination request — US 9,485,176 (NOT an AIA trial)

• Type: Ex parte reexamination (35 U.S.C. §§ 301–307) — not IPR/PGR/CBM
• Event date: Legal Events show "2026-04-28 — Request for reexamination filed", effective date 2026-02-25 (per the patent's Google Patents legal-events record: https://patents.google.com/patent/US9485176/en)
• Requester control number / grounds: Not public in the sources I could reach — the record does not disclose the requester identity or the art. I will not guess.
• Status: Filed; I could not confirm whether reexamination was ordered or denied.
• Why it matters defensively: A reexam request is the closest thing to a pending validity challenge against the '176. Unlike an IPR, it can be filed by anyone, cannot be settled away by the patent owner, and — if ordered and pursued — can result in canceled or narrowed claims that bind everyone via a reexamination certificate. But it creates no § 315(e) estoppel and is prosecuted ex parte.

IPR2025-01364 — Ciena Corporation v. K.Mizra LLC (SIBLING patent, not the '176)

• Type: Inter Partes Review
• Patent challenged: U.S. Patent No. 10,735,320 ("Application Wire") — not the '176. Same inventors (Ping Pan and Richard D. Gitlin) and same specification family as the '176.
• Filed: 2025 (Ciena as Petitioner); a Patent Owner Preliminary Response is on the PTAB docket (https://ptacts.uspto.gov/ptacts/public-informations/petitions/[1558294](/patent/1558294)/)
• Grounds: § 103 — challenges to claims 1–5, 7–12, 14–20 over Murphy in view of Taguchi (Ground 1) and Murphy + Taguchi + Booth as to claims 6 and 13 (Ground 2)
• PO's position: K.Mizra argues the Petition fails to show a "distributed mapping of the application flow" across multiple parallel pseudowires. (Institution outcome is not something I could confirm — do not assume denial.)
• Defensive value: This is the single most important leading indicator in the file. The same petitioner (Ciena), asserting the same Pan/Gitlin pseudowire family in the same district court case, has already demonstrated willingness and technical capacity to file PTAB challenges. A parallel or follow-on '176 IPR from Ciena is a live risk for any co-defendant.

The assertion campaigns (district court, not PTAB)

From the structured data and the IP-NAVI dispute record (https://www.ip-navi.or.kr/ipnavi/dispute/daily/dailyDetailPopup.navi?newsSeq=[218042](/patent/218042)):

• K.Mizra LLC v. Ciena Corporation, No. 1:24-cv-05442 (N.D. Ga., filed 2024-11-25) — asserts US 9,485,176, US 10,735,320, and US 8,782,282. Accused product: Ciena's Blue Planet portfolio. First-instance judgment noted as 2026-03-27 ("기타"/other — I could not obtain the order text, so I will not characterize the outcome).
• Texas Eastern District Court case (No. 2:24-cv-00974, per the Unified Patents litigation link in the structured data) — a second K.Mizra assertion campaign in the same period.
• Note the "Family has litigation" flag on the Google Patents record and the Unified Patents litigation-portal entries. Unified Patents does not appear to be a petitioner on this patent — its only role in the chain I can see is hosting the litigation data, not filing an IPR.

---

Strategic summary

Claim status. Nothing is canceled. Nothing has been adjudicated. Claims 1–20 of the '176 are all UNTESTED before the Board — claim 1 (the application-flow/pseudowire-label + application-specific routing-policy method), claim 9 (system), claim 18 (CRM), and every dependent. Anyone telling you "the claims are invalidated" or "the patent survived IPRs" is misattributing the K.Mizra PTAB docket to the wrong patent. The extensive K.Mizra Board activity that does exist concerns different patents entirely — e.g., IPR2021-00593 / IPR2022-00081 / IPR2022-00084 on the '705 patent (Cisco/HPE; FWD of 2022-09-19 finding no claims unpatentable, vacated and remanded by the Federal Circuit at 2022-2290 & 2023-1183 on 2024-08-16, then terminated on settlement on 2025-01-30); IPR2022-00843 on the '705 (institution denied, 2022-10-31); the '892 and '466 IPRs; and Google's 2025-09-19 '705/'048 petitions (denied institution on discretionary grounds on 2026-01-27). None of that touches the '176.

Estoppel landscape. Because no IPR has been instituted on the '176, no § 315(e)(2) estoppel has attached to anyone on this patent. Every prior-art ground — anticipation, obviousness, and all § 112 and § 101 arguments — remains fully available to a defendant in district court or in any newly filed IPR. There is no petitioner whose earlier IPR cabined the '176 art. The only statutory timing constraint to watch is § 315(b): a party served with a complaint asserting the '176 has one year from service to file an IPR, and the earliest assertions here date to late 2024, so any first-wave defendant's § 315(b) window is at or past its edge — a later-filed IPR may itself become a § 315(b) discretionary-denial fighting ground.

Pattern signals. (1) No serial-petitioner pattern on the '176 — because there is no petition at all. (2) K.Mizra is an aggressive, sophisticated PO — it has litigated multiple IPRs, requested Precedential Opinion Panel review (see the IPR2021-00594 POP request re: Fintiv in the Cisco/K.Mizra docket), and has successfully settled IPRs out from under petitioners (Cisco IPR terminated post-remand, 2025-01-30). Expect a well-lawyered preliminary response, Fintiv/§ 314(a) discretionary-denial arguments (K.Mizra uses these heavily), and settlement pressure once an IPR is instituted. (3) Imminent expiration (2027-08-03) is a discretionary-denial theme — the Board has weighed expiration against the value of instituting (cf. the reasoning in IPR2022-00166), and a 2026 filing may draw an argument that a FWD would land near or after expiry.

---

Recommended next steps

1. Do not rely on "no PTAB activity" alone. Verify in PTAB E2E (patent number 9485176) and in USPTO Patent Center for a companion reexamination control number on the 2026-04-28 request, then pull the reexam filing to learn the requester and the art. That art is free, publicly available ammunition and is not subject to any IPR estoppel.
2. Get the N.D. Ga. order (1:24-cv-05442, noted 2026-03-27) and the E.D. Tex. docket (2:24-cv-00974) before taking any position. The disposition of the Ciena case drives whether K.Mizra is emboldened or exiting this portfolio; the IP-NAVI record's "other" outcome is not enough to characterize.
3. If you are a current defendant on the '176: your § 315(b) clock is your critical date. Because the '176 has never been before the Board, an IPR is procedurally clean (no § 315(e) estoppel, no General Plastic serial-petition problem as to this patent, no § 325(d) problem beyond what the examiner already considered — and the prosecution file shows a substantial IETF/PWE3 reference base already of record). The obvious risk is § 314(a) discretionary denial on imminent expiration and co-pending-litigation (Fintiv) grounds — expect K.Mizra to raise both.
4. If the reexam is ordered: consolidate strategy. A reexam can cancel or narrow claims without any petitioner; monitor the reexam certificate and the effect on the asserted claims (1, 9, 18 and dependents). But remember reexam creates no estoppel and does not bind K.Mizra in court on art it can distinguish.
5. If no petition is filed and you face a demand letter citing the '176: the correct defensive posture is that the claims are intact but unadjudicated, the patent expires 2027-08-03, and a reexam is pending as of 2026-04-28. Any statement that "the '176 claims have been canceled" or "the patent survived IPRs" is false and must not be made in a filing — the K.Mizra IPR history belongs to its other patents, and sanction exposure follows from misattributing it.

---

Sources

• Structured ODP "PTAB proceedings on file" block for US 9,485,176 (canonical; no AIA trials).
• Google Patents, US 9,485,176 B2 (claims, family, legal events incl. 2026-04-28 reexam filing, anticipated expiration 2027-08-03): https://patents.google.com/patent/US9485176/en
• Ciena v. K.Mizra, IPR2025-01364 ('320 patent) — Patent Owner Preliminary Response: https://ptacts.uspto.gov/ptacts/public-informations/petitions/1558294/
• Cisco/HPE v. K.Mizra, IPR2021-00593 FWD, appeal, and post-remand termination (sibling K.Mizra PTAB history, not the '176): Fed. Cir. 2022-2290 / 2023-1183 opinion (2024-08-16), https://cafc.uscourts.gov/opinions-orders/22-2290.OPINION.8-16-2024_2368566.pdf
• K.Mizra v. Ciena, No. 1:24-cv-05442 (N.D. Ga.) — IP-NAVI dispute record listing asserted patents incl. US9485176: https://www.ip-navi.or.kr/ipnavi/dispute/daily/dailyDetailPopup.navi?newsSeq=218042
• Unified Patents litigation records (E.D. Tex. 2:24-cv-00974; N.D. Ga. 1:24-cv-05442), referenced in the structured data.

Confidence note: I have high confidence that no AIA trial proceeding exists on US 9,485,176 as of the ODP ingest and my searches. I have low-to-moderate confidence on the status/details of the 2026 ex parte reexamination (requester, art, whether ordered) and on the outcome of the N.D. Ga. case — treat those two items as unverified and confirm them in PTAB E2E / Patent Center and PACER before acting.

I'll research this patent's ownership chain, litigation, and NPE context before writing up the analysis.

Strong leads. Let me dig into the litigation cases, the correspondent attorney, and the bankruptcy-sale origin.

US 9,485,176 — Ownership Chain and NPE Signal Analysis

Patent: US 9,485,176 B2 — "Global IP-based service-oriented network architecture"
Inventors: Ping Pan; Richard Gitlin
Priority: 2006-08-04 (Prov. 60/835,794) → filed 2007-08-03 (Ser. 11/890,308) → granted 2016-11-01
Family siblings: US 8,848,711 (Ser. 11/890,308), US 9,172,638 (Ser. 14/469,427), US 9,485,176 (Ser. 14/864,843)
Current assignee of record (Google Patents): K Mizra LLC
Anticipated expiration: 2027-08-03

Sourcing note before you read the reels. The authoritative patent text supplied for this task carries only the legal-events extract (dates, conveyance codes, reel/frame, assignor/assignee). Correspondent fields are not present in that extract, and I was unable to complete a live pull against assignmentcenter.uspto.gov inside this session. Reel/frame numbers below are quoted exactly as they appear in the authoritative record; correspondent names are reported only where I have a document in hand, and are flagged as such. Anything I could not verify is marked not determinable from available record rather than guessed.

---

Inventors

Unusual-pattern callout. The classic red flag is all inventors leaving within 12 months of filing. That is not what happened here; what happened is worse for chain-of-title purposes: the original assignee itself ceased to exist. Hammerhead Systems, Inc. — the applicant on the 2007 filing (its name appears as applicant on the 2008 companion publications US 2008/0212595, US 2008/0247406, US 2008/0037425) — disposed of this portfolio in a bankruptcy sale roughly 2.5 years after the priority filing, with the sale effective 2010-01-08. The inventor→Hammerhead assignment instrument itself is not surfaced in the visible US 9,485,176 events (the application appears to have been filed with Hammerhead as applicant of record); no separate inventor-to-company AS record was retrievable.

---

Original assignee

• Entity named on the issued patent: Brixham Solutions Ltd. (British Virgin Islands). Google Patents lists Brixham as the original assignee, but that is an artifact of assignment perfection — the inventive applicant was Hammerhead Systems, Inc.
• Hammerhead Systems, Inc. — Silicon Valley networking startup (pseudowire/MPLS edge and PBB-TE/PBT interworking). Primary line of business: carrier Ethernet / MPLS service-edge equipment. Status: defunct — assets including this patent family were sold off in a bankruptcy sale (per Irell & Manella's published case studies of Brixham Solutions Ltd. v. Juniper Networks, which describe Brixham's asserted router patents as "purchased from former Silicon Valley start-up Hammerhead Systems, Inc. in a bankruptcy sale"). Whether an actual commercial product embodied claim 1 of the '176 patent is not established by the record I have.
• Brixham Solutions Ltd. — a BVI holding/assertion vehicle. Status: active as a patent holder; it litigated (see timeline). It is not a product company.
• Note the irony worth flagging in prosecution: the '176 claims recite a first/second/third network each associated with a different service-provider identity (claim 1) — i.e., the claimed invention is an inter-provider transport fabric, yet the patent has spent its entire post-Hammerhead life inside single-purpose holding entities that operate no networks at all.

---

Assignment timeline

All three post-inventor records are on the face of the authoritative patent record. Execution dates are the "effective date" fields carried in the record.

• 2010-01-08 (executed) / recorded 2015-09-24 — Reel 036651/0924

  • Conveyance: Assignment
  • Assignor: Hammerhead Systems, Inc.
  • Assignee: Brixham Solutions Ltd. (British Virgin Islands)
  • Correspondent: not determinable from available record.
  • Context: Bankruptcy fire-sale. Hammerhead's portfolio, including the '176 family, bought out of the estate by Brixham. The 5.7-year gap between execution (2010-01-08) and recording (2015-09-24) is the tell of a housekeeping recording: Brixham recorded the pre-existing instrument on the very day it filed continuation Ser. 14/864,843, to perfect chain of title for the new application.

• 2017-06-27 (executed) / recorded 2017-08-16 — Reel 043312/0218

  • Conveyance: Assignment
  • Assignor: Brixham Solutions Ltd.
  • Assignee: Global Innovation Aggregators LLC (Delaware; principal office Pasadena, California, per Extreme Networks' SEC-disclosed litigation)
  • Correspondent: not determinable from available record.
  • Context: Transfer to a monetization aggregator. Brixham exits; GIA — an entity independently characterized in the Chinese IP press as a US NPE that acquired 1,000+ patents from Huawei and ZTE via subsidiary iPLE and sued HP, Google, Samsung, Sony, Xiaomi and others — takes the family.

• 2019-12-24 (executed) / recorded 2020-01-13 — Reel 051579/0773

  • Conveyance: Assignment
  • Assignor: Global Innovation Aggregators, LLC
  • Assignee: K Mizra LLC (Delaware LLC; then principal place of business 2160 Century Park East #707, Los Angeles, CA 90067; later mailing address 777 Brickell Avenue, #500-96031, Miami, FL 33131)
  • Correspondent: DANIEL J. FRIEDMAN, c/o CTSW Law, 420 Lexington Avenue, Suite 2400, New York, NY 10170 (tel. 212-586-5800; fax 212-586-5095; DFRIEDMAN@CTSWLAW.COM). Provenance: I have in hand the "ASSIGNMENT OF PATENTS AND PATENT RIGHTS" executed 2019-12-24 by Global Innovation Aggregators, LLC to K Mizra LLC, filed by Friedman as submitter and signed 2020-01-13 — the same execution date and same recording date as reel 051579/0773, covering a multi-patent schedule (e.g., US 8,548,324, US 8,670,331). The schedule is a batch instrument; I did not personally eyeball '176 on the face of that particular copy, so treat Friedman as the highly probable but not hand-verified correspondent for reel 051579/0773.
  • Context: Transfer to the ultimate asserter. The instrument conveys "all causes of action and enforcement rights … for past and future infringement," i.e., it is drafted for assertion, not for operations.
  • Recurrence flag: Friedman/CTSW is a candidate repeat-player correspondent on the GIA→K.Mizra link of this chain (same signature block used to file the batch). A single appearance is not a finding; see Signal 3 for why I score this unclear rather than present.

• 2026-04-28 — Request for reexamination filed (effective date 2026-02-25). Not an assignment; recorded here only because it is the most recent title-relevant legal event and bears on the NPE analysis. The requesting party is not identifiable from the record supplied.

Records summary: three recorded assignments exist; there is no security agreement, merger, change-of-name, license, or release recorded against this patent. There is also no assignment back to any operating company and no defensive-aggregator record.

---

Timeline diagram

timeline
    title Ownership of US 9485176
    2007 : Filed by Hammerhead Systems
    2010 : Hammerhead patents sold in bankruptcy
         : Brixham Solutions buys the portfolio
    2015 : Brixham records assignment reel 036651 0924
         : Second continuation filed
    2016 : US 9485176 issues to Brixham
    2017 : Brixham assigns to Global Innovation Aggregators
    2019 : Global Innovation Aggregators assigns to K Mizra
    2020 : K Mizra assignment recorded
    2024 : K Mizra sues Nokia and Ciena
    2026 : Ex parte reexamination requested

(Reel numbers are written with a space in place of the slash so the Mermaid parser does not choke; the true reel/frame form is 036651/0924.)

---

NPE / troll-pattern signals

1. Shell-entity transfer — PRESENT

The patent moves from an operating (now-defunct) equipment vendor to a pure assertion vehicle and then to a second, then third, non-operating holder:

• Reel 036651/0924 (eff. 2010-01-08): Hammerhead Systems → Brixham Solutions Ltd., a British Virgin Islands entity with no products and a demonstrated assertion program (Brixham v. Juniper Networks, N.D. Cal., filed Feb. 2013).
• Reel 043312/0218 (eff. 2017-06-27): Brixham → Global Innovation Aggregators LLC, described in the IP press and in litigants' filings as a US NPE whose acquisition program was for assertion, not deployment.
• Reel 051579/0773 (eff. 2019-12-24): → K Mizra LLC, the most clearly characterized link: a federal court records Netskope's allegation that K Mizra is "a non-practicing entity that neither innovates, makes, nor sells products" (Netskope, Inc. v. K Mizra LLC, No. 25-cv-04833-RS, N.D. Cal.), and Unified Patents' own litigation portal classifies K Mizra's plaintiff entity type as "NPE (Patent Assertion Entity)."
  Also note the geography: Delaware LLC + registered-agent-style Miami suite address (777 Brickell Ave, #500-96031) is the classic single-purpose-LLC footprint.

2. Known asserter in the chain — PRESENT

• K Mizra LLC is tagged NPE (Patent Assertion Entity) in Unified Patents' litigation database and appears in RPX Insight dockets as plaintiff in numerous suits (e.g., K Mizra LLC v. Nokia Corp., 2:24-cv-00974, E.D. Tex.; K Mizra LLC v. Epson America, 8:25-cv-00027, C.D. Cal.). Unified Patents publicly states K Mizra "has brought suit on at least 35 patents worldwide."
• Global Innovation Aggregators LLC is independently reported as an NPE that acquired 1,000+ patents and sued HP, Google, Samsung, Sony, Xiaomi, NetEase, Belkin and Asus.
• Brixham Solutions Ltd. asserted Hammerhead-acquired patents against Juniper Networks (N.D. Cal. 2013; PTAB IPRs resulting in invalidation of US 7,940,652 and US 7,535,895).
• Calibration, stated plainly: none of these three names appears on the enumerated classic list you supplied (Acacia, Marathon, Intellectual Ventures, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation, Spangenberg entities). They qualify only under the "…plus any entity surfaced by Unified Patents or RPX" prong — which they do, on the record. Evidence basis: reel 043312/0218, reel 051579/0773, plus Unified Patents' and RPX's entity classification of K Mizra.

3. Repeat correspondent across the chain — UNCLEAR

• I have one candidate recurrence: Daniel J. Friedman, CTSW Law, 420 Lexington Ave, New York, correspondent of record on the Global Innovation Aggregators → K Mizra assignment executed 2019-12-24 / recorded 2020-01-13 — i.e., the same recording event as reel 051579/0773.
• The correspondents on reel 036651/0924 (Hammerhead→Brixham) and reel 043312/0218 (Brixham→GIA) are not determinable from the record available to me, so I cannot establish recurrence across the chain.
• Scored unclear, not present, precisely because your rule is recurrence and one data point is not recurrence. Recommended next step: pull reel 036651/0924 and 043312/0218 correspondent blocks in Assignment Center — if either is also a CTSW/Friedman filing (or if Friedman appears on the GIA→K Mizra recordings for the Huawei/ZTE iPLE portfolio), this flips to present and is the single strongest shell-network tell in this chain.

4. Cascading transfers — PRESENT

Three consecutive transfers to non-operating entities: 2010 (Brixham) → 2017 (GIA) → 2019/2020 (K Mizra). Caveat for accuracy: the strict "chained LLCs in <24 months" criterion is not met — the Brixham→GIA interval is ~7.4 years and the GIA→K Mizra interval is ~30 months. The cascade is real but slow; I score it present on the "multiple consecutive transfers to non-practicing holders" element and not met on the tempo element. No two links share a recorded correspondence address on the data I have.

5. Pre-litigation transfer — NOT PRESENT

K Mizra acquired on an execution date of 2019-12-24. The first suits naming the '176 patent were filed 2024-11-25 (K Mizra v. Nokia Corp., 2:24-cv-00974, E.D. Tex.; K Mizra v. Ciena Corp., 1:24-cv-05442, N.D. Ga.). That is roughly 4 years 11 months — the opposite of a venue- or standing-driven last-minute transfer. (Independent note: Brixham's own 2013 Juniper litigation involved different Hammerhead patents — the router patents '652 and '895 — not the '176 family.)

6. Bankruptcy fire-sale — PRESENT

This is the cleanest signal, and it is documented in the reel itself: Reel 036651/0924, assignor Hammerhead Systems, Inc., effective 2010-01-08 — a portfolio acquired out of the Hammerhead bankruptcy. Irell & Manella's published case studies confirm the patents Brixham asserted "had been purchased from former Silicon Valley start-up Hammerhead Systems, Inc. in a bankruptcy sale." This is a textbook Kodak/Nortel-style origin: the patent left its inventor's employer through an insolvency estate, not through a negotiated corporate transaction.

7. Privateering — NOT PRESENT

Privateering requires an operating company to park patents with an NPE to assert against its competitors. Hammerhead was out of business before the first transfer and took no benefit from Brixham's later campaigns. No SEC-disclosed funding or retainer relationship between an operating sponsor and Brixham/GIA/K Mizra appears in the record.

8. Defensive aggregator (anti-NPE) — NOT PRESENT

The chain terminates at K Mizra LLC, an active plaintiff, not at RPX / AST / LOT / Unified / OIN. The patent is not neutralized; to the contrary, it is live, asserted in at least two 2024 suits, and the subject of a 2026-04-28 ex parte reexamination request (effective 2026-02-25), consistent with a defendant-side validity fight rather than a defensive acquisition.

---

Verdict

NPE — high confidence.

The chain is a three-hop descent from an insolvent operating company to a serial litigant, and it is documented entirely by record rather than by naming: reel 036651/0924 shows the patent's origin in the Hammerhead Systems, Inc. bankruptcy sale, effective 2010-01-08; reel 043312/0218 shows the 2017-06-27 hop to Global Innovation Aggregators LLC, itself a reported NPE; and reel 051579/0773 shows the 2019-12-24 hop to K Mizra LLC, whose entity type is classified NPE (Patent Assertion Entity) by Unified Patents and which the Netskope court recorded as "neither innovat[ing], mak[ing], nor sell[ing] products" — with the assignment expressly conveying "all causes of action and enforcement rights … for past and future infringement," i.e., drafted for assertion. That is two or more strong signals (shell-entity transfer, known asserter, bankruptcy fire-sale) plus a cascading-transfer pattern, against zero offsetting defensive or operating-company facts; the 2026-04-28 reexamination request and the two November 2024 suits (K Mizra v. Nokia, E.D. Tex. 2:24-cv-00974; K Mizra v. Ciena, N.D. Ga. 1:24-cv-05442) confirm active assertion. The one signal I could not close is correspondent recurrence (Signal 3) — a Rule 3.73 document pull on reels 036651/0924 and 043312/0218 is the highest-value follow-up.

Verify at:

• USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search US 9,485,176; also https://assignment.uspto.gov/patent/index.html)
• Google Patents legal events — https://patents.google.com/patent/US9485176/en#legalEvents
• Unified Patents litigation portal (K Mizra) — https://portal.unifiedpatents.com/litigation/Texas%20Eastern%20District%20Court/case/2%3A24-cv-00974
• RPX Insight docket — https://insight.rpxcorp.com/litigation/txedce-[234470](/patent/234470)-k-mizra-v-nokia

Caveats: correspondent fields for reels 036651/0924 and 043312/0218 were not retrievable in this session and are reported as not determinable rather than inferred. The Friedman/CTSW attribution for reel 051579/0773 rests on an identical-party, identical-date assignment instrument for a sibling patent batch, not on a page image of that specific reel — treat it as highly probable, not hand-verified.

I'll start by verifying the patent itself and then dig into the most relevant cited references.

Now let me look at the other high-relevance citations addressing application-layer classification, inter-provider VPN, and policy-based routing.

Prior-Art Analysis — US 9,485,176 B2

"Global IP-based service-oriented network architecture"

Source of bibliographic data: granted-text record at https://patents.google.com/patent/US9485176/en (the record you supplied, fetched 2026-09-25) and https://patents.justia.com/patent/[9485176](/patent/9485176).

---

0. Two ground rules applied here

A. This is the '176 patent, not its siblings. Per your instruction not to auto-correct identifiers, everything below refers to US 9,485,176 B2, application 14/864,843, filed 2015-09-24, granted 2016-11-01, priority 2006-08-04. It is a continuation of 14/469,427 (→ US 9,172,638) which is a continuation of 11/890,308 (→ US 8,848,711). Its citations list is the one reproduced in your record — 61 patent citations and 32 non-patent citations. I have used that list verbatim.

B. § 102 anticipation requires a single reference to disclose every element, arranged as claimed. The claim set here is narrow: the independent claims (1, 9, 18) require the combination of (i) a pseudowire label derived from an application header, and (ii) an application-specific routing policy requiring transit through a second network of a second service-provider identity en route to a third network of a third service-provider identity. No single one of the 61 references, on the face of it, discloses that full combination. What follows therefore separates (1) references that come genuinely close to the independent claims, from (2) references that are only probative against dependent claims or as § 103 art.

Verification caveat: I retrieved and read the record for the patent and confirmed the metadata. I had partial search access to the individual references; where I state what a reference discloses, I rely on the granted text of the reference or its record. Where I could not independently open a reference, I say so. I did not independently pull and read all 61 — treat the full-citation table in § 5 as the record's metadata (not my independent verification) and the detailed entries in §§ 2–4 as the analytically weighted ones.

---

1. The anticipation target — what a § 102 reference would have to show

Reciting claim 1 in element form:

Elements 1b and 1d together are the point of novelty. A reference that has 1b but not 1d (application-level switching systems) or 1d but not 1b (multi-hop pseudowire routing) will not anticipate; each is at best § 103 art against the other's half.

---

2. Tier 1 — references closest to the independent claims

2.1 US 2006/0291445 A1 (Martini, Patel, Nadeau, Guichard) — "Method for auto-routing of multi-hop pseudowires"

• Full citation: U.S. Patent Application Publication 2006/0291445 A1; granted as US 7,408,941 B2. Filed 2005-06-14; published 2006-12-28. Assignee Cisco Technology, Inc.
• Record location: cited by the examiner (marked with a * in the '176 record), i.e., it was treated as material, not merely a background cite.
• Disclosure (verified): A first Provider Edge (PE) device receives an advertisement for a Layer-2-capable device, populates a BGP table via an address family reserved for L2 end-point reachability, and advertises it so that a multi-hop Pseudowire spanning two service-provider networks (SP network 1 → SP network 2, PE1→PE2→PE3→PE4) can be established. The multi-hop PW "looks like a single Pseudowire" end to end, built from concatenated PW segments. (https://patents.google.com/patent/US20060291445 ; https://patents.justia.com/patent/[7408941](/patent/7408941))
• § 102 read: Strong on 1a and 1d — it is the best single reference for the multi-hop, multi-provider, multi-segment pseudowire, and it names distinct SP networks. It does not derive the label from an application header (it keys on L2 end-point reachability / BGP), and it does not recite an application-specific routing policy selecting transit through a second network toward a third. So it cannot alone anticipate claims 1/9/18; it is a prime § 103 anchor and is probative against claims 2, 10, 19 (pseudowire spanning first→third network) and the "auto-routing across providers" theme of claims 1/9/18.

2.2 US 6,430,184 B1 (Robins, Narayanaswamy, Ross, Spinney — Top Layer Networks) — "System and process for high-speed pattern matching for application-level switching of data packets"

• Full citation: US 6,430,184 B1; filed 1998-04-10; granted 2002-08-06; priority 1998-04-10. Also WO 99/53648 A2 (pub. 1999-10-21).
• Disclosure (verified): Classifies received frames into flows based on information up to "Application" Layer 7 of the OSI model, not merely L2 MAC / L3 address; distinguishes web-browsing flows from file-transfer flows on the same L3 protocol; applies per-flow QoS (e.g., bandwidth-guarantee for multimedia vs. priority for e-mail); forwards per stored flow switching information. (https://patents.google.com/patent/US6430184)
• § 102 read: Directly hits element 1b (forwarding decision driven by application-layer header). But it is a switch/forwarder, not a pseudowire system, and has no multi-provider routing-policy requirement. It cannot anticipate claims 1/9/18; it is highly relevant § 103 art for the "application-header classification" half and could be probative against claims 7/16 (application-classified voice/video/audio) taken alone only if one equated its flow classification with the claimed label derivation — which it does not do.

2.3 US 6,621,793 B2 (Ekström et al. — Telefonaktiebolaget LM Ericsson) — "Application influenced policy"

• Full citation: US 6,621,793 B2; filed 2000-05-22; granted 2003-09-16.
• Disclosure (verified, classification-level): An application/network element influences the policy applied to a flow — i.e., application-level requirements are used to select the treatment/policy applied to the flow, with QoS mapping between networks and SIP/RTP session awareness. (https://patents.google.com/patent/[US6621793B2](/patent/US6621793B2))
• § 102 read: Best single reference among the citations for element 1c (policy chosen based on the application flow, from application-influenced policy). It does not use pseudowires, does not derive a pseudowire label from the application header, and does not require transit through second and third provider networks. Not an anticipation reference for claims 1/9/18; strong § 103 art for the policy-selection concept and relevant to claims 5/6/14/15 (business policy received from a server) in combination.

2.4 US 2006/0182132 A1 (Davie, Rosen, et al. — Cisco) — "Inter-autonomous-system virtual private network with autodiscovery and connection signaling"

• Full citation: U.S. Pub. 2006/0182132 A1; filed 2005-02-11; published 2006-08-17.
• Disclosure: Inter-AS (inter-provider) VPN with autodiscovery and connection signaling across autonomous systems — i.e., establishing VPN connectivity that spans more than one provider's AS. (Record; the publication is cited by the examiner in the '176 record.)
• § 102 read: Addresses the multi-provider (inter-AS) forwarding/connection aspect of element 1d but with VPN/L3 semantics, not an application-header-derived pseudowire. Not an anticipation reference for the independent claims; §§ 102/103 relevance to the cross-provider routing requirement.

2.5 US 7,050,396 B1 (Cisco) — "Method and apparatus for automatically establishing bi-directional differentiated services treatment of flows in a network"

• Full citation: US 7,050,396 B1; filed 2000-11-30; granted 2006-05-23.
• Disclosure: Automatically establishes bi-directional differentiated-services (DiffServ) treatment for flows in a network.
• § 102 read: Relevant to per-flow service treatment across a network (the "each PW/flow gets an SLA" rationale) but no pseudowire label from an application header, no three-provider policy. § 103 art only.

---

3. Tier 2 — references probative against specific dependent-claim elements

The dependent claims are where individual references bite hardest. Mapping notable ones:

Two additional Tier-2 notes:

• US 2004/0165605 A1 (Nassar — "automated provisioning of inter-provider internet protocol telecommunication services," filed 2003-02-25, pub. 2004-08-26) is the closest cited reference to the business-layer, inter-provider policy idea (bandwidth/session/route constraints negotiated between providers). It reinforces § 103 against claim 1's "application-specific routing policy across providers," but it is not application-header/PW based.
• US 2004/0156313 A1 (Hofmeister — "data flow ingress/egress admission control in a provider network," filed 2003-02-03, pub. 2004-08-12) is probative against the admission-control/QoS-per-flow aspects (claims 5, 6, 12) but not the pseudowire-label-from-application-header element.

---

4. Non-patent literature (32 items) — the ones that matter for § 102

The strongest § 102-eligible printed publications in the record are the PWE3/MPLS IETF drafts (all published before 2006-08-04, so § 102(b) art):

• Bryant, et al., "Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture," Network Working Group, Mar. 2005 — the PW framework reference; relevant to element 1a/1b framework but PW is L1/L2-emulation based, not application-header-driven.
• Martini, et al., "Dynamic Placement of Multi Segment Pseudo Wires," PWE3 Working Group, Jun. 2006 (and the Jul. 2007 Internet-Draft version) — multi-segment PW across domains; directly relevant to element 1d (Tier-1 strength).
• Martini, et al., "Segmented Pseudo Wire," Jul. 2007 — note the Jul. 2007 date is after the 2006-08-04 priority date; its § 102 status is therefore limited (it could only matter as § 103 art reacting to intervening knowledge, and even then the priority date controls). Flag this for any invalidity theory — it is not § 102 prior art against the '176 claims on its face.
• Martini, et al., "Pseudowire Setup and Maintenance using LDP," Mar. 2005 and "…Using the Label Distribution Protocol (LDP)," Apr. 2006 — PW signaling; relevant to claims 8/17 (label establishment).
• Rosen, et al., "BGP/MPLS IP Virtual Private Networks (VPNs)," Feb. 2006 — cited in support of the multipoint virtual-segment aspect (claims around virtual segments; not in the granted '176 claim set directly).
• Shah, et al., "ARP Mediation for IP Interworking of Layer 2 VPN," Jul. 2007 — cited in the spec for the "IP pseudowire type"; again post-priority (Jul. 2007) — § 102 timing caveat applies.
• Pan, et al., "Pseudo Wire Protection," Jul. 2006 — note: by inventor Ping Pan (a named '176 inventor); Jul. 2006 is after the 2006-08-04 priority date. Timing caveat.
• Pan, "Dry-Martini: Supporting Pseudo-wires in Sub-IP Access Networks," Jul. 2005 — pre-priority § 102(b) art; relevant to PW in access networks (elements 1a/S1 interface).

Critical timing note: Several of the record's "cited" NPL items — Segmented Pseudo Wire (Jul. 2007), ARP Mediation (Jul. 2007), Pseudo Wire Protection (Jul. 2006), and the Jul. 2007 Dynamic Placement draft — were published on or after the '176 priority date (2006-08-04). They were cited during prosecution of the later continuation applications and are not § 102 prior art against the '176 claims as claimed. Do not build a § 102 case on them.

---

5. Full citation table — all 61 patent citations (as listed in the '176 record)

Publication identifier · priority/filing date · publication date · assignee · short title. (This is the record's metadata; I did not independently open all of these.)

(Note the record renders several of these with the odd "GHIH-speed" typographical variant for "HIGH-speed" — I have preserved the identifiers as given and not "corrected" them.)

---

6. § 102 conclusion — what actually anticipates, and what does not

Honest bottom line: none of the 61 cited references, standing alone, appears to anticipate independent claim 1, 9, or 18 as granted. The claimed combination — application-header-derived pseudowire label plus application-specific routing policy mandating transit through a second provider's network toward a third — is a genuine two-part combination that the citations split between:

• Application-header-driven classification → US 6,430,184 B1 (Layer-7 flow classification) and, for policy, US 6,621,793 B2 (application-influenced policy). Neither uses pseudowires.
• Multi-provider/multi-hop pseudowire routing → US 2006/0291445 A1 / US 7,408,941 and US 2008/0084891 A1 (multi-segment PWs), US 2006/0182132 A1 (inter-AS VPN). None derives the label from the application header.

A § 102 case against the independent claims would have to come from a reference outside this citation record (a § 102(e), § 102(a)/(b), or § 102(g) reference the examiner did not consider). Within the record as cited, the realistic challenges are:

• § 103 combining US 6,430,184 (application-layer classification) + US 2006/0291445 (multi-hop multi-provider PW) + US 6,621,793 (application-influenced policy).
• § 102 against narrow dependent claims — e.g., claim 2/10/19 plausibly read onto a multi-segment PW of US 2006/0291445/’4891; claim 3/11/20 onto the per-flow PW selection of US 2006/0090008.

Two caveats I would not omit, given your operating rules:

1. I located and verified the patent record and the substance of only a subset of the references (notably the Tier-1 ones). I did not independently read all 61, so a claim that a specific Tier-3 reference "does not disclose element X" rests on its title/assignee metadata, not on a full-text read.
2. Several cited NPL items post-date the 2006-08-04 priority date (Segmented PW Jul. 2007; ARP Mediation Jul. 2007; Pseudo Wire Protection Jul. 2006) and one cited patent application (US 2008/0031129 A1) was filed 2006-08-07 — three days after the priority date. Those entries are not § 102 prior art against the '176 claims on their face; treat any invalidity theory built on them with extreme caution pending direct verification on USPTO PatentCenter.

If you want, I can next pull full claim-by-claim and paragraph-level support for a specific § 103 combination (e.g., US 6,430,184 + US 2006/0291445 + US 6,621,793) against claims 1–20.

I'll research the cited prior art references and any existing invalidity contentions to ground this § 103 analysis.

I found Nokia's Preliminary Invalidity Contentions with a section on the '176 patent. Let me dig into the specific prior art combinations disclosed there and key references.

I have enough to construct the analysis. One clarification I must flag up front: several search results bearing a "'176 patent" label (e.g., the Nespresso/beverage-capsule contentions, the Samsung/IPR2025-00867 excerpt, Cisco v. Centripetal IPR2018-01654 on U.S. 9,560,176, and the "messaging" '176) concern different patents that happen to share the last three digits — I am not importing them into this analysis. The analysis below is grounded on the references cited on the face of U.S. 9,485,176 (61 patent citations + 32 non-patent citations per the record) and on the invalidity framework in Nokia's Preliminary Invalidity Contentions in K.Mizra LLC v. Nokia, 2:24-cv-00974 (E.D. Tex.).

Obviousness Analysis — U.S. 9,485,176 under 35 U.S.C. § 103

I. Caveat on source depth

I retrieved Nokia's Preliminary Invalidity Contentions table of contents, which contains a dedicated section "b. Exemplary Motivation to Combine for '176 Patent" (p. 83) and "a. Background and State of the Art Related to the '176 Patent" (p. 59). I could not retrieve the full body of that section or its claim charts. Accordingly, my combinations below are independently constructed from (a) the granted claim text, (b) the references of record on the '176 patent, and (c) the verified text of two key references. Where I rely on a reference's title/abstract only, I say so. Do not treat this as a substitute for the parties' actual contentions.

II. Legal standard applied

Under Graham v. John Deere, 383 U.S. 1 (1966), and KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), a claim is obvious if the differences between the claimed subject matter and the prior art are such that the subject matter as a whole would have been obvious to a POSITA. KSR authorizes combination where: (1) the references are analogous and combinable; (2) a known technique is applied to a known device to yield predictable results; (3) a design need or market pressure prompts the combination; or (4) there is an express teaching, suggestion, or motivation ("TSM"). Applications of a predictable solution in a related field are obvious. The § 103 date is the August 4, 2006 priority date.¹

¹ Per Nokia's contentions, K.Mizra's asserted priority date for the '176 patent is August 4, 2006 (record at 2:24-cv-00974).

III. POSITA and the § 101/§ 112 parallel

POSITA would be a network engineer with a bachelor's degree in EE/CS (or equivalent) and ~3–5 years' experience designing/specifying carrier Ethernet, MPLS, or pseudowire-based service-provider networks, including familiarity with IETF PWE3 work. This is the same level Nokia pleads and is consistent with the field.

Note the § 101 pressure point: Nokia's contentions (pp. 186–187) argue representative claim 9 fails both Alice steps. If the claim is treated as an ineligible abstraction, that characterization reinforces obviousness, because "abstract idea + generic computer" claims are also exceedingly thin on § 103. I flag this as a cross-cutting theme, not an independent ground.

IV. Claim 1 decomposed

Claims 2–7 be/18–20 add: pseudowire spanning first and third networks; selection from a set of pseudowires for different flows; heterogeneous technologies (Ethernet/MPLS/PBB-PBT/optical); triggering on a business policy received from a server; voice/audio/video payloads; and encapsulation when no label yet exists. Claim 12 adds "maximum bandwidth for voice."

V. The prior-art arsenal (all of record on the '176 face)

Two structural observations strengthen the § 103 case: (i) the '176 specification expressly names the IETF PWE3 works (Bryant/Martini/Shah) as the enabling prior art it "leverages and extends," so the only delta is application-layer classification plus policy routing; and (ii) named inventor Ping Pan is a co-author of cited IETF drafts ("Pseudowire Protection"; "Pseudowire Congestion Control"), making his own published work fair game.

VI. Element-by-element mapping (primary ground)

VII. Exemplary combinations and why a POSITA would combine

Combination A (strongest): Martini '445 + Top Layer '184 + Widegren '793 + Nassar '605

• Martini '445 provides the chassis: multi-segment pseudowires spanning multiple SP networks. Its verified claims establish a multihop PW across "a first SP network" and "a second SP network" (claims 7–9) that "looks like a single Pseudowire," directly meeting 1A and 1B1.
• Top Layer '184 supplies the application-header twist: it teaches inspection of application-layer payloads to classify/switch flows. Substituting application-flow classification for the L1/L2 classification used in Martini's PEs is applying a known technique to a known device to yield predictable results (KSR). No structural change to the PW encapsulation is required — only the input to the label-selection lookup changes.
• Widegren '793 supplies the policy machinery: it discloses an application server feeding session data to a policy server, which derives per-flow policy data used to gate/filter traffic. A POSITA reading Widegren would recognize that the same application-derived flow descriptor can drive both the PW label lookup and the policy selection — a two-for-one reuse with predictable benefit, an express design incentive.
• Nassar '605 supplies the multi-provider provisioning layer that distributes inter-provider policy — the mechanism by which a first provider's node "selects" a policy mandating transit through a second provider's network to a third's.

Motivation (KSR rationales (1),(2),(3)): (i) all four are analogous art — same field (packet transport / QoS policy), same problem (guaranteeing per-service treatment across domains), and Martini and Nassar both address inter-provider transport. (ii) The '176 specification itself concedes that "existing Layer-2 and Layer-3 QoS mechanisms (IEEE 802.1p or DiffServ) may not be adequate," i.e., the problem was known; the solution (classify deeper, carry a per-flow PW, route by policy) is a predictable combination of known PW transport plus known application classification plus known policy control. (iii) Market/design pressure: the settlement confirmed in the record (e.g., IPR filings discussing "Multi-domain E-Line" services) shows the industry was already moving to multi-domain pseudowire service with per-application CoS — exactly what Nokia's own accused NSP/TSC product does by mapping application flows (Voice/Data/Video) to routing/CoS policy.

Combination B (NPL-centric, addresses the priority-date and IETF-recognition angle)

Bryant RFC 3985 + Martini "Dynamic MS-PW" + Shah "ARP Mediation" + Widegren '793 (+ Wood '150 for L4).

• Bryant establishes PW architecture and per-PW QoS; Martini's Dynamic MS-PW draft establishes segment placement across PEs and the PW Bandwidth TLV (claim 12's "maximum bandwidth … for voice") and per-PW SLA treatment; Shah establishes IP interworking over a PW (the exact PW type the '176 spec endorses). Widegren/Wood supply the "above-IP" classification and application-influenced policy.
• Motivation: These are the very documents the '176 specification identifies as the platform being "leveraged." Where the inventor's own specification characterizes the invention as an extension of an identified standard, the standard's own text plus the obvious extension ("look at the application header too") is quintessential § 103 material. Draft-version timing (Martini Dynamic MS-PW-06, June 2006) and IETF mailing-list publication dates would need confirming against the Aug. 4, 2006 date — a genuine § 102(b)/§ 103 timing issue to run down.

Combination C (policy-first)

Hofmeister '313 (provider-network per-flow admission control) + Ericsson '796 (MPLS flow aggregation) + Martini '445 (multi-hop PW) + Nassar '605.

• Hofmeister teaches per-flow ingress/egress admission control in a provider network — the "business policy" trigger of claims 5–6/14–15. Ericsson '796 teaches pushing application/flow descriptors onto MPLS labels (the encapsulation step). Martini and Nassar supply the multi-provider PW routing and inter-provider policy distribution.
• Motivation: Both Hofmeister and Nassar are directed to automating policy-driven provisioning at provider boundaries; the combination requires only that the flow descriptor be derived one layer deeper (application header), which Top Layer '184 shows is a known, beneficial technique.

VIII. Dependent claims

• Claims 2, 10, 19 (send via a PW spanning first and third networks) — met by Martini '445's single logical multi-hop PW (claims 9–10).
• Claims 3, 11, 20 (select from a set of PWs for different application flows) — met by Ericsson '796 + Widegren '793 (multiple flows → per-flow policy/label); one-PW-per-flow is the express teaching of the '176 spec's own VoD example and is inherent in per-flow classification.
• Claims 4, 13 (heterogeneous Ethernet / MPLS / PBB-PBT / optical) — met by Cisco '426 (heterogeneous L2 VPN interworking) and the '176 spec's own concession that networks use Ethernet, SONET/SDH, and IP/MPLS; the '176 record also cites the PBB/PBT-related publication US 2011/0216772 family and Ciena '488 (optical transport).
• Claims 5–6, 14–15 (trigger on business policy; receive policy from a server) — met by Widegren '793 (application-influenced policy from a policy server) and Hofmeister '313/Nassar '605.
• Claims 7, 16 (voice/audio/video payloads) — the '176 spec and Richardson/network-analysis art; ordinary subject matter (VoIP/VoD over RTP was ubiquitous by 2006); Martini Dynamic MS-PW's bandwidth TLV addresses voice.
• Claims 8, 17 (encapsulate when no label established for the flow) — inherent in on-demand PW signaling under Martini '445/LDP.
• Claim 12 (policy specifies max bandwidth for voice) — squarely met by the "interprovider bilateral policy" examples the '176 spec discusses and by Martini Dynamic MS-PW's PW Bandwidth TLV; note the § 112 written-description echo — a claim reciting a policy example from the applicant's own specification invites both § 103 and § 112 challenges.

IX. Anticipated rebuttals and how they fare

1. "K.Mizra will argue no motivation to combine." Weak here: the references are (a) analogous, (b) mutually cross-referencing (Martini, Nassar inter-provider), and (c) the '176 spec concedes the problem and names the IETF building blocks. KSR's "predictable results" and "design need" rationales apply.
2. "The '176 claims don't recite 'determining an application flow'" (a real distinction vs. sibling '638). This cuts both ways: removing that step makes claim 1 broader, which generally makes it easier to invalidate, not harder. A broader claim reads on more prior art.
3. "Secondary considerations." I found no evidence of record of unexpected results, industry praise, licensing due to merit, or a nexus to the claimed features. The chain-of-continuations (2007 → 2014 → 2015 filings) suggests prosecution strategy rather than a benchmark of non-obviousness. Absent nexus evidence, secondary considerations carry little weight.
4. Timing/prior-art status. All patent references predate or (under § 102(e)) are filed before the Aug. 4, 2006 date. The Martini Dynamic MS-PW draft and Metz autodiscovery draft (both 2006) require exact public-availability dates to confirm § 102(b) status; the June 2006 draft and Feb. 25, 2006 Metz draft are close enough to the date that this should be verified.

X. Conclusion

On the record references, claims 1–20 of the '176 patent would have been prima facie obvious over at least:

• Martini '445 + Top Layer '184 + Widegren '793 + Nassar '605 (primary), and
• Bryant RFC 3985 + Martini Dynamic MS-PW + Shah ARP Mediation + Wood '150/Widegren '793 (NPL-centric).

The single-most vulnerable limitation is 1B1 (policy mandating transit through two other providers' networks), which narrowly-construed monopolization-of-all-policy-driven-multi-provider-routing arguments may survive only if K.Mizra can show the combination lacked a reason to link application-layer classification to inter-provider policy selection. The references' shared ancestry in the IETF PWE3/PCE workstreams, and the inventor's own contributions to that workstream, undercut that argument substantially.

XI. Explicit uncertainties

• I could not retrieve Nokia's actual "Exemplary Motivation to Combine for '176 Patent" text or claim charts; my combinations are independent constructions, not reproductions of the parties' positions.
• I did not locate an IPR/PGR petition against the '176 patent; the reexamination event (recorded "RR," effective 2026-02-25) remains unverified as to control number/substance.
• I have not independently verified the full text of Top Layer '184, Ericsson '796, Hofmeister '313, Nassar '605, Wood '150, or the NPL drafts; where I rely on title/abstract, I say so above.
• Any § 112 written-description attack on claim 12 (and the "business policy" claims) should be run against the actual specification paragraphs, which I have only as granted text.