Master/slave negotiation associated with a synchronous ethernet network

Patent metadata

Field	Value
Publication number	US-2017366286-A1
Application number	US-201715691994-A
Country	US
Kind code	A1
Filing date	Aug 31, 2017
Priority date	Jun 25, 2015
Publication date	Dec 21, 2017
Grant date	—

Abstract

A device may determine a link master/slave relationship for an Ethernet link associated with a connection between a component of the device and a component of another device. The device may determine that Synchronous Ethernet (SyncE) is to be enabled on the Ethernet link. The device may identify the component of the device as a SyncE slave or a SyncE master associated with enabling SyncE on the Ethernet link. The device may provide an indication that the component of the device has been identified as the SyncE slave or the SyncE master. The device may determine a SyncE master/slave relationship associated with enabling SyncE on the Ethernet link. The SyncE master/slave relationship may supersede the link master/slave relationship without altering the link master/slave relationship. The device may cause the component of the device to recover a clock based on the SyncE master/slave relationship rather than the link master/slave relationship.

First claim

1 - 20 . (canceled)

21 . A method, comprising:
determining, by a first network element, a link master/slave relationship for an Ethernet link,
the Ethernet link being associated with a connection between a first component of the first network element and a second component of a second network element;
receiving, by the first network element, an indication that the second component of the second network element has been selected as a Synchronous Ethernet (SyncE) slave associated with enabling SyncE on the Ethernet link; identifying, by the first network element and based on the indication, the first component as a SyncE master associated with enabling SyncE on the Ethernet link; providing, by the first network element and to the second network element, acknowledgment information indicating that the first component has been identified as the SyncE master; and determining, by the first network element and based on providing the acknowledgment information, a SyncE master/slave relationship associated with enabling SyncE on the Ethernet link,
the SyncE master/slave relationship superseding the link master/slave relationship for the Ethernet link.

22 . The method of claim 21 , where receiving the indication that the second component of the second network element has been selected as the SyncE slave comprises:
receiving the indication, that the second component has been selected as the SyncE slave, from the second network element using an auto-negotiation next page.

23 . The method of claim 21 , where the second component of the second network element recovers a clock based on the SyncE master/slave relationship rather than the link master/slave relationship.

24 . The method of claim 21 , further comprising:
detecting the connection between the first component of the first network element and the second component of the second network element; and determining the link master/slave relationship for the Ethernet link based on detecting the connection between the first component of the first network element and the second component of the second network element.

25 . The method of claim 21 , where the first network element is positioned upstream from the second network element.

26 . The method of claim 21 , where determining the link master/slave relationship for the Ethernet link comprises:
determining the link master/slave relationship based on an auto-negotiation procedure associated with establishing the Ethernet link.

27 . The method of claim 21 , where the Ethernet link is a 1000Base-T Ethernet link.

28 . A first network element, comprising:
one or more processors to:
determine a link master/slave relationship for an Ethernet link,
the Ethernet link being associated with a connection between a first component of the first network element and a second component of a second network element;

receive an indication that the second component of the second network element has been selected as a Synchronous Ethernet (SyncE) slave associated with enabling SyncE on the Ethernet link;
identify, based on the indication, the first component as a SyncE master associated with enabling SyncE on the Ethernet link;
provide, to the second network element, acknowledgment information indicating that the first component has been identified as the SyncE master; and
determine, based on providing the acknowledgment information, a SyncE master/slave relationship associated with enabling SyncE on the Ethernet link,
the SyncE master/slave relationship superseding the link master/slave relationship for the Ethernet link.

29 . The first network element of claim 28 , where, when receiving the indication that the second component of the second network element has been selected as the SyncE slave, the one or more processors are to:
receive the indication, that the second component has been selected as the SyncE slave, from the second network element using an auto-negotiation next page.

30 . The first network element of claim 28 , where the second component of the second network element recovers a clock based on the SyncE master/slave relationship rather than the link master/slave relationship.

31 . The first network element of claim 28 , where the one or more processors are further to:
detect the connection between the first component of the first network element and the second component of the second network element; and determine the link master/slave relationship for the Ethernet link based on detecting the connection between the first component of the first network element and the second component of the second network element.

32 . The first network element of claim 28 , where the first network element is positioned upstream from the second network element.

33 . The first network element of claim 28 , where, when determining the link master/slave relationship for the Ethernet link, the one or more processors are to:
determine the link master/slave relationship based on an auto-negotiation procedure associated with establishing the Ethernet link.

34 . The first network element of claim 28 , where the Ethernet link is a 1000Base-T Ethernet link.

35 . A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors of a first network element, cause the one or more processors to:
determine a link master/slave relationship for an Ethernet link,
the Ethernet link being associated with a connection between a first component of the first network element and a second component of a second network element;

receive an indication that the second component of the second network element has been selected as a Synchronous Ethernet (SyncE) slave associated with enabling SyncE on the Ethernet link;
identify, based on the indication, the first component as a SyncE master associated with enabling SyncE on the Ethernet link;
provide, to the second network element, acknowledgment information indicating that the first component has been identified as the SyncE master; and
determine, based on providing the acknowledgment information, a SyncE master/slave relationship associated with enabling SyncE on the Ethernet link,
the SyncE master/slave relationship superseding the link master/slave relationship for the Ethernet link.

36 . The non-transitory computer-readable medium of claim 35 , where the one or more instructions, that cause the one or more processors to receive the indication that the second component of the second network element has been selected as the SyncE slave, cause the one or more processors are to:
receive the indication, that the second component has been selected as the SyncE slave, from the second network element using an auto-negotiation next page.

37 . The non-transitory computer-readable medium of claim 35 , where the second component of the second network element recovers a clock based on the SyncE master/slave relationship rather than the link master/slave relationship.

38 . The non-transitory computer-readable medium of claim 35 , where the instructions further comprise:
one or more instructions that, when executed by the one or more processors, cause the one or more processors to:
detect the connection between the first component of the first network element and the second component of the second network element; and
determine the link master/slave relationship for the Ethernet link based on detecting the connection between the first component of the first network element and the second comp

Assignees

• Juniper Networks Inc

Inventors

• Reddy M Ramana
• S Satheesh Kumar

Classifications

• H04J3/0638 Primary

  Clock or time synchronisation among nodes; Internode synchronisation (synchronization for ring networks H04L12/422; data switching networks with synchronous transmission H04L12/43) · CPC title

• H04J3/12 Primary

  Arrangements providing for calling or supervisory signals · CPC title

• H04L12/403

  with centralised control, e.g. polling · CPC title

• H04J3/0658

  Clock or time synchronisation among packet nodes · CPC title