WO2021042789A1 - 用于实现时钟源选取的方法、装置、***及存储介质 - Google Patents

用于实现时钟源选取的方法、装置、***及存储介质 Download PDF

Info

Publication number
WO2021042789A1
WO2021042789A1 PCT/CN2020/094411 CN2020094411W WO2021042789A1 WO 2021042789 A1 WO2021042789 A1 WO 2021042789A1 CN 2020094411 W CN2020094411 W CN 2020094411W WO 2021042789 A1 WO2021042789 A1 WO 2021042789A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
clock source
port
clock
announce message
Prior art date
Application number
PCT/CN2020/094411
Other languages
English (en)
French (fr)
Inventor
吕京飞
许德坚
李晓霞
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20860856.2A priority Critical patent/EP4027585A4/en
Priority to KR1020227008937A priority patent/KR102600909B1/ko
Priority to JP2022514714A priority patent/JP7401656B2/ja
Priority to CN202080003884.XA priority patent/CN112771817A/zh
Publication of WO2021042789A1 publication Critical patent/WO2021042789A1/zh
Priority to US17/687,056 priority patent/US20220190945A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0658—Clock or time synchronisation among packet nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0641—Change of the master or reference, e.g. take-over or failure of the master
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H04L7/0016—Arrangements for synchronising receiver with transmitter correction of synchronization errors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0658—Clock or time synchronisation among packet nodes
    • H04J3/0661—Clock or time synchronisation among packet nodes using timestamps
    • H04J3/0667—Bidirectional timestamps, e.g. NTP or PTP for compensation of clock drift and for compensation of propagation delays

