Processing methods and equipment for packet scheduling channel failures.

Abstract

Invention details;

Description

A method and device for processing packet synchronization channel failure

Technical field

[0001] The present invention relates to the technical field of packet time synchronization, and in particular to a method and device for processing packet synchronization channel failure. [Background Technology]

[0002] High-precision time synchronization is one of the key requirements for 5G bearer, and has application scenarios in wireless communications, communication networks, the Internet of Things, the Industrial Internet, and other fields.

[0003] The mainstream time synchronization technology used in the industry is based on IEEE 1588v2. The clock models commonly used in networking applications are boundary clocks (BC) and ordinary clocks (OC). The time synchronization tracking path is determined by the Best Master Clock (BMC) algorithm defined in 1588v2.

[0004] Real-time monitoring of the synchronization channel of the time synchronization link is a key mechanism for synchronization OAM and is of great significance to the stable operation of the time synchronization network. Monitoring of the packet synchronization channel includes various monitoring contents, such as: Precision Time Protocol (PTP) message loss, PTP message information anomalies, PTP timing unreliability, PTP input degradation, channel network delay variation (PDV) exceeding the limit, etc. Once a degradation event is detected, the packet synchronization channel is deemed to have failed. After the synchronization channel fails, the synchronization node will not be able to achieve accurate time source information recovery through this channel. How to handle the packet synchronization channel failure (PTCF) event and enhance the robustness of the synchronization network is a key issue.

[0005] [Summary of the invention]

[0006] The technical problem to be solved by this invention is to utilize packet synchronization channel monitoring technology to re-determine the synchronization path when a packet synchronization channel failure event is detected. Switching the synchronization link to another path can ensure normal synchronization of the synchronization link. However, under the current mechanism, this implementation has the following technical problems:

[0007] The current source selection algorithm and the synchronization measurement protocol operate independently, lacking a correlation mechanism. As shown in Figure 1, the source selection algorithm determines the node's tracking direction and the port's synchronization status. The synchronization port then runs the synchronization measurement protocol based on the source selection's operating status: master or slave. The synchronization measurement protocol layer cannot influence the source selection algorithm's decisions, nor can failures of the packet synchronization channel implemented by the synchronization measurement protocol layer. Relying solely on Announce messages, the source selection algorithm will cause the node's tracking port to remain in the direction of the port where the packet synchronization channel failed.

[0008] Furthermore, the solution of the present invention is also used to solve the following sub-problem: Monitoring of the packet synchronization channel is implemented at the slave clock port based on the synchronization measurement protocol. By analyzing received PTP synchronization messages, timestamp information, and other information, it is determined whether a packet synchronization channel failure event has occurred on that port's packet synchronization channel. Once a packet synchronization channel failure event is detected and path switching is triggered, the port with the failed packet synchronization channel no longer operates in the slave clock state, thus losing the ability to monitor the packet synchronization channel failure and unable to complete state recovery or synchronization path reswitching, resulting in the port remaining in an abandoned state.

[0009] The present invention adopts the following technical solutions:

[0010] In the first aspect, the present invention provides a method for processing the failure of a packet synchronization channel. When a port in the Slave state detects a packet channel failure event, the port is stripped from the main decision domain time source information set and a status decision is made based on the separated sub-decision domain time source information set and the main decision domain time source information set. The result is a monitoring state or a master clock state.

[0011] Preferably, the monitoring state is a newly added state; or, it is an extension of the existing Master, Slave, and Passive states.

[0012] Preferably, the port in the monitoring state can receive and send synchronization messages, run the PTP mechanism, and calculate and analyze the delay and clock deviation; the calculation results are not used for synchronization tracking.

[0013] Preferably, the port in the Slave state detects a packet channel failure event, and the port is stripped from the main decision domain time source information set, specifically including: the sub-decision domain of the port no longer provides time source information to the main decision domain, and at the same time needs to obtain the time source information of the main decision domain.

[0014] Preferably, it also includes that if the port in the monitoring state detects that the failure alarm disappears, the sub-decision domain restores the binding with the main decision domain, re-provides time source information to the main decision domain, and triggers the main decision domain to make a new decision.

[0015] Preferably, when the state decision of the sub-decision domain is a monitoring state, it specifically includes:

[0016] The sub-decision domain of the port extracts the time source information of the Announce message received from the outside and obtains the time source information of the main decision domain. If the time source information received by the sub-decision domain is better than the time source information of the main decision domain, the port is decided to be in monitoring state;

[0017] Alternatively, if the sub-decision domain receives an Announce message from an external port and the time source information set of the main decision domain is empty, the port is decided to be in the monitoring state.

[0018] Preferably, when the state decision of the sub-decision domain is the master clock state, the state decision specifically includes:

[0019] If the time source information of the main decision domain is better than that of the sub-decision domain synchronization port of the corresponding port, the port operates in the master clock state.

[0020] Preferably, if the number of ports or the status of slave ports changes, the master decision domain will restart the status decision.

[0021] Preferably, the monitoring state can also be entered through configuration, and in this case it is not related to the failure alarm, and the system is always in the monitoring state unless the configuration is changed.

[0022] In a second aspect, the present invention further provides a method for processing a packet synchronization channel failure, wherein port A of a first node is connected to port B' of a second node, and port A of the first node operates in a master clock state, and port B' of the second node operates in a slave clock state, the processing method comprising:

[0023] The port B' of the second node starts packet synchronization channel monitoring. When a packet synchronization channel failure event is detected, the second node sets the packet synchronization channel failure event flag of the port B' to be valid.

[0024] The sub-decision domain of the port B' of the second node is separated from the main decision domain of the second node, and the port B' of the second node enters the monitoring state;

[0025] The sub-decision domains of the other ports of the second node remain bound to the main decision domain of the second node; through the main domain decision algorithm, port C' of the second node becomes the new and only slave clock port of the second node; the sub-decision domain of port C' of the second node replaces the sub-decision domain of port B' of the second node to provide time source information to the main decision domain of the second node.

[0026] Preferably, after the port B' of the second node enters the monitoring state, the method further includes:

[0027] The second node sends the packet synchronization channel failure event information to the first node;

[0028] The second node restarts the PTP protocol stack of port B' and stops monitoring the synchronization channel;

[0029] The first node receives the packet synchronization channel failure event information sent by the second node, restarts the PTP protocol stack of port A in the first node, and sends the packet synchronization channel failure event response information to the second node;

