# US 2020/0404080 A1 · Inferring Client-Server Relations for UDP Connections

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

- Number: US 2020/0404080 A1
- Document ID: US20200404080A1
- Status: Published application
- Kind: A1
- Application number: 16/449,468
- Filed: 2019-06-24
- Published: 2020-12-24
- Earliest claimed: 2019-06-24
- Assignees: Guardicore Ltd.
- Applicants: Guardicore Ltd.
- Inventors: Uri Hershcovits; Liron Schiff; Itamar Tal
- Web page: https://patentgrep.com/patent/US20200404080A1

## CPC

- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- G06F 9/54: Interprogram communication
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- G06F 11/3051: {Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs (verification or detection of system hardware configuration G06F11/2247)}
- G06F 11/3096: {wherein the means or processing minimize the use of computing system or of computing system component resources, e.g. non-intrusive monitoring which minimizes the probe effect: sniffing, intercepting, indirectly deriving the monitored data from other directly available data}
- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 43/065: related to network devices
- H04L 43/18: Protocol analysers
- H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
- H04L 47/2483: involving identification of individual flows
- H04L 69/164: Adaptation or special uses of UDP protocol
- G06F 2209/541: Client-server
- H04L 43/04: Processing captured monitoring data, e.g. for logfile generation
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for monitoring a computing system including multiple endpoints, includes monitoring, in at least some of the endpoints, operating-system (OS) system calls relating to a transport protocol having no handshake mechanism. First and second endpoints, which exchange a flow of packets with one another using the transport protocol, are identified from among the multiple endpoints. A deduction is made, from the monitored system calls, which of the first and second endpoints acts as a server in the flow of packets, and which of the first and second endpoints acts as a client in the flow of packets.

## Claims

### Claim 1

A method for monitoring a computing system comprising multiple endpoints, the method comprising:
monitoring, in at least some of the endpoints,
operating-system (OS) system calls relating to a transport protocol having no handshake mechanism;
identifying, from among the multiple endpoints, first and second endpoints that exchange a flow of packets with one another using the transport protocol; and
deducing, from the monitored system calls, which of the first and second endpoints acts as a server in the flow of packets, and which of the first and second endpoints acts as a client in the flow of packets.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the transport protocol comprises a User Datagram Protocol (UDP).

### Claim 3 (depends on 1)

The method according to claim 1, further comprising identifying, based on the monitored system calls, at least one process in at least one of the first and second endpoints that is associated with the flow of packets.

### Claim 4 (depends on 1)

The method according to claim 1, wherein monitoring the OS system calls comprises monitoring in the first and second endpoints (i) system calls that create network sockets and (ii) system calls that perform initial communication transactions occurring after the creation of the respective network sockets.

### Claim 5 (depends on 1)

The method according to claim 1, wherein deducing which of the endpoints acts as a server and which of the endpoints acts as a client comprises:
identifying (i) creation of a network socket for the flow of packets in the first endpoint, and (ii) an initial communication transaction occurring in the first endpoint after the creation of the network socket;
if the initial communication transaction is a write transaction, deducing that the first endpoint acts as a client; and
if the initial communication transaction is a read transaction, deducing that the first endpoint acts as a server.

### Claim 6 (depends on 1)

The method according to claim 1, wherein identifying the first and second endpoints comprises identifying a matching flow tuple in the first and second endpoints.

### Claim 7 (depends on 1)

The method according to claim 1, wherein deducing which of the endpoints acts as a server and which of the endpoints acts as a client comprises:
if memory addresses, which were allocated from a memory pool in the first endpoint for send operations, are closer to a base address of the memory pool than the memory addresses allocated for receive operations, deducing that the first endpoint acts as a client; and
if the memory addresses, which were allocated for the receive operations, are closer to the base address than the memory addresses allocated for the send operations, deducing that the first endpoint acts as a server.

### Claim 8 (depends on 1)

