# US 2026/0222171 A1 · Clock synchronization between networked devices based on packet congestion information

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

- Number: US 2026/0222171 A1
- Document ID: US20260222171A1
- Status: Published application
- Kind: A1
- Application number: 19/629,230
- Filed: 2026-03-26
- Published: 2026-07-30
- Earliest claimed: 2023-07-10
- Assignees: Mellanox Technologies, Ltd.
- Applicants: Mellanox Technologies, Ltd.
- Inventors: Wojciech Wasko; Dotan David Levi; Thomas Kernen
- Web page: https://patentgrep.com/patent/US20260222171A1

## CPC

- H04J 3/0673: {using intermediate nodes, e.g. modification of a received timestamp before further transmission to the next packet node, e.g. including internal delay time or residence time into the packet}
- H04L 7/0033: {Correction by delay}
- H04J 3/0664: {unidirectional timestamps}
- H04L 7/0079: {Receiver details}
- H04L 47/10: Flow control; Congestion control
- H04J 3/0667: {Bidirectional timestamps, e.g. NTP or PTP for compensation of clock drift and for compensation of propagation delays (arrangements for monitoring round trip delays in packet switching networks H04L43/0864)}
- H04J: MULTIPLEX COMMUNICATION (transmission in general H04B; peculiar to transmission of digital information H04L5/00; systems for the simultaneous or sequential transmission of more than one television signal H04N7/08; in exchanges H04Q11/00; stereophonic systems H04S)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A network device includes control logic coupled to a receiver. The network device receives, via the receiver, a packet from a second network device over a network, wherein the packet is associated with clock synchronization between the network device and the second network device. The network device determines that a congestion indicator of the packet is asserted, indicating that the packet has incurred congestion traversing the network and adjust, based on an assertion of the congestion indicator, a weight applied to timestamps associated with the packet in performing clock synchronization with the second network device.

## Claims

### Claim 1

A network device comprising:
control logic coupled to a receiver and configured to:
receive, via the receiver, a packet from a second network device over a network, wherein the packet is associated with clock synchronization between the network device and the second network device;
determine that a congestion indicator of the packet is asserted, indicating that the packet has incurred congestion traversing the network; and
adjust, based on an assertion of the congestion indicator, a weight applied to timestamps associated with the packet in performing clock synchronization with the second network device.

### Claim 2 (depends on 1)

The network device of claim 1, wherein the congestion indicator comprises a bit of a congestion notification field of the packet.

### Claim 3 (depends on 1)

The network device of claim 1, wherein the congestion indicator comprises information within a type-length-value (TLV) field that indicates the packet has incurred congestion.

### Claim 4 (depends on 1)

The network device of claim 1, wherein to adjust the weight, the control logic is configured to reduce the weight based on the assertion of the congestion indicator.

### Claim 5 (depends on 1)

The network device of claim 1, further comprising a local clock source coupled to the control logic, wherein the control logic is further configured to:
estimate a local clock error based on a period of time since a last synchronization of the local clock source and a known accuracy metric value of the local clock source; and
apply no weight to the timestamps in synchronizing the local clock source in response to determining that the local clock error is less than or equal to a maximum congestion error for the network.

### Claim 6 (depends on 1)

The network device of claim 1, wherein the control logic is further configured to, in response to a congestion indicator of a second packet being unasserted, apply a full weight to timestamps associated with the second packet in performing clock synchronization with the second network device.

### Claim 7 (depends on 1)

The network device of claim 1, wherein the network is established with communication devices capable of sending explicit congestion notifications.

### Claim 8

A method comprising:
receiving, by a first network device, a plurality of packets from a second network device, wherein each packet of the plurality of packets is associated with clock synchronization between the first network device and the second network device;
determining, for each packet of the plurality of packets, whether a congestion indicator of the packet is asserted, indicating that the packet has incurred congestion traversing a network;
identifying, based on the determining, which packets of the plurality of packets were affected by congestion; and
adjusting a weight applied to timestamps associated with the identified packets in performing clock synchronization with the second network device.

### Claim 9 (depends on 8)

The method of claim 8, wherein adjusting the weight comprises applying no weight to timestamps associated with the identified packets.

### Claim 10 (depends on 8)

The method of claim 8, wherein adjusting the weight comprises applying a reduced weight to timestamps associated with the identified packets.

### Claim 11 (depends on 8)

The method of claim 8, further comprising applying a full weight to timestamps associated with packets of the plurality of packets that were not affected by congestion.

### Claim 12 (depends on 8)

The method of claim 8, wherein the congestion indicator comprises a bit of a congestion notification field.

### Claim 13 (depends on 8)

The method of claim 8, further comprising synchronizing a local clock source of the first network device to a clock source of the second network device based on the adjusted weight applied to the timestamps associated with the identified packets.

### Claim 14 (depends on 8)

The method of claim 8, further comprising estimating a local clock error based on a period of time since a last synchronization of a local clock source and a known accuracy metric value of the local clock source of the first network device, wherein adjusting the weight is further based on the local clock error.

### Claim 15

A method comprising:
receiving, by a first network device, a synchronization packet from a second network device, wherein the synchronization packet is associated with a first timestamp and a second timestamp;
determining that a congestion indicator of the synchronization packet is asserted, indicating the synchronization packet has incurred congestion traversing a network;
determining a clock offset estimation error based on the congestion;
determining a local clock error of a local clock source of the first network device based on a period of time since a last synchronization of the local clock source and a drift rate of the local clock source;
comparing the clock offset estimation error to the local clock error; and
adjusting a weight applied to the first timestamp and the second timestamp based on the comparing.

### Claim 16 (depends on 15)

The method of claim 15, wherein adjusting the weight comprises reducing the weight in response to the clock offset estimation error being greater than the local clock error.

### Claim 17 (depends on 15)

The method of claim 15, wherein adjusting the weight comprises applying no weight to the first timestamp and the second timestamp in response to the local clock error being less than or equal to a maximum congestion error for the network.

### Claim 18 (depends on 15)

The method of claim 15, wherein the congestion indicator comprises a bit of a congestion notification field of the synchronization packet.

### Claim 19 (depends on 15)

The method of claim 15, wherein the drift rate comprises a known accuracy metric value of the local clock source.

### Claim 20 (depends on 15)

The method of claim 15, further comprising synchronizing the local clock source to a clock source of the second network device based on the adjusted weight applied to the first timestamp and the second timestamp.
