US 6286050

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

Let me check for any litigation or post-grant proceedings specifically involving this patent.

US Patent 6,286,050 — Verification Summary

Sourcing note: I retrieved the full authoritative patent text from Google Patents (patents.google.com/patent/US6286050). I searched for CAFC 2026 docket activity tied to this specific number and found none. There is no indication this patent is in any 2026 Federal Circuit appeal. The only litigation hit I could confirm is an older district-court case (below). Everything else is cited to the patent record.

Bibliographic Data

Later assignment events: a security interest to Credit Suisse AG (recorded 2013-03-07, re Alcatel-Lucent USA Inc.) and a release by secured party back to Alcatel-Lucent USA Inc. (recorded 2014-10-09).

Family / Related Publications

• EP 0954917 B1; EP 1753167 B1; DE 69836537 T2; ES 2340412 T3; TW 530220 B; WO 1998033302 A1.

Litigation Note

The record shows a US case filed in Delaware District Court, 1:14-cv-00628 (source: Google Patents / Unified Patents litigation data), and a Darts-IP family litigation entry. This is a 2014 filing, not 2026 CAFC activity. The patent's expiration in 2017 further makes fresh 2026 appellate activity unlikely. I could not verify a CAFC 2026 docket for this patent and state that as an explicit negative finding, not as a confirmed absence in every database.

Abstract (as issued)

A system (20) for monitoring and management of telecommunications equipment (10, 30) in a telecommunications network via the internet (34). Includes a plurality of user devices (36, 46, 50) each executing a web browser (64) for communications with the internet (34). An intranet (32) is in communications with the internet (34). A web server (84) identifiable by an internet address resides on each telecommunications equipment (10, 30), the equipment being coupled to the intranet (32). A plurality of web pages (90) for displaying monitoring and management information associated with the equipment are accessible by the web server (84) via the internet (34) and intranet (32).

Plain-Language Overview of the Independent Claims

Claim 1 — System (equipment-resident web server).
A system where the telecommunications equipment itself hosts a web server that gives the equipment its own internet address. Web pages that display monitor information about the equipment (and accept user input) are served by that web server, each page having its own internet address. A web browser on a user's machine connects directly to the equipment using its internet address, receives the pages over the internet, and sends user input back to the web server — and the web server can then modify or update the equipment's operations based on that input.

Claim 11 — System in a network (intranet + internet).
A broader network-level system: multiple user devices each running a web browser; an intranet connected to the internet; a web server residing on each piece of telecommunications equipment in the network, each reachable by its own internet address; and web pages (each individually addressable) displaying monitor information. Each user device can directly connect to a particular piece of equipment by its internet address to reach its pages, and the web server can modify that equipment's operations in response to user input.

Claim 20 — Method.
A method comprising: connecting user devices running web browsers to the internet; connecting the telecommunications equipment to the internet via an intranet; accessing a piece of equipment by specifying its internet address through a web server resident on the equipment; downloading web pages (displaying monitor/management information) from that web server to a user device over the internet/intranet, with direct user-device-to-equipment connection by internet address; receiving user input at the web server; and modifying the associated equipment's operations in response to that input.

Common thread across all three independents: (1) a web server embedded in the telecommunications equipment and directly internet-addressable; (2) direct browser-to-equipment connection (no intermediary gateway), with the pages carrying monitoring/management content; and (3) closed-loop control — user input at the browser flows to the web server, which changes equipment operations.

Dependent claims add: dedicated AMA/billing, information-and-problem-report, and trace-log servers or page sets (claims 2–4, 8–10, 12–14, 17–19, 21–23, 25–27); downloadable Java applets executed by the browser (5, 15, 24); the distributed switching system / service unit + delivery unit architecture (6, 16); and the intranet coupling (7).

Uncertainties / Caveats

• No 2026 CAFC docket activity found for this patent. I cannot affirmatively certify this across all dockets; I report it as a negative search result.
• The internal patent text refers to an incorporated application, U.S. Ser. No. 08/757,465 ("Database-Driven Automatic Message Accounting System and Method"), and to U.S. Pat. No. 5,495,484 ("Distributed Telecommunications Switching System," Self et al., Feb. 27, 1996) — both cited as in the specification.
• Searches surfaced unrelated documents sharing the digits "6286050" (e.g., a Japanese patent JP 6286050 B2, and a Lithuanian registry/grant ID). These are not US 6,286,050 and were excluded as non-relevant per your instruction to interpret identifiers literally and avoid similar numbers.

I'll search litigation sources for US patent 6286050.

Let me drill into the specific Delaware case referenced on the patent page and check Unified Patents' litigation database.

Known litigation for US Patent 6,286,050

