Clock Domain Management for Circuit Emulation Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In high-speed computing networks, maintaining minimal data loss and packet drop during data traffic across multiple communication networks is challenging due to CES circuits being clocked at different reference clocks, requiring manual assignment of clock domains by network administrators.

Innovation Solution

An apparatus and method for managing clock domains that automatically selects and adjusts clock domains based on traffic buffer usage rates, using a process that stores data streams in a traffic buffer, monitors buffer capacity, and replaces clock domains as needed to ensure optimal timing for CES data packets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual clock domain assignment is used, then network administrators can control timing domains, but operational complexity increases and automation is reduced

Engineering Contradiction:
Improveclock domain assignment operationVSAvoidclock domain assignment automation
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The system automatically monitors buffer usage rates and selects appropriate clock domains without requiring manual administrator intervention. The clock domain management process self-adjusts based on real-time traffic conditions, eliminating the need for manual clock domain assignment while reducing operational complexity.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If multiple clock domains are used to handle different timing requirements, then network adaptability improves, but device complexity increases

Engineering Contradiction:
Improvenetwork timing domain adaptabilityVSAvoidclock domain management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system dynamically selects and switches between different clock domains based on real-time buffer usage monitoring. Instead of having static clock domain configurations, the system adapts its timing domain selection dynamically according to traffic conditions, improving network adaptability while managing complexity through automated decision-making.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The clock domain management process continuously monitors buffer usage rates and uses this feedback to determine when to switch between different clock domains. This closed-loop feedback mechanism enables the system to adapt to changing network conditions automatically, handling multiple timing requirements without proportionally increasing operational complexity.

Inventive Principle:
Principle #23Feedback

3Reliability

If buffer capacity is increased to reduce packet drop, then data loss decreases, but storage resources are consumed

Engineering Contradiction:
Improvedata loss rateVSAvoidbuffer storage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system changes the operational parameters of different clock domains to optimize buffer usage. By adjusting timing parameters and clock frequencies, the system can achieve better data flow synchronization, reducing packet drop without requiring proportionally larger buffer capacity, thus maintaining reliability while conserving storage resources.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8416813B1Methods and apparatus for clocking domain discovery in multi-domain networks
Publication Date: 2013.04.09 TELLABS OPERATIONS
  • US8416813B1 patent drawing
  • US8416813B1 patent drawing
  • US8416813B1 patent drawing

AI summary

An apparatus and method for managing clock domain(s) crossing several communication networks are disclosed. In one embodiment, a process capable of managing clock domains receives a data stream over a circuit emulation service (“CES”). Upon storing the data stream in a traffic buffer, the process selects a first clock domain for processing the data stream in the traffic buffer. For example, the process is capable of using the first clock domain to process and/or empty a jitter buffer, which stores CES data packets. The traffic buffer is monitored and the first clock domain can be replaced with a second clock domain if the storage capacity of the traffic buffer indicates that a different clock domain is needed.