US 10567474

Here is a concise summary of US patent 10567474:

Title: Direct binary file transfer based network management system free of messaging, commands and data format conversions

Assignee: OPTIMUM COMMUNICATIONS SERVICES Inc. (Current Assignee), Optimum Communications Services Inc Canada (Original Assignee)

Inventors: Mark Henrik Sandstrom

Filing Date: March 6, 2018

Issue Date: February 18, 2020

Abstract: Telecommunication network management operations are performed based on accessing network management data (NMD) files via GUIs and general purpose computers including a network management system (NMS) server, and automatic routines for transferring binary NMD files between the general purpose computers and remote network elements (NEs) being managed. A system user produces configuration files at the NMS server for NEs using a network management GUI, and the hardware of NEs automatically complete the network management operations indicated by the NMD files transferred to them from the NMS server and produce their status files to the NMS server. The network management GUI displays network status based on the latest NE status files at the NMS server. This provides direct, binary file transfer based NMS communication that avoids the complexity and restrictions of intermediate messaging protocols or transaction languages and conversions thereof.

Plain-Language Overview of Independent Claims:

• Claim 1 (System Claim): This claim describes an infrastructure management system. It includes remote elements with storage for configuration data (CD) that is kept in sync with user-accessible copies on a computer system. Digital logic in the remote elements uses this CD to perform operations. The computer system has a storage facility for the user-accessible CD, a user interface to manage the remote elements by accessing this CD, and a network interface to transfer CD to the remote elements for synchronization. Crucially, the configuration data is automatically generated from parameters defining a service contract for the remote elements, and these element-side copies of CD directly control hardware logic registers on the remote elements. The user interface allows users to view and modify both the user-accessible CD and the contract parameters from which the CD and register contents are derived.

• Claim 5 (System Claim): This claim describes an infrastructure management system focused on monitoring. It includes remote elements with storage for status data (SD) that is continuously synchronized with user-accessible copies on a computer system. Digital logic in the remote elements generates the content for this element-side SD. The computer subsystem provides a storage facility for the user-accessible SD, a user interface to monitor the remote elements by accessing this SD, and a network interface to transfer SD from the remote elements to the computer subsystem for synchronization. The user interface specifically displays the status of defects at the remote elements, including a summary of whether each remote element has at least one active defect, which indicates a detected operational fault condition.

• Claim 9 (Method Claim): This claim describes a method for interaction between system components over a wide area network. It involves a first component producing a series of management data units, where each unit contains information fields, one of which indicates an action for a second component. These data units are transferred from the first component to the second component to keep their management data in sync. The second component then processes the information fields and performs the indicated action. The method specifies that memories at both components have segments for configuration and status files, and the management data unit includes information corresponding to both.

  • In a first scenario, where the first component is a computer subsystem and the second is a remote element, the action-indicating information is in the configuration file segment, and the remote element performs the action.
  • In a second scenario, where the first component is the remote element and the second is the computer subsystem, the action-indicating information is in the status file segment, and the computer subsystem performs the action.
  • The management data at the computer subsystem is user-accessible for remote management of the remote element.

(No uncertainty identified in the authoritative information provided by the patent text itself.)

US patent 10567474 is currently involved in multiple litigation cases. Here's a summary of the known cases:

• Case 1:

  • Jurisdiction: Minnesota District Court
  • Case Number: 0:24-cv-03118
  • Status: Active

• Case 2:

  • Jurisdiction: Virginia Eastern District Court
  • Case Number: 1:24-cv-01681
  • Status: Active

• Case 3:

  • Jurisdiction: Virginia Eastern District Court
  • Case Number: 1:24-cv-01687
  • Status: Active

• Case 4:

  • Jurisdiction: Virginia Eastern District Court
  • Case Number: 1:24-cv-01682
  • Status: Active

• Case 5:

  • Jurisdiction: International Trade Commission
  • Case Number: 337-TA-3792
  • Status: Active

• Case 6:

  • Jurisdiction: Minnesota District Court
  • Case Number: 0:24-cv-03053
  • Status: Active

• Case 7:

  • Jurisdiction: Minnesota District Court
  • Case Number: 0:24-cv-02796
  • Status: Active

• Case 8:

  • Jurisdiction: Court of Appeals for the Federal Circuit
  • Case Number: 25-1269
  • Status: Active

• Case 9:

  • Jurisdiction: International Trade Commission
  • Case Number: 337-TA-1391
  • Status: Active

The available information from the provided patent text does not specify the plaintiffs, defendants, or filing dates for these cases, nor does it provide details on the outcomes or current status beyond "Active."

Proceedings overview

As of today, July 21, 2026, there are no AIA trial proceedings on file for US Patent 10567474 according to the USPTO ODP API. A web search for PTAB proceedings related to this patent also did not reveal any IPR, PGR, or CBM trials.

Strategic summary

Currently, there are no PTAB proceedings (IPR, PGR, or CBM) recorded for US Patent 10567474. This means all claims (1-18) of the patent remain untested by the PTAB.

Since no AIA trials have been initiated, there is no estoppel landscape established under 35 U.S.C. § 315(e)(2). Therefore, all prior art grounds remain available for a defendant to challenge the patent's validity, either in district court litigation or through future PTAB proceedings.

The absence of PTAB activity could indicate several things: the patent may not have been heavily asserted, the patent owner may have chosen not to engage in PTAB proceedings, or potential challengers have not yet filed petitions.

Recommended next steps

Since no PTAB activity exists for US10567474, the patent has not been subjected to the scrutiny of an IPR, PGR, or CBM trial. For a defendant facing assertion of this patent, all claims (1-18) are currently considered valid as granted by the USPTO.

The absence of PTAB activity means that a potential defendant has a full range of prior art and statutory grounds (§ 102, § 103, § 112) available to challenge the patent's validity if they choose to pursue an IPR. It is important to note that well-asserted patents often eventually attract IPRs.

I'll research the assignment record for US 10567474, starting with the USPTO Assignment Center and cross-referencing.

Now let me dig into the assignment records and the entities involved.

I have strong leads. Let me pin down the specific assignment records and correspondent details.

I was able to retrieve the key assignment data, but note the tool limit meant I could not open the USPTO Assignment Center's abstract-of-title directly. The reconstruction below combines the patent's own legal‑events feed (which cites a specific reel/frame), the sibling OCS assignment records surfaced via Google Patents, and litigation/corporate records. I flag gaps explicitly rather than fill them.

---

Inventors

Mark Henrik Sandstrom — sole named inventor. No co-inventors on US10567474 or its parent chain.

• Employer at time of filing: Optimum Communications Services, Inc. ("OCS"). Sandstrom publicly identifies as president and director of OCS since 2005 (and of ThroughPuter, Inc. since 2012; before that, president/director of Optimum Communications Technologies in the San Francisco Bay Area).
• Address of record: The OCS-family prosecution records show Sandstrom at 344 Grove Street #242, Jersey City, NJ 07302; later filings list Virginia Beach, VA, and Alexandria, VA.
• Pattern note: This is not the "all inventors depart the original assignee within 12 months" fire-sale precursor. It is the inverse pattern — a sole inventor who also controls the assignee, later asserting the patent himself (pro se) and through his own company. Stanford's NPE Litigation Database indexes US10567474 with the asserter category "9 Individual."

