The present invention relates to computer systems, and in particular, but not exclusively to, clock synchronization.
Clock synchronization among network devices is used in many network applications. One application of using a synchronized clock value is for measuring latency between two devices. If the clocks are not synchronized the resulting latency measurement will be inaccurate.
Synchronous Ethernet (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 synchronization inside a network with respect to a master device clock source or master clock. Each network element (e.g., a switch, a network interface card (NIC), or router) needs to recover the master clock from high-speed data received from the master device clock source and use the recovered master clock for its own data transmission in a manner such that the master clock spreads throughout the network.
Time, clock and frequency synchronization are crucial in some modern computer network applications. They enable 5G and 6G networks, and are proven to enhance the performance of certain data center workloads. SyncE standard enables improving (Precision Time Protocol) PTP accuracy by having less accumulated drift between PTP messages, and helps achieve an accurate time solution for an extended period after completely losing receipt of a PTP source.
There is provided in accordance with an embodiment of the present disclosure, a communication system, including a plurality of network devices, each network device including a network interface to receive at least one data stream, a given one of the network devices being configured to recover a remote clock from the at least one data stream received by the given network device, and a frequency synthesizer to generate a clock signal and output the clock signal to each of the network devices, wherein the given network device is configured to find a clock frequency differential between the clock signal and the recovered remote clock, and provide a control signal to the frequency synthesizer responsively to the clock frequency differential, the control signal causes the frequency synthesizer to adjust the clock signal so as to iteratively reduce an absolute value of the clock frequency differential between the clock signal and the recovered remote clock.
Further in accordance with an embodiment of the present disclosure the frequency synthesizer includes a control input connector and at least one output connector, the given network device being connected to the control input connector, and the network devices being connected to the at least one output connector, the frequency synthesizer being configured to receive the control signal via the control input connector, and output the clock signal via the at least one output connector.
Still further in accordance with an embodiment of the present disclosure the given network device is configured to directly provide the control signal to the frequency synthesizer.
Additionally in accordance with an embodiment of the present disclosure, the system includes a processor to execute control software, and wherein the frequency synthesizer includes a control input connector and at least one output connector, another one of the network devices is connected to the control input connector, the network devices are connected to the at least one output connector, the given network device is configured to provide a first control signal to the control software, which is configured to provide a second control signal to the frequency synthesizer, and the frequency synthesizer is configured to receive the second control signal via the control input connector, and output the clock signal via the at least one output connector.
Moreover, in accordance with an embodiment of the present disclosure the control software is configured to provide a third control signal to the other network device, which is configured to provide the second control signal to the frequency synthesizer.
Further in accordance with an embodiment of the present disclosure the frequency synthesizer includes at least one control input connector and at least one output connector, the network devices are connected to the at least one control input connector and the at least one output connector, a first network device of the network devices is configured to recover a first remote clock from a first data stream received by the first network device, find a first clock frequency differential between the clock signal and the recovered first remote clock, and provide a first control signal to the frequency synthesizer responsively to the first clock frequency differential, the first control signal causes the frequency synthesizer to adjust the clock signal so as to iteratively reduce an absolute value of the first clock frequency differential between the clock signal and the recovered first remote clock, the frequency synthesizer is configured to receive the first control signal from the first network device via the at least one control input connector, and output the clock signal via the at least one output connector, a second network device of the network devices is configured to recover a second remote clock from a second data stream received by the second network device, find a second clock frequency differential between the clock signal and the recovered second remote clock, and provide a second control signal to the frequency synthesizer responsively to the second clock frequency differential, the second control signal causes the frequency synthesizer to adjust the clock signal so as to iteratively reduce an absolute value of the second clock frequency differential between the clock signal and the recovered second remote clock, and the frequency synthesizer is configured to receive the second control signal from the second network device via the at least one control input connector, and output the clock signal via the at least one output connector.
Still further in accordance with an embodiment of the present disclosure, the system includes a processor to execute control software to receive Synchronous Ethernet (SyncE) messages, and first select the a network interface of the first network device as receiving a first master clock with which to synchronize the network devices and then select the network interface of the second network device as receiving a second master clock with which to synchronize the network devices, responsively to the SyncE messages.
Additionally in accordance with an embodiment of the present disclosure the first network device is configured to directly provide the first control signal to the frequency synthesizer, and the second network device is configured to directly provide the second control signal to the frequency synthesizer.
Moreover, in accordance with an embodiment of the present disclosure the frequency synthesizer includes a clock input connected to an output of an oscillator and a control input connected to an output of the given network device to receive the control signal.
Further in accordance with an embodiment of the present disclosure the frequency synthesizer is a frequency jitter synchronizer.
Still further in accordance with an embodiment of the present disclosure the frequency synthesizer is a jitter network synchronizer clock.
Additionally in accordance with an embodiment of the present disclosure, the system includes a processor to execute control software to receive Synchronous Ethernet (Synch) messages, and select the network interface of the given network device as receiving a master clock with which to synchronize the network devices responsively to at least one of the SyncF messages.
Moreover, in accordance with an embodiment of the present disclosure each of the network devices is included in an independent application-specific integrated circuit (ASIC).
Further in accordance with an embodiment of the present disclosure, the system includes a printed circuit board on which the ASIC of each of the network devices is disposed and the frequency synthesizer.
Still further in accordance with an embodiment of the present disclosure, the system includes printed circuit board traces connecting outputs of the frequency synthesizer to the network devices, wherein each of the printed circuit board traces are about the same length.
Additionally in accordance with an embodiment of the present disclosure, the system includes at least one addition frequency synthesizer connected to an output of the frequency synthesizer and configured to output clock signals to respective ones of the network devices.
Moreover, in accordance with an embodiment of the present disclosure, the system includes a signal divider device connected to an output of the frequency synthesizer and configured to divide the clock signal into clock signals for output to respective ones of the network devices.
There is also provided in accordance with another embodiment of the present disclosure, a communication method, including each network device of a plurality of network devices receiving at least one data stream, a given one of the network devices recovering a remote clock from the at least one data stream received by the given network device, a frequency synthesizer generating a clock signal and outputting the clock signal to each of the network devices, the given network device finding a clock frequency differential between the clock signal and the recovered remote clock, and the given network device providing a control signal to the frequency synthesizer responsively to the clock frequency differential, and the frequency synthesizer adjusting the clock signal responsively to the control signal so as to iteratively reduce an absolute value of the clock frequency differential between the clock signal and the recovered remote clock.
The present invention will be understood from the following detailed description, taken in conjunction with the drawings in which:
Clock synchronization between network devices remains a challenge in the networking industry due to continued demand for tighter clock synchronization. In many scenarios, network devices in a system need to be synchronized accurately. One solution is to connect the network devices together and synchronize from one device to the other devices by passing clock signals between the network devices. Such a solution may be inflexible and lack accuracy in some cases.
Embodiments of the present invention address some of the above drawbacks by providing a network synchronization system (e.g., on a printed circuit board (PCB)) including multiple network devices (e.g., separate application-specific integrated circuits (ASICs) mounted on the PCB), with fan-out circuitry to push the same clock frequency signal from a frequency synthesizer to the network devices.
A control input of the frequency synthesizer is connected, via a control channel, to one or more of the network devices to receive a control signal from the network device(s). The control signal instructs the frequency synthesizer whether to increase or decrease the frequency of a clock signal generated by the frequency synthesizer. One or more clock outputs of the frequency synthesizer carry the clock signal generated by the frequency synthesizer to all of the network devices (e.g., on the PCB) so that all the network devices are synchronized to the same clock frequency.
One of the network devices (which may be selected as a master clock of the network devices) recovers a remote clock and finds a clock frequency differential between the recovered remote clock and the clock signal received from the frequency synthesizer. The master clock network device generates a control signal to be sent to the frequency synthesizer based on the clock frequency differential. In response to receiving the control signal, the frequency synthesizer adjusts the clock frequency signal provided to the network devices thereby moving the clock signal closer to the recovered remote clock. In this manner, the frequency synthesizer adjusts the clock signal so as to iteratively reduce an absolute value of the clock frequency differential between the clock signal and the recovered remote clock.
In some embodiments, the control input of the frequency synthesizer is connected to a single network device (on the PCB), which acts as the “synchronization master” for all the network devices, and all clock frequency adjustment operations pass through the synchronization master. For example, if a SyncE external source is connected to a given network device other than the synchronization master, the given network device provides a first control signal to the synchronization master, which in turn passes a second control signal (based on the first control signal or the same as the first control signal) to the frequency synthesizer. This may be achieved by passing frequency offset information (e.g., the control signal) through software, so that the information would pass from the synchronization master to the frequency synthesizer, which eventually feeds the network devices with the clock frequency signal.
In some embodiments, all of the network devices (on the PCB) are connected via respective control channels to the network synchronizer control input (e.g., in a multi-master I2C topology), with each network device serving as the synchronization master, as long as only one device is providing a control signal to the frequency synthesizer at any given time. In this manner, a SyncE control loop may be closed between the synchronization master and the frequency synthesizer without passing frequency offset information through software. This embodiment is faster, and a more stable control loop can be achieved since no latency jitter is introduced by software and a central processing unit (CPU).
Software should be aware of the control channel connectivity of the board, whether all network devices are connected to the frequency synthesizer, or only one or a subset of network devices are connected to the frequency synthesizer so that for devices not directly connected to the frequency synthesizer, frequency offset information is passed through the software and redirected to a device which has a direct control channel with the frequency synthesizer.
In some embodiments, none of the network devices are connected via a direct control channel to the frequency synthesizer and all frequency offset information is passed through the software and passed via a direct control channel between the CPU and the frequency synthesizer.
In some embodiments, one or more signal dividers or frequency synthesizers may be used to split the output clock synchronization signals for receipt by multiple network devices (on the PCB).
Reference is now made to
The system 10 include a plurality of network devices 12, a frequency synthesizer 14, and a processor 16.
The system 10 may also include printed circuit board traces 20 connecting outputs of the frequency synthesizer 14 to clock input ports 22 of respective ones of the network devices 12. In some embodiments, the printed circuit board traces 20 are about the same length (e.g., within a tolerance of 5%). In other embodiments, the traces 20 are different lengths.
Each network device 12 includes a network interface 24, clock synchronization circuitry 26, the clock input port 22, and may include a physical hardware clock 28. The network interface 24 is configured to receive at least one data stream, which may include clock frequency information (e.g., encoded in the data stream(s)) supplied by a remote master clock 30.
The frequency synthesizer 14 may be 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 14 includes a control input connector 32, a clock input 34, and at least one output connector 36. In the example of
In some embodiments, the system 10 also includes an oscillator 40. The output of the oscillator 40 is connected to the clock input 34 of the frequency synthesizer 14. The frequency synthesizer 14 is configured to generate a clock signal and output the clock signal to the clock input port 22 of each of the network devices 12. The clock signal frequency is based on the frequency of the signal output by the oscillator 40 and may be adjusted based on the received control signal 44.
The processor 16 is configured to execute control software 42 to receive Synchronous Ethernet (SyncE) messages; and select the (port of the) network interface 24 of one of the network devices 12 receiving the most accurate remote clock. In the example of
The network device 12-1 is configured to: recover a remote clock from the data stream(s) received by the network interface 24 of the network device 12-1 (block 202); and find a clock frequency differential between the clock signal (received from the frequency synthesizer 14) and the recovered remote clock (block 204). The network device 12-1 is configured to generate the control signal 44 and provide the control signal 44 to the frequency synthesizer 14 responsively to the clock frequency differential (block 206). For example, if the recovered remote clock is faster than the clock signal then the control signal 44 commands the frequency synthesizer 14 to quicken the clock signal, and vice-versa. In the example of
The frequency synthesizer 14 is configured to: receive the control signal 44 via the control input connector 32; adjust the clock signal responsively to the control signal 44; and output the clock signal from the output connectors 36 via the traces 20 to the respective clock input ports 22 of the network devices 12. Therefore, traces 20 and connection 38 form a control loop between the network device 12-1 and the frequency synthesizer 14 to synchronize the clock signal with the recovered remote clock. The clock signal is also fed to all the now network devices 12 in the system 10.
Reference is now made to
Reference is now made to
In the example of
Reference is now made to
One of the network devices 12 is assigned as the master network device 12 by the control software 42. The control software 42 may also instructs the non-master network devices 12 to not compute a difference between their recovered remote clocks and the clock signal and/or not send a control signal to the frequency synthesizer 14 via the control software 42.
Any one of the network devices 12 (e.g., the master network device 12) may be configured to: recover a remote clock from a data stream received by that network device 12; find a clock frequency differential between the clock signal (received from frequency synthesizer 14) and the recovered remote clock; and directly provide (i.e., not via software) a control signal to the frequency synthesizer 14 responsively to the clock frequency differential. The control signal causes the frequency synthesizer 14 to adjust the clock signal so as to iteratively reduce an absolute value of the clock frequency differential between the clock signal and the recovered remote clock. The frequency synthesizer 14 is configured to: receive the control signal from that network device 12 via the control input connector 32; and output the clock signal via the output connectors 36 to the network devices 12.
In some cases, the frequency synthesizer 14 may not include enough output connectors 36 to connect to each of the network devices 12. Therefore, the system 10 may include one or more signal divider devices 502 and/or one or more additional frequency synthesizers 504 to receive the clock signal from the frequency synthesizer 14 and output multiple copies of the clock signal to connected network devices 12. In the example of
In some embodiments, the signal divider devices 502 are configured to divide a received clock signal into multiple clock signals for output to respective network devices 12. In some embodiments, the frequency synthesizers 504 are configured to output clock signals to respective network devices 12. In some embodiments, any combination of the signal divider devices 502 and/or the frequency synthesizers 504 may be arranged in a tree structure to divide the clock signals among the network devices 12, for example using multiple levels of signal divider devices 502 and/or frequency synthesizers 504.
In practice, some or all of the functions of the clock synchronization circuitry 26 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 26 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.
In practice, some or all of the functions of the processor 16 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 processor 16 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.
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 | 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 |
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 |
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 | 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 | Jun 2015 | A1 |
20150318941 | Zheng et al. | Nov 2015 | A1 |
20160057518 | Neudorf | Feb 2016 | A1 |
20160072602 | Earl 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 | 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 | 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 |
20190220300 | Rosenboom | Jul 2019 | A1 |
20190265997 | Merrill et al. | Aug 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 |
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 | 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 |
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 |
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 PCle 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/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. |
PCI-SIG, “PCI Express®—Base Specification—Revision 3.0,” pp. 1-860, Nov. 10, 2010. |
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. |
IEEE Standard 1588™—Apr. 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/868,841, filed Jul. 20, 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/313,026 Office Action dated Dec. 19, 2023. |
U.S. Appl. No. 17/191,736 Office Action dated Jan. 5, 2024. |
Number | Date | Country | |
---|---|---|---|
20240031121 A1 | Jan 2024 | US |