US 6445695

I'll verify the patent details and check for any litigation/docket activity before summarizing.

Verification notes first

I searched for the exact identifier 6445695 / US6445695B1 and deliberately excluded look-alike numbers. Two caveats on method:

• No CAFC 2026 docket activity for this patent surfaced in any search. The appellate results my query returned were unrelated matters (e.g., Headwater v. Verizon, USCA No. 26-1884; Spero v. Mercedes-Benz, No. 2025-1470; FedEx v. Qualcomm, No. 2024-1236). I cannot rule out a sealed or unindexed docket, but I found none, so I will not claim there was one.
• The authoritative record I retrieved is the Google Patents full text (source: https://patents.google.com/patent/[US6445695](/patent/US6445695)/en, fetched 2026-09-28 per that page header), which mirrors the USPTO grant. I did not retrieve a live USPTO PatentCenter/Patent Public Search page as a separate primary source, so bibliographic fields below are grounded in that grant text plus the assignment chain shown on the same page.

Bibliographic summary

Points of ambiguity to flag: the assignment history is messy — there are corrective reassignments and a security-interest release recorded in 2021 whose stated effective date (2020-03-03) predates its recordation (2021-12-06), and one 2012 record spells the owner "CENBAND US LLC" before being corrected to "GENBAND US LLC." I report these literally rather than cleaning them up. Whether Ribbon (rather than Genband US LLC) is the present legal owner is a question for the assignment record, not something this text states definitively.

Abstract (as granted)

"A system and method for supporting communications services on behalf of a communications device which cannot provide those services itself in a communications network based on functional signaling. A terminal is designed to identify a supporting server/terminal proxy upon initialization. Henceforth, the terminal provides each user input stimulus to the server and responds to stimulus from the server. The server manages the state machine of the terminal, provides supplementary services, and meets protocol requirements for the network interface."

Plain-language overview of the independent claims

The patent has four independent claims falling into three statutory buckets: one system claim (1, with dependent claims 2–13), one method claim (14), one means-plus-function system claim (15), and one computer-program-product claim (16).

Claim 1 — System (apparatus).
A "client proxy signaling system" for an IP telephony network made of two things: (a) at least one terminal connected to an IP network, and (b) a terminal proxy connected to that same IP network and able to communicate with the terminal, which provides "logical call processing signaling on behalf of" the terminal. The closing clause is the heart of it: the terminal proxy communicates with and manages the call processing logic for the terminal "with respect to the remainder of a telephony network." In plain terms: a thin/cheap endpoint plus a network-resident server that does the endpoint's call-control thinking for it, so the rest of the telephony world sees a normal, fully-featured endpoint.

Claim 14 — Method.
Two steps: (a) the terminal identifies its terminal proxy on the IP network when it initializes (i.e., the endpoint discovers its supporting server at boot/registration — the spec likens this to DHCP or manual keying), and (b) the terminal and proxy exchange call processing messages so that the proxy manages call processing logic on the terminal's behalf vis-à-vis the rest of the telephony network. Plain terms: "find your brain at startup, then keep feeding it stimuli and obeying its commands."

Claim 15 — Means-plus-function system.
Same substance as claim 14, expressed as means for performing each of the two steps ("means for identifying a terminal proxy… upon initialization" and "means for exchanging call processing messages…"). Under the final paragraph of the specification, the recited means are intended to cover the corresponding structures disclosed and their equivalents — here, the terminal-proxy software entity and the stimulus-protocol interface between endpoint and proxy described in connection with FIG. 1 and FIG. 2.

Claim 16 — Computer program product.
Same two functional steps again, but claimed as program code embodied on a medium: code for identifying the terminal proxy at initialization, and code for exchanging call processing messages so the proxy manages call processing on the terminal's behalf. The specification expressly contemplates storage on diskette, hard disk, CD-ROM, tape, ROM/RAM, or transfer over a data network.

Dependent claims in brief (not independent, but they carry most of the technical specificity): claim 2 adds a terminal adapter between non-IP terminals (e.g., 2500-type POTS sets) and the IP network, converting the terminal's call-control protocol into an IP protocol; claim 3 specifies SGCP between terminal adapter and terminal proxy; claims 4–8 specify H.323 between terminal proxy and a network server, with the network server being a PSTN central office switch, a PBX, an H.323 gatekeeper, or a SIP proxy respectively; claims 9–13 repeat that network-server list but with a Q.931 stimulus-protocol subset in place of H.323. Reported verbatim, the specification also describes UNISTIM IP as the endpoint-to-proxy stimulus protocol in one embodiment.

What the patent says distinguishes it from prior approaches

Per the specification itself: the terminal proxy is not a network call-processing engine and is not physically in the media path. It is described as a "signaling translator" that is only logically between the endpoint and the telephony server, and it "makes a terminal look like a terminal of another type from the perspective of the IP PBX controller or the central office." This is the distinction the applicant drew against (i) IP PBX controllers and (ii) analog-to-digital "black box" adapters that sit physically between a PBX and a phone and process media.

Confidence and open items

• High confidence on title, inventor, assignee chain as recorded, dates, abstract text, claim set, and claim summaries — all taken from the granted text.
• Moderate confidence on the current owner identification, for the reassignment-spelling reasons noted above.
• Low/unverified: any CAFC 2026 activity (none found), and the substance of the 2007 Delaware case 1:07-cv-00507 (the patent page links it but the search results did not return a docket or outcome). If you need those, they should be confirmed directly against PACER/CM-ECF and the Federal Circuit docket rather than inferred.

I'll research litigation involving US patent 6445695 across patent litigation databases.

Litigation involving US 6,445,695

I searched litigation-specific sources (Google Patents' litigation/family links, Unified Patents, Justia Dockets/Justia Patents, CourtListener/RECAP, the Stanford NPE litigation database, and SEC/EDGAR disclosures that describe the disputes). One litigation matter involving US 6,445,695 has been identified. No appellate (CAFC) proceeding and no PTAB/IPR proceeding involving this patent was found.

Case 1 — Vonage Holdings Corp. v. Nortel Networks Inc. and Nortel Networks Ltd.

Details and grounding:

• The court's AO-120 "Report on the Filing or Determination of an Action Regarding a Patent" in this case (D. Del., Doc. 4, filed 08/20/2007) lists the plaintiff as "Vonage Holding Inc.," the defendants as "Nortel Networks Inc." and "Nortel Networks Ltd.," and the patents as 6,091,808 (holder: Nortel Networks Corporation), 6,445,695 B1 (holder: Nortel Networks Limited), and 7,050,861 B1 (holder: Nortel Networks Limited). This is the most direct evidence that '695 was placed in suit.
• Vonage sought a declaratory judgment that the Nortel patents were "invalid, void and/or unenforceable" (Justia docket summary for 1:2007cv00507).
• The Delaware action was a response to Nortel's motion to add counter-counterclaims in a parallel Texas case (see Case 2). Nortel's counsel argued that "Vonage has brought a declaratory-judgment action against it in a Delaware court regarding the Nortel-asserted patents. Thus, at this point … there is no question that [its asserted patents] will be litigated."
• Termination: Vonage's Form 8-K (filed March 14, 2008) states that on March 10, 2008, Vonage and Nortel entered a Settlement Agreement effective January 1, 2008, implementing a Memorandum of Understanding dated December 28, 2007. Under it the parties agreed to file, within five days, joint stipulations of dismissal, without costs, dismissing without prejudice all claims and counterclaims in the Delaware action (and in the Texas action). The deal was a limited cross-license of three Nortel and three Vonage patents with no monetary payments, with claims as to past damages and the remaining patents dismissed (Reuters, Bloomberg, CBC reports of Dec. 31, 2007; Vonage 8-K). The Patent Settlement Agreement is publicly available (contracts.justia.com, Vonage Holdings Corp.).

Uncertainty to flag: The complaint in the Delaware action (the DJ filing) covered '695. I could not confirm with high confidence whether Nortel's counterclaims in that same Delaware case separately asserted '695 — Nortel's December 14, 2007 answer/counter-counterclaim document that I located asserts the '808, 6,823,370, 7,035,390, 6,934,279, 6,337,858, 6,798,786, 5,991,389, and 6,799,210 patents. That excerpt may be partial, so treat the counterclaim list as incomplete.

Case 2 — Related Texas action (context; '695 appears only as the subject of a denied motion)

Matters checked where '695 was NOT asserted

• Genband US LLC v. Metaswitch Networks Ltd. / Metaswitch Networks Corp., No. 2:14-cv-00033 (E.D. Tex., filed Jan. 21, 2014) and 2:16-cv-00582; and Metaswitch Networks Ltd. v. Genband US LLC, No. 2:14-cv-00744. The asserted Nortel-origin patents were 6,772,210; 6,791,971; 6,885,658; 6,934,279; 7,995,589; 7,047,561; 7,184,427; and 7,990,984 — '695 was not among them.
• No CAFC appeal and no IPR/PGR/CBM proceeding on '695 was found.

Ownership/status notes (not litigation, but relevant to standing)

• '695 issued Sept. 3, 2002 to Nortel Networks Limited (inventor Samuel H. Christie, IV; original assignee Northern Telecom Limited, later Nortel Networks Ltd.).
• It passed to Genband US LLC via the Nortel CVAS transaction (2010); the assignment reel cited by the court in the Metaswitch discovery order for the "Nortel Transferred Patents" is Reel 024879/0519, which is the very assignment recorded for this patent, corrected by Reel 027992/0443.
• Current listed assignee: Ribbon Communications Operating Company, Inc. (f/k/a Genband US LLC and Sonus Networks, Inc.). Legal status: Expired – Lifetime (anticipated expiration Dec. 31, 2018).

Bottom line

Only one litigation is known in which US 6,445,695 was actually placed at issue: Vonage Holdings Corp. v. Nortel Networks Inc. and Nortel Networks Ltd., D. Del. No. 1:07-cv-00507-GMS, filed August 17, 2007, in which Vonage sought a declaratory judgment of invalidity/unenforceability of '695 (along with 6,091,808 and 7,050,861). It was terminated by the December 2007/January 2008 Nortel–Vonage cross-license settlement and dismissed without prejudice in 2008, with no monetary payment. '695 was also named in the Nortel-asserted-patents group in the related N.D. Tex. action (4:04-cv-00548-Y), but the court refused to allow those claims into that case. I found no infringement suit that proceeded to judgment on '695.

Sources: Google Patents US6445695B1 (litigation link to D. Del. case 1:07-cv-00507); D. Del. AO-120 Patent/Trademark Report, Case 1:07-cv-00507-GMS (Doc. 4, 08/20/2007); Justia Docket, Vonage Holdings Corp. v. Nortel Networks Inc. et al., 1:2007cv00507; N.D. Tex. Order, Doc. 280 in 4:04-cv-00548-Y (Oct. 30, 2007); Vonage 8-K, March 14, 2008; Vonage–Nortel Patent Settlement Agreement; Reuters, "Vonage and Nortel settle patent dispute," Dec. 31, 2007; CBC News, "Nortel, Vonage agree to patent truce"; Genband v. Metaswitch findings of fact (E.D. Tex. 2:14-cv-00033).

I'll verify the structured "no AIA proceedings" default against live sources before reporting.

Proceedings overview

There are no AIA trial proceedings on file for US 6,445,695 — zero IPRs, zero PGRs, zero CBMs. By status: 0 active, 0 with claims invalidated, 0 with claims sustained, 0 settled, 0 institution denials. This matches the canonical "PTAB proceedings on file" block from the USPTO Open Data Portal, and my independent web searches returned no proceeding (IPR/PGR/CBM) naming this patent. The defensive posture for a defendant is therefore not "the patent has been hardened by surviving IPRs" and not "claims have been canceled." It is: the patent was never administratively tested, and instead died of old age — the 20-year term ran out on 2018-12-31. Expiration, not PTAB invalidation, is your principal shield. That cuts both ways: you have no FWD to hide behind, but you also inherit no estoppel and face no PTAB-loss momentum against you.

No proceedings to enumerate

I cannot write proceeding-by-proceeding entries because there are no proceeding numbers to write, and I will not invent them. What I can document is the verification trail and the near-misses, because in a zero-result setting the false positives are the real analytical work.

Adjacent proceedings examined and expressly excluded (false positives):

Why zero is plausible here, not just an indexing gap:

1. Timing. The AIA trial regime began 2012-09-16. This patent was filed and granted long before, so it was IPR-eligible from day one of the regime (35 U.S.C. § 311(c) applies to any patent, regardless of filing date). But the patent's known assertion activity — the Delaware case cited on its face — dates to 2007, five years before IPRs existed. By the time IPRs were available, the 2007 case was long over, and the patent had roughly six years of term left.
2. Expiration. The term expired 2018-12-31 (per the record). An expired patent can still be IPR'd, but the practical incentive collapses once prospective infringement (and injunctive exposure) is off the table.
3. CBM is not a fit. CBM review (AIA § 18) required a claim directed to a financial product or service, and the Federal Circuit's Unwired Planet line narrowed that further. A terminal-proxy/signalling-translator telephony patent would not qualify. Also, CBM sunset in 2020.

Confidence and open items (stated plainly): I could not drive the PTAB E2E / Patent Trial and Appeal Board End-to-End search UI directly, so my confirmation rests on (a) the ODP structured data block, which is canonical, and (b) absence of any hit across multiple targeted web searches. If a very old proceeding existed, it would be a post-institution IPR from the 2012–2018 window; I found none. Residual risk is low but non-zero. One specific blind spot: ex parte reexamination is not an AIA trial and would not appear in this data at all — if you need the full administrative history, that has to be checked separately (see next steps).

Strategic summary

Claim status across the patent: no claims are canceled, none are sustained, and all 16 — claims 1–16, including independents 1, 14, 15, and 16 — are UNTESTED. There has been no administrative adjudication of any claim. Every claim stands exactly as granted in 2002, un-narrowed by any PTAB amendment or disclaimer. Practically, that means the claim set a plaintiff would assert today is the full original set: independent claim 1 (system: terminal + terminal proxy managing call processing logic for the terminal vis-à-vis the rest of the telephony network), claim 14 (method: identify proxy at initialization + exchange call processing messages), claim 15 (means-plus-function version of the same), and claim 16 (computer program product), plus dependents 2–13. Nothing is "dead." Conversely, nothing has been validated by the PTAB either — there is no FWD you can point to as a considered-rejected challenge.

Estoppel landscape: there is none, and that is affirmatively good for a defendant. Section 315(e)(2) estoppel arises only against "the petitioner in an inter partes review that results in a final written decision," and its privies. With no petition and no FWD, no estoppel attaches to anyone. Every prior-art ground remains available to a defendant in district court, including grounds an IPR petitioner could have raised — and, critically, grounds an IPR petitioner could not have raised, because IPR is limited to patents and printed publications under §§ 102/103 (35 U.S.C. § 311(b)). For this patent that leaves the full § 282 invalidity menu open: public use, on-sale, and prior-art system evidence (highly relevant for 1998-era telephony — Nortel's own UNISTIM IP deployments, SGCP/UNISTIM documentation, and contemporaneous VoIP product literature are the obvious hunting grounds); § 112 challenges to the very broad functional language of claims 1/14/15/16 and to the "means for identifying/exchanging" claim 15 (no corresponding structure may be adequately disclosed); and § 101 for the software-implemented method and CRM claims. The catch is the burden: § 282 presumption of validity, clear and convincing evidence, and a trial that would have to reconstruct 1998 art with the file history in hand.

Pattern signals: none to read. No serial petitioner, no repeat filer, no defensive aggregator, no PTAB appeals, and no CAFC docket activity for this patent (consistent with the previously generated note finding no 2026 appellate activity). The absence of a "pattern" is itself the finding: this is a pre-AIA patent with a 2007 litigation footprint, a modest remaining term that expired in 2018, and no administrative challenge history — the profile of a patent that was litigated before IPRs existed and then aged out.

Recommended next steps

• Do not build a defense narrative around a PTAB outcome — there isn't one. There is no Final Written Decision to link to and no claim-disposition language to quote. Any brief asserting otherwise, or citing a proceeding number for this patent, would be a fabrication risk.
• Lead with expiration. Confirm the 2018-12-31 expiration date directly against USPTO Patent Center (application 09/223,880) before relying on it, since a maintenance-fee lapse or a terminal-disclaimer/PTA adjustment could shift the operative end date. If the patent is expired, prospective injunctive relief and ongoing royalties are off the table; exposure shrinks to pre-2018-12-31 damages, which then becomes a limitations/§ 287 notice and damages-apportionment fight.
• If you are defending historical (2002–2018) damages, go straight to district court invalidity using the non-IPR-capable art IPRs could never have reached: § 102(b) public-use and on-sale evidence, plus system prior art, alongside § 112 indefiniteness against claim 15's means-plus-function recitations and § 101 against claims 14–16. Because no estoppel exists, nothing is foreclosed.
• Close the ex parte reexamination gap. Because the ODP AIA-trial data structurally excludes reexaminations, have someone run the patent's full prosecution/reexam history in USPTO Patent Center or Patent Public Search. If an ex parte reexam occurred, the claims sitting in the file today may not be the claims as granted — which would change everything above.
• Mirror-check the enforcement chain. Confirm the current owner of record (the assignment history here is messy — corrective reassignments, a 2021 release with a 2020 effective date, and one "GENBAND"/"CENBAND" spelling error), and pin down what actually happened in D. Del. 1:07-cv-00507, which neither this analysis nor the prior section verified. Standing and prior-litigation estoppel are the two issues most likely to matter if a new demand surfaces.

Bottom line for a defendant: there is no PTAB record to exploit and none to fear. The patent has never been administratively challenged, so no claim is canceled and no FWD exists — but it expired on 2018-12-31, so verify the date, attack any residual historical-damages theory on the merits in court, and treat the "zero proceedings" result as the absence of evidence rather than evidence of the patent's strength.

I'll research the assignment record and correspondent details before reconstructing the chain.

Let me dig into correspondent details and the asserter directories.

Inventors

Unusual-pattern check: No unusual pattern. There is a single inventor, not a team, so the "all inventors departed within 12 months" tell cannot arise. No inventor-side assignment separate from the corporate chain appears in the record. Nothing in the chain (see below) shows an inventor retaining or re-acquiring rights.

Original assignee

Northern Telecom Limited (Canada), per Reel 009769/0634. That entity was renamed twice on the corporate record, not sold:

• Northern Telecom Limited → Nortel Networks Corporation (Reel 010567/0001, effective 1999-04-29).
• Nortel Networks Corporation → Nortel Networks Limited (Reel 011195/0706, effective 2000-08-30). This is the entity that appears as the holder on the issued patent and on the D. Del. AO-120 patent report in the 2007 Vonage case.

Primary line of business: Nortel was, at the time, one of the largest global telecom-equipment vendors (carrier switching, optical, wireless, and enterprise VoIP). The patent itself names a Nortel-proprietary protocol ("UNISTIM IP") as the endpoint-to-proxy stimulus protocol and describes a terminal-proxy/client-server architecture, which is consistent with Nortel's actual IP-telephony product line (UNISTIM-based IP sets driven by a centralized call server).

Did they ship a product embodying the claims? Plausible and likely, on the face of the specification (the spec describes a Nortel in-house protocol rather than an abstract reference), but I could not verify a specific shipping product from a primary source in this pass — treat this as moderate confidence, not confirmed.

Current status of the original assignee: Insolvent / sold off. Nortel sought creditor protection in January 2009 (Chapter 11 in the U.S. and CCAA in Canada). Its Carrier VoIP and Applications Solutions (CVAS) business — including the VoIP patent family this patent belongs to — was sold to Genband in 2010, which is the transaction reflected in the 2010 assignment entries below.

Assignment timeline

The USPTO Assignment Center / Patent Assignment Search does have records for this patent — the chain below is reconstructed from the recorded legal events on the grant (reel/frame numbers as recorded). Important method caveat up front: the source I retrieved (Google Patents' legal-events mirror of the USPTO record) exposes reel/frame, conveyance, assignor, assignee, execution/effective date, and recording date, but it does not expose the correspondent-of-record field. My attempts to pull the underlying assignment PDFs / Assignment Center summary pages by reel-frame did not return correspondent names in searchable form. So I can report the chain faithfully but I cannot supply attorney correspondents — that is an open item, not a negative finding, and it is flagged again in the signals section.

Chronological list:

• 1999-01-12 (executed) / recorded 1999-02-17 — Reel 009769/0634

  • Conveyance: Assignment of assignors interest
  • Assignor: Christie, Samuel H., IV
  • Assignee: Northern Telecom Limited
  • Correspondent: not retrievable (see caveat above).
  • Context: original inventor-to-employer assignment at filing.

• 1999-04-29 (effective) / recorded 1999-12-23 — Reel 010567/0001

  • Conveyance: Change of Name
  • Assignor: Northern Telecom Limited
  • Assignee: Nortel Networks Corporation
  • Correspondent: not retrievable.
  • Context: change of name only — no transfer of ownership.

• 2000-08-30 (effective) / recorded 2000-08-30 — Reel 011195/0706

  • Conveyance: Change of Name
  • Assignor: Nortel Networks Corporation
  • Assignee: Nortel Networks Limited
  • Correspondent: not retrievable.
  • Context: change of name only.

• 2005-10-24 (effective) / recorded 2010-03-09 — Reel 024045/0401

  • Conveyance: Release of Security Interests
  • Assignor: JPMorgan Chase Bank, N.A.
  • Assignee: Nortel Networks Limited
  • Correspondent: not retrievable.
  • Context: release of a pre-existing lender lien — securitization cleanup (note: the grant of that JPMorgan security interest is not separately shown on this patent's event list; only the release is, which is itself an open item).

• 2010-05-27 (effective) / recorded 2010-08-25 — Reel 024879/0519

  • Conveyance: Assignment of interest
  • Assignor: Nortel Networks Corporation
  • Assignee: Genband US LLC
  • Correspondent: not retrievable.
  • Context: bankruptcy-era asset sale — the Nortel CVAS transaction. This is the substantive ownership transfer off Nortel.

• 2010-05-27 (effective) / recorded 2010-06-02 — Reel 024468/0507

  • Conveyance: Change of Name
  • Assignor: Genband Inc.
  • Assignee: Genband US LLC
  • Correspondent: not retrievable.
  • Context: change of name only (Genband Inc. → Genband US LLC).

• 2010-05-28 (effective) / recorded 2010-06-18 — Reel 024555/0809

  • Conveyance: Patent Security Agreement
  • Assignor: Genband US LLC
  • Assignee: One Equity Partners III, L.P., as Collateral Agent
  • Correspondent: not retrievable.
  • Context: securitization — secured financing in connection with the Genband acquisition.

• 2010-10-28 (effective) / recorded 2010-11-09 — Reel 025333/0054

  • Conveyance: Security Agreement
  • Assignor: Genband US LLC
  • Assignee: Comerica Bank
  • Correspondent: not retrievable.
  • Context: securitization — second secured lender.

• 2010-05-27 (effective) / recorded 2012-03-30 — Reel 027992/0443

  • Conveyance: Corrective Assignment (to correct the conveying-party data recorded at Reel 024879/0519 by adding Nortel Networks Limited as an assignor alongside Nortel Networks Corporation)
  • Assignor: Nortel Networks Limited; Nortel Networks Corporation
  • Assignee: Genband US LLC
  • Correspondent: not retrievable. (The related 2012 record is the one that momentarily renders the assignee as "CENBAND US LLC" before correction — flagged in the earlier section.)
  • Context: record correction, not a new transfer.

• 2012-12-19 (effective) / recorded 2014-01-10 — Reel 031968/0955

  • Conveyance: Release by Secured Party
  • Assignor: One Equity Partners III, L.P., as Collateral Agent
  • Assignee: Genband US LLC
  • Correspondent: not retrievable.
  • Context: securitization — lien release.

• 2016-07-01 (effective) / recorded 2016-07-06 — Reel 039269/0234

  • Conveyance: Patent Security Agreement
  • Assignor: Genband US LLC
  • Assignee: Silicon Valley Bank, as Administrative Agent
  • Correspondent: not retrievable.
  • Context: securitization — refinancing.

• 2016-07-01 (effective) / recorded 2016-07-07 — Reel 039280/0467

  • Conveyance: Release and Reassignment of Patents
  • Assignor: Comerica Bank, as Agent
  • Assignee: Genband US LLC
  • Correspondent: not retrievable.
  • Context: securitization — prior lien released on refinancing.

• 2016-07-01 (effective) / recorded 2017-01-03 — Reel 041422/0080

  • Conveyance: Corrective Assignment (to correct patent no. 6,381,239 previously recorded at Reel 039269/0234)
  • Assignor: Genband US LLC
  • Assignee: Silicon Valley Bank, as Administrative Agent
  • Correspondent: not retrievable.
  • Context: record correction of the SVB security agreement.

• 2017-12-21 (effective) / recorded 2017-12-29 — Reel 044986/0303

  • Conveyance: Termination and Release of Patent Security Agreement
  • Assignor: Silicon Valley Bank, as Administrative Agent
  • Assignee: Genband US LLC
  • Correspondent: not retrievable.
  • Context: securitization — first SVB lien terminated as part of a refinancing round.

• 2017-12-29 (effective) / recorded 2018-01-02 — Reel 044978/0801

  • Conveyance: Security Interest
  • Assignor: Genband US LLC; Sonus Networks, Inc.
  • Assignee: Silicon Valley Bank, as Administrative Agent
  • Correspondent: not retrievable.
  • Context: securitization — replacement SVB lien covering both Genband and Sonus as the two companies integrated (Genband/Sonus become Ribbon).

• 2020-03-03 (effective) / recorded 2020-03-03 — Reel 052076/0905

  • Conveyance: Security Interest
  • Assignor: Ribbon Communications Operating Company, Inc.
  • Assignee: Citizens Bank, N.A., as Administrative Agent
  • Correspondent: not retrievable.
  • Context: securitization — new lender replacing SVB.

• 2020-03-03 (effective) / recorded 2021-12-06 — Reel 058949/0497

  • Conveyance: Termination and Release of Patent Security Agreement at R/F 044978/0801
  • Assignor: Silicon Valley Bank, as Administrative Agent
  • Assignee: Ribbon Communications Operating Company, Inc. (f/k/a Genband US LLC and Sonus Networks, Inc.)
  • Correspondent: not retrievable.
  • Context: securitization — SVB lien formally cleared. (Note the recorded date (2021-12-06) post-dates the stated effective date (2020-03-03) by ~21 months — reported literally.)

• 2024-06-20 (effective) / recorded 2024-06-24 — Reel 067822/0433

  • Conveyance: Release by Secured Party
  • Assignor: Citizens Bank, N.A.
  • Assignee: Ribbon Communications Operating Company, Inc.
  • Correspondent: not retrievable.
  • Context: securitization — final recorded lien release.

What this chain is: one true ownership transfer off the original assignee (Reel 024879/0519, Nortel → Genband US LLC, 2010) plus a run of name changes, record corrections, and secured-lien recordings/releases spanning 2005–2024. There is no chain of successive LLC-to-LLC assignments.

Timeline diagram

timeline
    title Ownership and liens US 6445695
    1999 : Christie assigns to Northern Telecom
         : Renamed Nortel Networks Corporation
    2000 : Renamed Nortel Networks Limited
    2005 : JPMorgan security interest released
    2010 : Nortel insolvency sale to Genband US LLC
         : Genband Inc renamed Genband US LLC
         : One Equity Partners security interest
         : Comerica Bank security agreement
    2012 : Corrective assignment adds Nortel Networks Limited
    2014 : One Equity Partners release
    2016 : Silicon Valley Bank security agreement
         : Comerica Bank release
    2017 : SVB lien terminated and replaced
    2018 : SVB security interest recorded
         : Patent term expires
    2020 : Citizens Bank security interest
    2021 : SVB termination recorded
    2024 : Citizens Bank release

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT.
Every entity that ever held title is a product-shipping telecom vendor (Northern Telecom Limited → Nortel Networks Corporation → Nortel Networks Limited via Reels 010567/0001 and 011195/0706; then Genband US LLC via Reel 024879/0519), and the chain's terminus is Ribbon Communications Operating Company, Inc. (Reel 058949/0497; Reel 067822/0433). No "IP / Patents / Licensing / Holdings / Ventures" LLC appears anywhere. Note the countervailing evidence against a shell reading of Genband US LLC: it carried multiple rounds of secured bank debt (Reel 024555/0809 One Equity Partners; Reel 025333/0054 Comerica Bank; Reel 039269/0234 and 044978/0801 Silicon Valley Bank; Reel 052076/0905 Citizens Bank) and, per the Metaswitch complaint, employed ~335 people in the E.D. Tex. district. Shells do not typically sustain that financing and headcount profile.

2. Known asserter in the chain — NOT PRESENT.
None of the assignees at any link matches the tracked NPE lists (Acacia, Marathon, IV, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, Innovatio, MPHJ, Lumen View, Round Rock, Document Generation Corp, Spangenberg entities, RPX/Unified high-frequency plaintiffs). Genband and Ribbon are frequent litigants, but as operating vendors suing/being sued by competitors (e.g., Genband v. Metaswitch, E.D. Tex. 2:14-cv-00033; Metaswitch v. Genband, 2:14-cv-00744) — that is ordinary operating-company litigation, not NPE assertion.

3. Repeat correspondent across the chain — UNCLEAR (cannot be evaluated on the evidence retrieved).
This is the one signal I cannot score either way, and it is the signal the task most emphasized. I could not retrieve the correspondent-of-record field for any of the ~19 entries. The Google Patents legal-event mirror omits it, and my searches for the underlying Assignment Center summary pages / assignment PDFs (by reel-frame, e.g. 009769/0634, 024879/0519, 024468/0507) returned the bibliographic fields but no attorney or recording-firm names. I am therefore not reporting a repeat correspondent as present, and I am not reporting it as absent — it is untested. The correct way to close this is to open each conveyance's PDF icon in the Assignment Center (see verification link below) and read the "Correspondent" block; that is a 15-minute manual task I could not complete via search. Do not treat the corporate-secretary/registered-agent conventions visible in the Genband-era records as an attorney finding — that would be inferring from naming alone.

4. Cascading transfers (<24 months through chained LLCs) — NOT PRESENT.
The ownership moves are decades apart (1999 inventor assignment; 2010 Nortel→Genband sale). Everything between 2010 and 2024 is lien activity and name/record corrections (Reels 024555/0809, 025333/0054, 027992/0443, 031968/0955, 039269/0234, 039280/0467, 041422/0080, 044986/0303, 044978/0801, 052076/0905, 058949/0497, 067822/0433). No LLC-to-LLC chain.

5. Pre-litigation transfer — NOT PRESENT.
The only matter that put '695 at issue was Vonage's declaratory-judgment complaint filed 2007-08-17 (D. Del. 1:07-cv-00507). At that time title was still with Nortel Networks Limited — the 2010 Genband transfer (Reel 024879/0519) came ~3 years after the suit, not within 6 months before it. There is no transfer timed to enable the assertion.

6. Bankruptcy fire-sale — PRESENT (factually).
Nortel entered insolvency proceedings in January 2009, and the ownership transfer at Reel 024879/0519 (effective 2010-05-27, recorded 2010-08-25) moved this patent from Nortel Networks Corporation to Genband US LLC as part of the Nortel CVAS disposition. This is corroborated by (i) Genband's own 37 C.F.R. § 3.73(b) statement in application 09/735,427 listing the chain of title, and (ii) the Nortel bankruptcy court's definition of "Nortel Transferred Patents" by reel numbers 27992-443, 24879-519, 24879-475. Caveat that matters for NPE scoring: the buyer was an operating vendor making a strategic business-line acquisition, not a licensing entity acquiring the patent to assert it — so this is a fire-sale of assets, not a fire-sale to a troll.

7. Privateering — NOT PRESENT (no evidence).
Nothing in the record or in the retrieved coverage shows Nortel transferring the patent to an NPE to assert on Nortel's behalf against competitors. No SEC disclosure or Patent Progress/EFF-style coverage surfaced to that effect.

8. Defensive aggregator — NOT PRESENT.
The chain terminates at Ribbon Communications Operating Company, Inc., an operating VoIP/optical vendor — not RPX, AST, LOT Network, Unified Patents, or OIN. The patent was not neutralized by a defensive aggregator; it simply expired.

Verdict

Operating-company assertion.

The entire chain is operating-company-to-operating-company: inventor → Northern Telecom Limited (Reel 009769/0634), two name changes (Reels 010567/0001, 011195/0706), the Nortel bankruptcy-era sale to Genband US LLC (Reel 024879/0519, effective 2010-05-27), and finally Ribbon Communications Operating Company, Inc. (Reels 058949/0497, 067822/0433) — all product-shipping telecom vendors, with the intervening records being bank liens and their releases (Reels 024555/0809, 025333/0054, 039269/0234, 044978/0801, 052076/0905) plus corrective filings (Reels 027992/0443, 041422/0080). No licensing-only entity ever held title, and no transfer was timed to enable the one 2007 Vonage declaratory-judgment action, which was brought while Nortel still owned the patent.

Two honest caveats: (i) the correspondent-of-record signal is unscored because I could not retrieve attorney names from the sources available to me — that is the single gap in this analysis and it is worth closing manually; and (ii) of the available verdict labels, "Operating-company assertion" is the best fit for a chain that is unquestionably non-NPE, though the strict second prong (current assignee affirmatively suing competitors on this patent) is not met — '695 was never affirmatively asserted by its owner and it reached full-term expiration on 2018-12-31.

Verification link: USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search by patent number 6445695); mirror index at https://assignment.uspto.gov/patent/index.html. Corroborating primary sources used: Google Patents legal events for US6445695B1 (https://patents.google.com/patent/US6445695B1/en); Genband's 37 C.F.R. § 3.73(b) chain-of-title statement in application 09/735,427 (Reels 011195/0706, 024468/0507, 024879/0519, 024879/0475); D. Del. bankruptcy record defining "Nortel Transferred Patents" by those reels; and the Metaswitch v. Genband complaint (E.D. Tex. 2:14-cv-00744) describing Genband US LLC as a Delaware LLC with a Corporation Service Company registered agent and ~335 district employees.

I'll research the specific prior-art references cited against US 6,445,695. Let me pull the granted patent and each examiner citation from authoritative sources.

Now let me retrieve the remaining citations.

⚠️ Note on a date discrepancy before I start: the system header for this session gives today as 2026-09-28, while this task block says "Current Date: April 26, 2026." I'm flagging it per the "flag contradictions" instruction and proceeding with the reference analysis, which does not depend on which of those is correct.

Prior art cited against US 6,445,695 B1

1. Scope and method

Patent under analysis (confirmed, not auto-corrected): US 6,445,695 B1, "System and method for supporting communications services on behalf of a communications device which cannot provide those services itself," App. No. 09/223,880, filed/priority 1998‑12‑31, granted 2002‑09‑03, sole inventor Samuel H. Christie, IV, original assignee Nortel Networks.

Source used: the granted front page and full text as mirrored at Google Patents — https://patents.google.com/patent/US6445695/en (the same record relied on in the previously generated sections). The front page carries a single left-column list headed "Patent Citations (9)" (duplicated in the machine-readable block as "Citations (9)"), and every entry in it is marked with a "*" = cited by the examiner. So the complete prior-art set considered against '695 in the record I retrieved is exactly nine patent documents, all examiner-cited, with no non-patent-literature citations shown.

Two lists on the page that are NOT prior art against '695 (call these out so they aren't confused): "Cited By (33)" / "Cited By (76)" are forward citations — later documents that cite '695 — and "Similar Documents" is a Google similarity list. Neither is a §102 reference. (Minor internal inconsistency on the page: the forward-citation table is headed "Cited By (33)" in one place and "Cited By (76)" in another; I report both literally rather than reconciling them.)

Limits of my verification: I retrieved the grants/publications for US 6,031,896, US 6,259,691, US 6,229,804, and US 2001/0026548 A1 directly. I did not retrieve full text for US 2001/0028649 A1, US 2002/0018464 A1, US 6,161,008 A1, US 2001/0028654 A1, or US 6,275,574 B1 — their bibliographic data below comes from the '695 front page, and their descriptions are my characterization from title/field with the confidence level stated. I also did not obtain an independent USPTO PatentCenter page for '695 (tool limits), so bibliographic fields rest on the grant text as mirrored on Google Patents.

2. Legal framework

'695 was filed 1998‑12‑31, i.e., before the AIA first-inventor-to-file provisions (effective for applications filed on/after 2013‑03‑16). Pre-AIA 35 U.S.C. §§ 102/103 therefore govern. Because every one of the nine references has a US filing/priority date earlier than 1998‑12‑31, the operative subsection is principally pre-AIA § 102(e) (a US patent or published application "by another filed in the United States before the invention by the applicant"). The issued patents in the list (6,031,896; 6,161,008; 6,229,804; 6,259,691; 6,275,574) all issued after the '695 filing date, so they cannot be § 102(a)/(b) "patented/published" art as of the filing date, but they qualify under § 102(e) as of their US filing dates. The four pre-grant publications (2001/0026548; 2001/0028649; 2002/0018464; 2001/0028654) likewise qualify under § 102(e) as of their earliest US filing date.

Anticipation vs. obviousness — the key caveat. Anticipation under § 102 requires a single reference to disclose every element of the claim as arranged. On their face, none of the nine references discloses the full combination of independent claim 1 (thin terminal + network-resident terminal proxy that "manages the call processing logic for said at least one terminal with respect to the remainder of a telephony network"), or of claims 14/15/16 (terminal identifying its proxy at initialization + exchanging call-processing messages so the proxy manages call processing on the terminal's behalf). Each reference therefore is best characterized as § 103 art; I flag the one or two that come closest to a § 102 read on an individual limitation.

3. The nine cited references (bibliographic table, as listed on the '695 front page)

(The '695 page separately shows a 6,161,008 entry once in "Patent Citations" and once in "Citations"; where the assignee is shown it is Nortel Networks Limited.)

4. Per-reference analysis

1. US 2001/0026548 A1 — Strathmeyer, "Apparatus and method for computer controlled call processing applications in packet switched telephone networks"

• Dates: priority/filing 1997‑10‑21 (continuation-in-part of App. 08/955,834); published 2001‑10‑04. The '695 page also attributes a co-inventor "Finnie, Donald." (The family later issued as US 6,901,068 B1 and US 9,497,230 B2.) Verified text: https://patentimages.storage.googleapis.com/1e/dc/00/7844e87f9c2297/US20010026548A1.pdf
• Description (verified): Adds a CTI interface onto an H.323 gatekeeper (called a "call controller") so that external application computers can monitor and control calls "in progress at an endpoint," including establishing/tearing down calls, transferring, conferencing, determining call state/length, and routing unanswered calls. The application computer may be remote and exchanges packetized messages with the gatekeeper over the data network; the gatekeeper performs the call control "on behalf of" the external application.
• § 102 assessment: The reference has the architectural inverse of '695 — an outside brain (application computer) driving a network call controller, rather than a network proxy supplying the terminal's own intelligence. It does not disclose a terminal that "cannot provide those services itself" relying on a proxy for its call-processing state. Not anticipatory of claims 1/14/15/16; strong § 103 art for claim 1's "network entity performing call processing logic ... with respect to the remainder of a telephony network," and for the H.323/gatekeeper limitations of claims 4 and 7.

2. US 2001/0028649 A1 — Pogossiants, "Using XML expressed primitives for platform and system-independent call modeling"

• Dates: priority 1998‑02‑17; published 2001‑10‑11.
• Description (from title/field; full text not retrieved): Representing telephony call models as XML-expressed primitives so call processing is platform- and system-independent.
• § 102 assessment: This is about how call logic is modeled/described, not about where it executes on a terminal's behalf. It supplies no terminal-proxy or per-terminal delegation. § 103 art at most, directed to claims 1 and 14's "call processing logic" and to the prototype "server provides supplementary services" theme.

3. US 6,259,691 B1 — Naudus, "…efficiently transporting DTMF/MF tones…" (verified)

• Dates: filed 1998‑07‑24 (App. 09/122,201), issued 2001‑07‑10; 3Com Corporation; inventor Stanley T. Naudus. https://uspto.report/patent/grant/6259691 ; https://patents.google.com/patent/US6259691
• Description (verified): A VoIP gateway method/system that detects DTMF in the audio stream, removes it into a separate DTMF stream, and imposes an audio delay (via talk-spurt elongation or fill packets) to realign the two streams; delay is removed when DTMF is no longer likely. It recites H.323, H.245, Q.931 Setup/Connect/Release-Complete messaging and gatekeeper address resolution.
• § 102 assessment: The claims are squarely about tone transport and jitter/skew — no terminal proxy, no per-terminal call-state delegation. It cannot anticipate claims 1/14/15/16. It is § 103 art (and general background) for the protocol-translation / gateway limitations of claim 2 and the H.323/Q.931 framework of claims 4 and 9. Cited by the examiner largely, I would infer, for the terminal↔gateway↔network protocol context and the "call setup via Q.931 Setup / Connect / Release Complete" flow that mirrors '695's FIG. 2.

4. US 2002/0018464 A1 — Kikinis, "Integrating SIP control messaging into existing communication center routing infrastructure"

• Dates: priority 1998‑09‑24; published 2002‑02‑14.
• Description (from title/field; full text not retrieved): Integrating SIP control messaging into an existing call-center/telephony routing infrastructure.
• § 102 assessment: Relevant only to the "network server = SIP proxy" species in dependent claims 8 and 13, and to the general notion of an external infrastructure controlling calls. Not anticipatory of any independent claim; § 103 art for claims 8 and 13 (and 1/14 as routing-infrastructure context).

5. US 6,031,896 A — Gardell et al., "Real-time voicemail monitoring and call control over the internet" (verified) — the closest reference to '695's core idea

• Dates: filed 1998‑10‑23 (App. 09/177,415), issued 2000‑02‑29; GTE Laboratories Incorporated (Waltham, MA); inventors Gardell, Chopra, Zibman. https://patents.google.com/patent/[US6031896A](/patent/US6031896A) ; https://patentimages.storage.googleapis.com/39/61/97/8455658a36a9c1/US6031896.pdf
• Description (verified): An H.323 voice-mail system. Notably it discloses a **"Service Terminal 40 [that] 'lives in the network' and behaves like an H.323 terminal … acts as a surrogate for a live terminal. The Service Terminal 40 provides a place for actual services to be rendered to the caller on behalf of the called party."* It also discloses a gatekeeper (address table/directs calls), an internet telephone switch, a gateway with signaling conversion PSTN↔H.323, and a voice-mail intercept service terminal that connects an incoming call to the called party's internet telephone.
• § 102 assessment: This is the single reference that most nearly reads on claim 1's "providing logical call processing signaling on behalf of said at least one terminal." Its "Service Terminal … behaves like an H.323 terminal … surrogate for a live terminal … on behalf of the called party" is textually close to '695's "terminal proxy … makes a terminal look like a terminal of another type." However, the Gardell surrogate is the called party's terminating service node; it is not described as managing the terminal's own call-processing state/bearer connections on behalf of a computationally limited endpoint, which is the express point of '695. So:
  • Potentially anticipatory of claim 1 only if one reads "on behalf of said at least one terminal" broadly enough to cover a network surrogate providing services on behalf of the called party — a strained reading; more likely a § 103 combination (Gardell surrogate + a thin terminal's discovery of its server).
  • Directly relevant (§ 102(e)/§ 103) to claim 7 (network server = H.323 gatekeeper) and to the H.323 network context of the preamble.
  • Relevant to claims 14/15/16 for the "identify/register with a supporting network entity at initialization" concept via its gatekeeper address-table routing, but Gardell does not recite terminal-initiated proxy identification.

6. US 6,229,804 B1 — Mortsolf et al., "Gatekeeper election methods for internet telephony" (verified) — closest to claim 14(a)

• Dates: filed 1998‑11‑17 (App. 09/193,691), issued 2001‑05‑08; 3Com Corporation; inventors Harper, Mortsolf, Peirce, Stoner. https://patents.google.com/patent/[US6229804B1](/patent/US6229804B1)
• Description (verified): Gatekeepers in an H.323 zone elect a single "active gatekeeper" via broadcast "active gatekeeper claim" messages and priority values. Critically, it discloses that a Gateway/Terminal discovers the gatekeeper during an initialization phase ("The gateway's 40, 80 should discover the gatekeeper 22 during an initialization phase … If the gateway does not know the gatekeeper's IP Address, then it should use the DNS"), and that an elected gatekeeper provides an alternate gatekeeper list to the initiating Gateway/Terminal.
• § 102 assessment: This is the reference that most directly touches claim 14, step (a) ("identifying a terminal proxy on an IP network upon initialization of the terminal") and the corresponding means (claim 15) and program-code (claim 16) limitations — for a gatekeeper. But claims 14/15/16 also require step (b) (exchange call-processing messages so the proxy manages the terminal's call-processing logic), which Mortsolf does not teach (its gatekeeper does admission/bandwidth, not terminal-side call-state management). So not a full § 102 anticipation; strong § 103 art for the init-identification limitation and § 102(e)/§ 103 for claim 7 (server = H.323 gatekeeper).

7. US 6,161,008 A — "Personal mobility and communication termination for users operating in a plurality of heterogeneous networks"

• Dates: filed 1998‑11‑23, issued 2000‑12‑12; assignee listed as Nortel Networks Limited.
• Description (from title/field; full text not retrieved): Personal-mobility feature in which communications are terminated to a user across a plurality of heterogeneous networks (e.g., PSTN/wireless/IP) via a network-side mobility agent.
• § 102 assessment: Touches '695's "with respect to the remainder of a telephony network" and the heterogeneous-network context, and network-side termination of a subscriber's calls. It does not disclose a terminal proxy that performs the endpoint's own call-processing logic for a limited terminal. § 103 art for claim 1 and the "remainder of a telephony network" language; no independent-claim anticipation.

8. US 2001/0028654 A1 — Anjum, "Architecture for the rapid creation of telephony services in a next generation network"

• Dates: priority 1998‑12‑11; published 2001‑10‑11.
• Description (from title/field; full text not retrieved): A service-creation architecture (service nodes/call-model frameworks) for rapidly deploying telephony services in a next-generation network.
• § 102 assessment: Directed to network services/supplementary services — i.e., the '695 specification's "providing … supplementary services" theme and the network-server species of claims 4–13. Not anticipatory; § 103 art for claim 1 and the "supplementary services" aspects referenced in the spec.

9. US 6,275,574 B1 — "Dial plan mapper"

• Dates: filed 1998‑12‑22, issued 2001‑08‑14; assignee Cisco Technology, Inc.
• Description (from title/field; full text not retrieved): Maps/translates dial plans between telephony systems (i.e., converting call-setup/digit information between a PSTN-side and a packet-side telephony domain).
• § 102 assessment: Related to the signaling translation function '695 attributes to the terminal proxy. However, a dial-plan mapper operates on numbering/dial-plan data, not on a terminal's call-state machine. Not anticipatory; § 103 art for claim 1 and for the method claims 14/15/16 to the extent they recite exchanging call-processing messages through an intermediary.

5. Claim-mapping summary (which cited reference potentially anticipates which claim)

Net: the nine references collectively cover (i) network-side call control proxies/surrogates (US 6,031,896, US 2001/0026548), (ii) endpoint/gatekeeper discovery and election at initialization (US 6,229,804), (iii) tone/gateway protocol handling in VoIP (US 6,259,691), (iv) SIP/call-center routing (US 2002/0018464), (v) call modelling and service-creation architectures (US 2001/0028649, US 2001/0028654), (vi) personal mobility termination across heterogeneous networks (US 6,161,008), and (vii) dial-plan/signaling translation (US 6,275,574). None of them, alone, discloses the full '695 independent claim 1 or the two-step method of claim 14.

6. Caveats and open items

• Verified directly: US 6,031,896, US 6,259,691, US 6,229,804, US 2001/0026548 — grants/publications retrieved (URLs above).
• NOT independently verified this session (bib from the '695 front page; descriptions inferred from title/field): US 2001/0028649 (Pogossiants), US 2002/0018464 (Kikinis), US 6,161,008 (Nortel), US 2001/0028654 (Anjum), US 6,275,574 (Cisco). If you need the actual claim text of these, they should be pulled from USPTO Patent Public Search / PatentCenter and the descriptions confirmed — I will not assert their precise disclosures beyond the titles.
• No non-patent literature appears in the retrieved front-page citation set for '695; the H.323/SGCP/Q.931/UNISTIM-IP/LSSGR standards referenced in the specification are described by the patent, not cited as prior art.
• Forward citations ≠ prior art. The "Cited By (33/76)" and "Similar Documents" tables on the page are later documents citing '695; they are not § 102 references and I have excluded them from the analysis above.
• Continuation/priority nuance for § 102(e): for US 2001/0026548 the Google "priority date" of 1997‑10‑21 reflects a continuation parent; the § 102(e) date is the US filing date of the application as to the subject matter relied upon. If a rejection were ever constructed on these, the reference date should be re-derived from the specific family member actually relied on.

Bottom line: the examiner's nine citations are, taken individually, § 103/background art, not anticipatory art, for '695's independent claims. The two references that come closest on a single limitation are US 6,031,896 (network "surrogate … on behalf of the called party," reading on claim 1's "on behalf of" language) and US 6,229,804 (endpoint discovers/identifies its gatekeeper at initialization, reading on claim 14(a)/15/16's identification step). No single cited reference, as described in the record, discloses the full combination of a limited terminal plus a network terminal proxy that manages that terminal's call-processing logic against the remainder of the telephony network.

I'll research the cited prior-art references from the patent page before building the § 103 combinations.

Now the remaining cited references.

Obviousness Analysis — US 6,445,695 B1 under 35 U.S.C. § 103

0. Scope, date law, and what "prior art" means on this page

Important scoping rule for this page. The Google Patents page has two prior-art sections. Only the "Citations (9)" list is available as § 102/§ 103 prior art. The "Cited By (33)" / "Cited By (76)" entries must not be used: every one of them has a priority date later than 1998-12-31 (earliest is US 6,937,597, priority 1999-02-26, and the bulk are 1999–2006). They are useful only as evidence of later industry practice/claim-construction context, never as anticipatory or combinable references.

1. Person having ordinary skill in the art (PHOSITA) — December 1998

A PHOSITA here would hold a B.S. in EE or CS (or equivalent) plus roughly 2–3 years designing packet-telephony systems, and would be familiar with: ITU-T H.323 (v1 1996 / v2 1998) and its zone model (gatekeeper/terminal/gateway, plus Gatekeeper Discovery GRQ/GCF and RRQ registration); Q.931 / H.225.0; H.245; RTP; the emerging SIP drafts and the SIP proxy/registrar model; the SGCP Internet-Draft (Arango & Huitema, 1998) and the then-current "gateway decomposition" proposal (a call agent/media gateway controller driving relatively unintelligent media gateways); LSSGR and 2500-set/CLASS POTS interfaces; and DHCP/BOOTP for endpoint configuration. This skill level is not contested by the specification, which itself invokes H.323, Q.931, SGCP, SIP, DHCP and UNISTIM IP by name as known technologies.

2. The nine cited references, mapped to claim elements

The applicant's own admissions are prior art too

The '695 specification supplies several of the claim elements expressly as known art (usable under In re Fout and Riverwood v. RTC):

• H.323 zone architecture (gatekeeper = "network entity responsible for IP network address resolution and bandwidth allocation"; gateway; terminals as endpoints) is described as existing technology.
• "UNISTIM IP assumes a call control architecture in which the call control 'intelligence' lies outside of the telephone and is thus handled by external call control elements." — i.e., the delegation architecture per se is admitted.
• "To implement such a system it is necessary for the terminal to identify its supporting server within the IP network upon initialization. This is achieved utilizing standard operations that are well known in the art such as, for instance, DHCP or direct keying into the terminal." — an express admission covering the claim-14/15/16 "identifying" step.
• Table 1 admits an established taxonomy of network-based vs. terminal-based calling services.
• The spec's own embodiment uses "a stimulus subset of the Q.931 protocol" and SGCP — i.e., the dependent-claim protocols/network-server types are the applicant's own enumerated implementations.

3. Proposed § 103 combinations

Combination A — Claim 1 (and 4, 7, 8-type subject matter): Strathmeyer + Kikinis + Nortel '008

Element mapping to claim 1.

• "at least one terminal coupled to an IP network" → Strathmeyer's H.323 endpoints 202/204/406; Kikinis' IPNT endpoints; '008's terminals.
• "a terminal proxy coupled to said IP network communicable with said at least one terminal for providing logical call processing signaling on behalf of said at least one terminal" → Strathmeyer's call controller/gatekeeper "arranged to interface with a plurality of external call processing applications," which "sets up and controls call sessions between the various H.323 or equivalent endpoints" and implements call processing functionality "on behalf of" another entity; Kikinis' network SIP server/session management application; '008's server that selects and returns the terminal address and enforces profiles on the user's behalf.
• "manages the call processing logic for said at least one terminal with respect to the remainder of a telephony network" → Strathmeyer's gatekeeper "provides services analogous to the call processing function within a PBX," handles bandwidth/zone management/address translation/admission for a designated set of terminals, and exhibits the identical FIG. 2 signalling sequence the '695 patent relies on for its own FIG. 2 (setup → alerting → answer → release).

Motivation to combine (KSR): all three address the same problem — removing call-control intelligence from the endpoint and concentrating it in a network node so that endpoints can be simpler and services can be administered centrally. Strathmeyer explicitly asks what an H.323 gatekeeper can be made to do "on behalf of" endpoints and external applications; Kikinis supplies the express teaching that a network SIP server can deliver "ISDN and Intelligent Network telephony subscriber services" (i.e., supplementary services) on the network's initiative; '008 supplies the terminal-facing registration/query/selection mechanics and server-side profile logic. Combining a call controller that already mediates endpoint signalling with a second, expressly interchangeable session protocol (SIP proxy) and a terminal-facing registration/query layer is a combination of known elements in the same field, with predictable results (KSR; In re Keller). The '695 specification itself provides the motivation by admitting that the stimulus-call-control delegation architecture was known.

Assessment: Claim 1 is a broad, largely functional claim whose only structural requirement is a network node that talks to a terminal and runs that terminal's call processing with respect to the rest of the network. Strathmeyer alone comes very close (a real anticipation question, not a § 103 question); adding Kikinis and '008 closes any residual gap for § 103. Likely obvious.

Combination B — Claims 2–3 (terminal adapter; SGCP): 3Com '691 + Strathmeyer/Kikinis + admitted SGCP

Claim 2 adds only a terminal adapter that receives a non-IP terminal's call-control protocol and converts it to IP. 3Com '691 discloses precisely this at the network access server / gateway: a device coupling POTS and TDM interfaces to a packet network, with a Gateway/Terminal and gatekeeper in the path. The '695 specification itself admits the necessity of "network interfaces capable of converting between IP standards and protocols and existing standards and protocols" and admits the LSSGR interface for 2500 sets. Claim 3 merely names SGCP as the TA↔proxy protocol — a protocol published in 1998 explicitly designed for the decomposed call-agent/gateway model, so its selection is the substitution of one known signalling protocol for another with predictable results (In re Kuhle; In re Boesch). Highly likely obvious.

Combination C — Claims 4–8 (H.323 to network server; server = PSTN CO switch / PBX / H.323 GK / SIP proxy): Strathmeyer + Kikinis + Cisco '574

• H.323 between the proxy and the network server: Strathmeyer works wholly within H.323; the '695 spec admits its own embodiment does exactly this.
• H.323 gatekeeper as the network server: Strathmeyer's call controller is an H.323 gatekeeper; Cisco '574's gatekeeper 26 performs the same mediation between IP phones and PSTN/PBX gateways.
• SIP proxy: Kikinis (SIP server/proxy computing routing determinations); Cisco '574 lists SIP as a selectable session protocol alongside H.323.
• PSTN central office switch / PBX: Cisco '574's packet-to-PSTN gateway 18 and packet-to-PBX gateway 28; Strathmeyer's PBX analogy; '008's PSTN/cellular interworking.

Motivation: the recited items are four alternative destination-node types for the same interworking function, each individually well known. Selecting among known, art-recognized alternatives to achieve the same disclosed result is the paradigm of obviousness (KSR: "a court must ask whether the improvement is more than the predictable use of prior art elements according to their established functions"). These dependent claims add essentially no structural or functional content beyond claim 1. Highly likely obvious.

Combination D — Claims 9–13 (Q.931 stimulus subset instead of H.323): Strathmeyer + Kikinis + applicant's own admission

The '695 specification states its own embodiment "uses UNISTIM IP as the signaling protocol between terminal adapter 140 and terminal proxy 150 while a stimulus subset of the Q.931 protocol is for communication between terminal proxy 150 and network server 170." Q.931/H.225.0 is the standard ISDN/PBX call-control protocol and is incorporated by reference in Strathmeyer. Kikinis expressly contemplates mixing protocols (SIP used "to determine that the party can be reached via H.323, obtain the H.245 gateway and user address and then use H.225.0 to establish a call"). Swapping a full H.323 stack for a Q.931 stimulus subset is a design trade-off (lower endpoint/server overhead, native PBX/CO interworking) with a predictable result. Highly likely obvious.

Combination E — Claims 14, 15, 16 (method / means / CPP; "identifying a terminal proxy upon initialization"): 3Com '804 + Strathmeyer/Kikinis + Nortel '008 + admitted DHCP

• The "identifying a terminal proxy on an IP network upon initialization" step is: (i) admitted in the '695 specification to be conventional ("standard operations … well known in the art such as, for instance, DHCP or direct keying"); (ii) taught by 3Com '804 (gatekeeper election/discovery for IP telephony endpoints); (iii) taught by H.323 Gatekeeper Discovery (GRQ/GCF) and SIP registration to a registrar/proxy, both of which a PHOSITA in Dec. 1998 would know; and (iv) taught in substance by '008 (terminal sends a service query to the network server and receives routing/server information, with registration/de-registration and timer semantics).
• The "exchanging call processing messages" step is the FIG. 1/FIG. 2 content of Strathmeyer and Kikinis verbatim in kind.
• Claim 15 is the same subject matter in means-plus-function form, governed by the specification's own statement that the means clauses cover "the structures described herein … and equivalents" — i.e., the terminal-proxy software entity and the stimulus interface, both of which are disclosed by the references above. Claim 16 is the same subject matter as program code on a medium; the medium recitation adds nothing patentable (In re Beauregard), and the '695 specification itself lists diskette/hard disk/CD-ROM/tape/ROM/RAM as conventional media.

Motivation: a claim element the applicant concedes is "well known in the art" cannot by itself supply novelty or non-obviousness; the objective of a thin endpoint requires server discovery at boot, so the "identifying" step is an inherent and expected part of any such system. Highly likely obvious.

4. Anticipated applicant arguments and rebuttals

5. Bottom line

The strongest single-reference attack surface is Strathmeyer, which is why its § 102(e) date needs to be nailed down (see below). The strongest overall combination for the dependent claims is Strathmeyer + Kikinis + Cisco '574 + 3Com '691, with the applicant's own specification admissions supplying the "identifying the supporting server upon initialization" limitation.

6. Explicit caveats and things to verify before relying on this

1. Strathmeyer § 102(e) date. US 2001/0026548 A1 was filed as a CIP (Ser. No. 09/805,501, 2001-03-13) of Ser. No. 08/955,834 (1997-10-21), which issued as US 6,201,805 on 2001-03-13. For pre-AIA § 102(e), only matter carried over from the 1997 parent gets the 1997-10-21 date; CIP-introduced matter gets the 2001 filing date and would not qualify. A validity challenge must rely on US 6,201,805 (or on the parent's specification) and must verify that each relied-upon passage appears there. The examiner cited the '548 publication, which suggests the examiner treated it as art, but this should be independently confirmed.
2. Four references were not retrieved in full. US 6,229,804 B1, US 6,031,896 A, US 2001/0028654 A1 and US 2001/0028649 A1 are characterized above from their titles, dates, assignees and general subject matter only. My use of them is corroborative/background; the core combinations do not depend on them. Treat those mappings as moderate confidence and verify before relying on them.
3. Two references are only days before the critical date. Anjum (1998-12-11) and Cisco '574 (1998-12-22) are § 102(e) art, but because they were filed before the 2000-11-29 rule change they are not automatically excluded from a 37 CFR 1.131 swear-behind, and their own priority could be junior to the '695 inventor's actual date of invention. Use them as secondary/state-of-the-art evidence, not as the primary reference.
4. Non-cited art may be stronger. The most on-point art for this disclosure may never have been cited: the SGCP Internet-Draft (Arango & Huitema, 1998) and the associated gateway-decomposition/call-agent architecture; H.323 v2's Gatekeeper Discovery and registration procedures; early SIP drafts and RFC 2543; and MGCP/H.248 lineage. If a challenge were ever contemplated, these need public-availability dates verified against the 1998-12-31 critical date. (Note: an expired patent remains amenable to ex parte reexamination, but any IPR/PGR/CBM route is time-barred, and the record shows no IPR was ever filed.)
5. No judicial validity determination exists. As established in the earlier litigation section, the only case placing '695 at issue — Vonage Holdings Corp. v. Nortel Networks Inc., D. Del. 1:07-cv-00507-GMS — was a declaratory-judgment action terminated by the Dec. 2007/Jan. 2008 Nortel–Vonage cross-license and dismissed without prejudice. There is therefore no judicial finding either way on claims 1–16, and nothing in the record estops or supports an obviousness position.
6. "Cited By" is not prior art. Reiterating because it is easy to slip: all 33 (and 76) "Cited By" documents postdate the '695 priority date and cannot be combined against these claims.

Sources: Google Patents US6445695B1 (grant text, claims, Citations (9), Cited By lists, assignments); US 2001/0026548 A1 (Strathmeyer); US 6,201,805 family/CIP cross-references; US 6,161,008 A (Lee et al., Nortel); US 6,259,691 B1 (3Com); US 2002/0018464 A1 (Kikinis); US 6,275,574 B1 (Oran, Cisco); US 6,636,594 B1 (continuation, same family as '574).