[0030] The port B' of the second node receives the packet synchronization channel failure event response information fed back by the first node, and restarts the monitoring of the synchronization channel.

[0031] Preferably, if the failure of the packet synchronization channel associated with the port B' of the second node is successfully repaired, the method further includes:

[0032] The second node sets the packet synchronization channel failure event flag of its port B' to invalid; the synchronization subdomain of the port B' of the second node re-establishes the binding relationship with the main decision domain, and starts the main domain decision algorithm; so as to obtain the time source information from the packet synchronization channel of the repaired port B' of the second node and the time source information obtained from the port C' of the second node, and decide the better time source information between the two as the time source information of the main decision domain of the second node.

[0033] Preferably, when the port B' of the second node times out when receiving the notification message of the first node, the method further includes:

[0034] Clear the sub-decision domain time source information of the port B' of the second node, switch the decision port B' to the listening state, and set the packet synchronization channel failure event flag of the port B' of the second node to invalid;

[0035] The sub-decision domain of port B' of the second node rebinds to the main decision domain of the second node, and accepts the time source information obtained by the main decision domain of the second node from port C' of the second node;

[0036] The second node sends the time source information acquired by the port C' of the second node to the first node through the connection between the port B' and the port A of the first node.

[0037] Preferably, when port B' receives one or more notification messages, the method further includes:

[0038] The sub-decision domain of port B' determines the optimal time source from one or more received notification messages, updates the time source information of the sub-decision domain, maintains the monitoring status of port B', and keeps the packet synchronization channel failure event flag set to the valid state;

[0039] After waiting for the second node's packet synchronization channel monitoring to confirm that the packet synchronization channel is restored, port B' is re-bound to the main decision domain so as to re-determine the port status.

[0040] Preferably, if it is detected that the packet synchronization channel of the second node port B' is restored, the method further includes:

[0041] The packet synchronization channel failure event flag of the second node port B' is cleared, and the sub-decision domain of the second node port B' is re-bound to the main decision domain;

[0042] If the time source information of the main decision domain is better than that of the second node port B', when the sub-decision domain synchronization port receives the external time source information, the second node port B' is decided to work in the master clock state.

[0043] Preferably, if the time source information received by the newly bound port C' of the second node's main decision domain is better than the time source information historically received by the port B' sub-decision domain of the second node, the method further includes:

[0044] Set the port B' of the second node to the master clock state, set the packet synchronization channel failure event flag to the invalid state, and bind the sub-decision domain of port B' to the master decision domain of the second node;

[0045] The second node sends the time source information obtained from the primary decision domain of the second node to the port A of the first node via a notification message through the port B';

[0046] The first node switches the working state of its port A from the historical master clock state to the slave clock state.

[0047] Preferably, if the primary decision domain bound port C' of the second node times out due to receiving the notification message, the packet synchronization channel failure event flag corresponding to the port C' is invalid, the method further includes:

[0048] The main decision domain of the second node decides that the bound port C' enters the listening state, the sub-decision domain of port B' maintains the port monitoring state, and maintains the packet synchronization channel failure event flag of port B' as valid.

[0049] Preferably, the above is achieved by running the PTP slave clock protocol and performing clock deviation calculation, and the calculation result is used for channel monitoring and analysis;

[0050] The channel monitoring and analysis includes monitoring whether the packet synchronization channel fails and comparing the channel's packet timing with the frequency or time deviation of the local clock;

[0051] The monitoring state can be migrated between the slave clock state (Slave), the master clock state (Master), the blocking state (Passive), and the listening state (Listening) under the corresponding port.

[0052] Preferably, the port C' of the second node starts packet synchronization channel monitoring, and when a packet synchronization channel failure event is detected, the second node sets the packet synchronization channel failure event flag of the port C' to be valid;

[0053] The sub-decision domain of the port C' of the second node is separated from the main decision domain of the second node, and the port C' of the second node enters the monitoring state;

[0054] The sub-decision domains of the other ports of the second node remain bound to the main decision domain of the second node; through the sub-domain decision algorithm, port D' of the second node becomes the new and only clock port of the second node; the sub-decision domain of port D' of the second node replaces the sub-decision domain of port C' of the second node to provide time source information to the main decision domain of the second node.

[0055] In a third aspect, the present invention further provides a device for processing packet synchronization channel failure, for implementing the method for processing packet synchronization channel failure according to the first and second aspects, the device comprising:

[0056] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the processor to execute the method for processing packet synchronization channel failure described in the first aspect and the second aspect.

[0057] In a fourth aspect, the present invention further provides a non-volatile computer storage medium storing computer executable instructions, which are executed by one or more processors to complete the method for processing packet synchronization channel failure described in the first aspect.

[0058] The present invention solves the problem of lack of a processing solution after a packet synchronization channel failure event is introduced, so that a synchronization OAM event is associated with a synchronization path decision, thereby improving the reliability of synchronization network operation.

[0059] Associating packet synchronization channel failure events in synchronization path decisions, for example, establishing a connection between the source selection decision algorithm and the synchronization measurement protocol layer, so that the packet synchronization channel failure event information can be referenced in the synchronization port status decision, and the normal synchronization channel path can be selected. The packet synchronization channel failure event can also be cleared in the corresponding decision scenario.

Brief Description of the Drawings

[0060] To more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. Those skilled in the art can also derive other drawings based on these drawings without inventive effort.

[0061] FIG1 is a diagram illustrating the hierarchical structure of a source selection decision algorithm and a synchronous measurement mechanism in the prior art provided by the present invention;

[0062] FIG2 is a diagram of a separation mechanism in the prior art provided by the present invention;

[0063] FIG3 is a diagram of an association mechanism provided by an embodiment of the present invention;

[0064] FIG4 is a schematic diagram of a monitoring state jump provided by an embodiment of the present invention;

[0065] FIG5 is a schematic diagram of a single-domain decision framework in the prior art provided by the present invention;

[0066] FIG6 is a schematic diagram of a dynamic subdomain decision framework provided by an embodiment of the present invention;

[0067] FIG7 is a schematic diagram of a packet synchronization channel failure event recovery mechanism provided by an embodiment of the present invention;

[0068] 8 is a schematic flow chart of a method for processing a packet synchronization channel failure according to an embodiment of the present invention;

[0069] 9 is a schematic flow diagram of a method for processing a packet synchronization channel failure according to an embodiment of the present invention;

[0070] 10 is a schematic flow diagram of a method for processing a packet synchronization channel failure according to an embodiment of the present invention;