---

Original assignee

Optimum Communications Services, Inc. ("OCS").

• Entity / jurisdiction — a flagged contradiction. The patent's face and Google Patents list the original/current assignee as Optimum Communications Services Inc (Canada) (the sibling US7333511 assignment history shows an Alberta corporation re-domiciled through a Delaware corporation). However, the recorded 2023 assignment and the ITC complainant both name a New Jersey corporation at 344 Grove Street #242, Jersey City, NJ. So the "original assignee" name is right but the jurisdiction of record is inconsistent across sources. Treat "Canada" on the face vs. "New Jersey" in the 2023 recording as a genuine discrepancy to verify at the Assignment Center.
• Line of business: telecom/optical-networking and network-management technology (network element configuration, xPON/FTTH transport, NMS communications). It is effectively a patent-holding and licensing/assertion vehicle controlled by the inventor.
• Does it ship products embodying the claims? No evidence. OCS's own ITC complaint pleaded a domestic industry based on "authorized usage of the asserted patents" (i.e., licensing), not on articles it manufactures.
• Current status: active as the asserting/licensing entity for this family; no bankruptcy, acquisition, or dissolution found; principal address is a residential apartment, not a corporate campus.
• External misattribution to flag: some Chinese-language trade alerts state "Optimum is owned and operated by Altice USA." That conflates Altice USA's "Optimum" cable brand with Optimum Communications Services, Inc. The ITC notice (344 Grove Street #242, Jersey City, NJ 07302) and the Federal Circuit record (Sandstrom controlling OCS) show they are unrelated.

---

Assignment timeline

Two caveats before the list: (1) the Google Patents legal-events feed for US10567474 shows only one recorded assignment post-issuance and does not surface any pre-issue recording, even though the face of the patent already names OCS; (2) I could not open the Assignment Center abstract-of-title to pull the parent-application reels/frames. So the list below is the confirming record I could actually verify, not necessarily every link.

• 2023-12-01 (executed) / recorded 2023-12-01 — Reel 065737/0513
  • Conveyance: Assignment of assignors' interest
  • Assignor: Mark Henrik Sandstrom (individually)
  • Assignee: Optimum Communications Services, Inc. (New Jersey)
  • Correspondent: not retrievable from the sources I could reach. No outside counsel has appeared for OCS in its related ITC matters — Sandstrom signed as OCS's president — which suggests the recording may have been filed by the assignee rather than through a law firm. Flagging the correspondent as undetermined, not as a repeat player.
  • Context: transfer-to-asserter / standing-clearing transfer — executed ~7 weeks before OCS's 2024-01-19 ITC complaint asserting the '474.

For context only — sibling OCS records (different patents, same owner family), showing the OCS entity chain on Google Patents:

