IP Library Granted Patent US 11,005,585
Granted Patent B1
US 11,005,585 · App. 16/778,363 · Granted May 11, 2021

Transporting client timing information across a network

Inventors: Kamatchi S. Gopalakrishnan (Dublin, CA); Rajagopalan Subbiah (San Jose, CA); Julian Kazimierz Lucek (Ipswich, GB)
Assignee: Juniper Networks, Inc.
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 11,005,585
App. No.
16/778,363
Granted
May 11, 2021
Kind
B1
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 (66)

1. A method, comprising:

receiving, by a network device of a network, a timing control packet from a first client device;

determining, by the network device, that the network device is in a synchronized state relative to a network grandmaster clock;

modifying, by the network device, a first field of a header of the timing control packet to indicate that the network device is in the synchronized state;

modifying, by the network device, 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; and

forwarding, by the network device and via the network, the timing control packet toward a second client device.

2. The method of claim 1 , wherein the first field comprises a first portion and a second portion,

wherein the first portion includes a first indication that the network device is in the synchronized state, and

wherein the second portion includes a second indication of one or more attributes of the second field.

3. The method of claim 2 , wherein the one or more attributes include a location of the second field within the header of the timing control packet or include a quantity of bits associated with the second field.

4. The method of claim 1 , wherein the timing control packet comprises a precision time protocol control packet.

5. The method of claim 1 , further comprising:

parsing the timing control packet to determine that the timing control packet includes client timing information for synchronizing the second client device with the first client device,

wherein the network device determines whether the network device is in the synchronized state based on determining that the timing control packet includes the client timing information.

6. The method of claim 1 , further comprising:

receiving, from the network grandmaster clock, network timing information to synchronize the network device with the network grandmaster clock; and

updating a clock of the network device based on the network timing information,

wherein the network device determines that the network device is in the synchronized state based on updating the clock of the network device.

7. The method of claim 1 , further comprising:

modifying a third field of the header of the timing control packet to identify the network device as an ingress network device for the timing control packet.

8. A method, comprising:

receiving, by an egress network device of a network, a timing control packet from an ingress network device via the network;

identifying, by the egress network device and within a first field of a header of the timing control packet, a first indication that indicates that the ingress network device was in a synchronized state when the ingress network device received the timing control packet from a first client device;

identifying, by the egress network device and within a second field of the header of the timing control packet, a second indication that indicates a time at which the ingress network device received the timing control packet from the first client device;

determining, by the egress network device, that the ingress network device is in the synchronized state;

determining, by the egress network device, a time at which the egress network device will transmit the timing control packet;

determining, by the egress network device, a resident time of the timing control packet on the network based on the second indication and the time at which the egress network device will transmit the timing control packet;

modifying, by the egress network device, a third field of the header of the timing control packet to indicate the resident time of the timing control packet on the network; and

forwarding, by the egress network device, the timing control packet toward a second client device.

9. The method of claim 8 , wherein the first field comprises a first portion and a second portion,

wherein the first portion indicates that the ingress network device was in the synchronized state, and

wherein the second portion indicates a location of the second field within the header of the timing control packet or indicates a quantity of bits associated with the second field.

10. The method of claim 8 , wherein the synchronized state is a first synchronized state; and

the method further comprising:

receiving, from a network grandmaster clock, network timing information to synchronize the egress network device with the network grandmaster clock; and

updating a clock of the ingress network device based on the network timing information,

wherein the egress network device determines that the egress network device is in a second synchronized state based on updating the clock of the egress network device.

11. The method of claim 8 , wherein the network comprises a multi-protocol label switching network.

12. The method of claim 8 , wherein the egress network device provides an interface between the second client device and the network, and

wherein the ingress network device provides an interface between the network and the first client device.

13. The method of claim 8 , further comprising, before forwarding the timing control packet toward the second client device, setting the first field and the second field to a null state.

14. A system comprising:

an ingress network device of a network to:

receive a timing control packet from a first client device;

determine that the ingress network device is in a first synchronized state;

modify a header of the timing control packet to include:

a first indication that the ingress network device is in the first synchronized state; and

a second indication that indicates a time at which the ingress network device received the timing control packet from the first client device; and

forward the timing control packet toward an egress network device via the network; and

the egress network device of the network to:

receive the timing control packet via the network;

identify, within the header of the timing control packet, the first indication and the second indication;

determine that the egress network device is in a second synchronized state;

determine a resident time of the timing control packet on the network based on the second indication and a time at which the egress network device will transmit the timing control packet;

modify the header of the timing control packet to indicate the resident time of the timing control packet on the network; and

forward the timing control packet toward a second client device.

15. The system of claim 14 , wherein the ingress network device is further to modify the header of the timing control packet to indicate one or more attributes of the header.

16. The system of claim 15 , wherein the one or more attributes include a location of the second indication within the header of the timing control packet or include a quantity of bits associated with the second indication.

17. The system of claim 14 , wherein the timing control packet comprises a precision time protocol control packet.

18. The system of claim 14 , wherein the ingress network device is further to:

parse the timing control packet to determine that the timing control packet includes client timing information for synchronizing the second client device with the first client device,

wherein the ingress network device initiates a determination of whether the ingress network device is in the first synchronized state based on determining that the timing control packet includes the client timing information.

19. The system of claim 14 , wherein the ingress network device is further to:

modify the header of the timing control packet to identify the ingress network device as the ingress network device for the timing control packet.

20. The system of claim 14 , wherein the ingress network device provides an interface between the first client device and the network, and

wherein the egress network device provides an interface between the second client device and the network.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 11, 2024
From: JUNIPER NETWORKS, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 067692/0250 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2020
From: GOPALAKRISHNAN, KAMATCHI S.; SUBBIAH, RAJAGOPALAN; LUCEK, JULIAN KAZIMIERZ
To: JUNIPER NETWORKS, INC.
Reel/Frame 051686/0066 →
Continuity (1)
Provisional Application 62955938 · Dec 31, 2019
Cited By (5)
US 12,273,912 US 12,301,340 US 12,425,996 US 12,537,735 US 12,634,852