The method according to claim 1, wherein deducing which of the endpoints acts as a server and which of the endpoints acts as a client comprises deducing that the first endpoint acts as a client in response to assessing that a port assigned to the flow of packets in the first endpoint is an ephemeral port.

### Claim 9 (depends on 1)

The method according to claim 1, wherein deducing which of the endpoints acts as a server and which of the endpoints acts as a client comprises deducing that the first endpoint acts as a server in response to assessing that a port assigned to the flow of packets in the first endpoint is also assigned in one or more additional flows of packets.

### Claim 10 (depends on 1)

The method according to claim 1, wherein deducing which of the endpoints acts as a server and which of the endpoints acts as a client comprises identifying, in at least one of the endpoints, a configuration of a port as a server port.

### Claim 11 (depends on 1)

The method according to claim 1, wherein deducing which of the endpoints acts as a server and which of the endpoints acts as a client comprises analyzing a temporal pattern of the OS system calls.

### Claim 12

An apparatus for monitoring a computing system comprising multiple endpoints, the apparatus comprising:
an interface, configured to receive, from at least some of the endpoints, monitored operating-system (OS) system calls relating to a transport protocol having no handshake mechanism; and
a processor, configured to identify, from among the multiple endpoints, first and second endpoints that exchange a flow of packets with one another using the transport protocol, and to deduce, from the monitored system calls, which of the first and second endpoints acts as a server in the flow of packets, and which of the first and second endpoints acts as a client in the flow of packets.

### Claim 13 (depends on 12)

The apparatus according to claim 12, wherein the transport protocol comprises a User Datagram Protocol (UDP).

### Claim 14 (depends on 12)

The apparatus according to claim 12, wherein the processor is further configured to identify, based on the monitored system calls, at least one process in at least one of the first and second endpoints that is associated with the flow of packets.

### Claim 15 (depends on 12)

The apparatus according to claim 12, wherein the processor is configured to monitor in the first and second endpoints (i) system calls that create network sockets and (ii) system calls that perform initial communication transactions occurring after the creation of the respective network sockets.

### Claim 16 (depends on 12)

The apparatus according to claim 12, wherein the processor is configured to:
identify (i) creation of a network socket for the flow of packets in the first endpoint, and (ii) an initial communication transaction occurring in the first endpoint after the creation of the network socket;
if the initial communication transaction is a write transaction, deduce that the first endpoint acts as a client; and
if the initial communication transaction is a read transaction, deduce that the first endpoint acts as a server.

### Claim 17 (depends on 12)

The apparatus according to claim 12, wherein the processor is configured to identify the first and second endpoints by identifying a matching flow tuple in the first and second endpoints.

### Claim 18 (depends on 12)

The apparatus according to claim 12, wherein the processor is configured to:
if memory addresses, which were allocated from a memory pool in the first endpoint for send operations, are closer to a base address of the memory pool than the memory addresses allocated for receive operations, deduce that the first endpoint acts as a client; and
if the memory addresses, which were allocated for the receive operations, are closer to the base address than the memory addresses allocated for the send operations, deduce that the first endpoint acts as a server.

### Claim 19 (depends on 12)

The apparatus according to claim 12, wherein the processor is configured to deduce that the first endpoint acts as a client in response to assessing that a port assigned to the flow of packets in the first endpoint is an ephemeral port.

### Claim 20 (depends on 12)

The apparatus according to claim 12, wherein the processor is configured to deduce that the first endpoint acts as a server in response to assessing that a port assigned to the flow of packets in the first endpoint is also assigned in one or more additional flows of packets.

### Claim 21 (depends on 12)

The apparatus according to claim 12, wherein the processor is configured to deduce which of the endpoints acts as a server and which of the endpoints acts as a client by identifying, in at least one of the endpoints, a configuration of a port as a server port.

### Claim 22 (depends on 12)

The apparatus according to claim 12, wherein the processor is configured to deduce which of the endpoints acts as a server and which of the endpoints acts as a client by analyzing a temporal pattern of the OS system calls.