[0071] 11 is a schematic flow diagram of a method for processing a packet synchronization channel failure according to an embodiment of the present invention;

[0072] 12 is a schematic flow diagram of a method for processing a packet synchronization channel failure according to an embodiment of the present invention;

[0073] 13 is a schematic flow diagram of a method for processing a packet synchronization channel failure according to an embodiment of the present invention;

[0074] FIG14 is a schematic diagram of a packet synchronization channel node relationship provided by an embodiment of the present invention;

[0075] FIG15 is an example diagram of a sub-decision domain decision logic provided by an embodiment of the present invention;

[0076] 16 is a schematic diagram of a message format of a frame header of a PTP message according to an embodiment of the present invention;

[0077] 17 is a schematic diagram of a delay request message frame header message according to an embodiment of the present invention;

[0078] FIG18 is a schematic structural diagram of a device for processing packet synchronization channel failure provided by an embodiment of the present invention. [Specific implementation method]

[0079] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0080] In the description of the present invention, the terms "inside", "outside", "longitudinal", "lateral", "upper", "lower", "top", "bottom", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing the present invention and do not require that the present invention must be constructed and operated in a specific orientation. Therefore, they should not be understood as limitations on the present invention.

[0081] Before producing the content of the specific embodiment scheme of the present invention, the core improved technical points of the present invention involved in each embodiment of the present invention are first separated out in advance and introduced separately, and then the technical content of the corresponding core improved points are integrated into the embodiment scenario through the technical presentation of each embodiment for relevant explanation.

[0082] Referring to Figure 2, a separate architecture is shown: the source selection decision algorithm determines the PTP operating status of the output port, and only then can the PTP port perform packet synchronization channel monitoring (labeled as the "synchronization measurement mechanism" in the figure). However, the monitoring results are unrelated to the source selection decision. The technical solution of the present invention, referring to Figure 3, establishes a connection between the packet synchronization channel failure event flag and the source selection decision (also described as a sub-decision domain algorithm in subsequent embodiments of the present invention). This will bring about changes to the processing flow of each part, as explained below:

[0083] The packet synchronization channel failure event flag has been changed: Previously, the packet synchronization channel failure event flag was only set or cleared by the synchronization channel monitoring mechanism. Now, the flag can also be cleared by the source selection decision algorithm (for example, when the subdomain decides to be the master, the failure alarm is cleared; the significant technical significance of this will be described in detail in the extended implementation scheme developed later in the embodiments of this invention).

[0084] Changes to the source selection algorithm's processing mechanism: Previously, the packet synchronization channel failure event flag was not associated with source selection decisions. Now, it can be read by the source selection algorithm and used in port operating status decisions. To address the decision-making scenarios brought about by the introduction of the packet synchronization channel failure event flag, the source selection algorithm adopts a dynamic subdomain decision framework, which allows for dynamic binding and separation with the main decision domain. (The significant technical significance of this will be fully described in the expanded implementation scheme later in this embodiment of the present invention.)

[0085] Changes to the synchronization measurement mechanism: To monitor failed channels, a new monitoring state model is adopted to ensure monitoring continuity after synchronization path switching.

[0086] In step 202 of the embodiment 1 of the present invention, the port B' of the second node enters the monitoring state, and the corresponding monitoring state is implemented based on the monitoring state model proposed in the embodiment of the present invention.

[0087] In order to solve the problem of monitoring the failed synchronization channel after the synchronization path of the packet synchronization channel is switched, a new monitoring state model is introduced in the synchronization measurement protocol. A monitoring state is added to the synchronization port working state (the existing synchronization port working states include slave clock state (Slave), master clock state (Master), blocking state (Passive) and listening state (Listening)). Different from the original single channel monitoring (which means that only the Slave port can be monitored. There will only be one Slave port on the BC node), continuous monitoring of multiple channels can be achieved (that is, multiple channels that may be connected to one port, monitoring the time source information that may be sent by multiple channels). Monitoring of the packet synchronization channels of multiple PTP ports can be achieved. The PTP port is a logical concept. Multiple PTP ports can be associated with one physical port or with different physical ports. The specific plan is as follows:

[0088] The monitoring state can be applied to boundary clocks (BCs) or ordinary clocks (OCs). For boundary clock node applications, multiple ports can be in the monitoring state at the same time.

[0089] The monitoring state can be entered through the state decision algorithm (in the embodiment of the present invention, specifically, it is entered when the packet synchronization channel failure event flag is set to valid, and it can be entered after the sub-domain decision, and the sub-domain decision may also be decided as Master), and it can also be manually set in the manual planning mode. If it is entered through the state decision algorithm, the corresponding port will transfer from the initial slave clock Slave state to the monitoring state. The packet synchronization channel monitoring mechanism (i.e., the monitoring state) proposed in the embodiment of the present invention adopts a solution based on the PTP measurement protocol, which determines whether the packet synchronization channel is working properly by monitoring and analyzing factors such as the type, quantity, integrity, and rationality of the timestamp of the synchronization message. Only when the port runs the slave clock protocol can it obtain complete synchronization messages and all timestamp information.

[0090] A port in the Monitoring state can transition to the Slave, Master, Passive, or Listening states. There are two scenarios for state transitions: 1) a decision event caused by the disappearance of a packet channel alarm; 2) a decision event caused by a change in a received notification message. If a decision is made by merging into the main decision domain, the port may transition to the Slave, Master, Passive, or Listening states. If the decision is still made by a sub-decision domain, the port will only transition to the Master state. See Figure 4 for details.