Definitions

  • This application relates to the field of clock technology, and in particular to a method, device, system and storage medium for selecting a clock source.
  • NTP network time protocol
  • IEEE 1588 precision clock synchronization protocol the precision clock synchronization protocol standard for network measurement and control systems
  • PTP precision timing protocol
  • the embodiments of the present application provide a method, device, system, and storage medium for selecting a clock source to solve the problems provided by related technologies.
  • the technical solutions are as follows:
  • a method for selecting a clock source includes: a first node receives a first packet sent by a second node through a first port on the first node; When a message carries a first mark, the first node does not select the clock source corresponding to the first port when selecting the clock source, and the first mark is used to indicate that the time synchronization of the second node is not determine.
  • the clock source data corresponding to the first port is not used to select the clock source, so as to avoid the time of the upstream node. Uncertain synchronization makes the time of downstream nodes jump, which in turn affects the time jump of the entire network and the normal operation of services.
  • not selecting the clock source corresponding to the first port includes: when the first node selects the clock source, not using the first port The clock source data received by the port selects the clock source.
  • selecting the clock source without using the clock source data received through the first port includes: corresponding to the first port according to the first mark
  • the clock source data set of is set as an empty set; the clock source is selected according to the clock source data set corresponding to each port of the first node.
  • selecting the clock source without using the clock source data received through the first port includes: corresponding to the first port according to the first mark
  • the clock source data set of is set as an empty set; the clock source is selected according to the non-empty clock source data set in the clock source data set corresponding to each port of the first node.
  • the setting the clock source data set corresponding to the first port to an empty set according to the first mark includes: setting the signal abnormality attribute of the first port based on the first mark The value of is set to a first value, which is used to indicate that a signal abnormality occurs at the first port; based on the first value of the signal abnormality attribute, the clock source data set corresponding to the first port is set to an empty set.
  • the signal abnormality attribute of the first port is the port signal failure attribute portDS.SF, and the first value of the portDS.SF is TRUE. Since the port signal failure attribute portDS.SF is an attribute defined in the existing standards, the clock source data set corresponding to the first port is set to an empty set based on the port signal failure attribute portDS.SF, which can be applied to the existing standards and improve The applicability of the method provided in the embodiments of this application.
  • the setting the value of the signal abnormality attribute of the first port to the first value based on the first flag includes: determining the packet timing of the first port based on the first flag Signal failure PTSF event; based on the PTSF event, the value of portDS.SF of the first port is set to the first value.
  • the PTSF event is a packet timing signal failure-lost synchronization PTSF-lossSync event, a packet timing signal failure-unusable PTSF-unusable event or an extended PTSF event. Since the packet timing signal failure-lost synchronization PTSF-lossSync event, and the packet timing signal failure-unusable PTSF-unusable event are events defined in existing standards, they can be applied to existing standards and improve the performance of the method provided in the embodiments of this application. applicability. In addition, the PTSF event is extended through the extended PTSF event, and the way to determine the port signal failure attribute portDS.SF is extended.
  • the first message is an Announce message.
  • the synchronization Uncertain flag in the Announce message is used to carry the first flag, and when the value of the synchronizationUncertain is a third value, it is used to indicate the time of the second node Uncertain synchronization.
  • the third value of the synchronizationUncertain is TRUE.
  • a method for selecting a clock source includes: a second node generates a first Announce message, and when the time synchronization of the second node is uncertain, the first The level corresponding to the target parameter carried in the Announce message is lower than the reference level, where the reference level is the level corresponding to the target parameter when the second node synchronizes time; sending the first Announce message to the first node , The parameters carried in the first Announce message are used to select a clock source.
  • the second node is an intermediate node, and before generating the first Announce message, it also receives a second Announce message sent by an upstream node. Accordingly, the first Announce message is generated according to the second Announce message. Announce message.
  • the target parameter carried in the first Announce message is inferior to the target parameter carried in the second Announce message (that is, the level of the target parameter carried in the second Announce message is used as the reference level).
  • the target parameter carried in the first Announce message is inferior to the target parameter when the time server is in lock mode (that is, the target parameter when the time server is in lock mode).
  • the level of the parameter serves as the reference level).
  • the first Announce message When the time synchronization of the second upstream node is uncertain, the first Announce message carries target parameters with a level lower than the reference level, so that when the first downstream node selects the clock source, the first Announce message contains the target parameter.
  • the target parameter level is low, and the clock source corresponding to the port that receives the first Announce message is not selected, so as to avoid the time jump of the downstream node due to the uncertain time synchronization of the upstream node, which affects the time jump of the entire network. Change and normal business.
  • the target parameter is one or more of clock class clockclass, clock accuracy clockAccuracy, and offsetScaledLogVariance parameter of the offset scale.
  • the generation of the first Announce message by the second node includes: the second node receives the second Announce message sent by the upstream node, and the target parameter in the second Announce message The level of is modified to obtain the first Announce message, or the first Announce message is generated according to the information in the second Announce message.
  • a device for selecting a clock source is provided.
  • the device is applied to a first node.
  • the device includes: a receiving module configured to receive a second clock source through a first port on the first node.
  • the first mark is used to indicate that the time synchronization of the second node is uncertain.
  • the selecting module is configured to select the clock source without using the clock source data received through the first port when selecting the clock source.
  • the selection module is configured to set the clock source data set corresponding to the first port as an empty set according to the first tag; according to the clock source corresponding to each port of the first node The data set selects a clock source, or the clock source is selected according to a non-empty clock source data set in the clock source data set corresponding to each port of the first node.
  • the selection module is configured to set the value of the signal abnormality attribute of the first port to a first value based on the first tag, and is used to indicate that a signal abnormality occurs in the first port; Based on the first value of the signal abnormality attribute, the clock source data set corresponding to the first port is set to an empty set.
  • the signal abnormality attribute of the first port is the port signal failure attribute portDS.SF, and the first value of the portDS.SF is TRUE.
  • the selection module is configured to determine that a packet timing signal failure PTSF event occurs on the first port based on the first flag; and based on the PTSF event, change the portDS.SF of the first port The value of is set to the first value.
  • the PTSF event is a packet timing signal failure-lost synchronization PTSF-lossSync event, a packet timing signal failure-unusable PTSF-unusable event or an extended PTSF event.
  • the first message is an Announce message.
  • the synchronization Uncertain flag in the Announce message is used to carry the first flag, and when the value of the synchronizationUncertain is a third value, it is used to indicate the time of the second node Uncertain synchronization.
  • the third value of the synchronizationUncertain is TRUE.
  • a device for selecting a clock source is provided, the device is applied to a second node, and the device includes:
  • the generation module is used to generate a first Announce message when the time synchronization of the second node is uncertain.
  • the target parameter carried in the first Announce message corresponds to a level lower than the reference level, and the reference level is The level corresponding to the target parameter of the second node during time synchronization;
  • the sending module is configured to send the first Announce message to the first node, and the parameters carried in the first Announce message are used to select a clock source.
  • the second node is an intermediate node
  • the generating module is specifically configured to generate the first Announce message according to a second Announce message received from an upstream node of the second node.
  • the target parameter carried in the first Announce message is inferior to the target parameter carried in the second Announce message (that is, the level of the target parameter carried in the second Announce message is used as the reference level).
  • the target parameter carried in the first Announce message is inferior to the target parameter when the time server is in lock mode (that is, the target parameter when the time server is in lock mode).
  • the level of the parameter serves as the reference level).
  • the target parameter is one or more of clock class clockclass, clock accuracy clockAccuracy, and offsetScaledLogVariance parameter of the offset scale.
  • the generating module is configured to receive a second Announce message sent by an upstream node, and modify the level of the target parameter in the second Announce message to obtain the first Announce message Or, according to the information in the second Announce message, the first Announce message is generated.
  • a system for selecting a clock source includes: a first node and a second node; and the second node is configured to send a first node to a first port of the first node.
  • a message; the first node is configured to receive a first message sent by the second node through a first port on the first node; when the first message carries a first tag,
  • the clock source corresponding to the first port is not selected, and the first mark is used to indicate that the time synchronization of the second node is uncertain.
  • the first node is configured to select a clock source without using clock source data received through the first port when selecting a clock source.
  • the first node is configured to set the clock source data set corresponding to the first port as an empty set according to the first label; according to the clock corresponding to each port of the first node
  • the source data set selects a clock source, or the clock source is selected based on a non-empty clock source data set in the clock source data set corresponding to each port of the first node.
  • the first node is configured to set the value of the signal abnormality attribute of the first port to a first value based on the first tag, and is used to indicate that a signal abnormality occurs on the first port ; Based on the first value of the signal abnormality attribute, the clock source data set corresponding to the first port is set to an empty set.
  • the signal abnormality attribute of the first port is the port signal failure attribute portDS.SF, and the first value of the portDS.SF is TRUE.
  • the first node is configured to determine, based on the first flag, that a packet timing signal failure PTSF event occurs on the first port; based on the PTSF event, the portDS of the first port.
  • the value of SF is set to the first value.
  • the PTSF event is a packet timing signal failure-lost synchronization PTSF-lossSync event, a packet timing signal failure-unusable PTSF-unusable event or an extended PTSF event.
  • the first message is an Announce message.
  • the synchronization Uncertain flag in the Announce message is used to carry the first flag, and when the value of the synchronizationUncertain is a third value, it is used to indicate the time of the second node Uncertain synchronization.
  • the third value of the synchronizationUncertain is TRUE.
  • a system for selecting a clock source comprising: a first node and a second node; the second node is used when the time synchronization of the second node is uncertain , Generating a first Announce message, the level corresponding to the target parameter carried in the first Announce message is lower than a reference level, and the reference level is the level corresponding to the target parameter when the second node synchronizes time Send the first Announce message to the first node; the first node is configured to receive the first Announce message sent by the second node, and the parameters carried in the first Announce message are used To select the clock source.
  • the second node is an intermediate node, and is also used to receive a second Announce message sent by an upstream node before generating the first Announce message, and accordingly, when the first Announce message is generated It is specifically used to generate the first Announce message according to the second Announce message.
  • the target parameter carried in the first Announce message is inferior to the target parameter carried in the second Announce message (that is, the level of the target parameter carried in the second Announce message is used as the reference level).
  • the target parameter carried in the first Announce message is inferior to the target parameter when the time server is in lock mode (that is, the target parameter when the time server is in lock mode).
  • the level of the parameter serves as the reference level).
  • the target parameter is one or more of clock class clockclass, clock accuracy clockAccuracy, and offsetScaledLogVariance parameter of the offset scale.
  • the second node is configured to receive a second Announce message sent by an upstream node, and modify the level of the target parameter in the second Announce message to obtain the first Announce message Or, generate the first Announce message according to the information in the second Announce message.
  • a device for selecting a clock source comprising: a port and a processor, the port is used to communicate with other nodes, and the processor is used to implement any one of the above-mentioned methods for implementing a clock source The selected method.
  • the port is the above-mentioned first port.
  • a computer-readable storage medium is also provided, and at least one instruction is stored in the storage medium, and the instruction is loaded and executed by a processor to implement the method for selecting a clock source as described above.
  • Another communication device which includes a transceiver, a memory, and a processor.
  • the transceiver, the memory, and the processor communicate with each other through an internal connection path, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the transceiver to receive signals and control the transceiver to send signals And when the processor executes the instructions stored in the memory, the processor is caused to execute the method in any one of the foregoing possible implementation manners.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor may be provided separately.
  • the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.
  • ROM read only memory
  • a computer program (product) is provided, the computer program (product) includes: computer program code, when the computer program code is executed by a computer, the computer executes the methods in the above aspects.
  • a chip including a processor, configured to call and execute instructions stored in the memory from a memory, so that a communication device installed with the chip executes the methods in the foregoing aspects.
  • Another chip including: an input interface, an output interface, a processor, and a memory.
  • the input interface, output interface, the processor, and the memory are connected through an internal connection path, and the processor is used to execute all When the code in the memory is executed, the processor is used to execute the methods in the foregoing aspects.
  • FIG. 1 is a schematic diagram of a 1588 synchronization network scenario provided by an embodiment of the application
  • FIG. 2 is a flowchart of a method for selecting a clock source provided by an embodiment of the application
  • FIG. 3 is a flowchart of a method for selecting a clock source provided by an embodiment of the application
  • FIG. 4 is a flowchart of a method for selecting a clock source provided by an embodiment of the application.
  • FIG. 5 is a flowchart of a method for selecting a clock source provided by an embodiment of the application
  • FIG. 6 is a flowchart of a method for selecting a clock source provided by an embodiment of the application.
  • FIG. 7 is a flowchart of a method for selecting a clock source provided by an embodiment of the application.
  • FIG. 8 is a flowchart of a method for selecting a clock source provided by an embodiment of the application.
  • FIG. 9 is a schematic structural diagram of an apparatus for implementing clock source selection provided by an embodiment of the application.
  • FIG. 10 is a schematic structural diagram of an apparatus for implementing clock source selection provided by an embodiment of the application.
  • FIG. 11 is a schematic structural diagram of a device for implementing clock source selection provided by an embodiment of the application.
  • the network includes nodes A, B, C, D, E, and F.
  • node E includes two ports, port 1 and port 2.
  • Port 1 corresponds to node B, and is used to receive PTP packets sent by node B.
  • Port 2 corresponds to node D and is used to receive PTP packets sent by node D.
  • both node A and node C track the global positioning system (GPS), and the clock class (clockClass) in the Announce message sent by node A and node C to downstream node B and node D It is 6, and other parameters representing the IEEE 1588 quality level in the Announce message, such as clock accuracy (clockAccuracy), logarithmic variance of offset scale (offsetScaledLogVariance), etc. are also the same.
  • the clockClass in the Announce message sent by the node B and the node D to the downstream node E is also 6, and other parameters representing the IEEE 1588 quality level in the Announce message, such as clockAccuracy, offsetScaledLogVariance, etc., are also the same.
  • the port of each node has four port states, including master state (master, M), slave state (slave, S), passive state (passive, P), and uncalibrated (UNCALIBRATED) state.
  • master state master, M
  • slave state slave, S
  • passive state passive, P
  • uncalibrated UNCALIBRATED
  • the communication port with the port status of Master is referred to as the Master port for short.
  • the Master port is used to broadcast the best quality clock source selected by the node to the entire network; the port in the slave state (abbreviated as the slave port) and the port in the UNCALIBRATED state are used to track upstream nodes
  • the state of the port will change from the slave state to the UNCALIBRATED state or from the UNCALIBRATED state to the slave state according to the time synchronization state; the Passive port is in An intermediate position neither broadcasts the clock source nor tracks the clock of the upstream node.
  • Passive in the port status generally means that there are two or more clock sources of similar quality in the entire PTP network system. As shown in Fig.
  • node E selects node B or node D as tracking based on the best master clock (BMC) algorithm Clock source.
  • BMC master clock
  • node B If node B loses power, node E will select the backup path C->D->E for synchronization, and node E can ensure that the time output to node F does not jump.
  • node A When node B is powered on again, node A sends a PTP message to node B, so node B will first synchronize with node A, that is, synchronize the PTP message of node A with the time of node A.
  • the time synchronization of the node B is uncertain, where the uncertain time synchronization of the node means that the time of the node has a large adjustment during the synchronization time period.
  • the embodiment of the present application does not limit it.
  • the node in cases 1, 2A, and 3A, the node is an intermediate node, and in cases 2B and 3B, the node is a source node (that is, a time server).
  • the source node refers to a node that performs time synchronization by directly tracking satellite signals (such as GPS signals), such as nodes A and C in Figure 1.
  • Intermediate nodes refer to nodes that perform time synchronization by tracking upstream nodes, such as nodes B, D, E, and F in Figure 1.
  • the clock source signal of the source node is the satellite signal to be tracked
  • the clock source signal of the intermediate node is the time signal obtained by tracking the upstream node, which can generally be regarded as the time signal of the upstream node.
  • Case 1 The node restarts or switches the clock source.
  • the ingress port of the node is in the uncalibrated state (UNCALIBRATED state), indicating that the node is doing clock synchronization.
  • the time of the node is usually adjusted greatly, so In this case, it is determined that the time synchronization of the node is uncertain.
  • the time of the node is synchronously determined.
  • the reference duration may be set based on experience or application scenarios, and the embodiment of the present application does not limit the reference duration.
  • Case 2 Including Case 2A and Case 2B.
  • Case 2A The node is an intermediate node.
  • the node periodically checks whether the time difference between the time and the clock source signal (that is, the time difference with the upstream node) is less than the threshold. If the time difference is greater than the threshold, it can be understood that the ingress port of the node is in the uncalibrated state (UNCALIBRATED state). In this case, usually the time of the node has a large adjustment, so it is judged that the time synchronization of the node is uncertain.
  • Case 2B The node is the source node (that is, the time server).
  • the node periodically detects whether the time difference with the clock source signal (that is, the time difference with the time of the received satellite signal) is less than the threshold, and if the time difference is greater than the threshold, it is determined that the time synchronization of the node is uncertain.
  • Case 3 Including case 3A and case 3B.
  • Case 3A The node is an intermediate node. After the node restarts or changes the clock source, it detects whether the time difference with the upstream node is less than the threshold. If the time difference is greater than the threshold, it can be understood that the ingress port of the node is in the uncalibrated state (UNCALIBRATED state). In this case, usually the time of the node has a large adjustment, so it is judged that the time synchronization of the node is uncertain.
  • Case 3B This node is the source node. After the node restarts or switches the clock source, it detects whether the time difference with the received satellite signal is less than the threshold. If the time difference is greater than the threshold, it is determined that the time synchronization of the node is uncertain.
  • the time difference between the upstream node and the upstream node is detected to be greater than the threshold to determine that the time synchronization of the node is uncertain.
  • the time synchronization of the node can be determined.
  • the thresholds in cases 2A, 2B, 3A, and 3B may be the same or different.
  • the threshold may be set based on experience, or may be limited based on application scenarios. The embodiment of the present application does not limit the threshold size.
  • the time of node B will be adjusted according to the time of node A (that is, the time in the clock source signal).
  • the node B can also determine whether the time of the node B is synchronized by whether the time difference between the node B and the node A is less than the threshold value. For example, after node B receives the PTP message of node A, it calculates the time difference between node B and node A based on the PTP message of node A.
  • the time difference is less than the threshold, it indicates that the time of node B is synchronized with the time of the clock source signal, that is, the time of node B is in the synchronization determination state (the synchronization determination state will be referred to as synchronization determination or synchronization later), if the time difference is not less than the threshold value , It indicates that the time of node B is in a state of indeterminate synchronization (in the future, the state of indeterminate synchronization will be referred to as indeterminate synchronization for short).
  • the output time of node B has a jump. If the node B sends a PTP message to the node E, it will cause the node E to select the clock source corresponding to the port that receives the PTP message, so that the output time of the node E also jumps. This situation needs to be avoided in the 1588 application, otherwise it will affect the time jump of the entire network and the normal operation of the business.
  • the above description only takes the IEEE1588 scenario as an example.
  • NTP when the clock is synchronized, there are also problems that the output time of the node jumps, which affects the time jump of the entire network and the normal operation of services.
  • the embodiment of the present application provides a method for selecting a clock source.
  • the method notifies downstream nodes whether the time of each node on the path of the clock source is synchronized by carrying a first mark in a first message. If the downstream node detects that the time synchronization of the upstream clock source is uncertain, the downstream node does not select the clock source corresponding to the upstream node's port, so as to prevent the downstream node's output time from being affected.
  • the method for selecting the clock source provided in the embodiments of the present application will be described. As shown in Figure 2, the method includes the following processes:
  • the first node receives a first packet sent by a second node through a first port on the first node.
  • the first node is connected to one or more upstream second nodes, and the first node can receive the first message sent by the second node through the first port on the first node, and the first message includes but is not limited to PTP Message or NTP message.
  • PTP Message or NTP message.
  • the first message includes but is not limited to PTP Message or NTP message.
  • the first message includes but is not limited to PTP Message or NTP message.
  • PTP Message a synchronization (sync) message, a follow_up message, Delay request (delay_req) messages, delay response (delay_resp) messages and management (management) messages.
  • Verision2 adds three kinds of PTP messages in the peer-delay mechanism on the basis of verision1, namely the point delay request (Pdelay_req) message, the point delay response (Pdelay_resp) message, and the point delay response follower. (Pdelay_resp_Follow_up) message. In addition, a signaling message and an Announce message are added.
  • messages such as sync, delay_req, follow_up, and delay_resp are used to generate and communicate time information for synchronizing ordinary clocks and boundary clocks through a response mechanism (delay request-response mechanism).
  • Messages such as Pdelay_req, Pdelay_resp, and Pdelay_resp_Follow_up are used to measure the link delay between two clock ports through a peer delay mechanism.
  • the Announce message is used to establish a synchronization path, and the status and characteristic information of the node and the root node that send the Announce message; the management message is used to query and update the PTP data set maintained by the clock, and the signaling message is used for other purposes, such as The master and slave coordinate the sending frequency of unicast packets.
  • the first node can receive any of the foregoing first messages sent by the second node to the first node through the first port.
  • the downstream node can be sent to the downstream node by carrying the first tag in the first packet. Notify that the time synchronization of the upstream second node is uncertain.
  • the first tag may be carried in an existing field of the first message, or may be carried in a newly defined field of the first message. The embodiment of this application does not treat the first message. The way of carrying the first mark is limited.
  • the Announce message sent by the second node to the first port of the first node Carry the first mark, and indicate that the time synchronization of the second node is uncertain through the first mark.
  • the first mark may be carried in an existing field of the Announce message, or may be carried in a newly added field of the Announce message. Taking the first mark carried in the existing field of the Announce message as an example, the first mark may be carried through the synchronization Uncertain mark (synchronization Uncertain) in the Announce message.
  • the value of synchronizationUncertain when the value of synchronizationUncertain is TRUE, it is used to indicate that the time synchronization of the second node is uncertain.
  • the value of synchronizationUncertain may also be other values other than TURE and FLASE.
  • the embodiment of the present application does not limit the value of synchronizationUncertain used to indicate that the time synchronization of the second node is uncertain.
  • the Announce message sent by the second node may also carry other parameters, for example, Parameters include clockClass, clockAccuracy and offsetScaledLogVariance, etc.
  • the method provided in this embodiment of the present application also supports the use of other parameters in the Announce message to carry the first mark when the time synchronization of the second node is uncertain.
  • the second node determines that the time synchronization is uncertain
  • the second node sets the value of one or more of the clockClass, clockAccuracy, and offsetScaledLogVariance parameters in the Announce message to be sent to a specific value.
  • the specific value indicates that the time synchronization of the second node is uncertain. Take the network shown in Figure 1 as an example.
  • the clockClass in the Announce messages sent by node A and node C to downstream nodes B and D is 6.
  • the second node determines that the time synchronization of the second node is uncertain
  • the second node sets the clockClass of the Announce message to 187 or 248 and then sends it to the first node, thereby indicating the first node by setting the clockClass to a specific value of 187 or 248.
  • the time synchronization between the two nodes is uncertain, so that the first node will not select the second node as the clock source.
  • the clockClass of the Announce message sent by the node on the master port should be the clockClass received by the slave port, not the slave port.
  • the clockClass received by the port is degraded and sent out.
  • the existing IEEE 1588v2 standard is not changed, the above-mentioned method of carrying the first mark through the synchronizationUncertain in the Announce message can be adopted.
  • the first node When the first packet carries the first flag, the first node does not select the clock source corresponding to the first port when selecting the clock source, and the first flag is used to indicate that the time synchronization of the second node is uncertain.
  • the first node After the first node receives the first message sent by the second node, the first node parses the first message. If the analysis finds that the first message carries the first tag, it can be determined that the time synchronization of the second node is uncertain.
  • the clock source the clock source corresponding to the first port is not selected.
  • the first node does not select the clock source corresponding to the first port when selecting the clock source, including but not limited to the first node not using the clock source data received through the first port when selecting the clock source Select the clock source.
  • the first node receives the first message through the first port.
  • the clock source data received through the first port is not used to select the clock source, and the clock source corresponding to the first port is not selected. Avoid time jumps.
  • the first node can respond to the first packet.
  • the time synchronization of the two nodes is recorded in an uncertain state. For example, the first node records that the first port has received the first message carrying the first tag, so that when the first node selects the clock source, the first node does not use the second node based on the recorded time synchronization uncertain state of the second node.
  • the clock source data received by one port so when selecting the clock source, the clock source corresponding to the first port will not be selected.
  • each port of the first node has a clock source data set.
  • the first packet takes the first packet as an annouce packet as an example, in addition to carrying the first tag, the first packet also carries clock source data, such as clockClass and clockID, and the clock source data set includes clockClass in the annouce packet. Therefore, when the time synchronization of the second node is uncertain, the first node does not use the clock source data received through the first port to select the clock source when selecting the clock source. It can also include But it is not limited to the following two ways:
  • the first node since the first message carries the first mark, and the first mark indicates that the time synchronization of the second node is uncertain, when the first node selects the clock source, it corresponds to the first port according to the first mark
  • the clock source data set of is set to an empty set, and then the clock source is selected according to the clock source data set corresponding to each port of the first node.
  • the clock source data set corresponding to each port of the first node includes the clock source data set corresponding to the first port. That is to say, when the first node selects the clock source, the first node can obtain the data corresponding to all the ports of the first node. Clock source data set, and then compare the clock source data in all clock source data sets to select the clock source.
  • the clock source data set corresponding to the first port is an empty set, the clock source data received through the first port will not be used to select the clock source.
  • the method of selecting the clock source can refer to the BMC source selection process of ITU-T G.8275.1 and G.8275.2 released in March 2018.
  • Method 2 When the first node selects the clock source, it sets the clock source data set corresponding to the first port as an empty set according to the first mark; according to the non-empty clock source data in the clock source data set corresponding to each port of the first node
  • the centralized clock source data selects the clock source.
  • the first node when the first node selects the clock source, the first port is set according to the first mark.
  • the corresponding clock source data set is set to an empty set.
  • the difference from the first method is that in the second method, after the first node sets the clock source data set corresponding to the first port to an empty set, the clock source is not selected based on the clock source data sets corresponding to all the ports of the first node. Instead, only the non-empty clock source data set is obtained, and the clock source is selected according to the non-empty clock source data set. That is to say, the first node in the second method compares the clock source data in the non-empty clock source data set to select the clock source.
  • the first node when it selects the clock source, it sets the clock source data set corresponding to the first port to the empty set according to the first mark, including but Not limited to: when the first node selects the clock source, it sets the value of the signal abnormality attribute of the first port to the first value based on the first mark, which is used to indicate that the first port has signal abnormality; the first value is based on the signal abnormality attribute , Set the clock source data set corresponding to the first port to an empty set.
  • the current ITU-T G.8275.2 defines the signal failure attribute portDS.SF. If the value of portDS.SF of the first port is the first value, such as TRUE, then the first node corresponds to the first port The clock source data set (Erbest) is set to an empty set. Therefore, in the method provided by the embodiment of the present application, the signal failure attribute portDS.SF of the port can be used as the signal abnormality attribute. If the first value of portDS.SF of the first port is TRUE, the clock of the first port The source data set (Erbest) is set to an empty set.
  • the value of portDS.SF of the first port can be determined by a packet timing signal fail (PTSF) event.
  • PTSF packet timing signal fail
  • the value of the signal abnormality attribute of the first port is set to the first flag based on the first flag.
  • a value includes: determining that a PTSF event occurs on the first port based on the first flag; and setting the value of portDS.SF of the first port to the first value based on the PTSF event.
  • the default value of the PTSF event can be FALSE, indicating that no PTSF event has occurred.
  • the value of the PTSF event can be set to TRUE.
  • the value of portDS.SF of the first port is set to the first value.
  • the attribute portDS.SF is determined based on the packet timing signal failure-loss of synchronization (PTSF-lossSync) event and the packet timing signal failure-unusable (PTSF-unusable) event, if If the port cannot receive the PTP message, it is determined that the PTSF-lossSync event has occurred, and the value of the PTSF-lossSync event is set to the second value (for example, the second value is TRUE), otherwise it is FALSE; if the port receives the PTP message If the performance of the document exceeds the tolerance range of the node, it is determined that a PTSF-unusable event has occurred, and the value of the PTSF-unusable event is set to a second value (for example, the second value is TRUE), otherwise it is FALSE.
  • PTSF-lossSync packet timing signal failure-loss of synchronization
  • PTSF-unusable packet timing signal failure-unusable
  • the value of portDS.SF is TRUE.
  • the method provided in the embodiment of the present application also supports the extension of a new PTSF event to trigger the setting of the value of the portDS.SF attribute of the first port to the first value.
  • the synchronizationUncertain in the received Announce message corresponds to a new extended PTSF event.
  • the extended PTSF event is named packet timing signal failure-synchronization uncertainty (PTSF-syncUncertain) event, which is used to indicate the first A port has a signal abnormality due to the uncertain time synchronization of the upstream node.
  • PTSF-syncUncertain packet timing signal failure-synchronization uncertainty
  • the value of synchronizationUncertain in the received Announce message is TRUE, then it is determined that the PTSF-syncUncertain event has occurred, the value of the PTSF-syncUncertain event is set to the second value (for example, TRUE), and the value of portDS.SF is set to The first value.
  • the value of portDS.SF is TRUE, so that the Erbest of the first port is set to the empty set, so that When the first node selects the clock source, the clock source data corresponding to the first port is not used. Therefore, setting the value of the signal abnormality attribute of the first port to the first value based on the first mark includes but is not limited to the following methods:
  • Method 1 Taking the extended PTSF event as the PTSF-syncUncertain event as an example, it is determined that the PTSF-syncUncertain event has occurred on the first port based on the first flag, which is used to indicate that the first port has a signal abnormal event due to the uncertain time synchronization of the upstream node;
  • the PTSF-syncUncertain event sets the value of portDS.SF of the first port to the first value.
  • the value of the PTSF-syncUncertain event is set to the second value.
  • the second value is TRUE, that is, when the PTSF-syncUncertain event occurs, it indicates that the first port is due to the upstream node's time Synchronization is uncertain when a signal abnormal event occurs, so it is triggered to set the value of portDS.SF of the first port to the first value.
  • the value of portDS.SF is TRUE, which triggers the setting of the clock source data set corresponding to the first port Empty set.
  • the second value of the PTSF-syncUncertain event can also be set to FALSE, that is, when the PTSF-syncUncertain event occurs, the value of the PTSF-syncUncertain event is FALSE, indicating the first
  • the port has a signal abnormal event due to the time synchronization of the upstream node, which triggers the portDS.SF value of the first port to be set to the first value.
  • the value of portDS.SF is TRUE, which triggers the corresponding to the first port.
  • the clock source data set is set to an empty set.
  • the second value of the PTSF-syncUncertain event may also be other manifestations other than TRUE and FALSE, which is not limited in the embodiment of the present application.
  • Manner 2 Based on the first flag, it is determined that the PTSF-lossSync event occurs on the first port; based on the PTSF-lossSync event, the value of portDS.SF of the first port is set to the first value.
  • the value of the PTSF-lossSync event is set to the second value, and the second value is TRUE, that is, when the value of the PTSF-lossSync event is TRUE, it indicates that the first port is caused by upstream
  • the time synchronization of the node does not determine the occurrence of signal abnormal events, so it triggers the portDS.SF value of the first port to be set to the first value, for example, the value of portDS.SF is TRUE, which triggers the clock source data corresponding to the first port Set to empty set.
  • the second value of the PTSF-lossSync event may also be other manifestations other than TRUE, which is not limited in the embodiment of the present application.
  • Manner 3 Determine that a PTSF-unusable event occurs on the first port based on the first flag; and set the value of portDS.SF of the first port to the first value based on the PTSF-unusable event.
  • the value of the PTSF-unusable event is set to the second value, for example, the second value is TRUE, that is, when the value of the PTSF-unusable event is TRUE, it indicates that the first port is caused by upstream
  • the time synchronization of the node does not determine the occurrence of signal abnormal events, so it triggers the portDS.SF value of the first port to be set to the first value, for example, the value of portDS.SF is TRUE, which triggers the clock source data corresponding to the first port Set to empty set.
  • the second value of the PTSF-unusable event may also be other manifestations other than TRUE, which is not limited in the embodiment of the present application.
  • the first tag is carried in the first message to indicate that the time synchronization of the second node is uncertain.
  • the downstream first node receives the first message carrying the first tag through the first port, when selecting the clock source, it does not use the clock source data corresponding to the first port to select the clock source, thereby avoiding the problem.
  • the time synchronization of the upstream node is uncertain, which causes the time of the downstream node to jump, which in turn affects the time jump of the entire network and the normal operation of services.
  • node E in FIG. 1 is the first node
  • node B is the second node
  • the first message is an Announce message.
  • the method for selecting the clock source includes:
  • the node B When the time synchronization of the node B is uncertain, it sends an Announce message to the node E, and the value of synchronizationUncertain in the Announce message is TRUE.
  • the first port of node E receives the Announce message, analyzes to obtain that the value of synchronizationUncertain in the Announce message is TRUE, and sets the clock source data set corresponding to the first port as an empty set.
  • Node E obtains clock source data sets of all ports of node E, including clock source data sets whose data sets are empty and clock source data sets whose data sets are not empty.
  • the node E selects the clock source according to the clock source data in the non-empty clock source data set, and does not use the clock source data corresponding to the first port to select the clock source.
  • the process of node E selecting the clock source can refer to the BMC source selection process of ITU-T G.8275.1 and G.8275.2 released in March 2018.
  • the method for selecting the clock source includes:
  • the first port of node E receives the Announce message, analyzes and obtains that the value of synchronizationUncertain in the Announce message is TRUE, and sets the value of portDS.SF of the first port to TRUE.
  • Node E sets the clock source data set corresponding to the first port to an empty set based on the value of portDS.SF.
  • Node E obtains clock source data sets of all ports of node E, including clock source data sets whose data sets are empty and clock source data sets whose data sets are non-empty.
  • the node E selects the clock source according to the clock source data in the non-empty clock source data set, and does not use the clock source data corresponding to the first port to select the clock source.
  • the process of node E selecting the clock source can refer to the BMC source selection process of ITU-T G.8275.1 and G.8275.2 released in March 2018.
  • the method for selecting the clock source includes:
  • the first port of the node E receives the Announce message, analyzes and obtains that the value of synchronizationUncertain in the Announce message is TRUE, and determines that a PTSF-syncUncertain event occurs on the first port.
  • Node E sets the value of portDS.SF of the first port to TRUE based on the PTSF-syncUncertain event.
  • the node E sets the clock source data set corresponding to the first port to be empty based on the value of portDS.SF.
  • Node E obtains clock source data sets of all ports of node E, including clock source data sets whose data sets are empty and clock source data sets whose data sets are not empty.
  • the node E selects the clock source according to the clock source data in the non-empty clock source data set, and does not use the clock source data corresponding to the first port to select the clock source.
  • the process of node E selecting the clock source can refer to the BMC source selection process of ITU-T G.8275.1 and G.8275.2 released in March 2018.
  • the method for selecting the clock source includes:
  • the first port of the node E receives the Announce message, analyzes and obtains that the value of synchronizationUncertain in the Announce message is TRUE, and determines that a PTSF-lossSync event occurs on the first port.
  • Node E sets the value of portDS.SF of the first port to TRUE based on the PTSF-lossSync event.
  • Node E sets the clock source data set of the first port to be empty based on the value of portDS.SF.
  • Node E obtains clock source data sets of all ports of node E, including clock source data sets whose data sets are empty and clock source data sets whose data sets are not empty.
  • the node E selects the clock source according to the clock source data in the non-empty clock source data set, and does not use the clock source data corresponding to the first port to select the clock source.
  • the process of node E selecting the clock source can refer to the BMC source selection process of ITU-T G.8275.1 and G.8275.2 released in March 2018.
  • the method for selecting the clock source includes:
  • the first port of node E receives the Announce message, and obtains that the value of synchronizationUncertain in the Announce message is TRUE by parsing, and it is determined that a PTSF-unusable event has occurred on the first port.
  • Node E sets the value of portDS.SF of the first port to TRUE based on the PTSF-unusable event.
  • the node E sets the clock source data set of the first port to be empty based on the value of portDS.SF.
  • Node E obtains clock source data sets of all ports of node E, including clock source data sets whose data sets are empty and clock source data sets whose data sets are not empty.
  • the node E selects the clock source according to the clock source data in the non-empty clock source data set, and does not use the clock source data corresponding to the first port to select the clock source.
  • the process of node E selecting the clock source can refer to the BMC source selection process of ITU-T G.8275.1 and G.8275.2 released in March 2018.
  • the first node receives through the first port of the first node the transmission carried by the second node. After a marked first message, the clock source corresponding to the first port is not selected, so as to avoid the time jump as an example. If the time of the second node is subsequently synchronized, a second message is sent to the first node.
  • the second message may carry a second mark, and the second mark is used to indicate the time synchronization of the second node.
  • the clock source data set corresponding to the port of the second node on the first node may not be set to an empty set, thereby setting the clock source corresponding to the first port As the selection object, the clock source is selected accordingly.
  • the value of the synchronization Uncertain flag synchronizationUncertain of the Announce message sent by node B on the master port is FALSE, that is, the value of synchronizationUncertain is carried by the value of synchronizationUncertain.
  • the second mark is used to notify the downstream that the time of the node B has been synchronized.
  • Node E selects node B or node D as the clock source for tracking based on the BMC algorithm. Since downstream node E receives the Announce message of node B on port 1, and parses and obtains that the value of synchronizationUncertain of the Announce message of node B is FALSE, then node E sets the Erbest data set of port 1 to the Announce message of node B Information, still taking the clockID of node A in Fig. 1 being smaller than the clockID of node C as an example, then node E will re-select port 1 to trace to node B.
  • the downstream first node does not choose the clock source corresponding to the first port that receives the first packet of the second node.
  • the method provided in the embodiment of the present application also supports parameter degradation to prevent the clock source of the first port from being selected, thereby avoiding the time jump of the first node.
  • the specific implementation methods include implementation A and implementation B in the following methods.
  • the method for selecting a clock source includes:
  • the second node generates a first Announce message, where the first Announce message includes a target parameter.
  • the target parameter in the first Announce message includes at least one of the first target parameter and the second target parameter.
  • the first target parameter is used to characterize the priority of the master clock, such as master clock priority 1 (grandmasterPriority1) and master clock priority 2 (grandmasterPriority2) in the PTP protocol.
  • the second target parameter is used to characterize the quality of the master clock, such as the master clock quality (grandmasterClockQuality) in the PTP protocol, and may specifically include at least one of the following quality parameters:
  • the parameters used to characterize the traceability of the international atomic time TAI of the clock such as the clock class in the PTP protocol;
  • clock accuracy in the PTP protocol
  • a parameter used to characterize clock stability such as the logarithmic variance of the offset scale (offsetScaledLogVariance).
  • the second node may specifically be an intermediate node or a source node. When it is an intermediate node, it will first receive the second Announce message sent by the upstream node before step 801, and generate the first Announce message according to the second Announce message in step 801.
  • the time of the second node may be in a state of synchronization determination, or may be in a state of indeterminate synchronization.
  • the target parameter carried in the first Announce message is a poor parameter.
  • the target parameter is inferior.
  • the target parameter carried in the first Announce message is a better parameter.
  • the level corresponding to the target parameter carried in the first Announce message is lower than the reference level, and the reference level is the second node
  • the level corresponding to the target parameter when the time is synchronized can be set to a preset value, and the preset value corresponds to a level lower than the reference level.
  • the target parameter includes clockclass and clockAccuracy, and clockclass corresponds to The preset value of is 248, and the preset value corresponding to clockAccuracy is unknown.
  • the level corresponding to the target parameter carried in the first Announce message is the reference level.
  • the level of the target parameter carried in the second Announce message can be used as the reference level. Accordingly, the target parameter carried in the first Announce message is inferior to the second Announce message.
  • Target parameters carried in the text For example, the clockclass carried in the second Announce message is 6, and the value of clockclass carried in the first Announce message is greater than 6, such as 187 or 248.
  • the target parameter carried in the first Announce message is inferior to the target parameter carried in the second Announce message, which means that the target parameter carried in the first Announce message All the parameters in the target parameter are inferior to the corresponding parameters in the target parameter carried in the second Announce message.
  • the target parameter includes clockclass and clockAccuracy
  • the clockclass carried in the first Announce message is inferior to the clockclass carried in the second Announce message
  • the clockAccuracy carried in the first Announce message is inferior to the second Announce message
  • the clockAccuracy carried in the text is inferior to the target parameter.
  • the level corresponding to the target parameter when the time server is in the lock mode can be used as the reference level. Accordingly, the target parameter carried in the first Announce message is inferior to the reference level.
  • the target parameter when the time server is in the locked mode may be defined by the PTP protocol. For example, the PTP protocol defines that the clockclass when the time server is in the lock mode is 6, and the value of the clockclass carried in the first Announce message is a value greater than 6, such as 248.
  • the target parameter carried in the first Announce message is the target parameter when the time server is in the lock mode.
  • the first node Since the level corresponding to the target parameter is lower than the reference level, when selecting the clock source, the first node is less likely to select the clock source corresponding to the port that receives the first Announce message.
  • the standard is different, and the target parameter corresponds to a different reference level when the second node is time synchronized, and the reference level is different, and the value of the target parameter is different.
  • the base level of each node is usually the same.
  • the level corresponding to the target parameter carried in the first Announce message of the second node can be lower than the minimum base level of all types of nodes. value.
  • the target parameter clockclass in the 1588v2, G.8275.1, and G.8275.2 protocol standards, when the clockclass is the reference level, the value of the clockclass is 6.
  • the value of the clockclass is 84.
  • the value of the clockclass is 6 as an example. If the time synchronization of the second node is uncertain, the value of clockclass can be set to 187 or 248. The value of clockclass is 187 or 248, and the corresponding level is lower than the level corresponding to the value of clockclass of 6, and also lower than the value of clockclass of 84 The corresponding level. In this case, if the level of the target parameter in the first Announce message sent by other nodes in time synchronization is higher than the level of the target parameter in the first Announce message sent by the second node, the first node does not choose to receive The clock source corresponding to the port of the first Announce message.
  • the master clock identifier included in the first Announce message may also be a clock identifier (clockIdentity) in a default dataset (default dataset) of the second node.
  • the second node generates the first Announce message according to the second Announce message, in an exemplary embodiment, it includes but is not limited to the following manner:
  • Manner 1 Modify the level of the target parameter in the second Announce message to obtain the first Announce message.
  • the clockclass in the second Announce message is 6, and the value of clockclass is modified to a value greater than 6, such as 248.
  • the second node acts as an intermediate node and receives the second Announce message sent by the upstream node.
  • the level of the target parameter in the second Announce message is the reference level of the upstream node.
  • the reference level of different nodes may be different.
  • the second node modifies the level of the target parameter in the second Announce message, for example, downgrades the target parameter in the second Announce message to obtain The first Announce message carrying the degraded target parameter.
  • the reference level of each node is the same, the level corresponding to the degraded target parameter carried in the first Announce message is lower than the reference level of the second node. If the reference levels of the nodes are different, the level corresponding to the degraded target parameter carried in the first Announce message is lower than the minimum value of the reference levels of all types of nodes.
  • the parameter downgrade also includes modifying the addresses of the source port and the destination port in the second Announce message.
  • Manner 2 Generate the first Announce message according to the information in the second Announce message.
  • the first Announce message When the first Announce message is generated, parameters whose levels are lower than the target parameters in the second Announce message are filled into the corresponding fields of the first Announce message.
  • the clockclass in the second Announce message is 6, and a value greater than 6 (such as 248) is filled in the clockclass field of the first Announce message.
  • the second node serves as an intermediate node, and after receiving the second Announce message, the second node parses the second Announce message to obtain the information in the second Announce message. After that, the second node generates the first Announce message based on the situation of the second node itself and the information in the second Announce message when the time synchronization is uncertain. That is to say, the second method is different from the first method in that the second method does not modify the second Announce message, but regenerates a new Announce message, that is, the first Announce message.
  • the target parameter carried in the first Announce message is a default clock parameter of the second node, such as a parameter in a default dataset of the second node.
  • the default clock parameters are preset parameters.
  • the level corresponding to the default clock parameter of the second node is usually lower than the reference level in Embodiment A.
  • the master clock identifier included in the first Announce message may also be a clock identifier (clockIdentity) in a default dataset (default dataset) of the second node.
  • the above methods 1 and 2 are based on the second node as an intermediate node as an example.
  • the second node is the first node in the network to initiate an Announce message (ie, the source node), rather than the intermediate node.
  • the second node may directly generate the first Announce message based on its own situation when the time synchronization is uncertain.
  • the second node sends a first Announce message to the first node, and the parameters carried in the first Announce message are used to select a clock source.
  • the first node parses the first Announce message. If the base level of each node is the same, the level corresponding to the degraded target parameter carried in the first Announce message Lower than the baseline level of the second node. If the reference level of each node is different, the level corresponding to the degraded target parameter carried in the first Announce message is lower than the minimum value of the reference level of all types of nodes. Therefore, when the first node selects the clock source, it does not The clock source corresponding to the port that receives the first Announce message will be selected.
  • the first Announce message when the time synchronization of the second upstream node is uncertain, the first Announce message carries the target parameter with a level lower than the reference level, so that the first downstream node selects the clock source. Due to the low level of the target parameter in the first Announce message, the clock source corresponding to the port receiving the first Announce message is not selected to avoid the time jump of the downstream node due to the uncertain time synchronization of the upstream node , Which in turn affects the time jump of the entire network and the normal operation of services.
  • the first node when only the second node time synchronization is not determined, the first node does not select the clock source corresponding to the port that receives the first Announce message, thereby avoiding time jumps. It has been described as an example. If the subsequent time of the second node is synchronized, the level of the target parameter in the Announce message sent to the first node can be the reference level of the second node, so that the first node will receive the port of the first Announce message The corresponding clock source is used as the selection object to select the clock source.
  • the embodiment of the present application provides a device for selecting a clock source.
  • the device is applied to a first node. Referring to FIG. 9, the device includes:
  • the receiving module 901 is configured to receive the first packet sent by the second node through the first port on the first node;
  • the selection module 902 is used for when the first message carries the first mark, the first node does not select the clock source corresponding to the first port when selecting the clock source, and the first mark is used to indicate that the time synchronization of the second node is not determine.
  • the selecting module 902 is configured to select the clock source without using the clock source data received through the first port when selecting the clock source.
  • the selecting module 902 is configured to set the clock source data set corresponding to the first port as an empty set according to the first label; select the clock source according to the clock source data set corresponding to each port of the first node, or , Select the clock source according to the non-empty clock source data set in the clock source data set corresponding to each port of the first node.
  • the selection module 902 is configured to set the value of the signal abnormality attribute of the first port to the first value based on the first mark, and is used to indicate that the signal abnormality of the first port occurs; Value, set the clock source data set corresponding to the first port to an empty set.
  • the signal abnormality attribute of the first port is the port signal failure attribute portDS.SF, and the first value of portDS.SF is TRUE.
  • the selection module 902 is configured to determine that a packet timing signal failure PTSF event occurs on the first port based on the first flag; and based on the PTSF event, set the value of portDS.SF of the first port to the first value.
  • the PTSF event is a packet timing signal failure-lost synchronization PTSF-lossSync event, a packet timing signal failure-unusable PTSF-unusable event or an extended PTSF event.
  • the first message is an Announce message.
  • the synchronization undetermined flag synchronizationUncertain in the Announce message is used to carry the first flag, and when the value of synchronizationUncertain is the third value, it is used to indicate that the time synchronization of the second node is uncertain.
  • the third value of synchronizationUncertain is TRUE.
  • the embodiment of the present application provides a device for selecting a clock source.
  • the device is applied to a second node. Referring to FIG. 10, the device includes:
  • the generating module 1001 is used to generate the first announcement message.
  • the sending module 1002 is configured to send the first Announce message to the first node, and the parameters carried in the first Announce message are used to select the clock source.
  • the specific implementation of the generation module 1001 includes the following implementation X and implementation Y, respectively corresponding to implementation A and implementation B in the method embodiment shown in FIG. 8.
  • Embodiment X When the time synchronization of the second node is uncertain, the level corresponding to the target parameter carried in the first Announce message generated by the generating module 1001 is lower than the reference level, which is the target parameter of the second node during time synchronization The corresponding level.
  • the target parameter is one or more of the clock class clockclass, clock accuracy clockAccuracy, and offsetScaledLogVariance parameters of the logarithmic variance of the offset scale.
  • the generating module 1001 is configured to receive a second Announce message sent by an upstream node, and generate the first Announce message according to the second Announce message.
  • the target parameter carried in the first Announce message is inferior to the target parameter carried in the second Announce message (that is, the level of the target parameter carried in the second Announce message is used as the reference level).
  • the level of the target parameter in the second Announce message can be modified to obtain the first Announce message, or the first Announce message can be generated based on the information in the second Announce message Message.
  • the target parameter carried in the first Announce message is inferior to the target parameter when the time server is in lock mode (that is, the level of the target parameter when the time server is in lock mode is used as the reference level ).
  • Embodiment Y When the time synchronization of the second node is uncertain, the target parameter carried in the first Announce message generated by the generating module 1001 is the default clock parameter of the second node, such as the default data of the second node The parameters in the default dataset.
  • the embodiment of the present application provides a system for selecting a clock source, and the system includes: a first node and a second node;
  • the second node is used to send the first message to the first port of the first node
  • the first node is used to receive the first message sent by the second node through the first port on the first node; when the first message carries the first tag, the first node does not select the first message when selecting the clock source A clock source corresponding to a port, and the first mark is used to indicate that the time synchronization of the second node is uncertain.
  • the first node is used to select the clock source without using the clock source data received through the first port when selecting the clock source.
  • the first node is configured to set the clock source data set corresponding to the first port as an empty set according to the first label; select the clock source according to the clock source data set corresponding to each port of the first node, or , Select the clock source according to the non-empty clock source data set in the clock source data set corresponding to each port of the first node.
  • the first node is used to set the value of the signal abnormality attribute of the first port to the first value based on the first tag, and is used to indicate that signal abnormality occurs in the first port; Value, set the clock source data set corresponding to the first port to an empty set.
  • the signal abnormality attribute of the first port is the port signal failure attribute portDS.SF, and the first value of portDS.SF is TRUE.
  • the first node is configured to determine that a packet timing signal failure PTSF event occurs on the first port based on the first flag; and based on the PTSF event, set the value of portDS.SF of the first port to the first value.
  • the PTSF event is a packet timing signal failure-lost synchronization PTSF-lossSync event, a packet timing signal failure-unusable PTSF-unusable event or an extended PTSF event.
  • the first message is an Announce message.
  • the synchronization undetermined flag synchronizationUncertain in the Announce message is used to carry the first flag, and when the value of synchronizationUncertain is the third value, it is used to indicate that the time synchronization of the second node is uncertain.
  • the third value of synchronizationUncertain is TRUE.
  • the embodiment of the present application provides a system for selecting a clock source, and the system includes: a first node and a second node;
  • the second node is used to generate the first Announce message and send the first Announce message to the first node;
  • the first node is configured to receive the first Announce message sent by the second node, and the parameters carried in the first Announce message are used to select the clock source.
  • the level corresponding to the target parameter carried in the first Announce message is lower than the reference level, and the reference level is The level corresponding to the target parameter of the second node during time synchronization.
  • the target parameter is one or more of the clock class clockclass, clock accuracy clockAccuracy, and offsetScaledLogVariance parameters of the logarithmic variance of the offset scale.
  • the second node is configured to receive a second Announce message sent by an upstream node, and generate the first Announce message according to the second Announce message.
  • the target parameter carried in the first Announce message is inferior to the target parameter carried in the second Announce message (that is, the level of the target parameter carried in the second Announce message is used as the reference level).
  • the level of the target parameter in the second Announce message can be modified to obtain the first Announce message, or the first Announce message can be generated based on the information in the second Announce message Message.
  • the target parameter carried in the first Announce message is inferior to the target parameter when the time server is in lock mode (that is, the level of the target parameter when the time server is in lock mode is used as the reference level ).
  • the target parameter carried in the first Announce message is the default clock parameter of the second node.
  • the default clock parameter of the second node Such as the parameters in the default dataset of the second node.
  • an embodiment of the present application also provides a device 1100 for implementing clock source selection.
  • the device 1100 for implementing clock source selection shown in FIG. 11 is used to perform the aforementioned method for implementing clock source selection. Operation.
  • the device 1100 for selecting a clock source includes a processor 1102 and a port 1103, and the processor 1102 and the port 1103 are connected by a bus 1104.
  • the port 1103 is used to communicate with other devices in the network.
  • the port 1103 may be implemented in a wireless or wired manner.
  • the processor 1102 is used to implement any one of the above-mentioned methods for selecting a clock source.
  • the device 1100 for selecting a clock source further includes a memory 1101, at least one instruction is stored in the memory 1101, at least one instruction is loaded and executed by the processor 1102, the memory 1101, the processor 1102, and the port The 1103 are connected through the bus 1104.
  • FIG. 11 only shows a simplified design of the device 1100 for implementing clock source selection.
  • the device that selects the clock source can include any number of interfaces, processors, or memories.
  • the above-mentioned processor may be a central processing unit (CPU), other general-purpose processors, digital signal processing (DSP), application specific integrated circuit (ASIC), Field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or any conventional processor. It is worth noting that the processor may be a processor that supports an advanced reduced instruction set machine (advanced RISC machines, ARM) architecture.
  • the foregoing memory may include a read-only memory and a random access memory, and provide instructions and data to the processor.
  • the memory may also include non-volatile random access memory.
  • the memory can also store device type information.
  • the memory can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memory, wherein the non-volatile memory can be a read-only memory (read-only memory, ROM) , Programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not limiting illustration, many forms of RAM are available.
  • static random access memory static random access memory
  • dynamic random access memory dynamic random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate synchronous dynamic random access Memory double data date SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • serial link DRAM SLDRAM
  • direct memory bus random access memory direct rambus RAM
  • a computer-readable storage medium is also provided, and at least one instruction is stored in the storage medium, and the instruction is loaded and executed by a processor to implement the method for selecting a clock source as described above.
  • This application provides a computer program.
  • the computer program When the computer program is executed by a computer, it can cause a processor or computer to execute various operations and/or procedures corresponding to the foregoing method embodiments.
  • the computer may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium, (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种用于实现时钟源选取的方法、装置、***及存储介质，属于时钟技术领域。方法包括：第一节点通过第一节点上的第一端口接收第二节点发送的第一报文；当第一报文携带有第一标记时，第一节点在选取时钟源时，不选取第一端口对应的时钟源，第一标记用于指示第二节点的时间同步不确定。当上游的第二节点的时间同步不确定时，通过在第一报文中携带第一标记，以指示该第二节点的时间同步不确定。通过第一端口接收到携带有第一标记的第一报文后，在选择时钟源时，不使用该第一端口对应的时钟源数据选择时钟源，以此避免因上游节点时间同步不确定而使得下游节点的时间发生跳变，进而影响整网的时间跳变及业务的正常进行。

Description

用于实现时钟源选取的方法、装置、***及存储介质 技术领域
本申请涉及时钟技术领域，特别涉及一种用于实现时钟源选取的方法、装置、***及存储介质。
背景技术
当通信和网络应用上越来越多的使用分布式***时，时钟同步变得越来越重要，网络时间协议(network time protocol，NTP)作为一种时钟同步方式，被得到了广泛的应用。此外，为了满足越来越多的高精度时间同步要求，使分布式***内的最精确时钟与其他时钟保持同步的电气和电子工程师协会(institute of electrical and electronics engineers，IEEE)1588协议标准也应运而生。其中，IEEE 1588协议标准全称是网络测量和控制***的精密时钟同步协议标准(IEEE 1588precision clock synchronization protocol)，简称精确定时协议(precision timing protocol，PTP)。无论是在IEEE 1588的应用场景中，还是NTP场景中，如何选取时钟源，是保持时钟同步的关键。
发明内容
本申请实施例提供了一种用于实现时钟源选取的方法、装置、***及存储介质，以解决相关技术提供的问题，技术方案如下：
一方面，提供了一种用于实现时钟源选取的方法，所述方法包括：第一节点通过所述第一节点上的第一端口接收第二节点发送的第一报文；当所述第一报文携带有第一标记时，所述第一节点在选取时钟源时，不选取所述第一端口对应的时钟源，所述第一标记用于指示所述第二节点的时间同步不确定。
第一节点通过第一端口接收到该携带有第一标记的第一报文后，在选择时钟源时，不使用该第一端口对应的时钟源数据选择时钟源，以此避免因上游节点时间同步不确定而使得下游节点的时间发生跳变，进而影响整网的时间跳变及业务的正常进行。
在示例性实施例中，所述第一节点在选取时钟源时，不选取所述第一端口对应的时钟源，包括：所述第一节点在选取时钟源时，不使用通过所述第一端口接收到的时钟源数据选取时钟源。
在示例性实施例中，所述第一节点在选取时钟源时，不使用通过所述第一端口接收的时钟源数据选取时钟源，包括：根据所述第一标记将所述第一端口对应的时钟源数据集设为空集；根据所述第一节点的各端口对应的时钟源数据集选取时钟源。通过将第一端口对应的时钟源数据集设为空集，从而在根据第一节点的各端口对应的时钟源数据集选取时钟源时，不会选取第一端口的时钟源数据，以此避免因上游节点时间同步不确定而使得下游节点的时间发生跳变。
在示例性实施例中，所述第一节点在选取时钟源时，不使用通过所述第一端口接收的时钟源数据选取时钟源，包括：根据所述第一标记将所述第一端口对应的时钟源数据集设为空集；根据所述第一节点的各端口对应的时钟源数据集中的非空时钟源数据集选取时钟源。通过将第一端口对应的时钟源数据集设为空集，在选取时钟源时，根据第一节点的各端口对应 的时钟源数据集中的非空时钟源数据集选取时钟源，无需再筛选空集的时钟源数据集，简化选取流程。
在示例性实施例中，所述根据所述第一标记将所述第一端口对应的时钟源数据集设为空集，包括：基于所述第一标记将所述第一端口的信号异常属性的值设为第一值，用于指示所述第一端口发生信号异常；基于所述信号异常属性的第一值，将所述第一端口对应的时钟源数据集设置为空集。
在示例性实施例中，所述第一端口的信号异常属性为端口信号失效属性portDS.SF，所述portDS.SF的第一值为真TRUE。由于端口信号失效属性portDS.SF为已有标准中定义的属性，基于该端口信号失效属性portDS.SF将第一端口对应的时钟源数据集设置为空集，可以适用于已有的标准，提高本申请实施例提供的方法的适用性。
在示例性实施例中，所述基于所述第一标记将所述第一端口的信号异常属性的值设为第一值，包括：基于所述第一标记确定所述第一端口发生包定时信号失效PTSF事件；基于所述PTSF事件，将所述第一端口的portDS.SF的值设为第一值。
在示例性实施例中，所述PTSF事件为包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件或扩展的PTSF事件。由于包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件为已有标准中定义的事件，可以适用于已有的标准，提高本申请实施例提供的方法的适用性。此外，通过扩展的PTSF事件对PTSF事件进行了扩展，扩展了端口信号失效属性portDS.SF的确定方式。
在示例性实施例中，所述第一报文为声明Announce报文。
在示例性实施例中，所述Announce报文中的同步未确定标记synchronizationUncertain用于携带所述第一标记，当所述synchronizationUncertain的值为第三值时，用于指示所述第二节点的时间同步不确定。
在示例性实施例中，所述synchronizationUncertain的第三值为TRUE。
第二方面，提供了一种用于实现时钟源选取的方法，所述方法包括：第二节点生成第一声明Announce报文，当所述第二节点的时间同步不确定时，所述第一Announce报文中携带的目标参数对应的级别低于基准级别，所述基准级别为所述第二节点在时间同步时所述目标参数对应的级别；向第一节点发送所述第一Announce报文，所述第一Announce报文中携带的参数用于选取时钟源。
在一种实现方式中，该第二节点为中间节点，在生成该第一Announce报文之前还接收上游节点发送的第二Announce报文，相应地，根据该第二Announce报文生成该第一Announce报文。在该实现方式中，该第一Announce报文携带的目标参数劣于该第二Announce报文中携带的目标参数(即将该第二Announce报文中携带的目标参数的级别作为该基准级别)。
在另一种实现方式中，该第二节点为时间服务器时，该第一Announce报文携带的目标参数劣于该时间服务器处于锁定模式时的目标参数(即将该时间服务器处于锁定模式时的目标参数的级别作为该基准级别)。
当上游的第二节点的时间同步不确定时，通过在第一Announce报文中携带级别低于基准级别的目标参数，使得下游的第一节点在选取时钟源时，由于第一Announce报文中的目标参数的级别低，而不选择接收第一Announce报文的端口对应的时钟源，以此避免因上游节点时间同步不确定而使得下游节点的时间发生跳变，进而影响整网的时间跳变及业务的正常进行。
在示例性实施例中，所述目标参数为时钟等级clockclass、时钟精度clockAccuracy，偏移 量刻度的对数方差offsetScaledLogVariance参数中的一个或多个。
在示例性实施例中，所述第二节点生成第一声明Announce报文，包括：所述第二节点接收上游节点发送的第二Announce报文，对所述第二Announce报文中的目标参数的级别进行修改，得到所述第一Announce报文，或者，根据所述第二Announce报文中的信息，生成所述第一声明Announce报文。
第三方面，提供了一种用于实现时钟源选取的装置，所述装置应用于第一节点，所述装置包括：接收模块，用于通过所述第一节点上的第一端口接收第二节点发送的第一报文；选取模块，用于当所述第一报文携带有第一标记时，所述第一节点在选取时钟源时，不选取所述第一端口对应的时钟源，所述第一标记用于指示所述第二节点的时间同步不确定。
在示例性实施例中，所述选取模块，用于在选取时钟源时，不使用通过所述第一端口接收到的时钟源数据选取时钟源。
在示例性实施例中，所述选取模块，用于根据所述第一标记将所述第一端口对应的时钟源数据集设为空集；根据所述第一节点的各端口对应的时钟源数据集选取时钟源，或者，根据所述第一节点的各端口对应的时钟源数据集中的非空时钟源数据集选取时钟源。
在示例性实施例中，所述选取模块，用于基于所述第一标记将所述第一端口的信号异常属性的值设为第一值，用于指示所述第一端口发生信号异常；基于所述信号异常属性的第一值，将所述第一端口对应的时钟源数据集设置为空集。
在示例性实施例中，所述第一端口的信号异常属性为端口信号失效属性portDS.SF，所述portDS.SF的第一值为真TRUE。
在示例性实施例中，所述选取模块，用于基于所述第一标记确定所述第一端口发生包定时信号失效PTSF事件；基于所述PTSF事件，将所述第一端口的portDS.SF的值设为第一值。
在示例性实施例中，所述PTSF事件为包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件或扩展的PTSF事件。
在示例性实施例中，所述第一报文为声明Announce报文。
在示例性实施例中，所述Announce报文中的同步未确定标记synchronizationUncertain用于携带所述第一标记，当所述synchronizationUncertain的值为第三值时，用于指示所述第二节点的时间同步不确定。
在示例性实施例中，所述synchronizationUncertain的第三值为TRUE。
第四方面，提供了一种用于实现时钟源选取的装置，所述装置应用于第二节点，所述装置包括：
生成模块，用于当第二节点的时间同步不确定时，生成第一声明Announce报文，所述第一Announce报文中携带的目标参数对应的级别低于基准级别，所述基准级别为所述第二节点在时间同步时所述目标参数对应的级别；
发送模块，用于将所述第一Announce报文发送至第一节点，所述第一Announce报文中携带的参数用于选取时钟源。
在一种实现方式中，该第二节点为中间节点，该生成模块具体用于根据接收自所述第二节点的上游节点的第二Announce报文生成该第一Announce报文。在该实现方式中，该第一Announce报文携带的目标参数劣于该第二Announce报文中携带的目标参数(即将该第二Announce报文中携带的目标参数的级别作为该基准级别)。
在另一种实现方式中，该第二节点为时间服务器时，该第一Announce报文携带的目标参数劣于该时间服务器处于锁定模式时的目标参数(即将该时间服务器处于锁定模式时的目标参数的级别作为该基准级别)。
在示例性实施例中，所述目标参数为时钟等级clockclass、时钟精度clockAccuracy，偏移量刻度的对数方差offsetScaledLogVariance参数中的一个或多个。
在示例性实施例中，所述生成模块，用于接收上游节点发送的第二Announce报文，对所述第二Announce报文中的目标参数的级别进行修改，得到所述第一Announce报文，或者，根据所述第二Announce报文中的信息，生成所述第一声明Announce报文。
第五方面，提供了一种用于实现时钟源选取的***，所述***包括：第一节点和第二节点；所述第二节点，用于向所述第一节点的第一端口发送第一报文；所述第一节点，用于通过所述第一节点上的第一端口接收所述第二节点发送的第一报文；当所述第一报文携带有第一标记时，所述第一节点在选取时钟源时，不选取所述第一端口对应的时钟源，所述第一标记用于指示所述第二节点的时间同步不确定。
在示例性实施例中，所述第一节点，用于在选取时钟源时，不使用通过所述第一端口接收到的时钟源数据选取时钟源。
在示例性实施例中，所述第一节点，用于根据所述第一标记将所述第一端口对应的时钟源数据集设为空集；根据所述第一节点的各端口对应的时钟源数据集选取时钟源，或者，根据所述第一节点的各端口对应的时钟源数据集中的非空时钟源数据集选取时钟源。
在示例性实施例中，所述第一节点，用于基于所述第一标记将所述第一端口的信号异常属性的值设为第一值，用于指示所述第一端口发生信号异常；基于所述信号异常属性的第一值，将所述第一端口对应的时钟源数据集设置为空集。
在示例性实施例中，所述第一端口的信号异常属性为端口信号失效属性portDS.SF，所述portDS.SF的第一值为真TRUE。
在示例性实施例中，所述第一节点，用于基于所述第一标记确定所述第一端口发生包定时信号失效PTSF事件；基于所述PTSF事件，将所述第一端口的portDS.SF的值设为第一值。
在示例性实施例中，所述PTSF事件为包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件或扩展的PTSF事件。
在示例性实施例中，所述第一报文为声明Announce报文。
在示例性实施例中，所述Announce报文中的同步未确定标记synchronizationUncertain用于携带所述第一标记，当所述synchronizationUncertain的值为第三值时，用于指示所述第二节点的时间同步不确定。
在示例性实施例中，所述synchronizationUncertain的第三值为TRUE。
第六方面，提供了一种用于实现时钟源选取的***，所述***包括：第一节点和第二节点；所述第二节点，用于当所述第二节点的时间同步不确定时，生成第一声明Announce报文，所述第一Announce报文中携带的目标参数对应的级别低于基准级别，所述基准级别为所述第二节点在时间同步时所述目标参数对应的级别；向第一节点发送所述第一Announce报文；所述第一节点，用于接收所述第二节点发送的所述第一Announce报文，所述第一Announce报文中携带的参数用于选取时钟源。
在一种实现方式中，该第二节点为中间节点，还用于在生成该第一Announce报文之前接 收上游节点发送的第二Announce报文，相应地，在生成该第一Announce报文时具体用于根据该第二Announce报文生成该第一Announce报文。在该实现方式中，该第一Announce报文携带的目标参数劣于该第二Announce报文中携带的目标参数(即将该第二Announce报文中携带的目标参数的级别作为该基准级别)。
在另一种实现方式中，该第二节点为时间服务器时，该第一Announce报文携带的目标参数劣于该时间服务器处于锁定模式时的目标参数(即将该时间服务器处于锁定模式时的目标参数的级别作为该基准级别)。
在示例性实施例中，所述目标参数为时钟等级clockclass、时钟精度clockAccuracy，偏移量刻度的对数方差offsetScaledLogVariance参数中的一个或多个。
在示例性实施例中，所述第二节点，用于接收上游节点发送的第二Announce报文，对所述第二Announce报文中的目标参数的级别进行修改，得到所述第一Announce报文，或者，根据所述第二Announce报文中的信息，生成所述第一声明Announce报文。
还提供一种用于实现时钟源选取的设备，所述设备包括：端口及处理器，所述端口用于与其他节点通信，所述处理器用于实现上述任一所述的用于实现时钟源选取的方法。当所述用于实现时钟源选取的设备为第一节点时，所述端口为上述第一端口。
还提供了一种计算机可读存储介质，所述存储介质中存储有至少一条指令，所述指令由处理器加载并执行以实现如上任一所述的用于实现时钟源选取的方法。
提供了另一种通信装置，该装置包括：收发器、存储器和处理器。其中，该收发器、该存储器和该处理器通过内部连接通路互相通信，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制收发器接收信号，并控制收发器发送信号，并且当该处理器执行该存储器存储的指令时，使得该处理器执行上述任一种可能的实施方式中的方法。
作为一种示例性实施例，所述处理器为一个或多个，所述存储器为一个或多个。
作为一种示例性实施例，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
提供了一种计算机程序(产品)，所述计算机程序(产品)包括：计算机程序代码，当所述计算机程序代码被计算机运行时，使得所述计算机执行上述各方面中的方法。
提供了一种芯片，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有所述芯片的通信设备执行上述各方面中的方法。
提供另一种芯片，包括：输入接口、输出接口、处理器和存储器，所述输入接口、输出接口、所述处理器以及所述存储器之间通过内部连接通路相连，所述处理器用于执行所述存储器中的代码，当所述代码被执行时，所述处理器用于执行上述各方面中的方法。
附图说明
图1为本申请实施例提供的1588同步网络场景示意图；
图2为本申请实施例提供的用于实现时钟源选取的方法流程图；
图3为本申请实施例提供的用于实现时钟源选取的方法流程图；
图4为本申请实施例提供的用于实现时钟源选取的方法流程图；
图5为本申请实施例提供的用于实现时钟源选取的方法流程图；
图6为本申请实施例提供的用于实现时钟源选取的方法流程图；
图7为本申请实施例提供的用于实现时钟源选取的方法流程图；
图8为本申请实施例提供的用于实现时钟源选取的方法流程图；
图9为本申请实施例提供的用于实现时钟源选取的装置结构示意图；
图10为本申请实施例提供的用于实现时钟源选取的装置结构示意图；
图11为本申请实施例提供的用于实现时钟源选取的设备的结构示意图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
在IEEE 1588或NTP的应用场景中，当网络中的某一节点因掉电或故障修复等原因重启或切换时钟源时，该节点的输出时间相比重启或切换时钟源之前会有跳变。如果下游节点以该掉电重启或故障修复重启或选时钟源时的节点作为时钟源，则下游节点的输出时间也会有跳变，进而会影响整网的时间跳变以及业务的正常进行。
以图1所示的IEEE 1588同步网络场景为例，该网络中包括节点A、B、C、D、E和F几个节点。其中，节点E包括两个端口，端口1和端口2。端口1对应于节点B，用于接收节点B发送的PTP报文。端口2对应于节点D，用于接收节点D发送的PTP报文。在正常情况下，节点A和节点C都跟踪全球定位***(global positioning system，GPS)，节点A和节点C发给下游节点B和节点D的声明(Announce)报文里的时钟等级(clockClass)为6，并且Announce报文中其它代表IEEE 1588质量等级的参数，如时钟精度(clockAccuracy)，偏移量刻度的对数方差(offsetScaledLogVariance)等也相同。节点B和节点D发给下游节点E的Announce报文里的clockClass也为6，Announce报文里的其它代表IEEE 1588质量等级的参数，如clockAccuracy，offsetScaledLogVariance等也相同。
各个节点的端口具备四种端口状态，包括主状态(master，M)、从状态(slave，S)、被动状态(passive，P)和未校准(UNCALIBRATED)状态。端口状态为Master的通信端口简称为Master端口，Master端口用来向整个网络广播本节点选取的质量最好的时钟源；Slave状态的端口(简称Slave端口)和UNCALIBRATED状态的端口用来跟踪上游节点的时钟，在利用某一端口跟踪上游节点的时钟进行时间同步的过程中，该端口的状态会根据时间同步的状态由Slave状态转为UNCALIBRATED状态，或由UNCALIBRATED状态转为Slave状态；Passive端口处于一个中间地位，既不广播时钟源，也不跟踪上游节点的时钟。端口状态出现Passive，一般意味着在整个PTP网络***中有两个或者两个以上的时钟源质量不相上下。如图1所示，以节点E上对应于节点B的端口的状态为slave，节点E上对应于节点D的端口的状态为passive为例。根据IEEE1588v2协议和国际电信联盟电信标准分局(International Telecommunication Union Telecommunication Standardization Sector，ITU-T)G.8275.1协议，节点E基于最好主时钟(best master clock，BMC)算法选择节点B或者节点D为跟踪的时钟源。以图1中节点A的clockID小于节点C的clockID为例，节点E的主跟踪路径为A->B->E，而备路径为C->D->E。
如果节点B掉电，节点E会选择备路径C->D->E进行同步，节点E可以保证输出给节点F的时间无跳变。当节点B重新上电后，节点A向节点B发PTP报文，因而节点B会首先同步于节点A，即基于节点A的PTP报文与节点A的时间进行同步。在与节点A的时间进行同步的过程中， 节点B的时间同步不确定，其中，节点的时间同步不确定是指在同步时间段内，节点的时间有大的调整。关于确定时间有大的调整的方式，本申请实施例不进行限定，示例性地，包括但不限于基于如下三种情况确定时间有大的调整。其中，在情况1、2A和3A中，该节点为中间节点，在情况2B和3B中，该节点为源节点(即时间服务器)。源节点指的是通过直接跟踪卫星信号(如GPS信号)进行时间同步的节点，如图1中的节点A、C。中间节点指的是通过跟踪上游节点进行时间同步的节点，如图1中的节点B、D、E、F。相应地，源节点的时钟源信号为跟踪的卫星信号，中间节点的时钟源信号为通过跟踪上游节点获得的时间信号，通常可以认为是上游节点的时间信号。
情况1：节点重启或者切换时钟源，该节点的入端口处于未校准状态(UNCALIBRATED state)，表明该节点正在做时钟同步，而这种情况下，通常该节点的时间有大的调整，因而在该种情况下，判断节点的时间同步不确定。
在示例性实施例中，该种情况下，可认为参考时长之后，该节点的时间同步确定。其中，参考时长可基于经验设定，也可以基于应用场景设定，本申请实施例不对参考时长进行限定。
情况2：包括情况2A和情况2B。
情况2A：该节点为中间节点。该节点周期性检测与时钟源信号的时间的时间差(即与上游节点的时间差)是否小于阈值如果时间差大于阈值，可以理解为该节点的入端口处于未校准状态(UNCALIBRATED state)。而这种情况下，通常该节点的时间有大的调整，因而判断节点的时间同步不确定。
情况2B：该节点为源节点(即时间服务器)。该节点周期性检测与时钟源信号的时间的时间差(即与接收的卫星信号的时间的时间差)是否小于阈值，如果时间差大于阈值，确定该节点的时间同步不确定。
情况3：包括情况3A和情况3B。
情况3A：该节点为中间节点。该节点重启或者换时钟源后，检测与上游节点的时间差是否小于阈值，如果时间差大于阈值，可以理解为该节点的入端口处于未校准状态(UNCALIBRATED state)。而这种情况下，通常该节点的时间有大的调整，因而判断节点的时间同步不确定。
情况3B：该节点为源节点。该节点重启或者切换时钟源后，检测与接收的卫星信号的时间差是否小于阈值，如果时间差大于阈值，确定该节点的时间同步不确定。
可以理解的是，上述情况2和情况3均以检测与上游节点的时间差大于阈值来判断节点的时间同步不确定，对于检测出与上游节点的时间差小于阈值的情况，可判断节点的时间同步。此外，情况2A、2B、3A、3B中的阈值可以相同，也可以不同，该阈值的大小可基于经验设置，也可以基于应用场景限定，本申请实施例不对阈值大小进行限定。
以图1为例，节点B在时间同步过程中，节点B的时间会按照节点A的时间(即时钟源信号中的时间)进行调整。另外，节点B还通过节点B与节点A的时间差是否小于阈值，可以判断节点B的时间是否同步。例如，节点B接收到节点A的PTP报文后，基于节点A的PTP报文计算节点B与节点A之间的时间差。如果时间差小于阈值，则表明节点B的时间与该时钟源信号的时间同步，即节点B的时间处于同步确定状态(后续将处于同步确定状态简称为同步确定、或同步)，如果时间差不小于阈值，则表明节点B的时间处于同步不确定状态(后续将处于同步不确定状态简称为同步不确定)。
对应节点B的时间同步不确定的情况，则节点B的输出时间有跳变。如果节点B向节点E发送PTP报文，会导致节点E选择对应于接收PTP报文的端口的时钟源，从而使得节点E的输 出时间也有跳变。这种情况在1588的应用中是需要避免的，否则会影响整网的时间跳变以及业务正常工作。以上仅以IEEE1588场景为例进行了说明，对于NTP，在时钟同步时，也同样存在因节点的输出时间跳变，导致影响整网的时间跳变以及业务正常工作的问题。
对此，本申请实施例提供了一种选取时钟源的方法，该方法通过在第一报文里携带第一标记向下游节点通知本时钟源路径上的各个节点的时间是否同步。下游节点如果检测到上游时钟源的时间同步不确定，下游节点不选中对应于该上游节点的端口的时钟源，这样可以避免下游节点的输出时间受影响。接下来，以上游节点为第二节点，下游节点为第一节点，由第一节点选取时钟源为例，对本申请实施例提供的选取时钟源的方法进行说明。如图2所示，该方法包括如下过程：
201，第一节点通过第一节点上的第一端口接收第二节点发送的第一报文。
第一节点连接一个或多个上游的第二节点，该第一节点通过该第一节点上的第一端口可以接收第二节点发送的第一报文，该第一报文包括但不限于PTP报文或NTP报文。示例性地，以第一报文为PTP报文中的任一类型的报文为例，在IEEE1588v1中有五种PTP报文，分别为同步(sync)报文、跟随(follow_up)报文、延迟请求(delay_req)报文、延迟响应(delay_resp)报文和管理(management)报文。verision2在verision1的基础上，增加了点延迟机制(peer-delay mechanism)中的三种PTP报文，分别为点延迟请求(Pdelay_req)报文、点延迟响应(Pdelay_resp)报文和点延迟响应跟随(Pdelay_resp_Follow_up)报文。此外，还增加了信号(signaling)报文和声明(Announce)报文。
其中，sync、delay_req、follow_up和delay_resp等报文通过应答机制(delay request-response mechanism)用于产生和通信用于同步普通时钟和边界时钟的时间信息。Pdelay_req、Pdelay_resp和Pdelay_resp_Follow_up等报文通过对等延迟机制(peer delay mechanism)用于测量两个时钟端口(port)之间的链接延时。Announce报文用于建立同步路径，发送Announce报文的节点和根节点的状态和特征信息；management报文用于查询和更新时钟所维护的PTP数据集，signaling报文用于其他目的，例如在主从之间协调单播报文的发送频率。在本申请实施例提供的方法中，第一节点通过该第一端口可以接收第二节点向第一节点发送的上述任一种第一报文。
在示例性实施例中，如果第二节点因掉电重启或者故障修复重启，未同步到该第二节点的上游节点的时间，则可以通过在第一报文中携带第一标记来向下游节点通知该上游的第二节点的时间同步不确定。在本申请实施例提供的方法中，该第一标记可以携带在第一报文的已有字段中，也可以携带在第一报文新定义的字段中，本申请实施例不对第一报文携带第一标记的方式进行限定。
以该第二节点向第一节点的第一端口发送的第一报文为Announce报文为例，如果第二节点的时间同步不确定，则第二节点向第一节点发送的Announce报文中携带第一标记，通过第一标记指示第二节点的时间同步不确定。在示例性实施例中，该第一标记可以携带在Announce报文的已有字段中，也可以携带在Announce报文新增的字段中。以将第一标记携带在Announce报文的已有字段中为例，可以通过Announce报文中的同步不确定标记(synchronizationUncertain)携带第一标记。示例性地，当synchronizationUncertain的值为TURE时，用于指示第二节点的时间同步不确定。或者，该synchronizationUncertain的值还可以是TURE和FLASE之外的其他值，本申请实施例不对用于指示第二节点的时间同步不确定的synchronizationUncertain的值进行限定。此外，无论用于指示第二节点的时间同步不确定的synchronizationUncertain的值为哪种表现形式，第二节点发送的Announce报文中除了携带第一 标记外，还可以携带其他参数，例如，携带的参数包括clockClass，clockAccuracy和offsetScaledLogVariance等。
除了采用Announce报文中的synchronizationUncertain来携带第一标记的方式外，本申请实施例提供的方法还支持在第二节点的时间同步不确定时，采用Announce报文中的其他参数来携带第一标记。示例性地，当第二节点确定时间同步不确定时，该第二节点将要发送的Announce报文中的clockClass，clockAccuracy和offsetScaledLogVariance等参数中的一个或多个参数的值设为特定值，通过该特定值指示第二节点的时间同步不确定。以图1所示的网络为例，在正常情况下，节点A和节点C都跟踪GPS后，节点A和节点C发给下游节点B和节点D的Announce报文里的clockClass为6。第二节点确定第二节点的时间同步不确定时，第二节点将Announce报文的clockClass设为187或248之后发送至第一节点，由此通过clockClass为特定值187或248的方式来指示第二节点的时间同步不确定，使得第一节点不会选择第二节点作为时钟源。
需要说明的是，采用上述哪种方式来携带第一标记，本申请实施例不进行限定。考虑到IEEE 1588v2标准中，当节点在slave端口状态下，选中某个时钟源后，该节点在master端口发送出去的Announce报文的clockClass应该是slave端口收到的clockClass，而不应该是将slave端口收到的clockClass降级后再发出去。对此，如果在不更改已有的IEEE 1588v2标准的情况下，可以采用上述通过Announce报文中的synchronizationUncertain来携带第一标记的方式。
202，当第一报文携带有第一标记时，第一节点在选取时钟源时，不选取第一端口对应的时钟源，第一标记用于指示第二节点的时间同步不确定。
第一节点接收到第二节点发送的第一报文后，第一节点对该第一报文进行解析。如果解析得到该第一报文携带了第一标记，则可以确定第二节点的时间同步不确定，在选取时钟源时，不选取第一端口对应的时钟源。示例性地，第一节点在选取时钟源时，不选取第一端口对应的时钟源的方式，包括但不限于第一节点在选取时钟源时，不使用通过第一端口接收到的时钟源数据选取时钟源。第一节点通过第一端口接收该第一报文，在选取时钟源时，不使用通过第一端口接收到的时钟源数据选取时钟源，也就不会选取对应于第一端口的时钟源，避免了时间跳变。
在示例性实施例中，第一节点的第一端口接收到携带了第一标记的第一报文后，由于该第一标记指示第二节点的时间同步不确定，因而第一节点可以对第二节点的时间同步不确定状态进行记录。例如，第一节点记录第一端口接收到了携带第一标记的第一报文，使得第一节点在选取时钟源时，基于记录的第二节点的时间同步不确定状态使得第一节点不使用第一端口接收到的时钟源数据，从而在选取时钟源时不会选取对应于第一端口的时钟源。
除上述记录第一标记对应的端口的方式外，第一节点的每个端口都有时钟源数据集。例如，以第一报文为annouce报文为例，该第一报文中除了携带第一标记，还携带时钟源数据，例如clockClass、clockID，而时钟源数据集中包括annouce报文中的如clockClass、clockID等时钟源数据，因此，在第二节点的时间同步不确定的情况下，第一节点在选取时钟源时，不使用通过第一端口接收到的时钟源数据选取时钟源，还可以包括但不限于如下两种方式：
方式一：第一节点在选取时钟源时，根据第一标记将第一端口对应的时钟源数据集设为空集；根据第一节点的各端口对应的时钟源数据集选取时钟源。
该方式一中，由于第一报文中携带了第一标记，而该第一标记指示第二节点的时间同步不确定，第一节点在选取时钟源时，根据第一标记将第一端口对应的时钟源数据集设置为空集，之后再根据第一节点的各个端口对应的时钟源数据集选取时钟源。第一节点的各个端口 对应的时钟源数据集包括该第一端口对应的时钟源数据集，也就是说，第一节点在选取时钟源时，第一节点可以获取第一节点的所有端口对应的时钟源数据集，之后将所有时钟源数据集中的时钟源数据进行比对，选取出时钟源。由于该第一端口对应的时钟源数据集为空集，因而也就不会使用通过第一端口接收到的时钟源数据选取时钟源。例如，选取时钟源的方式可参见2018年3月发布的ITU-T G.8275.1和G.8275.2的BMC选源流程。
方式二：第一节点在选取时钟源时，根据第一标记将第一端口对应的时钟源数据集设为空集；根据第一节点的各端口对应的时钟源数据集中的非空时钟源数据集中的时钟源数据选取时钟源。
该方式二中，同样由于第一报文中携带了第一标记，而该第一标记指示第二节点的时间同步不确定，第一节点在选取时钟源时，根据第一标记将第一端口对应的时钟源数据集设置为空集。与方式一不同的是，该方式二中，第一节点将第一端口对应的时钟源数据集设置为空集后，并不是根据第一节点的所有端口对应的时钟源数据集选取时钟源，而是仅获取非空时钟源数据集，根据非空时钟源数据集选取时钟源。也就是说，方式二中第一节点是将非空时钟源数据集中的时钟源数据进行比对，从而选取出时钟源。
在示例性实施例中，无论是上述方式一，还是上述方式二，第一节点在选取时钟源时，根据第一标记将第一端口对应的时钟源数据集设为空集的方式，包括但不限于：第一节点在选取时钟源时，基于第一标记将第一端口的信号异常属性的值设为第一值，用于指示第一端口发生信号异常；基于信号异常属性的第一值，将第一端口对应的时钟源数据集设置为空集。
例如，当前ITU-T G.8275.2定义了信号失效属性portDS.SF，如果第一端口的portDS.SF的值为第一值，例如为真(TRUE)，那么第一节点将该第一端口对应的时钟源数据集(Erbest)设置为空集。因此，在本申请实施例提供的方法中，可将端口的信号失效属性portDS.SF作为信号异常属性，如果第一端口的portDS.SF的第一值为TRUE，则将该第一端口的时钟源数据集(Erbest)设置为空集。
其中，第一端口的portDS.SF的值可以通过包定时信号失效(packet timing signal fail，PTSF)事件来确定，示例性地，基于第一标记将第一端口的信号异常属性的值设为第一值，包括：基于第一标记确定第一端口发生PTSF事件；基于该PTSF事件，将第一端口的portDS.SF的值设为第一值。其中，PTSF事件的默认值可以为FALSE，表明没有发生PTSF事件。发生PTSF事件后，可以将PTSF事件的值设为TRUE。当PTSF事件的值为TURE时，将第一端口的portDS.SF的值设为第一值。
例如，在ITU-T G.8275.2中，portDS.SF这个属性是根据包定时信号失效-丢失同步(PTSF-lossSync)事件和包定时信号失效-不可用(PTSF-unusable)事件来确定的，如果端口接收不到PTP报文，那么确定发生了PTSF-lossSync事件，将该PTSF-lossSync事件的值设为第二值(例如第二值为TRUE)，否则为FALSE；如果端口接收到的PTP报文的性能超过本节点的容忍范围，那么确定发生了PTSF-unusable事件，将该PTSF-unusable事件的值设为第二值(例如第二值为TRUE)，否则为FALSE。如果发生PTSF-lossSync事件或者PTSF-unusable事件，那么portDS.SF的值为TRUE。则在本申请实施例提供的方法中，可以基于第一标记确定发生PTSF-lossSync事件或者PTSF-unusable事件，从而使得portDS.SF的值为第一值(例如TRUE)。此外，本申请实施例提供的方法还支持扩展新的PTSF事件来触发将第一端口的portDS.SF这个属性的值设置为第一值。示例性地，将接收到的Announce报文中的synchronizationUncertain对应一个新的扩展的PTSF事件，例如：扩展的PTSF事件命名为包定时信号失效-同步不确定(PTSF-syncUncertain)事件，用于指示第一端口因上游节点的时间 同步不确定发生信号异常。当接收到的Announce报文中的synchronizationUncertain的值为TRUE，那么确定发生PTSF-syncUncertain事件，将该PTSF-syncUncertain事件的值设为第二值(例如TRUE)，则将portDS.SF的值设为第一值。
综上所述，如果发生PTSF-lossSync事件，PTSF-unusable事件或者扩展的PTSF事件(例如PTSF-syncUncertain)，那么portDS.SF的值为TRUE，从而将第一端口的Erbest设置为空集，使得第一节点在选取时钟源时，不使用该第一端口对应的时钟源数据。因此，基于第一标记将第一端口的信号异常属性的值设为第一值，包括但不限于如下方式：
方式一：以扩展的PTSF事件为PTSF-syncUncertain事件为例，基于第一标记确定第一端口发生PTSF-syncUncertain事件，用于指示第一端口因上游节点的时间同步不确定发生信号异常事件；基于PTSF-syncUncertain事件，将第一端口的portDS.SF的值设为第一值。
示例性地，发生PTSF-syncUncertain事件，将该PTSF-syncUncertain事件的值设为第二值，如第二值为TRUE，也即当发生PTSF-syncUncertain事件时，指示第一端口因上游节点的时间同步不确定发生信号异常事件，因而触发将第一端口的portDS.SF的值设为第一值，例如portDS.SF的值为TRUE，由此触发将第一端口对应的时钟源数据集设为空集。除此之外，发生PTSF-syncUncertain事件时，将该PTSF-syncUncertain事件的第二值还可以设为FALSE，也即当发生PTSF-syncUncertain事件时，PTSF-syncUncertain事件的值为FALSE，指示第一端口因上游节点的时间同步不确定发生信号异常事件，因而触发将第一端口的portDS.SF的值设为第一值，例如portDS.SF的值为TRUE，由此触发将第一端口对应的时钟源数据集设为空集。又或者，PTSF-syncUncertain事件的第二值还可以为除了TRUE和FALSE之外的其他表现形式，本申请实施例对此不加以限定。
方式二：基于第一标记确定第一端口发生PTSF-lossSync事件；基于PTSF-lossSync事件，将第一端口的portDS.SF的值设为第一值。
示例性地，发生PTSF-lossSync事件，将该PTSF-lossSync事件的值设为第二值，该第二值为TRUE，也即当PTSF-lossSync事件的值为TRUE时，指示第一端口因上游节点的时间同步不确定发生信号异常事件，因而触发将第一端口的portDS.SF的值设为第一值，例如portDS.SF的值为TRUE，由此触发将第一端口对应的时钟源数据集设为空集。或者，PTSF-lossSync事件的第二值还可以为除了TRUE之外的其他表现形式，本申请实施例对此不加以限定。
方式三：基于第一标记确定第一端口发生PTSF-unusable事件；基于PTSF-unusable事件，将第一端口的portDS.SF的值设为第一值。
示例性地，发生PTSF-unusable事件，将该PTSF-unusable事件的值设为第二值，例如第二值为TRUE，也即当PTSF-unusable事件的值为TRUE时，指示第一端口因上游节点的时间同步不确定发生信号异常事件，因而触发将第一端口的portDS.SF的值设为第一值，例如portDS.SF的值为TRUE，由此触发将第一端口对应的时钟源数据集设为空集。或者，PTSF-unusable事件的第二值还可以为除了TRUE之外的其他表现形式，本申请实施例对此不加以限定。
本申请实施例提供的方法，当上游的第二节点的时间同步不确定时，通过在第一报文中携带第一标记，以指示该第二节点的时间同步不确定。使得下游的第一节点通过第一端口接收到该携带有第一标记的第一报文后，在选择时钟源时，不使用该第一端口对应的时钟源数据选择时钟源，以此避免因上游节点时间同步不确定而使得下游节点的时间发生跳变，进而影响整网的时间跳变及业务的正常进行。
接下来，以图1所示的网络为例，对本申请实施例提供的方法所涉及的几种可能的实施方 式进行举例说明。其中，图1中的节点E为第一节点，节点B为第二节点，第一报文为Announce报文。如图3所示，用于实现时钟源选取的方法包括：
301，节点B时间同步不确定时，向节点E发送Announce报文，该Announce报文中的synchronizationUncertain的值为TRUE。
302，节点E的第一端口接收到该Announce报文，解析得到Announce报文中的synchronizationUncertain的值为TRUE，将第一端口对应的时钟源数据集设为空集。
303，节点E获取节点E的所有端口的时钟源数据集，包括数据集为空集的时钟源数据集，以及数据集为非空的时钟源数据集。
304，节点E根据非空的时钟源数据集中的时钟源数据选取时钟源，不会使用第一端口对应的时钟源数据选取时钟源。
其中，节点E选取时钟源的过程，可参见2018年3月发布的ITU-T G.8275.1和G.8275.2的BMC选源流程。
仍以图1所示的网络，其中，图1中的节点E为第一节点，节点B为第二节点，第一报文为Announce报文为例，对本申请实施例提供的方法进行举例说明。如图4所示，用于实现时钟源选取的方法包括：
401，节点B时间同步不确定时，向节点E发送Announce报文，该Announce报文中的synchronizationUncertain的值为TRUE。
402，节点E的第一端口接收到该Announce报文，解析得到Announce报文中的synchronizationUncertain的值为TRUE，将第一端口的portDS.SF的值设为TRUE。
403，节点E基于portDS.SF的值，将第一端口对应的时钟源数据集设置为空集。
404，节点E获取节点E的所有端口的时钟源数据集，包括数据集为空集的时钟源数据集，以及数据集为非空的时钟源数据集。
405，节点E根据非空的时钟源数据集中的时钟源数据选取时钟源，不会使用第一端口对应的时钟源数据选取时钟源。
其中，节点E选取时钟源的过程，可参见2018年3月发布的ITU-T G.8275.1和G.8275.2的BMC选源流程。
仍以图1所示的网络，其中，图1中的节点E为第一节点，节点B为第二节点，第一报文为Announce报文为例，对本申请实施例提供的方法进行举例说明。如图5所示，用于实现时钟源选取的方法包括：
501，节点B时间同步不确定时，向节点E发送Announce报文，该Announce报文中的synchronizationUncertain的值为TRUE。
502，节点E的第一端口接收到该Announce报文，解析得到Announce报文中的synchronizationUncertain的值为TRUE，确定第一端口发生PTSF-syncUncertain事件。
503，节点E基于PTSF-syncUncertain事件将第一端口的portDS.SF的值设为TRUE。
504，节点E基于portDS.SF的值，将第一端口对应的时钟源数据集设置为空。
505，节点E获取节点E的所有端口的时钟源数据集，包括数据集为空集的时钟源数据集，以及数据集为非空的时钟源数据集。
506，节点E根据非空的时钟源数据集中的时钟源数据选取时钟源，不会使用第一端口对应的时钟源数据选取时钟源。
其中，节点E选取时钟源的过程，可参见2018年3月发布的ITU-T G.8275.1和G.8275.2的BMC选源流程。
仍以图1所示的网络，其中，图1中的节点E为第一节点，节点B为第二节点，第一报文为Announce报文为例，对本申请实施例提供的方法进行举例说明。如图6所示，用于实现时钟源选取的方法包括：
601，节点B时间同步不确定时，向节点E发送Announce报文，该Announce报文中的synchronizationUncertain的值为TRUE。
602，节点E的第一端口接收到该Announce报文，解析得到Announce报文中的synchronizationUncertain的值为TRUE，确定第一端口发生PTSF-lossSync事件。
603，节点E基于PTSF-lossSync事件将第一端口的portDS.SF的值设为TRUE。
604，节点E基于portDS.SF的值，将第一端口的时钟源数据集设置为空。
605，节点E获取节点E的所有端口的时钟源数据集，包括数据集为空集的时钟源数据集，以及数据集为非空的时钟源数据集。
606，节点E根据非空的时钟源数据集中的时钟源数据选取时钟源，不会使用第一端口对应的时钟源数据选取时钟源。
其中，节点E选取时钟源的过程，选源流程可参见2018年3月发布的ITU-T G.8275.1和G.8275.2的BMC选源流程。
仍以图1所示的网络，其中，图1中的节点E为第一节点，节点B为第二节点，第一报文为Announce报文为例，对本申请实施例提供的方法进行举例说明。如图7所示，用于实现时钟源选取的方法包括：
701，节点B时间同步不确定时，向节点E发送Announce报文，该Announce报文中的synchronizationUncertain的值为TRUE。
702，节点E的第一端口接收到该Announce报文，解析得到Announce报文中的synchronizationUncertain的值为TRUE，确定第一端口发生PTSF-unusable事件。
703，节点E基于PTSF-unusable事件将第一端口的portDS.SF的值设为TRUE。
704，节点E基于portDS.SF的值，将第一端口的时钟源数据集设置为空。
705，节点E获取节点E的所有端口的时钟源数据集，包括数据集为空集的时钟源数据集，以及数据集为非空的时钟源数据集。
706，节点E根据非空的时钟源数据集中的时钟源数据选取时钟源，不会使用第一端口对应的时钟源数据选取时钟源。
其中，节点E选取时钟源的过程，可参见2018年3月发布的ITU-T G.8275.1和G.8275.2的BMC选源流程。
需要说明的是，上述图2-图7所示实施例中，仅以第二节点时间同步不确定的情况下，第一节点通过第一节点的第一端口接收第二节点发送的携带有第一标记的第一报文后，不选取第一端口对应的时钟源，从而避免时间跳变为例进行了说明。如果后续第二节点的时间同步了，则向第一节点发送第二报文，该第二报文里可以携带第二标记，该第二标记用于指示第二节点的时间同步。第一节点接收到携带了第二标记的第二报文后，可以将第一节点上对应于第二节点的端口的时钟源数据集不设置为空集，从而将第一端口对应的时钟源作为选择对 象，据此选取时钟源。例如，仍以图1所示的网络为例，当节点B的时间同步后，节点B在master端口发送出去的Announce报文的同步不确定标记synchronizationUncertain的值为FALSE，即通过synchronizationUncertain的值携带第二标记，以此向下游通知该节点B的时间已同步。节点E基于BMC算法选择节点B或者节点D为跟踪的时钟源。由于下游的节点E在端口1接收到节点B的Announce报文后，解析得到节点B的Announce报文的synchronizationUncertain的值为FALSE，那么节点E将端口1的Erbest数据集等于节点B的Announce报文信息，仍以图1中节点A的clockID小于节点C的clockID为例，则节点E会重新选择端口1跟踪到节点B。
在示例性实施例中，除上述通过第一标记指示第二节点的时间同步不确定，从而使得下游的第一节点不选择接收第二节点的第一报文的第一端口对应的时钟源的方式外，本申请实施例提供的方法还支持以参数降级的方式，来使得该第一端口的时钟源不被选中，从而避免第一节点发生时间跳变。具体实现方式包括如下方法中的实施方式A和实施方式B。
如图8所示，本申请实施例提供的用于实现时钟源选取的方法包括：
801，第二节点生成第一Announce报文，该第一Announce报文包括目标参数。
该第一Announce报文中的目标参数包括第一目标参数和第二目标参数中的至少一项。
该第一目标参数用于表征主时钟优先级，如PTP协议中的主时钟优先级1(grandmasterPriority1)、主时钟优先级2(grandmasterPriority2)。
该第二目标参数用于表征主时钟质量，如PTP协议中的主时钟质量(grandmasterClockQuality)，具体可以包括如下质量参数中的至少一项：
用于表征时钟的国际原子时间TAI可追溯性的参数，如PTP协议中的时钟等级(clockclass)；
用于表征时钟精度的参数，如PTP协议中的时钟精度(clockAccuracy)；
用于表征时钟稳定性的参数，如偏移量刻度的对数方差(offsetScaledLogVariance)。
该第二节点具体可以是中间节点，也可以是源节点。当为中间节点时，在步骤801之前还会先接收上游节点发送的第二Announce报文，并在步骤801中根据该第二Announce报文生成该第一Announce报文。
如前所述，该第二节点的时间可能处于同步确定状态，也可能处于同步不确定状态。根据本申请实施例，当该第二节点的时间处于同步不确定状态时，该第一Announce报文携带的目标参数为较劣的参数，当该第二节点的时间处于同步确定状态时，该第一Announce报文携带的目标参数为较优的参数。
在实施方式A中，当该第二节点的时间同步不确定(即处于同步不确定状态)时，第一Announce报文中携带的目标参数对应的级别低于基准级别，基准级别为第二节点在时间同步时(即处于同步确定状态时)目标参数对应的级别。在具体实现时，可以将该第一Announce报文中的目标参数设置为预设的值，该预设的值对应的级别低于该基准级别，如，该目标参数包括clockclass和clockAccuracy，clockclass对应的预设的值为248，clockAccuracy对应的预设的值为未知(unknown)。另外，当该第二节点的时间同步时，第一Announce报文中携带的目标参数对应的级别为该基准级别。
当该第二节点为中间节点时，可以将该第二Announce报文中携带的目标参数的级别作为该基准级别，相应地，该第一Announce报文携带的目标参数劣于该第二Announce报文中携带的目标参数。如，该第二Announce报文中携带的clockclass为6，该第一Announce报文中携带的clockclass的值为大于6的值，如187或248。需要说明的是，当该目标参数包括不止一个参数时，该第一Announce报文携带的目标参数劣于该第二Announce报文中携带的目标参数指的是， 该第一Announce报文携带的目标参数中的所有参数均劣于该第二Announce报文中携带的目标参数中对应的参数。如，该目标参数包括clockclass和clockAccuracy，则该第一Announce报文携带的clockclass劣于该第二Announce报文中携带的clockclass，且该第一Announce报文携带的clockAccuracy劣于该第二Announce报文中携带的clockAccuracy。
当该第二节点为源节点(即时间服务器)时，可以将时间服务器处于锁定模式时的目标参数对应的级别作为该基准级别，相应地，该第一Announce报文携带的目标参数劣于该时间服务器处于锁定模式时的目标参数。该时间服务器处于锁定模式时的目标参数可以是PTP协议所定义的。如，PTP协议定义时间服务器处于锁定模式时的clockclass为6，该第一Announce报文中携带的clockclass的值为大于6的值，如248。另外，当该时间服务器的时间同步确定时，第一Announce报文中携带的目标参数为该时间服务器处于锁定模式时的目标参数。
由于目标参数对应的级别低于基准级别，使得第一节点在选取时钟源时，选取接收该第一Announce报文的端口对应的时钟源的可能性较低。
需要说明的是，标准不同，第二节点在时间同步时目标参数对应的基准级别不同，基准级别不同，目标参数的值不同。各节点的基准级别通常是相同的，对于各节点的基准级别可能不同的情况，第二节点在第一Announce报文中携带的目标参数对应的级别可以低于所有类型的节点的基准级别的最小值。例如，针对目标参数clockclass，在1588v2、G.8275.1和G.8275.2协议标准中，该clockclass为基准级别时，该clockclass的值为6。在G8265.1协议标准中，该clockclass为基准级别时，该clockclass的值为84。
示例性地，以1588v2协议标准中，clockclass为基准级别时，该clockclass的值为6为例。如果第二节点的时间同步不确定，则clockclass的值可以设为187或248，clockclass的值为187或248对应的级别低于clockclass的值为6对应的级别，也低于clockclass的值为84对应的级别。该种情况下，如果时间同步的其他节点发送的第一Announce报文中的目标参数的级别高于第二节点发送的第一Announce报文中的目标参数的级别，则第一节点不选取接收该第一Announce报文的端口对应的时钟源。
另外，该第一Announce报文包括的主时钟标识还可以为该第二节点的默认数据集(default dataset)中的时钟标识(clockIdentity)。
关于第二节点根据第二Announce报文生成第一Announce报文的方式，在示例性实施例中，包括但不限于如下方式：
方式一：对第二Announce报文中的目标参数的级别进行修改，得到第一Announce报文。在修改时，将该第二Announce报文中的目标参数修改为级别低于该目标参数的级别的参数。如，第二Announce报文中的clockclass为6，将clockclass的值修改为大于6的值，如248。
该种方式下，第二节点作为中间节点，接收上游节点发送的第二Announce报文，如果上游节点的时间同步，则第二Announce报文中的目标参数的级别为上游节点的基准级别。不同节点的基准级别可能不同，第二节点在时间同步不确定的情况下，对第二Announce报文中的目标参数的级别进行修改，例如将第二Announce报文中的目标参数降级，从而得到携带有降级后的目标参数的第一Announce报文。其中，如果各节点的基准级别相同，则第一Announce报文中携带的降级后的目标参数对应的级别低于第二节点的基准级别。如果各节点的基准级别不同，则第一Announce报文中携带的降级后的目标参数对应的级别低于所有类型的节点的基准级别的最小值。
需要说明的是，由于第二Announce报文和第一Announce报文所对应的源端口和目的端口不同，在对第二Announce报文进行修改，得到第一Announce报文的过程中，除了对目标参数 降级，还包括修改第二Announce报文中的源端口和目的端口的地址。
方式二：根据第二Announce报文中的信息，生成第一Announce报文。在生成第一Announce报文时，将级别低于该第二Announce报文中的目标参数的参数填到该第一Announce报文的相应字段中。如，第二Announce报文中的clockclass为6，将大于6的值(如248)填到第一Announce报文的clockclass字段。
该方式二中，第二节点作为中间节点，第二节点接收到第二Announce报文后，对第二Announce报文进行解析，得到第二Announce报文中的信息。之后，第二节点在时间同步不确定的情况下，基于第二节点自身的情况及第二Announce报文中的信息，生成第一Announce报文。也就是说，该方式二与方式一不同的是，方式二并不在第二Announce报文基础上修改，而是重新生成一个新的Announce报文，即第一Announce报文。
在实施方式B中，该第一Announce报文中携带的目标参数为所述第二节点的默认时钟参数，如该第二节点的默认数据集(default dataset)中的参数。该默认时钟参数为预设参数。
需要说明的是，由于默认时钟参数中的值通常是比较劣的值，该第二节点的默认时钟参数对应的级别通常是低于实施方式A中的基准级别的。
另外，该第一Announce报文包括的主时钟标识还可以为该第二节点的默认数据集(default dataset)中的时钟标识(clockIdentity)。
第二节点根据该第二Announce报文生成第一Announce报文的方式参见上述方式一和方式二，不再赘述。
需要说明的是，以上方式一和方式二均是以第二节点为中间节点为例，针对第二节点是网络中第一个发起Announce报文的节点(即源节点)，而非中间节点的情况，第二节点在时间同步不确定的情况下，可直接基于自身的情况生成第一Announce报文。
802，第二节点将第一Announce报文发送至第一节点，第一Announce报文中携带的参数用于选取时钟源。
第二节点将第一Announce报文发送至第一节点后，第一节点解析第一Announce报文，如果各节点的基准级别相同，第一Announce报文中携带的降级后的目标参数对应的级别低于第二节点的基准级别。如果各节点的基准级别不同，则第一Announce报文中携带的降级后的目标参数对应的级别低于所有类型的节点的基准级别的最小值，因此，第一节点在选取时钟源时，不会选取接收该第一Announce报文的端口对应的时钟源。
本申请实施例提供的方法，当上游的第二节点的时间同步不确定时，通过在第一Announce报文中携带级别低于基准级别的目标参数，使得下游的第一节点在选取时钟源时，由于第一Announce报文中的目标参数的级别低，而不选择接收第一Announce报文的端口对应的时钟源，以此避免因上游节点时间同步不确定而使得下游节点的时间发生跳变，进而影响整网的时间跳变及业务的正常进行。
需要说明的是，上述图8所示实施例中，仅以第二节点时间同步未确定的情况下，第一节点不选取接收该第一Announce报文的端口对应的时钟源，从而避免时间跳变为例进行了说明。如果后续第二节点的时间同步了，则向第一节点发送的Announce报文里的目标参数的级别可以为第二节点的基准级别，从而使得第一节点将接收该第一Announce报文的端口对应的时钟源作为选择对象进行时钟源的选取。
本申请实施例提供了一种用于实现时钟源选取的装置，该装置应用于第一节点，参见图9，该装置包括：
接收模块901，用于通过第一节点上的第一端口接收第二节点发送的第一报文；
选取模块902，用于当第一报文携带有第一标记时，第一节点在选取时钟源时，不选取第一端口对应的时钟源，第一标记用于指示第二节点的时间同步不确定。
在示例性实施例中，选取模块902，用于在选取时钟源时，不使用通过第一端口接收到的时钟源数据选取时钟源。
在示例性实施例中，选取模块902，用于根据第一标记将第一端口对应的时钟源数据集设为空集；根据第一节点的各端口对应的时钟源数据集选取时钟源，或者，根据第一节点的各端口对应的时钟源数据集中的非空时钟源数据集选取时钟源。
在示例性实施例中，选取模块902，用于基于第一标记将第一端口的信号异常属性的值设为第一值，用于指示第一端口发生信号异常；基于信号异常属性的第一值，将第一端口对应的时钟源数据集设置为空集。
在示例性实施例中，第一端口的信号异常属性为端口信号失效属性portDS.SF，portDS.SF的第一值为真TRUE。
在示例性实施例中，选取模块902，用于基于第一标记确定第一端口发生包定时信号失效PTSF事件；基于PTSF事件，将第一端口的portDS.SF的值设为第一值。
在示例性实施例中，PTSF事件为包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件或扩展的PTSF事件。
在示例性实施例中，第一报文为声明Announce报文。
在示例性实施例中，Announce报文中的同步未确定标记synchronizationUncertain用于携带第一标记，当synchronizationUncertain的值为第三值时，用于指示第二节点的时间同步不确定。
在示例性实施例中，synchronizationUncertain的第三值为TRUE。
本申请实施例提供了一种用于实现时钟源选取的装置，该装置应用于第二节点，参见图10，该装置包括：
生成模块1001，用于生成第一声明Announce报文。
发送模块1002，用于将第一Announce报文发送至第一节点，第一Announce报文中携带的参数用于选取时钟源。
生成模块1001的具体实现方式包括如下实施方式X和实施方式Y，分别对应如图8所示的方法实施例中的实施方式A和实施方式B。
实施方式X：当第二节点的时间同步不确定时，生成模块1001生成的第一Announce报文中携带的目标参数对应的级别低于基准级别，基准级别为第二节点在时间同步时目标参数对应的级别。
在示例性实施例中，目标参数为时钟等级clockclass、时钟精度clockAccuracy，偏移量刻度的对数方差offsetScaledLogVariance参数中的一个或多个。
当该第二节点为中间节点时，在示例性实施例中，生成模块1001，用于接收上游节点发送的第二Announce报文，根据该第二Announce报文生成该第一Announce报文。在该实现方式中，该第一Announce报文携带的目标参数劣于该第二Announce报文中携带的目标参数(即将该第二Announce报文中携带的目标参数的级别作为该基准级别)。在生成该第一Announce报文时，可以对第二Announce报文中的目标参数的级别进行修改，得到第一Announce报文，或者，根据第二Announce报文中的信息，生成第一声明Announce报文。
当该第二节点为时间服务器时，该第一Announce报文携带的目标参数劣于该时间服务器 处于锁定模式时的目标参数(即将该时间服务器处于锁定模式时的目标参数的级别作为该基准级别)。
实施方式Y：当第二节点的时间同步不确定时，生成模块1001生成的该第一Announce报文中携带的目标参数为所述第二节点的默认时钟参数，如该第二节点的默认数据集(default dataset)中的参数。
应理解的是，上述图9和图10提供的装置在实现其功能时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置与方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
本申请实施例提供了一种用于实现时钟源选取的***，该***包括：第一节点和第二节点；
第二节点，用于向第一节点的第一端口发送第一报文；
第一节点，用于通过第一节点上的第一端口接收第二节点发送的第一报文；当第一报文携带有第一标记时，第一节点在选取时钟源时，不选取第一端口对应的时钟源，第一标记用于指示第二节点的时间同步不确定。
在示例性实施例中，第一节点，用于在选取时钟源时，不使用通过第一端口接收到的时钟源数据选取时钟源。
在示例性实施例中，第一节点，用于根据第一标记将第一端口对应的时钟源数据集设为空集；根据第一节点的各端口对应的时钟源数据集选取时钟源，或者，根据第一节点的各端口对应的时钟源数据集中的非空时钟源数据集选取时钟源。
在示例性实施例中，第一节点，用于基于第一标记将第一端口的信号异常属性的值设为第一值，用于指示第一端口发生信号异常；基于信号异常属性的第一值，将第一端口对应的时钟源数据集设置为空集。
在示例性实施例中，第一端口的信号异常属性为端口信号失效属性portDS.SF，portDS.SF的第一值为真TRUE。
在示例性实施例中，第一节点，用于基于第一标记确定第一端口发生包定时信号失效PTSF事件；基于PTSF事件，将第一端口的portDS.SF的值设为第一值。
在示例性实施例中，PTSF事件为包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件或扩展的PTSF事件。
在示例性实施例中，第一报文为声明Announce报文。
在示例性实施例中，Announce报文中的同步未确定标记synchronizationUncertain用于携带第一标记，当synchronizationUncertain的值为第三值时，用于指示第二节点的时间同步不确定。
在示例性实施例中，synchronizationUncertain的第三值为TRUE。
应理解的是，上述***与图2方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
本申请实施例提供了一种用于实现时钟源选取的***，该***包括：第一节点和第二节点；
第二节点，用于生成第一声明Announce报文，并向第一节点发送该第一Announce报文；
第一节点，用于接收第二节点发送的第一Announce报文，第一Announce报文中携带的参数用于选取时钟源。
如图8所示的方法实施例中的实施方式A所述，当第二节点的时间同步不确定时，该第一Announce报文中携带的目标参数对应的级别低于基准级别，基准级别为第二节点在时间同步时目标参数对应的级别。
在示例性实施例中，目标参数为时钟等级clockclass、时钟精度clockAccuracy，偏移量刻度的对数方差offsetScaledLogVariance参数中的一个或多个。
在示例性实施例中，第二节点，用于接收上游节点发送的第二Announce报文，根据该第二Announce报文生成该第一Announce报文。在该实现方式中，该第一Announce报文携带的目标参数劣于该第二Announce报文中携带的目标参数(即将该第二Announce报文中携带的目标参数的级别作为该基准级别)。在生成该第一Announce报文时，可以对第二Announce报文中的目标参数的级别进行修改，得到第一Announce报文，或者，根据第二Announce报文中的信息，生成第一声明Announce报文。
当该第二节点为时间服务器时，该第一Announce报文携带的目标参数劣于该时间服务器处于锁定模式时的目标参数(即将该时间服务器处于锁定模式时的目标参数的级别作为该基准级别)。
如图8所示的方法实施例中的实施方式B所述，当第二节点的时间同步不确定时，该第一Announce报文中携带的目标参数为所述第二节点的默认时钟参数，如该第二节点的默认数据集(default dataset)中的参数。
应理解的是，上述***与图8方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
参见图11，本申请实施例还提供一种用于实现时钟源选取的设备1100，图11所示的用于实现时钟源选取的设备1100用于执行上述用于实现时钟源选取的方法所涉及的操作。该用于实现时钟源选取的设备1100包括：处理器1102及端口1103，处理器1102及端口1103之间通过总线1104连接。
端口1103用于与网络中的其他设备进行通信，该端口1103可以通过无线或有线的方式实现，处理器1102用于实现上述任一所述的用于实现时钟源选取的方法。
在示例性实施例中，该用于实现时钟源选取的设备1100还包括存储器1101，存储器1101中存储有至少一条指令，至少一条指令由处理器1102加载并执行，存储器1101、处理器1102及端口1103之间通过总线1104连接。
应理解的是，图11仅仅示出了用于实现时钟源选取的设备1100的简化设计。在实际应用中，选取时钟源的设备可以包含任意数量的接口，处理器或者存储器。此外，上述处理器可以是中央处理器(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processing，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field－programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者是任何常规的处理器等。值得说明的是，处理器可以是支持进阶精简指令集机器(advanced RISC machines，ARM)架构的处理器。
进一步地，在一种可选的实施例中，上述存储器可以包括只读存储器和随机存取存储器， 并向处理器提供指令和数据。存储器还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。
该存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者，其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用。例如，静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic random access memory，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data date SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
还提供了一种计算机可读存储介质，存储介质中存储有至少一条指令，指令由处理器加载并执行以实现如上任一所述的选取时钟源的方法。
本申请提供了一种计算机程序，当计算机程序被计算机执行时，可以使得处理器或计算机执行上述方法实施例中对应的各个操作和/或流程。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk)等。
以上所述仅为本申请的实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (49)

  1. 一种用于实现时钟源选取的方法，其特征在于，所述方法包括：
    第一节点通过所述第一节点上的第一端口接收第二节点发送的第一报文；
    当所述第一报文携带有第一标记时，所述第一节点在选取时钟源时，不选取所述第一端口对应的时钟源，所述第一标记用于指示所述第二节点的时间同步不确定。
  2. 根据权利要求1所述的方法，其特征在于，所述第一节点在选取时钟源时，不选取所述第一端口对应的时钟源，包括：所述第一节点在选取时钟源时，不使用通过所述第一端口接收到的时钟源数据选取时钟源。
  3. 根据权利要求2所述的方法，其特征在于，所述第一节点在选取时钟源时，不使用通过所述第一端口接收的时钟源数据选取时钟源，包括：
    根据所述第一标记将所述第一端口对应的时钟源数据集设为空集；
    根据所述第一节点的各端口对应的时钟源数据集选取时钟源，或者，根据所述第一节点的各端口对应的时钟源数据集中的非空时钟源数据集选取时钟源。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述第一标记将所述第一端口对应的时钟源数据集设为空集，包括：
    基于所述第一标记将所述第一端口的信号异常属性的值设为第一值，用于指示所述第一端口发生信号异常；
    基于所述信号异常属性的第一值，将所述第一端口对应的时钟源数据集设置为空集。
  5. 根据权利要求4所述的方法，其特征在于，所述第一端口的信号异常属性为端口信号失效属性portDS.SF，所述portDS.SF的第一值为真TRUE。
  6. 根据权利要求5所述的方法，其特征在于，所述基于所述第一标记将所述第一端口的信号异常属性的值设为第一值，包括：
    基于所述第一标记确定所述第一端口发生包定时信号失效PTSF事件；
    基于所述PTSF事件，将所述第一端口的portDS.SF的值设为第一值。
  7. 根据权利要求6所述的方法，其特征在于，所述PTSF事件为包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件或扩展的PTSF事件。
  8. 根据权利要求1-7任一所述的方法，其特征在于，所述第一报文为声明Announce报文。
  9. 根据权利要求8所述的方法，其特征在于，所述Announce报文中的同步未确定标记synchronizationUncertain用于携带所述第一标记，当所述synchronizationUncertain的值为TRUE时，用于指示所述第二节点的时间同步不确定。
  10. 一种用于实现时钟源选取的方法，其特征在于，所述方法包括：
    第二节点生成第一声明Announce报文，当所述第二节点的时间同步不确定时，所述第一Announce报文中携带的目标参数劣于接收自所述第二节点的上游节点的第二Announce报文中携带的目标参数；
    所述第二节点向第一节点发送所述第一Announce报文，所述第一Announce报文中携带的参数用于所述第一节点选取时钟源。
  11. 根据权利要求10所述的方法，其特征在于，所述目标参数包括第一目标参数和/或第二目标参数，所述第一目标参数用于表征主时钟优先级，所述第二目标参数用于表征主时钟质量。
  12. 根据权利要求11所述的方法，其特征在于，所述第二目标参数包括用于表征时钟的国际原子时间TAI可追溯性的参数、用于表征时钟精度的参数、以及用于表征时钟稳定性的参数中的一个或多个。
  13. 根据权利要求12所述的方法，其特征在于，所述用于表征时钟的国际原子时间TAI可追溯性的参数包括时钟等级clockclass，所述用于表征时钟精度的参数包括时钟精度clockAccuracy，所述用于表征时钟稳定性的参数包括偏移量刻度的对数方差offsetScaledLogVariance。
  14. 根据权利要求10-13任一所述的方法，其特征在于，所述第一Announce报文还包括主时钟标识，所述第一Announce报文包括的主时钟标识不同于所述第二Announce报文包括的主时钟标识。
  15. 根据权利要求14所述的方法，其特征在于，所述第一Announce报文包括的主时钟标识为所述第二节点的默认数据集default dataset中的时钟标识clockIdentity。
  16. 根据权利要求10-15任一所述的方法，其特征在于，所述第二节点的时间同步不确定包括：
    所述第二节点的用于接收所述第二Announce报文的端口处于未校准UNCALIBRATED状态；
    或者，
    所述第二节点的时间与时钟源信号的时间的时间差大于阈值。
  17. 一种用于实现时钟源选取的方法，其特征在于，所述方法包括：
    时间服务器生成第一声明Announce报文，当所述时间服务器的时间同步不确定时，所述第一Announce报文中携带的目标参数劣于所述时间服务器处于锁定模式时的目标参数；
    所述时间服务器向第一节点发送所述第一Announce报文，所述第一Announce报文中携带的参数用于所述第一节点选取时钟源。
  18. 根据权利要求17所述的方法，其特征在于，所述目标参数包括第一目标参数和/或第二目标参数，所述第一目标参数用于表征主时钟优先级，所述第二目标参数用于表征主时钟 质量。
  19. 根据权利要求18所述的方法，其特征在于，所述第二目标参数包括用于表征时钟的国际原子时间TAI可追溯性的参数、用于表征时钟精度的参数、以及用于表征时钟稳定性的参数中的一个或多个。
  20. 根据权利要求19所述的方法，其特征在于，所述用于表征时钟的国际原子时间TAI可追溯性的参数包括时钟等级clockclass，所述用于表征时钟精度的参数包括时钟精度clockAccuracy，所述用于表征时钟稳定性的参数包括偏移量刻度的对数方差offsetScaledLogVariance。
  21. 根据权利要求17-20任一所述的方法，其特征在于，所述时间服务器的时间同步不确定包括，所述时间服务器的时间与接收的卫星信号的时间差大于阈值。
  22. 一种用于实现时钟源选取的方法，其特征在于，所述方法包括：
    第二节点生成第一声明Announce报文，当所述第二节点的时间同步不确定时，所述第一Announce报文中携带的目标参数为所述第二节点的默认时钟参数；
    所述第二节点向第一节点发送所述第一Announce报文，所述第一Announce报文中携带的参数用于所述第一节点选取时钟源。
  23. 根据权利要求22所述的方法，其特征在于，所述目标参数包括第一目标参数和/或第二目标参数，所述第一目标参数用于表征主时钟优先级，所述第二目标参数用于表征主时钟质量。
  24. 根据权利要求23所述的方法，其特征在于，所述第二目标参数包括用于表征时钟的国际原子时间TAI可追溯性的参数、用于表征时钟精度的参数、以及用于表征时钟稳定性的参数中的一个或多个。
  25. 根据权利要求24所述的方法，其特征在于，所述用于表征时钟的国际原子时间TAI可追溯性的参数包括时钟等级clockclass，所述用于表征时钟精度的参数包括时钟精度clockAccuracy，所述用于表征时钟稳定性的参数包括偏移量刻度的对数方差offsetScaledLogVariance。
  26. 根据权利要求22-25所述的方法，其特征在于，所述第二节点生成第一Announce报文之前还包括：所述第二节点接收上游节点发送的第二Announce报文；
    所述第二节点生成第一Announce报文包括：根据所述第二Announce报文生成所述第一Announce报文。
  27. 根据权利要求22-26所述的方法，其特征在于，所述第二节点的默认时钟参数为所述第二节点的默认数据集default dataset中的参数。
  28. 根据权利要求22-27所述的方法，其特征在于，所述第二节点的时间同步不确定包括：
    所述第二节点的用于接收所述第二Announce报文的端口处于未校准UNCALIBRATED状态；或者，
    所述第二节点的时间与时钟源信号的时间的时间差大于阈值。
  29. 一种用于实现时钟源选取的装置，其特征在于，所述装置应用于第一节点，所述装置包括：
    接收模块，用于通过所述第一节点上的第一端口接收第二节点发送的第一报文；
    选取模块，用于当所述第一报文携带有第一标记时，所述第一节点在选取时钟源时，不选取所述第一端口对应的时钟源，所述第一标记用于指示所述第二节点的时间同步不确定。
  30. 根据权利要求29所述的装置，其特征在于，所述选取模块，用于在选取时钟源时，不使用通过所述第一端口接收到的时钟源数据选取时钟源。
  31. 根据权利要求30所述的装置，其特征在于，所述选取模块，用于根据所述第一标记将所述第一端口对应的时钟源数据集设为空集；根据所述第一节点的各端口对应的时钟源数据集选取时钟源，或者，根据所述第一节点的各端口对应的时钟源数据集中的非空时钟源数据集选取时钟源。
  32. 根据权利要求31所述的装置，其特征在于，所述选取模块，用于基于所述第一标记将所述第一端口的信号异常属性的值设为第一值，用于指示所述第一端口发生信号异常；基于所述信号异常属性的第一值，将所述第一端口对应的时钟源数据集设置为空集。
  33. 根据权利要求32所述的装置，其特征在于，所述第一端口的信号异常属性为端口信号失效属性portDS.SF，所述portDS.SF的第一值为真TRUE。
  34. 根据权利要求33所述的装置，其特征在于，所述选取模块，用于基于所述第一标记确定所述第一端口发生包定时信号失效PTSF事件；基于所述PTSF事件，将所述第一端口的portDS.SF的值设为第一值。
  35. 根据权利要求34所述的装置，其特征在于，所述PTSF事件为包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件或扩展的PTSF事件。
  36. 根据权利要求29-35任一所述的装置，其特征在于，所述第一报文为声明Announce报文。
  37. 根据权利要求36所述的装置，其特征在于，所述Announce报文中的同步未确定标记synchronizationUncertain用于携带所述第一标记，当所述synchronizationUncertain的值为TURE时，用于指示所述第二节点的时间同步不确定。
  38. 一种用于实现时钟源选取的装置，其特征在于，所述装置包括：生成模块和发送模 块；
    所述生成模块，用于执行根据权利要求10-28任一所述的方法中生成第一Announce报文的操作；
    所述发送模块，用于向第一节点发送所述第一Announce报文，所述第一Announce报文中携带的参数用于所述第一节点选取时钟源。
  39. 一种用于实现时钟源选取的***，其特征在于，所述***包括：第一节点和第二节点；
    所述第二节点，用于向所述第一节点的第一端口发送第一报文；
    所述第一节点，用于通过所述第一节点上的第一端口接收所述第二节点发送的第一报文；当所述第一报文携带有第一标记时，所述第一节点在选取时钟源时，不选取所述第一端口对应的时钟源，所述第一标记用于指示所述第二节点的时间同步不确定。
  40. 根据权利要求39所述的***，其特征在于，所述第一节点，用于在选取时钟源时，不使用通过所述第一端口接收到的时钟源数据选取时钟源。
  41. 根据权利要求40所述的***，其特征在于，所述第一节点，用于根据所述第一标记将所述第一端口对应的时钟源数据集设为空集；根据所述第一节点的各端口对应的时钟源数据集选取时钟源，或者，根据所述第一节点的各端口对应的时钟源数据集中的非空时钟源数据集选取时钟源。
  42. 根据权利要求41所述的***，其特征在于，所述第一节点，用于基于所述第一标记将所述第一端口的信号异常属性的值设为第一值，用于指示所述第一端口发生信号异常；基于所述信号异常属性的第一值，将所述第一端口对应的时钟源数据集设置为空集。
  43. 根据权利要求42所述的***，其特征在于，所述第一端口的信号异常属性为端口信号失效属性portDS.SF，所述portDS.SF的第一值为真TRUE。
  44. 根据权利要求43所述的***，其特征在于，所述第一节点，用于基于所述第一标记确定所述第一端口发生包定时信号失效PTSF事件；基于所述PTSF事件，将所述第一端口的portDS.SF的值设为第一值。
  45. 根据权利要求44所述的***，其特征在于，所述PTSF事件为包定时信号失效-丢失同步PTSF-lossSync事件、包定时信号失效-不可用PTSF-unusable事件或扩展的PTSF事件。
  46. 根据权利要求39-45任一所述的***，其特征在于，所述第一报文为声明Announce报文。
  47. 一种用于实现时钟源选取的***，其特征在于，所述***包括：第一节点和第二节点；
    所述第二节点，用于实现如权利要求10-28中任一所述的方法；
    所述第一节点，用于接收所述第二节点发送的第一Announce报文，根据所述第一Announce报文中携带的参数选取时钟源。
  48. 一种用于实现时钟源选取的设备，其特征在于，所述设备包括：端口及处理器，所述端口用于与其他节点通信，所述处理器用于实现权利要求1-28中任一所述的用于实现时钟源选取的方法。
  49. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有至少一条指令，所述指令由处理器加载并执行以实现如权利要求1-28中任一所述的用于实现时钟源选取的方法。
PCT/CN2020/094411 2019-09-06 2020-06-04 用于实现时钟源选取的方法、装置、***及存储介质 WO2021042789A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP20860856.2A EP4027585A4 (en) 2019-09-06 2020-06-04 METHOD OF ACHIEVING CLOCK SOURCE SELECTION, DEVICE, SYSTEM AND STORAGE MEDIA
KR1020227008937A KR102600909B1 (ko) 2019-09-06 2020-06-04 클록 소스를 선택하기 위한 방법, 장치, 시스템, 및 저장 매체
JP2022514714A JP7401656B2 (ja) 2019-09-06 2020-06-04 クロック・ソースを選択するための方法、装置、及びシステム、並びに記憶媒体
CN202080003884.XA CN112771817A (zh) 2019-09-06 2020-06-04 用于实现时钟源选取的方法、装置、***及存储介质
US17/687,056 US20220190945A1 (en) 2019-09-06 2022-03-04 Method, Apparatus, and System for Selecting Clock Source, and Storage Medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910844122.1 2019-09-06
CN201910844122.1A CN112367137B (zh) 2019-09-06 2019-09-06 用于实现时钟源选取的方法、装置、***、设备及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/687,056 Continuation US20220190945A1 (en) 2019-09-06 2022-03-04 Method, Apparatus, and System for Selecting Clock Source, and Storage Medium

Publications (1)

Publication Number Publication Date
WO2021042789A1 true WO2021042789A1 (zh) 2021-03-11

Family

ID=74516467

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094411 WO2021042789A1 (zh) 2019-09-06 2020-06-04 用于实现时钟源选取的方法、装置、***及存储介质

Country Status (6)

Country Link
US (1) US20220190945A1 (zh)
EP (1) EP4027585A4 (zh)
JP (1) JP7401656B2 (zh)
KR (1) KR102600909B1 (zh)
CN (3) CN112367137B (zh)
WO (1) WO2021042789A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114650113A (zh) * 2020-12-18 2022-06-21 华为技术有限公司 选择时钟源的方法及装置
CN114980181A (zh) * 2021-02-27 2022-08-30 华为技术有限公司 一种时钟同步方法、装置及承载网设备
CN114173367B (zh) * 2021-12-23 2023-11-03 烽火通信科技股份有限公司 时间同步路径保护方法、装置及可读存储介质
CN116489758A (zh) * 2022-01-14 2023-07-25 华为技术有限公司 一种授时方法、通信装置及通信***
CN118118935A (zh) * 2022-11-30 2024-05-31 华为技术有限公司 一种时钟质量等级设置方法、设备及***

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207606A (zh) * 2006-12-18 2008-06-25 华为技术有限公司 主时钟选举的方法和装置
US20110236031A1 (en) * 2010-03-29 2011-09-29 Fujitsu Limited Optical interface device, and abnormality monitoring method for input frequency deviation
CN102223197A (zh) * 2011-06-14 2011-10-19 中兴通讯股份有限公司 一种时钟同步方法及设备
CN102957488A (zh) * 2011-08-18 2013-03-06 中兴通讯股份有限公司 一种时间同步选源方法及装置
CN103428081A (zh) * 2012-05-14 2013-12-04 中兴通讯股份有限公司 一种分组网络同步方法、装置及***
CN103686982A (zh) * 2012-09-17 2014-03-26 ***通信集团公司 一种基于时钟信息的时间同步方法以及节点设备
CN104426645A (zh) * 2013-09-02 2015-03-18 华为技术有限公司 确定以太时钟源的方法和装置
CN105323086A (zh) * 2014-07-11 2016-02-10 中兴通讯股份有限公司 指示同步时间源选择的方法、装置及***

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102123024B (zh) * 2011-03-17 2015-06-03 中兴通讯股份有限公司 一种时钟源设备切换选择方法、***及装置
CN103001720B (zh) 2012-11-12 2017-05-10 中兴通讯股份有限公司 时间同步方法和装置
CN106899370A (zh) * 2015-12-18 2017-06-27 中兴通讯股份有限公司 一种时钟链路切换方法、装置及基站
CN106921509B (zh) * 2015-12-28 2020-07-10 中兴通讯股份有限公司 一种全网时钟同步管理的方法及装置
WO2017130034A1 (en) * 2016-01-27 2017-08-03 Telefonaktiebolaget Lm Ericsson (Publ) A method of timing loop prevention for the precision time protocol (ptp) with g.8275.1 profile
JP2017216563A (ja) 2016-05-31 2017-12-07 日本電気株式会社 中継装置、制御方法、及び、通信システム
GB2557312B (en) * 2016-12-06 2021-07-21 Canon Kk Method, device, and computer program for improving synchronization of clocks in devices linked according to a daisy-chain topology
CN107026702A (zh) * 2017-04-20 2017-08-08 中国南方电网有限责任公司电网技术研究中心 高精度守时方法和装置

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207606A (zh) * 2006-12-18 2008-06-25 华为技术有限公司 主时钟选举的方法和装置
US20110236031A1 (en) * 2010-03-29 2011-09-29 Fujitsu Limited Optical interface device, and abnormality monitoring method for input frequency deviation
CN102223197A (zh) * 2011-06-14 2011-10-19 中兴通讯股份有限公司 一种时钟同步方法及设备
CN102957488A (zh) * 2011-08-18 2013-03-06 中兴通讯股份有限公司 一种时间同步选源方法及装置
CN103428081A (zh) * 2012-05-14 2013-12-04 中兴通讯股份有限公司 一种分组网络同步方法、装置及***
CN103686982A (zh) * 2012-09-17 2014-03-26 ***通信集团公司 一种基于时钟信息的时间同步方法以及节点设备
CN104426645A (zh) * 2013-09-02 2015-03-18 华为技术有限公司 确定以太时钟源的方法和装置
CN105323086A (zh) * 2014-07-11 2016-02-10 中兴通讯股份有限公司 指示同步时间源选择的方法、装置及***

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4027585A4 *

Also Published As

Publication number Publication date
CN112367137B (zh) 2022-02-11
CN112367137A (zh) 2021-02-12
JP7401656B2 (ja) 2023-12-19
CN112771817A (zh) 2021-05-07
KR102600909B1 (ko) 2023-11-09
US20220190945A1 (en) 2022-06-16
CN114448548A (zh) 2022-05-06
EP4027585A4 (en) 2022-10-26
EP4027585A1 (en) 2022-07-13
KR20220050926A (ko) 2022-04-25
JP2022547891A (ja) 2022-11-16

Similar Documents

Publication Publication Date Title
WO2021042789A1 (zh) 用于实现时钟源选取的方法、装置、***及存储介质
US11283535B2 (en) Method of remotely monitoring the timing performance of a PTP slave
US11444747B2 (en) Measure and improve clock synchronization using combination of transparent and boundary clocks
US9219562B2 (en) System and method to dynamically redistribute timing and synchronization in a packet switched network
US20040109474A1 (en) Radio access network system, radio communication method, synchronous server and node
JP2018037885A (ja) 時刻同期システム
RU2556082C1 (ru) Устройство синхронизации и способ синхронизации
CN111385050B (zh) 时钟同步方法、装置和存储介质
US9955447B2 (en) Clock synchronization method, mobile network system, network controller and network switch
CN111385051B (zh) 时钟同步方法、装置和存储介质
WO2017032113A1 (zh) 一种时间同步偏差检测方法和装置
US20180262287A1 (en) Time synchronization packet processing method and device
WO2022151993A1 (zh) 检测时间同步性能的方法、装置及***
CN116800366A (zh) 一种时钟同步方法、设备及存储介质
JP2024518525A (ja) パケット伝送方法および装置、デバイス、ならびに記憶媒体
CN112929115A (zh) 时间校准精度的检测方法、设备、***及存储介质
US20220337384A1 (en) Clock Port Attribute Recovery Method, Device, and System
CN117278190B (zh) 时间同步单元、方法、芯片架构、网络设备及介质
WO2023115403A1 (en) Methods and network devices for ptp clock synchronization
US20230179313A1 (en) Method and time synchronization (ts) node for enabling extended holdover time
JP2018157462A (ja) ログ保存方法
WO2020155738A1 (en) Clock distribution method and apparatus in network
CN117241365A (zh) 时间偏差的监控方法、装置及***

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20860856

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022514714

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20227008937

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020860856

Country of ref document: EP

Effective date: 20220406