Network Device Timestamping for Multiple Synchronization Domains

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Network devices with multiple synchronization domains face challenges in implementing timestamping at network interfaces due to the need to provide multiple clocks, which increases communication complexity, cost, power consumption, and physical size, as they must determine the synchronization domain and select the appropriate clock for timestamping.

Innovation Solution

A network device processes timing packets by using a local-domain clock to generate a domain-specific timestamp, accounting for internal delays, allowing for accurate timestamping across multiple synchronization domains without requiring each network interface to operate with multiple domain-specific clocks, thus reducing internal communication demands and costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple clocks are provided to each network interface for timestamping in multiple synchronization domains, then the network device can perform accurate timestamping across multiple domains, but the device complexity and internal communication requirements increase

Engineering Contradiction:

Improvemulti-domain timestamping capabilityVSAvoidinternal communication complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the timestamping function by separating domain-specific timestamp generation (handled by the packet processor using domain-specific clocks) from local-domain timestamp generation (handled by the network interface using a shared local-domain clock). This segmentation allows each component to work with a single clock source, reducing internal communication complexity while maintaining multi-domain capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The packet processor acts as an intermediary between the network interface and the domain-specific clocks. It receives packets with local-domain timestamps from the network interface, converts them to domain-specific timestamps using the appropriate domain-specific clock, and then processes them further. This intermediary approach eliminates the need to provide multiple clocks directly to each network interface.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

Engineering Contradiction:

Improvemulti-domain timestamping capabilityVSAvoidpower consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the clock distribution architecture by providing only one local-domain clock to each network interface instead of multiple domain-specific clocks. The packet processor separately manages domain-specific timestamps using domain-specific clocks, but the network interface itself only needs to handle a single clock source, significantly reducing power consumption.

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

Engineering Contradiction:

Improvemulti-domain timestamping capabilityVSAvoidphysical size

Core Design Contradiction:

Adaptability or versatilityVSVolume of moving object

Solution Approach 1:

The patent segments the timestamping responsibilities so that network interfaces only need to accommodate a single local-domain clock signal rather than multiple domain-specific clock signals. This reduces the number of clock distribution lines and components at each network interface, thereby reducing the physical size of the network device.

Inventive Principle:

Principle #1Segmentation

4Adaptability or versatility

If network interfaces are configured with capabilities to perform timestamping in multiple synchronization domains, then the network device can support multiple domains, but the network interface complexity increases

Engineering Contradiction:

Improvemulti-domain timestamping capabilityVSAvoidnetwork interface complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The packet processor serves as an intermediary that handles the complexity of domain-specific timestamp conversion. Network interfaces only need to implement simple local-domain timestamping using a single clock source. The complex conversion from local-domain timestamps to domain-specific timestamps is performed by the packet processor, which selects and applies the appropriate domain-specific clock based on packet characteristics.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12160309B1Timestamping for multiple synchronization domains in a network device

Publication Date: 2024.12.03 MARVELL ISRAEL (M L S L) LTD

AI summary

A packet processor of a network device receives a packet and a local-domain timestamp generated for the packet at a network interface of the network device based on a local-domain clock maintained by the network device. The packet processor generates a domain-specific timestamp for the packet based on a domain-specific clock maintained by the network device, and determines a delay value using the local-domain clock. The delay value accounts for a time delay experienced by the packet between a time at which the local-domain timestamp was generated at the network interface and a time, according to the local-domain clock, at which the domain-specific timestamp is generated by the packet processor. The packet processor adjusts the domain-specific timestamp based on the delay value to generate an adjusted domain-specific timestamp for the packet, and performs at least one synchronization operation using the adjusted domain-specific timestamp.