[0091] During the implementation process, the monitoring state is implemented by running the PTP slave clock protocol, but does not participate in node synchronization (specifically, the execution code of the corresponding synchronization function can be set to invalid or timeout response, etc.), while the existing slave clock state also runs the PTP slave clock protocol, which participates in node synchronization; this is also one of the essential differences between the monitoring state and the slave clock state proposed in the embodiment of the present invention. This is because, after the existing slave clock is finished running, it will perform clock deviation calculation, which will be used to adjust the local frequency or time; the port in the monitoring state of the technology of the present invention does not adjust the local time with the calculation result, but the calculation result will be used for channel monitoring analysis (for example: monitoring whether the packet synchronization channel fails, comparing the channel's packet timing with the frequency or time deviation of the local clock, etc.), and is only used for monitoring. Thus, the port can monitor the synchronization channel for failure events through the monitoring state; and, when the corresponding port is in the monitoring state, it can receive and process announcement messages (Announce), but the information is limited to the port sub-decision domain and will not be directly applied to the main decision domain, but is transmitted based on whether the sub-decision domain is bound to the main decision domain (see the explanation of the sub-domain decision framework later in the text for details);

[0092] If a port is manually configured to enter the monitoring state, the state can only be cleared manually and cannot be changed through the subdomain state decision. The port that is manually configured to be in the monitoring state also needs to be separated from the main decision-making and no longer participates in the decision-making of the main domain, and no longer transmits the received time source information to the main decision-making domain. The port subdomain does not process the received notification messages, nor does it initiate subdomain decisions, nor does it send notification messages to the outside. The port that is manually configured to be in the monitoring state will run the PTP measurement protocol slave port protocol and has all the monitoring functions described above (for example: monitoring whether the packet synchronization channel has failed, comparing the channel's packet timing with the frequency or time deviation of the local clock, etc.), and can be used to perform packet synchronization channel analysis and monitoring on the specified synchronization port.

[0093] To meet the needs of packet synchronization channel monitoring, the upstream synchronization port must operate in the master clock state. Ports operating in the monitoring state proposed in this embodiment of the present invention will not send Announce messages. The upstream synchronization node then determines the source state and sets the upstream synchronization port to the master clock state.

[0094] In the specific implementation of the present invention, the above monitoring state can be achieved by defining a new PTP port operating state type, or by redefining the blocking state Passive in the existing port operating state to meet the above requirements. Among the existing PTP port states, Passive is the most suitable; the Master state cannot run the PTP slave clock protocol and cannot effectively monitor the synchronization channel.

[0095] In the core framework modification of the present invention, in addition to the above-mentioned monitoring state model, another major modification is the proposal of the sub-domain decision framework.

[0096] The subdomain decision algorithm in the subdomain decision framework can be used to solve the decision scenario caused by the introduction of the packet synchronization channel failure event flag.

[0097] The existing source selection decision algorithm uses a single-domain decision framework, as shown in Figure 5. Each node represents a decision domain, and notification messages received by all synchronization ports (port 1, port 2, ..., port n) are compared and aggregated before a unified source selection decision is made. This solution is difficult to adapt to decision-making scenarios caused by information flow differences after the introduction of the packet synchronization channel failure event flag.

[0098] 6 , the subdomain decision algorithm under the subdomain decision framework proposed in an embodiment of the present invention is described as follows:

[0099] The nodes are divided into sub-decision domains according to the synchronization ports, and they correspond one to one with the number of ports;

[0100] The sub-decision domain and the main decision domain are dynamically bound and separated based on the validity and invalidity of the packet synchronization channel failure event flag. When the packet synchronization channel failure event flag is invalid, the port sub-decision domain corresponding to the synchronization channel is bound to the main decision domain and participates in the unified source selection decision of the main decision domain. When the packet synchronization channel failure event flag is valid, the port sub-decision domain corresponding to the synchronization channel is separated from the main decision domain and independently makes source selection decisions. The specific mechanism is as follows:

[0101] After binding to the main decision domain, the sub-decision domain transmits the received time source information to the main decision domain and accepts the unified source selection decision of the main decision domain. The main decision domain receives the time source information sent by the sub-decision domain and forms the time source information set of the main decision domain. The time source information set of the main decision domain can adopt the optimal time source information set (E best ) to organize information; the sub-decision domain separated from the main decision domain no longer transmits time source information to the main decision domain, but receives time source information from the main decision domain. The sub-decision domain forms a sub-decision domain time source information set based on the time source information received by the port. The time source information set of the sub-decision domain can adopt the port optimal time source information set (E rbest ) to organize information. However, when the Announce message received by the port in the separated sub-decision domain times out, it is necessary to receive the time source information from the main decision domain. This is used by the corresponding port to make decisions based on the time source information from the main decision domain after the packet synchronization channel fails, reestablish a master-slave relationship with the port with which it is connected, and restore the synchronization channel between the two ports. If the Announce message from the main decision domain is also lost, the optimal time source information is the local clock information, that is, the local clock is used as the time source to send information outward.

[0102] The change of the packet synchronization channel failure event flag of the corresponding port will immediately trigger the binding or separation between the sub-decision domain of the corresponding port and the main decision domain. If the time source information obtained by the corresponding port in the past was selected by the main decision domain as the time source information of the main decision domain, the corresponding separation action will trigger the main decision domain to re-select the source decision.

[0103] The source selection decision of the sub-decision domain adopts a new decision process, which can determine the new state and clear the packet synchronization channel failure event flag. The specific method is as follows:

[0104] When the sub-decision domain synchronization port receives external time source information that is better than the optimal time source information of the main decision domain (including the main decision domain has no time information sent, that is, the port of the main decision domain fails to receive the external announce message), the decision synchronization port works in the monitoring state.

[0105] When the sub-decision domain synchronization port receives time source information from the main decision domain that is better than the external time source information (including no external time source information, that is, no Announce message is received from the external port), the decision synchronization port state is the master clock (Master) state, the port group synchronization channel failure event flag is cleared, and the sub-decision domain will rebind to the main decision domain.

[0106] When a port in monitoring state detects that the packet channel failure event has disappeared, for example, synchronization messages are no longer lost and timestamps are stable, the packet synchronization channel failure event flag for that port is cleared. The sub-decision domain is then rebound to the main decision domain, which then re-determines the port's operating state. This state can be Master, Slave, or Passive Listening.

[0107] When the number of ports in the master decision domain or the status of slave ports changes, the status decision will be made again according to the existing 1588 protocol.

[0108] When the synchronization port of a sub-decision domain fails to receive external time source information, a notification message reception timeout occurs. The sub-decision domain time source information is cleared, and the synchronization port (specifically, the second node port B' in Embodiment 1 of the present invention) decides to clear the port group synchronization channel failure event flag and simultaneously transition to the listening state. The sub-decision domain then rebinds to the main decision domain.

[0109] When the main decision domain does not receive any other time source information and each unified source selection decision port is in the listening state, the sub-decision domain will maintain the synchronization port working in the monitoring state and the group synchronization channel failure event flag is valid.

[0110] The present invention also involves improvements to the recovery mechanism for packet synchronization channel failure events. Since the cause of packet synchronization channel failure events is mostly related to the operation of the synchronization port PTP protocol stack, automatic recovery of the failure can be attempted, which can improve the fault tolerance of the synchronization network. The recovery process is shown in Figure 7 and is explained as follows:

[0111] When the sub-decision domain decides that the synchronization port (specifically, port B' of the second node in this embodiment of the present invention) enters the monitoring state, it immediately sends information carrying the packet synchronization channel failure event flag to the upstream dual master clock port. For example, this information is carried in the idle bit of the DelayReq message frame header.

[0112] Then restart the PTP protocol stack of this port. The restart is only performed once and only for this port, without affecting the synchronization status of other ports of the node;

[0113] The upstream node's dual master clock port receives a message indicating a packet synchronization channel failure event and, after determining the event, restarts the PTP protocol stack on that port. This restart occurs only once, and a notification is displayed indicating the restart event. After the restart, a message carrying a response is sent to the downstream node. For example, this information can be carried in the idle bit of the DelayResp message header.

[0114] In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0115] Embodiment 1:

[0116] Embodiment 1 of the present invention provides a method for handling packet synchronization channel failure. In the embodiment of the present invention, in order to facilitate the description of the method features by different ports, descriptions such as port A of the first node and port B' of the second node are schematically given. In actual practice, the corresponding ports can be any customized description scheme. Therefore, the port numbers involved in the embodiment of the present invention do not have a limited meaning such as order or specific position, but are only used to distinguish the identities of ports. Similarly, port C' of the second node does not mean that there is a sequence relationship with port B' of the second node. It is only used to descriptively represent that they are two different ports of the second node. Therefore, if port C' of the corresponding second node is represented as port D' of the second node, it is also feasible in the embodiment of the present invention. In the embodiment of the present invention, it is assumed that the initial situation is that port A of the first node is connected to port B' of the second node, and port A of the first node operates in the master clock state and port B' of the second node operates in the slave clock state. For example, through the source selection decision algorithm, port A of the first node operates in the master clock state, and port B' of the second node operates in the slave clock state.

[0117] The source selection decision algorithm involves a node's PTP port receiving different notification messages and comparing the information carried in each message through a standardized process to select the optimal time source for tracking. The notification message carries time source information such as the source clock ID, priority 1, clock level, priority 2, and hop count. In this example, after receiving the notification message from the first node, announcing the source selection decision, the second node's port B' operates in slave mode.

[0118] As shown in FIG8 , the processing method according to the embodiment of the present invention includes:

[0119] In step 201, port B' of the second node starts packet synchronization channel monitoring. When a packet synchronization channel failure event is detected, the second node sets a packet synchronization channel failure event flag of port B' to valid.

[0120] The monitoring mechanism for packet synchronization channel failure falls within the scope of synchronization OAM. It defines a variety of failure events, such as PTP message loss, PTP message information anomalies, unreliable PTP timing, PTP input degradation, and PDV limit violations. These events are uniformly represented by the packet synchronization channel failure event flag (portPTCF), which is bound to the synchronization port. Whenever a failure event occurs in the channel on that port, the packet synchronization channel failure event flag becomes active.

[0121] In step 202 , the sub-decision domain of the port B′ of the second node is separated from the main decision domain of the second node, and the port B′ of the second node enters a monitoring state.

[0122] Nodes are divided into sub-decision domains according to the synchronization port (for example, port B' of the second node and port C' of the second node), and the sub-decision domains correspond to the number of ports one by one. The sub-decision domains and the main decision domain are dynamically bound and separated based on the validity and invalidity of the packet synchronization channel failure event flag. When the packet synchronization channel failure event flag is invalid, the port sub-decision domain corresponding to the synchronization channel is bound to the main decision domain and participates in the unified source selection decision of the main decision domain. When the packet synchronization channel failure event flag is valid, the port sub-decision domain corresponding to the synchronization channel is separated from the main decision domain and independently makes the source selection decision. The specific mechanism is as follows:

[0123] After binding to the main decision domain, the sub-decision domain transmits the received time source information to the main decision domain and accepts the unified source selection decision of the main decision domain;

[0124] The sub-decision domain separated from the main decision domain no longer transmits time source information to the main decision domain. However, when the Announce message received by the port corresponding to the separated sub-decision domain times out, the sub-decision domain is re-bound to the main decision domain and needs to receive the optimal time source information after comparison and decision by the main decision domain. When the packet synchronization channel fails, the corresponding port uses the time source information decided by the main decision domain to re-establish a master-slave relationship with the port in the other node with which it has a connection relationship, thereby restoring the synchronization channel between the two ports.

[0125] The change of the packet synchronization channel failure event flag of the corresponding port will immediately trigger the binding or separation between the sub-decision domain of the corresponding port and the main decision domain. If the time source information obtained by the corresponding port in the past was selected by the main decision domain as the time source information of the main decision domain, the corresponding separation action will trigger the main decision domain to re-select the source decision.

[0126] In step 203, the sub-decision domains of the other ports of the second node remain bound to the master decision domain of the second node; through the master domain decision algorithm, port C' of the second node becomes the new and only slave clock port of the second node; the sub-decision domain of port C' of the second node replaces the sub-decision domain of port B' of the second node to provide time source information to the master decision domain of the second node.

[0127] In the embodiments of the present invention, the main domain decision algorithm and the sub-decision domain algorithm are expressed in different places. Their essence is the source selection decision algorithm, and the difference lies in the scope of data objects calculated by the corresponding algorithm; for the sub-decision domain algorithm, its calculation scope is the time source information obtained by the port itself, while for the main decision domain algorithm, its calculation scope is the time source information obtained by all ports bound to it.

[0128] The embodiment of the present invention solves the problem of lack of a processing solution after a packet synchronization channel failure event is introduced, so that a synchronization OAM event is associated with a synchronization path decision, thereby improving the reliability of synchronization network operation.

[0129] The embodiment of the present invention associates the packet synchronization channel failure event in the synchronization path decision. For example, a connection is established between the source selection decision algorithm (expressed as a subdomain decision algorithm in the embodiment of the present invention) and the two layers of the synchronization measurement protocol (i.e., the method content associated with the packet synchronization channel failure event flag). This enables the packet synchronization channel failure event information to be referenced in the synchronization port state decision (including the slave clock state Slave, the master clock state Master, the blocking state Passive and the listening state Listening, as well as the monitoring state proposed in the embodiment of the present invention) to select a normal synchronization channel path. The packet synchronization channel failure event can also be cleared (i.e., the packet synchronization channel failure event flag is adjusted to invalid) through the subdomain decision algorithm in the corresponding decision scenario.

[0130] As previously explained at the beginning of the present invention, since the cause of the packet synchronization channel failure event is mostly related to the operation of the synchronization port PTP protocol stack, it is possible to attempt to automatically recover from the failure, which can improve the fault tolerance of the synchronization network. Referring to Figure 14, the recovery process is as follows: after the port B' of the second node enters the monitoring state, as shown in Figure 9, it also includes:

[0131] In step 301, the second node sends packet synchronization channel failure event information to the first node; for example, bit 7 of the 7th byte in the delay request (DelayReq) message frame header carries the packet synchronization channel failure event information and sends it to the first node, and bit 7=1 indicates valid.

[0132] In this embodiment of the present invention, the corresponding second node completes the sending of the packet synchronization channel failure event information through its port B' and the connection channel between port B' and the port A of the first node.

[0133] In step 302, the second node restarts the PTP protocol stack of port B' and stops monitoring the synchronization channel, for example, by simultaneously reporting a "PTP Reset" event trigger of port B'.

[0134] In the specific implementation process, it is usually performed by restarting the PTP protocol stack of port B' in the second node once and recording the port PTP protocol stack restart event. The corresponding recording of the port PTP protocol stack restart event is to eliminate the problem of the PTP protocol stack when further in-depth analysis of the cause of the problem is carried out later.

[0135] In step 303, the first node receives the packet synchronization channel failure event information sent by the second node, restarts the PTP protocol stack of port A in the first node, and sends packet synchronization channel failure event response information to the second node.

[0136] In step 304, the port B' of the second node receives the packet synchronization channel failure event response information fed back by the first node and restarts the monitoring of the synchronization channel.

[0137] By performing the monitoring, stopping, and restarting process of the synchronization channel in the method of steps 301 to 304, it is possible to avoid misjudgment during the restart of the PTP protocol stack, thereby affecting the analysis of the cause of the fault.

[0138] If the port B' of the second node does not receive the packet synchronization channel failure event response information fed back by the first node for a long time, the synchronization channel monitoring will be restarted after the timeout. The judgment time can be adjusted according to different systems.

[0139] In the embodiment of the present invention, the method process of steps 201 to 203 is further continued. If the failure of the packet synchronization channel associated with the port B' of the second node is successfully repaired, the method further includes:

[0140] The second node sets the packet synchronization channel failure event flag of its port B' to invalid; the synchronization subdomain of the second node's port B' re-establishes a binding relationship with the main decision domain and initiates the subdomain decision algorithm. This allows the system to obtain time source information from the repaired packet synchronization channel of the second node's port B' and the time source information obtained by the second node's port C', and then determine the more optimal time source information as the time source information for the second node's main decision domain. This is because, in the previous round of the source selection decision algorithm, port C' did not defeat port B'. Therefore, the historical time source information of port B' is more optimal than that of port C'.

[0141] Among them, the successful repair of the failure of the packet synchronization channel associated with the port B' of the second node can be completed by the second node restarting the PTP protocol stack of the port B' in the above-mentioned step 302, or it can be other forms of restoration to normal for one or more of the above-mentioned failure events such as PTP message loss, PTP message information abnormality, PTP timing unreliability, PTP input degradation, PDV limit violation, etc.

[0142] In a specific implementation, the packet synchronization channel failure event is further subdivided into a notification message timeout. In this case, the execution process of the provided method has its own unique characteristics. As shown in FIG10 , a timeout occurs when the port B′ of the second node receives the notification message of the first node. The method further includes:

[0143] In step 401, the sub-decision domain time source information of the port B' of the second node is cleared, the decision port B' switches to a listening state, and the packet synchronization channel failure event flag of the port B' of the second node is set to invalid.

[0144] In step 402, the sub-decision domain of port B' of the second node rebinds to the main decision domain of the second node, and accepts the time source information obtained by the main decision domain of the second node from port C' of the second node.

[0145] In step 403, the second node sends the time source information acquired by port C' of the second node to the first node through the connection between port B' and port A of the first node.

[0146] If steps 201-203 are also prepared to resolve the packet synchronization channel failure event, and then rebind the sub-decision domain of the port B' of the second node to the main decision domain, and incorporate the time source information calculated by the sub-decision domain itself through the sub-decision domain into the main decision domain to re-trigger the time source decision of the main decision domain; then the technical performance of the above steps 401-403 is that the port B' of the second node has lost the possibility of restoring the packet synchronization channel, or it can be understood that in order to put the corresponding port B' of the second node into effective use as soon as possible, therefore, the execution actions of the above steps 401-403 are carried out, and the time source information of the sub-decision domain of the port B' of the second node is cleared, which is also to avoid the invalid time source information brought by the sub-decision domain of the corresponding port B' of the second node when rebinding the second node main decision domain, resulting in invalid source selection decision calculation on the main decision domain side.

[0147] The process from step 401 to step 403 is exactly the opposite of the above process. That is, when port B' is able to receive the notification message and receives one or more notification messages, for example, due to topology adjustment or time source switching upstream of the second node, as shown in FIG11 , the method further includes:

[0148] In step 501, the port B' sub-decision domain determines the optimal time source from one or more received notification messages, updates the time source information of the sub-decision domain, maintains the monitoring status of port B', and maintains the packet synchronization channel failure event flag to be set to the valid state.

[0149] If the notification message can still be received, it means that the connection with port A of the first node is still maintained, but at this time, the packet synchronization channel has not been restored, so the corresponding port B' sub-decision domain only makes the decision on the optimal time source within a private range (that is, separated from the main decision domain).

[0150] In step 502, after waiting for the second node's packet synchronization channel monitoring to confirm that the packet synchronization channel is restored, port B' is re-bound to the main decision domain so as to re-determine the port status.

[0151] Since, in an embodiment of the present invention, the packet synchronization channel status fails when the port B' of the second node is used as a slave clock, after the sub-decision domain decision is made through the received notification message in the above-mentioned scenario of steps 501-502, the original master-slave relationship between the port B' of the second node and the port A of the first node will be maintained unchanged, but it cannot guarantee that the packet synchronization channel will return to normal. If the packet synchronization channel failure event flag is cleared without judgment, the second node will make a decision to track the upstream through port B'. The packet synchronization channel monitoring mechanism will detect the failure of the packet synchronization channel again, and the second node will switch the synchronization path again, causing synchronization oscillation. Therefore, when the port B' of the second node is in the monitoring state and port B' receives the notification message, it is necessary to adopt this technical solution to ensure the stability of the synchronization path switching.

[0152] The above steps 501-502 and steps 401-403 constitute two detailed branch processes in the execution process of steps 201-203 of the embodiment of the present invention. That is, the above two branches can be understood as one of the specific implementation situations after port B' of the second node enters the monitoring state in step 202.

[0153] As one implementation scheme of the embodiment of the present invention, for port B' of the second node, if its associated sub-decision domain and the main decision domain of the second node are to be re-bound after the separation action of step 202 is performed, in addition to the timeout of the notification message received by the second node's associated port B' in step 401 and the restoration of the monitoring confirmation packet synchronization channel in step 502, there is another situation where the time source information received by the newly bound port C' of the main decision domain of the second node is better than the time source information previously received by the sub-decision domain of port B' of the second node, as shown in FIG12, the method further includes:

[0154] In step 601, the port B' of the second node is set to the master clock state, the packet synchronization channel failure event flag is set to the invalid state, and the sub-decision domain of the port B' is bound to the master decision domain of the second node.

[0155] In step 602, the second node sends the time source information obtained from the primary decision domain of the second node to the port A of the first node via the port B' via a notification message.

[0156] In step 603, the first node switches the working state of its port A from the historical master clock state to the slave clock state.

[0157] The motivation for triggering the above-mentioned third method of restoring the rebinding of the sub-decision domain of port B' of the second node and the main decision domain of the second node is that it is found that the time source information historically received by the sub-decision domain of port B' of the second node is not as good as the time source information from port C' of the second node determined in step 203 of the embodiment of the present invention. At this time, if port B' of the second node is set to the master clock (Master) state as described in step 601, then port B' of the second node does not need to worry about whether the failure of the packet synchronization channel is effectively resolved, because port B' of the second node has become a dominant node at this time. Even if the failure of the packet synchronization channel is not resolved, it will have no effect on it as the master clock (Master).

[0158] In addition, as another method process that is similar to the results of steps 601-603 above, but whose method logic is different, and which can be considered as continuing from step 502, as shown in FIG13, if it is detected that the packet synchronization channel of the second node port B' is restored, the method further includes:

[0159] In step 701, the packet synchronization channel failure event flag of the second node port B' is cleared, and the sub-decision domain of the second node port B' is re-bound to the main decision domain.

[0160] In step 702, if the time source information of the main decision domain is better than that of the sub-decision domain synchronization port of the second node port B' receiving the external time source information, the second node port B' is determined to operate in the master clock state.

[0161] As a supplement to the logical branches of the above methods, compared with the situations where steps 401-403, 501-502, and 601-603 occur, a worse situation may occur, that is, the port C' of the second node selected in the above step 203 also times out the receiving channel message (that is, a synchronization channel failure event occurs) and the packet synchronization channel failure event flag of the corresponding port C' is invalid. The method also includes: the main decision domain of the second node decides that the bound port C' enters the listening state, and the port B' sub-decision domain maintains the port monitoring state and maintains the packet synchronization channel failure event flag of the port B' as valid.

[0162] Example 2:

[0163] In the embodiment of the present invention, the implementation mechanism characteristics of the sub-decision domain are separately extracted and explained relatively completely, and the explanation content of the corresponding mechanism can be applied to other embodiments of the present invention.

[0164] The sub-decision domain algorithm only applies to decisions about the operating status of synchronization ports that have been unbound from the main decision domain. Typically, after a node boots up, the synchronization port sub-decision domain is bound to the main decision domain by default, and the synchronization port operating status is determined by the main decision domain. Only after the packet synchronization channel monitoring mechanism is activated and a packet synchronization channel failure event occurs will an independent sub-decision domain be formed, requiring the sub-decision domain algorithm to be run.

[0165] The datasets maintained by the sub-decision domain include:

[0166] The time source information received by the subdomain associated port through the notification message;

[0167] The optimal time source information determined by the node's main decision domain;

[0168] It is important to note that a sub-decision domain separated from a node's main decision domain does not need to transmit the optimal time source information determined by the sub-decision domain to the node's main decision domain. However, when a sub-decision domain rebinds to the main decision domain, it must send the optimal time source information it calculated (limited to the sub-decision domain) to the main decision domain, thereby triggering the main decision domain to perform a new round of source selection algorithm.

[0169] The sub-decision domain only makes decisions on the working status of the associated ports and remains independent of other sub-decision domains, and the decision results are also unrelated. The main decision domain will make a unified decision for all bound ports;

[0170] The sub-decision domain determines the port's operating status, including monitoring and master clock status. When determining the port's master clock status, the port's packet channel failure event flag is cleared. The master decision domain determines a maximum of one slave clock, an indefinite number of master clocks, and blocked ports, and does not operate on the port's packet channel failure event flag.

[0171] The decision scenarios that the sub-decision domain needs to handle include the following logic in some instances:

[0172] When a port receives new time source information, the sub-decision domain determines a scenario where the time source is superior to the local clock.

[0173] When a port receives new time source information, the sub-decision domain determines a decision scenario in which the time source information constituted by the local clock is no better than that of the local clock.

[0174] The time source information received by the port is better than the optimal time source information of the main decision domain;

[0175] The time source information received by the port is not better than the optimal time source information of the primary decision domain;

[0176] Decision processing after the sub-decision domain receives the notification message timeout;

[0177] Decision processing after the optimal time source of the main decision domain is lost;

[0178] For the corresponding sub-decision domain, in the decision scenario of receiving the time source information, the corresponding decision logic can be implemented with reference to FIG15. In FIG15, in order to indicate that the corresponding port does not specifically refer to a certain port, port r is used to represent it, where r represents a possible general port identifier, for example, r is 1, 2, 3, and so on. Compared with Example 1, the embodiment of the present invention introduces the concept of logical superiority and the technical concept of local clock (i.e., the clock signal generated by the local crystal oscillator) into the decision logic corresponding to FIG15. In the comparison decision algorithm in the BMC, the corresponding conclusion will form superiority or logical superiority, which will form different decision results in the main decision domain (this is an existing protocol mechanism and will not be elaborated in detail in the implementation scheme of the present invention).

[0179] In step 801 , it is determined whether the packet synchronization channel failure event flag of port r is valid. If it is valid, the process proceeds to step 802 ; if it is invalid, the process proceeds to step 809 .

[0180] In step 802 , it is determined whether the local clock is superior or logically superior to the optimal clock determined by the main decision domain. If so, the process proceeds to step 803 ; otherwise, the process proceeds to step 806 .

[0181] In step 803 , it is determined whether the local clock is superior or logically superior to the optimal clock determined by the port r sub-decision domain. If so, the process proceeds to step 805 ; otherwise, the process proceeds to step 804 .

[0182] In step 804, the sub-decision domain of port r decides to enter the monitoring state.

[0183] This can be understood as a logic for entering the monitoring state in the current scenario, similar to the step 202 in Example 1, in which port B' of the second node enters the monitoring state. That is, port B' of the second node enters the monitoring state only after the judgment condition of step 804 is met.

[0184] In step 805, port r decides to be in the master clock state, sends local time source information (the local time source information is generated from the local clock), and clears the port r failure flag.

[0185] In step 806 , it is determined whether the main decision domain clock is superior or logically superior to the optimal clock determined by the port r sub-decision domain. If so, the process proceeds to step 807 ; otherwise, the process proceeds to step 808 .

[0186] In step 807, port r is decided to be in the master clock state, sends the optimal time source determined by the master decision domain as its own time source information, and clears the port r failure flag.

[0187] In step 808, the sub-decision domain of port r decides to enter the monitoring state.

[0188] In step 809, the decision logic of the main decision domain is entered.

[0189] Example 3:

[0190] The embodiment of the present invention further combines the signaling protocol and specifically presents the technical solution of embodiment 1 in another form of node port representation. The method includes:

[0191] As shown in Figure 14, port A of the first node is connected to port B' of the second node. Through source selection, port A of the first node works in the master clock state, while port B' of the second node works in the slave clock state.

[0192] Port 1 of node 2 starts monitoring the packet synchronization channel. Upon detecting a packet synchronization channel failure event, node 2 sets the packet synchronization channel failure event flag (portDS.CF) of port 1 to "1," i.e., portDS.CF = 1. As shown in Figure 16 , portDS.CF is the port's attribute data and can be associated with the corresponding field in flagField that carries the packet synchronization channel failure information.

[0193] The sub-decision domain of port 1 of node 2 is immediately separated from the main decision domain of node 2, and the sub-domain decision algorithm is started. The result of the sub-domain decision algorithm is that port 1 of node 2 enters the monitoring state. The decision process is shown in Figure 15.

[0194] At this point, the sub-decision domains of port 2, port 3, and port 4 of node 2 remain bound to the master decision domain. Through the master decision domain's source selection algorithm, port 3 becomes the new and only slave port of node 2. Since the sub-decision domain of port 1 of node 2 no longer provides time source information to the master decision domain of node 2,

[0195] After the port 1 of node 2 decides to enter the monitoring state, it immediately sends the packet synchronization channel failure event information to node 1 through bit 7 of the 7th byte in the delay request (DelayReq) message frame header, bit 7=1 indicates valid, and the definition of each byte of the corresponding DelayReq message is shown in Figure 17. Then, port 1 of node 2 restarts the PTP protocol stack of this port once. Node 1 receives the packet synchronization channel failure event information, detects that the synchronization channel failure event flag is valid, and also restarts the PTP protocol stack of port 2 of this node once, and sends the packet synchronization channel failure event response information to node 2 through bit 7 of the 7th byte in the delay response (DelayResp) message frame header; and port 1 of node 2 continues to monitor the synchronization channel;

[0196] Next, we will present the possible technical branches of the complete solution in several situations:

[0197] If the recovery mechanism is successful, port 1 of node 2 detects the restoration of the synchronization channel failure through the packet synchronization channel monitoring mechanism and sets portDS.CF of port 1 to 0. The synchronization subdomain of port 1 of node 2 is immediately bound to the master decision domain, and the source selection decision of node 2's master decision domain is initiated. Based on the networking in the example, if the time source and networking remain unchanged, the slave clock port of node 2 will be restored to port 1. Manual restoration of the synchronization channel failure will follow the same binding and rescheduling decision process.

[0198] If port 1 of node 2 times out when receiving a notification message from node 1, the time source information in port 1's sub-decision domain is immediately cleared, port 1 enters the listening state, and portDS.CF = 0. The sub-decision domain of port 1 rebinds to the main decision domain of node 2 and accepts the time source information from the main decision domain.

[0199] If a topology adjustment or time source switch occurs upstream of node 2, causing port 1 to receive a different notification message, the port 1 sub-decision domain only needs to determine the optimal time source in the received message, update the sub-domain information, maintain the monitoring status of port 1, and maintain portDS.CF = 1.

[0200] If the synchronization network topology is adjusted or the time source is switched, so that the time source information received by the port bound to the main decision domain of node 2 (port 2, port 3, or port 4) is better than the time source information received by the sub-decision domain of port 1, then decision port 1 works in the master clock (Master) state, makes portDS.CF = 0, and binds to the main decision domain.

[0201] If the port bound to the main decision domain of node 2 times out due to a notification message reception failure, the decision domain of port 1 will enter the monitoring state and maintain portDS.CF=1.

[0202] Example 4:

[0203] Figure 18 is a schematic diagram of the architecture of a device for processing packet synchronization channel failure according to an embodiment of the present invention. The device for processing packet synchronization channel failure according to this embodiment includes one or more processors 21 and a memory 22. Figure 18 uses one processor 21 as an example.

[0204] The processor 21 and the memory 22 may be connected via a bus or other means. FIG18 takes the bus connection as an example.

[0205] The memory 22, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs and non-volatile computer-executable programs, such as the method for handling packet synchronization channel failure in Example 1. The processor 21 executes the method for handling packet synchronization channel failure by running the non-volatile software programs and instructions stored in the memory 22.

[0206] The memory 22 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some embodiments, the memory 22 may optionally include a memory remotely located relative to the processor 21, and such remote memory may be connected to the processor 21 via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0207] The program instructions / modules are stored in the memory 22 and, when executed by the one or more processors 21, execute the method for handling packet synchronization channel failure in the above-mentioned embodiment 1, for example, execute the steps shown in Figures 8 to 12 described above.

[0208] It is worth noting that the information interaction, execution process, etc. between the modules and units within the above-mentioned devices and systems are based on the same concept as the processing method embodiment of the present invention. The specific content can be found in the description of the method embodiment of the present invention and will not be repeated here.

[0209] Those skilled in the art will understand that all or part of the steps in the various methods of the embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a disk or an optical disk, etc.

[0210] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Images