IP Library Granted Patent US 8,879,586
Granted Patent B2
US 8,879,586 · App. 13/722,985 · Granted Nov 4, 2014

Inband timestamping

Inventor: Jeffrey Tzeng (Cupertino, CA)
Assignee: Broadcom Corporation
H04J3/0635
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 8,879,586
App. No.
13/722,985
Granted
Nov 4, 2014
Kind
B2
Abstract

Embodiments are directed to timing synchronization between network nodes, such as, for example, based upon IEEE 1588. Example embodiments provide for a node in a IEEE 1588 message exchange to obtain the T3 timestamp without using its host interface to access the physical layer. Methods and systems include aspects of determining an egress timestamp corresponding to a time at which a first packet is transmitted from a physical interface of a first network entity on to a network media, storing the egress timestamp in a memory associated with the physical interface, receiving a second packet at the physical interface, retrieving the egress timestamp from the memory based upon the second packet, and updating the second packet with the retrieved egress timestamp. Embodiments may further include providing the updated second packet for protocol processing in the first network entity, or transmitting the updated second packet from the physical interface on to a network media.

Claims (59)

1. A method, comprising:

determining an egress timestamp corresponding to a time at which a first packet is transmitted from a physical interface of a first network entity;

storing the egress timestamp and an identifier of the first packet in a memory associated with the physical interface;

receiving at the physical interface a second packet from a second network entity;

retrieving the egress timestamp from the memory based upon the received second packet;

updating the second packet with the retrieved egress timestamp; and

providing the updated second packet for protocol processing in the first network entity.

2. The method of claim 1 , wherein the second packet is transmitted by the second network entity in response to receiving the first packet.

3. The method of claim 1 , wherein the retrieving comprises:

determining an identifier for the received second packet; and

accessing the memory using the determined identifier.

4. The method of claim 3 , wherein the determining an identifier comprises:

combining a plurality of header fields from the received second packet to form the identifier.

5. The method of claim 1 , wherein the updating comprises:

writing the retrieved egress timestamp in a reserved field in a header of the received second packet.

6. The method of claim 5 , wherein the updating further comprises:

calculating a checksum after writing the retrieved egress timestamp; and

writing the checksum in the received second packet.

7. The method of claim 1 , wherein the memory and the physical interface are on a network physical layer chip.

8. The method of claim 1 , wherein the retrieving and the updating are performed in a network physical layer chip.

9. The method of claim 1 , wherein the providing comprises:

sending the updated second packet from a network physical layer to a higher layer in response to a request over a host interface to the physical interface.

10. The method of claim 1 , further comprising:

obtaining the egress timestamp and an ingress timestamp from the provided second packet; and

determining a clock correction for the first network entity based at least upon the obtained egress and ingress timestamps.

11. The method of claim 10 , wherein the ingress timestamp corresponds to a time at which the first packet is received at the second network entity.

12. The method of claim 1 , wherein the first and second packets are IEEE 1588 packets, and wherein the egress timestamp corresponds to an egress time of a delay request packet.

13. A method, comprising:

determining an egress timestamp corresponding to a time at which a first packet is transmitted from a physical interface of a first network entity;

storing the egress timestamp in a memory associated with the physical interface;

receiving a second packet at the physical interface;

retrieving the egress timestamp from the memory based upon the received second packet;

updating the second packet with the retrieved egress timestamp; and

transmitting the updated second packet from the physical interface on to a network media.

14. The method of claim 13 , wherein the retrieving and the updating are performed in a network physical layer chip.

15. The method of claim 13 , wherein the retrieving comprises:

determining an identifier for the received second packet; and

accessing the memory using the determined identifier.

16. A system, comprising:

(a) a network physical layer (PHY) configured to be accessed by a central processing unit (CPU) using a host interface, the network PHY comprising:

a physical interface configured to transmit packets to and receive packets from a network medium; and

a timestamp memory,

and the network PHY being further configured to:

determine an egress timestamp corresponding to a time at which a first packet is transmitted from the physical interface to the network medium;

store the egress timestamp in the timestamp memory;

receive at the physical interface a second packet from a second network entity;

retrieve the egress timestamp from the timestamp memory based upon the received second packet;

update the second packet with the retrieved egress timestamp; and

provide the updated second packet for protocol processing on the CPU.

17. The system of claim 16 , further comprising:

(a) a system memory coupled to the CPU; and

(b) a protocol processing module configured to execute on the CPU, and further configured to:

receive the second packet from the network PHY; and

obtain the egress timestamp and one or more other timestamps from the second packet.

18. The system of claim 17 , wherein the protocol processing module is further configured to:

obtain the egress timestamp and an ingress timestamp from the provided second packet; and

determine a clock correction for the first network entity based at least upon the obtained egress and ingress timestamps.

19. The system of claim 18 , wherein the ingress timestamp corresponds to a time the first packet is received at the second network entity.

20. The system of claim 16 , wherein the second packet is transmitted by the second network entity in response to the first packet.

Assignments (7)
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. Recorded Mar 22, 2019
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 051144/0648 →
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. Recorded Oct 29, 2018
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047349/0001 →
MERGER Recorded Oct 4, 2018
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047229/0408 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Feb 3, 2017
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: BROADCOM CORPORATION
Reel/Frame 041712/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2017
From: BROADCOM CORPORATION
To: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
Reel/Frame 041706/0001 →
PATENT SECURITY AGREEMENT Recorded Feb 11, 2016
From: BROADCOM CORPORATION
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 037806/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2012
From: TZENG, JEFFREY
To: BROADCOM CORPORATION
Reel/Frame 029514/0045 →
Continuity (1)
Related Publication 20140177653A1 · Jun 26, 2014