# US 10,097,297 B2 · Apparatus and method for two-way timestamp exchange

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,097,297 B2
- Document ID: US10097297B2
- Status: Granted
- Kind: B2
- Application number: 14/903,666
- Filed: 2013-07-11
- Published: 2016-06-16
- Granted: 2018-10-09
- Earliest claimed: 2013-07-11
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget L M Ericsson (publ)
- Inventors: Qingfeng Yang; Guoliang Gao; Jun Wang
- Web page: https://patentgrep.com/patent/US10097297B2

## CPC

- H04J 3/0667: {Bidirectional timestamps, e.g. NTP or PTP for compensation of clock drift and for compensation of propagation delays (arrangements for monitoring round trip delays in packet switching networks H04L43/0864)}
- H04L 45/24: Multipath
- H04J: MULTIPLEX COMMUNICATION (transmission in general H04B; peculiar to transmission of digital information H04L5/00; systems for the simultaneous or sequential transmission of more than one television signal H04N7/08; in exchanges H04Q11/00; stereophonic systems H04S)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method in a first network entity, which is capable of communicating over a plurality of communication links with a second network entity using a two-way timestamp exchange, comprises the step of receiving at the first network entity a first message from the second network entity. The link on which the first message was received is determined. Based on the determination of the link, a second message is transmitted from the first network entity to the second network entity on the same link.

## Claims

### Claim 1

A method in a first network entity which is capable of communicating over a plurality of communication links with a second network entity using a two-way timestamp exchange, the method comprising the steps of:
transmitting a notification signal to the second network entity for informing the second network entity that the first network entity is configured to specify receiving and transmitting timestamp messages via a same link;
after transmitting the notification signal:
receiving at the first network entity a first timestamp message of the two-way timestamp exchange protocol from the second network entity;
determining on which link the first timestamp message was received; and
based on the determination of the link, transmitting from the first network entity a second timestamp message to the second network entity on the determined link.

### Claim 2 (depends on 1)

A method as claimed in claim 1, wherein the notification signal indicates the same link for receiving and transmitting timestamp messages.

### Claim 3 (depends on 1)

A method as claimed in claim 1, the method further comprising:
determining that the second network entity is not configured to specify receiving and transmitting timestamp messages via a same link, and subsequently, transmitting the second timestamp message to the second network entity on the same link as the first timestamp message was received.

### Claim 4 (depends on 1)

A method as claimed in claim 1, the method further comprising;
determining that the second network entity is configured to specify receiving and transmitting timestamp messages via a same link, and subsequently, the first network entity transmits a first timestamp message on a determined link prior to receipt of a timestamp message from the second network entity.

### Claim 5 (depends on 1)

A method as claimed in claim 1, wherein the first network entity comprises a master node and the second network entity comprises a slave node, the method comprising:
determining that the slave node is not configured to specify receiving and transmitting timestamp messages via a same link, and subsequently, transmitting the second timestamp message to the slave node on the same link as the first timestamp message was received from the slave node.

### Claim 6 (depends on 1)

A method as claimed in claim 1, wherein the first network entity comprises a slave node and the second network entity comprises a slave node.

### Claim 7 (depends on 1)

A method as claimed in claim 1, wherein the determining step is performed in response to detecting a change in the status of at least one of the plurality of communication links between the first network entity and the second network entity.

### Claim 8 (depends on 7)

A method as claimed in claim 7, wherein a change in status comprises:
a change of communication link resulting from a resiliency diversity mechanism that is configured to control the plurality of communication links; and/or
a failure of one or more links of the plurality of communication links that constitute a link aggregation group, LAG, or a multi-chassis link aggregation group, MC-LAG, between the first network entity and the second network entity; or
a change to the communication links that constitute a link aggregation group, LAG, or a multi-chassis link aggregation group, MC-LAG, between the first network entity and second network entity.

### Claim 9 (depends on 1)

A method as claimed in claim 1, wherein the plurality of communication links form at least one of a resiliency diversity mechanism and a link aggregation group.

### Claim 10 (depends on 1)

A method as claimed in claim 1, wherein the two-way timestamp exchange is part of a precision time protocol, PTP.

