WO2015172476A1 - 同步方法、控制器、同步节点及同步网络、存储介质 - Google Patents

同步方法、控制器、同步节点及同步网络、存储介质 Download PDF

Info

Publication number
WO2015172476A1
WO2015172476A1 PCT/CN2014/086453 CN2014086453W WO2015172476A1 WO 2015172476 A1 WO2015172476 A1 WO 2015172476A1 CN 2014086453 W CN2014086453 W CN 2014086453W WO 2015172476 A1 WO2015172476 A1 WO 2015172476A1
Authority
WO
WIPO (PCT)
Prior art keywords
synchronization
node
controller
rule
unit
Prior art date
Application number
PCT/CN2014/086453
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 US15/311,192 priority Critical patent/US10181919B2/en
Priority to EP14891855.0A priority patent/EP3145111A4/en
Publication of WO2015172476A1 publication Critical patent/WO2015172476A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/02Details
    • H04J3/06Synchronising arrangements
    • H04J3/0635Clock or time synchronisation in a network
    • H04J3/0638Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0641Change of the master or reference, e.g. take-over or failure of the master
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/02Details
    • H04J3/06Synchronising arrangements
    • H04J3/0635Clock or time synchronisation in a network
    • H04J3/0679Clock or time synchronisation in a network by determining clock distribution path in a network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • H04L41/122Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/02Details
    • H04J3/12Arrangements providing for calling or supervisory signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/02Details
    • H04J3/14Monitoring arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies

Definitions

  • the present invention relates to the field of network communications, and in particular, to a synchronization method, a controller, a synchronization node, a synchronization network, and a storage medium, which are applicable to a Software Defined Network (SDN).
  • SDN Software Defined Network
  • the existing communication network packet synchronization network can be divided into a frequency synchronization network and a time synchronization network.
  • the frequency synchronization network uses a Synchronous Ethernet (SyncE) network or a Precision Time Protocol (PTP) to extract clock information from a physical code stream or a packet, and uses a synchronization status message (SSM, Synchronization Status Message). ) Perform frequency source selection and path switching.
  • the time synchronization network uses PTP to extract timestamp information from the timing message, calculate the time offset and perform time calibration.
  • the time synchronization network uses PTP to select the time source and perform path switching.
  • each device in the PTN can act as a network node (NE) once the reference source and/or synchronization link in the PTN fails.
  • NE network node
  • the existing PTN lacks an effective switching mechanism, so that the real-time performance of the synchronous link switching cannot be guaranteed.
  • the embodiment of the present invention provides a synchronization method, a controller, a synchronization node, a synchronization network, and a storage medium, which can quickly switch a synchronization link to meet a synchronization chain.
  • the real-time nature of the road switching thereby effectively improving the synchronization performance of the entire network.
  • an embodiment of the present invention provides a synchronization method, where the method includes:
  • the controller determines the synchronization link topology information of the synchronization network according to the physical link topology information of the synchronization network and the synchronization information of the synchronization node in the synchronization network;
  • the controller generates a synchronization rule of the synchronization node according to the synchronization link topology information
  • the controller sends a synchronization rule and/or a request message to the synchronization node in the synchronization network according to the synchronization link topology information.
  • an embodiment of the present invention further provides a synchronization method, where the method includes:
  • the synchronization node receives a synchronization rule and/or a request message sent by the controller, where the request message carries the synchronization rule;
  • the synchronization node locks the best valid reference source according to the synchronization rule, and outputs reference source information to other ports.
  • an embodiment of the present invention provides a controller, where the controller includes a first determining unit, a generating unit, and a first sending unit, where:
  • the first determining unit is configured to determine synchronization link topology information of the synchronization network according to physical link topology information of the synchronization network and synchronization information of the synchronization node in the synchronization network;
  • the generating unit is configured to generate a synchronization rule of the synchronization node according to the synchronization link topology information
  • the first sending unit is configured to send a synchronization rule and/or a request message to the synchronization node in the synchronization network according to the synchronization link topology information.
  • an embodiment of the present invention provides a synchronization node, where the synchronization node includes a second receiving unit and a locking unit, where:
  • the second receiving unit is configured to receive a synchronization rule and/or a request message sent by the controller, where the request message carries the synchronization rule;
  • the locking unit is configured to lock an optimal valid reference source according to the synchronization rule, and output reference source information to other ports.
  • an embodiment of the present invention provides a synchronization method, where the method includes:
  • the controller determines the synchronization link topology information according to the physical link topology information of the synchronization network and the synchronization information of the synchronization node in the synchronization network;
  • the controller generates a synchronization rule of the synchronization node according to the synchronization link topology information
  • the controller sends a synchronization rule and/or a request message to the synchronization node in the synchronization network according to the synchronization link topology information, where the request message carries the synchronization rule;
  • the synchronization node receives the synchronization rule and/or the request message
  • the synchronization node locks the best valid reference source according to the synchronization rule, and outputs reference source information to other ports.
  • an embodiment of the present invention provides a synchronization network, where the synchronization network includes a controller and a synchronization node, where the controller includes a first determining unit, a generating unit, and a first sending unit, where the synchronization node includes a second receiving unit and a locking unit, wherein:
  • the first determining unit is configured to determine synchronization link topology information according to physical link topology information of the synchronization network and synchronization information of the synchronization node in the synchronization network;
  • the generating unit is configured to generate a synchronization rule of the synchronization node according to the synchronization link topology information
  • the first sending unit is configured to send a synchronization rule and/or a request message to the second receiving unit according to the synchronization link topology information, where the request message carries the synchronization rule;
  • the second receiving unit is configured to receive the synchronization rule and/or the request message sent by the first sending unit;
  • the locking unit is configured to lock an optimal valid reference source according to the synchronization rule, And output reference source information to other ports.
  • the embodiment of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions, where the computer executable instructions are used to execute the synchronization method provided by the first aspect of the embodiments of the present invention.
  • the computer executable instructions are used in the synchronization method provided by the second aspect of the embodiments of the present invention.
  • the synchronization method, the controller, the synchronization node, the synchronization network, and the storage medium provided by the embodiment of the present invention, wherein the controller in the synchronization network synchronizes the synchronization node according to the physical link topology information of the synchronization network.
  • the information is used to determine the synchronization link topology information; the controller generates a synchronization rule of the synchronization node according to the synchronization link topology information; and the controller sends the synchronization rule to the synchronization network according to the synchronization link topology information.
  • the synchronization node sends the synchronization rule and/or the request message. In this way, the synchronization link can be quickly switched, thereby realizing the real-time performance of the synchronization link switching, thereby effectively improving the synchronization performance of the entire network.
  • Figure 1-1 is a schematic structural diagram of a synchronous link in a related PTN
  • Figure 1-2 is a schematic flowchart of switching when a synchronous link in a related PTN fails.
  • Figure 1-3 is a schematic flowchart of switching when a synchronous link in a related SDN fails.
  • 2-1 is a schematic flowchart 1 of an implementation process of a synchronization method according to an embodiment of the present invention
  • FIG. 2-2 is a second schematic diagram of an implementation process of a synchronization method according to an embodiment of the present invention.
  • 2-3 is a schematic flowchart 3 of an implementation process of a synchronization method according to an embodiment of the present invention.
  • 2-4 is a schematic flowchart 1 of an implementation process of a synchronization method according to Embodiment 2 of the present invention
  • 2-5 are schematic flowcharts showing the implementation process of the synchronization method according to the second embodiment of the present invention.
  • FIG. 3 is a timing diagram of a third synchronization method according to an embodiment of the present invention.
  • FIG. 4 is a timing diagram of a method for synchronizing four embodiments according to an embodiment of the present invention.
  • FIG. 5 is a timing diagram of a fifth synchronization method according to an embodiment of the present invention.
  • FIG. 6 is a timing diagram of a sixth synchronization method according to an embodiment of the present invention.
  • FIG. 7-1 is a schematic structural diagram of a network when an abnormality occurs in a network according to Embodiment 7 of the present invention.
  • FIG. 7-2 is a schematic diagram 1 of a network structure when an abnormality occurs in a network according to Embodiment 7 of the present invention.
  • FIG. 7-3 is a schematic diagram 2 of a network structure when an abnormality occurs in a network according to Embodiment 7 of the present invention.
  • FIG. 8-1 is a schematic diagram 1 of a network structure when an abnormality occurs in a network according to Embodiment 8 of the present invention.
  • FIG. 8-2 is a schematic diagram 2 of a network structure when an abnormality occurs in a network according to Embodiment 8 of the present invention.
  • FIG. 8-3 is a schematic diagram 3 of a network structure when an abnormality occurs in a network according to Embodiment 8 of the present invention.
  • 9-1 is a first schematic structural diagram of a controller of a ninth embodiment of the present invention.
  • FIG. 9-2 is a second schematic structural diagram of a controller according to Embodiment 9 of the present invention.
  • FIG. 9-3 is a schematic structural diagram 3 of a configuration of a controller according to Embodiment 9 of the present invention.
  • 10-1 is a first schematic structural diagram of a ten-synchronous node according to an embodiment of the present invention.
  • 10-2 is a second schematic structural diagram of a ten synchronization node according to an embodiment of the present invention.
  • 10-3 is a schematic structural diagram 3 of a ten-synchronous node according to an embodiment of the present invention.
  • 11-1 is a first schematic structural diagram 1 of a synchronous network according to an eleventh embodiment of the present invention.
  • FIG. 11-2 is a schematic structural diagram 2 of a synchronous network according to Embodiment 11 of the present invention.
  • the synchronization node selects the best input reference source (referred to as the reference source) by running the reference source selection algorithm, and switches to the new optimal input reference source as soon as possible.
  • the selection algorithm comprises an SSM based SSM protocol or PTP.
  • the PTN network shown in Figure 1-1 includes a total of 11 nodes NE1 to NE11, and the two clock reference sources are referred to as the primary reference source.
  • Each node NE includes more than two ports. Only two or three node ports are shown in FIG. 1-1.
  • the node NE1 has three ports, including: one input port for connecting the primary reference source, that is, the lock port of NE1 in FIG. 1-1, respectively.
  • connection nodes NE2 and NE3 are the two output ports of NE1; in Figure 1-1, the lock port is represented by a solid dot, and the output port is represented by a hollow origin. The output port is also called the export port.
  • Each of the synchronization links in Figure 1-1 is marked with a clock quality level (QL).
  • QL clock quality level
  • the S1 byte in the SSM is defined to convey synchronization status information.
  • the QL level of the SSM is high.
  • the node NE3 needs to switch to the new reference source as soon as possible, that is, the step of performing the switching in step S100, for the node NE3
  • the switching time is required to be completed within a few hundred milliseconds (ms), otherwise it will affect the synchronization performance of all downstream nodes of node NE3.
  • the SSM message carrying the fault information is transmitted to the node NE5.
  • the node NE5 runs the reference source selection algorithm according to the SSM protocol. After the algorithm calculates that node NE5 has no better reference source, node NE5 enters the hold state.
  • NE6 and node NE5 nodes NE7 to NE5 run the reference source selection algorithm and will switch to the new reference source one by one.
  • the hop-by-hop transmission of the above SSM message has a certain delay, and the total switching delay increases with the hop count, thereby affecting the frequency synchronization. Performance and time synchronization performance.
  • the architecture of control and forwarding separation is adopted in the SDN technology, that is, the synchronization link topology is calculated by the controller, and the frequency synchronization and/or time synchronization is completed by the synchronization device.
  • the protection switching of the synchronous link has strict time requirements, and it is required to switch to the backup synchronous link as soon as possible in the event of a failure to meet the performance specifications of the existing standard specifications.
  • the controller performs the synchronous link switching, the real-time performance of the synchronous link switching is difficult to meet due to the uncertainty of the message delay and processing delay between the controller and the device. As shown in FIG.
  • step S103 it is assumed that the link between the node NE3 and the node NE5 fails, and then the node NE5 enters the step of entering and holding as in step S103. Then, the synchronization network proceeds to the QL degradation of step S104, and the hop-by-hop notification Step; since the node NE8 locks the node NE7 at the beginning, then the controller commands the node NE8 and the node NE7 to switch, but due to the uncertainty of the communication delay, the node NE7 first performs the switching, so that the node NE7 will lock the node NE8, but the node NE8 still locks node NE7, which causes node NE7 and node NE8 to synchronize link interlocking. Although the interlock time is short, it will still affect the performance of the entire synchronous network.
  • the first embodiment of the present invention provides a synchronization method, which is applied to a controller in a synchronous network.
  • the synchronization network may be an SDN.
  • the controller may be an SDN.
  • Figure 2-1 is a schematic flowchart 1 of the implementation of the synchronization method according to the embodiment of the present invention. As shown in Figure 2-1, the method includes:
  • Step S211 the controller in the synchronization network determines the synchronization link topology information of the synchronization network according to the physical link topology information of the synchronization network and the synchronization information of the synchronization node in the synchronization network.
  • the synchronization information includes at least one of the following information: clock quality level QL information, port priority information, hop count information, synchronization capability information, and the like.
  • the node in the synchronization network refers to a synchronization node controlled by the controller, that is, the controller according to the physical link information of the synchronization network and the synchronization information of the synchronization node controlled by the controller,
  • the synchronization link topology information of the synchronization network is determined.
  • the synchronization capability information can indicate whether the synchronization node has the ability to support frequency synchronization and/or time synchronization. Further, it can indicate whether the port of the synchronization node has the ability to support frequency synchronization and/or time synchronization.
  • Step S212 the controller generates a synchronization rule of the synchronization node according to the synchronization link topology information.
  • the synchronization rule may also be referred to as a synchronization policy, where the synchronization rule includes port information of the input and output of the synchronization node, port priority information, identification (ID) information of each input reference source (optional), Quality level information (optional) of each input reference source, and priority information of each input reference source.
  • the synchronization method and device and the synchronization network provided by the embodiments of the present invention can be applied to a time synchronization network, a frequency synchronization network, or a frequency synchronization network and a time synchronization network.
  • the synchronization rule further includes a transmission rate and a working mode of the timing message of each input/output interface/port, such as a single-step method, a two-step method, etc., wherein the timing message Types include Sync, Follow_up, Delay_req, Delay_resp, Pdelay_req, Pdelay_resp, and so on.
  • the synchronization rule includes at least one of the following:
  • Step S213 the controller sends the synchronization rule and/or request message to the synchronization node in the synchronization network according to the synchronization link topology information.
  • the request message is used to indicate that a synchronization node controlled by the controller establishes a synchronization link according to a synchronization rule
  • the controller sends the synchronization rule and/or the request message to the synchronization node in the synchronization network according to the synchronization link topology information, including:
  • the controller sends the synchronization rule to a synchronization node in the synchronization network according to the synchronization link topology information;
  • the controller sends a synchronization rule and a request message to the synchronization node in the synchronization network according to the synchronization link topology information.
  • the controller sends a synchronization rule and a request message to the synchronization node in the synchronization network according to the synchronization link topology information, including:
  • the controller sends a synchronization rule to the synchronization node in the synchronization network according to the synchronization link topology information, and then sends a request message to the synchronization node in the synchronization network, where the request message does not carry the synchronization rule.
  • the controller sends a synchronization rule and a request message to the synchronization node in the synchronization network according to the synchronization link topology information, including:
  • the controller sends a request message to the synchronization node in the synchronization network according to the synchronization link topology information, where the request message carries the synchronization rule.
  • the method before the step S211, as shown in FIG. 2-2, the method further includes:
  • Step S210 After the power-on is started, the controller acquires synchronization information of the synchronization node in the synchronization network, and detects a physical connection relationship between the ports of the synchronization node to obtain the physical link topology information.
  • the method further includes:
  • Step 214 After receiving the switching completion message sent by the synchronization node, the controller updates the synchronization link topology information and/or the synchronization rule.
  • the step S214 includes:
  • the controller After receiving the switching completion message sent by the synchronization node, the controller updates the synchronization link topology information; or
  • the controller After receiving the switching completion message sent by the synchronization node, the controller updates the synchronization rule; or
  • the controller After receiving the switching completion message sent by the synchronization node, the controller updates the synchronization link topology information and the synchronization rule;
  • the first manner includes:
  • step A1 the controller updates the synchronization link topology information according to the physical link topology information of the synchronization network and the synchronization information of the synchronization node in the synchronization network.
  • step A2 the controller updates the synchronization rule according to the synchronization link topology information.
  • the controller updates the synchronous link topology according to the identifier information of the best reference source, where the switching completion message carries the identifier information of the optimal reference source.
  • Information and synchronization rules are used to determine the synchronous link topology according to the identifier information of the best reference source.
  • the method further includes:
  • the controller carries the topology information and the synchronization rule of the updated synchronization link in the setup request message, and sends the synchronization node to the synchronization node that needs to be resynchronized.
  • the method further includes:
  • the controller receives a fault message sent by the synchronization node to indicate that there are no other valid reference sources;
  • the controller determines whether all of the downstream nodes of the synchronization node have an alternate reference source, and when yes, sends a switching request message indicating the switching to the alternate reference source to the downstream node having the candidate reference source.
  • the method further includes:
  • the controller sends a hold request message to the first downstream node to request the first downstream node to enter a hold mode.
  • the second embodiment of the present invention provides a synchronization method, which is applied to a synchronization node in a synchronization network.
  • the synchronization network may be an SDN.
  • the synchronization node may be a synchronization node in the SDN.
  • 4 is a schematic flowchart 1 of an implementation process of a synchronization method according to Embodiment 2 of the present invention. As shown in FIG. 2-4, the method includes:
  • Step S221 the synchronization node in the synchronization network receives the synchronization rule and/or the request message sent by the controller in the synchronization network;
  • the synchronization node receives the synchronization rule and/or the request message sent by the controller in the synchronization network, including:
  • the synchronization node receives a synchronization rule sent by a controller in the synchronization network; or
  • the synchronization node receives a request message sent by a controller in the synchronization network;
  • the synchronization node receives a synchronization rule and a request message sent by a controller in the synchronization network.
  • the synchronization node receives the synchronization rule and the request message sent by the controller in the synchronization network, including:
  • the synchronization node receives the synchronization rule sent by the controller in the synchronization network, and then receives the request message sent by the controller for establishing a synchronization link.
  • the synchronization node receives the synchronization rule and the request message sent by the controller in the synchronization network, and the synchronization node receives the request message sent by the controller in the synchronization network, where the request message carries the Synchronization rules.
  • Step S222 the synchronization node locks an optimal valid reference source according to the synchronization rule, and outputs reference source information to other ports.
  • the reference source information includes frequency and/or time information; the locks the best valid reference source, including the frequency and/or time of the input port that locks the optimal valid reference source.
  • the best effective reference source may be the highest priority input reference source, or the input reference source with the highest quality level information. Those skilled in the art may also determine the best effective reference according to various prior art techniques. Source, so I won't go into details.
  • the method further includes:
  • Step S223 the synchronization node determines whether an alarm is generated by the input reference source, and if yes, continues to determine whether there are other valid reference sources according to the synchronization rule;
  • Step S224 when the synchronization node determines that there are other valid reference sources according to the synchronization rule, the synchronization node switches to the best reference source according to the synchronization rule.
  • the method further includes:
  • the synchronization node updates the local synchronization rule and sends a switch completion message to the controller.
  • the controller updates the synchronization link topology information and the synchronization rule after receiving the switching completion message.
  • the switching completion message only carries the switching completion identifier, and the switching completion identifier is only used to notify the controller that the synchronization node has been switched, and the controller itself includes physical link topology information and synchronization of all nodes. Information, therefore, the controller can update the synchronization link topology information according to the description of step S211, and update the synchronization rule according to the description of step S212. It can be seen that updating the synchronization link topology information and the synchronization rule in this manner are all performed on the controller side, and thus it is suitable for the synchronization network that the number of synchronization nodes is not huge.
  • the switching completion message may carry the identification information of the best reference source, and the method of carrying the two types of identifiers is compared with the previous method of carrying only the switching completion identifier.
  • There is a switching completion flag so that the controller can update the synchronization link topology information and the synchronization rule more specifically according to the switching completion flag, thereby enabling fast update, and, due to updating the synchronization link topology information and synchronization rules
  • the computing power consumed by the controller is relatively weak, so the way with two types of identification is suitable for synchronizing a large number of synchronous networks.
  • the method further includes:
  • the synchronization node that needs to perform resynchronization receives the request message sent by the controller, where the request message carries the updated synchronization link topology information and synchronization rules;
  • the synchronization node that needs to perform resynchronization locks the best effective reference source according to the synchronization rule, and outputs the reference source information to other ports.
  • the method further includes:
  • the synchronization node enters a hold mode when it is determined that there are no other valid reference sources according to the synchronization rule, and sends to the controller to indicate that there are no other valid reference sources. Fault message.
  • the method further includes:
  • the synchronization node After receiving the switching request message sent by the controller to indicate switching to the alternate reference source, the synchronization node switches to the candidate reference source, and sends a switching message indicating the switching to the first synchronization node in the upstream.
  • the method further includes:
  • the first synchronization node of the upstream determines, according to the synchronization rule, whether an input port that receives the switching message is legal;
  • the reference source switching is performed according to the synchronization rule, and the switching completion message is sent to the controller; and when it is determined that there is a valid input reference source, the switching message is forwarded to the port with the valid input reference source. Notifying the upstream node, or delaying the period of time, forwarding the reverse message to the port having the valid input reference source to advertise the upstream node; not determining the switching of the original input source when it is determined that there is no valid input reference source itself Message.
  • a third embodiment of the present invention provides a synchronization method, which is applied to a synchronization network, where the synchronization network includes a controller 300 and a plurality of synchronization nodes 380 controlled by the controller 300.
  • the synchronization network may be SDN;
  • FIG. 3 is a timing diagram of a third synchronization method according to an embodiment of the present invention. As shown in FIG. 3, the method includes:
  • Step S311 obtaining physical link topology information.
  • the controller 300 acquires the synchronization information of all the synchronization nodes in the synchronization network, and detects the physical connection relationship between the ports of all the synchronization nodes, and obtains the physical link topology information. Preferably, this step is performed when the synchronous network is powered on.
  • Step S312 determining synchronization link topology information
  • the controller in the synchronization network according to the physical link topology information of the synchronization network, Synchronizing information of the synchronization node in the synchronization network to determine synchronization link topology information of the synchronization network;
  • the synchronization information includes at least one of the following information: clock quality level QL information, port priority information, hop count information, synchronization capability information, and the like.
  • the controller generates a synchronization rule of the synchronization node according to the synchronization link topology information
  • Step S314 sending a request message
  • the controller sends a request message for establishing a synchronization link to the synchronization node in the synchronization network according to the synchronization link topology information, where the request message carries the synchronization rule.
  • the request message in step S314 may also not carry the synchronization rule generated in step S313, and correspondingly, in step S313, further includes the step of transmitting a synchronization rule to the synchronization node.
  • the request message may not be sent to the synchronization node, and only the synchronization rule is sent to the synchronization node, and the synchronization node starts to execute step S315 after receiving the synchronization rule.
  • the synchronization rule includes at least one of the following:
  • the synchronization node When the synchronization node detects an alarm, the synchronization node first determines whether it has multiple valid reference sources, and if yes, it switches to the most according to the synchronization rule. A good reference source sends a switch completion message to the controller; otherwise, the synchronization node enters the hold mode and sends an alert message to the controller.
  • a policy of how to forward the synchronization node when receiving the switching message of the downstream node, where the switching message is used to indicate how the synchronization node performs switching is used to indicate how the synchronization node performs switching.
  • the synchronization policy determines the validity of the switching message according to the synchronization rule. When it is determined that the switching message is invalid, no switching is performed. When it is judged that the switching message is legal, it is based on the The message is exchanged and the controller is notified; then, it is determined whether the state of the input source after the switching is valid. When it is determined that the state of the input source is valid, the switching message is continuously sent to the output port, otherwise the switching message is not sent.
  • each synchronization node 380 locks the frequency and/or time information of the best valid reference source input port according to the synchronization rule, and outputs the frequency and/or to other output ports in the synchronization node. Or time information.
  • step S314 in this embodiment may also be split into two steps.
  • the controller 300 sends the synchronization rule to each synchronization node 380.
  • the controller 300 sends a request message for establishing a synchronization link to each synchronization node 380, so that the synchronization rule may not be carried in the request message in the second step.
  • the fourth embodiment of the present invention provides a synchronization method, which is applied to a synchronization network, where the synchronization network includes a controller 400 and a plurality of synchronization nodes controlled by the controller 400.
  • the synchronization method in the fourth embodiment includes the following figure. After the steps S311 to S315 shown in FIG. 3, as shown in FIG. 4, the method further includes:
  • Step S411 the synchronization node 410 detects an alarm
  • the synchronization node 410 controlled by the controller 400 detects an input source failure, that is, the synchronization node 410 detects an alarm;
  • Step S412 the synchronization node 410 determines whether there is a valid reference source, if yes, proceeds to step S413;
  • the synchronization node 410 determines whether it has other valid input reference sources according to the synchronization rule, and if yes, proceeds to step S413;
  • Step S413 the synchronization node 410 switches to the best reference source, and updates the local synchronization rule
  • the synchronization node 410 determines that there are other valid inputs in itself according to the synchronization rule. After entering the reference source, the priority information of the input reference source in the synchronization rule is switched to the optimal input reference source, and the local synchronization rule is updated after the conversion;
  • Step S414 the synchronization node 410 sends a switching completion message to the controller 400;
  • the switching completion message sent by the synchronization node 410 to the controller 400 can be referred to the second embodiment, and therefore will not be described again.
  • Step S415 the controller 400 updates the synchronization link topology information and the synchronization rule
  • the controller 400 updates the synchronization link topology information and the synchronization rule. For details, refer to the second embodiment. Therefore, the controller 400 needs to determine that the resynchronization needs to be performed according to the updated synchronization link topology information. Synchronize nodes.
  • the controller 400 carries the topology information and the synchronization rule of the updated synchronization link in the setup request message, and sends the synchronization node 420 to the synchronization node 420 that needs to be resynchronized.
  • Step S417 the synchronization node 420 that needs to perform resynchronization performs locking and outputting;
  • the synchronization node 420 that needs to perform resynchronization receives the request message sent by the controller, where the request message carries the updated synchronization link topology information and synchronization rules;
  • the synchronization node that needs to perform resynchronization locks the frequency and/or time of the best valid reference source input port according to the synchronization rule, and outputs frequency and/or time information to other ports.
  • the fifth embodiment of the present invention provides a synchronization method, which is applied to a synchronization network, where the synchronization network includes a controller 500 and a plurality of synchronization nodes controlled by the controller 500.
  • the synchronization method in the fifth embodiment includes the following After the steps S311 to S315 shown in FIG. 3, as shown in FIG. 5, the method further includes:
  • Step S511 the synchronization node 510 detects an alarm
  • the synchronization node 510 controlled by the controller 500 detects an input source failure, that is, the synchronization node 510 detects an alarm;
  • Step S512 the synchronization node 510 determines whether there is a valid reference source, if not, proceeds to step S513;
  • the synchronization node 510 determines whether it has other valid input reference sources according to the synchronization rule, if not, proceeds to step S513;
  • Step S513 the synchronization node 510 enters a hold mode
  • the phase locked loop in the synchronization node 510 will enter a hold mode or a hold state; in step S513, the phase locked loop in the synchronization node 510 will enter the hold mode. Or keeping the state belongs to the prior art, so it will not be described again.
  • Step S514 the synchronization node 510 sends a fault message to the controller 500;
  • the synchronization node 510 will send a fault message to the controller 500;
  • the fault message is used to indicate that the synchronization node 510 has an alarm condition, that is, an abnormality occurs in the synchronization network; the controller 500 learns that the synchronization node 510 is abnormal through the fault message, and it can be seen that the control message of the fault message is synchronously switched by the synchronization node 510.
  • the controller 500 is handed over to the controller 500 for synchronous link switching by the controller 500 in a subsequent step.
  • the fault message is forwarded to the controller 500 by the synchronization section 510.
  • the synchronization node 510 determines that it has a valid input reference source, the synchronous switching is performed.
  • the control is controlled by its own synchronization node 510.
  • the synchronization node 510 determines that it does not have a valid reference source itself, it is necessary to hand over the control of the synchronization switching to the controller 500.
  • Step S515 the controller 500 determines whether there is an alternative reference source among all the downstream nodes. Node, if yes, proceed to step S516;
  • the controller 500 will determine whether there is a node with an alternate reference source among all the nodes downstream of the synchronization node 510, assuming that there is an alternative reference in the downstream node of the synchronization node 510.
  • the node of the source is the synchronization node 520, and if yes, the process proceeds to step S516;
  • the switching request message is used to request a downstream node with an alternate input reference source to switch to an alternate input reference source, and to request the downstream node with the alternate input reference source to its first upstream node
  • the switching message is sent; specifically, in the synchronization node 520 in this embodiment, the switching request message is used for the downstream node 520 to switch to the alternate input reference source, and is used to request the downstream node 520 to the first upstream node of the node 520.
  • 530 sends a reverse message, assuming that the first upstream node of downstream node 520 is synchronization node 530.
  • Step S517 the synchronization node 520 switches to the candidate reference source
  • the synchronization node 520 receives the switching request message sent by the controller 500; the switching request message may also carry the identification information of the candidate reference source, or may not carry the identification information of the candidate reference source; when the switching request message carries When the identification information of the reference source is alternately referenced, the synchronization node 520 switches to the candidate input reference source according to the identification information of the candidate reference source; when the switching request message does not carry the identification information of the candidate reference source, the synchronization node The 520 is switched to an alternate input reference source according to a synchronization rule.
  • the switching completion message sent by the synchronization node 520 to the controller can be referred to the second embodiment described above, and therefore will not be described again.
  • Step S519 the controller 500 updates the synchronization link topology information and the synchronization rule
  • step S518 can be specifically referred to the foregoing embodiment 2, and therefore will not be described again; in addition, step S518 and step S19 are related to each other, that is, step S518 occurs first, and step S519 occurs. It happened later.
  • Step S520 the synchronization node 520 sends a switching message to the synchronization node 530;
  • the synchronization node 530 is the first node upstream of the synchronization node 520;
  • the switching message is used to indicate that the first node in the upstream performs switching; in addition, there is no sequential association between steps S520 and S518, which may occur before step S518, or may occur after step S518.
  • Step S521 the synchronization node 530 verifies the legality, and if yes, proceeds to step S522;
  • the synchronization node 530 After receiving the switching message sent by the synchronization node 520, the synchronization node 530 performs the validity verification of the received switching message, that is, checks the legality of the switching message input port according to the output port information in the synchronization rule, when The synchronization node 530 continues to determine whether it has a valid input reference source according to the synchronization rule, that is, whether the link is faulty. If there is an input reference source, indicating that the link is normal, the forwarding message is forwarded to the output port (enter step) S522); otherwise, the process proceeds to step S523.
  • step S521 is an optional step, and the switching message may be directly sent to the upstream node without performing verification.
  • Step S522 the synchronization node 520 sends a switching message to the synchronization node 540;
  • the synchronization node 540 is the first node upstream of the synchronization node 530, that is, the second node upstream of the synchronization node 530; at this time, the synchronization node 540 still verifies the validity of the reverse message, and when it is legal, the synchronization node 540 continues to send a reverse message to its first upstream node, and then the first upstream node of synchronization node 540 verifies the validity of the reverse message, and so on, until the reverse message is delivered to the upstream node to the synchronization node 510.
  • Step S523 the synchronization node 530 sends an illegal message to the controller 500;
  • the synchronization node 530 when verifying that the received switching message is illegal, the synchronization node 530 sends an illegal message to the controller 500, where the illegal message is used to indicate that the synchronization node 530 is abnormal, and the controller 500 learns that the synchronization node 530 is abnormal through the illegal message. , visible, the illegal message will be synchronized The changed control is handed over to the controller 500 by the synchronization node 530. In the subsequent steps, the controller 500 performs synchronous link switching. The subsequent more specific steps will be detailed in the following sixth embodiment.
  • the fault message in the process of fault transmission, is directly transmitted to the controller, and then the controller 500 performs a link switching decision; thus, the abnormal node or link of the network can be quickly detected. It is passed to the controller, which is quickly switched by the controller, thereby avoiding the drawbacks of the technology in the hop-by-hop transmission mode.
  • the fault delivery process refers to a process in which the synchronization node 510 sends an error message to the controller 500 when the synchronization node 510 has an alarm and the synchronization node 510 does not have a standby input reference source.
  • hop-by-hop transmission for fault transmission is that in the hop-by-hop transmission process, each node needs to maintain a delay time, and the total switching delay will increase as the hop count increases, which makes it difficult to ensure that the switching is satisfied. Time requirements are within a few hundred milliseconds (ms), affecting frequency synchronization performance and time synchronization performance.
  • the hop-by-hop transmission mode is adopted in the process of link synchronization, and the delay time of each synchronization node may not be maintained in the process of hop-by-hop transmission, that is, after receiving the switching message, it is determined.
  • the switching message is legal, the switching message is directly delivered to the next synchronization node; if the total switching time is allowed, the delay time may also be maintained on each synchronization node; whether to maintain the delay time, control
  • the device can determine according to the number of hops. If the hop count is within the threshold range, it can be maintained. If it is not within the threshold range, the maintenance is not performed.
  • the reason for the link-by-hop transmission in the process of link synchronization is to avoid link interlocking.
  • the sixth embodiment of the present invention provides a synchronization method, which is applied to a synchronization network, where the synchronization network includes a controller 600 and a plurality of synchronization nodes controlled by the controller 600.
  • the synchronization method in the sixth embodiment includes the following figure. After the steps S311 to S315 shown in FIG. 3, as shown in FIG. 6, the method further includes:
  • Step S611 the synchronization node 610 detects an alarm
  • the synchronization node 610 controlled by the controller 600 detects an input source failure, that is, the synchronization node 610 detects an alarm;
  • Step S612 the synchronization node 610 determines whether there is a valid reference source, if not, proceeds to step S613;
  • the synchronization node 610 determines whether it has other valid input reference sources according to the synchronization rule, if not, proceeds to step S613;
  • Step S613 the synchronization node 610 enters the hold mode
  • the phase locked loop in the synchronization node 610 will enter a hold mode or a hold state.
  • Step S614 the synchronization node 610 sends a fault message to the controller 600;
  • Step S615 the controller 600 determines whether there is a node with an alternate reference source among all the downstream nodes, if not, proceeds to step S616;
  • the controller 600 will determine whether there is a node with an alternate reference source among all nodes downstream of the synchronization node 610, assuming that there is an alternative reference in the downstream node of the synchronization node 610.
  • the node of the source is the synchronization node 620, if not, proceed to step S616;
  • Step S616 the controller 600 determines a synchronization node of a clock having a higher QL or better retention performance
  • the controller 600 determines a synchronization node of a clock having a higher QL or better retention performance among all nodes downstream of the synchronization node 610, assuming synchronization of the clock (crystal oscillator) having a higher QL or better retention performance
  • the node is node 620;
  • Step S617 the controller 600 sends a hold request message to the synchronization node 620.
  • the hold request message indicates that the synchronization node 620 enters a hold mode.
  • Step S619 the synchronization node 620 sends a status notification message to the controller 600;
  • the status announcement message sent by the synchronization node 620 to the controller is used to indicate that the synchronization node 620 has entered the hold mode.
  • controllers 400, 500 and 600 are only denoted by different reference numerals in different embodiments, and in fact the controllers 400, 500 and 600 refer to the same object, for example.
  • Controllers 400, 500, and 600 can all refer to controllers in the same SDN; synchronization nodes 410, 510, and 610 also refer to the same synchronization node, ie, the synchronization node in the same SDN where an alarm occurs.
  • synchronization method is applicable not only to a frequency synchronization network (SyncE, PTP) but also to a time synchronization network (PTP).
  • SynE frequency synchronization network
  • PTP time synchronization network
  • a synchronization method provided by an embodiment of the present invention is applied to a synchronization network, and the method includes the following steps:
  • Step C1 After the controller and the synchronization node in the synchronization network are powered on, all the synchronization nodes establish a Transmission Control Protocol (TCP) and a TCP/Secure Sockets Layer (SSL) connection with the controller.
  • TCP Transmission Control Protocol
  • SSL TCP/Secure Sockets Layer
  • the node information includes a Media Access Control (MAC) address, an Internet Protocol (IP) address, a device capability parameter, a port configuration parameter, and the like; wherein the port (P, Port) Refers to the node's input (I, Input) port or output (O, Output) port.
  • MAC Media Access Control
  • IP Internet Protocol
  • P, Port Refers to the node's input (I, Input) port or output (O, Output) port.
  • step C2 the controller detects the physical connection relationship between the nodes of all the synchronization nodes in the synchronization network by sending a Link Layer Discovery Protocol (LLDP) packet, so that the controller obtains the physical link topology information of the synchronization network.
  • LLDP Link Layer Discovery Protocol
  • the controller sends an LLDP packet, and detects that the physical link topology of the synchronization network shown in Figure 7-1 includes two ring links, where a ring link refers to a node.
  • another ring link is a ring link composed of NE3 to NE11.
  • Step C3 The controller determines synchronization link topology information based on information such as quality/time source (QL) information of the clock/time source, QL information of the synchronization node, and local priority and hop count of the synchronization port.
  • QL quality/time source
  • the synchronous link topology represented by the synchronous link topology information is a topology without a ring link; and the physical link topology represented by the foregoing physical link topology information is a ring link including Topology.
  • the local priority of the synchronization port is abbreviated as priority and is represented by the Arabic numerals 1, 2, 3, etc., wherein the smaller the number indicating the priority, the higher the priority level it represents, that is, the priority A level of 1 indicates the highest priority.
  • the synchronization link topology determined by the controller is shown by a solid black line, wherein the direction of the arrow of the black solid line is the transmission direction of the reference source;
  • the dotted line is a broken point, that is, the link between the node NE3 and the node NE4 is a broken point, and the link between the node NE8 and the node NE9 is a broken point;
  • Step C4 The controller generates a synchronization node synchronization rule according to the physical link topology information and the synchronization link topology information, and delivers the synchronization rule to the synchronization node.
  • the synchronization node NE3 is taken as an example to describe that the controller sends a synchronization rule to the synchronization node.
  • the synchronization rules sent by the controller to the node NE3 are as shown in Figure 7-1.
  • the ports (P, Port) 31 and P32 of the NE3 are the input ports of the reference source, but the priority of the reference source of the P31 is higher than the priority of the P32.
  • the node NE3 obtains the input reference source from P31; meanwhile, the reference sources of the two input ports P31 and P32 of the node NE3 are valid, indicating that there is no alarm, etc.
  • step C5 the controller sends a request message for establishing a synchronization link to each synchronization node to establish a synchronization link of the frequency and/or time of the entire network.
  • each synchronization node After receiving the request message, each synchronization node receives the request message.
  • the highest priority reference source will be locked according to the synchronization rule and frequency and/or time information will be sent to other ports;
  • the controller determines the synchronization topology information, it sends a request message for establishing a synchronization link to the synchronization node NE3 (see the dotted line L701); after receiving the request message, the synchronization node NE3 will synchronize according to The rule locks the corresponding reference source input port, that is, locks P31, and outputs frequency and/or time information to other ports, namely P33 and P32;
  • Step C6 After the synchronization node detects the current input source failure, if there are other valid reference sources in the synchronization rule, the current reference is switched to the best reference source according to the priority, the local synchronization rule is updated after the switching, and the switching completion notification notification control is performed.
  • the controller updates the synchronization link topology information and the synchronization rule, and establishes a new synchronization link;
  • the NE3 node is taken as an example. If the input source of the node NE3 fails, the node NE3 enters the alarm detecting step as shown in step S721.
  • the node NE3 enters the step of local switching as shown in step S722, including: the node NE3 determines that it has other valid reference sources according to the synchronization rule, and then switches to P32 according to the synchronization rule;
  • the node NE3 enters the step of switching the notification as shown in step S723, and includes: after the switching is completed, the node NE3 sends a switching completion message to notify the controller.
  • the controller enters the step of performing topology recalculation as shown in step S724, including: after receiving the switching completion message, the controller re-determines the synchronization link topology information; and regenerating the synchronization node synchronization rule;
  • the controller enters the steps of the topology update and the synchronization rule update as shown in step S725, including: after the controller recalculates the topology, and discovers that the topology of the node NE7 and the node NE8 changes, the synchronization rules of the NE7 and the NE8 are updated. And establish a new synchronous link; other nodes The topology and synchronization rules remain the same.
  • Step C7 After the synchronization node detects the current input source failure, if the synchronization rule has no other valid reference source, the synchronization node enters the hold state, and then sends a fault message to the controller, and the controller performs synchronous link switching;
  • the node NE6 if the NE6 input reference source fails, the node NE6 first enters the step of entering and holding as shown in step S731, that is, there is no other valid in the NE6 check synchronization rule. Entering the reference source, the node NE6 enters the hold state;
  • step S732 includes: the node NE6 sends a fault message to the controller, and the controller performs the processing of the synchronous link;
  • the controller enters the step of performing topology recalculation as shown in step S733, including: after receiving the fault message, the controller re-determines the synchronization link topology information; and regenerating the synchronization node synchronization rule;
  • the controller enters the step of the switching request as shown in step S734, including: after the controller recalculates the topology, the controller finds that the downstream node NE8 of the node NE6 has an alternate reference source, and sends a switching request message to the node NE8.
  • the switching request message is used to instruct the node NE8 to switch to the node NE9, and instructs the NE8 to send a switching message to the upstream node NE7.
  • the foregoing switching process belongs to a real-time switching process.
  • the synchronization node immediately performs local switching as soon as it finds that the local input reference source is available, and notifies the controller to perform topology update after the switching is completed.
  • the synchronization rule update on the other hand, when the synchronization node finds that there is no standby input reference source locally, the fault message is immediately sent to the controller, and the controller performs the synchronization link switching. It can be seen that, in this embodiment, whether the notification after the local switching is completed or the failure notification is directly interacted with the controller, the real-time performance of the link synchronization can be ensured.
  • This embodiment provides a synchronization method applied to a synchronization network, where the synchronization network includes control And a plurality of synchronization nodes controlled by the controller; the method comprising:
  • the first five steps D1 to D5 of this embodiment can be referred to C1 to C5 in the seventh embodiment accordingly, and therefore, details are not described herein again.
  • Step D6 When the current input reference source of the synchronization node fails, check whether there are other valid reference sources in the synchronization rule; if not, the synchronization node first enters the hold state and updates the synchronization rule; then sends a fault message to the controller. , the synchronization link processing by the controller;
  • the node NE5 if the current input reference source of the node NE5 fails, the node NE5 enters the step of entering and holding as shown in step S811, including: the node NE5 checks that there is no other available input reference source in the synchronization rule, NE5 enters the hold state and updates the synchronization rule;
  • the step of the node NE5 entering the alarm notification as shown in step S812 includes: the node NE5 is notified to the controller by the fault message, and the controller performs the processing of the synchronization link;
  • Step D7 the controller receives the fault message, then checks whether all nodes downstream of the synchronization node have an alternative input reference source, if yes, proceeds to step D81; if not, proceeds to step D82;
  • step D81 the controller sends a switching request message to the node with the alternative input reference source, and then proceeds to step D9;
  • the switching request message is used to request that a node with an alternate input reference source is switched to an alternate reference source, and is configured to request the node with the candidate input reference source to send a switching message to the upstream node;
  • step S813 the controller enters the steps of the topology recalculation as shown in step S813, including:
  • the controller receives the fault message of the node NE5, first updates the synchronization rule of the node NE5, checks whether there are nodes with the alternative input reference source in all the downstream nodes of the node NE5, and checks that the downstream node NE8 has an alternative input reference. source;
  • step S814 the controller The node NE8 sends a switching request message, which is used to request that the synchronization node NE8 is switched to the candidate reference source, and is used to request the synchronization node NE8 to send a switching message to the upstream node NE7 to notify the synchronization node NE7 to perform synchronous link switching. ;
  • the controller also needs to notify the node that the topology changes to update the synchronization rule; here, refer to step L801 of FIG. 8-1, including: the controller discovers the synchronization of the node NE9 according to the topology recalculation. The rule needs to be updated, and a request message is sent to the node NE8, which carries the synchronization rule of NE9.
  • Step D82 the controller determines a node of the downstream node of the synchronization node that has a higher quality level or better retention performance, and then the controller sends a hold request message to the node with a high quality level or better maintained performance clock. Entering a hold mode in a node requesting a clock with a high quality level or better performance;
  • step S831 and step S832 in FIG. 8-3 are respectively the same as steps S811 and S812 in FIG. 8-1, and therefore will not be described again.
  • the controller detects that there is no alternative input reference source in the downstream node of the node NE5, but the downstream node NE8 of the node NE5 has a better retention performance clock, that is, the TSC node.
  • the controller sends a hold request message to the node NE8, requesting the node NE8 to enter the hold mode, so that the NE8 can enter the hold as soon as possible, thereby improving the synchronization performance of the base station.
  • Step D9 the node with the alternative input reference source sends a switching message to the upstream node, proceeds to step D10;
  • step D81 the example in step D81 is continued.
  • the synchronization node NE8 transmits a switching message to the upstream node NE7.
  • step D10 the upstream node receives the switching message sent by the node with the candidate input reference source, and calculates the port information according to the synchronization rule to check the validity of the switching message entry; if it is legal, the reference source switching is performed according to the synchronization rule. After the switchover is completed, a message is sent to notify the controller;
  • step D10 takes the above step D9;
  • the upstream node NE7 receives the switching message sent by the synchronization node NE8, and the upstream node NE7 checks according to the synchronization port according to the input port information of the switching message, and finds the switching message. If it is received from the downstream port (P72), it is determined that the switching message is legal;
  • the node NE7 switches to the downstream port P72 and updates the synchronization rule
  • the node NE7 sends a switch completion message to notify the controller that the controller updates the synchronization rule of the node NE7 to ensure the consistency of the synchronization rules.
  • the node NE7 checks that the synchronization rule has a valid input reference source (corresponding to the port 71), and then forwards the reverse message to the port 71;
  • the switching message may be delayed for a period of time and then forwarded, that is, the switching message may be forwarded by the NE7 to the upstream node NE6 after the delay time is maintained;
  • Step D11 after the second upstream node of the node with the candidate input reference source receives the switching message sent by the first upstream node of the node with the candidate input reference source, performs legality verification and forwards the reverse message;
  • the step D11 continues to take the step D10, and continues to take the example in the step D10.
  • the processing flow of the NE6 and the node NE7 receive The processing flow of the switching message sent to the node NE8 is similar, so it will not be described again.
  • the switching message reaches the faulty node NE5. After the faulty node NE5 completes the switching, the switching completion message is sent to the controller, and the node NE5 finds the original reference source, that is, the primary reference. After the source is invalid, the switching message is no longer forwarded.
  • FIG. 9-1 is a schematic structural diagram 1 of a controller according to Embodiment 9 of the present invention.
  • the controller 900 includes a first determining unit 901 and a generating unit. 902 and a first sending unit 903, wherein:
  • the first determining unit 901 is configured to perform a physical link topology information according to the synchronization network.
  • Information synchronization information of the synchronization node in the synchronization network, determining synchronization link topology information of the synchronization network;
  • the generating unit 902 is configured to generate a synchronization rule of the synchronization node according to the synchronization link topology information.
  • the first sending unit 903 is configured to send the synchronization rule and/or request message to a synchronization node in the synchronization network according to the synchronization link topology information;
  • the first sending unit 903 is configured to: when the request message is sent to the synchronization node in the synchronization network according to the synchronization link topology information, the request message carries the synchronization rule.
  • the controller 900 further includes an obtaining unit 904 and a detecting unit 905, where:
  • the acquiring unit 904 is configured to acquire synchronization information of the synchronization node in the synchronization network
  • the detecting unit 905 is configured to detect a physical connection relationship between ports of the synchronization nodes, and obtain the physical link topology information.
  • the controller 900 further includes a first receiving unit 906 and an updating unit 907, wherein:
  • the first receiving unit 906 is configured to receive a switching completion message sent by the synchronization node, and trigger the updating unit;
  • the updating unit 907 is configured to update the synchronization link topology information and/or the synchronization rule.
  • the updating unit 907 is further configured to: according to the physical link topology information of the synchronization network, the synchronization network. Synchronizing information of the synchronization node, updating the synchronization link topology information; and updating the synchronization rule according to the synchronization link topology information.
  • the switching completion message carries the identifier information of the best reference source;
  • the update unit 907 is further configured to: the controller update the synchronization link topology information and the synchronization rule according to the identifier information of the optimal reference source.
  • the first sending slip 906 is further configured to: determine, according to the updated synchronization link topology information, a synchronization node that needs to be resynchronized; and carry the updated synchronization link topology information and the synchronization rule in the setup request. In the message, it is sent to the synchronization node that needs to be resynchronized.
  • the controller further includes a first determining unit
  • the first receiving unit is further configured to receive a fault message sent by the synchronization node to indicate that there is no other valid reference source, triggering the determining unit;
  • the first determining unit is configured to determine whether all the downstream nodes of the synchronization node have an alternate reference source, and when yes, trigger the first sending unit;
  • the first sending unit is configured to send, to a downstream node having an alternate reference source, a switching request message for indicating switching to an alternate reference source.
  • the first determining unit is further configured to: when it is determined that all the downstream nodes of the synchronization node do not have an alternative reference source, determine that the downstream node of the synchronization node has a higher quality level or The first downstream node of the clock that maintains performance is triggered to trigger the first sending unit;
  • the first sending unit is configured to send a hold request message to the first downstream node to request the first downstream node to enter a hold mode.
  • FIG. 10-1 is a schematic structural diagram 1 of a ten-synchronization node according to an embodiment of the present invention.
  • the synchronization node 1000 includes a second receiving unit 1001 and a locking unit. 1002, where:
  • the second receiving unit 1001 is configured to receive a synchronization rule and/or a request message sent by a controller in the synchronization network;
  • the locking unit 1002 is configured to lock an optimal valid reference source according to the synchronization rule, and output reference source information to other ports.
  • the synchronization node further includes a second determining unit 1003 and a switching unit 1004, where:
  • the second determining unit 1003 is configured to determine whether an alarm is generated by the input reference source, and if yes, continue to determine whether there are other valid reference sources according to the synchronization rule, and when yes, trigger the switching unit;
  • the switching unit 1004 is configured to switch to an optimal reference source according to the synchronization rule.
  • the synchronization node 1000 further includes a second sending unit 1005 configured to update a local synchronization rule and send the signal to the controller. Switch completion message.
  • the second receiving unit is further configured to receive a request message sent by the controller, where the request message carries updated synchronization link topology information and a synchronization rule, and the locking is triggered. unit;
  • the locking unit is configured to lock an optimal valid reference source according to a synchronization rule and output reference source information to other ports.
  • the synchronization node further includes a holding unit
  • the second determining unit is configured to trigger the holding unit when determining that there is no other valid reference source according to the synchronization rule
  • the holding unit is configured to enable the synchronization node to enter a hold mode and trigger the second sending unit;
  • the second sending unit is configured to send a fault message to the controller indicating that there are no other valid reference sources.
  • the second receiving unit is configured to receive a switching request message sent by the controller for indicating switching to an alternate reference source, and trigger the switching unit;
  • the switching unit is configured to switch to an alternate reference source and trigger the second sending unit
  • the second sending unit is configured to send a switching message for indicating switching to the first synchronization node in the upstream.
  • the second receiving unit is configured to receive the switching message, and trigger the second determining unit
  • the second determining unit is configured to determine, according to the synchronization rule, whether an input port that receives the switching message is legal, and when yes, trigger the switching unit;
  • the switching unit is configured to perform reference source switching according to a synchronization rule, and trigger the second sending unit;
  • the second sending unit is configured to send a switching completion message to the controller.
  • FIG. 11-1 is a schematic structural diagram 1 of a synchronization network according to Embodiment 11 of the present invention.
  • the synchronization network includes a controller 900 and a synchronization node 1000.
  • the controller 900 includes a first determining unit 901, a generating unit 902, and a first sending unit 903.
  • the synchronization node 1000 includes a second receiving unit 1001 and a locking unit 1002, where:
  • the first determining unit 901 is configured to determine synchronization link topology information of the synchronization network according to physical link topology information of the synchronization network and synchronization information of a synchronization node in the synchronization network.
  • the generating unit 902 is configured to generate a synchronization rule of the synchronization node according to the synchronization link topology information.
  • the first sending unit 903 is configured to send the synchronization rule and/or request message to the second receiving unit according to the synchronization link topology information;
  • the second receiving unit 1001 is configured to receive the synchronization rule and/or request message sent by the first sending unit.
  • the locking unit 1002 is configured to lock an optimal valid reference source according to the synchronization rule, and output reference source information to other ports.
  • the controller 900 further includes a first receiving unit 906 and an updating unit 907;
  • the synchronization node further includes a second determining unit 1003, a switching unit 1004, and a second sending unit 1005, where:
  • the second determining unit 1003 is configured to determine whether an alarm is generated by the input reference source, and if yes, continue to determine whether there are other valid reference sources according to the synchronization rule, and when yes, trigger the switching unit;
  • the switching unit 1004 is configured to switch to an optimal reference source according to the synchronization rule.
  • the second sending unit 1005 is configured to update a local synchronization rule, and send a switching completion message to the first receiving unit 906.
  • the first receiving unit 906 is configured to receive the second sending unit 1005 to send a switching completion message, triggering the updating unit 907;
  • the updating unit 907 is configured to update the synchronization link topology information and a synchronization rule.
  • the first determining unit, the generating unit, the first sending unit, the obtaining unit, the detecting unit, the first receiving unit, and the updating unit in the controller provided by the embodiment of the present invention may be implemented by a processor in the controller;
  • the second receiving unit, the locking unit, the second determining unit, the switching unit, the second sending unit, and the holding unit in the synchronization node provided by the embodiment of the invention may be implemented by a processor in the synchronization node;
  • the functions may also be implemented by specific logic circuits; in a particular embodiment, the processor may be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate array (
  • the FPGA or the like may be a device such as a mobile phone or a tablet computer.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • program codes such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions for performing the application in the controller provided in the embodiments of the present invention.
  • the controller, the synchronization node, and the synchronization network provided by the embodiments of the present invention are only schematic.
  • the division of the unit is only a logical function division, and the actual implementation may have another division manner, such as: Units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.
  • the coupling, or direct coupling, or communication connection of the various components shown or discussed may be indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.
  • the controller, the synchronization node, and the synchronization network provided by the embodiments of the present invention are only schematic, and are also embodied in some more specific contents, and need to refer to the synchronization method of the foregoing embodiment.
  • the above-mentioned units may or may not be physically separated; they may be located in one place or on multiple network devices; for example, the controller and the synchronization node in the embodiment of the present invention may be located on the same network entity device. Because the controller is a logical concept, it may be located on the same network entity device as the synchronization node, or may be located on two network entity devices respectively. Those skilled in the art may select some or all of the units according to actual needs. Come The purpose of implementing the solution of this embodiment is achieved.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated into one unit;
  • the unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes
  • the foregoing storage method includes: a removable storage device, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like.
  • the medium of the program code includes: a removable storage device, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like.
  • the above-described integrated unit of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a standalone product.
  • the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a ROM, a RAM, a magnetic disk, or an optical disk.
  • the controller in the synchronization network determines the synchronization link topology information according to the physical link topology information of the synchronization network and the synchronization information of the synchronization node in the synchronization network; the controller is configured according to the synchronization.
  • Link topology information generating a synchronization rule of the synchronization node; the controller sending the synchronization rule and/or request message to a synchronization node in the synchronization network according to the synchronization link topology information;
  • the synchronous link is quickly switched to meet the real-time performance of the synchronous link switching, thereby effectively improving the synchronization performance of the entire network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

本发明公开了一种同步方法,所述方法包括:控制器根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定同步链路拓扑信息;所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和/或请求消息。本发明同时还公开一种控制器、同步节点和同步网络、存储介质。

Description

同步方法、控制器、同步节点及同步网络、存储介质 技术领域
本发明涉及网络通信领域,尤其涉及一种适用于软件定义网络(SDN,Software Defined Network)的同步方法、控制器、同步节点及同步网络、存储介质。
背景技术
现有的通信网络分组同步网络(PTN,Packet Transport Network)可以分为频率同步网和时间同步网。其中,频率同步网采用同步以太(SyncE,Synchronous Ethernet)网或精确定时协议(PTP,Precision Time Protocol)从物理码流或分组报文中提取时钟信息,并采用同步状态消息(SSM,Synchronization Status Message)进行频率源选择和路径倒换。而时间同步网采用PTP从定时报文中提取时间戳信息,计算出时间偏差并进行时间校准,时间同步网采用PTP选择时间源和进行路径倒换。PTN中存在几千台设备,从而导致维护网络的工作量极大;PTN中的每一台设备都可以作为一个网络节点(NE),一旦PTN中的参考源和/或同步链路发生故障时,在故障发生时由于现有的PTN缺乏有效的的倒换机制,从而无法保证同步链路倒换的实时性。
发明内容
有鉴于此,本发明实施例为解决现有技术中存在的问题而提供一种同步方法、控制器、同步节点及同步网络、存储介质,能够快速地使同步链路进行倒换,从而满足同步链路倒换的实时性,进而有效地提高整网的同步性能。
本发明实施例的技术方案是这样实现的:
第一方面,本发明实施例提供一种同步方法,所述方法包括:
控制器根据同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定所述同步网络的同步链路拓扑信息;
所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和/或请求消息。
第二方面,本发明实施例还提供一种同步方法,所述方法包括:
同步节点接收控制器发送的同步规则和/或请求消息,所述请求消息中携带有所述同步规则;
所述同步节点根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
第三方面,本发明实施例提供一种控制器,所述控制器包括第一确定单元、生成单元和第一发送单元,其中:
所述第一确定单元,配置为根据同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定所述同步网络的同步链路拓扑信息;
所述生成单元,配置为根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
所述第一发送单元,配置为根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和/或请求消息。
第四方面,本发明实施例提供一种同步节点,所述同步节点包括第二接收单元和锁定单元,其中:
所述第二接收单元,配置为接收控制器发送的同步规则和/或请求消息,所述请求消息中携带有所述同步规则;
所述锁定单元,配置为根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
第五方面,本发明实施例提供一种同步方法,所述方法包括:
控制器根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定同步链路拓扑信息;
所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和/或请求消息,所述请求消息中携带有所述同步规则;
所述同步节点接收所述同步规则和/或所述请求消息;
所述同步节点根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
第六方面,本发明实施例提供一种同步网络,所述同步网络包括控制器和同步节点,其中,所述控制器包括第一确定单元、生成单元和第一发送单元,所述同步节点包括第二接收单元和锁定单元,其中:
所述第一确定单元,配置为根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定同步链路拓扑信息;
所述生成单元,配置为根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
所述第一发送单元,配置为根据所述同步链路拓扑信息,向所述第二接收单元发送同步规则和/或请求消息,所述请求消息中携带有所述同步规则;
所述第二接收单元,配置为接收所述第一发送单元发送的所述同步规则和/或所述请求消息;
所述锁定单元,配置为根据所述同步规则,锁定最佳的有效参考源, 并向其它端口输出参考源信息。
第七方面,本发明实施例提供一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,该计算机可执行指令用于执行本发明实施例第一方面提供的同步方法,
和/或,
该计算机可执行指令用于本发明实施例第二方面提供的同步方法。
本发明实施例提供的同步方法、控制器、同步节点及同步网络、存储介质,其中,同步网络中的控制器根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定同步链路拓扑信息;所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送所述同步规则和/或请求消息;如此,能够快速地使同步链路进行倒换,从而满足同步链路倒换的实时性,进而有效地提高整网的同步性能。
附图说明
图1-1为相关的PTN中同步链路发生故障时的结构示意图;
图1-2为相关的PTN中同步链路发生故障时进行倒换的流程示意图;
图1-3为相关的SDN中同步链路发生故障时进行倒换的流程示意图;
图2-1为本发明实施例一同步方法的实现流程示意图一;
图2-2为本发明实施例一同步方法的实现流程示意图二;
图2-3为本发明实施例一同步方法的实现流程示意图三;
图2-4为本发明实施例二同步方法的实现流程示意图一;
图2-5为本发明实施例二同步方法的实现流程示意图二;
图3为本发明实施例三同步方法的时序示意图;
图4为本发明实施例四同步方法的时序示意图;
图5为本发明实施例五同步方法的时序示意图;
图6为本发明实施例六同步方法的时序示意图;
图7-1为本发明实施例七网络未出现异常时的网络结构示意图;
图7-2为本发明实施例七网络出现异常时的网络结构示意图一;
图7-3为本发明实施例七网络出现异常时的网络结构示意图二;
图8-1为本发明实施例八网络出现异常时的网络结构示意图一;
图8-2为本发明实施例八网络出现异常时的网络结构示意图二;
图8-3为本发明实施例八网络出现异常时的网络结构示意图三;
图9-1为本发明实施例九控制器的组成结构示意图一;
图9-2为本发明实施例九控制器的组成结构示意图二;
图9-3为本发明实施例九控制器的组成结构示意图三;
图10-1为本发明实施例十同步节点的组成结构示意图一;
图10-2为本发明实施例十同步节点的组成结构示意图二;
图10-3为本发明实施例十同步节点的组成结构示意图三;
图11-1为本发明实施例十一同步网络的组成结构示意图一;
图11-2为本发明实施例十一同步网络的组成结构示意图二。
具体实施方式
在PTN中,当参考源或同步链路发生故障,同步节点通过运行参考源选择算法选择最佳的输入参考源(可简称为参考源),并尽快切换到新的最佳的输入参考源上,其中所述选择算法包括基于SSM的SSM协议或者PTP。在如图1-1所示的PTN网络一共包括11个节点NE1至NE11、以及主备两个时钟参考源简称为主、被参考源,其中,每一节点NE都包括两个以上的端口,在图1-1中仅示出两个或者三个节端口,例如节点NE1具有三个端口,包括:一个用于连接主参考源的输入端口即图1-1中NE1的锁定端口、分别用于连接节点NE2和NE3的两个输出端口即NE1的两个输出端口;在图1-1中锁定端口用实心的圆点表示,而输出端口用空心的原点来表示, 输出端口又称导出端口。在图1-1中的每一条同步链路上都标注有时钟质量等级(QL),在ITU-TG707标准中,定义SSM中的S1字节来传递同步状态信息,SSM的QL等级由高到低为:QL=0000=0表示同步质量不可知;QL=0010=2表示一级时钟;QL=0100=4表示二级时钟;QL=1000=8表示三级时钟;QL=1011=11表示同步数字体系(SDH,Synchronous Digital Hierarchy)设备时钟;QL=1111=15表示不可用,即不可用作同步时钟。由于当前采用QL=2的主参考源,因此,图1-1中同步链路的QL=2。假设节点NE3的输入参考源发生故障,如节点NE1与节点NE3之间的同步链路发生故障时,节点NE3需要尽快切换到新的参考源上,即进入步骤S100的倒换的步骤,对于节点NE3的倒换时间要求在几百毫秒(ms)内完成,否则将影响节点NE3的所有下游节点的同步性能。
如图1-2所示,当节点NE3和节点NE5之间的链路发生故障,此时会通过携带有故障信息的SSM消息传递给节点NE5,在节点NE5将根据SSM协议运行参考源选择算法,经过该算法计算后发现节点NE5没有更好的参考源,则节点NE5进入保持状态。节点NE5进入如步骤S101的降质通告的步骤,包括:节点NE5将向下游通告降质后的时钟质量等级(QL=11,即SDH设备时钟);由于没有更好的参考源,下游节点NE6和NE7将继续锁定NE5,并向下游通告降级的参考源时钟质量等级(QL=11);携带QL=11的SSM消息逐跳传递到节点NE8,节点NE8将根据SSM协议运行参考源选择算法,经过该算法计算后将选择QL=2的参考源,节点NE8将锁定节点NE9方向的参考源。然后,节点NE5进入如步骤S102所示的保护倒换步骤,包括:节点NE8将向下游通告新的参考源质量等级(QL=2);携带QL=2的SSM消息逐跳通告到节点NE7、节点NE6和节点NE5,节点NE7至NE5运行参考源选择算法,将逐个倒换到新的参考源。上述SSM消息的逐跳传递存在一定的延迟,总的倒换延迟随跳数增加,从而影响频率同步 性能和时间同步性能。
另外,如果故障节点下游没有备选参考源,但具有更高质量的同步节点,这时需要尽快通知该故障节点进入保持状态。如图1-2所示,当节点NE3和节点NE5之间的链路发生故障,而对于节点NE5的下游节点NE6至NE8来说,节点NE6至NE8均没有备选参考源,但是NE8具有比质量等级QL=11更高的质量等级QL=2的同步节点NE9,但采用如图1-2中的逐跳转发机制存在一定的延迟,也不能尽快通告末端的时间从时钟(TSC,Time Slave Clock)节点NE8进入保持模式。
针对如图1-1和图1-2中问题,在SDN技术中采用了控制和转发分离的架构,即由控制器计算同步链路拓扑,由同步设备完成频率同步和/或时间同步。但同步链路的保护倒换有严格的时间要求,要求在故障情况下能尽快切换到备份的同步链路,以满足现有标准规范的性能指标要求。但采用SDN方式部署同步网,如果完全由控制器进行同步链路倒换,由于控制器和设备之间消息延迟和处理延迟的不确定性,使得同步链路的倒换实时性难于满足。如图1-3所示,假设节点NE3与节点NE5之间的链路发生故障,然后节点NE5进入如步骤S103的进入保持的步骤,接着,同步网络进入步骤S104的QL降级,逐跳通告的步骤;由于开始时节点NE8锁定节点NE7,然后控制器命令节点NE8和节点NE7倒换,但由于通信延迟的不确定性,节点NE7先进行倒换,从而导致节点NE7将锁定节点NE8,但这时节点NE8仍锁定节点NE7,从而导致节点NE7和节点NE8同步链路互锁,虽然互锁时间短暂,但还是会给整个同步网的性能到来不确定的影响因素。
下面结合附图和具体实施例对本发明的技术方案进一步详细阐述。
实施例一
本发明实施例一提供一种同步方法,应用于同步网络中的控制器;作为优选的实施例,该同步网络可以是SDN,对应地,该控制器可以为SDN 中的控制器;图2-1为本发明实施例一同步方法的实现流程示意图一,如图2-1所示,该方法包括:
步骤S211,同步网络中的控制器根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定所述同步网络的同步链路拓扑信息;
这里,所述同步信息至少包括以下信息至少之一:时钟质量等级QL信息、端口优先级信息、跳数信息、同步能力信息等。
所述同步网络中的节点是指,由所述控制器所控制的同步节点,也就是说,控制器根据同步网络的物理链路信息和由所述控制器所控制的同步节点的同步信息,来确定所述同步网络的同步链路拓扑信息。所述同步能力信息能够表明同步节点是否具有支撑频率同步和/或时间同步的能力,进一步来说,能够表明同步节点的端口是否具有支撑频率同步和/或时间同步的能力。
步骤S212,所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
这里,所述同步规则也可以称为同步策略,所述同步规则中包括该同步节点的输入输出的端口信息、以及端口优先级信息、各输入参考源的标识(ID)信息(可选)、各输入参考源的质量等级信息(可选)、以及各输入参考源的优先级信息等。本发明各实施例提供的同步方法以及装置、同步网络可以适用于时间同步网,也可以适用于频率同步网,也可以同时适用于频率同步网和时间同步网。当本发明的各实施例实施于时间同步网时,所述同步规则还包括各个输入输出接口/端口的定时报文的发送速率和工作模式如单步法、两步法等,其中定时报文的类型包括Sync、Follow_up、Delay_req、Delay_resp、Pdelay_req、Pdelay_resp等。
这里,所述同步规则,包括以下中的至少之一种策略:
所述同步节点的输入参考源无告警时的策略;
所述同步节点的输入参考源出现告警时的策略;
所述同步节点收到下游节点的倒换消息时的策略,所述倒换消息用于指示所述同步节点如何进行倒换。
步骤S213,所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送所述同步规则和/或请求消息。
这里,所述请求消息用于指示由所述控制器控制的同步节点根据同步规则建立同步链路;
这里,所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送所述同步规则和/或请求消息,包括:
所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送所述同步规则;或者,
所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送请求消息;或者,
所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和请求消息。
其中,所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和请求消息,包括:
所述控制器根据所述同步链路拓扑信息,先向所述同步网络中的同步节点发送同步规则,然后向所述同步网络中的同步节点发送请求消息,该请求消息中不携带所述同步规则。
其中,作为优选的实施例,所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和请求消息,包括:
所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送请求消息,所述请求消息中携带有所述同步规则。
本发明实施例中,在所述步骤S211之前,如图2-2所示,所述方法还包括:
步骤S210,上电启动后,所述控制器获取所述同步网络中同步节点的同步信息,并检测同步节点之间端口的物理连接关系,获得所述物理链路拓扑信息。
本发明实施例中,在除了图2-2所示的步骤外,如图2-3所示,在步骤S213之后,所述方法还包括:
步骤214,所述控制器接收所述同步节点发送的倒换完成消息后,更新所述同步链路拓扑信息和/或同步规则。
所述步骤S214,包括:
所述控制器接收所述同步节点发送的倒换完成消息后,更新所述同步链路拓扑信息;或者,
所述控制器接收所述同步节点发送的倒换完成消息后,更新所述同步规则;或者,
所述控制器接收所述同步节点发送的倒换完成消息后,更新所述同步链路拓扑信息和所述同步规则;
这里,本实施例中提供两种更新所述同步链路拓扑信息和同步规则的方式,其中第一种方式包括:
步骤A1,所述控制器根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,更新同步链路拓扑信息;
步骤A2,所述控制器根据同步链路拓扑信息更新同步规则。
当所述倒换完成消息中携带有所述最佳参考源的标识信息;对应地,所述第二种方式包括步骤B:所述控制器根据最佳参考源的标识信息,更新同步链路拓扑信息和同步规则。
本发明实施例中,所述方法还包括:
所述控制器根据更新后的同步链路拓扑信息,确定需要进行重新同步的同步节点;
所述控制器将更新后的同步链路的拓扑结构信息和同步规则携带于建立请求消息中,发送给所述需要进行重新同步的同步节点。
本发明实施例中,所述方法还包括:
所述控制器接收所述同步节点发送的用于表明不存在其它有效的参考源的故障消息;
所述控制器判断所述同步节点的所有下游节点是否存在备选的参考源,是时,向具有备选参考源的下游节点发送用于指示倒换到备用参考源的倒换请求消息。
本发明实施例中,所述方法还包括:
所述控制器判断所述同步节点的所有下游节点不存在备选的参考源时,确定所述同步节点的下游节点中具有更高质量等级或更好保持性能的时钟的第一下游节点;
所述控制器向所述第一下游节点发送保持请求消息,以请求所述第一下游节点进入保持模式。
实施例二
本发明实施例二提供一种同步方法,应用于同步网络中的同步节点;作为优选的实施例,该同步网络可以是SDN,对应地,该同步节点可以为SDN中的同步节点;图2-4为本发明实施例二同步方法的实现流程示意图一,如图2-4所示,该方法包括:
步骤S221,同步网络中的同步节点接收所述同步网络中的控制器发送的同步规则和/或请求消息;
这里,所述同步节点接收所述同步网络中的控制器发送的同步规则和/或请求消息,包括:
所述同步节点接收所述同步网络中的控制器发送的同步规则;或者,
所述同步节点接收所述同步网络中的控制器发送的请求消息;或者,
所述同步节点接收所述同步网络中的控制器发送的同步规则和请求消息。
其中,所述同步节点接收所述同步网络中的控制器发送的同步规则和请求消息,包括:
同步节点接收所述同步网络中的控制器发送的同步规则,然后再接收所述控制器发送的用于建立同步链路的请求消息。
其中,所述同步节点接收所述同步网络中的控制器发送的同步规则和请求消息,包括:同步节点接收所述同步网络中的控制器发送的请求消息,所述请求消息中携带有所述同步规则。
步骤S222,所述同步节点根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
这里,所述参考源信息包括频率和/或时间信息;所述锁定最佳的有效参考源,包括锁定最佳的有效参考源的输入端口的频率和/或时间。
这里,最佳的有效参考源可以是优先级最高的输入参考源,也可以是质量等级信息最高的输入参考源,本领域的技术人员还可以根据各种现有技术来确定最佳的有效参考源,因此不再赘述。
本发明实施例中,在所述步骤S222之后,如图2-5所示,该方法还包括:
步骤S223,所述同步节点判断输入参考源是否出现告警,是时,根据所述同步规则继续判断是否存在其它有效的参考源;
步骤S224,所述同步节点根据所述同步规则确定存在其它有效的参考源时,根据所述同步规则倒换到最佳的参考源。
本发明实施例中,在步骤S224发生的同时,该方法还包括:
所述同步节点更新本地的同步规则,并向所述控制器发送倒换完成消息。
这里,控制器在接收到倒换完成消息之后,才会更新同步链路拓扑信息以及同步规则。
这里,所述倒换完成消息只携带倒换完成标识,该倒换完成标识只用于向控制器通告本同步节点已倒换完成,此时,由于控制器本身包括有物理链路拓扑信息、所有节点的同步信息,因此,控制器可以根据步骤S211的记载进行更新同步链路拓扑信息,以及根据步骤S212的记载进行更新同步规则。可见,该方式中更新同步链路拓扑信息和同步规则都是在控制器端完成的,因而适合于同步节点的数量不是巨大的同步网络。
所述倒换完成消息除携带倒换完成标识外,还可以携带最佳参考源的标识信息;该携带有两种标识的方式与前一种只携带倒换完成标识的方式相比,由于倒换完成消息携带有倒换完成标识,从而控制器可以根据倒换完成标识更有针对性的对同步链路拓扑信息和同步规则进行更新,因而可以实现快速地更新,而且,由于在更新同步链路拓扑信息和同步规则时控制器消耗的计算能力相对减弱,因此带有两种标识的方式适合于同步节点的数量巨大的同步网络。
本发明实施例中,所述方法还包括:
所述需要进行重新同步的同步节点接收所述控制器发送的请求消息,其中所述请求消息中携带有更新后的同步链路拓扑信息和同步规则;
所述需要进行重新同步的同步节点根据同步规则锁定最佳的有效参考源,并向其它端口输出参考源信息。
本发明实施例中,所述方法还包括:
所述同步节点当根据所述同步规则确定不存在其它有效的参考源时,进入保持模式,并向所述控制器发送用于表明不存在其它有效的参考源的 故障消息。
本发明实施例中,所述方法还包括:
接收所述控制器发送的用于指示倒换到备用参考源的倒换请求消息后,所述同步节点倒换到备选参考源,并向上游的第一个同步节点发送用于指示倒换的倒换消息。
本发明实施例中,所述方法还包括:
所述上游的第一个同步节点接收到所述倒换消息后,根据所述同步规则判断接收到所述倒换消息的输入端口是否合法;
判断不合法时,丢弃所述倒换消息;
判断合法时,根据同步规则进行参考源倒换,并向所述控制器发送倒换完成消息;并在确定其自身存在有效的输入参考源时,向具有有效的输入参考源的端口转发所述倒换消息以通告上游节点,或延迟一段时间后再向所述具有有效的输入参考源的端口转发所述倒换消息以通告上游节点;在确定其自身不存在有效的输入参考源时,不转发所述倒换消息。
实施例三
本发明实施例三提供一种同步方法,应用于同步网络,所述同步网络包括控制器300和由所述控制器300控制的若干个同步节点380;作为优选的实施例,该同步网络可以是SDN;图3为本发明实施例三同步方法的时序示意图,如图3所示,该方法包括:
步骤S311,获得物理链路拓扑信息;
具体地,控制器300获取同步网络中所有同步节点的同步信息,并检测所有同步节点之间端口的物理连接关系,获得所述物理链路拓扑信息。优选地,该步骤是在同步网络上电启动时执行。
步骤S312,确定同步链路拓扑信息;
具体地,同步网络中的控制器根据所述同步网络的物理链路拓扑信息、 所述同步网络中同步节点的同步信息,确定所述同步网络的同步链路拓扑信息;
这里,所述同步信息至少包括以下信息至少之一:时钟质量等级QL信息、端口优先级信息、跳数信息、同步能力信息等。
步骤S313,生成同步规则;
所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
步骤S314,发送请求消息;
具体地,所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送用于建立同步链路的请求消息,其中所述请求消息携带有所述同步规则。
这里,在步骤S314中的所述请求消息也可以不携带步骤S313中生成的同步规则,对应地,在步骤S313中还包括向同步节点发送同步规则的步骤。
这里,本实施例中还可以不向同步节点发送请求消息,只向同步节点发送同步规则,而同步节点在收到同步规则后就开始执行步骤S315。
这里,所述同步规则,包括以下中的至少之一种策略:
所述同步节点的输入参考源出现告警时的策略;具体地,当同步节点检测到告警时,该同步节点先判断其自身是否有多个有效参考源,是时,则根据同步规则倒换到最佳的参考源上,并发送倒换完成消息通告控制器;反之,该同步节点则进入保持模式,并发送告警消息通告控制器。
所述同步节点收到下游节点的倒换消息时如何转发的策略,所述倒换消息用于指示所述同步节点如何进行倒换。具体地,当同步节点收到下游节点发送的倒换消息,则根据同步规则对倒换消息进行合法性判断。当判断倒换消息不合法时,则不进行倒换。当判断倒换消息合法时,则根据倒 换消息进行倒换,并通告控制器;然后判断倒换后的输入源状态是否有效,当确定输入源的状态有效时,则继续往输出端口发送倒换消息,否则不发送倒换消息。
步骤S315,锁定和输出;
具体地,各同步节点380收到所述请求消息后,将根据同步规则锁定最佳的有效参考源输入端口的频率和/或时间信息,并向本同步节点中的其它输出端口输出频率和/或时间信息。
需要说明的是,本实施例中的步骤S314,也可以拆分为两个步骤,其中第一个步骤中,控制器300将所述同步规则发送给各同步节点380;第二个步骤中,控制器300将用于建立同步链路的请求消息发送给各同步节点380,这样,在第二个步骤中所述请求消息中也可以不携带同步规则。
实施例四
本发明实施例四提供一种同步方法,应用于同步网络,所述同步网络包括控制器400和由所述控制器400控制的若干个同步节点;本实施例四中的同步方法在包括如图3所示步骤S311至S315之后,如图4所示,该方法还包括:
步骤S411,同步节点410检测到告警;
具体地,由所述控制器400控制的同步节点410检测到输入源故障,即该同步节点410检测告警;
步骤S412,同步节点410判断是否存在有效的参考源,是时,进入步骤S413;
具体地,同步节点410根据同步规则判断其自身是否具有其他有效的输入参考源,是时,进入步骤S413;
步骤S413,同步节点410倒换到最佳的参考源,并更新本地同步规则;
具体地,同步节点410根据同步规则判断其自身中存在其它有效的输 入参考源,则根据同步规则中输入参考源的优先级信息倒换到最佳的输入参考源上,倒换完后更新本地同步规则;
步骤S414,同步节点410向控制器400发送倒换完成消息;
这里,同步节点410向控制器400发送的倒换完成消息可以参见实施例二,因此不再赘述。
步骤S415,控制器400更新同步链路拓扑信息和同步规则;
这里,控制器400更新同步链路拓扑信息和同步规则具体参见实施例二,因此不再赘述;这里,所述控制器400还需要根据更新后的同步链路拓扑信息,确定需要进行重新同步的同步节点。
步骤S416,控制器400向需要进行重新同步的同步节点420发送请求消息;
具体地,所述控制器400将更新后的同步链路的拓扑结构信息和同步规则携带于建立请求消息中,发送给所述需要进行重新同步的同步节点420。
步骤S417,需要进行重新同步的同步节点420进行锁定和输出;
具体地,所述需要进行重新同步的同步节点420接收所述控制器发送的请求消息,其中所述请求消息中携带有更新后的同步链路拓扑信息和同步规则;
所述需要进行重新同步的同步节点根据同步规则锁定最佳的有效参考源输入端口的频率和/或时间,并向其它端口输出频率和/或时间信息。
实施例五
本发明实施例五提供一种同步方法,应用于同步网络,所述同步网络包括控制器500和由所述控制器500控制的若干个同步节点;本实施例五中的同步方法在包括如图3所示步骤S311至S315之后,如图5所示,该方法还包括:
步骤S511,同步节点510检测到告警;
具体地,由所述控制器500控制的同步节点510检测到输入源故障,即该同步节点510检测告警;
步骤S512,同步节点510判断是否存在有效的参考源,否时,进入步骤S513;
具体地,同步节点510根据同步规则判断其自身是否具有其他有效的输入参考源,否时,进入步骤S513;
步骤S513,同步节点510进入保持模式;
具体地,同步节点510在判断其自身没有有效的输入参考源时,同步节点510中的锁相环将进入保持模式或者保持状态;该步骤S513中同步节点510中的锁相环将进入保持模式或者保持状态属于现有技术,因此不再赘述。
步骤S514,同步节点510向控制器500发送故障消息;
具体地,同步节点510在进入保持模式后,将发送故障消息给控制器500;
这里,所述故障消息用于表明同步节点510出现告警情况,即同步网络出现异常;控制器500通过故障消息获知同步节点510出现异常,可见,该故障消息将同步倒换的控制权由同步节点510交给控制器500,在后续的步骤中将由控制器500进行同步链路倒换。其中,该故障消息将同步倒换的控制权由同步节510交给控制器500,具体可以这样理解:在本发明实施例四,当同步节点510判断其自身具有有效的输入参考源时,同步倒换的控制权是由其自身同步节点510掌握的;而在本实施例五步骤S512中,由于同步节点510判断其自身没有有效的参考源,因此需要将同步倒换的控制权交给控制器500。
步骤S515,控制器500判断下游所有节点中是否存在具有备选参考源 的节点,是时,进入步骤S516;
具体地,控制器500在收到同步节点510发送的故障消息之后,将判断同步节点510下游的所有节点中是否存在具有备选参考源的节点,假设同步节点510的下游节点中具有备选参考源的节点为同步节点520,是时,进入步骤S516;
步骤S516,控制器500向下游节点520发送倒换请求消息;
这里,所述倒换请求消息用于请求有备选的输入参考源的下游节点倒换到备选的输入参考源,并用于请求该具有备选的输入参考源的下游节点向其第一个上游节点发送倒换消息;具体以本实施例中的同步节点520来说,该倒换请求消息用于下游节点520倒换到备选的输入参考源,并用于请求下游节点520向节点520的第一个上游节点530发送倒换消息,这里假设下游节点520的第一个上游节点为同步节点530。
步骤S517,同步节点520倒换到备选参考源;
这里,同步节点520接收控制器500发送的倒换请求消息;所述倒换请求消息中还可以携带备选参考源的标识信息,也可以不携带备选参考源的标识信息;当倒换请求消息携带有备选参考源的标识信息时,同步节点520根据所述备选参考源的标识信息倒换到备选的输入参考源上;当倒换请求消息不携带有备选参考源的标识信息时,同步节点520根据同步规则倒换到备选的输入参考源上。
步骤S518,同步节点520向控制器500发送倒换完成消息;
这里,同步节点520向控制器发送的倒换完成消息,可以参见上述的实施例二,因此不再赘述。
步骤S519,控制器500更新同步链路拓扑信息和同步规则;
这里,步骤S518具体可以参见上述实施例二,因此不再赘述;另外,步骤S518与步骤S19是相互关联的,即步骤S518发生在前,而步骤S519 发生在后。
步骤S520,同步节点520向同步节点530发送倒换消息;
这里,所述同步节点530为同步节点520上游的第一个节点;
这里,所述倒换消息用于指示上游的第一个节点进行倒换;另外,步骤S520与S518之间并无先后的关联,可以发生在步骤S518之前,也可以发生在步骤S518之后。
步骤S521,同步节点530验证合法性,是时,进入步骤S522;
具体地,同步节点530接收到同步节点520发送的倒换消息后,将所接收的倒换消息进行合法性验证,即:根据同步规则中输出端口信息,检查倒换消息输入端口的合法性,是时,同步节点530继续根据同步规则判断其自身是否具有有效的输入参考源,即判断链路是否出现故障,如果有输入参考源,即表明链路是正常的,则向输出端口转发倒换消息(进入步骤S522);否时,进入步骤S523。
这里,所述步骤S521为可选步骤,也可以不进行验证,直接向上游节点发送倒换消息。
步骤S522,同步节点520向同步节点540发送倒换消息;
这里,所述同步节点540为同步节点530上游的第一个节点,也即同步节点530上游的第二个节点;此时,同步节点540依然会验证倒换消息的合法性,合法时,同步节点540继续向其的第一上游节点发送倒换消息,然后同步节点540的第一上游节点验证倒换消息的合法性,依次类推,直至该倒换消息向上游节点传递到同步节点510时为止。
步骤S523,同步节点530向控制器500发送非法消息;
具体地,同步节点530在验证所收到的倒换消息为非法时,向控制器500发送非法消息,该非法消息用于表明同步节点530出现异常,控制器500通过非法消息获知同步节点530出现异常,可见,该非法消息将同步倒 换的控制权由同步节点530交给控制器500,在后续的步骤中将由控制器500进行同步链路倒换,后续更为具体的步骤将在后面的实施例六中详述。
本发明实施例五中,在故障传递的过程中,通过故障消息直接传递到控制器,然后交由控制器500进行链路倒换的决策;这样,可以快速地将网络出现异常的节点或链路传递给控制器,从而交由控制器进行快速地倒换,从而避免有关技术中采用逐跳传输方式进行故障传递的弊端。其中,故障传递过程是指:同步节点510出现告警,且同步节点510其自身没有备用的输入参考源时,同步节点510向控制器500发送故障消息的过程。采用逐跳传输方式进行故障传递的弊端在于,在逐跳传输的过程,在每一节点均需要保持一个延迟时间,总的倒换延迟将随跳数的增加而增加,这样将很难保证满足倒换时间要求在几百毫秒(ms)内的要求,从而影响频率同步性能和时间同步性能。
本发明实施例五中,在链路同步的过程中又采用了逐跳传输的方式,在逐跳传输的过程中可以不维持每一同步节点的延迟时间,即接收到倒换消息后在确定该倒换消息为合法时,直接将该倒换消息传递给下一同步节点;在总的倒换时间允许的情况下,该延迟时间也可以在每一同步节点上进行维持;具体是否维持该延迟时间,控制器可以根据跳数进行判断,如果跳数在阈值范围内,则可以进行维持,若不在阈值范围内,不进行维持。之所以在链路同步的过程中采用逐跳传输的方式,这样可以避免链路互锁的情况发生。
实施例六
本发明实施例六提供一种同步方法,应用于同步网络,所述同步网络包括控制器600和由所述控制器600控制的若干个同步节点;本实施例六中的同步方法在包括如图3所示步骤S311至S315之后,如图6所示,该方法还包括:
步骤S611,同步节点610检测到告警;
具体地,由所述控制器600控制的同步节点610检测到输入源故障,即该同步节点610检测告警;
步骤S612,同步节点610判断是否存在有效的参考源,否时,进入步骤S613;
具体地,同步节点610根据同步规则判断其自身是否具有其他有效的输入参考源,否时,进入步骤S613;
步骤S613,同步节点610进入保持模式;
具体地,同步节点610在判断其自身没有有效的输入参考源时,同步节点610中的锁相环将进入保持模式或者保持状态。
步骤S614,同步节点610向控制器600发送故障消息;
步骤S615,控制器600判断下游所有节点中是否存在具有备选参考源的节点,否时,进入步骤S616;
具体地,控制器600在收到同步节点610发送的故障消息之后,将判断同步节点610下游的所有节点中是否存在具有备选参考源的节点,假设同步节点610的下游节点中具有备选参考源的节点为同步节点620,否时,进入步骤S616;
步骤S616,控制器600确定具有更高QL或更好保持性能的时钟的同步节点;
具体地,控制器600在同步节点610的下游所有节点中,确定具有更高QL或更好保持性能的时钟的同步节点,假设该具有更高QL或更好保持性能的时钟(晶振)的同步节点为节点620;
步骤S617,控制器600向同步节点620发送保持请求消息;
这里,所述保持请求消息指示所述同步节点620进入保持模式。
步骤S618,同步节点620进入保持模式;
步骤S619,同步节点620向控制器600发送状态通告消息;
这里,同步节点620向控制器发送的状态通告消息,用于表明所述同步节点620已经进入保持模式。
本发明实施例四、五和六中,控制器400、500和600只是在不同的实施例中采用不同的标号来表示而已,实际上控制器400、500和600指代的为同一对象,例如控制器400、500和600都可以指代同一SDN中的控制器;同步节点410、510和610也指代同一同步节点,即同一SDN中发生告警的同步节点。
需要说明的是,本发明上述实施例提供的同步方法不仅适用于频率同步网(SyncE、PTP),而且适用于时间同步网(PTP)。
实施例七
本发明实施例提供的一种同步方法,应用于同步网络,该方法包括以下步骤:
步骤C1,同步网络中的控制器和同步节点上电启动后,所有同步节点将和控制器建立传输控制协议(TCP,Transmission Control Protocol)TCP/安全套接层协议层(SSL,Secure Sockets Layer)连接,控制器获得同步节点的节点信息;
这里,所述节点信息包括介质访问控制(MAC,Media Access Control)地址、网络之间互连的协议(IP,Internet Protocol)地址、设备能力参数、端口配置参数等;其中端口(P,Port)是指节点的输入(I,Input)端口或输出(O,Output)端口,在图7-1至7-3以及8-1至8-2中,输入端口简写为入或I,而输出端口简写为出或O。
步骤C2,控制器通过发送链路层发现协议(LLDP,Link Layer Discovery Protocol)报文,来检测同步网络中所有同步节点之间端口物理连接关系,从而控制器获得同步网络的物理链路拓扑信息;
这里,参见图7-1,控制器过发送LLDP报文,检测到如图7-1所示的同步网络的物理链路拓扑结构包括两个环形链路,其中,一个环形链路是指节点NE1至NE4组成的环形链路,另一个环形链路是指NE3至NE11组成的环形链路。
步骤C3,控制器基于时钟/时间源的质量等级(QL)信息、同步节点的QL信息、同步端口的本地优先级和跳数等信息,确定出同步链路拓扑信息;
这里,同步链路拓扑信息所表示的同步链路拓扑结构是一种无环形链路的拓扑结构;而前述的物理链路拓扑信息所表示的物理链路拓扑结构是一种包括环形链路的拓扑结构。在图7-1中,同步端口的本地优先级简写为优先级,并用阿拉伯数字1、2、3等来表示,其中表示优先级的数字越小,其代表的优先级等级越高,即优先级为1时表示最高的优先级。
这里,仍以图7-1为例,如图7-1所示,控制器确定的同步链路拓扑结构如黑色实线所示,其中黑色实线的箭头方向为参考源的传递方向;黑色点划线为破环点,即:节点NE3与节点NE4之间的链路为破环点,以及节点NE8与节点NE9之间的链路为破环点;
步骤C4,控制器根据物理链路拓扑信息和同步链路拓扑信息,生成同步节点同步规则,并下发该同步规则给同步节点;
这里,以同步节点NE3为例,来说明控制器向同步节点下发同步规则。控制器向节点NE3下发的同步规则如图7-1所示,NE3的端口(P,Port)31和P32为参考源的输入端口,但P31的参考源的优先级比P32的优先级高,这里依然假定数字越小,所表示的优先级越高,因此,节点NE3从P31获取输入参考源;同时,节点NE3的两个输入端口P31和P32的参考源都有效,表明都没有告警等故障发生;另外,P33为输出端口,用于向下游输出频率和/或时间信息;
步骤C5,控制器向同步节点下发用于建立同步链路的请求消息给各个同步节点,以建立全网的频率和/或时间的同步链路;各同步节点接收到所述请求消息后,将根据同步规则锁定最高优先级的参考源,并向其它端口发送频率和/或时间信息;
如图7-1,控制器确定出同步拓扑结构信息后,发送用于建立同步链路的请求消息给同步节点NE3(参见虚线L701);同步节点NE3收到所述请求消息后,将根据同步规则锁定对应的参考源输入端口,即锁定P31,并向其它端口即P33和P32输出频率和/或时间信息;
步骤C6,当同步节点检测到当前输入源故障后,如果同步规则中存在其它有效的参考源,则根据优先级倒换到最佳参考源,倒换完后更新本地同步规则,并发倒换完成消息通知控制器;
控制器更新同步链路拓扑信息和同步规则,并建立新的同步链路;
这里,可参见图7-2所示,先以NE3节点为例,假如节点NE3的输入源失效,即节点NE3进入如步骤S721所示的告警检测步骤;
其次,节点NE3进入如步骤S722所示的本地倒换的步骤,包括:节点NE3根据同步规则判断其自身具有其它有效的参考源,则按同步规则倒换到P32;
再次,节点NE3进入如步骤S723所示的倒换通告的步骤,包括:节点NE3在倒换完成后,发送倒换完成消息通告控制器。
然后,控制器进入如步骤S724所示的拓扑重计算的步骤,包括:接收到所述倒换完成消息后,控制器重新确定出同步链路拓扑信息;以及重新生成同步节点同步规则;
最后,控制器进入如步骤S725所示的拓扑更新和同步规则更新的步骤,包括:控制器重新计算拓扑结构后,发现节点NE7和节点NE8的拓扑发生变化,则更新NE7和NE8的同步规则,并建立新的同步链路;而其它节点 的拓扑结构和同步规则保持不变。
步骤C7,当同步节点检测到当前输入源故障后,如果同步规则无其它有效参考源,则该同步节点进入保持状态,然后发送故障消息给控制器,由控制器进行同步链路倒换;
这里,还可参见图7-3,以节点NE6为例,假如NE6输入参考源失效,即节点NE6首先进入如步骤S731所示的进入保持的步骤,即:NE6检查同步规则中没有其他有效的输入参考源,则节点NE6进入保持状态;
其次,节点NE6进入如步骤S732所示的告警通告的步骤,包括:节点NE6发送故障消息通告给控制器,由控制器进行同步链路的处理;
然后,控制器进入如步骤S733所示的拓扑重计算的步骤,包括:接收到所述故障消息后,控制器重新确定出同步链路拓扑信息;以及重新生成同步节点同步规则;
最后,控制器进入如步骤S734所示的倒换请求的步骤,包括:控制器重新计算拓扑结构后,控制器发现节点NE6的下游节点NE8具有备选的参考源,则向节点NE8发送倒换请求消息,该倒换请求消息用于指示节点NE8倒换到节点NE9,以及指示NE8向上游节点NE7发送倒换消息。
本发明实施例七中,上述的倒换过程属于实时倒换过程,一方面,同步节点只要发现本地具有备用的输入参考源,就立即进行本地倒换,并在倒换完成后通告控制器,以进行拓扑更新和同步规则的更新;另一方面,当同步节点发现本地没有备用的输入参考源时,则立即发送故障消息通告控制器,由控制器进行同步链路的倒换。可见,本实施例中,无论是在本地倒换完成后的通告,还是故障通告,都是直接与控制器进行交互,从而能够保证链路同步的实时性。
实施例八:
本实施例提供一种同步方法,应用于同步网络,该同步网络包括控制 器,以及由该控制器控制的若干同步节点;该方法包括:
本实施例的前5个步骤D1至D5可以相应地参见实施例七中的C1至C5,因此,不再赘述。
步骤D6,当同步节点的当前输入参考源失效,则检查同步规则中是否存在其它有效的参考源;如果没有,则该同步节点首先进入保持状态,并更新同步规则;然后发送故障消息给控制器,由控制器进行同步链路处理;
这里,参见图8-1,假如节点NE5的当前输入参考源失效,节点NE5进入如步骤S811所所示的进入保持的步骤,包括:节点NE5检查发现同步规则中没有其它可用的输入参考源,则NE5进入保持状态,并更新同步规则;
然后,节点NE5进入如步骤S812所示的告警通告的步骤,包括:节点NE5通过故障消息通告给控制器,由控制器进行同步链路的处理;
步骤D7,控制器收到故障消息,则检查该同步节点下游所有节点是否存在备选的输入参考源,如果有,进入步骤D81;如果没有进入步骤D82;
D81,控制器向具有备选的输入参考源的节点发送倒换请求消息,然后进入步骤D9;
其中,所述倒换请求消息用于请求有备选的输入参考源的节点倒换到备选参考源,并用于请求该具有备选的输入参考源的节点向上游节点发送倒换消息;
这里,继续承接步骤D6中的例子,参见图8-1,控制器进入如步骤S813所示的拓扑重计算的步骤,包括:
控制器收到节点NE5的故障消息,首先更新节点NE5的同步规则,检查节点NE5的所有下游节点中是否存在具有备选的输入参考源的节点,经过检查发现下游节点NE8具有备选的输入参考源;
然后,控制器进入步骤S814所示的倒换请求的步骤,包括:控制器向 节点NE8发送倒换请求消息,该倒换请求消息用于请求有同步节点NE8倒换到备选参考源,并用于请求该同步节点NE8向上游节点NE7发送倒换消息,以通知同步节点NE7进行同步链路倒换;
另外,在该步骤D71中,控制器还需要通知拓扑发生变化的节点更新同步规则;这里,可参见图8-1的步骤L801,包括:控制器根据在拓扑重新计算后,发现节点NE9的同步规则需要更新,就发送请求消息给节点NE8,该请求消息中携带有NE9的同步规则。
步骤D82,控制器确定该同步节点的下游节点中具有更高质量等级或更好保持性能的时钟的节点,然后控制器发送保持请求消息给具有高质量等级或更好保持性能的时钟的节点,以请求具有高质量等级或更好保持性能的时钟的节点进入保持模式;
这里,请参见图8-3,图8-3中的步骤S831和步骤S832分别对应地与图8-1中的步骤S811和步骤S812相同,因此不再赘述。在图8-3中,节点NE5发生故障后,控制器检测到节点NE5的下游节点中没有备选的输入参考源,但节点NE5的下游节点NE8具有更好保持性能的时钟即TSC节点,则控制器向节点NE8发送保持请求消息,请求节点NE8进入保持模式,从而使得NE8能尽快进入保持,从而提高了基站的同步性能。
步骤D9,具有备选的输入参考源的节点向上游节点发送倒换消息,进入步骤D10;
这里,继续承接步骤D81中的例子,参见图8-1所示,同步节点NE8向上游节点NE7发送倒换消息。
步骤D10,该上游节点接收到具有备选的输入参考源的节点发送的倒换消息,则根据同步规则的计算出端口信息,检查倒换消息入口合法性;如果合法,则根据同步规则进行参考源倒换,倒换完成后发送消息通知控制器;
这里,步骤D10承接上述步骤D9;
这里,继续承接步骤D9中的例子,参见图8-1,上游节点NE7收到同步节点NE8发送的倒换消息,上游节点NE7根据倒换消息的输入端口信息,根据同步规则进行检查,发现该倒换消息是从下游端口(P72)收到的,则判断该倒换消息是合法的;
然后,节点NE7倒换到下游端口P72,并更新同步规则;
然后,节点NE7发送倒换完成消息通知控制器,控制器更新节点NE7的同步规则,保证同步规则的一致性。另外,节点NE7检查同步规则具有有效的输入参考源(对应端口71),则向端口71转发倒换消息;
这里,倒换消息可以延迟一段时间再转发,即倒换消息可以在保持延迟时间之后再由NE7转发给上游节点NE6;
步骤D11,具有备选的输入参考源的节点的第二个上游节点收到具有备选的输入参考源的节点的第一个上游节点发送的倒换消息后,进行合法性验证以及转发倒换消息;
这里,步骤D11继续承接步骤D10,而且继续承接步骤D10中的例子,参见图8-1和图8-2,节点NE6收到下游节点NE7发送的倒换消息后,NE6的处理流程和节点NE7收到节点NE8发送的倒换消息的处理流程类似,因此不再赘述;最终,倒换消息达到故障节点NE5,故障节点NE5完成倒换后,发送倒换完成消息通告控制器,节点NE5发现原参考源即主参考源无效后,便不再转发倒换消息。
实施例九
本发明实施例提供一种控制器,图9-1为本发明实施例九控制器的组成结构示意图一,如图9-1所示,所述控制器900包括第一确定单元901、生成单元902和第一发送单元903,其中:
所述第一确定单元901,配置为根据所述同步网络的物理链路拓扑信 息、所述同步网络中同步节点的同步信息,确定所述同步网络的同步链路拓扑信息;
所述生成单元902,配置为根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
所述第一发送单元903,配置为根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送所述同步规则和/或请求消息;
这里,所述第一发送单元903,所述第一发送单元配置为根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送请求消息时,所述请求消息携带有所述同步规则。
基于图9-1所示的实施例,如图9-2所示,本发明实施例提供的控制器900,还包括获取单元904和检测单元905,其中:
所述获取单元904,配置为获取所述同步网络中同步节点的同步信息;
所述检测单元905,配置为检测同步节点之间端口的物理连接关系,获得所述物理链路拓扑信息。
基于图9-1所示的实施例,如图9-3所示,本发明实施例提供的控制器900,还包括第一接收单元906和更新单元907,其中:
所述第一接收单元906,配置为接收所述同步节点发送的倒换完成消息,触发所述更新单元;
所述更新单元907,配置为更新所述同步链路拓扑信息和/或同步规则。
本发明实施例中,所述更新单元配置为更新所述同步链路拓扑信息和同步规则时,所述更新单元907,进一步配置为根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,更新同步链路拓扑信息;以及根据同步链路拓扑信息更新同步规则。
本发明实施例中,所述更新单元配置为更新所述同步链路拓扑信息和同步规则时,所述倒换完成消息中携带有所述最佳参考源的标识信息;对 应地,所述更新单元907,进一步配置为所述控制器根据最佳参考源的标识信息,更新同步链路拓扑信息和同步规则。
所述第一发送单906,还配置为根据更新后的同步链路拓扑信息,确定需要进行重新同步的同步节点;以及,将更新后的同步链路的拓扑结构信息和同步规则携带于建立请求消息中,发送给所述需要进行重新同步的同步节点。
本发明实施例中,所述控制器还包括第一判断单元;
所述第一接收单元,还配置为接收所述同步节点发送的用于表明不存在其它有效的参考源的故障消息,触发所述判断单元;
所述第一判断单元,配置为判断所述同步节点的所有下游节点是否存在备选的参考源,是时,触发所述第一发送单元;
所述第一发送单元,配置为向具有备选参考源的下游节点发送用于指示倒换到备用参考源的倒换请求消息。
本发明实施例中,所述第一确定单元,还配置为判断所述同步节点的所有下游节点不存在备选的参考源时,确定所述同步节点的下游节点中具有更高质量等级或更好保持性能的时钟的第一下游节点,触发所述第一发送单元;
所述第一发送单元,配置为向所述第一下游节点发送保持请求消息,以请求所述第一下游节点进入保持模式。
实施例十
本发明实施例提供一种同步节点,图10-1为本发明实施例十同步节点的组成结构示意图一,如图10-1所示,所述同步节点1000包括第二接收单元1001和锁定单元1002,其中:
所述第二接收单元1001,配置为接收所述同步网络中的控制器发送的同步规则和/或请求消息;
所述锁定单元1002,配置为根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
在图10-1所示的实施例的基础上,如图10-2所示,所述同步节点还包括第二判断单元1003和倒换单元1004,其中:
所述第二判断单元1003,配置为判断输入参考源是否出现告警,是时,根据所述同步规则继续判断是否存在其它有效的参考源,是时,触发所述倒换单元;
所述倒换单元1004,配置为根据所述同步规则倒换到最佳的参考源。
在图10-2所示的实施例的基础上,如图10-3所示,所述同步节点1000还包括第二发送单元1005,配置为更新本地的同步规则,并向所述控制器发送倒换完成消息。
本发明实施例中,所述第二接收单元,还配置为接收所述控制器发送的请求消息,其中所述请求消息中携带有更新后的同步链路拓扑信息和同步规则,触发所述锁定单元;
所述锁定单元,配置为根据同步规则锁定最佳的有效参考源,并向其它端口输出参考源信息。
本发明实施例中,所述同步节点还包括保持单元;
所述第二判断单元,配置为根据所述同步规则确定不存在其它有效的参考源时,触发所述保持单元;
所述保持单元,配置为使所述同步节点进入保持模式,并触发所述第二发送单元;
所述第二发送单元,配置为向所述控制器发送用于表明不存在其它有效的参考源的故障消息。
本发明实施例中,所述第二接收单元,配置为接收所述控制器发送的用于指示倒换到备用参考源的倒换请求消息,并触发所述倒换单元;
所述倒换单元,配置为倒换到备选参考源,并触发所述第二发送单元;
所述第二发送单元,配置为向上游的第一个同步节点发送用于指示倒换的倒换消息。
本发明实施例中,所述第二接收单元,配置为接收到所述倒换消息,触发所述第二判断单元;
所述第二判断单元,配置为根据所述同步规则判断接收到所述倒换消息的输入端口是否合法,是时,触发所述倒换单元;
所述倒换单元,配置为根据同步规则进行参考源倒换,并触发所述第二发送单元;
所述第二发送单元,配置为向所述控制器发送倒换完成消息。
实施例十一
本发明实施例提供一种同步网络,图11-1为本发明实施例十一同步网络的组成结构示意图一,如图11-1所示,所述同步网络包括控制器900和同步节点1000,其中,所述控制器900包括第一确定单元901、生成单元902和第一发送单元903,所述同步节点1000包括第二接收单元1001和锁定单元1002,其中:
所述第一确定单元901,配置为根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定所述同步网络的同步链路拓扑信息;
所述生成单元902,配置为根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
所述第一发送单元903,配置为根据所述同步链路拓扑信息,向所述第二接收单元发送所述同步规则和/或请求消息;
所述第二接收单元1001,配置为接收所述第一发送单元发送的所述同步规则和/或请求消息;
所述锁定单元1002,配置为根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
在图11-1所示的实施例的基础上,如图11-2所示,在本实施例所提供的同步网络中,所述控制器900还包括第一接收单元906和更新单元907;所述同步节点还包括第二判断单元1003、倒换单元1004和第二发送单元1005,其中:
所述第二判断单元1003,配置为判断输入参考源是否出现告警,是时,根据所述同步规则继续判断是否存在其它有效的参考源,是时,触发所述倒换单元;
所述倒换单元1004,配置为根据所述同步规则倒换到最佳的参考源。
所述第二发送单元1005,配置为更新本地的同步规则,并向所述第一接收单元906发送倒换完成消息。
所述第一接收单元906,配置为接收所述第二发送单元1005发送倒换完成消息,触发所述更新单元907;
所述更新单元907,配置为更新所述同步链路拓扑信息和同步规则。
本发明实施例提供的控制器中的第一确定单元、生成单元、第一发送单元、获取单元、检测单元、第一接收单元和更新单元等都可以通过控制器中的处理器来实现;本发明实施例提供的同步节点中的第二接收单元、锁定单元、第二判断单元、倒换单元、第二发送单元和保持单元等都可以通过同步节点中的处理器来实现;当然处理器执行的功能也可通过具体的逻辑电路实现;在具体实施例的过程中,处理器可以为中央处理器(CPU)、微处理器(MPU)、数字信号处理器(DSP)或现场可编程门阵列(FPGA)等,前述通信终端可以是手机、平板电脑等设备。
需要说明的是,本发明实施例中,如果以软件功能模块的形式实现上述应用于控制器中的同步方法和/或应用于同步节点中的同步方法,并作为 独立的产品销售或使用时,也可以存储在一个计算机可读取存储介质中。基于这样的理解,本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read Only Memory)、磁碟或者光盘等各种可以存储程序代码的介质。这样,本发明实施例不限制于任何特定的硬件和软件结合。
相应地,本发明实施例再提供一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,该计算机可执行指令用于执行本发明各实施例中提供的应用于控制器中的同步方法和/或应用于同步节点中的同步方法。
本发明实施例所提供的控制器、同步节点以及同步网络仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,如:多个单元或组件可以结合,或可以集成到另一个系统,或一些特征可以忽略,或不执行。另外,所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口,设备或单元的间接耦合或通信连接,可以是电性的或其它形式的。本发明实施例所提供的控制器、同步节点以及同步网络仅是示意性的,还体现在有些更为具体的内容,需要参照上述的实施例的同步方法,
上述单元可以是、或也可以不是物理上分开的;既可以位于一个地方,也可以分布到多个网络设备上;例如,本发明实施例中的控制器和同步节点可能位于同一网络实体设备上,因为控制器是逻辑上的概念,因而可能与同步节点位于同一个网络实体设备,也可以分别位于两个网络实体设备上,本领域的技术人员可以根据实际的需要选择其中的部分或全部单元来 实现本实施例方案的目的。
另外,在本发明各实施例中的各功能单元可以全部集成在一个处理单元中,也可以是各单元分别单独作为一个单元,也可以两个或两个以上单元集成在一个单元中;上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能单元的形式实现。
本领域普通技术人员可以理解:实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成,前述的程序可以存储于计算机可读取存储介质中,该程序在执行时,执行包括上述方法实施例的步骤;而前述的存储介质包括:移动存储设备、只读存储器(ROM,Read Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
或者,本发明上述集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时,也可以存储在一个计算机可读取存储介质中。基于这样的理解,本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括:移动存储设备、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本发明的具体实施方式,但本发明的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本发明的保护范围之内。因此,本发明的保护范围应以所述权利要求的保护范围为准。
工业实用性
本发明实施例中,同步网络中的控制器根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定同步链路拓扑信息;所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送所述同步规则和/或请求消息;如此,能够快速地使同步链路进行倒换,从而满足同步链路倒换的实时性,进而有效地提高整网的同步性能。

Claims (35)

  1. 一种同步方法,所述方法包括:
    控制器根据同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定所述同步网络的同步链路拓扑信息;
    所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
    所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和/或请求消息。
  2. 根据权利要求1所述的方法,其中,当所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送请求消息时,所述请求消息中携带有所述同步规则。
  3. 根据权利要求1所述的方法,其中,所述方法还包括:
    所述控制器获取所述同步网络中同步节点的同步信息;
    所述控制器检测同步节点之间端口的物理连接关系,获得所述物理链路拓扑信息。
  4. 根据权利要求1所述的方法,其中,所述向所述同步网络中的同步节点发送同步规则和/或请求消息之后,所述方法还包括:
    所述控制器接收所述同步节点发送的倒换完成消息后,更新所述同步链路拓扑信息和/或同步规则。
  5. 根据权利要求4所述的方法,其中,所述更新所述同步链路拓扑信息和同步规则,包括:
    所述控制器根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,更新同步链路拓扑信息;
    所述控制器根据同步链路拓扑信息更新同步规则。
  6. 根据权利要求4所述的方法,其中,所述倒换完成消息中携带有所述最佳参考源的标识信息;对应地,所述更新所述同步链路拓扑信息和同步规则,包括:
    所述控制器根据最佳参考源的标识信息,更新同步链路拓扑信息和同步规则。
  7. 根据权利要求4所述的方法,其中,所述方法还包括:
    所述控制器根据更新后的同步链路拓扑信息,确定需要进行重新同步的同步节点;
    所述控制器将更新后的同步规则携带于建立请求消息中,发送给所述需要进行重新同步的同步节点。
  8. 根据权利要求1至7任一项所述的方法,其中,所述方法还包括:
    所述控制器接收所述同步节点发送的故障消息;
    所述控制器判断所述同步节点的所有下游节点是否存在备选的参考源,是时,向具有备选参考源的下游节点发送倒换请求消息。
  9. 根据权利要求1至7任一项所述的方法,其中,所述方法还包括:
    所述控制器判断所述同步节点的所有下游节点不存在备选的参考源时,确定所述同步节点的下游节点中具有更高质量等级或更好保持性能的时钟的第一下游节点;
    所述控制器向所述第一下游节点发送保持请求消息,以请求所述第一下游节点进入保持模式。
  10. 一种同步方法,所述方法包括:
    同步节点接收控制器发送的同步规则和/或请求消息,所述请求消息中携带有所述同步规则;
    所述同步节点根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
  11. 根据权利要求10所述的方法,其中,所述方法还包括:
    所述同步节点判断输入参考源是否出现告警,是时,根据所述同步规则继续判断是否存在其它有效的参考源;
    所述同步节点根据所述同步规则确定存在其它有效的参考源时,根据所述同步规则倒换到最佳的参考源。
  12. 根据权利要求11所述的方法,其中,所述根据所述同步规则倒换到最佳的参考源的同时,所述方法还包括:
    所述同步节点更新本地的同步规则,并向所述控制器发送倒换完成消息。
  13. 根据权利要求11所述的方法,其中,所述方法还包括:
    所述同步节点接收所述控制器发送的请求消息,其中所述请求消息中携带有更新后的同步规则;
    所述同步节点根据同步规则锁定最佳的有效参考源,并向其它端口输出参考源信息。
  14. 根据权利要求11所述的方法,其中,所述方法还包括:
    所述同步节点当根据所述同步规则确定不存在其它有效的参考源时,进入保持模式,并向所述控制器发送故障消息。
  15. 根据权利要求11至14任一项所述的方法,其中,所述方法还包括:
    接收所述控制器发送的倒换请求消息后,所述同步节点倒换到备选参考源,并向上游的第一个同步节点发送倒换消息。
  16. 根据权利要求15所述的方法,其中,所述方法还包括:
    所述上游的第一个同步节点接收到所述倒换消息后,根据所述同步规则判断接收到所述倒换消息是否合法;
    判断不合法时,丢弃所述倒换消息;
    判断合法时,根据同步规则进行参考源倒换,并向所述控制器发送倒换完成消息;并在确定其自身存在有效的输入参考源时,向具有有效的输入参考源的端口转发所述倒换消息以通告上游节点,或延迟一段时间后再向所述具有有效的输入参考源的端口转发所述倒换消息以通告上游节点;在确定其自身不存在有效的输入参考源时,不转发所述倒换消息。
  17. 一种控制器,所述控制器包括第一确定单元、生成单元和第一发送单元,其中:
    所述第一确定单元,配置为根据同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定所述同步网络的同步链路拓扑信息;
    所述生成单元,配置为根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
    所述第一发送单元,配置为根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和/或请求消息。
  18. 根据权利要求17所述的控制器,其中,所述第一发送单元配置为根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送请求消息时,所述请求消息中携带有所述同步规则。
  19. 根据权利要求17所述的控制器,其中,所述控制器还包括获取单元和检测单元,其中:
    所述获取单元,配置为获取所述同步网络中同步节点的同步信息;
    所述检测单元,配置为检测所述同步节点之间端口的物理连接关系,获得所述物理链路拓扑信息。
  20. 根据权利要求17所述的控制器,其中,所述控制器还包括第一接收单元和更新单元,其中
    所述第一接收单元,配置为接收所述同步节点发送的倒换完成消息,触发所述更新单元;
    所述更新单元,配置为更新所述同步链路拓扑信息和/或同步规则。
  21. 根据权利要求20所述的控制器,其中,所述更新单元配置为更新所述同步链路拓扑信息和同步规则时,所述更新单元,进一步配置为根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,更新同步链路拓扑信息;以及根据同步链路拓扑信息更新同步规则。
  22. 根据权利要求20所述的控制器,其中,所述更新单元配置为更新所述同步链路拓扑信息和同步规则时,所述倒换完成消息中携带有所述最佳参考源的标识信息;对应地,所述更新单元,进一步配置为所述控制器根据最佳参考源的标识信息,更新同步链路拓扑信息和同步规则。
  23. 根据权利要求20所述的控制器,其中,所述第一发送单元,还配置为根据更新后的同步链路拓扑信息,确定需要进行重新同步的同步节点;以及,将更新后的同步规则携带于建立请求消息中,发送给所述需要进行重新同步的同步节点。
  24. 根据权利要求20至23任一项所述的控制器,其中,所述控制器还包括第一判断单元;
    所述第一接收单元,还配置为接收所述同步节点发送的故障消息,触发所述第一判断单元;
    所述第一判断单元,配置为判断所述同步节点的所有下游节点是否存在备选的参考源,是时,触发所述第一发送单元;
    所述第一发送单元,配置为向具有备选参考源的下游节点发送倒换请求消息。
  25. 根据权利要求20至23任一项所述的控制器,其中,所述第一确定单元,还配置为判断所述同步节点的所有下游节点不存在备选的参考源时,确定所述同步节点的下游节点中具有更高质量等级或更好保持性能的时钟的第一下游节点,触发所述发送单元;
    所述第一发送单元,配置为向所述第一下游节点发送保持请求消息,以请求所述第一下游节点进入保持模式。
  26. 一种同步节点,所述同步节点包括第二接收单元和锁定单元,其中:
    所述第二接收单元,配置为接收控制器发送的同步规则和/或请求消息,所述请求消息中携带有所述同步规则;
    所述锁定单元,配置为根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
  27. 根据权利要求26所述的同步节点,其中,所述同步节点还包括第二判断单元和倒换单元,其中:
    所述第二判断单元,配置为判断输入参考源是否出现告警,是时,根据所述同步规则继续判断是否存在其它有效的参考源,是时,触发所述倒换单元;
    所述倒换单元,配置为根据所述同步规则倒换到最佳的参考源。
  28. 根据权利要求27所述的同步节点,其中,所述同步节点还包括第二发送单元,配置为更新本地的同步规则,并向所述控制器发送倒换完成消息。
  29. 根据权利要求27所述的同步节点,其中,所述第二接收单元,还配置为接收所述控制器发送的请求消息,其中所述请求消息中携带有更新后的同步规则,触发所述锁定单元;
    所述锁定单元,配置为根据同步规则锁定最佳的有效参考源,并向其它端口输出参考源信息。
  30. 根据权利要求27所述的同步节点,其中,所述同步节点还包括保持单元;
    所述第二判断单元,配置为根据所述同步规则确定不存在其它有效的 参考源时,触发所述保持单元;
    所述保持单元,配置为使所述同步节点进入保持模式,并触发所述第二发送单元;
    所述第二发送单元,配置为向所述控制器发送故障消息。
  31. 根据权利要求27至30任一项所述的同步节点,其中,所述第二接收单元,配置为接收所述控制器发送的倒换请求消息,并触发所述倒换单元;
    所述倒换单元,配置为倒换到备选参考源,并触发所述第二发送单元;
    所述第二发送单元,配置为向上游的第一个同步节点发送倒换消息。
  32. 根据权利要求31所述的同步节点,其中,所述第二接收单元,配置为接收到所述倒换消息,触发所述第二判断单元;
    所述第二判断单元,配置为根据所述同步规则判断接收到所述倒换消息的输入端口是否合法,是时,触发所述倒换单元;
    所述倒换单元,配置为根据同步规则进行参考源倒换,并触发所述第二发送单元;
    所述第二发送单元,配置为向所述控制器发送倒换完成消息。
  33. 一种同步方法,所述方法包括:
    控制器根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定同步链路拓扑信息;
    所述控制器根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
    所述控制器根据所述同步链路拓扑信息,向所述同步网络中的同步节点发送同步规则和/或请求消息;
    所述同步节点接收所述同步规则和/或所述请求消息;
    所述同步节点根据所述同步规则,锁定最佳的有效参考源,并向其它 端口输出参考源信息。
  34. 一种同步网络,所述同步网络包括控制器和同步节点,其中,所述控制器包括第一确定单元、生成单元和第一发送单元,所述同步节点包括第二接收单元和锁定单元,其中:
    所述第一确定单元,配置为根据所述同步网络的物理链路拓扑信息、所述同步网络中同步节点的同步信息,确定同步链路拓扑信息;
    所述生成单元,配置为根据所述同步链路拓扑信息,生成所述同步节点的同步规则;
    所述第一发送单元,配置为根据所述同步链路拓扑信息,向所述第二接收单元发送同步规则和/或请求消息;
    所述第二接收单元,配置为接收所述第一发送单元发送的所述同步规则和/或所述请求消息;
    所述锁定单元,配置为根据所述同步规则,锁定最佳的有效参考源,并向其它端口输出参考源信息。
  35. 一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,该计算机可执行指令用于执行权利要求1至9任一项所述的同步方法,
    和/或,
    该计算机可执行指令用于执行权利要求10至16任一项所述的同步方法。
PCT/CN2014/086453 2014-05-16 2014-09-12 同步方法、控制器、同步节点及同步网络、存储介质 WO2015172476A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/311,192 US10181919B2 (en) 2014-05-16 2014-09-12 Synchronization method, controller, synchronization node, synchronous network, and storage medium
EP14891855.0A EP3145111A4 (en) 2014-05-16 2014-09-12 Synchronization method, controller, synchronization node, synchronous network, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410209706.9 2014-05-16
CN201410209706.9A CN105099647A (zh) 2014-05-16 2014-05-16 一种同步方法、控制器、同步节点及同步网络

Publications (1)

Publication Number Publication Date
WO2015172476A1 true WO2015172476A1 (zh) 2015-11-19

Family

ID=54479236

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/086453 WO2015172476A1 (zh) 2014-05-16 2014-09-12 同步方法、控制器、同步节点及同步网络、存储介质

Country Status (4)

Country Link
US (1) US10181919B2 (zh)
EP (1) EP3145111A4 (zh)
CN (1) CN105099647A (zh)
WO (1) WO2015172476A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180122688A (ko) * 2016-03-18 2018-11-13 후아웨이 테크놀러지 컴퍼니 리미티드 클록 동기화 토폴로지를 갱신하는 방법, 클록 동기화 경로를 결정하는 방법, 및 기기
CN111049886A (zh) * 2019-11-29 2020-04-21 紫光云(南京)数字技术有限公司 多区域sdn控制器数据同步方法、服务器及系统
CN112350794A (zh) * 2019-08-09 2021-02-09 诺基亚通信公司 一种端到端透明时钟和转发ptp报文的方法
CN113328889A (zh) * 2021-05-31 2021-08-31 河南财政金融学院 一种软件定义网络中控制层架构分布式优化方法

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106921509B (zh) * 2015-12-28 2020-07-10 中兴通讯股份有限公司 一种全网时钟同步管理的方法及装置
CN107465476A (zh) * 2016-06-06 2017-12-12 中兴通讯股份有限公司 时钟同步的方法及装置
CN108988976B (zh) * 2017-05-31 2021-01-26 中兴通讯股份有限公司 一种同步网自动保护方法和装置
US10420101B2 (en) * 2017-09-29 2019-09-17 Intel Corporation Traffic-aware slot assignment
CN108111423B (zh) * 2017-12-28 2020-11-17 迈普通信技术股份有限公司 流量传输管理方法、装置及网络分路设备
US11671490B2 (en) 2018-03-23 2023-06-06 Clearblade, Inc. Asset synchronization systems and methods
US11683110B2 (en) * 2018-03-23 2023-06-20 Clearblade, Inc. Edge synchronization systems and methods
JP7238535B2 (ja) * 2019-03-27 2023-03-14 オムロン株式会社 ネットワーク管理装置、管理方法、管理プログラムおよび記録媒体
EP4011045B1 (en) * 2019-08-13 2024-04-24 Huawei Technologies Co., Ltd. Control and management for impairment-aware optical network
CN115765912A (zh) * 2020-04-14 2023-03-07 华为技术有限公司 参数配置方法、设备及系统
CN112214065B (zh) * 2020-09-17 2022-10-21 北京普源精电科技有限公司 设备同步校准方法、装置、设备及存储介质
CN112087385B (zh) * 2020-09-18 2021-11-12 北京航空航天大学 一种基于多控制器协商的sdn一致性更新方法
CN113452465B (zh) * 2021-05-17 2023-12-26 新华三信息安全技术有限公司 一种时钟同步方法及装置
CN115102660B (zh) * 2022-08-26 2022-11-04 深圳市英特瑞半导体科技有限公司 基于同步以太网的破环方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1770701A (zh) * 2004-11-03 2006-05-10 华为技术有限公司 Mesh网中时钟跟踪的实现方法
CN101043316A (zh) * 2006-05-24 2007-09-26 华为技术有限公司 一种同步方法和系统
CN102075317A (zh) * 2011-01-24 2011-05-25 博威通讯系统(深圳)有限公司 一种家庭基站系统中可靠的时频同步方法及系统
CN103166750A (zh) * 2011-12-14 2013-06-19 中兴通讯股份有限公司 时钟时间同步源配置方法及装置
CN103634091A (zh) * 2012-08-20 2014-03-12 中兴通讯股份有限公司 一种多同步域的时间同步系统、方法及跨域设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6711411B1 (en) * 2000-11-07 2004-03-23 Telefonaktiebolaget Lm Ericsson (Publ) Management of synchronization network
US8867520B2 (en) * 2008-03-07 2014-10-21 Charles Nicholls Using a network frequency reference to augment timing Synchronization in a wireless base station
US8149881B2 (en) * 2009-06-26 2012-04-03 Alcatel Lucent Centralized node clock auto reconfiguration
US8203969B2 (en) * 2009-12-10 2012-06-19 Alcatel Lucent Network timing topology via network manager
WO2011072881A1 (en) * 2009-12-17 2011-06-23 Telefonaktiebolaget L M Ericsson (Publ) Configuration of synchronisation network having synchronization trails for time sync and frequency sync

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1770701A (zh) * 2004-11-03 2006-05-10 华为技术有限公司 Mesh网中时钟跟踪的实现方法
CN101043316A (zh) * 2006-05-24 2007-09-26 华为技术有限公司 一种同步方法和系统
CN102075317A (zh) * 2011-01-24 2011-05-25 博威通讯系统(深圳)有限公司 一种家庭基站系统中可靠的时频同步方法及系统
CN103166750A (zh) * 2011-12-14 2013-06-19 中兴通讯股份有限公司 时钟时间同步源配置方法及装置
CN103634091A (zh) * 2012-08-20 2014-03-12 中兴通讯股份有限公司 一种多同步域的时间同步系统、方法及跨域设备

Non-Patent Citations (1)

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

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180122688A (ko) * 2016-03-18 2018-11-13 후아웨이 테크놀러지 컴퍼니 리미티드 클록 동기화 토폴로지를 갱신하는 방법, 클록 동기화 경로를 결정하는 방법, 및 기기
EP3419230A4 (en) * 2016-03-18 2019-05-01 Huawei Technologies Co., Ltd. METHOD FOR UPDATING CLOCK SYNCHRONIZATION TOPOLOGY, CLOCK SYNCHRONIZATION PATH DETERMINATION METHOD, AND APPARATUS
US10892884B2 (en) 2016-03-18 2021-01-12 Huawei Technologies Co., Ltd. Method for updating clock synchronization topology, method for determining clock synchronization path, and device
KR102205992B1 (ko) * 2016-03-18 2021-01-20 후아웨이 테크놀러지 컴퍼니 리미티드 클록 동기화 토폴로지를 갱신하는 방법, 클록 동기화 경로를 결정하는 방법, 및 기기
KR20210008940A (ko) * 2016-03-18 2021-01-25 후아웨이 테크놀러지 컴퍼니 리미티드 클록 동기화 토폴로지를 갱신하는 방법, 클록 동기화 경로를 결정하는 방법, 및 기기
KR102503516B1 (ko) 2016-03-18 2023-02-23 후아웨이 테크놀러지 컴퍼니 리미티드 클록 동기화 토폴로지를 갱신하는 방법, 클록 동기화 경로를 결정하는 방법, 및 기기
CN112350794A (zh) * 2019-08-09 2021-02-09 诺基亚通信公司 一种端到端透明时钟和转发ptp报文的方法
CN112350794B (zh) * 2019-08-09 2024-01-16 诺基亚通信公司 一种端到端透明时钟和转发ptp报文的方法
CN111049886A (zh) * 2019-11-29 2020-04-21 紫光云(南京)数字技术有限公司 多区域sdn控制器数据同步方法、服务器及系统
CN113328889A (zh) * 2021-05-31 2021-08-31 河南财政金融学院 一种软件定义网络中控制层架构分布式优化方法

Also Published As

Publication number Publication date
EP3145111A1 (en) 2017-03-22
US10181919B2 (en) 2019-01-15
EP3145111A4 (en) 2017-06-14
US20180131459A1 (en) 2018-05-10
CN105099647A (zh) 2015-11-25

Similar Documents

Publication Publication Date Title
WO2015172476A1 (zh) 同步方法、控制器、同步节点及同步网络、存储介质
EP2820783B1 (en) Frequency distribution using precision time protocol
US9819541B2 (en) PTP over IP in a network topology with clock redundancy for better PTP accuracy and stability
CN103107876B (zh) 一种多时钟同步技术混合组网的实现方法和系统和装置
CN102843205B (zh) 一种基于精确时间协议的时间同步收敛的方法和装置
CN102263630B (zh) 一种时钟源的选择方法
WO2013170736A1 (zh) 一种分组网络同步方法、装置及系统
EP2541815B1 (en) Clock synchronization network
US20160156427A1 (en) Clock recovery in a packet based network
JP6170415B2 (ja) 時刻同期システム、時刻同期方法及びコンピュータプログラム
CN101616163B (zh) 精确时间传递协议报文处理方法及装置
WO2014101669A1 (zh) 时间同步方法及系统
WO2013189176A2 (zh) 一种多同步域的时间同步系统、方法及跨域设备
WO2016004644A1 (zh) 一种监控以太网时钟同步的方法及装置
WO2015165192A1 (zh) 一种时间同步的方法及装置
US9363206B2 (en) Method and apparatus for selecting passive port of transparent clock node based on PTP
CN102006135A (zh) 一种选择同步时钟源的方法及装置
US20110305248A1 (en) Clock selection for synchronous ethernet
CN102158335B (zh) 时间同步端口的处理方法及装置
WO2012163172A1 (zh) 一种时钟同步方法及设备
WO2011134371A1 (zh) 一种同步时钟的方法和时钟同步装置
CN102457346A (zh) 时间同步实现方法及时钟节点
WO2016004645A1 (zh) 一种基于e1链路的ieee1588时钟同步方法、系统及装置
CN102404104B (zh) 基于不同延时机制的自适应同步方法及系统
CN102761492B (zh) 一种基于ospf协议的路由重学方法和设备

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: 14891855

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014891855

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014891855

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15311192

Country of ref document: US