A method for frequency synchronization of a multiport device may include recovering a clock frequency of a master port of a first device that is linked to the multiport device at a slave port of the multiport device. A clock frequency of the slave port may be locked to the recovered-clock frequency of the master port of the first device. frequency data may be stored in a first frequency register associated with the slave port. The stored frequency data may include a difference between the recovered-clock frequency of the master port of the first device and a local-clock frequency of the multiport device. A clock frequency of one or more master ports of the multiport device may be synchronized with the locked clock frequency of the slave port by coupling the first frequency register to frequency registers associated with one or more master ports.
|
1. A method for frequency synchronization of a multiport device, the method comprising:
recovering a clock frequency of a master port of a first device linked to the multiport device at a slave port of the multiport device;
locking a clock frequency of the slave port to the recovered-clock frequency of the master port of the first device;
storing, in a first frequency register associated with the slave port, frequency data; and
synchronizing a clock frequency of at least one master port of the multiport device with the locked clock frequency of the slave port by coupling the first frequency register to a second frequency register associated with at least one master port,
wherein the stored frequency data is indicative of a difference between the recovered-clock frequency of the master port of the first device and a local-clock frequency of the multiport device.
19. A multiport device comprising:
a slave port configured to recover a clock frequency of a master port of a first device linked to the multiport device;
a slave phased-locked loop (PLL) configured to lock a clock frequency of the slave port to the recovered-clock frequency of the master port of the first device; and
a master frequency register coupled to a slave frequency register and configured to facilitate synchronizing a clock frequency of at least one master port of the multiport device with the locked clock frequency of the slave port, wherein:
the master and slave frequency registers are associated, respectively, with the at least one master port and the slave port,
the slave frequency register stores frequency data, and
the stored frequency data comprises information pertaining the recovered-clock frequency of the master port of the first device and a local-clock frequency of the multiport device.
10. A system comprising:
a slave port configured to recover a clock frequency of a master port of a first device linked to the multiport device;
a first phased-locked loop (PLL) configured to lock a clock frequency of the slave port to the recovered-clock frequency of the master port of the first device;
a first frequency register to store frequency data, the first frequency register being associated with the slave port; and
a second frequency register coupled to the first frequency register and configured to synchronize a clock frequency of at least one master port of the multiport device with the locked clock frequency of the slave port, the second frequency register being associated with the at least one master port,
wherein the stored frequency data is indicative of a difference between the recovered-clock frequency of the master port of the first device and a local-clock frequency of the multiport device.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
configuring the control logic to selectively enable/disable an automatic detection of the plurality of ports of the multiport device for synchronization; and
determining, by using the control logic, pairs of ports for synchronization.
9. The method of
activating the frequency synchronization of the clock frequency of the at least one master port of the multiport device with the locked clock frequency of the slave port when a link between the slave port and the first device is established, and
deactivating the frequency synchronization of the clock frequency of the at least one master port of the multiport device with the locked clock frequency of the slave port when the link between the slave port and the first device is lost.
11. The system of
12. The system of
13. The system of
14. The system of
15. The system of
the system comprises a multiport device, wherein the multiport device comprises an Ethernet node,
the multiport device comprises a reference clock generator, and
the reference clock generator is configured to generate a reference frequency that is used to generate the local-clock frequency of the multiport device.
16. The system of
17. The system of
18. The system of
20. The multiport device of
the master frequency register is associated with a master PLL, and wherein the master PLL is associated with the at least one master port,
information pertaining the recovered-clock frequency comprises a difference between the recovered-clock frequency of the master port of the first device and a local-clock frequency of the multiport device,
the multiport device further comprises a processing module configured to couple the master frequency register to the slave frequency register,
the processing module comprises a circuit that is configured to provide for the master PLL to follow the slave PLL,
the processing module comprises a smoothing filter configured to reduce clock signal jitters,
the smoothing filter comprises a leaky integrator comprising an N-bit register and a divide-by-2″ block, and
the leaky integrator is configured to have a time constant that is defined by n.
|
The present application claims the benefit of priority from U.S. Provisional Patent Application Ser. No. 61/807,265, filed on Apr. 1, 2013, which is hereby incorporated by reference in its entirety for all purposes.
The present description relates generally to Ethernet communications, and more particularly, but not exclusively, to a low-cost port synchronization method in multiport Ethernet devices.
Ethernet technology has been widely accepted and used in many applications. As specified in IEEE 802.3 series of specifications, various data rates may be supported at distances up to 100 meters. There are many applications with longer range requirements that may use multiple Ethernet link segments for establishing a connection between two nodes. In addition to range requirements, other networking constraints may result in multiple Ethernet link segments between two communication nodes. As an example application, a connection between one or more mobile base stations and a center node may include multiple Ethernet link segments.
In certain applications, for example, connecting a mobile base station to a center node, there may also be a tight clock synchronization requirement between two data communication nodes. When multiple Ethernet link segments are used to connect the base station to the center node, each link segment may be on a different clock frequency reference, violating synchronization requirement between the mobile base station (e.g., an end node) and the center node.
Certain features of the subject technology are set forth in the appended claims. However, for purpose of explanation, several embodiments of the subject technology are set forth in the following figures.
The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology may be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a thorough understanding of the subject technology. However, it will be clear and apparent to those skilled in the art that the subject technology is not limited to the specific details set forth herein and may be practiced using one or more implementations. In one or more instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject technology.
It is also understood that when the multi-segment link 100A is used to connect a base station (e.g., the end node 130) to the center node 110, each link segment may be on a different clock frequency reference. This may violate synchronization requirement between the mobile base station and the center node. It is further understood that the two ends of each Ethernet link segment (e.g., nodes 120-1 and 120-2) are synchronized (e.g., are operated in a loop-timing mode) and operate on the same frequency domain (e.g., have similar operating frequencies). For example, in 1000 BASE-T and 10 GBT standards, when two Ethernet nodes are linked together, one node may be designated as a master node and another may be designated as a slave node. However, for multi-segment Ethernet links, each node may include more than one port and the synchronization requirement may need to be dealt with differently as addressed by the subject technology and disclosed herein.
Each of the slave ports 152, 162, or 172 may include a slave-port phase-locked loop (PLL) (e.g., 156, 166, or 176), and each of the master ports 154, 164, or 174 may include a master-port PLL (e.g., 158, 168, or 178). Each of the PLLs 156, 166, 176, 158, 168, or 178 may use a reference clock signal generated by a reference clock (e.g., 155, 165, or 175) to generate a local-clock signal. Before the link of a segment (e.g., between nodes 150 and 160) is locked, the master port 154 in node 150 may operate at the frequency set by the reference clock 155, and the slave port 162 in node 160 may operate at the frequency set by the reference clock 165. In order to establish the link, a loop-timing mechanism may be executed. According to the loop timing, the slave- port PLL 166 may act such that the local clock is locked to the master clock in node 150 (e.g., at the frequency set by the reference clock 155) by recovering the clock frequency of the master port 154 through the link segment L56 connecting the port 150 to the port 160. Therefore, after the link is established, the slave port 162 may operate at the frequency of the reference clock 155, whereas the master port 164 of the same node (e.g., 160) may operate at the frequency of the reference clock 165. The loop-timing mechanism is part of IEEE 802.3 standard and is similarly executed by other segments of the multi-segment link 100B. For example, the slave port 172 may have to operate at the frequency of the reference clock 165 after the link L67 is established. As a result, two network segments may have to be operating at two different clock frequencies, which is not desirable. Therefore, the two or more ports of each node need to be synchronized, as addressed by the subject technology and described in greater detail herein.
The digital PLL 215 may store in the frequency register 216 frequency data including a delta frequency (Δf) that is a difference between the recovered-clock frequency of the master port of the other device and the local-clock frequency of the dual-port device 200. It is understood that the Δf is of the order of a few ppm (e.g., 10 ppm). The digital PLL 225 may be still operating at the local-clock frequency of the dual-port device 200. An objective of the subject technology is to synchronize the master port 220 to the slave port 210. The synchronization may be implemented by coupling the frequency register 226 to the frequency register 216. In one or more implementations of the subject technology, the synchronization of the master port 220 with the slave port 210 may be performed by the processing module 230. In this role, the processing module 230 may couple the frequency register 226 to the frequency register 216 through the summation block 222 and make the frequency register 226 to follow the frequency of the register 216 in terms of operating frequency. In one or more implementations, the processing module 230 may include a smoothing filter, as discussed in further detail below.
The programmable control logic 240 may include programmable registers and may allow designation of the two ports (e.g., in case of a multiport device) that are to be synchronized. In some implementations, the programmable control logic 240 may automatically detect the ports to be synchronized. The programmable control logic 240 may further allow enabling and disabling the synchronization feature. For example, in multiport chips with more than two ports, synchronized pairs of ports may be determined by registers of the programmable control logic 240. More than one master port may be synchronized with a single slave port through the control registers. The frequency synchronization circuit (e.g., summation block 222 and the processing module 230) may be activated or deactivated as the link on the slave port 210 (e.g., to another multiport device) is established or lost. In one or more implementations, the activation or deactivation of the frequency synchronization circuit may be performed by the programmable control logic 240. The programmable control logic 240 and the processing module 230 can be implemented in hardware. In one or more implementations, the processing module 230 can be implemented in software executable by, for example, a processor of the multiport device 200.
In one or more aspects, the processing module 230 may be implemented by, but is not limited to, an infinite impulse response (IIR) filter, such as a leaky integrator. The leaky integrator may include an N-bit register 234, a divide-by-2″ block 236, a summation block 235, and a subtraction module 238. A time constant of the leaky integrator may be defined by the positive integer n of the divide-by-2″ block 236. The content of the frequency register 216 (e.g., signal 218) may be added by the summation block 235 to a signal 239 to generate a signal 219, which is stored in the N-bit register 234. The instantaneous content (e.g., signal 231) of the N-bit register 234 may be divided by 2″ by the divide-by-2″ block 236 to generate signal 237. The signal 237 may be subtracted from the signal 231, by the subtraction block 238 to generate the signal 239.
The PHY chip 310 may include a reference clock generator and programmable control logic (e.g., similar to 240 of
Although the various aspects of the subject technology disclosed herein are implemented within integrated multiport chips, they may also be implemented on ports of different chips on the same board or even ports on different boards with proper extension of the disclosed circuits and logics.
Those of skill in the art would appreciate that the various illustrative blocks, modules, elements, components, and methods described herein may be implemented as electronic hardware, computer software, or combinations of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, and methods have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application. Various components and blocks may be arranged differently (e.g., arranged in a different order, or partitioned in a different way) all without departing from the scope of the subject technology.
As used herein, the phrase “at least one of” preceding a series of items, with the term “and” or “or” to separate any of the items, modifies the list as a whole, rather than each member of the list (i.e., each item). The phrase “at least one of” does not require selection of at least one of each item listed; rather, the phrase allows a meaning that includes at least one of any one of the items, and/or at least one of any combination of the items, and/or at least one of each of the items. By way of example, the phrases “at least one of A, B, and C” or “at least one of A, B, or C” each refer to only A, only B, or only C; any combination of A, B, and C; and/or at least one of each of A, B, and C.
A phrase such as “an aspect” does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology. A disclosure relating to an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples of the disclosure. A phrase such as an “aspect” may refer to one or more aspects and vice versa. A phrase such as an “embodiment” does not imply that such embodiment is essential to the subject technology or that such embodiment applies to all configurations of the subject technology. A disclosure relating to an embodiment may apply to all embodiments, or one or more embodiments. An embodiment may provide one or more examples of the disclosure. A phrase such an “embodiment” may refer to one or more embodiments and vice versa. A phrase such as a “configuration” does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. A disclosure relating to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples of the disclosure. A phrase such as a “configuration” may refer to one or more configurations and vice versa.
The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” or as an “example” is not necessarily to be construed as preferred or advantageous over other embodiments. Furthermore, to the extent that the term “include,” “have,” or the like is used in the description or the claims, such term is intended to be inclusive in a manner similar to the term “comprise” as “comprise” is interpreted when employed as a transitional word in a claim.
All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.”
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. Pronouns in the masculine (e.g., his) include the feminine and neuter gender (e.g., her and its) and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the subject disclosure.
Tazebay, Mehmet Vakif, Chini, Ahmad
Patent | Priority | Assignee | Title |
Patent | Priority | Assignee | Title |
8819161, | Jan 18 2010 | CAVIUM INTERNATIONAL; MARVELL ASIA PTE, LTD | Auto-syntonization and time-of-day synchronization for master-slave physical layer devices |
20100150288, | |||
20130308658, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
May 01 2013 | CHINI, AHMAD | Broadcom Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 030421 | /0451 | |
May 02 2013 | TAZEBAY, MEHMET VAKIF | Broadcom Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 030421 | /0451 | |
May 08 2013 | Broadcom Corporation | (assignment on the face of the patent) | / | |||
Feb 01 2016 | Broadcom Corporation | BANK OF AMERICA, N A , AS COLLATERAL AGENT | PATENT SECURITY AGREEMENT | 037806 | /0001 | |
Jan 19 2017 | BANK OF AMERICA, N A , AS COLLATERAL AGENT | Broadcom Corporation | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS | 041712 | /0001 | |
Jan 20 2017 | Broadcom Corporation | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 041706 | /0001 | |
May 09 2018 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | MERGER SEE DOCUMENT FOR DETAILS | 047229 | /0408 | |
Sep 05 2018 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT NUMBER 9,385,856 TO 9,385,756 PREVIOUSLY RECORDED AT REEL: 47349 FRAME: 001 ASSIGNOR S HEREBY CONFIRMS THE MERGER | 051144 | /0648 | |
Sep 05 2018 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE PREVIOUSLY RECORDED ON REEL 047229 FRAME 0408 ASSIGNOR S HEREBY CONFIRMS THE THE EFFECTIVE DATE IS 09 05 2018 | 047349 | /0001 |
Date | Maintenance Fee Events |
Oct 15 2018 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Oct 06 2022 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Apr 14 2018 | 4 years fee payment window open |
Oct 14 2018 | 6 months grace period start (w surcharge) |
Apr 14 2019 | patent expiry (for year 4) |
Apr 14 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
Apr 14 2022 | 8 years fee payment window open |
Oct 14 2022 | 6 months grace period start (w surcharge) |
Apr 14 2023 | patent expiry (for year 8) |
Apr 14 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
Apr 14 2026 | 12 years fee payment window open |
Oct 14 2026 | 6 months grace period start (w surcharge) |
Apr 14 2027 | patent expiry (for year 12) |
Apr 14 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |