IP Library Granted Patent US 12,301,340
Granted Patent B2
US 12,301,340 · App. 18/332,059 · Granted May 13, 2025

Transporting client timing information across a network

Inventors: Kamatchi S. Gopalakrishnan (Dublin, CA); Rajagopalan Subbiah (San Jose, CA); Julian Kazimierz Lucek (Ipswich, GB)
Assignee: Hewlett Packard Enterprise Development LP
H04J3/0667
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,301,340
App. No.
18/332,059
Granted
May 13, 2025
Kind
B2
Abstract

A network device may receive a timing control packet from a first client device. The network device may determine that the network device is in a synchronized state relative to a network grandmaster clock. The network device may modify a first field of a header of the timing control packet to indicate that the network device is in a synchronized state. The network device may modify a second field of the header of the timing control packet to indicate a time at which the network device received the timing control packet from the first client device. The network device may forward, via the network, the timing control packet toward a second client device.

Claims (59)

1. A method, comprising:

identifying, by a network device and based on a timing control packet, information that indicates a first time associated with receipt of the timing control packet;

determining, by the network device, a second time associated with when the network device expects to transmit the timing control packet,

wherein the second time is associated with at least one of:

a time at which the network device expects the timing control packet to exit the network device,

a time at which the network device expects the timing control packet to reach a port for transmission toward another device, or

a time at which the network device expects the timing control packet to reach a particular component of the network device;

determining, by the network device and based on the information that indicates the first time and information that indicates the second time, a resident time associated with the timing control packet; and

forwarding, by the network device, a modified timing control packet that indicates the resident time.

2. The method of claim 1 , wherein the timing control packet is received from an ingress network device of a network associated with the network device.

3. The method of claim 1 , wherein the first time is associated with another network device receiving the timing control packet, and

wherein the timing control packet is received by the network device from the other network device.

4. The method of claim 1 , wherein the first time is associated with another network device receiving the timing control packet from a first client device, and

wherein the modified timing control packet is forwarded to a second client device.

5. The method of claim 1 , wherein the modified timing control packet is based on modifying one or more fields of the timing control packet to a null state.

6. The method of claim 1 , wherein the timing control packet includes at least one of:

information indicating that another network device, from which the timing control packet was received, was in a synchronized state when the other device received the timing control packet, or

information indicating a location within a header, of the timing control packet, that indicates the first time.

7. The method of claim 1 , wherein the resident time is determined further based on determining that the network device is in a synchronized state.

8. A network device, comprising:

one or more memories; and

one or more processors to:

identify, based on a timing control packet, information that indicates a first time associated with receipt of the timing control packet;

determine a second time associated with when the network device expects to transmit the timing control packet,

wherein the second time is associated with at least one of:

a time at which the network device expects the timing control packet to exit the network device,

a time at which the network device expects the timing control packet to reach a port for transmission toward another device, or

a time at which the network device expects the timing control packet to reach a particular component of the network device;

determine, based on the information that indicates the first time and information that indicates the second time, a resident time associated with the timing control packet; and

forward a modified timing control packet that indicates the resident time.

9. The network device of claim 8 , wherein the timing control packet is received from an ingress network device of a network associated with the network device.

10. The network device of claim 8 , wherein the first time is associated with another network device receiving the timing control packet, and

wherein the timing control packet is received by the network device from the other network device.

11. The network device of claim 8 , wherein the first time is associated with another network device receiving the timing control packet from a first client device, and

wherein the modified timing control packet is forwarded to a second client device.

12. The network device of claim 8 , wherein the modified timing control packet is based on modifying one or more fields of the timing control packet to a null state.

13. The network device of claim 8 , wherein the timing control packet includes at least one of:

information indicating that another network device, from which the timing control packet was received, was in a synchronized state when the other device received the timing control packet, or

information indicating a location within a header, of the timing control packet, that indicates the first time.

14. The network device of claim 8 , wherein the resident time is determined further based on determining that the network device is in a synchronized state.

15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a network device, cause the network device to:

identify, based on a timing control packet, information that indicates a first time associated with receipt of the timing control packet;

determine a second time associated with when the network device will transmit the timing control packet,

wherein the second time is associated with at least one of:

a time at which the network device expects the timing control packet to exit the network device,

a time at which the network device expects the timing control packet to reach a port for transmission toward another device, or

a time at which the network device expects the timing control packet to reach a particular component of the network device;

determine, based on the information that indicates the first time and information that indicates the second time, a resident time associated with the timing control packet; and

forward a modified timing control packet that indicates the resident time.

16. The non-transitory computer-readable medium of claim 15 , wherein the timing control packet is received from an ingress network device of a network associated with the network device.

17. The non-transitory computer-readable medium of claim 15 , wherein the first time is associated with another network device receiving the timing control packet, and

wherein the timing control packet is received by the network device from the other network device.

18. The non-transitory computer-readable medium of claim 15 , wherein the first time is associated with another network device receiving the timing control packet from a first client device, and

wherein the modified timing control packet is forwarded to a second client device.

19. The non-transitory computer-readable medium of claim 15 , wherein the modified timing control packet is based on modifying one or more fields of the timing control packet to a null state.

20. The non-transitory computer-readable medium of claim 15 , wherein the timing control packet includes at least one of:

information indicating that another network device, from which the timing control packet was received, was in a synchronized state when the other device received the timing control packet, or

information indicating a location within a header, of the timing control packet, that indicates the first time.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 14, 2024
From: GOPALAKRISHNAN, KAMATCHI S.; SUBBIAH, RAJAGOPALAN; LUCEK, JULIAN KAZIMIERZ
To: JUNIPER NETWORKS, INC.
Reel/Frame 067729/0240 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 11, 2024
From: JUNIPER NETWORKS, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 067692/0205 →
Continuity (4)
Continuation 17302202 · Apr 27, 2021
Continuation 16778363 · Jan 31, 2020
Provisional Application 62955938 · Dec 31, 2019
Related Publication 20230327792A1 · Oct 12, 2023
References Cited (61)
US 6697382B1 · Eatherton · 2004 [cited by applicant]
US 6970935B1 · Maes · 2005 [cited by applicant]
US 8462821B1 · Sagarwala et al. · 2013 [cited by applicant]
US 8504820B2 · Lu et al. · 2013 [cited by applicant]
US 8718482B1 · Roberts · 2014 [cited by examiner]
US 8879552B2 · Zheng et al. · 2014 [cited by applicant]
US 9209921B2 · Bui et al. · 2015 [cited by applicant]
US 9407733B1 · Mizrahi · 2016 [cited by applicant]
US 9871648B2 · Lanzone et al. · 2018 [cited by applicant]
US 10341083B2 · Mayer et al. · 2019 [cited by applicant]
US 11005585B1 · Gopalakrishnan et al. · 2021 [cited by applicant]
US 11025404B2 · Pietiläinen · 2021 [cited by applicant]
US 11677486B2 · Gopalakrishnan et al. · 2023 [cited by applicant]
US 20020080829A1 · Ofek et al. · 2002 [cited by applicant]
US 20050226204A1 · Uehara · 2005 [cited by applicant]
US 20070115814A1 · Gerla et al. · 2007 [cited by applicant]
US 20070237177A1 · Endo et al. · 2007 [cited by applicant]
US 20080056307A1 · DeCUSATIS · 2008 [cited by applicant]
US 20080181114A1 · Fourcand · 2008 [cited by applicant]
US 20100040369A1 · Zhao et al. · 2010 [cited by applicant]
US 20100085990A1 · Belhadj · 2010 [cited by examiner]
US 20100118721A1 · Sakurada et al. · 2010 [cited by applicant]
US 20110051754A1 · Lansdowne · 2011 [cited by examiner]
US 20110093609A1 · Blom et al. · 2011 [cited by applicant]
US 20110305307A1 · Wang et al. · 2011 [cited by applicant]
US 20120128011A1 · Holmeide · 2012 [cited by examiner]
US 20120137013A1 · Steindl · 2012 [cited by applicant]
US 20120300795A1 · Joergensen · 2012 [cited by examiner]
US 20130100832A1 · Flinn · 2013 [cited by examiner]
US 20130301634A1 · Ehlers et al. · 2013 [cited by applicant]
US 20130315606A1 · Lanzone · 2013 [cited by examiner]
US 20140177653A1 · Tzeng · 2014 [cited by applicant]
US 20150063375A1 · Tzeng et al. · 2015 [cited by applicant]
US 20150093109A1 · Joergensen · 2015 [cited by applicant]
US 20160285575A1 · Holmeide · 2016 [cited by applicant]
US 20170324497A1 · Ruffini et al. · 2017 [cited by applicant]
US 20180337833A1 · Attarwala · 2018 [cited by applicant]
US 20190036804A1 · Mihelic · 2019 [cited by examiner]
US 20200099734A1 · Sun · 2020 [cited by applicant]
US 20200267673A1 · Joseph et al. · 2020 [cited by applicant]
CN 1728717A · 2006 [cited by applicant]
CN 103098396A · 2013 [cited by applicant]
CN 104170291A · 2014 [cited by applicant]
CN 104471883A · 2015 [cited by applicant]
CN 107667491A · 2018 [cited by applicant]
CN 109565435A · 2019 [cited by applicant]
EP 2437416A2 · 2012 [cited by applicant]
EP 2530860A1 · 2012 [cited by applicant]
EP 2541815A1 · 2013 [cited by applicant]
WO 2010139210A1 · 2010 [cited by applicant]
WO WO2012104326A1 · 2012 [cited by examiner]
WO 2015135874A1 · 2015 [cited by applicant]
WO 2016198102A1 · 2016 [cited by applicant]
WO WO2018104237A1 · 2018 [cited by examiner]
Editor., et al., “Draft G.8264 (G.pacmod) V0.3 (for consent)”, 3GPP draft 487R1, Mar. 18, 2008, vol. RAN WG3 (Shenzhen), 32 pages, XP050163788. [cited by applicant]
Extended European Search Report for Application No. EP20165152.8, mailed on Sep. 28, 2020, 7 pages. [cited by applicant]
IEEE Instrumentation and Measurement Society “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems”, IEEE Std 1588TM-2008, Jul. 24, 2008, 289 pages. [cited by applicant]
Pallec M.L., et al., “Time and Frequency Distribution Over Packet Switched Networks”, Bell Labs Technical Journal, Jul. 1, 2009, vol. 14 (2), pp. 131-153. [cited by applicant]
3GPP TR 23.734 V16.2.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhancement of 5G System (5GS) for Vertical and Local Area Network (LAN) Services (Release… [cited by applicant]
Extended European Search Report for Application No. EP23163558.2, mailed on Jun. 20, 2023, 10 Pages. [cited by applicant]
International Telecommunication Union., “Distributed Boundary and Transparent Clocks,” Study Group 15—Contribution 811, Study Period 2009-2012, May 2010, 4 pages. XP017447988. [cited by applicant]