# US 2025/0158893 A1 · Network monitoring system and method including software agents

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0158893 A1
- Document ID: US20250158893A1
- Status: Published application
- Kind: A1
- Application number: 18/508,414
- Filed: 2023-11-14
- Published: 2025-05-15
- Earliest claimed: 2023-11-14
- Assignees: Nozomi Networks Sagl
- Applicants: Nozomi Networks Sagl
- Inventors: Alessandro CAVALLARO CORTI
- Web page: https://patentgrep.com/patent/US20250158893A1

## CPC

- H04L 41/145: {involving simulating, designing, planning or modelling of a network}
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 41/12: Discovery or management of network topologies
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 43/028: by filtering
- H04L 43/045: for graphical visualisation of monitoring data
- H04L 43/12: Network monitoring probes
- H04L 45/74: Address processing for routing
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 43/067: using time frame reporting
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Network monitoring system (100) comprising: a communication network (NT) comprising a plurality of nodes (N1-NN) and a plurality of node connections (E1-EP); wherein each node comprises an asset (AS1-ASF) configured to receive/transmit packets; a plurality of software agents (AG1-AGN) each installed in at least part of said plurality of nodes; each software agent being configured to redirect packets from a respective asset; at least one monitoring computer (CS) provided with software resources configured to: receive the packets sent by each software agent (AG1-AGN); extract from said packets source addresses and destination addresses; identify the plurality of nodes (N1-NN) and the plurality of node connections (E1-EP) from said source and destination addresses and associate each node to a corresponding node identifier; constructing an abstract model (200) representing said communication network (NT), wherein each node is represented by the corresponding node identifier and each node connection is represented by a corresponding link between respective nodes.

## Claims

### Claim 1

Network monitoring system comprising:
a communication network comprising a plurality of nodes and a plurality of node connections; wherein each node comprises an asset configured to receive/transmit packets;
a plurality of software agents each installed in at least part of said plurality of nodes; each software agent being configured to redirect packets from a respective asset;
at least one monitoring computer provided with software resources configured to:
receive the packets sent by each software agent;
extract from said packets source addresses and destination addresses;
identify the plurality of nodes and the plurality of node connections from said source and destination addresses and associate each node to a corresponding node identifier;
constructing an abstract model representing said communication network, wherein each node is represented by the corresponding node identifier and each node connection is represented by a corresponding link between respective nodes.

### Claim 2 (depends on 1)

Network monitoring system according to claim 1, wherein said software resources are part of a cloud computing service.

### Claim 3 (depends on 1)

Network monitoring system according to claim 1, wherein said software resources are configured to construct the abstract model under the form of a displayable topological graph.

### Claim 4 (depends on 1)

Network monitoring system according to claim 1, wherein said software resources are configured so as said source addresses and destination addresses include addresses of the network layer from which the software resources are configured to identify links between nodes.

### Claim 5 (depends on 1)

Network monitoring system according to claim 1, wherein said software resources are configured so as said source addresses and destination addresses include addresses of the physical layer from which the software resources are configured to identify links between nodes.

### Claim 6 (depends on 1)

Network monitoring system according to claim 1, wherein said software resources have Deep Packet Inspection capabilities.

### Claim 7 (depends on 1)

Network monitoring system according to claim 1, wherein:
the plurality of nodes is associated to a managing entity;
the communication network further includes at least one public network device.

### Claim 8 (depends on 1)

Network monitoring system according to claim 1, wherein a first node of said plurality of nodes includes a first asset comprising a computer running any version of Windows, Linux or macOS.

### Claim 9 (depends on 1)

Network monitoring system according to claim 1, wherein said plurality of software agents is configured to operate as packet sniffers.

### Claim 10 (depends on 9)

Network monitoring system according to claim 9, wherein said plurality of software agents is configured to operate as packet sniffers and extract from said packet at least one of the following technical information relating to each asset: host label, operating system version, firmware version in case of an Operation Technology device, Central Processing Unit usage, RAM Random Access Memory usage, disk usage, installed software.

### Claim 11 (depends on 10)

Network monitoring system according to claim 10, wherein the plurality of software agents is configured to associate to the technical information relating to each asset a timestamp representing an extraction time.

### Claim 12 (depends on 11)

Network monitoring system according to claim 11, wherein said software resources are configured to:
perform a merging process by processing the technical information received by the plurality of software agents;
associate to each node of the abstract model a corresponding technical information relating to the corresponding asset.

### Claim 13 (depends on 12)

Network monitoring system according to claim 12, wherein said software resources are configured to:
receive from a first software agent a first value assumed by a technical information key; the first value being associated with a first timestamp value and related to a selected node;
receive from a second software agent a second value assumed by said technical information key; the second value being associated with a second timestamp value and related to said selected node;
selectively associate to the abstract model the first value and the second value depending on said first and second timestamp values.

### Claim 14 (depends on 1)

Network monitoring system according to claim 1, wherein said software resource and/or said plurality of agents are configured to perform anomaly detection.

### Claim 15

Network monitoring method comprising:
accessing a communication network comprising a plurality of nodes and a plurality of node connections; wherein each node comprises an asset configured to receive/transmit packets;
providing a plurality of software agents each installed in at least part of said plurality of nodes; each software agent being configured to redirect packets from a respective asset;
providing at least one monitoring computer having software resources configured to:
receive the packets sent by each software agent;
extract from said packets source addresses and destination addresses;
identify the plurality of nodes and the plurality of node connections from said source and destination addresses and associate each node to a corresponding node identifier;
constructing an abstract model representing said communication network, wherein each node is represented by the corresponding node identifier and each node connection is represented by a corresponding link between respective nodes.

### Claim 16 (depends on 4)

Network monitoring system, according to claim 4, wherein said software resources are configured so as said source addresses and destination addresses include addresses of the physical layer from which the software resources are configured to identify links between nodes.