### Claim 11 (depends on 1)

A computer program product comprising instructions stored on non-transient computer-readable media which, when executed by a processor, perform the steps of claim 1.

### Claim 12

A method in a second network entity which is configured to communicate over a plurality of communication links with a first network entity using a two-way timestamp exchange, the method comprising the steps of:
detecting a change in the status of at least one of the plurality of communication links between the second network entity and the first network entity, and, in response thereto:
determining whether a notification signal is received from the first network entity within a predefined period, the notification signal informing the second network entity that the first network entity will be receiving and transmitting timestamp messages via the same link, and, in the event that the notification signal is not received within the predetermined period:
receiving at the second network entity first timestamp message from the first network entity;
determining on which link the first timestamp message was received; and
based on the determination of the link, transmitting from the second network entity a second timestamp message to the first network entity on the determined link.

### Claim 13 (depends on 12)

A method as claimed in claim 12 whereby, in response to a notification signal being received within the predefined period, the method comprises the steps of:
determining on which link the notification signal was received; and
using this link for subsequent communication of timestamp messages with the first network entity.

### Claim 14

A network entity which is capable of communicating over a plurality of communication links with a second network entity using a two-way timestamp exchange, the network entity comprising:
a receiver;
a transmitter; and
a processor configured to:
cause a notification signal to be transmitted to the second network entity for informing the second network entity that the first network entity is configured to specify receiving and transmitting timestamp messages via a same link:
after causing the notification signal to be transmitted:
determine on which link a first timestamp message is received from the second network entity; and
based on the determination of the link, transmit from the network entity a second timestamp message to the second network entity on the determined link.

### Claim 15 (depends on 14)

A network entity as claimed in claim 14, wherein the processor is further configured to determine the link in response to detecting a change in the status of at least one of the plurality of communication links between the network entity and the second network entity.

### Claim 16 (depends on 14)

A network entity as claimed in claim 14, wherein the plurality of communication links constitute a link aggregation group or wherein the two-way timestamp exchange constitutes part of a precision time protocol, PTP.

### Claim 17

A network entity which is capable of communicating over a plurality of communication links with another network entity using a two-way timestamp exchange, the network entity comprising:
a receiver;
a transmitter; and
a processor configured to:
detect a change in the status of at least one of the plurality of communication links, and, in response thereto:
determine whether a notification signal is received from the another network entity within a predefined period, the notification signal informing the network entity that the another network entity will be receiving and transmitting timestamp messages via the same link; and wherein, in the event that the notification signal is not received within the predetermined period the processor being further configured to:
determine on which link a first timestamp message is received; and
based on the determination of the link, transmit from the network entity a second timestamp message to the another network entity on the same link.

### Claim 18 (depends on 17)

A network entity as claimed in claim 17 whereby, in response to a notification signal being received within the predefined period, the processor is configured to:
determine on which link the notification signal was received; and use this link for subsequent communication of timestamp messages with the another network entity.

### Claim 19

A system comprising a first network entity and a second network entity capable of communicating over a plurality of communication links using a two-way timestamp exchange,
wherein the first network entity comprises a first processor configured to:
detect a change in the status of at least one of the plurality of communication links, and, in response thereto:
transmit a notification signal to the second network entity configured to inform the second network entity that the first network entity is configured to specify receiving and transmitting timestamp messages via the same link,
wherein the second network entity comprises a second processor configured to:
detect a change in the status of at least one of the plurality of communication links, and, in response thereto:
determine whether a notification signal is received from the first network entity within a predefined period, the notification signal informing the second network entity that the first network. entity is configured to specify receiving and transmitting timestamp messages via the same link; and wherein,
in the event that the notification signal is received by the second network entity within the predetermined period the second processor being further configured to:
determine on which link the notification signal was received; and
use the determined link for subsequent communication of timestamp messages with the first network entity.

### Claim 20 (depends on 19)

The system as claimed in claim 19 wherein the first processor is further configured to:
determine on which link a first timestamp message was received from the second network entity;
and
based on the determination of the link, transmit from the first network entity a second timestamp message to the second network entity on the same link as the first timestamp was received.