I searched litigation-oriented sources (Unified Patents litigation portal, Google Patents' litigation links, and general case-law/docket sources). One US district court case involving this patent is documented. I could not confirm its final disposition from the sources retrieved, and I flag that explicitly rather than guessing.

Case 1 — Alcatel-Lucent v. Cyberoam / Sophos

Sources:

• https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1%3A14-cv-00628
• Google Patents' "Family has litigation" link for US6286050B1 points to exactly this case: https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1%3A14-cv-00628
• Google Patents also lists a "First worldwide family litigation filed" via Darts-IP for family ID 56289796: https://patents.darts-ip.com/?family=56289796

Other points relevant to your request

• No PTAB proceedings found. My searches surfaced no IPR, PGR, or CBM proceeding naming U.S. Patent 6,286,050. I cannot rule out that one exists; PTAB (ptacts.uspto.gov) would be the authoritative check.
• No CAFC appeal identified for this patent or for 1:14-cv-00628 in the results retrieved.
• Family-level litigation: Google Patents indicates the US6286050 family "has litigation," with the Delaware case above plus a Darts-IP family-level first-litigation entry — i.e., the family (including EP0954917B1 / EP1753167B1) may have additional foreign proceedings I did not verify.
• Patent term: Google Patents lists an anticipated expiration of 2017-09-30 and legal status "Expired – Lifetime," so any enforcement window for this patent has closed.

Important caution on the identifier you gave

Per your instruction to interpret identifiers literally and not auto-correct them, I note that a search on "6286050" returns several unrelated documents that happen to share the number and are not US Patent 6,286,050:

• JP Patent No. 6286050 B2 — avian influenza virus miRNA, applicant Jiangsu Micromedmark Biotech Co., Ltd. (https://patentimages.storage.googleapis.com/50/55/f5/9ca1bb330e00f8/JP6286050B2.pdf)
• A CourtListener docket ID 6286050 (Rincon-Marin v. Credit Control LLC)
• Various corporate/registry and geological entries

I have excluded all of these. Similarly, case number "5:14-cv-00628" (W.D. Tex.) and "3:13-cv-00628" (D. Nev.) are different cases and are not litigation of US 6,286,050.

Bottom line

One known US litigation involves US Patent 6,286,050: Alcatel-Lucent v. Cyberoam Inc. and Sophos Inc., No. 1:14-cv-00628 (D. Del.), filed 2014, in which the '050 patent was one of five asserted. The outcome and current status are unverified from the sources I could reach; for a definitive disposition you should pull the PACER docket for 1:14-cv-00628 (D. Del.) or the Delaware docket directly. If you'd like, I can run additional targeted searches on the docket number, on Sophos/Cyberoam as defendants, or on the co-asserted patents to try to pin down a disposition.

I'll start by verifying the structured data with targeted searches for any PTAB activity on this patent.

Let me run a few more targeted searches to confirm the absence of PTAB activity and identify the litigation context.

Proceedings overview

Total AIA trial proceedings on file: 0. The USPTO Open Data Portal returns no IPR, PGR, or CBM proceeding for US 6,286,050, and my independent searches of PTAB/P-TACTS and public commentary surfaced no petition, no institution decision, and no Final Written Decision against this patent. There is nothing to break down by active / invalidated / sustained / settled / denied — the patent stands with all 27 claims intact and unadjudicated. The bottom-line defensive posture is therefore the opposite of a hardened-patent story: this is an untested, expired, 1997-priority patent that no challenger has ever attacked at the Board. For a defendant, that means (a) there is no PTAB record to leverage and no § 315(e)(2) estoppel to exploit, but also (b) the entire validity surface is still open for you to attack in district court or in a first-instance IPR of your own.

No proceedings to report

There is no {PROCEEDING_NUMBER} — {Petitioner} v. {Patent Owner} entry to populate. I did not find an IPR, PGR, or CBM number, and I will not invent one. What follows is the affirmative record of absence plus the surrounding signals.

What I checked and what I found

• The structured "PTAB proceedings on file" block (USPTO ODP) is empty for this patent.
• Targeted searches for an IPR/CBM/PGR tied to 6,286,050 / 6286050 returned either the patent's own bibliographic pages or unrelated patents (e.g., the frequently-surfaced 7,551,625, 8,155,012, and various Sisvel/Nokia matters). None named 6,286,050 as the challenged patent.
• No Final Written Decision, institution decision, or POPR is publicly associated with this patent number in any source I could retrieve.

Signals that explain the absence

• The patent expired on 2017-09-30. The front page carries the notice that it issued on a continued prosecution application and is "subject to the twenty year patent term provisions of 35 U.S.C. 154(a)(2)" — i.e., 20 years from the 1997-09-30 filing date. Google Patents' legal-status field confirms "Anticipated expiration 2017-09-30" and "Expired - Lifetime."
• PGR is time-barred by statute. Post-grant review must be petitioned within 9 months of issuance; this patent issued 2001-09-04, so PGR has been unavailable for over two decades (35 U.S.C. § 321(c)).
• CBM is sunset and no longer available. The patent is CBM-eligible in principle (pre-March-15-2013 priority), but the transitional CBM program expired 2020-09-16. It cannot now be invoked.
• IPR remains theoretically available but economically unattractive. An IPR can be filed even against an expired patent, but the Board would apply Phillips claim construction (no Phillips/SAS timing benefit here) and there is no injunction to enjoin — so the only rational petitioner would be a defendant already facing a damages demand.

Litigation context (from the structured data)

The Google Patents record flags one US case: Delaware District Court, No. 1:14-cv-00628, plus a Darts-IP "first worldwide family litigation" flag. I was unable to confirm the party names, the asserted claims, or the outcome of that 2014 Delaware action from the sources I retrieved — I am flagging it rather than guessing. If you are evaluating a demand letter, this docket is the first thing to pull, because it is the only historical assertion of the patent I can identify and it may contain validity contentions and prior art that never matured into a PTAB petition.

Strategic summary

Claim status: everything is UNTESTED. No claim of 6,286,050 — independent claims 1, 11, and 20, or any of dependent claims 2–10, 12–19, and 21–27 — has been canceled, confirmed, or even construed by the PTAB. Unlike the hardened-patent scenario, there is no narrowed claim set. The practical consequence is double-edged for a defendant: you cannot point to a canceled claim and say "the demand letter cites a dead claim," but you also face zero precedential claim-construction guidance. Independent claim 1 is a fairly broad "web server residing on the telecommunications equipment + web pages + web browser over the internet, wherein the web server modifies operations in response to user input" system claim — exactly the kind of claim that drew heavy § 103 and § 101 scrutiny in the late-1990s network-management art, but no tribunal has ruled on it here.

Estoppel landscape: none. Because no AIA trial was ever instituted, there is no § 315(e)(2) estoppel binding anyone, and no petitioner-privy bar to worry about. Every prior-art ground — including the references cited on the face of the patent (US 5,241,588 to Babson; US 5,488,569 to Kaplan; US 5,495,484 to Self; US 5,721,908 to Lagarde; EP 0 592 080; EP 0 592 091; EP 0 602 824; EP 0 737 922; WO 95/11560) and the non-patent literature the examiner considered (Larsen, Data Communications "Weaving the Management Web" and "The Next Web Wave: Network Management"; Hatonen et al., "TASA"; Hamilton, "Java and the Shift to Net-Centric Computing"; Pennino on AMA) — is un-adjudicated and fully available in a district-court invalidity case. Note, however, that if you are the first to file an IPR, you personally take on § 315(e)(2) estoppel and the § 315(b) one-year clock from service of the complaint.

Pattern signals. There is no serial petitioner (no entity has filed even one petition), no patent-owner appeal activity at the Federal Circuit, and no evidence of a defensive aggregator such as Unified Patents in the chain — although Unified's public patent portal does index US-6286050-B1, that indexing is not a proceeding. The absence of any IPR is itself the signal: a patent with a 1997 priority date, a 2014 assertion, and only 27 claims that apparently attracted no challenger in the 2012–2020 heyday of IPR filing suggests either that the 2014 matter resolved quietly/quickly or that the patent was never pressed hard enough to justify the cost of a petition.

Recommended next steps

• No PTAB activity exists — say so plainly and do not let opposing counsel imply otherwise. There is no FWD to link to and no PTAB disposition to quote. Any assertion that claims of 6,286,050 have been "invalidated" or "canceled" at the Board would be inaccurate.
• Pull the Delaware docket, No. 1:14-cv-00628. It is the single most valuable artifact. Identify the parties, the claims asserted, the invalidity contentions served, and whether any prior-art combinations were developed. Those contentions are a ready-made starting point, and none are estopped because no IPR followed.
• Lead with the expiration date. The patent lapsed 2017-09-30. Any damages theory is capped by the 35 U.S.C. § 286 six-year lookback and the expiration date; there is no prospective injunction. Price the exposure accordingly before litigating validity.
• If you choose to file an IPR, do it before your § 315(b) clock runs (one year from service of the infringement complaint) and build the petition as a first petition — there is no prior petition to be a "follow-on" of, so no General Plastic / § 314(a) follow-on discretionary-denial risk of the kind seen in cases like Alcatel-Lucent USA Inc. v. Oyster Optics, LLC, IPR2018-00257.
• Flag for verification: confirm current ownership/standing (the chain runs DSC Telecom L.P. → Alcatel USA Sourcing L.P. → Alcatel-Lucent USA Inc., with a 2013 Credit Suisse security interest released in 2014). Whether the current owner is an operating Alcatel-Lucent successor or a monetization entity affects your litigation posture and settlement leverage.

Caveat on sourcing: the proceeding list above rests on the structured ODP block (empty) plus negative results from my searches. Negative search results are not the same as a certified "no proceedings" report. Before filing anything, confirm via PTAB E2E / the Patent Trial and Appeal Board's public docket and PAIR for US 6,286,050, since P-TACTS indexing of older matters can be incomplete.

I'll verify the assignment record against live sources before writing.

US 6,286,050 B1 — Assignment & Ownership Reconstruction

Patent: System and method for monitoring and management of telecommunications equipment using enhanced internet access
App. No.: 08/940,827 · filed 1997-09-30 · issued 2001-09-04 · provisional 60/034,874 (1997-01-27)
Status: Expired – Lifetime (anticipated expiration 2017-09-30)
Sources used: Google Patents legal-events/assignment table for US6286050B1 (which mirrors the USPTO Assignment Center reel/frame data), the patent's own assignment recitals, and open litigation/docket searches.

Data-integrity note up front: this record is internally incomplete in one important way (see "Original assignee"), and the two fields you flagged as highest-value — correspondent of record and the direction of the 2014 Delaware litigation — were not exposed in any source I could retrieve in this session. I flag both rather than guess.

Inventors

The 1997-09-30 assignment record (Reel 008836/0489) recites: "ASSIGNMENT OF ASSIGNORS INTEREST; ASSIGNORS: PULLEN, STEVE M.; MILLER, DONALD W., JR.; ATKINSON, CARLA M.; AND OTHERS." The "and others" is the recorder's truncation; the assignor set is the seven named inventors listed above.

Unusual patterns: none in the assignment record. All seven signed within a four-day window (1997-09-26 to 1997-09-29) immediately before the 1997-09-30 filing — a standard employment/pre-filing assignment, not the "all inventors exit within 12 months" pattern that often precedes a fire-sale. I have no data on individual inventor departure dates, and I do not infer them. Note the priority gap: the provisional was filed 1997-01-27 and the utility filing followed ~8 months later, which is ordinary, not indicative.

Original assignee

Entity named on the issued patent: Alcatel USA Sourcing, L.P. (Google Patents normalizes this as "Alcatel USA Sourcing Inc"); it is the same legal person as the original assignor DSC Telecom L.P., renamed by the change-of-name record at Reel 009596/0527, effective 1998-09-09. Google's "current assignee" field also shows Alcatel USA Sourcing Inc — see the discrepancy note below.

• Primary line of business: digital switching and transmission equipment for the public switched telephone network. DSC Telecom L.P. was the operating partnership of DSC Communications Corporation, which Alcatel acquired in 1998 — the recorded name-change effective date of 1998-09-09 lines up exactly with the closing of that acquisition and is the clearest corroboration in the record that the 1998 event is a corporate reorg, not a sale.
• Did they ship a product embodying the claims? Yes, on the face of the specification. FIG. 4 of this patent is the entry web page labeled "DSC Megahub™ Sites," and the monitored equipment is the distributed switching system of incorporated-by-reference U.S. 5,495,484 (Self et al., DSC Communications). The claimed subject matter — a web server embedded in the switch serving HTML pages and Java applets to a Java-enabled browser for craft monitoring/management — is a description of the assignee's deployed element-management feature, not a paper design.
• Current status: the DSC → Alcatel → Alcatel-Lucent (2006) → Nokia (2016) chain means Alcatel-Lucent USA Inc. is now a Nokia entity. The patent itself expired 2017-09-30. I found no bankruptcy filing by any assignee in this chain; Alcatel-Lucent was acquired, not liquidated.

⚠ Discrepancy in the record (must be verified): the 2013 security-interest record names the debtor/assignor as ALCATEL-LUCENT USA INC., yet there is no recorded assignment from Alcatel USA Sourcing, L.P. to Alcatel-Lucent USA Inc. anywhere in the legal-events table. Either (a) the Sourcing → Alcatel-Lucent USA transfer was recorded in a bulk reel Google's table does not link to this patent, or (b) Google's table is incomplete for this patent. This gap means the "no NPE ever touched this patent" conclusion below cannot be stated as absolute — see Verdict.

Assignment timeline

Four recorded post-filing events exist. Reel/frame numbers are as recorded.

• 1997-09-26 to 1997-09-29 (executed) / recorded 1997-09-30 — Reel 008836/0489

  • Conveyance: Assignment (Assignment of Assignors' Interest)
  • Assignor: Steve M. Pullen; Donald W. Miller, Jr.; Carla M. Atkinson; Eddie E. Bishop, Jr.; Joe K. Horvath; Alfred J. Blanchard; Ronald H. Gates
  • Assignee: DSC Telecom L.P. (Texas)
  • Correspondent: Not exposed in the retrieved record. The Assignment Center reel image will show it; it was not available from any source I could reach.
  • Context: Routine pre-filing employment assignment by all seven inventors to the operating company — the ordinary case, not an acquisition or fire-sale.

• 1998-09-09 (effective) / recorded 1998-11-27 — Reel 009596/0527

  • Conveyance: Change of Name (explicitly so recited: "CHANGE OF NAME; ASSIGNOR: DSC TELECOM L.P.")
  • Assignor: DSC Telecom L.P.
  • Assignee: Alcatel USA Sourcing, L.P. (Texas)
  • Correspondent: Not exposed in the retrieved record.
  • Context: Internal reorg / change of name only — no change in beneficial ownership; follows Alcatel's acquisition of DSC Communications.

• 2013-01-30 (effective) / recorded 2013-03-07 — Reel 030510/0627

  • Conveyance: Security Agreement / Security Interest (grant of collateral lien, not a title transfer)
  • Assignor: Alcatel-Lucent USA Inc.
  • Assignee: Credit Suisse AG (New York) — as secured party / collateral agent, reels of this type covering large Alcatel-Lucent portfolios
  • Correspondent: Not exposed in the retrieved record.
  • Context: Securitization — patent-collateral financing. Credit Suisse appears here as a lender, not a patent owner or asserter. Note this record is the evidence that title sat with Alcatel-Lucent USA Inc. by Jan 2013, despite the missing assignment noted above.

• 2014-08-19 (effective) / recorded 2014-10-09 — Reel 033949/0531

  • Conveyance: Release by Secured Party ("RELEASE BY SECURED PARTY; ASSIGNOR: CREDIT SUISSE AG")
  • Assignor: Credit Suisse AG
  • Assignee: Alcatel-Lucent USA Inc. (New Jersey)
  • Correspondent: Not exposed in the retrieved record.
  • Context: Lien discharge — encumbrance lifted, clean title returned to the operating company. This is the last recorded event in the chain.

Non-assignment legal events (for completeness, not ownership changes): fee-payment/entity-status entry 2000-11-01; patent grant 2001-08-16; maintenance fees paid 2005-03-01, 2009-02-26, 2013-02-22.

Litigation flag: Google Patents reports "Family has litigation — US case filed in Delaware District Court," case 1:14-cv-00628 (Unified Patents litigation link: https://portal.unifiedpatents.com/litigation/Delaware%20District%20Court/case/1%3A14-cv-00628), plus a Darts-IP "first worldwide family litigation" entry. I could not verify the parties or the plaintiff/defendant direction of that case — my docket searches returned different cases bearing the same docket suffix (e.g., 3:13-cv-00628, 1:23-cv-00628, 6:23-cv-00628). Do not treat the direction of that suit as established.

Timeline diagram

timeline
    title Ownership of US 6286050
    1997 : Filed 30 Sept
         : All 7 inventors assign to DSC Telecom L.P.
    1998 : Name change to Alcatel USA Sourcing L.P.
    2013 : Credit Suisse security interest
    2014 : Lien released to Alcatel-Lucent USA Inc.
         : Delaware case 14-cv-00628 flagged
    2017 : Patent expires

NPE / troll-pattern signals

Verdict

Operating-company assertion.

The ownership chain never leaves the DSC → Alcatel → Alcatel-Lucent (Nokia) operating-company lineage: title was assigned by all seven inventors to DSC Telecom L.P. at Reel 008836/0489 (recorded 1997-09-30), renamed to Alcatel USA Sourcing, L.P. at Reel 009596/0527 (effective 1998-09-09), and the only later events are a Credit Suisse collateral lien (Reel 030510/0627, effective 2013-01-30) and its discharge back to Alcatel-Lucent USA Inc. (Reel 033949/0531, effective 2014-08-19). Those are lender-side securitization events, not NPE transfers, and the assignee family demonstrably shipped products embodying the claims — the specification's own entry page is labeled "DSC Megahub™ Sites" (FIG. 4). One caveat I will not paper over: the "suing competitors" prong is not established here, because the 2014 Delaware matter (1:14-cv-00628) could not be verified as to direction, and because there is a real gap in the record (no recorded assignment from Alcatel USA Sourcing, L.P. to Alcatel-Lucent USA Inc.). Treat this as a strong NPE-negative finding on a reconstructed chain with one unverified edge, not as a confirmed litigation finding.

Verification steps (in order):

1. USPTO Patent Assignment Search — search App. No. 08/940,827 or Patent 6,286,050: https://assignmentcenter.uspto.gov/ (indexed front end: https://assignment.uspto.gov/patent/index.html). Open the reel images for 008836/0489, 009596/0527, 030510/0627, 033949/0531 and capture the correspondent of record on each — that is the missing field.
2. In the same tool, run the assignor name "ALCATEL USA SOURCING" and "DSC TELECOM" to locate the missing Sourcing → Alcatel-Lucent USA assignment (if it exists).
3. Cross-check Google Patents legal events (already used): https://patents.google.com/patent/US6286050/en.
4. Confirm D. Del. 1:14-cv-00628 parties in PACER/Unified Patents portal to settle the assertion direction before relying on signal 5 or the verdict's litigation prong.

I'll research US patent 6286050 and its cited prior art references.

Let me gather details on the remaining cited references.

Prior-Art Analysis — US 6,286,050 B1

Patented subject matter (confirmed): US 6,286,050 B1, "System and method for monitoring and management of telecommunications equipment using enhanced internet access." Inventors: Pullen, Miller, Atkinson, Bishop, Horvath, Blanchard, Gates. Original assignee DSC Telecom L.P., later Alcatel USA Sourcing, L.P. Provisional Ser. No. 60,034,874 filed Jan. 27, 1997; application 08/940,827 filed Sep. 30, 1997; granted Sep. 4, 2001. Status expired (Sep. 30, 2017). (Source: https://patents.google.com/patent/US6286050/en)

Claim architecture (27 claims; independent claims 1, 11, 20):

• Claim 1 — web server residing on the telecommunications equipment; equipment identifiable by internet address; web pages displaying monitor information and receiving user input; browser "directly connect[s]" to the equipment; web server modifies/updates equipment operations in response to user input.
• Claim 11 — adds user devices + intranet coupled to the internet, web server on each equipment; same modify-in-response-to-input limitation.
• Claim 20 — method counterpart (connect users → connect equipment via intranet → access by internet address through on-equipment web server → download web pages → receive input → modify operations).
• Dependent claims concentrate on: AMA/billing (2, 8, 12, 17, 21, 25), information & problem reports/status (3, 9, 13, 18, 22, 26), trace log (4, 10, 14, 19, 23, 27), Java applets (5, 15, 24), distributed switch = service unit + delivery unit (6, 16), intranet coupler (7).

Because the pre-AIA statute governs (application filed 1997), the operative sections are pre-AIA § 102(a), (b), and (e).

A. The 17 Patent Citations

Tier 1 — Most relevant prior art

1. US 5,742,762 A — Scholl & Witowsky (Telogy Networks, Inc.), "Network management gateway"

• Priority/filing: May 19, 1995; granted Apr. 21, 1998.
• Description: A gateway that receives Web-client requests (via CGI) from a Web server, parses them into network-management requests (NMRs), obtains management data from managed networks/agents, and converts the results into HTML documents returned to the Web browser in real time. Explicitly covers configuration, fault, performance, accounting, security management and customer support. Claim 1(i)–(j) recites the real-time HTML conversion and transmission.
• Potentially relevant to: claims 1, 11, 20 (browser + web server + web-page management interface; the "accounting management" category touches claims 2/12/17/21). Also relevant to claims 3/13 (fault management) and 4/14 (performance/trace).
• Caveat: Its gateway is a distinct appliance/middleware, not a web server residing on the managed equipment; and it does not expressly recite modifying the operations of the far-end equipment from the browser. Strong under § 103 when combined with Larsen and Bruno below; weaker as pure § 102 anticipation of claims 1/11/20.
• Sources: https://patents.google.com/patent/[US5742762A](/patent/US5742762A)/en ; http://www.everypatent.com/comp/pat5742762.html

2. US 5,721,908 A — Lagarde et al. (IBM), "Computer network for WWW server data access over internet"

• Priority/filing: Jun. 7, 1995; granted Feb. 24, 1998.
• Description: A web server with a "control program agent" organizes sub-agents to gather data across an intranet protected by a firewall and the Internet, and returns reports via a Web home page; claims expressly recite a browser associated with a homepage by URL, coupling to an intranet, and reaching across the intranet.
• Potentially relevant to: claims 1, 7, 11 (browser→URL→web server; intranet/firewall coupling; web-page presentation). Relevant to claim 9/13 (status reporting).
• Caveat: Not telecommunications-switch-specific; no on-equipment web server.
• Source: https://patents.google.com/patent/[US5721908A](/patent/US5721908A)

3. US 5,802,146 A — Dulman (Bell Atlantic Network Services), "Maintenance operations console for an advanced intelligent network"

• Filing: Nov. 22, 1995; granted Sep. 1, 1998.
• Description: Remotely monitors/controls AIN elements over a data network using standardized network management messages (SNMP/TCP-IP); a Maintenance Operations Console shows status on a GUI and a corrective-action module sends SNMP objects to modify/restore node operations (abort/restart modules, reload software, fail-over).
• Potentially relevant to: claims 1, 9, 11, 18, 20 — specifically the "receive user input → modify operations of the telecommunications equipment" limitation. Uses SNMP rather than HTTP/HTML.
• Sources: https://patents.google.com/patent/US5802146 ; https://patentimages.storage.googleapis.com/f3/a4/a9/6be3dbca300de9/US5802146.pdf

4. US 5,958,016 A — Chang & Rostock (Bell Atlantic), "Internet-web link for access to intelligent network service control"

• Priority/filing: Jul. 13, 1997; granted Sep. 28, 1999.
• Description: A web-page interface over the public Internet by which validated users review service data and input control data to network management systems, which in turn "modifie[s] operations of the traffic network" (provisioning, billing/usage systems, SCP records, central-office profiles).
• Potentially relevant to: claims 1, 11, 20 — notably the "modify operations ... in response to the user input" element, which is the point of novelty over the earlier web-management art.
• Timing caveat: filed Jul. 13, 1997 — after the Jan. 27, 1997 provisional date but before the Sep. 30, 1997 filing. Usable only as pre-AIA § 102(e) art (with the date problems that entails), not § 102(a)/(b). Do not treat as a § 102(b) bar.
• Source: https://patents.google.com/patent/[US5958016A](/patent/US5958016A)

5. US 5,915,008 A — Bell Atlantic, "System and method for changing advanced intelligent network services from customer premises equipment"

• Filing: Oct. 4, 1995; granted Jun. 22, 1999.
• Description: Allows subscribers to change/modify AIN service features from CPE over a data link — i.e., remotely altering switch/SCP service data.
• Potentially relevant to: claims 1, 11, 20 (remote modification of telecommunications service/equipment operations). Not browser/HTML-based in the web-server sense.
• Source: listed among citations at https://patents.google.com/patent/EP0954148A1

6. US 5,826,029 A — IBM, "Secured gateway interface"

• Filing: Oct. 31, 1995; granted Oct. 20, 1998.
• Description: Secure gateway/firewall-mediated interface for controlled access to protected intranet resources from outside clients.
• Potentially relevant to: claims 7, 11 (intranet/firewall coupling) and the security discussion in the specification ("security measures such as fire walls ... may be used"). Probably background, not anticipating.
• Source: cited in US6286050 citation table (Google Patents).

Tier 2 — Structural / architectural support

7. US 5,495,484 A — Self et al. (DSC Communications Corp.), "Distributed telecommunications switching system"

• Filing: Oct. 12, 1993; granted Feb. 27, 1996.
• Description: The distributed switching system with a service unit and at least one delivery unit — expressly incorporated by reference into the 6,286,050 specification (FIG. 1 discussion).
• Potentially relevant to: claims 6 and 16 ("distributed switching system having a service unit coupled to at least one delivery unit"). This is the only cited reference that supplies that structural limitation; it does not disclose the web-server/browser aspects.
• Source: https://patents.google.com/patent/[US5495484A](/patent/US5495484A)

8. EP 0 737 922 A1 — Sun Microsystems, "Method and apparatus for managing computer processes"

• Filing: Mar. 22, 1995; published Oct. 16, 1996.
• Description: Process/daemon management in a computer system.
• Potentially relevant to: claim 1/11 concept of the "services element (SE) 80 which is a process manager that controls and manages all the servers." Background; not anticipating.

9. US 5,241,588 A — Bell Communications Research, "Systems and processes providing programmable or customized customer telephone information services"

• Filed Dec. 18, 1990; granted Aug. 31, 1993.
• Description: Programmable/customizable telephony service creation and modification.
• Potentially relevant to: the general "modify operations of telecommunications equipment" concept; § 102(b) art but too remote to anticipate the Internet-access claims.

10. US 5,488,569 A — AT&T, "Application-oriented telecommunication system interface"

• Filed Dec. 20, 1993; granted Jan. 30, 1996.
• Description: Application-oriented interface for telecom systems (API-style access to switch functions).
• Potentially relevant to: claims 1/20 general aim of programmatic monitoring/control interfaces. Background.

11. EP 0 602 824 A2 — AT&T, "Automatic network element identity information registration apparatus and method"

• Filed Dec. 14, 1992; published Jun. 22, 1994.
• Description: Automatic registration of network-element identity information.
• Potentially relevant to: claims 7, 11 node-identification aspects (the spec's "node identifier (ID)" discussion around FIG. 7) and equipment addressing. Background.

12. EP 0 592 080 A2 — IBM, "Method and apparatus for interprocess communication in a multicomputer system" (filed Sep. 24, 1992; pub. Apr. 13, 1994)
13. EP 0 592 091 A2 — IBM, "Method and system for object management" (filed Oct. 6, 1992; pub. Apr. 13, 1994)
14. WO 95/11560 A1 — Martino, "Application programming interface system and technique" (filed Oct. 21, 1993; pub. Apr. 27, 1995)

• Description: distributed interprocess communication, object management, and API design.
• Potentially relevant to: the client/server and applet/server messaging architecture underlying claims 1, 5, 15, 20. All are § 102(b) art but are general computer-science background and do not disclose browser-based telecom monitoring.

15. US 5,826,030 A — Excel Switching Corp., "Telecommunication switch having a universal API..."

• Filed Nov. 30, 1995; granted Oct. 20, 1998.
• Description: Universal API on a telecom switch with generic call-processing messages.
• Potentially relevant to: claims 1/20 (programmatic access to a switch), but not web/Internet access.

16. US 5,913,061 A — Crossroads Software, "Modular application collaboration"

• Filed Jan. 8, 1997; granted Jun. 15, 1999.
• Description: Modular application/component collaboration architecture.
• Potentially relevant to: claims 1, 5, 11, 20 (modular downloadable application components). Pre-AIA § 102(e) only (filed before the Jan. 27, 1997 provisional date? Jan. 8, 1997 is before Jan. 27, 1997 — so it could qualify as § 102(e) art).

17. US 5,794,018 A — Intel Corp., "System and method for synchronizing data streams"

• Filed Nov. 24, 1993; granted Aug. 11, 1998.
• Description: Multiprocessor data-stream synchronization.
• Potentially relevant to: none of the claim limitations meaningfully; general computing background only.

B. The 7 Non-Patent Citations

NPL-1 — A.K. Larsen, "The Next Web Wave: Network Management," Data Communications, vol. 25, no. 1, Jan. 1, 1996, pp. 31–32, 34.

• Description (as characterized in the EP counterpart's discussion): places web software directly into network equipment (hubs/routers) so that managers use web-browser software to monitor and control the device; each device becomes a web server with a management home page, letting managers view status and configure ports.
• Potentially relevant to: claims 1, 11, 20 — the single most on-point piece for the "web server residing on the equipment + browser access to monitor/control" concept. The DPMA/EPO considered it sufficiently material to summarize in the EP0954917 B1 specification itself.
• Source: https://patentimages.storage.googleapis.com/b0/69/cb/a24a2d518923f9/EP0954917B1.pdf

NPL-2 — A.K. Larsen, "Weaving the Management Web," Data Communications, vol. 25, no. 1, Jan. 1, 1996, pp. 92, 94. Companion article; same theme (web-based network management architecture). Relevant to same claims.

NPL-3 — E. Pennino, "A Vision for an Automatic Message Accounting (AMA) Data Networking System," Proceedings of NOMS, vol. 1, Apr. 6–9, 1992, pp. 196–207.

• Description: networking of AMA (billing) data.
• Potentially relevant to: claims 2, 8, 12, 17, 21, 25 (AMA/billing server and web pages). Supplies the AMA-over-network concept, not the browser interface.

NPL-4 — K. Hatonen et al., "TASA: Telecommunication Alarm Sequence Analyzer," IEEE, Apr. 15, 1996, pp. 520–529.

• Description: analyzing telecom alarm sequences for network fault/status management.
• Potentially relevant to: claims 3, 9, 13, 18, 22, 26 (information & problem report / system status). Fault/alarm handling background.

NPL-5 — L. Bruno, "Lasting Legacy: Browsing Big Iron on the Web," Data Communications, vol. 25, no. 15, Nov. 1996, pp. 110–112, 116–118, 120.

• Description: using a web browser to access "big iron" (legacy mainframe/switch) management.
• Potentially relevant to: claims 1, 11, 20 — directly addresses browser-based access to large telecom/host equipment. Combined with Larsen, it is the closest non-patent art to the core independent claims. Note it post-dates Sep. 30, 1996, so it is § 102(a)/103 art as of Nov. 1996, not a § 102(b) bar relative to the Sep. 1997 filing.

NPL-6 — M.A. Hamilton, "Java and the Shift to Net-Centric Computing," Computer, vol. 29, no. 8, Aug. 1996, pp. 31–39.

• Description: Java "write once, run anywhere," downloadable applets executed in a browser.
• Potentially relevant to: claims 5, 15, 24 (Java applets downloadable to the user device and executed by the web browser). Classic § 102(b)/103 art for the applet limitations; the EP specification expressly acknowledges it.

NPL-7 — PCT Search Report, dated Aug. 24, 1999.

• Procedural, not substantive prior art; it is the international search report for the WO 98/33302 family member.

C. Bottom line — ranking and § 102 vs. § 103

Important analytical caveats (do not overstate anticipation):

1. No single cited reference discloses all elements of any independent claim. Every reference that provides browser/web-server access (US 5,742,762; US 5,721,908; Larsen; Bruno) lacks an on-equipment web server combined with the "modify/update operations of the telecommunications equipment in response to user input" limitation; every reference that provides remote modification of telecom equipment operations (US 5,802,146; US 5,958,016; US 5,915,008) lacks the browser/on-equipment-web-server architecture. Realistically these are § 103 combinations, not clean § 102 anticipation.
2. Statutory-date issues. US 5,958,016 (filed Jul. 13, 1997) and US 5,913,061 (filed Jan. 8, 1997) post-date or straddle the Jan. 27, 1997 provisional priority and can only be pre-AIA § 102(e) art. Bruno (Nov. 1996), EP 0 737 922 (Oct. 1996), US 5,913,061 and US 5,826,029 (both Oct. 1998 grants) cannot be § 102(b) bars measured against the Jan. 27, 1997 priority date. Larsen (Jan. 1996), Pennino (Apr. 1992), Hatonen (Apr. 1996), Hamilton (Aug. 1996), US 5,241,588, US 5,488,569, US 5,495,484, EP 0 592 080/091, EP 0 602 824 and WO 95/11560 all pre-date Sep. 30, 1996 and are available under § 102(b).
3. I have verified each citation's bibliographic data against the 6,286,050 front page and Google Patents. Where a reference year/date is from a search result rather than the front page (e.g., EP 0 737 922 publication, Crossroads filing date), I have stated it as reported; I did not independently confirm full-text of every one of the 17 references.

Note on identifiers: all patent numbers above are reproduced exactly as they appear in the 6,286,050 citation records; I have not normalized or corrected any of them.

I'll ground this analysis with live searches on the key prior-art references before building the § 103 combinations.

Good — I have solid grounding on two key references. Now let me verify the non-patent literature and the Bell Atlantic / DSC references.

Obviousness Analysis — U.S. Patent 6,286,050 B1

"System and Method for Monitoring and Management of Telecommunications Equipment Using Enhanced Internet Access"

Analytical frame: Pre‑AIA 35 U.S.C. § 103(a) (application filed 1997‑09‑30; never subject to AIA § 3). Governed by Graham v. John Deere, 383 U.S. 1 (1966) and KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007); structured per MPEP § 2143.

Verification note: I retrieved and read the full text of U.S. 5,742,762 and U.S. 5,721,908. For the remaining cited references I rely on the bibliographic data (number, title, assignee, date) as it appears on the Google Patents page for US 6,286,050 and on the title-implied subject matter. I flag confidence levels where I could not read the reference body. I did not locate the full text of the Larsen, Bruno, or Hamilton articles, nor the outcome of the D. Del. litigation (1:14‑cv‑00628) — treat those characterizations as inferences from title, venue, and examiner citation, not as verified quotations.

I. The Claimed Subject Matter

Three independent claims, all sharing the same core:

The patent's own Background supplies the problem statement and the motivation evidence a § 103 analysis will lean on heavily:

"Typically, a modem-based RS232 ASCII protocol is used for the link up between X-terminals located at the remote sites to the telecommunications equipment. Although graphical user interfaces (GUIs) can be supported by this access scheme, it is excruciatingly slow because it operates on a bit map or pixel information basis. Thus, a very wide pipe, such as a T1 span, is required to enable even minimally adequate graphical update of screen information."

That is a textbook statement of the known problem that browser/HTML architecture solved (send text and render client-side, rather than shipping bitmaps over a thin pipe). It frames the invention as a bandwidth/latency fix, not a new capability.

Effective filing date / prior-art status. Provisional 60/034,874 was filed 1997‑01‑27; the non-provisional 1997‑09‑30. If the claims are entitled to the provisional date, § 102(b) art must predate 1997‑01‑27 (i.e., 1996‑01‑27). If not, § 102(b) reaches back only to 1996‑09‑30. This matters:

• The two Larsen articles (Data Communications, 1996‑01‑01) are § 102(b) art on either date.
• Hamilton (IEEE Computer, Aug. 1996) and Bruno (Data Communications, Nov. 1996) are § 102(a) art on either date, and § 102(b) art if the provisional date is unavailable.
• U.S. 5,958,016 (Bell Atlantic, filed 1997‑07‑13) is § 102(e) art only if the claims do not get the provisional date. This is a genuine open question and the single most consequential date issue for the § 103 case below.
• All other cited patents issued or were filed well before the critical date.

II. Reference-by-Reference Mapping

Primary reference: U.S. 5,742,762 — Scholl & Witowsky, Telogy Networks (filed 1995‑05‑19; issued 1998‑04‑21) — verified

This is the strongest single reference and it maps nearly every limitation of claims 1, 11 and 20 except the physical situs of the web server.

• Browser as the network management console. "The present invention for the first time permits a Web client, communicating through a Web server, to perform network management… This permits a Web user to manage multiple networks and access multiple networks via a single Web client."
• HTML pages built on the fly from network-element data. Claim 1(i): "means for converting network management information transmissions, in real‑time, into HTML documents." Description: responses are converted "dynamically in real time… into HTML document files (that is, HTML files that are built 'on the fly')."
• Management categories that map to the dependent claims. Configuration management, fault management, performance management, accounting management, security management, help desk, trouble ticket and reporting — i.e., the fault/status, billing/accounting, and troubleshooting domains recited in claims 2–4 and 8–10.
• Remote modification, not mere viewing. Configuration management is defined as "tracking and changing network configuration from remote locations." The specification's worked example is remote reconfiguration of a phone network: "a single remote user… could control, manage, reconfigure, and account for all the company's phone systems."
• Co-residency is contemplated. Claim 4 of '762 requires that "the local managed information database is resident on the same hardware platform as the Web server," and the specification states the invention "can be embodied as a software application resident on a Web server."

The gap: Telogy's FIG. 3 positions the web server and the network management gateway as infrastructure upstream of the managed network elements, which are reached through proxy agents. It does not expressly place a web server on the switch. That gap is the entire battlefield for claim 1.

Secondary references

III. The Obviousness Combinations

Combination 1 (primary): Telogy '762 + Larsen (both articles) + Bruno + IBM '908 + Hamilton

Claim 1. Telogy '762 discloses every functional element: a web browser serving as the operator console; a web server answering the browser over the Internet; HTML documents generated in real time from network management data; user input received via CGI; and configuration management defined as changing configuration remotely, with a phone-network reconfiguration example. The only untaught element is that the web server resides on the telecommunications equipment, rather than on a gateway host.

Larsen and Bruno supply that element. The Data Communications pairing (Jan. 1, 1996), cited by the examiner, is contemporaneous, peer-reviewed trade press describing the state of web-based network management as of the critical date — including browser access to "big iron." A POSITA reading Telogy alongside this art would immediately recognize the design option of embedding the web server in the managed element itself.

Motivation to combine (three independent KSR rationales):

1. Known technique, known problem, predictable result. Browser/HTML was a known technique for remotely managing network equipment; the known problem was the bandwidth- and latency-prohibitive bitmap/X-terminal link recited in the patent's own Background. Applying HTML rendering to telecommunications equipment yields no more than the expected result — efficient, platform-independent display.
2. Design incentive / market trend. The art itself presses toward eliminating intermediaries: IBM '908's control-program-agent architecture already collapses the request/response path to a URL-addressed homepage, and Telogy expressly states the NMG "can be embodied as a software application resident on a Web server" and that its database may be "resident on the same hardware platform as the Web server." Once the management application and web server are co-located, the further step of co-locating them with the managed element eliminates a dedicated gateway host, its cost, and its single-point-of-failure — a predictable engineering trade-off, not an inventive leap.
3. "Directly connect" is answered by the address scheme. Claim 1's "directly connect with the telecommunications equipment using its internet address" is satisfied the moment the web server sits on the equipment, because the URL then resolves to the equipment itself. IBM '908 supplies the URL-addressing idiom.

Claim 11 adds only "a plurality of user devices" and "an intranet." IBM '908 discloses the intranet/Internet/firewall architecture expressly, including the definition of an intranet quoted above. Multiple browser clients are inherent in Telogy ('762 describes any "commercially available Web client" — Netscape, NCSA Mosaic, Enhanced Mosaic, IBM WebExplorer — on Macintosh, Windows and X-Windows).

Claim 20 is claim 1 in method form and falls with it; the "specifying an internet address associated therewith through a web server residing on the telecommunications equipment" step is the same co-residency limitation addressed by Larsen/Bruno.

Combination 2 (control/provisioning emphasis): Telogy '762 + U.S. 5,958,016 + U.S. 5,826,030

If an examiner or challenger wanted to fortify the "web server operable to modify or update operations" limitation (claim 1, last clause; claim 11; claim 20), U.S. 5,958,016 (web link to IN service control) and U.S. 5,826,030 (universal switch API with user-definable data and generic-format responses) are the natural complements. '030 teaches that a telecommunications switch exposes its call-processing and control functions through a standardized message interface — exactly the backend that a browser-submitted command would drive. Motivation: Telogy's configuration management already teaches remote changing of network configuration; '016/'030 merely supply a switch-specific instance of a general web-to-network-element control path.

Caveat: U.S. 5,958,016 is only available as § 102(e) art if the claims are denied the 1997‑01‑27 provisional date. Its filing date (1997‑07‑13) postdates the provisional.

Combination 3 (dependent claims — AMA/billing): Telogy '762 + Pennino (NOMS 1992)

Claims 2, 8, 12, 21 and 25 add "an automatic message accounting server" and "web pages dedicated to billing information monitoring and management." Telogy '762 enumerates accounting management ("the collection of statistical information on network use by subscribers") as one of five core management modules and expressly claims receiving browser requests for it. Pennino teaches that AMA data in a telecommunications network is a discrete, network-accessible data collection function. Motivation: AMA is an identified, pre-existing management domain and a network-accessible server was the known way to serve it; presenting its output through the existing browser console of Combination 1 is the predictable application of a known technique. The patent's own specification points to U.S. App. Ser. 08/757,465 for AMA detail, characterizing it as an implementation choice rather than inventive subject matter.

Combination 4 (dependent claims — fault/status): Telogy '762 + Hatonen (TASA) + Bell Atlantic '146

Claims 3, 9, 13, 18, 22 and 26 add an "information and problem report server." Telogy supplies fault management ("isolate, diagnose, resolve and log network problems on a real-time basis"). Hatonen (TASA, Apr. 1996) teaches telecom alarm-sequence analysis as a distinct function. U.S. 5,801,146 teaches an AIN maintenance operations console presenting fault/status information. Motivation: fault/status reporting is one of the standard OSI/Telecom Management Network functional areas the cited art already partitions; segregating it into a dedicated server behind the same web server is a conventional modularization.

Combination 5 (dependent claims — trace logs): weakest link

Claims 4, 10, 14, 19, 23 and 27 require "a trace log server… dedicated to program trace information." None of the seventeen cited references squarely discloses program trace logging. The closest art is U.S. 6,404,882 (Ameritech, "Method and system for call tracing," priority 1996‑11‑27), but that appears on this page under Cited By, not within the Citations set, and it concerns call tracing rather than program trace logs. This claim family is therefore better attacked as routine and well-known practice (program trace logs and the remote viewing thereof were standard switch-development and maintenance tooling) combined with Telogy's fault/troubleshooting modules, rather than by a specific reference mapping. I would rate these claims materially more defensible than claims 1, 11 and 20 on the cited record.

Combination 6 (dependent claims — Java applets and the distributed switch): Hamilton + Telogy '762 + U.S. 5,495,484

• Claims 5, 15, 24 (Java applets downloadable to the user device, executed by the web browser): Hamilton (IEEE Computer, Aug. 1996) is directly on point. Motivation: HTTP is stateless, and maintaining a rich interactive management GUI over repeated GET round-trips is impractical; Hamilton and Telogy's own disclosure supply the recognized client-side-execution solution. The patent specification itself simply recites Norton Navigator/Microsoft Explorer as Java-enabled browsers — describing the applet mechanism as an off-the-shelf capability.
• Claims 6, 16 (distributed switching system, service unit + at least one delivery unit, web server in the service unit): U.S. 5,495,484 is not merely cited — the 6,280,050 specification expressly incorporates it by reference and adopts its service unit / delivery unit / ring vocabulary. This is the patent's own admission of prior art. '484 supplies the switching architecture; Combination 1 supplies the web server placement in the service unit (which is where the Services Element process manager already runs, per FIG. 3 of '050).

IV. Rebuttal Arguments and Where the § 103 Case Is Weakest

Fairness requires identifying the counterarguments a patent owner would press:

1. Teaching away (the best defense). Telogy '762 is architected around a centralized "manager of managers" that unifies multiple incompatible managed networks behind one console. Its premise is that management intelligence is centralized and remote from the elements. Placing a web server on each individual switch arguably undercuts the MOM rationale, its multi-vendor abstraction layer, and its proxy-agent/MIB caching design. A patent owner would argue non-obviousness from this contextual tension. Counter: the tension is architectural preference, not a teaching away — '762 claim 4 and the specification both contemplate co-residency of the management application with the web server, and IBM '908 independently teaches URL-addressed access to a homepage-based resource.
2. The co-residency limitation is genuinely narrow. Claim 1's "residing on the telecommunications equipment" is the point of novelty relative to '762 and it is not a trivial limitation — it converts a general-purpose IT management gateway into an embedded-appliance architecture, and it carries real consequences (footprint, reliability, security surface on a central-office switch). The Patent Office allowed all claims over all seventeen references. My analysis is a reasoned § 103 challenge, not a legal conclusion.
3. Hindsight caution (In re McLaughlin; KSR's own warning). The combination's "motivation" is only as strong as the contemporaneous 1996 evidence. I verified Telogy '762 and IBM '908 in full, but could not read the Larsen, Bruno, or Hamilton texts in this session. If Larsen/Bruno turn out to address web-based management of data-network elements (routers, hubs) rather than telecommunications switches, the motivation for transposing the architecture to the patented distributed switching system weakens, and the case leans more heavily on Bruno's "big iron" framing and on the predictable-results rationale.
4. Objective indicia. No secondary-consideration evidence (licensing, copying, commercial success, failure of others) is apparent on the face of the record. Absent such evidence, the Graham factors favor the challenger. Notably, the patent's own Background concedes the problem was known and frames the invention as a performance improvement, which tends to neutralize "unexpected results."
5. Post-filing and datum caveats. U.S. 5,958,016 and U.S. 5,913,061 are § 102(e)-only references whose availability turns on the provisional-date question; U.S. 5,721,908 (filed 1995‑06‑07) and U.S. 5,742,762 (filed 1995‑05‑19) are safely prior art under every scenario.

V. Bottom Line

• Claims 1, 11 and 20 are the vulnerable claims, and the vulnerability is concentrated in one limitation: the web server residing on the telecommunications equipment. Telogy '762 + Larsen (Jan. 1, 1996) + Bruno (Nov. 1996), with IBM '908 for the intranet/URL architecture, renders them obvious under the "known technique / predictable result" and "design incentive" rationales of KSR. Hamilton (Aug. 1996) cleanly disposes of the Java-applet claims (5, 15, 24).
• Dependent claims 6/16 are the easiest of all, because U.S. 5,495,484 is admitted prior art incorporated by reference in the '050 specification itself.
• Claims 2/8/12/21/25 (AMA) and 3/9/13/18/22/26 (fault reporting) are strongly supported by Pennino and Hatonen respectively, combined with Telogy's enumerated accounting- and fault-management modules.
• Claims 4/10/14/19/23/27 (trace log server) are the patent's strongest claims, because no reference in the Citations set squarely discloses program trace logging; the challenge there must rest on routine-practice evidence rather than on a reference mapping.

Two caveats to carry forward: (i) the availability of U.S. 5,958,016 depends on whether the claims are entitled to the Jan. 27, 1997 provisional — a question I have not resolved; and (ii) I could not verify the body text of the Larsen/Bruno/Hamilton articles or of U.S. 5,801,146, 5,826,029, 5,826,030, 5,495,484, 5,913,061, 5,482,569, 6,404,882, or EP 0 737 922 in this session, so any element I attributed to them from title alone should be confirmed against the reference bodies before being relied upon. The patent expired 2017‑09‑30, so this analysis is relevant to validity in the context of the Delaware action cited on the record (1:14‑cv‑00628) rather than to any current enforcement.