• Reel 028496/0056 — related to Optimum Communications Services, Inc. (New Jersey) recording.
• Reel 028790/0437 — a notice of non-recordation (#50199863) dispute: "last proper assignment by Optimum Communications Services, Alberta Corp… latest lawful assignee is Optimum Communications Services, Delaware Corp."
• Reel 039070/0461 — executed/effective 2016-07-04, assignor Sandstrom, Mark (New Jersey) → Optimum Communications Services, Inc.

These confirm the OCS corporate chain (Alberta → Delaware → New Jersey) and the pattern of Sandstrom-to-OCS recordings, but they are not US10567474 records. They are a strong indication that a comparable Sandstrom→OCS recording exists for the '474's parent applications; that reel/frame is unverified here.

---

Timeline diagram

timeline
    title Ownership of US 10567474
    2006 : Priority application filed
    2018 : Continuation filed by Sandstrom
    2020 : Patent issued with OCS as assignee
    2023 : Sandstrom assigns to OCS New Jersey
         : Recorded reel 065737 frame 0513
         : OCS files first ITC complaints
    2024 : OCS ITC complaint asserts the 474 patent
         : Sandstrom files declaratory judgment suits
    2026 : Federal Circuit affirms no infringement

---

NPE / troll-pattern signals

1. Shell-entity transfer — Unclear. There is no third-party acquisition: the assignee (OCS) is the inventor's own long-standing company and was already the assignee on the patent's face, so this is not the classic "operating company sells to a licensing LLC" move. But the assignee shows shell-like characteristics — no products in commerce, a licensing-based domestic-industry showing, and a residential principal address (344 Grove Street #242, Jersey City, NJ). Evidence: Reel 065737/0513 and ITC Inv. No. 337-TA-1391 notice.

2. Known asserter in the chain — Unclear. Neither OCS nor ThroughPuter matches the classic public NPE lists (Acacia, Marathon, IV, IPNav, Wi-LAN/Conversant, Vringo, Pendrell, Round Rock, etc.) as current owner. However, third-party reporting states that some patents in this 11-member family "took a circuitous assignment route, into Intellectual Ventures LLC and back out, as well as to OCS and back." That IV passage is unconfirmed for US10567474 specifically, so I mark it unclear rather than present. Separately, the patent is indexed in Stanford's NPE Litigation Database (asserter category "Individual").

3. Repeat correspondent across the chain — Unclear. I could not retrieve the correspondent of record for Reel 065737/0513; no attorney or firm recurs in the sources available. No finding; do not infer a repeat player from absence.

4. Cascading transfers — Not present. US10567474 shows a single recorded assignment (065737/0513). No chained LLC-to-LLC sequence within 24 months on this patent.

5. Pre-litigation transfer — Present (strong). Assignment executed/recorded 2023-12-01 (Reel 065737/0513), roughly 7 weeks before OCS's 2024-01-19 ITC complaint asserting the '474 (Inv. No. 337-TA-1391; Fed. Reg. 89 FR 15611). The transfer cleared a clean standing/ownership record for the assertion.

6. Bankruptcy fire-sale — Not present. No Chapter 7/11 or judicial-sale records found for OCS or Sandstrom.

7. Privateering — Not present. The owner asserts directly (Sandstrom pro se in the Minnesota declaratory-judgment actions; OCS as ITC complainant). There is no third-party operating company using an NPE proxy.

8. Defensive aggregator — Not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN; it terminates at the asserting owner.

---

Verdict

NPE — moderate confidence.

The chain is driven by one strong signal: the 2023-12-01 assignment from inventor Sandstrom to Optimum Communications Services, Inc. (Reel 065737/0513), executed only ~7 weeks before the 2024-01-19 ITC complaint that first asserted the '474 — a textbook pre-litigation standing-clearing transfer, reinforced by a non-operating assignee (no products, licensing-based domestic industry, residential address) and by the patent's indexing in Stanford's NPE Litigation Database. I stop short of "high confidence" because there is only a single recorded link (no cascading LLCs, no classic shell transfer, no confirmed aggregator in the chain), and the assignee is the inventor's own long-standing corporation rather than a purpose-built third-party shell — and one third-party source's claim that the family passed through Intellectual Ventures could not be confirmed for this patent.

Verify at: USPTO Assignment Center — https://assignmentcenter.uspto.gov/ (search by patent number 10567474); confirm the full abstract of title, the parent-application reel/frame entries, and the correspondent for Reel 065737/0513.

Data-integrity notes: (a) the patent face names a Canada OCS entity while the 2023 recording and ITC complainant name a New Jersey OCS entity — unreconciled; (b) the Assignment Center was not directly queryable within my tool budget, so the parent-chain reels/frames remain unverified; (c) the previously-generated litigation summary omitted party names — the search results above supply them (e.g., OCS v. Changsha Silun et al., 337-TA-1391; Xenogenic Development LLC as intervenor; Sandstrom's D. Minn. DJ suits against AT&T/Charter/Ericsson/Nokia).

To identify the most relevant prior art for US patent 10567474 and analyze its potential anticipation of claims, I will examine the "Patent Citations" section of the patent document itself. The patent document provides a list of prior art patents cited by the examiner.

Here's the breakdown of the most relevant prior art, focusing on potential anticipation under 35 U.S.C. § 102. Please note that a full anticipation analysis would require a detailed claim construction and comparison, but this provides an initial assessment based on the descriptions.

Most Relevant Prior Art for US10567474

1. US5533116A: Network management system

• Full Citation: US5533116A
• Publication/Filing Date: Filed March 10, 1992 / Published July 2, 1996
• Brief Description: This patent describes a network management system.
• Potential Anticipation (35 U.S.C. § 102): The title alone suggests it could broadly anticipate elements of Claims 1, 5, and 9 related to a "network management system" and "infrastructure management system." Without further details on the mechanism, it's difficult to pinpoint specific elements, but any system managing network elements could be relevant.

2. US5365514A: Event driven interface for a system for monitoring and controlling a data communications network

• Full Citation: US5365514A
• Publication/Filing Date: Filed March 1, 1993 / Published November 15, 1994
• Brief Description: This patent describes an event-driven interface for monitoring and controlling a data communications network.
• Potential Anticipation (35 U.S.C. § 102): The "monitoring and controlling" aspects could anticipate parts of Claims 1 and 5, particularly regarding managing and monitoring remote elements, and the "event-driven interface" might relate to how status or configuration changes are handled.

3. US5566335A: Method and apparatus for firmware upgrades in embedded systems

• Full Citation: US5566335A
• Publication/Filing Date: Filed March 16, 1993 / Published October 15, 1996
• Brief Description: This patent details a method and apparatus for firmware upgrades in embedded systems.
• Potential Anticipation (35 U.S.C. § 102): This reference is highly relevant to the "transferring NE program and control files" and "NE program memory segment" mentioned in the description of US10567474's claims. Specifically, Claim 1 and Claim 9 (first instance, computer subsystem to remote element) involving configuration data/program files being transferred to remote elements. The concept of updating firmware in an embedded system could directly anticipate the program file transfer aspect.

4. US5506712A: Photonic frequency routing type time division highway switch

• Full Citation: US5506712A
• Publication/Filing Date: Filed July 14, 1993 / Published April 9, 1996
• Brief Description: This patent describes a photonic frequency routing type time division highway switch.
• Potential Anticipation (35 U.S.C. § 102): While seemingly focused on a specific hardware implementation, the idea of a "switch" (a network element) and its configuration could broadly relate to Claim 1, especially if the configuration of such a switch involves control data.

5. US5526349A: Data formats for telecommunications networks

• Full Citation: US5526349A
• Publication/Filing Date: Filed April 15, 1994 / Published June 11, 1996
• Brief Description: This patent discusses data formats for telecommunications networks.
• Potential Anticipation (35 U.S.C. § 102): This reference is relevant to the "binary network management data (NMD) files" aspect of US10567474, particularly how data is structured for transfer. It could anticipate the implicit data format in Claim 9's "management data units" and the explicit "binary NMD files" in the overall system.

6. GB2301717A: Network controller for monitoring the status of a network

• Full Citation: GB2301717A
• Publication/Filing Date: Filed June 2, 1995 / Published December 11, 1996
• Brief Description: This patent describes a network controller for monitoring the status of a network.
• Potential Anticipation (35 U.S.C. § 102): This is highly relevant to Claim 5, which focuses on monitoring the status of remote elements and displaying defect status. The core functionality of a "network controller for monitoring network status" directly overlaps with this aspect.

7. US5761429A: Network controller for monitoring the status of a network

• Full Citation: US5761429A
• Publication/Filing Date: Filed June 2, 1995 / Published June 2, 1998
• Brief Description: This patent describes a network controller for monitoring the status of a network.
• Potential Anticipation (35 U.S.C. § 102): Similar to GB2301717A, this is highly relevant to Claim 5, directly addressing the monitoring of network status and potentially the detection of operational fault conditions.

8. US6205563B1: Method and apparatus for inter-domain alarm correlation

• Full Citation: US6205563B1
• Publication/Filing Date: Filed May 28, 1996 / Published March 20, 2001
• Brief Description: This patent describes a method and apparatus for inter-domain alarm correlation.
• Potential Anticipation (35 U.S.C. § 102): This patent is relevant to the alarm notification aspects of US10567474, particularly Claim 5 and its dependent claims (6, 7, 8) that deal with displaying notifications of significant events and alarm activations. The handling of "defects" and "operational fault conditions" in US10567474 finds a strong parallel in "alarm correlation."

9. US5901320A: Communication system configured to enhance system reliability using special program version management

• Full Citation: US5901320A
• Publication/Filing Date: Filed November 29, 1996 / Published May 4, 1999
• Brief Description: This patent describes a communication system configured to enhance system reliability using special program version management.
• Potential Anticipation (35 U.S.C. § 102): This is relevant to the management of "NE program files" in US10567474, particularly in Claim 1 and Claim 9 (first instance). The concept of program version management directly relates to transferring and maintaining program files at remote elements.

10. US7146568B2: Dynamically drilling-down through a health monitoring map to determine the health status and cause of health problems associated with network objects of a managed network environment

• Full Citation: US7146568B2
• Publication/Filing Date: Filed May 29, 1998 / Published December 5, 2006
• Brief Description: This patent describes dynamically drilling-down through a health monitoring map to determine the health status and cause of health problems in a managed network environment.
• Potential Anticipation (35 U.S.C. § 102): Highly relevant to Claim 5, which deals with displaying network status and defects. The detailed "health monitoring" and "determining health status and cause of health problems" strongly overlaps with the concepts of monitoring defect status and operational fault conditions in US10567474.

11. US6347330B1: Dynamic selective distribution of events to server receivers

• Full Citation: US6347330B1
• Publication/Filing Date: Filed September 4, 1998 / Published February 12, 2002
• Brief Description: This patent describes the dynamic selective distribution of events to server receivers.
• Potential Anticipation (35 U.S.C. § 102): This could anticipate the mechanism by which status files (representing events/status changes) are transferred from NEs to the NMS server in Claim 5 and the second instance of Claim 9. The "distribution of events" could relate to how status information is disseminated within the system.

12. US6674714B1: Retainment of alarm events during wait restore (WTR) cycle of channel restoration and squelch table with reduced memory area

• Full Citation: US6674714B1
• Publication/Filing Date: Filed October 26, 1998 / Published January 6, 2004
• Brief Description: This patent describes the retainment of alarm events during a wait restore cycle of channel restoration and a squelch table with reduced memory area.
• Potential Anticipation (35 U.S.C. § 102): Directly relevant to the alarm and defect management aspects of Claim 5, particularly the handling and generation of alarm notifications (dependent claims 6-8). The "retainment of alarm events" and concepts related to alarm management are pertinent.

13. US6961343B1: Cross-connection switch

• Full Citation: US6961343B1
• Publication/Filing Date: Filed October 30, 1998 / Published November 1, 2005
• Brief Description: This patent describes a cross-connection switch.
• Potential Anticipation (35 U.S.C. § 102): Similar to US5506712A, as a type of "network element," the configuration and operation of such a switch could anticipate aspects of Claim 1, especially if configuration involves control data. Claim 2, which refers to "connecting communications data between different network interfaces of the given remote element," is particularly relevant here.

14. US7058704B1: Method and apparatus for implementing a service-level agreement

• Full Citation: US7058704B1
• Publication/Filing Date: Filed December 1, 1998 / Published June 6, 2006
• Brief Description: This patent describes a method and apparatus for implementing a service-level agreement.
• Potential Anticipation (35 U.S.C. § 102): Highly relevant to Claim 1, specifically where "contents of the user accessible copies of the CD are generated automatically through derivation from one or more parameters defining a contract that the set of remote elements are deployed for." This directly addresses the concept of configuring elements based on service contracts. Also relevant to Claim 10.

15. US6654802B1: Network system and method for automatic discovery of topology using overhead bandwidth

• Full Citation: US6654802B1
• Publication/Filing Date: Filed February 12, 1999 / Published November 25, 2003
• Brief Description: This patent describes a network system and method for automatic discovery of topology using overhead bandwidth.
• Potential Anticipation (35 U.S.C. § 102): While not directly addressing binary file transfer, the "network system" aspect could broadly relate to the overall system in Claims 1 and 5. The "automatic discovery of topology" might have implications for how NEs are initially recognized or integrated into the NMS, indirectly affecting configuration data.

16. EP1045548A2: Status display unit using icons and method therefore

• Full Citation: EP1045548A2
• Publication/Filing Date: Filed March 26, 1999 / Published October 18, 2000
• Brief Description: This patent describes a status display unit using icons and a method for it.
• Potential Anticipation (35 U.S.C. § 102): Very relevant to Claim 5, specifically the user interface displaying status, including "summarized representation of whether each given one of the remote elements has at least one active defect." The use of icons for status display could directly anticipate or render obvious the display aspects.

17. US7110358B1: Method and apparatus for managing data traffic between a high capacity source and multiple destinations

• Full Citation: US7110358B1
• Publication/Filing Date: Filed May 14, 1999 / Published September 19, 2006
• Brief Description: This patent describes a method and apparatus for managing data traffic between a high capacity source and multiple destinations.
• Potential Anticipation (35 U.S.C. § 102): This could be relevant to the network interface and transfer aspects of all claims, particularly how the "network interface transferring the user accessible copies of the CD" (Claim 1) or "network interface transferring the element-side copies of the SD" (Claim 5) operates. The efficient management of data traffic is a foundational element of any network management system.

18. US7363359B1: Element management system with automatic remote backup of network elements' local storage

• Full Citation: US7363359B1
• Publication/Filing Date: Filed May 26, 1999 / Published April 22, 2008
• Brief Description: This patent describes an element management system with automatic remote backup of network elements' local storage.
• Potential Anticipation (35 U.S.C. § 102): This is highly relevant to the synchronization of configuration and status data between remote elements and a central system, as described in Claims 1, 5, and 9. The "automatic remote backup" function could encompass the continuous synchronization of data.

19. US6714977B1: Method and system for monitoring computer networks and equipment

• Full Citation: US6714977B1
• Publication/Filing Date: Filed October 27, 1999 / Published March 30, 2004
• Brief Description: This patent describes a method and system for monitoring computer networks and equipment.
• Potential Anticipation (35 U.S.C. § 102): Directly relevant to the monitoring aspects of Claim 5, particularly the monitoring of remote elements and their status.

20. US6888841B1: Pipelined scheduling technique

• Full Citation: US6888841B1
• Publication/Filing Date: Filed November 10, 1999 / Published May 3, 2005
• Brief Description: This patent describes a pipelined scheduling technique.
• Potential Anticipation (35 U.S.C. § 102): While more general, scheduling techniques could be relevant to the "periodical routines" for transferring files in US10567474, particularly how the transfers are initiated and managed. This could potentially anticipate aspects of the method in Claim 9.

21. US6697373B1: Automatic method for dynamically matching the capacities of connections in a SDH/SONET network combined with fair sharing of network resources

• Full Citation: US6697373B1
• Publication/Filing Date: Filed January 18, 2000 / Published February 24, 2004
• Brief Description: This patent describes an automatic method for dynamically matching capacities of connections in an SDH/SONET network and fair sharing of network resources.
• Potential Anticipation (35 U.S.C. § 102): This reference is relevant to Claim 2, which specifies operations including "connecting communications data between different network interfaces." The dynamic matching and sharing of resources would involve such connections and configurations. The "automatic method" could also relate to the "automatic consequences" of NMD files in US10567474.

22. US20020049608A1: Systems and methods for providing differentiated business services in information management environments

• Full Citation: US20020049608A1
• Publication/Filing Date: Filed March 3, 2000 / Published April 25, 2002
• Brief Description: This patent describes systems and methods for providing differentiated business services in information management environments.
• Potential Anticipation (35 U.S.C. § 102): This could be relevant to the higher-level functionality enabled by the network management system, particularly how the configuration of network elements (Claim 1) might be driven by "business services" and "service contracts."

23. US20010038607A1: Packet switching system and method

• Full Citation: US20010038607A1
• Publication/Filing Date: Filed April 6, 2000 / Published November 8, 2001
• Brief Description: This patent describes a packet switching system and method.
• Potential Anticipation (35 U.S.C. § 102): A "packet switching system" involves network elements whose configuration and status would be managed. This broadly relates to Claims 1 and 5, especially if the operations performed by the digital logic in the remote elements include packet switching functions.

24. US7051097B1: Embedded database for computer system management

• Full Citation: US7051097B1
• Publication/Filing Date: Filed May 20, 2000 / Published May 23, 2006
• Brief Description: This patent describes an embedded database for computer system management.
• Potential Anticipation (35 U.S.C. § 102): The "storage facility holding the user accessible copies of the CD" and SD in Claims 1 and 5 could be considered a form of database. An "embedded database for computer system management" could anticipate how NMD files are stored and managed at the NMS server.

25. US20050198247A1: Granular management of network resources

• Full Citation: US20050198247A1
• Publication/Filing Date: Filed July 11, 2000 / Published September 8, 2005
• Brief Description: This patent describes granular management of network resources.
• Potential Anticipation (35 U.S.C. § 102): This is highly relevant to the overall management of network elements and their configuration (Claim 1). "Granular management" implies detailed control over network elements, which aligns with the purpose of NMD files for configuration.

26. US20020029266A1: Parallel processing architecture for alarm management network entities

• Full Citation: US20020029266A1
• Publication/Filing Date: Filed September 7, 2000 / Published March 7, 2002
• Brief Description: This patent describes a parallel processing architecture for alarm management network entities.
• Potential Anticipation (35 U.S.C. § 102): Directly relevant to the alarm notification aspects of Claim 5 and its dependent claims (6-8). The "alarm management" and "network entities" (equivalent to remote elements) directly overlap.

27. US20020080446A1: Optical switch and method of switching optical signals

• Full Citation: US20020080446A1
• Publication/Filing Date: Filed November 22, 2000 / Published June 27, 2002
• Brief Description: This patent describes an optical switch and a method of switching optical signals.
• Potential Anticipation (35 U.S.C. § 102): Similar to other switch-related patents, this could anticipate aspects of Claim 1, particularly if the optical switch is a remote element whose configuration is managed.

28. US20020099669A1: Service level agreement / virtual private network templates

• Full Citation: US20020099669A1
• Publication/Filing Date: Filed January 25, 2001 / Published July 25, 2002
• Brief Description: This patent describes service level agreement / virtual private network templates.
• Potential Anticipation (35 U.S.C. § 102): Very relevant to Claim 1, particularly the generation of configuration data based on "parameters defining a contract." Service level agreement (SLA) templates would be a direct source for such parameters and their derivation into configuration. Also relevant to Claim 10.

29. US20050259571A1: Self-healing hierarchical network management system, and methods and apparatus therefor

• Full Citation: US20050259571A1
• Publication/Filing Date: Filed February 28, 2001 / Published November 24, 2005
• Brief Description: This patent describes a self-healing hierarchical network management system, and methods and apparatus therefor.
• Potential Anticipation (35 U.S.C. § 102): This patent is broadly relevant to the entire concept of a network management system as described in Claims 1, 5, and 9. The "self-healing" aspect might involve automated responses to status changes, similar to how NE hardware acts on control file contents.

30. US7181436B1: Automatically generating replication topology information for use by a directory service

• Full Citation: US7181436B1
• Publication/Filing Date: Filed March 20, 2001 / Published February 20, 2007
• Brief Description: This patent describes automatically generating replication topology information for use by a directory service.
• Potential Anticipation (35 U.S.C. § 102): This could be relevant to the directory structure used at the NMS file server (FIG. 2) and how NEs access their specific directories. The concept of "replication topology information" could apply to how the NMD files are organized and synchronized across the system.

31. US6807186B2: Architectures for a single-stage grooming switch

• Full Citation: US6807186B2
• Publication/Filing Date: Filed April 27, 2001 / Published October 19, 2004
• Brief Description: This patent describes architectures for a single-stage grooming switch.
• Potential Anticipation (35 U.S.C. § 102): Another example of a network element that would require configuration and monitoring, broadly relevant to Claims 1 and 5.

32. US6883084B1: Reconfigurable data path processor

• Full Citation: US6883084B1
• Publication/Filing Date: Filed July 25, 2001 / Published April 19, 2005
• Brief Description: This patent describes a reconfigurable data path processor.
• Potential Anticipation (35 U.S.C. § 102): This is highly relevant to Claim 3, which mentions "programmable hardware logic implementing a logic design" and "changing at least in part the logic design implemented by the programmable hardware logic." The concept of a "reconfigurable data path processor" directly anticipates this, especially if the reconfiguration is driven by configuration data.

33. US7349414B2: System and method for maximizing the traffic delivery capacity of packet transport networks via real-time traffic pattern based optimization of transport capacity allocation

• Full Citation: US7349414B2
• Publication/Filing Date: Filed August 24, 2001 / Published March 25, 2008
• Brief Description: This patent describes a system and method for maximizing traffic delivery capacity of packet transport networks via real-time traffic pattern based optimization of transport capacity allocation.
• Potential Anticipation (35 U.S.C. § 102): This is relevant to Claim 2 and Claim 13, which refer to controlling "processing of data received on a port of the NE, transmission of data on a port of the NE, or connection of data between ports of the NE." The optimization of transport capacity would involve such control.

34. US20030069959A1: Alarm lists synchronization in an alarm management system

• Full Citation: US20030069959A1
• Publication/Filing Date: Filed October 4, 2001 / Published April 10, 2003
• Brief Description: This patent describes alarm list synchronization in an alarm management system.
• Potential Anticipation (35 U.S.C. § 102): Directly relevant to Claim 5, especially the display of defect status and alarm notifications (claims 6-8), and the synchronization of status data.

35. US20030074430A1: Object oriented provisioning server object model

• Full Citation: US20030074430A1
• Publication/Filing Date: Filed October 5, 2001 / Published April 17, 2003
• Brief Description: This patent describes an object-oriented provisioning server object model.
• Potential Anticipation (35 U.S.C. § 102): "Provisioning" directly relates to configuring network elements (Claim 1). An "object-oriented provisioning server" could anticipate the NMS server's role in creating and managing configuration data.

36. US20030074429A1: Object oriented provisioning server

• Full Citation: US20030074429A1
• Publication/Filing Date: Filed October 5, 2001 / Published April 17, 2003
• Brief Description: This patent describes an object-oriented provisioning server.
• Potential Anticipation (35 U.S.C. § 102): Similar to US20030074430A1, this is relevant to the configuration and management aspects of Claim 1.

37. US20040133581A1: Database management system, data structure generating method for database management system, and storage medium therefor

• Full Citation: US20040133581A1
• Publication/Filing Date: Filed May 21, 2002 / Published July 8, 2004
• Brief Description: This patent describes a database management system, a data structure generating method, and a storage medium.
• Potential Anticipation (35 U.S.C. § 102): This is highly relevant to the "storage facility" for NMD files and the "logical directory structure" described in US10567474. It could anticipate how the configuration and status data (CD/SD) are stored and organized at the NMS server (Claims 1 and 5).

38. US20030225876A1: Method and apparatus for graphically depicting network performance and connectivity

• Full Citation: US20030225876A1
• Publication/Filing Date: Filed May 31, 2002 / Published December 4, 2003
• Brief Description: This patent describes a method and apparatus for graphically depicting network performance and connectivity.
• Potential Anticipation (35 U.S.C. § 102): This is relevant to the user interface aspects of Claims 1 and 5, particularly the display of network status. Graphical depiction of performance and connectivity could directly anticipate the "displaying ... status of defects" and "summarized representation" in Claim 5.

39. US7251690B2: Method and system for reporting status over a communications link

• Full Citation: US7251690B2
• Publication/Filing Date: Filed August 7, 2002 / Published July 31, 2007
• Brief Description: This patent describes a method and system for reporting status over a communications link.
• Potential Anticipation (35 U.S.C. § 102): Directly relevant to Claim 5, specifically the transfer of element-side copies of status data to the computer subsystem. The "reporting status over a communications link" aligns perfectly with the mechanism for transferring NE status files.

40. US20040064542A1: Method and system for reporting status over a communications link

• Full Citation: US20040064542A1
• Publication/Filing Date: Filed August 7, 2002 / Published April 1, 2004
• Brief Description: This patent describes a method and system for reporting status over a communications link.
• Potential Anticipation (35 U.S.C. § 102): Similar to US7251690B2, this is highly relevant to Claim 5 and the status data transfer in Claim 9 (second instance).

41. US20040042495A1: Dynamically channelizable packet transport network

• Full Citation: US20040042495A1
• Publication/Filing Date: Filed August 29, 2002 / Published March 4, 2004
• Brief Description: This patent describes a dynamically channelizable packet transport network.
• Potential Anticipation (35 U.S.C. § 102): This could be relevant to the operations performed by the digital logic in remote elements (Claim 1) and the control of data flow (Claim 2, Claim 13). "Dynamically channelizable" implies configurable network elements.

42. US20050102529A1: Mobility access gateway

• Full Citation: US20050102529A1
• Publication/Filing Date: Filed October 21, 2002 / Published May 12, 2005
• Brief Description: This patent describes a mobility access gateway.
• Potential Anticipation (35 U.S.C. § 102): An "access gateway" is a type of network element, so its management and configuration could anticipate aspects of Claims 1 and 5.

43. US20040139308A1: System and apparatus for eliminating user interaction during hardware configuration at system boot

• Full Citation: US20040139308A1
• Publication/Filing Date: Filed January 9, 2003 / Published July 15, 2004
• Brief Description: This patent describes a system and apparatus for eliminating user interaction during hardware configuration at system boot.
• Potential Anticipation (35 U.S.C. § 102): This is highly relevant to the "automatic consequences of the contents of the NMD files" and the "NE hardware automatically, without SW involvement, completes the network management actions" in US10567474. Specifically, it could anticipate elements of Claim 1, where element-side copies of CD drive hardware logic control registers. The "eliminating user interaction" and "automatic configuration" aspects are very strong.

44. US20050125492A1: Integrated network element management system and method

• Full Citation: US20050125492A1
• Publication/Filing Date: Filed December 5, 2003 / Published June 9, 2005
• Brief Description: This patent describes an integrated network element management system and method.
• Potential Anticipation (35 U.S.C. § 102): This title is broadly anticipatory of the entire system and method claims (1, 5, and 9) of US10567474, which describes a "network management system" for "managing NEs."

45. US7567585B2: Automatic change method of virtual concatenation bandwidth

• Full Citation: US7567585B2
• Publication/Filing Date: Filed December 18, 2003 / Published July 28, 2009
• Brief Description: This patent describes an automatic change method of virtual concatenation bandwidth.
• Potential Anticipation (35 U.S.C. § 102): This is relevant to the automatic operations performed by network elements (Claim 1) and could specifically relate to Claim 2 and Claim 13, which involve controlling communication data and port processing. "Automatic change method" aligns with the automatic nature of configuration changes in US10567474.

46. US20050154801A1: Programming system and method for a video network

• Full Citation: US20050154801A1
• Publication/Filing Date: Filed December 29, 2003 / Published July 14, 2005
• Brief Description: This patent describes a programming system and method for a video network.
• Potential Anticipation (35 U.S.C. § 102): The "programming system and method" could relate to the transfer of "NE program and control files" in Claim 1 and Claim 9. A video network would comprise network elements that need to be configured.

47. US20060029085A1: Methods and apparatus for information processing and display for network

• Full Citation: US20060029085A1
• Publication/Filing Date: Filed January 16, 2004 / Published February 9, 2006
• Brief Description: This patent describes methods and apparatus for information processing and display for a network.
• Potential Anticipation (35 U.S.C. § 102): This is relevant to the processing of status data and its display via the user interface in Claim 5.

48. US20070297350A1: Componentized Automatic Provisioning And Management Of Computing Environments For Computing Utilities

• Full Citation: US20070297350A1
• Publication/Filing Date: Filed January 30, 2004 / Published December 27, 2007
• Brief Description: This patent describes componentized automatic provisioning and management of computing environments for computing utilities.
• Potential Anticipation (35 U.S.C. § 102): "Automatic Provisioning And Management" is highly anticipatory of the core concepts in Claims 1 and 9, covering the configuration and management of remote elements/components.

49. US20060005228A1: Behavior model generator system for facilitating confirmation of intention of security policy creator

• Full Citation: US20060005228A1
• Publication/Filing Date: Filed June 18, 2004 / Published January 5, 2006
• Brief Description: This patent describes a behavior model generator system for facilitating confirmation of intention of a security policy creator.
• Potential Anticipation (35 U.S.C. § 102): While more abstract, the concept of defining policies and having them reflected in system behavior could relate to how service contract parameters drive configuration data in Claim 1.

50. US7664848B2: System and method for monitoring networked devices employing RSS functionality

• Full Citation: US7664848B2
• Publication/Filing Date: Filed June 2, 2005 / Published February 16, 2010
• Brief Description: This patent describes a system and method for monitoring networked devices employing RSS functionality.
• Potential Anticipation (35 U.S.C. § 102): Directly relevant to the monitoring aspects of Claim 5, especially the monitoring of remote elements ("networked devices").

51. US20060277291A1: System and method for monitoring networked devices employing RSS functionality

• Full Citation: US20060277291A1
• Publication/Filing Date: Filed June 2, 2005 / Published December 7, 2006
• Brief Description: This patent describes a system and method for monitoring networked devices employing RSS functionality.
• Potential Anticipation (35 U.S.C. § 102): Similar to US7664848B2, highly relevant to the monitoring aspects of Claim 5.

52. US20070156919A1: Enforcing network service level agreements in a network element

• Full Citation: US20070156919A1
• Publication/Filing Date: Filed June 21, 2005 / Published July 5, 2007
• Brief Description: This patent describes enforcing network service level agreements in a network element.
• Potential Anticipation (35 U.S.C. § 102): Highly relevant to Claim 1 and Claim 10, specifically the generation of configuration data based on "parameters defining a contract" and the actual implementation of those contracts at the network elements.

53. US8495244B2: System and method for dynamic automatic communication path selection, distributed device synchronization and task delegation

• Full Citation: US8495244B2
• Publication/Filing Date: Filed June 29, 2005 / Published July 23, 2013
• Brief Description: This patent describes a system and method for dynamic automatic communication path selection, distributed device synchronization, and task delegation.
• Potential Anticipation (35 U.S.C. § 102): "Distributed device synchronization" is highly relevant to the continuous synchronization of CD/SD between the NMS server and remote elements in Claims 1, 5, and 9. "Dynamic automatic communication path selection" could relate to the network interface.

54. US20070083668A1: Method and apparatus for facilitating network expansion

• Full Citation: US20070083668A1
• Publication/Filing Date: Filed October 7, 2005 / Published April 12, 2007
• Brief Description: This patent describes a method and apparatus for facilitating network expansion.
• Potential Anticipation (35 U.S.C. § 102): Network expansion would involve configuring and managing new network elements, thus broadly relevant to the systems and methods of US10567474.

55. US20070083628A1: Automated, transparent and secure system and method for remotely managing network elements

• Full Citation: US20070083628A1
• Publication/Filing Date: Filed October 11, 2005 / Published April 12, 2007
• Brief Description: This patent describes an automated, transparent, and secure system and method for remotely managing network elements.
• Potential Anticipation (35 U.S.C. § 102): The title of this patent is strikingly similar to the core concepts of US10567474, making it highly anticipatory of all independent claims (1, 5, 9). The "automated" and "remotely managing network elements" directly align with the invention.

56. US20080037553A1: Systems and methods for allocating bandwidth to ports in a computer network

• Full Citation: US20080037553A1
• Publication/Filing Date: Filed December 22, 2005 / Published February 14, 2008
• Brief Description: This patent describes systems and methods for allocating bandwidth to ports in a computer network.
• Potential Anticipation (35 U.S.C. § 102): This is relevant to Claim 2 and Claim 13, which involve controlling data processing and transmission on network element ports. Bandwidth allocation is a specific type of control over these operations.

57. US20070208840A1: Graphical user interface for network management

• Full Citation: US20070208840A1
• Publication/Filing Date: Filed March 3, 2006 / Published September 6, 2007
• Brief Description: This patent describes a graphical user interface for network management.
• Potential Anticipation (35 U.S.C. § 102): Directly relevant to the "user interface" (GUI) aspects of Claims 1 and 5, particularly the ability to access and display information to manage and monitor remote elements.

58. US20070239842A1: System and method for provisioning a remote resource for an electronic device

• Full Citation: US20070239842A1
• Publication/Filing Date: Filed March 31, 2006 / Published October 11, 2007
• Brief Description: This patent describes a system and method for provisioning a remote resource for an electronic device.
• Potential Anticipation (35 U.S.C. § 102): "Provisioning a remote resource" is highly similar to configuring a remote element in Claim 1 and the first instance of Claim 9.

59. US20080104247A1: Adaptive management of computing resources

• Full Citation: US20080104247A1
• Publication/Filing Date: Filed October 31, 2006 / Published May 1, 2008
• Brief Description: This patent describes adaptive management of computing resources.
• Potential Anticipation (35 U.S.C. § 102): This broadly relates to the management aspects of Claims 1 and 5, where network elements are a type of computing resource.

60. US20080117808A1: Automatic configuration of network elements based on service contract definitions

• Full Citation: US20080117808A1
• Publication/Filing Date: Filed November 16, 2006 / Published May 22, 2008
• Brief Description: This patent describes the automatic configuration of network elements based on service contract definitions.
• Potential Anticipation (35 U.S.C. § 102): This patent is extremely relevant and potentially highly anticipatory of Claim 1 and Claim 10. The concept of "automatic configuration of network elements based on service contract definitions" is a direct match for key elements of US10567474. It shares the same priority date as US10567474, indicating it's a closely related family member or divisional. This would likely be a significant piece of prior art for all claims dealing with configuration based on contracts.

61. US20080155424A1: Network element abstraction within a network management system

• Full Citation: US20080155424A1
• Publication/Filing Date: Filed December 22, 2006 / Published June 26, 2008
• Brief Description: This patent describes network element abstraction within a network management system.
• Potential Anticipation (35 U.S.C. § 102): This is relevant to the overall architecture and how the NMS interacts with various NEs (Claims 1, 5, 9). Abstraction layers could be present in the user interface or server-side processing to present NEs consistently.

62. US20100042639A1: Configuration file framework to support high availability schema based upon asynchronous checkpointing

• Full Citation: US20100042639A1
• Publication/Filing Date: Filed August 13, 2008 / Published February 18, 2010
• Brief Description: This patent describes a configuration file framework to support high availability schema based upon asynchronous checkpointing.
• Potential Anticipation (35 U.S.C. § 102): "Configuration file framework" is highly relevant to the NMD configuration files in US10567474. The "asynchronous checkpointing" could relate to the asynchronous file transfer routines. This could anticipate aspects of Claim 1 and the first instance of Claim 9.

63. US8452906B2: Communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network

• Full Citation: US8452906B2
• Publication/Filing Date: Filed October 27, 2008 / Published May 28, 2013
• Brief Description: This patent describes a communication protocol system and method for a distributed-architecture heating, ventilation and air conditioning network.
• Potential Anticipation (35 U.S.C. § 102): While in a different application domain (HVAC), the "distributed-architecture network" and "communication protocol system and method" could broadly relate to the system and method claims of US10567474, particularly the transfer of management data units.

64. US8495244B2: System and method for dynamic automatic communication path selection, distributed device synchronization and task delegation

• Full Citation: US8495244B2
• Publication/Filing Date: Filed June 29, 2005 / Published July 23, 2013
• Brief Description: This patent describes a system and method for dynamic automatic communication path selection, distributed device synchronization and task delegation.
• Potential Anticipation (35 U.S.C. § 102): As mentioned before (citation 53), "distributed device synchronization" is highly relevant to the continuous synchronization of CD/SD between the NMS server and remote elements in Claims 1, 5, and 9.

Obviousness Analysis under 35 U.S.C. § 103

This analysis identifies combinations of prior art references that would render the claims of US patent 10567474 obvious to a person having ordinary skill in the art (PHOSITA) at the time of the invention. The primary objective of US10567474 is to provide a "Direct binary file transfer based network management system free of messaging, commands and data format conversions," addressing the complexities and restrictions of conventional NMS messaging protocols.

The most relevant prior art for this analysis are the closely related patent applications by the same inventor, Mark Henrik Sandstrom, which are explicitly cited in the "Description" section of US10567474:

• US20070083628A1 (publication of U.S. application Ser. No. 11/245,974, filed Oct. 11, 2005, referred to as in US10567474).
• US20080117808A1 (publication of U.S. application Ser. No. 11/566,178, filed Dec. 1, 2006, claiming benefit of U.S. Provisional Application No. 60/866,208 filed Nov. 16, 2006, referred to as in US10567474).
• US20070130327A1 (publication of U.S. application Ser. No. 11/563,079, filed Nov. 24, 2006, referred to as in US10567474).

While US10567474 is a continuation of the family stemming from US11/566,178 (which published as US20080117808A1) and thus generally shares its priority date (Nov. 16, 2006) for common subject matter, US20070083628A1 (filed Oct. 11, 2005, published April 12, 2007) serves as independent prior art against any new subject matter introduced in US10567474 that is not fully supported by the earliest priority document. Furthermore, even if direct anticipation by one reference is not found, combining multiple related references by the same inventor to achieve a more comprehensive solution is a strong basis for obviousness.

Analysis of Independent Claim 1

Claim 1 of US10567474 describes an infrastructure management system involving remote elements, a computer subsystem, continuous synchronization of configuration data (CD) via file transfers, digital logic in remote elements performing operations based on CD, and automatic generation of CD from contract parameters. The user interface allows access to both the CD and the contract parameters.

Combination: US20070083628A1 in view of US20080117808A1.

Rationale:

• Core File Transfer NMS: US20070083628A1 explicitly teaches an "automated, transparent and secure system and method for remotely configuring, controlling and monitoring network elements" based on "direct, binary NMD file transfer" that "avoids the complexity and restrictions of intermediate messaging protocols or transaction languages and conversion agents." This covers the remote elements, computer subsystem (NMS server), storage media for CD (NMD files), user-accessible copies, continuous synchronization via periodic file transfers, and digital logic in NEs performing operations based on these files. It specifically mentions NE hardware automatically completing actions indicated by control files. The NMS GUI provides write and read access to control register values within these files.
• CD from Contract Parameters: US20080117808A1, titled "Automatic configuration of network elements based on service contract definitions," directly teaches that "NEs are configured based on service contract definitions. The NMS server can convert service contract definitions into appropriate configuration files..." This precisely addresses the automatic generation of user-accessible CD from contract parameters.
• GUI Access to Contract Parameters: Given the explicit teaching in US20080117808A1 of deriving configuration from service contracts, and US20070083628A1's disclosure of a GUI providing access to configuration files, a PHOSITA would be motivated to enable GUI access to the underlying contract parameters themselves. This would enhance the transparency and flexibility of the NMS, allowing direct management of the source of configuration data, a goal explicitly stated as a benefit in both the prior art and US10567474.

Analysis of Independent Claim 5

Claim 5 of US10567474 describes an infrastructure management system focused on monitoring, including remote elements with storage for status data (SD), digital logic producing SD, a computer subsystem holding user-accessible SD, and a user interface that displays defect status, including a summarized representation of active defects.

Combination: US20070083628A1 in view of US20070130327A1.

Rationale:

• Core File Transfer NMS for Status Data: US20070083628A1 teaches NEs copying "contents of their status register segments... via a type of NMD file referred to as NE status file over a network 3 to their associated directories at the NMS server 7" for storage. It states that "the NE HW automatically maintains and updates a set of NE status parameters" and NE SW reads this to a status file that is copied to the server. The NMS GUI then displays "NE status data... based on the contents of the latest NE status file." This covers the remote elements, storage for SD, digital logic producing SD, computer subsystem with storage for user-accessible SD, and network interface for transferring SD to maintain synchronization.
• Display of Defects and Summarized Representation: US20070083628A1 mentions that the NMS GUI "displays notifications of significant events in the network such as NE alarm activations according to principles per referenced applications and." Reference is US20070130327A1, titled "Intelligent Network Alarm Status Monitoring." This patent explicitly describes a system for "monitoring the alarm status of a plurality of network elements" and the NMS "automatically detects and displays the alarm status of the NEs." A PHOSITA would find it obvious to integrate the detailed defect status display and summarization (e.g., indicating "at least one active defect") from US20070130327A1 into the GUI of the file-transfer-based NMS described in US20070083628A1. Such a feature is a standard and expected enhancement for any comprehensive alarm monitoring system.

Analysis of Independent Claim 9

Claim 9 of US10567474 describes a method for interaction between system components over a wide area network using management data units, where an information field indicates an action. It covers two instances: (1) computer subsystem to remote element for configuration (action at remote element from configuration file), and (2) remote element to computer subsystem for status (action at computer subsystem from status file). The data is user-accessible for remote management.

Combination: US20070083628A1.

Rationale:
US20070083628A1 fully teaches all limitations of Claim 9:

• System Components and Network: It describes an NMS server and NEs interacting over a network.
• Producing and Transferring Management Data Units: It teaches users producing configuration files at the NMS server, and NEs producing status files. Both are transferred as "NMD files" (management data units) to maintain synchronization.
• Action Indication and Performance: Control files (from server to NE) indicate NMS operations, which the NE hardware automatically completes. Status files (from NE to server) lead to the NMS software displaying status data and alarm notifications to the user. This covers the "certain information field whose contents are used to indicate an action" and the "performing the action."
• Configuration and Status File Segments: It details directory structures at both the NMS server (for program, control, and status files) and the NE's local memory (program, control, and status register segments). It explicitly states that "the phrase status NE status file herein shall include the contents of both the NE control and status registers."
• First Instance (Computer Subsystem to Remote Element): The user produces configuration files at the NMS server, which the NE copies and then autonomously completes the indicated NMS operations. This matches the action at the remote element based on the configuration file.
• Second Instance (Remote Element to Computer Subsystem): The NE copies its status registers via a status file to the NMS server, and the NMS software then displays this data via the GUI. This matches the action at the computer subsystem based on the status file.
• User Accessibility for Remote Management: The NMS GUI provides "write and read access to control register values within the NE control files" and "read access to the NE status files" at the server, enabling remote management.

Motivation to Combine References

A PHOSITA would have been highly motivated to combine the teachings of US20070083628A1, US20080117808A1, and US20070130327A1. All three references are by the same inventor, Mark Henrik Sandstrom, and clearly address a unified problem space: developing a more efficient, flexible, and transparent network management system that overcomes the limitations of conventional messaging-based approaches.

The motivation stems from the desire to build a comprehensive NMS solution that incorporates:

1. Efficient Communication: The foundational direct binary file transfer mechanism for NMD, as taught by US20070083628A1.
2. Automated Configuration: The ability to automatically derive configuration data from high-level service contract definitions, as taught by US20080117808A1, integrating business logic directly into network element configuration.
3. Intelligent Monitoring: The sophisticated alarm and defect status monitoring capabilities described in US20070130327A1, ensuring effective fault detection and reporting within the file-transfer NMS framework.

These references are not disparate pieces of prior art; rather, they represent complementary components of a coherent strategy for network management improvement. A PHOSITA would recognize the benefits of integrating these functionalities into a single, robust system to achieve the "streamlined network management communications, providing more intuitive, transparent and flexible operational capabilities with architecturally improved scalability, reliability and performance" that US10567474 aims to provide, thereby rendering the claimed subject matter obvious.