Source: https://patents.google.com/patent/US8982912B2/en
Timestamp: 2019-07-18 13:50:20
Document Index: 309721888

Matched Legal Cases: ['Application No. 60', 'Application No. 60', 'Application No. 60', 'art 3', 'art 3', 'art 3', 'art 3', 'art 3', 'art 3']

US8982912B2 - Inter-packet gap network clock synchronization - Google Patents
US8982912B2
US8982912B2 US13/624,625 US201213624625A US8982912B2 US 8982912 B2 US8982912 B2 US 8982912B2 US 201213624625 A US201213624625 A US 201213624625A US 8982912 B2 US8982912 B2 US 8982912B2
US13/624,625
US20130051407A1 (en
2012-09-21 Application filed by FutureWei Technologies Inc filed Critical FutureWei Technologies Inc
2012-09-21 Priority to US13/624,625 priority patent/US8982912B2/en
2012-09-26 Assigned to FUTUREWEI TECHNOLOGIES, INC. reassignment FUTUREWEI TECHNOLOGIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FOURCAND, SERGE FRANCOIS
2013-02-28 Publication of US20130051407A1 publication Critical patent/US20130051407A1/en
2015-03-17 Publication of US8982912B2 publication Critical patent/US8982912B2/en
A network component comprising a processor configured to receive a data stream from an upstream node, wherein the data stream comprises a plurality of Ethernet packets and a synchronization request comprising a timestamp, synchronize a clock with the timestamp, and transmit a response to the upstream node, wherein the data stream has the same bandwidth as a second data stream that does not have the synchronization request and the timestamp.
This application is a divisional of U.S. patent application Ser. No. 11/735,590, now U.S. Pat. No. 8,295,310, filed Apr. 16, 2007 and entitled “Inter-Packet Gap Network Clock Synchronization,” which claims priority to U.S. Provisional Application No. 60/826,764 filed Sep. 25, 2006 and entitled “System for TDM Data Transport Over Ethernet Interfaces,” U.S. Provisional Application No. 60/857,741 filed Nov. 8, 2006 and entitled “TDM Data Transport Over Ethernet,” and U.S. Provisional Application No. 60/886,833 filed Jan. 26, 2007 and entitled “Closed Loop Clock Synchronization,” all of which are by Serge F. Fourcand and are incorporated herein by reference as if reproduced in their entirety.
In one embodiment, the disclosure includes a network component comprising a processor, wherein the processor is configured to receive a data stream from an upstream node, wherein the data stream comprises a plurality of Ethernet packets and a synchronization request comprising a timestamp, synchronize a clock with the timestamp, and transmit a response to the upstream node, wherein the data stream has the same bandwidth as a second data stream that does not have the synchronization request and the timestamp.
In another embodiment, the disclosure includes a network component comprising a processor configured to receive a clock synchronization data in a data stream, wherein the clock synchronization data comprises a timestamp and a control header that indicates a requested operational mode, determine whether the network component supports the requested operational mode, and synchronize a clock with the clock synchronization data when the network component supports the operational mode, wherein the clock synchronization data is located in a gap between two of the Ethernet packets.
In yet another embodiment, the disclosure includes a method comprising receiving a first synchronization packet located in an inter-packet gap (IPG) of a first data stream at a downstream node, wherein the downstream node supports an operational mode indicated in the synchronization packet, synchronizing a clock with the synchronization packet, wherein the synchronization packet comprises a timestamp and a control header, and transmitting a second synchronization packet to an upstream node, wherein the data stream has the same bandwidth as a second data stream that does not have the synchronization packet and the timestamp in the IPG.
FIG. 9B illustrates a timeline of a successful initiation of frequency-synchronized and phase-aligned communication between the upstream node 902 and the downstream node 904 Like FIG. 5B, FIG. 9B contains a separate timeline for each of the upstream node 902 and the downstream node 904, where each timeline represents time relative to the corresponding node. Specifically, the time relative to the upstream node 902 may be shown above the timeline for the upstream node 902 and indicated by TUx, where x may be an integer. The time relative to the downstream node 904 may be shown below the timeline for the downstream node 904 and indicated by TDx, where x may be an integer. An absolute time may be shown between the two timelines and indicated by Tx, where x may be an integer. The time relative to the upstream node 902 and the time relative to the downstream node 904 may not necessarily be equal to the absolute time.
receive a first data stream from an upstream node, wherein the data stream comprises a plurality of Ethernet packets and a synchronization request comprising a timestamp;
synchronize a clock with the timestamp; and
transmit a response to the synchronization request to the upstream node in a second data stream having a same bandwidth as the first data stream,
wherein the timestamp is absent from the response to the synchronization request.
2. The network component of claim 1, wherein the second data stream comprises a second plurality of Ethernet packets to the upstream node, and wherein the response is located in a gap between two of the second plurality of Ethernet packets.
3. The network component of claim 1, wherein the timestamp is associated with a second clock in the upstream node, and wherein the clock is synchronized with the second clock in frequency.
4. The network component of claim 3, wherein only a single timestamp is required to synchronize the clock with the second clock.
5. The network component of claim 1, wherein the synchronization request comprises a requested operational mode, and wherein logic further causes the processor to transition to the requested operational mode.
6. The network component of claim 1, wherein the synchronization request comprises a requested operational mode, and wherein logic further causes the processor to maintain a current operational mode when the requested operational mode is not supported.
7. The network component of claim 1, wherein the synchronization request indicates a second quality of a second clock in the upstream node, and wherein the response comprises a second synchronization request when a quality of the clock is greater than the second quality of the second clock.
8. The network component of claim 1, wherein the synchronization request is located in a gap between two of the Ethernet packets.
9. The network component of claim 8, wherein the synchronization request is not located in every gap between the Ethernet packets.
10. The network component of claim 8, wherein the synchronization request comprises a first bit that indicates the synchronization request is a request for clock synchronization.
11. The network component of claim 8, wherein the upstream node is configured to add the timestamp to the synchronization request and transmit the synchronization request in the data stream, and wherein the timestamp corresponds to an upstream clock associated with the upstream node.
12. The network component of claim 11, wherein the timestamp synchronizes the upstream clock with the clock, and wherein logic further causes the processor to establish a synchronization window with the upstream node.
receive a clock synchronization data in a data stream, wherein the clock synchronization data comprises a timestamp and a control header that indicates a requested operational mode;
determine whether the network component supports the requested operational mode; and
synchronize a clock with the clock synchronization data when the network component supports the requested operational mode,
wherein the clock synchronization data is located in a gap between two Ethernet packets.
14. The network component of claim 13, wherein the clock is synchronized using the timestamp, and wherein the processor is further configured to transmit a response to an upstream node.
15. The network component of claim 13, wherein a first idle character occurs before the clock synchronization data and a second idle character occurs after the clock synchronization data.
16. The network component of claim 13, wherein the clock synchronization data is about four octets long, wherein a first bit in the control header indicates whether the clock synchronization data is a request or an acknowledgement, and wherein a second bit indicates the requested operational mode.
receiving a first synchronization packet located in an inter-packet gap (IPG) of a data stream at a downstream node, wherein the downstream node supports an operational mode indicated in the synchronization packet;
synchronizing a clock with the first synchronization packet, wherein the first synchronization packet comprises a timestamp and a control header; and
transmitting a second synchronization packet to an upstream node in a second data stream,
wherein the timestamp in the first synchronization packet is absent from the second synchronization packet.
18. The method of claim 17, wherein the control header indicates whether the first synchronization packet is a request for clock synchronization or an acknowledgement for clock synchronization, wherein the control header indicates the operational mode, and wherein the first synchronization packet is discarded when the downstream node does not support the operational mode.
19. The method of claim 17, wherein the timestamp is associated with the clock in the upstream node, and wherein the clock is synchronized with a second clock in frequency.
20. The method of claim 17, wherein the second synchronization packet comprises a second timestamp, wherein the second timestamp is associated with the clock in the upstream node, and wherein the second synchronization packet is located in the inter-packet gap (IPG) of a third data stream.
US13/624,625 2006-09-25 2012-09-21 Inter-packet gap network clock synchronization Active 2027-11-26 US8982912B2 (en)
US11/735,590 Division US8295310B2 (en) 2006-09-25 2007-04-16 Inter-packet gap network clock synchronization
US20130051407A1 US20130051407A1 (en) 2013-02-28
US8982912B2 true US8982912B2 (en) 2015-03-17
CN106788855B (en) * 2015-11-23 2018-12-07 华为技术有限公司 A flexible optical transmission network Ethernet service carrier method and apparatus
Final Office Action dated Jan. 14, 2013,15 pages, U.S. Appl. No. 11/735,596 filed on Apr. 16, 2007.
Final Office Action dated Jan. 4, 2013, 27 pages, U.S. Appl. No. 13/271,691, filed on Oct. 12, 2011.
Fourcand, Serge F.; U.S. Appl. No. 13/649,820; Title "System for TMD Data Transport Over Ethernet Interfaces"; filed Oct. 11, 2012.
IEEE Standard for Information Technology-Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirement Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications-IEEE Computer Society, IEEE Std. 802.3-2008, Dec. 26,2008-Section 5.
IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirement Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications—IEEE Computer Society, IEEE Std. 802.3-2008, Dec. 26,2008—Section 5.
IEEE Standard for Information Technology-Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirement Part 3; Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications-IEEE Computer Society, IEEE Std. 802.3-2008, Dec. 26, 2008-Section 2.
IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirement Part 3; Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications—IEEE Computer Society, IEEE Std. 802.3-2008, Dec. 26, 2008—Section 2.
IEEE Standards for Information Technology-Telecommunications and Information Exchange Between Systems-Local and Metropolitan Area Networks-Specific Requirement Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications-IEEE Computer Society, IEEE Std. 802.3-2008, Dec. 26, 2008-Section 1.
IEEE Standards for Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirement Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications—IEEE Computer Society, IEEE Std. 802.3-2008, Dec. 26, 2008—Section 1.
Notice of Allowance dated Apr. 11, 2011 8 pages, U.S. Appl. No. 11/735,602, filed on Apr. 16, 2007.
Notice of Allowance dated Aug. 1, 2013, 12 pages, U.S. Appl. No. 12/842,794, filed on Jul. 23, 2010.
Notice of Allowance dated Jul. 19, 2010, 12 pages, U.S. Appl. No. 11/971,386, filed on Jan. 9, 2008.
Notice of Allowance dated Jul. 30, 2013, 9 pages, U.S. Appl. No. 11/737,800, filed on Apr. 20, 2007.
Notice of Allowance dated Jun. 20, 2013, 40 pages, U.S. Appl. No. 13/271,691, filed on Oct. 12, 2011.
Notice of Allowance dated Jun. 21, 2012, 11 pages, U.S. Appl. No. 11/735,590, filed on Apr. 16, 2007.
Notice of Allowance dated May 22, 2013, 18 pages, U.S. Appl. No. 11/735,592, filed on Apr. 16, 2007.
Notice of Allowance dated Nov. 26, 2013, 38 pages, U.S. Appl. No. 11/735,596, filed on Apr. 16, 2007.
Notice of Allowance dated Oct. 16, 2012, 42 pages U.S. Appl. No. 12/691,367, filed on Jan. 21, 2010.
Office Action dated Apr. 24, 2013, 43 pages, U.S. Appl. No. 13/162,803, filed on Jun. 17, 2011.
Office Action dated Apr. 3, 2013, 58 pages, U.S. Appl. No. 12/842,794, filed on Jul. 23, 2010.
Office Action dated Aug. 2, 2013, 5 pages, U.S. Appl. No. 13/162,803, filed on Jun. 17, 2011.
Office Action dated Aug. 6, 2012, 25 pages, U.S. Appl. No. 11/735,596, filed on Apr. 16, 2007.
Office Action dated Aug. 7, 2009, 10 pages, U.S. Appl. No. 11/735,590, filed on Apr. 16, 2007.
Office Action dated Dec. 26, 2013, 30 pages, U.S. Appl. No. 12/862,521, filed on Aug. 24, 2010.
Office Action dated Dec. 30, 2009, 22 pages, U.S. Appl. No. 11/735,590, filed on Apr. 16, 2007.
Office Action dated Feb. 1, 2011, 10 pages, U.S. Appl. No. 11/735,590, filed on Apr. 16, 2007.
Office Action dated Feb. 1, 2013, 4 pages, U.S. Appl. No. 12/862,521, filed on Aug. 24, 2010.
Office Action dated Jan. 11, 2011, 10 pages, U.S. Appl. No. 11/735,590, filed on Apr. 16, 2007.
Office Action dated Jan. 23, 2012, 12 pages, U.S. Appl. No. 11/735,592, filed on Apr. 16, 2007.
Office Action dated Jul. 1, 2011, 18 pages, U.S. Appl. No. 11/737,800, filed on Apr. 20, 2007.
Office Action dated Jul. 3, 2014, 6 pages, U.S. Appl. No. 13/649,820, filed Oct. 11, 2012.
Office Action dated Jun. 17, 2011, 20 pages, U.S. Appl. No. 11/735,591, filed on Apr. 16, 2007.
Office Action dated Jun. 18, 2013, 18 pages, U.S. Appl. No. 12/842,794, filed on Jul. 23, 2010.
Office Action dated Jun. 20, 2012, 44 pages, U.S. Appl. No. 13/271,691, filed on Oct. 12, 2011.
Office Action dated Jun. 3, 2011, 17 pages, U.S. Appl. No. 11/735,590, filed on Apr. 16, 2007.
Office Action dated Jun. 4, 2013, 6 pages, U.S. Appl. No. 13/162,803, filed on Jun. 17, 2011.
Office Action dated Jun. 9, 2010, 13 pages, U.S. Appl. No. 11/735,590, filed on Apr. 16, 2007.
Office Action dated Mar. 13, 2013, 27 pages, U.S. Appl. No. 11/737,800, filed on Apr. 20, 2007.
Office Action dated Mar. 5, 2014, 20 paages, U.S. Appl. No. 13/162,803, filed on Jun. 17, 2011.
Office Action dated May 24, 2011, 14 pages, U.S. Appl. No. 11/735,604, filed on Apr. 16, 2007.
Office Action dated May 25, 2012, 8 pages, U.S. Appl. No. 11/737,800, filed on Apr. 20, 2007.
Office Action dated Nov. 21, 2011, 5 pages, U.S. Appl. No. 11/737,800, filed on Apr. 20, 2007.
Office Action dated Oct. 16, 2012, 40 pages, U.S. Appl. No. 12/862,521, filed on Aug. 24, 2010.
Office Action dated Oct. 25, 2011, 29 pages, U.S. Appl. No. 11/735,596, filed on Apr. 16, 2007.
Office Action dated Sep. 18, 2013, 7 pages, U.S. Appl. No. 12/862,521, filed on Aug. 24, 2010.
Office Action dated Sep. 3, 2013, 6 pages, U.S. Appl. No. 11/737,800, filed on Apr. 20, 2007.
Office Action dated Sep. 30, 2009, 15 pages, U.S. Appl. No. 11/735,598, filed on Apr. 16, 2007.
Pratt, G., et al., "Distributed Synchronous Clocking," IEEE Transactions On Parallel and Distrbuted Systems, vol. 6, No. 3, Mar. 1995, pp. 314-328.
US8295310B2 (en) 2012-10-23
GB2399263A (en) 2004-09-08 Clock synchronisation over a packet network
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FOURCAND, SERGE FRANCOIS;REEL/FRAME:029025/0965