The present invention relates to computer systems, and in particular, but not exclusively to, syntonization of computer devices.
Clock synchronization among network devices is used in many network applications. One application of using a synchronized clock value is for measuring one-way latency from one device to another device. If the clocks are not synchronized the resulting one-way latency measurement will be inaccurate.
Synchronization is typically achieved by syntonization, in which the clock frequency of two devices is aligned, and aligning offset and phase between the two devices.
For Ethernet, there are two complementary methods to achieve synchronization. One is Synchronous Ethernet (SyncE), which is a physical-layer protocol which achieves syntonization based on the receive/transmit symbol rate. SyncE is an International Telecommunication Union Telecommunication (ITU-T) Standardization Sector standard for computer networking that facilitates the transference of clock signals over the Ethernet physical layer. In particular, SyncE enables clock syntonization inside a network with respect to a master clock.
The other is Precision Time Protocol (PTP), which is a packet-based protocol that may be used with SyncE to align offset (e.g., in Coordinated Universal Time (UTC) format) and phase between two clocks. It should be noted that PTP may be used alone over Ethernet (without SyncE), but this is typically used for lower accuracy use cases. PTP is used to synchronize clocks throughout a computer network, and is considered to be the de-facto standard for this purpose.
Time, clock and frequency synchronization is crucial in some modern computer network applications. It enables 5G and 6G networks, and is proven to enhance the performance of data center workloads.
There is provided in accordance with an embodiment of the present disclosure, a clock syntonization system, including a first compute node including a first physical hardware clock to operate at a first clock frequency, a second compute node, and an interconnect data bus to transfer data from the first compute node at a data rate indicative of the first clock frequency of the first physical hardware clock, and wherein the second compute node includes clock synchronization circuitry to derive a second clock frequency from the data rate of the transferred data, and provide a clock signal at the derived second clock frequency.
Further in accordance with an embodiment of the present disclosure the first compute and second compute node may include any one or more of the following a central processing unit, a graphics processing unit, a network interface controller, a switch, a bridge, and a data processing unit.
Still further in accordance with an embodiment of the present disclosure the interconnect data bus is a peripheral device interconnect data bus.
Additionally in accordance with an embodiment of the present disclosure the data is transferred over the interconnect data bus in at least one digital signal.
Moreover, in accordance with an embodiment of the present disclosure the second compute node includes a second physical hardware clock to operate at a third clock frequency, the clock synchronization circuitry being configured to discipline the second physical hardware clock responsively to a difference between the derived second clock frequency and the third clock frequency.
Further in accordance with an embodiment of the present disclosure the second compute node includes a second physical hardware clock, the clock synchronization circuitry being configured to discipline the second physical hardware clock responsively to a difference between the derived second clock frequency and a transmission rate at which data is transferred from the second compute node to the first compute node via the interconnect data bus.
Still further in accordance with an embodiment of the present disclosure the second compute node includes a second physical hardware clock, the clock synchronization circuitry being configured to discipline the second physical hardware clock of the second compute node responsively to a difference between the data rate at which the data is received from the first compute node by the second compute node, and a transmission rate at which data is transferred from the second compute node to the first compute node via the interconnect data bus.
Additionally in accordance with an embodiment of the present disclosure the data rate is modulated to spread interference across a range of frequencies so that a variation of the data rate overtime describes a modulated signal of frequency against time.
Moreover, in accordance with an embodiment of the present disclosure the clock synchronization circuitry includes filtering circuitry to remove modulation from the modulated signal, the clock synchronization circuitry being configured to derive the second clock frequency from the modulated signal with the modulation removed.
Further in accordance with an embodiment of the present disclosure the clock synchronization circuitry includes filtering circuitry to digitally remove modulation from the modulated signal, the clock synchronization circuitry being configured to derive the second clock frequency from the modulated signal with the modulation removed.
Still further in accordance with an embodiment of the present disclosure the clock synchronization circuitry includes filtering circuitry to transform the modulated signal yielding a Fourier Transform, and identify the second clock frequency from the Fourier Transform.
Additionally in accordance with an embodiment of the present disclosure the clock synchronization circuitry is configured to sample the frequency of the modulated signal yielding multiple frequency values, average the frequency values yielding an average value, and derive the second clock frequency from the average value.
Moreover, in accordance with an embodiment of the present disclosure the clock synchronization circuitry is configured to derive the second clock frequency by fitting parameters of a mathematic model of the modulated signal, the parameters including a frequency based on the first clock frequency.
Further in accordance with an embodiment of the present disclosure the clock synchronization circuitry is configured to fit the parameters based on performing a regression analysis of the mathematical model.
Still further in accordance with an embodiment of the present disclosure the clock synchronization circuitry is configured to fit the parameters responsively to using a machine learning model.
There is also provided in accordance with still another embodiment of the present disclosure a clock syntonization method, including transferring data from a first compute node to a second compute node at a data rate indicative of a first clock frequency of a first physical hardware clock of the first compute node, deriving a second clock frequency from the data rate of the transferred data, and providing a clock signal at the derived second clock frequency in the second compute node.
Additionally in accordance with an embodiment of the present disclosure the data is transferred over an interconnect data bus in at least one digital signal.
Moreover, in accordance with an embodiment of the present disclosure, the method includes disciplining a second physical hardware clock of the second compute node operating at a third clock frequency responsively to a difference between the derived second clock frequency and the third clock frequency.
Further in accordance with an embodiment of the present disclosure, the method includes disciplining a second physical hardware clock of the second compute node responsively to a difference between the derived second clock frequency and a transmission rate at which data is transferred from the second compute node to the first compute node via an interconnect data bus.
Still further in accordance with an embodiment of the present disclosure, the method includes disciplining a second physical hardware clock of the second compute node responsively to a difference between the data rate at which the data is received from the first compute node by the second compute node, and a transmission rate at which data is transferred from the second compute node to the first compute node via an interconnect data bus.
Additionally in accordance with an embodiment of the present disclosure, the method includes modulating the data rate to spread interference across a range of frequencies so that a variation of the data rate over time describes a modulated signal of frequency against time.
Moreover, in accordance with an embodiment of the present disclosure the clock synchronization circuitry includes filtering circuitry to remove modulation from the modulated signal, the clock synchronization circuitry being configured to derive the second clock frequency from the modulated signal with the modulation removed.
Further in accordance with an embodiment of the present disclosure, the method includes digitally removing modulation from the modulated signal and deriving the second clock frequency from the modulated signal with the modulation removed.
Still further in accordance with an embodiment of the present disclosure, the method includes transforming the modulated signal yielding a Fourier Transform, and identifying the second clock frequency from the Fourier Transform.
Additionally in accordance with an embodiment of the present disclosure, the method includes sampling the frequency of the modulated signal yielding multiple frequency values, averaging the frequency values yielding an average value, and deriving the second clock frequency from the average value.
Moreover, in accordance with an embodiment of the present disclosure, the method includes deriving the second clock frequency by fitting parameters of a mathematic model of the modulated signal, the parameters including a frequency based on the first clock frequency.
Further in accordance with an embodiment of the present disclosure, the method includes fitting the parameters based on performing a regression analysis of the mathematical model.
Still further in accordance with an embodiment of the present disclosure, the method includes fitting the parameters responsively to using a machine learning model.
The present invention will be understood from the following detailed description, taken in conjunction with the drawings in which:
SyncE and PTP provide clock synchronization between network devices. There is also a need to push timing awareness towards the software stack enabling applications running on different compute nodes to be synchronized. For example, there may be one or more graphics processing unit (GPU) and/or central processing unit (CPU) processes that need to be synchronized. The synchronized timing speeds up utilization and balance of the work between the compute nodes, making connectivity much more efficient with less queues etc.
For many high-speed interconnects (e.g., Peripheral Component Interconnect Express (PCIe) or NVLink), packet-based protocols may provide synchronization between the devices involved (e.g., Precision Time Measurement (PTM) for PCIe). However, these packet-based protocols lack physical-layer-based syntonization and may stall performance. Other solutions such as using semaphore also lack performance.
Embodiments of the present invention address some of the above drawbacks by providing physical-layer-based syntonization between compute nodes (e.g., between two CPUs or GPUs) over an interconnect data bus wherein frequency information is transferred between compute nodes over the interconnect data bus based on the data rate (e.g., symbol rate) of the data transferred in digital signals between the compute nodes. In other words, the data transmission rate from one compute node (first compute node) to another (second compute node) is based on the clock frequency of the transmitting compute node. The receiving compute node then uses the frequency information indicated by the data transmission rate to generate or adjust its clock so that the clock of the receiving compute node is syntonized with the transmitting compute node. The interconnect data bus may include any suitable interconnect data bus such as PCIe, Ethernet, and InfiniBand.
In some embodiments, the second compute node may derive the clock frequency of the first compute node from the data rate of the data being transferred by the interconnect data bus between the first compute node and the second compute node. The derived frequency may then be used by the second compute node to generate a clock signal for use in the second compute node or to correct a clock signal generated by a clock of the second compute node so that the clock signal being used to drive timing in the second compute node is syntonized with the clock frequency of the first compute node.
In some embodiments, the second compute node adjusts its clock signal based on a difference between the derived frequency and the current frequency of the clock of the second compute node. In some embodiments, the second compute node adjusts its clock signal based on a difference between the transmission (TX) data rate from the second compute node to the first compute node and the receive (RX) data rate by the second compute node from the first compute node. In some embodiments, the second compute node adjusts its clock signal based on a difference between: the derived frequency; and the transmission (TX) data rate from the second compute node to the first compute node.
In many highspeed interconnects the frequency of data transmission may be non-constant and changes (e.g., is modulated) over some range. This is done to spread interference across a range of frequencies so that interference with other signals is reduced at any specific frequency. In PCIe, the signals may be reduced up to 0.5% of the base frequency of the clock of the transmitting compute node. Specifications may also specify how the frequency should be modulated (i.e., at what rate). In PCIe it is between 30 and 33 KHz.
The above is known as spread spectrum and modulates the base frequency of the clock used to drive the transmission data rate in a spread spectrum signal. In some embodiments, the base frequency of the clock is derived from the spread spectrum signal. One method to derive the base frequency of the clock is to use a high pass filter or band pass filter so that the spread spectrum modulation is removed to reveal the base frequency of the clock. Another method digitally separates the base frequency of the clock from the modulation signal, for example, using a Fourier Transform (FT). In yet another method, the spread spectrum signal may be sampled at suitably wide intervals to reveal an average signal indicative of the base frequency of the clock. In some embodiments, finite or infinite response filters may be used to transform the spread spectrum signal (e.g., using a FT) to identify the base frequency of the clock.
In some embodiments, a mathematical model of the spread spectrum signal is found, and parameters of the mathematical model are fit using regression analysis or a trained machine learning model to identify the base frequency of the clock which is one of the parameters. The parameters may also include amplitude of spread spectrum signal, modulating frequency of the spread spectrum signal, and phase offset of the function modulating the base frequency (e.g., the 30-33 kHz wave). For example, for a given time T0 of a local clock, T1 is the closest time to T0 when the modulating function reaches some specific value (e.g., the minimum, maximum, or mean of the modulating function) considered to be the beginning of the modulating function's cycle. T0 less T1 is the phase offset of the modulating function. By way of a more explicit, non-limiting example, where the modulating function is a sine function, the equation for the modulating function may be expressed as F(t)=A sin(Bt+C), where A is amplitude, B is related to frequency, and C is the phase offset.
Reference is now made to
The system 10 includes a plurality of compute nodes 12 (only two shown for the sake of simplicity) connected via one or more interconnect data buses 14 (only one shown for the sake of simplicity). The interconnect data bus 14 may include a peripheral device interconnect data bus. The interconnect data bus 14 may operate according to any suitable protocol, e.g., PCIe, Ethernet, or InfiniBand.
The system 10 is configured to synchronize all the compute nodes 12 in the system 10 to the clock frequency of one of the compute nodes 12 designated as a synchronization leader. The synchronization leader uses its frequency source to drive a transmission symbol rate on the interconnect data buses 14 from one compute node 12 to the other. The compute nodes 12 not designated as the synchronization leader are designated as synchronization followers. Each synchronization follower may use the symbol rate of data received on the interconnect data bus 14 to synchronize its clock to the clock rate indicated by the symbol rate of the received data or use the symbol rate to directly drive a clock signal, described in more detail below.
Each compute node 12 may include a physical hardware clock 16 and an interface 18. The physical hardware clock 16 is configured to maintain a clock frequency and/or clock time. The interface 18 is configured to transfer data with one or more of the compute nodes 12 over the interconnect data bus 14. Each compute node 12 may include clock synchronization circuitry 20 configured to synchronize the compute node 12 (in which the clock synchronization circuitry 20 is disposed) to the clock frequency of another compute node 12. Each compute 12 may include an oscillator 22 to provide a clock signal for use when no external clock input is provided. The clock synchronization circuitry 20 may include filtering circuitry 24 and/or a machine learning model 26, described in more detail below with reference to
In
The clock synchronization circuitry 20 of compute node 12-2 is configured to: derive a second clock frequency from the data rate of the transferred data (e.g., data rate 1) from compute node 12-1 (block 202); and provide a clock signal at the derived second clock frequency (block 204). In some embodiments, the clock signal provided in compute node 12-2 may be generated directly from the data rate of the transmitted data (e.g., data rate 1) and used in the compute node 12-2 for timing issues such as generating timestamps, timing execution of software, and setting a second data rate (e.g., data rate 2) at which data is transmitted by the interconnect data bus 14 from compute node 12-2 to compute node 12-1.
In some embodiments, the interconnect data bus 14 is configured to transmit data in a digital signal from compute node 12-2 to compute node 12-1 (or another one of the compute nodes 12) at the second data rate (e.g., data rate 2), which may be based on the clock frequency of the physical hardware clock 16 of compute node 12-2 (and operate at a third clock frequency), which may be driven by the oscillator 22 of compute node 12-2. The clock synchronization circuitry 20 of compute node 12-2 is configured to: derive the second clock frequency from the data rate of the transferred data (e.g., data rate 1) from compute node 12-1 (block 202); and provide the clock signal at the derived second clock frequency (block 204) by adjusting a clock signal provided by the physical hardware clock 16 of compute node 12-2 to the second clock frequency. In other words, if the physical hardware clock 16 of compute node 12-1 is running faster than the physical hardware clock 16 of compute node 12-2 as evidenced by the difference between the second and third clock frequency, or between data rate 1 and data rate 2, or between the second clock frequency and data rate 2, or between data rate 1 and the third clock frequency, then the clock synchronization circuitry 20 instructs the physical hardware clock 16 to speed up, and vice-versa. The adjustment of the physical hardware clock 16 of compute node 12-2 may be affected using a feedback loop which iteratively adjusts the clock frequency of the physical hardware clock 16 of compute node 12-2.
In some embodiments, the clock synchronization circuitry 20 of the compute node 12-2 is configured to discipline the physical hardware clock 16 of the compute node 12-2 responsively to a difference between the derived second clock frequency and the third clock frequency (block 206).
In some embodiments, the clock synchronization circuitry 20 of the compute node 12-2 is configured to discipline the physical hardware clock 16 of the compute node 12-2 responsively to a difference between the derived second clock frequency and a transmission rate (e.g., data rate 2) at which data is transferred from the compute node 12-2 to the compute node 12-1 via the interconnect data bus 14 (block 208).
In some embodiments, the clock synchronization circuitry 20 of the compute node 12-2 is configured to discipline the physical hardware clock 16 of the compute node 12-2 responsively to a difference between: the data rate (e.g., data rate 1) at which the data is received from the compute node 12-1 by the compute node 12-2; and a transmission rate (e.g., data rate 2) at which data is transferred from the compute node 12-2 to the compute node 12-1 via the interconnect data bus 14 (block 210).
The clock synchronization circuitry 20 may include any suitable frequency synthesizer such as a frequency jitter synchronizer and/or jitter network synchronizer clock. An example of a suitable frequency synthesizer 14 is Ultra-Low Jitter Network Synchronizer Clock LMK05318 commercially available from Texas Instruments Inc., 12500 TI Boulevard Dallas, Texas 75243 USA. The frequency synthesizer may receive a control signal (to adjust the clock frequency up or down) or a clock signal as input (e.g., when the compute node 12-2 does not include a physical hardware clock but uses the clock signal recovered from the data rate of data received over interconnect data bus 14) and output a clock signal responsively to the input control signal or clock signal. When no control signal or clock signal is input, the frequency synthesizer may generate a clock signal based on the output of the oscillator 22. In some embodiments, the frequency synthesizer may be replaced with a signal selector or switch which selectively uses the output of the oscillator 22 or the frequency of the received data (RX) signal as input.
In some embodiments, the synchronization leader may measure the difference between its own symbol transmission rate and the rate of symbols it receives from one or more of the synchronization followers (or perform a clock recovery of the received data stream and compare the recovered clock to the clock of the synchronization leader) to assess the syntonization accuracy of the follower(s) and take appropriate action, such as raise an alarm, log an event, and/or report a status to software.
In practice, some or all of the functions of the clock synchronization circuitry 20 may be combined in a single physical component or, alternatively, implemented using multiple physical components. These physical components may comprise hard-wired or programmable devices, or a combination of the two. In some embodiments, at least some of the functions of the clock synchronization circuitry 20 may be carried out by a programmable processor under the control of suitable software. This software may be downloaded to a device in electronic form, over a network, for example. Alternatively, or additionally, the software may be stored in tangible, non-transitory computer-readable storage media, such as optical, magnetic, or electronic memory.
Reference is now made to
In some embodiments, the data rate (of data transfer from the compute node 12-1 to compute node 12-2) is modulated to spread interference across a range of frequencies so that a variation of the data rate over time describes a modulated signal of frequency against time. The filtering circuitry 24 of clock synchronization circuitry 20 is configured to remove modulation from the modulated signal (block 302). The clock synchronization circuitry 20 is configured to derive the second clock frequency from the modulated signal with the modulation removed (block 304).
In some embodiments, the filtering circuitry 24 may include a high-pass or band-pass filter which is configured to remove the modulation from the modulated signal. In other embodiments, the filtering circuitry 24 is configured to digitally remove modulation from the modulated signal, and the clock synchronization circuitry 20 is configured to derive the second clock frequency from the modulated signal with the modulation removed. For example, a Fourier Transform (FT) of the modulated signal is performed, the modulation frequency is removed from the FT, an inverse FT is then performed of the FT with the modulation frequency removed, and then the second clock frequency is found from the inverse FT.
Reference is now made to
Reference is now made to
Reference is now made to
In some embodiments, clock synchronization circuitry 20 is configured to fit the parameters based on performing a regression analysis of the mathematical model (block 606). In other embodiments, the clock synchronization circuitry 20 is configured to fit the parameters responsively to using a machine learning model (block 608). The machine learning module may be generated, for example, by training a decision tree or neural network with inputs equal to the modulated signal and outputs equal to the parameters. The trained decision tree or neural network is used with modulated signal as input to yield an output comprising the parameters which include the base frequency.
Various features of the invention which are, for clarity, described in the contexts of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment may also be provided separately or in any suitable sub-combination.
The embodiments described above are cited by way of example, and the present invention is not limited by what has been particularly shown and described hereinabove. Rather the scope of the invention includes both combinations and sub-combinations of the various features described hereinabove, as well as variations and modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not disclosed in the prior art.
Number | Name | Date | Kind |
---|---|---|---|
5392421 | Lennartsson | Feb 1995 | A |
5402394 | Turski | Mar 1995 | A |
5416808 | Witsaman et al. | May 1995 | A |
5491792 | Grisham et al. | Feb 1996 | A |
5564285 | Jurewicz et al. | Oct 1996 | A |
5592486 | Lo et al. | Jan 1997 | A |
5896524 | Halstead, Jr. et al. | Apr 1999 | A |
6055246 | Jones | Apr 2000 | A |
6084856 | Simmons et al. | Jul 2000 | A |
6144714 | Bleiweiss et al. | Nov 2000 | A |
6199169 | Voth | Mar 2001 | B1 |
6289023 | Dowling et al. | Sep 2001 | B1 |
6449291 | Burns et al. | Sep 2002 | B1 |
6535926 | Esker | Mar 2003 | B1 |
6556636 | Takagi | Apr 2003 | B1 |
6556638 | Blackburn | Apr 2003 | B1 |
6718476 | Shima | Apr 2004 | B1 |
6918049 | Lamb et al. | Jul 2005 | B2 |
7111184 | Thomas, Jr. et al. | Sep 2006 | B2 |
7191354 | Purho | Mar 2007 | B2 |
7245627 | Goldenberg et al. | Jul 2007 | B2 |
7254646 | Aguilera et al. | Aug 2007 | B2 |
7334124 | Pham et al. | Feb 2008 | B2 |
7412475 | Govindarajalu | Aug 2008 | B1 |
7440474 | Goldman et al. | Oct 2008 | B1 |
7447975 | Riley | Nov 2008 | B2 |
7483448 | Bhandari et al. | Jan 2009 | B2 |
7496686 | Coyle | Feb 2009 | B2 |
7535933 | Zerbe et al. | May 2009 | B2 |
7623552 | Jordan et al. | Nov 2009 | B2 |
7636767 | Lev-Ran et al. | Dec 2009 | B2 |
7650158 | Indirabhai | Jan 2010 | B2 |
7656751 | Rischar et al. | Feb 2010 | B2 |
7750685 | Bunch et al. | Jul 2010 | B1 |
7904713 | Zajkowski et al. | Mar 2011 | B1 |
7941684 | Serebrin et al. | May 2011 | B2 |
8065052 | Fredriksson et al. | Nov 2011 | B2 |
8300749 | Hadzic et al. | Oct 2012 | B2 |
8341454 | Kondapalli | Dec 2012 | B1 |
8370675 | Kagan | Feb 2013 | B2 |
8407478 | Kagan et al. | Mar 2013 | B2 |
8607086 | Cullimore | Dec 2013 | B2 |
8699406 | Charles et al. | Apr 2014 | B1 |
8824903 | Christensen | Sep 2014 | B2 |
8879552 | Zheng | Nov 2014 | B2 |
8930647 | Smith | Jan 2015 | B1 |
9344265 | Karnes | May 2016 | B2 |
9397960 | Arad et al. | Jul 2016 | B2 |
9549234 | Mascitto | Jan 2017 | B1 |
9753854 | Bao | Sep 2017 | B1 |
9942025 | Bosch et al. | Apr 2018 | B2 |
9979998 | Pogue et al. | May 2018 | B1 |
10014937 | Di Mola et al. | Jul 2018 | B1 |
10027601 | Narkis et al. | Jul 2018 | B2 |
10054977 | Mikhaylov et al. | Aug 2018 | B2 |
10095543 | Griffin et al. | Oct 2018 | B1 |
10148258 | Carlson et al. | Dec 2018 | B2 |
10164759 | Volpe | Dec 2018 | B1 |
10320646 | Mirsky et al. | Jun 2019 | B2 |
10515045 | Mattina | Dec 2019 | B1 |
10623173 | Geng | Apr 2020 | B1 |
10637776 | Iwasaki | Apr 2020 | B2 |
10727966 | Izenberg et al. | Jul 2020 | B1 |
10778361 | Almog et al. | Sep 2020 | B1 |
10841243 | Levi et al. | Nov 2020 | B2 |
10879910 | Franck et al. | Dec 2020 | B1 |
10887077 | Ivry | Jan 2021 | B1 |
11070224 | Faig et al. | Jul 2021 | B1 |
11070304 | Levi et al. | Jul 2021 | B1 |
11128500 | Mentovich et al. | Sep 2021 | B1 |
11157433 | Lederman et al. | Oct 2021 | B2 |
11240079 | Kushnir et al. | Feb 2022 | B1 |
11303363 | Mohr et al. | Apr 2022 | B1 |
11336383 | Mula et al. | May 2022 | B2 |
11368768 | Bakopoulos et al. | Jun 2022 | B2 |
11379334 | Srinivasan et al. | Jul 2022 | B1 |
11388263 | Levi et al. | Jul 2022 | B2 |
11476928 | Levi et al. | Oct 2022 | B2 |
20010006500 | Nakajima et al. | Jul 2001 | A1 |
20020027886 | Fischer et al. | Mar 2002 | A1 |
20020031199 | Rolston et al. | Mar 2002 | A1 |
20040096013 | Laturell et al. | May 2004 | A1 |
20040153907 | Gibart | Aug 2004 | A1 |
20050033947 | Morris et al. | Feb 2005 | A1 |
20050172181 | Huliehel | Aug 2005 | A1 |
20050268183 | Barmettler | Dec 2005 | A1 |
20060109376 | Chaffee et al. | May 2006 | A1 |
20070008044 | Shimamoto | Jan 2007 | A1 |
20070072451 | Tazawa et al. | Mar 2007 | A1 |
20070104098 | Kimura et al. | May 2007 | A1 |
20070124415 | Lev-Ran et al. | May 2007 | A1 |
20070139085 | Elliot et al. | Jun 2007 | A1 |
20070159924 | Vook et al. | Jul 2007 | A1 |
20070266119 | Ohly | Nov 2007 | A1 |
20080069150 | Badt et al. | Mar 2008 | A1 |
20080225841 | Conway et al. | Sep 2008 | A1 |
20080285597 | Downey et al. | Nov 2008 | A1 |
20090055676 | Wiebe | Feb 2009 | A1 |
20090257458 | Cui et al. | Oct 2009 | A1 |
20100280858 | Bugenhagen | Nov 2010 | A1 |
20110182191 | Jackson | Jul 2011 | A1 |
20110194425 | Li et al. | Aug 2011 | A1 |
20120063556 | Hoang | Mar 2012 | A1 |
20120076319 | Terwal | Mar 2012 | A1 |
20120301134 | Davari et al. | Nov 2012 | A1 |
20130039359 | Bedrosian | Feb 2013 | A1 |
20130045014 | Mottahedin et al. | Feb 2013 | A1 |
20130215889 | Zheng et al. | Aug 2013 | A1 |
20130235889 | Aweya et al. | Sep 2013 | A1 |
20130294144 | Wang et al. | Nov 2013 | A1 |
20130315265 | Webb, III et al. | Nov 2013 | A1 |
20130336435 | Akkihal et al. | Dec 2013 | A1 |
20140085141 | Geva et al. | Mar 2014 | A1 |
20140153680 | Garg et al. | Jun 2014 | A1 |
20140185216 | Zeng et al. | Jul 2014 | A1 |
20140185632 | Steiner et al. | Jul 2014 | A1 |
20140253387 | Gunn et al. | Sep 2014 | A1 |
20140281036 | Cutler et al. | Sep 2014 | A1 |
20140301221 | Nadeau et al. | Oct 2014 | A1 |
20140321285 | Chew et al. | Oct 2014 | A1 |
20150019839 | Cardinell et al. | Jan 2015 | A1 |
20150078405 | Roberts | Mar 2015 | A1 |
20150092793 | Aweya | Apr 2015 | A1 |
20150127978 | Cui et al. | May 2015 | A1 |
20150163050 | Han et al. | Jun 2015 | A1 |
20150318941 | Zheng et al. | Nov 2015 | A1 |
20160057518 | Neudorf | Feb 2016 | A1 |
20160072602 | Earl et al. | Mar 2016 | A1 |
20160078901 | Toma et al. | Mar 2016 | A1 |
20160110211 | Karnes | Apr 2016 | A1 |
20160140066 | Worrell et al. | May 2016 | A1 |
20160277138 | Garg et al. | Sep 2016 | A1 |
20160285574 | White et al. | Sep 2016 | A1 |
20160315756 | Tenea et al. | Oct 2016 | A1 |
20170005903 | Mirsky | Jan 2017 | A1 |
20170017604 | Chen et al. | Jan 2017 | A1 |
20170126589 | Estabrooks et al. | May 2017 | A1 |
20170160933 | De Jong et al. | Jun 2017 | A1 |
20170214516 | Rivaud et al. | Jul 2017 | A1 |
20170302392 | Farra et al. | Oct 2017 | A1 |
20170331926 | Raveh et al. | Nov 2017 | A1 |
20170359137 | Butterworth et al. | Dec 2017 | A1 |
20180059167 | Sharf et al. | Mar 2018 | A1 |
20180152286 | Kemparaj et al. | May 2018 | A1 |
20180188698 | Dionne et al. | Jul 2018 | A1 |
20180191802 | Yang et al. | Jul 2018 | A1 |
20180227067 | Hu et al. | Aug 2018 | A1 |
20180309654 | Achkir et al. | Oct 2018 | A1 |
20190007189 | Hossain et al. | Jan 2019 | A1 |
20190014526 | Bader et al. | Jan 2019 | A1 |
20190089615 | Branscomb et al. | Mar 2019 | A1 |
20190149258 | Araki et al. | May 2019 | A1 |
20190158909 | Kulkarni et al. | May 2019 | A1 |
20190196563 | Lai | Jun 2019 | A1 |
20190273571 | Bordogna et al. | Sep 2019 | A1 |
20190319729 | Leong et al. | Oct 2019 | A1 |
20190349392 | Wetterwald et al. | Nov 2019 | A1 |
20190379714 | Levi et al. | Dec 2019 | A1 |
20200162234 | Almog et al. | May 2020 | A1 |
20200169379 | Gaist et al. | May 2020 | A1 |
20200235905 | Su et al. | Jul 2020 | A1 |
20200304224 | Neugeboren | Sep 2020 | A1 |
20200331480 | Zhang et al. | Oct 2020 | A1 |
20200344333 | Hawari et al. | Oct 2020 | A1 |
20200396050 | Perras et al. | Dec 2020 | A1 |
20200401434 | Thampi et al. | Dec 2020 | A1 |
20200403652 | Goff et al. | Dec 2020 | A1 |
20210006344 | Chen et al. | Jan 2021 | A1 |
20210141413 | Levi et al. | May 2021 | A1 |
20210218431 | Narayanan et al. | Jul 2021 | A1 |
20210243140 | Levi et al. | Aug 2021 | A1 |
20210288785 | Faig et al. | Sep 2021 | A1 |
20210297151 | Levi et al. | Sep 2021 | A1 |
20210297230 | Dror et al. | Sep 2021 | A1 |
20210318978 | Hsung | Oct 2021 | A1 |
20210328900 | Arnon Sattinger et al. | Oct 2021 | A1 |
20210392065 | Sela et al. | Dec 2021 | A1 |
20210409031 | Ranganathan et al. | Dec 2021 | A1 |
20220006606 | Levi et al. | Jan 2022 | A1 |
20220021393 | Ravid et al. | Jan 2022 | A1 |
20220066978 | Mishra et al. | Mar 2022 | A1 |
20220086105 | Levi et al. | Mar 2022 | A1 |
20220173741 | Ravid et al. | Jun 2022 | A1 |
20220191275 | Levi et al. | Jun 2022 | A1 |
20220191578 | Ramkumar et al. | Jun 2022 | A1 |
20220121691 | Mentovich et al. | Jul 2022 | A1 |
20220224500 | Mula et al. | Jul 2022 | A1 |
20220239549 | Zhao et al. | Jul 2022 | A1 |
20220342086 | Yoshida | Oct 2022 | A1 |
20220390979 | Xu | Dec 2022 | A1 |
20240204897 | Manevich | Jun 2024 | A1 |
Number | Date | Country |
---|---|---|
106817183 | Jun 2017 | CN |
108829493 | Nov 2018 | CN |
1215559 | Sep 2007 | EP |
2770678 | Aug 2014 | EP |
2011091676 | May 2011 | JP |
498259 | Aug 2002 | TW |
2012007276 | Jan 2012 | WO |
2013124782 | Aug 2013 | WO |
2013143112 | Oct 2013 | WO |
2014029533 | Feb 2014 | WO |
2014138936 | Sep 2014 | WO |
Entry |
---|
U.S. Appl. No. 17/579,630 Office Action dated Oct. 24, 2022. |
U.S. Appl. No. 17/579,630 Office Action dated Jan. 12, 2023. |
U.S. Appl. No. 17/670,540 Office Action dated Jan. 18, 2023. |
U.S. Appl. No. 17/191,736 Office Action dated Nov. 10, 2022. |
Levi et al., U.S. Appl. No. 17/582,058, filed Jan. 24, 2022. |
Levi et al., U.S. Appl. No. 17/246,730, filed May 3, 2021. |
Levi et al., U.S. Appl. No. 17/315,396, filed May 10, 2021. |
Levi et al., U.S. Appl. No. 17/359,667, filed Jun. 28, 2021. |
Wasko et al., U.S. Appl. No. 17/520,674, filed Nov. 7, 2021. |
Wasko et al., U.S. Appl. No. 17/582,058, filed Jan. 24, 2022. |
Levi et al., U.S. Appl. No. 17/667,600, filed Feb. 9, 2022. |
Shapira et al., U.S. Appl. No. 17/534,776, filed Nov. 24, 2021. |
Shapira et al., U.S. Appl. No. 17/578,115, filed Jan. 18, 2022. |
Kernen et al., U.S. Appl. No. 17/858,236, filed Jul. 6, 2022. |
Zhang et al., “TI BAW technology enables ultra-low jitter clocks for highspeed networks”, White paper, Texas Instruments, pp. 1-11, Feb. 2019. |
Skywork Solutions Inc., “PCI Express 3.1 JITTER Requirements”, AN562, pp. 1-16, year 2021. |
Intel, “Can Altera GX/GT/GZ device high speed transceivers handle Spread Spectrum Clocking (SSC), as required by PCIe or SATA/SAS protocols?”, p. 1, Sep. 11, 2012. |
Pismenny et al., U.S. Appl. No. 17/824,954, filed May 26, 2022. |
U.S. Appl. No. 17/867,779 Office Action dated Mar. 28, 2024. |
U.S. Appl. No. 17/871,937 Office Action dated Aug. 1, 2023. |
U.S. Appl. No. 17/578,115 Office Action dated Apr. 26, 2023. |
U.S. Appl. No. 17/534,776 Office Action dated Jun. 29, 2023. |
SiTime Corporation, “Sit5377—60 to 220 MHZ, ±100 ppb Elite RF™ Super-TCXO,” Product Description, pp. 1-3, last updated Mar. 18, 2023 as downloaded from https://web.archive.org/web/20230318094421/https://www.sitime.com/products/super-tcxos/sit5377. |
PCI-SIG, “PCI Express®—Base Specification—Revision 3.0,” pp. 1-860, Nov. 10, 2010. |
IEEE Standard 1588™-2008: “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems”, IEEE Instrumentation and Measurement Society, Revision of IEEE Standard 1588-2002, USA, pp. 1-289, Jul. 24, 2008. |
Weibel et al., “Implementation and Performance of Time Stamping Techniques”, 2004 Conference on IEEE 1588, pp. 1-29, Sep. 28, 2004. |
Working Draft Project American National Standard T10/1799-D, “Information Technology—SCSI Block Commands-3 (SBC-3)”, pp. 1-220, Revision 19, May 29, 2009. |
“Infiniband Architecture: Specification vol. 1”, pp. 1-1727, Release 1.2.1, Infiniband Trade Association, Nov. 2007. |
Mellanox Technologies, “Mellanox ConnectX IB: Dual-Port InfiniBand Adapter Cards with PCI Express 2.0”, pp. 1-2, USA, year 2008. |
Wikipedia—“Precision Time Protocol”, pp. 1-8, Aug. 24, 2019. |
IEEE Std 1588-2002, “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems”, IEEE Instrumentation and Measurement Society, pp. 1-154, Nov. 8, 2002. |
Weibel, H., “High Precision Clock Synchronization according to IEEE 1588 Implementation and Performance Issues”, Zurich University of Applied Sciences, pp. 1-9, Jan. 17, 2005. |
Lu et al., “A Fast CRC Update Implementation”, Computer Engineering Laboratory, Electrical Engineering Department, pp. 113-120, Oct. 8, 2003. |
Texas Instruments, “LMK05318 Ultra-Low Jitter Network Synchronizer Clock With Two Frequency Domains,” Product Folder, pp. 1-86, Dec. 2018. |
Dlugy-Hegwer et al., “Designing and Testing IEEE 1588 Timing Networks”, Symmetricom, pp. 1-10, Jan. 2007. |
Mellanox Technologies, “How to test 1PPS on Mellanox Adapters”, pp. 1-6, Oct. 22, 2019 downloaded from https://community.mellanox.com/s/article/How-To-Test-1PPS-on-Mellanox-Adapters. |
ITU-T recommendation, “G.8273.2/Y.1368.2—Timing characteristics of telecom boundary clocks and telecom time slave clocks”, pp. 1-50, Jan. 2017. |
Wasko et al., U.S. Appl. No. 17/549,949, filed Dec. 14, 2021. |
Ipclock, “IEEE 1588 Primer,” ip-clock.com, pp. 1-3, May 1, 2017 (downloaded from https://web.archive.org/web/20170501192647/http://ip-clock.com/ieee-1588-primer/). |
ITU-T Standard G.8261/Y.1361, “Timing and synchronization aspects in packet networks”, pp. 1-120, Aug. 2019. |
Levy et al., U.S. Appl. No. 17/313,026, filed May 6, 2021. |
“Precision Time Protocol,” PTP Clock Types, CISCO, pp. 1-52, Jul. 30, 2020, as downloaded from https://www.cisco.com/c/en/us/td/docs/dcn/aci/apic/5x/system-management-configuration/cisco-apic-system-management-configuration-guide-52x/m-precision-time-protocol.pdf. |
ITU-T Standard G.8262/Y.1362, “Timing characteristics of synchronous equipment slave clock”, pp. 1-44, Nov. 2018. |
ITU-T Standard G.8264/Y.1364, “Distribution of timing information through packet networks”, pp. 1-42, Aug. 2017. |
Manevich et al., U.S. Appl. No. 17/579,630, filed Jan. 20, 2022. |
Levi et al., U.S. Appl. No. 17/871,937, filed Jul. 24, 2022. |
Manevich et al., U.S. Appl. No. 17/867,779, filed Jul. 19, 2022. |
Manevich et al., U.S. Appl. No. 17/885,604, filed Aug. 11, 2022. |
U.S. Appl. No. 17/191,736 Advisory Action dated Feb. 16, 2023. |
“IEEE Standard for Local and Metropolitan Area Networks—Timing and Synchronization for Time-Sensitive Applications,” IEEE Std 802.1AS-2020, IEEE Computer Society, pp. 1-421, year 2020. |
U.S. Appl. No. 17/549,949 Office Action dated Mar. 30, 2023. |
Corbett et al., “Spanner: Google's Globally Distributed Database,” ACM Transactions on Computer Systems, vol. 31, No. 3, article 8, pp. 1-22, Aug. 2013. |
U.S. Appl. No. 17/191,736 Office Action dated Jun. 26, 2023. |
U.S. Appl. No. 17/885,604 Office Action dated Nov. 13, 2024. |
U.S. Appl. No. 17/867,779 Office Action dated Jan. 30, 2025. |
Number | Date | Country | |
---|---|---|---|
20240031124 A1 | Jan 2024 | US |