Secured clock synchronization in a packet-compatible network

Patent metadata

Field	Value
Publication number	US-12184407-B2
Application number	US-202217991356-A
Country	US
Kind code	B2
Filing date	Nov 21, 2022
Priority date	Nov 23, 2021
Publication date	Dec 31, 2024
Grant date	Dec 31, 2024

Abstract

There is provided a technique of securing clock synchronization between master clock node (MCN) and client clock node (CCN). During a cycle of exchanging PTP messages between MCN and CCN, MCN generates an associated paired message for each PTP message generated thereby and informative of t1 or t4 timestamps provided by MCN and sends each paired message to a validation entity (VE) via a secured channel between MCN and VE. When PTP messages traverse transparent clock nodes (TCN) between MCN and CCN, each TCN generates a paired message for each version of PTP message updated thereby and sends each generated paired message to VE via a secured channel between respective TCN and VE. VE uses the received paired messages to provide a validation of the cycle, wherein synchronization-related task(s) (e.g. clock correction by the client clock node, etc.) are provided only subject to successful validation of the cycle by VE.

First claim

The invention claimed is:

1. A method of securing a clock synchronization between a master clock node and a client clock node in a packet-compatible network, the method comprising:
during a cycle of exchanging one or more sequences of Precision Time Protocol (PTP) messages between the master clock node and the client clock node, generating, by the master clock node, a paired message for each PTP message generated thereby and informative of accurate t 1 timestamp or of t 4 timestamp provided by the master clock node;
sending, by the master clock node, each paired message to a validation entity, wherein the paired messages are sent via a secured channel between the master clock node and the validation entity;
using, by the validation entity, the paired messages to provide a validation of the cycle; and
providing a synchronization-related task subject to successful validation of the cycle by the validation entity.

2. The method of claim 1 , wherein the synchronization-related task is a clock correction provided by the client clock node.

3. The method of claim 1 , wherein the PTP messages are traversing one or more transparent clock nodes between the master clock node and the client clock node, each transparent clock node updating, with its residence time, correction fields in versions of at least part of PTP messages traversing therethrough, the method further comprising:
during the cycle, generating by each of the one or more transparent clock nodes a paired message for each version of PTP message updated thereby and sending each generated paired message to the validation entity, wherein
the paired messages are sent via a secured channel between a respective transparent clock node and the validation entity; and
using, by the validation entity, the paired messages received from the one or more transparent clocks when validating the cycle.

4. The method of claim 3 , wherein each of the one or more transparent clock nodes updates received versions of PTP messages from one of the following combinations of PTP messages: SYNC and DELAY REQUEST PTP messages, SYNC and DELAY RESPONSE PTP messages, FOLLOW UP and DELAY REQUEST PTP messages and FOLLOW UP and DELAY RESPONSE PTP messages.

5. The method of claim 3 , wherein the validation entity is implemented as a part of the client clock node and operatively connected by respective secured channels with the master clock node and each of the one or more transparent clock nodes or the validation entity is implemented as a centralized entity operatively connected with the master clock node, the client clock node and each of the one or more transparent clock nodes by respective secured channels.

6. The method of claim 3 , wherein each of the secured channels is Authenticated Encryption with Associated Data (AEAD) secured channel.

7. The method of claim 3 , wherein the paired messages are copies of respective versions of PTP messages or are derivatives thereof.

8. The method of claim 3 , wherein the master clock node generates the paired messages as copies of respective versions of PTP messages and the one or more transparent clock nodes generate the paired messages as derivatives of respectively updated versions, the derivatives informative of residence time of the respective transparent clock nodes.

9. The method of claim 3 , wherein the cycle is constituted by multiple sequences of PTP messages and wherein at least one among the master clock node and the one or more transparent clock nodes stores the paired messages generated during the cycle and transmit them all together to the validation entity for the cycle validation.

10. The method of claim 3 , wherein the validation of the cycle comprises validating all accurate t 1 timestamps, all t 4 timestamps and data in all respective correction fields in PTP messages received by the client clock during the cycle.

11. The method of claim 10 , wherein the validation of the cycle further comprises at least one of: 1) authorizing sources of SYNC PTP messages and, thereby validating t 2 timestamps provided by the client clock node in response to reception of the SYNC PTP messages, 2) authorizing the transparent clock nodes as sources of updated versions of PTP messages.

12. The method of claim 3 , wherein each paired message from the one or more transparent clock nodes is generated as a derivative from a respective updated version of PTP message and is informative of a residence time value used for a respective update.

13. The method of claim 12 , wherein the validation of the cycle comprises, for each sequence of PTP messages in the cycle:
comparing an accurate t 1 timestamp in a paired message received by the validation entity from the master clock node with an accurate t 1 timestamp in a version of PTP message received by the client clock node;
comparing a value in a correction field in the version of PTP message bearing the accurate t 1 timestamp and received by the client clock node with a sum of residence time values from all paired messages informative of the accurate t 1 timestamp and received by the validation entity from the one or more transparent clock nodes;
comparing a t 4 timestamp in a paired message received by the validation entity from the master clock node with a t 4 timestamp in a version of PTP message received by the client clock node;
comparing a value in a correction field of the version of DELAY RESPONSE message received by the client clock node with a sum of residence time values from all paired messages informative of t 4 or t 3 timestamps and received by the validation entity from the one or more transparent clock nodes; and
considering the validation of the cycle as successful when, for each sequence of PTP messages in the cycle, all compared values are equal.

14. A master clock node configured to operate in a packet-compatible network comprising a client clock node operatively connected to the master clock node, wherein the master clock node is further configured to:
during a cycle of exchanging one or more sequences of Precision Time Protocol (PTP) messages between the master clock node and the client clock node, generate a paired message for each PTP message generated thereby and informative of accurate t 1 timestamp or of t 4 timestamp provided by the master clock node;
send each paired message to a validation entity, wherein the paired messages are sent via a secured channel between the master clock node and the validation entity; and
upon successful validation of the cycle by the validation entity, provide a synchronization-related task, wherein the validation is provided with the help of the paired messages.

15. The master clock node of claim 14 configured to traverse the one or more sequences of PTP messages via one or more transparent clock nodes between the master clock node and the client clock node, each transparent clock node configured to update, with its residence time, correction fields in versions of at least part of PTP messages traversing therethrough.

16. The master clock node of claim 15 configured to be operatively connected to the validation entity implemented as a part of the client clock node and operatively connected by respective secured channels with each of the one or more transparent clock nodes between the master clock node and the client clock node.

17. The master clock node of claim 15 configured to be operatively connected to the validation entity implemented as a centralized entity operatively connected with the client clock node and each of the one or more transparent clock nodes by respective secured channels.

Assignees

• Adva Optical Networking Se
• Adtran Networks Se

Inventors

• Rabinovich Michael
• Sergeev Andrew
• Cho Joo Yeon
• Zou Shihuan

Classifications

• H04J3/0644

  External master-clock · CPC title

• H04L63/126

  the source of the received data · CPC title

• H04L63/0428

  wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title

• H04J3/0673

  using intermediate nodes, e.g. modification of a received timestamp before further transmission to the next packet node, e.g. including internal delay time or residence time into the packet · CPC title

• H04J3/14

  Monitoring arrangements {(for SDH/SONET rings H04J3/085)} · CPC title