Fault processing method and system for voice dial testing

Abstract

The invention provides a fault processing method and system for voice dial testing, and belongs to the technical field of communication network operation and maintenance, and the method comprises the steps: receiving a fault request from a signaling system; performing fault type identification on the fault requests in a preset cache period, and merging and compressing the fault requests of the same fault type; determining a first fault request in the merge set, and executing a routing tracking operation on a destination IP on a main / standby data communication equipment switch corresponding to a source IP of the first fault request to obtain current network state information; according to the current network state information and the historical network state information, whether routing abnormity and time delay abnormity exist or not is judged; determining a fault type according to a comparison result, and generating real-time alarm information; and in a preset time period, sending the real-time alarm information to a manager terminal. According to the invention, on the basis of real-time routing tracking, historical alarm comparison and time delay anomaly detection, large-scale fault requests can be quickly and accurately processed in a short time.

Description

Technical Field

[0001] The present invention relates to the technical field of communication network operation and maintenance, and in particular to a fault handling method and system for voice dialing. Background Art

[0002] With the continuous expansion of the scale of telecommunications networks and the continuous improvement of business complexity, the rapid discovery and location of network equipment faults has become a major challenge in the field of operation and maintenance. At present, the fault detection of telecommunications networks mainly relies on the alarm information and performance logs of the equipment itself. However, the number of these alarms is huge and scattered, making it difficult to quickly locate the root cause of the fault. Especially in large-scale networks, a large number of fault requests may appear in a short period of time. The traditional technology is inefficient in polling and retrieving historical alarms, and cannot meet the "one fifty" operation and maintenance timeliness requirements (that is, reporting faults within 1 minute, locating faults within 5 minutes, and restoring faults within 10 minutes). In addition, when processing fault requests, the existing technology usually performs network status detection operations (such as ping and trace) for each request separately, resulting in a large number of system resources being occupied when large-scale faults occur in a short period of time, and the response delay is significantly increased. It may even affect the performance of the switch due to frequent logins to data communication devices. At the same time, the existing technology lacks an effective merging and compression mechanism for fault requests, resulting in a large number of repeated requests being redundantly processed, further increasing the system burden. These problems not only reduce the efficiency of fault location, but may also cause key faults to be delayed in processing, affecting business continuity and user experience.

[0003] Therefore, how to quickly and accurately handle large-scale fault requests in a short period of time has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] The present invention provides a voice dialing fault processing method, system, electronic device and storage medium, which are used to solve the defects in the prior art and realize rapid and accurate processing of large-scale fault requests in a short time.

[0005] The present invention provides a voice dialing fault processing method, comprising the following steps: Receive a fault request from a signaling system, wherein the fault request includes a source IP and a destination IP; Identify the fault type of the fault request within a preset cache period, and merge and compress the fault requests of the same fault type to obtain a merged set; Determine the first fault request in the merged set, and perform a route tracing operation on the destination IP on the primary and standby data communication device switches corresponding to the source IP of the first fault request to obtain current network status information; According to the current network status information and the historical network status information, determine whether there is a routing anomaly and a delay anomaly; Determine the fault type according to the comparison result, and generate real-time alarm information including the fault type, the source IP and the destination IP; The real-time alarm information is sent to the administrator terminal within a preset time period.

[0006] According to a fault handling method for voice dialing provided by the present invention, the current network status information includes the current network connectivity status and the current delay value; the route tracing operation of the destination IP is performed on the primary and standby data communication device switches corresponding to the source IP of the first fault request to obtain the current network status information, specifically including: Determine the current network connectivity status according to the route tracing result, wherein the route tracing result is obtained after performing a route tracing operation on the destination IP on the primary and standby data communication device switches; When it is determined that the current network connectivity state is a connectivity state, a current delay value is obtained.

[0007] According to a voice dialing fault processing method provided by the present invention, determining the current network connectivity status according to the route tracing result specifically includes: When it is determined that the route tracing result is that the destination IP address can be reached, or when there is no interruption node in the route tracing result, determining that the current network connectivity state is a connectivity state; When it is determined that the route tracing result is that the destination IP address cannot be reached, or when there is an interrupted node in the route tracing result, it is determined that the current network connectivity state is a disconnected state.

[0008] According to a voice dialing fault processing method provided by the present invention, judging whether there is a routing anomaly and a delay anomaly based on the current network status information and the historical network status information specifically includes: When it is determined that the current network connectivity state is a non-connectivity state, determining that a routing anomaly exists; When it is determined that the current network connectivity state is a connectivity state, searching the historical network status information for a corresponding historical routing node for each current routing node in the current network status information; Calculating the delay difference between the current delay value of each current routing node and the historical delay value of the corresponding historical routing node; When any of the delay differences is greater than a preset delay threshold, it is determined that a delay anomaly exists.

[0009] According to a voice dialing fault processing method provided by the present invention, the method further includes: When the number of fault requests is greater than a preset first number, the real-time route tracing instructions and the periodic route tracing instructions initiated by the signaling system are processed concurrently on the primary and standby data communication equipment switches, wherein the priority of the real-time route tracing instructions is higher than the priority of the periodic route tracing instructions.

[0010] According to a voice dialing fault processing method provided by the present invention, the method further includes: Map the source IP and destination IP to the corresponding network element name through the pre-established service IP and network element correspondence table; Searching a preset historical alarm database according to the network element name to obtain historical alarm data; generating a link for viewing the route tracing operation and the historical alarm data; The link is added to the real-time alert information.

[0011] The present invention also provides a voice dialing fault processing system, comprising the following modules: A receiving module, used for receiving a fault request from a signaling system, wherein the fault request includes a source IP and a destination IP; A processing module, used to identify the fault type of the fault request within a preset cache period, and merge and compress the fault requests of the same fault type to obtain a merged set; The processing module is further used to determine the first fault request in the merged set, and perform a route tracing operation on the destination IP on the primary and standby data communication device switches corresponding to the source IP of the first fault request to obtain current network status information; The processing module is further used to determine whether there is a routing anomaly and a delay anomaly according to the current network status information and the historical network status information; An alarm generation module is used to determine the fault type according to the comparison result, and generate real-time alarm information including the fault type, the source IP and the destination IP; The alarm sending module is used to send the real-time alarm information to the management terminal within a preset time period.

[0012] The present invention also provides an electronic device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the fault handling method for voice dialing described in any one of the above is implemented.

[0013] The present invention also provides a non-transitory computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the fault handling method of voice dialing described in any one of the above is implemented.

[0014] The present invention also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the fault handling method of voice dialing described in any one of the above is implemented.

[0015] In summary, one or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages: By receiving fault requests from the signaling system and extracting the source IP and destination IP, the network fault can be accurately triggered and initially located. By identifying the fault type of the fault request within the preset cache period and merging and compressing the requests of the same type, the amount of redundant alarm processing can be significantly reduced, avoiding the waste of system resources and response delays caused by large-scale repeated requests in a short period of time. By giving priority to the first fault request in the merged set and performing route tracking operations on its corresponding active and standby data communication equipment switches, the real-time status detection of the core fault path can be focused to ensure the priority and efficiency of network diagnosis. By comparing and analyzing the routing jump node delay and path integrity of the current network status information with historical data, abnormal fluctuations or interruptions can be quickly identified to improve the accuracy and timeliness of fault judgment. By dynamically generating real-time alarm information containing specific fault types, source IPs and destination IPs based on the comparison results, clear and actionable data support can be provided to management personnel. By pushing the alarm information to the terminal within the preset time period, the operation and maintenance timeliness requirements are strictly met, and large-scale fault requests can be quickly and accurately processed in a short time. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1 This is one of the flow charts of the fault handling method of voice dialing provided by the present invention.

[0018] Figure 2 This is the second flow chart of the fault handling method of voice dialing provided by the present invention.

[0019] Figure 3 This is the third flow chart of the fault handling method of voice dialing provided by the present invention.

[0020] Figure 4 This is the fourth flow chart of the fault handling method of voice dialing provided by the present invention.

[0021] Figure 5It is a structural schematic diagram of the fault handling system of voice dialing test provided by the present invention.

[0022] Figure 6 It is a structural schematic diagram of the electronic device provided by the present invention. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0024] It should be noted that, in the description of the present invention, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "include one..." do not exclude the existence of other identical elements in the process, method, article or device including the elements. The orientation or positional relationship indicated by the terms "upper", "lower", etc. is based on the orientation or positional relationship shown in the accompanying drawings, and is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the system or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances.

[0025] The terms "first", "second", etc. in the present invention are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present invention can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" means at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0026] Combine the following Figure 1-Figure 6 The present invention describes a voice dialing fault processing method, system, electronic device and storage medium.

[0027] Figure 1FIG. 1 is a flow chart of a method for troubleshooting voice dialing provided by the present invention. Figure 1 As shown, including but not limited to the following steps: Step 101: Receive a fault request from a signaling system, where the fault request includes a source IP and a destination IP.

[0028] In this embodiment, in order to quickly receive and process fault information, the system first receives a fault request from the signaling system in step 101, which carries key fields such as source IP and destination IP. The reason for setting up this receiving link in the system is that the signaling system provides a data interface based on the RESTful protocol to the outside world, and ensures the security and timeliness of data transmission by limiting the IP address of the caller and configuring the HTTPHeader format.

[0029] Specifically, when the system is deployed, it will disclose the request address (for example, "http: / / IP address:port / nexwise_faultLocation / faultAlarmInfo") to the signaling system according to the pre-written interface document, and set the constraint of transmitting data in JSON format to ensure that the system can quickly parse the "source IP", "destination IP", "request serial number", "fault occurrence time" and other fields in the fault request through the HTTP POST method, and map them to the data structure required for the subsequent processing flow. Due to the use of the RESTful interface, when the signaling system pushes the fault information in the JSON message format, the system can encrypt and authenticate sensitive data in the parsing link, and perform performance scheduling for high-concurrency scenarios to ensure that the fault request will not be blocked or lost due to the influx of a large number of requests in a short period of time.

[0030] Through such a design, step 101 not only ensures real-time intercommunication with the signaling system, but also lays a data foundation for subsequent fault type identification, route tracing and real-time alarm information generation, thereby completing the capture and dispatch of business anomalies within minutes. The final effect is that any fault request from the signaling system can be accurately and quickly received and parsed, and the entire system can obtain key fields in the first place when facing large-scale network failures, and then start a series of actions such as merging and compression, route tracing and alarm reporting, which speeds up the efficiency of fault location and recovery.

[0031] Step 102: Identify the fault type of the fault request within a preset cache period, and merge and compress the fault requests of the same fault type to obtain a merged set.

[0032] In step 102, in order to cope with a large number of fault requests that may appear in a short period of time while ensuring the performance of rapid alarm reporting, the system pre-sets a cache period for identifying the fault type of the received fault requests and implementing merging and compression.

[0033] Specifically, when the system receives multiple fault requests with the same source IP or destination IP, or belonging to the same network category within the cache cycle, it will first identify the fault types of these fault requests based on key features (such as the attributes of the source network element or destination network element). After confirming that they belong to the same or similar fault types, all fault requests of the same type are merged into one "first fault request" to form a merged set.

[0034] The reason for this is that if routing tracing and alarm dispatching are performed separately for each fault request, the system will consume a lot of resources and may also delay the timely reporting of faults; by merging and compressing requests of the same fault type within the cache cycle, it can significantly reduce repeated routing tracing operations (i.e. trace operations, the trace that appears in the subsequent embodiments represents routing tracing) and multiple dispatching processes, speed up the fault detection link and optimize the overall efficiency of alarm processing. The final effect is that the merged set only needs to perform further routing tracing and historical alarm retrieval on the first fault request, which not only ensures the timeliness of alarm reporting within one minute, but also avoids the performance waste caused by repeated processing in the system in high concurrency scenarios.

[0035] Step 103: determine the first fault request in the merged set, and perform a route tracing operation on the destination IP on the active and standby data communication device switches corresponding to the source IP of the first fault request to obtain current network status information.

[0036] In step 103, the reason why it is necessary to "determine the first fault request in the merged set, and perform a route tracing operation on the destination IP on the primary and backup data communication device switches corresponding to the source IP of the first fault request" is that after completing the merging and compression of the fault requests, only the first fault request can truly reflect the earliest and most representative abnormal situation in the merged set. This can avoid repeated trace operations on multiple fault requests of the same type.

[0037] In one possible implementation, refer to Figure 2 , Figure 2 FIG. 2 is a flow chart of the fault handling method of the voice dialing test provided by the present invention. Figure 2 As shown, step 103 specifically includes steps 201-202: Step 201: Determine the current network connectivity status according to the route tracing result, wherein the route tracing result is obtained after executing the route tracing operation on the destination IP on the primary and backup data communication device switches.

[0038] In step 201, the reason for determining the current network connectivity status based on the route tracing result is to determine whether there is a link interruption or other abnormalities at the first time, so as to facilitate rapid troubleshooting and timely alarm.

[0039] In a possible implementation, step 201 specifically includes the following steps: When it is determined that the route tracing result is that the destination IP address can be reached, or when there is no interruption node in the route tracing result, it is determined that the current network connectivity state is a connectivity state.

[0040] When it is determined that the route tracing result is that the destination IP address cannot be reached, or when there is an interrupted node in the route tracing result, it is determined that the current network connectivity state is a disconnected state.

[0041] Specifically, after completing the route tracking instruction, the system will detect each hop from the source IP to the destination IP in turn, and obtain the IP address and delay information of each hop; if it can finally reach the destination address and there is no " " or other unresolved interrupted nodes, the system marks the current network connectivity status as connected, otherwise it is judged as disconnected. The effect of this is that the system can accurately identify the network status in the shortest time. Once the route tracking results show that the target address cannot be reached or there is an interrupted node, it can provide key basis for analyzing route anomalies and delay anomalies in subsequent steps, thereby meeting the operation and maintenance requirements of completing fault reporting and positioning within minutes.

[0042] Step 202: When it is determined that the current network connectivity state is a connectivity state, a current delay value is obtained.

[0043] In step 202, only when it is determined that the current network connectivity state is connected, the system will obtain the current delay value from the route tracking result. The reason is that when the link is reachable, it is necessary to further evaluate the transmission performance of the reachable path so as to compare the historical delay data in the subsequent process to determine whether there is an abnormality. The specific method is to parse the trace output executed by the main and standby data communication equipment switches, extract the delay information of each hop node from the source IP to the destination IP, and record or archive these delay values ​​according to the timestamp. By obtaining and saving the current delay value in this way, the system can compare it with the previous historical delay point by point in the next step. Once a large abnormal increment is found, it can quickly issue a warning or trigger a fault alarm, so that the potential high delay risk can be captured in time when the network connectivity is still normal, providing an important basis for subsequent rapid troubleshooting and business recovery.

[0044] Step 104: Determine whether there is a routing anomaly or a delay anomaly based on the current network status information and the historical network status information.

[0045] In step 104, the system determines whether there are routing anomalies and delay anomalies based on the current network status information and historical network status information. The fundamental reason is that the network health cannot be fully evaluated based on the results of a single routing trace. The historical route nodes and delay data in adjacent time periods must be combined to accurately identify possible performance deterioration or link failure.

[0046] In one possible implementation, refer to Figure 3 , Figure 3 FIG. 3 is a flow chart of the fault handling method of the voice dialing test provided by the present invention, as shown in FIG. Figure 3 As shown, step 104 specifically includes steps 301-304: Step 301: When it is determined that the current network connectivity state is a disconnected state, it is determined that there is a routing anomaly.

[0047] In step 301, the core network integrated network management system directly determines that there is a routing anomaly when determining that the current network connectivity state is a disconnected state, because one of the core goals of service dialing is to quickly identify faults that affect user communications, and the loss of network connectivity usually means that the network path is interrupted or the equipment is abnormal, and an alarm needs to be triggered immediately and the fault location process needs to be entered.

[0048] Specifically, after executing the trace operation, the system will analyze the path information returned by the trace. If it finds that the target IP is unreachable or a " " mark, the current network connectivity status is immediately determined to be disconnected, and the fault request is marked as a routing anomaly; in addition, to ensure the accuracy of the judgment, the system will also compare historical trace records to confirm whether the path has ever been reachable, so as to eliminate misjudgments caused by short-term congestion or policy changes. This design enables the system to identify whether a serious fault has occurred in the core node of the network in the shortest time and quickly report an alarm, avoiding long-term service interruptions caused by connectivity problems, improving overall operation and maintenance efficiency, and providing a reliable fault classification basis for subsequent steps, ensuring that different types of faults can be accurately handled and recovered in a timely manner.

[0049] Step 302: When it is determined that the current network connectivity state is a connectivity state, a corresponding historical routing node is searched for each current routing node in the current network status information from the historical network status information.

[0050] In step 302, the core network integrated network management system searches for the corresponding historical routing node for each current routing node in the current network status information from the historical network status information when the current network connectivity status is connected. The main purpose is to further analyze whether the network path has changed while maintaining connectivity, so as to detect potential abnormal situations and provide a comparison benchmark for subsequent delay analysis.

[0051] Specifically, when the system determines that the target IP is reachable, it will search for the corresponding historical routing nodes in the historical routing result table based on the current routing node list in the trace result, and perform a hop-by-hop comparison according to the matching rules to ensure the consistency of the current network path with the historical path; if it is found that some nodes do not exist in the historical trace or the node order has changed, the system will mark these nodes as possible abnormal path changes and store the comparison results for subsequent delay analysis.

[0052] Through such a design, the system can not only detect potential path drift problems when connectivity is normal, but also ensure the accuracy of the comparison in the subsequent delay calculation link, avoiding misjudgment due to changes in network paths, thereby improving the accuracy of overall fault identification and providing operation and maintenance personnel with more accurate decision-making basis to ensure network stability and business continuity.

[0053] Step 303: Calculate the delay difference between the current delay value of each current routing node and the historical delay value of the corresponding historical routing node.

[0054] In step 303, the core network integrated network management system calculates the delay difference between the current delay value of each current routing node and the historical delay value of the corresponding historical routing node in order to further evaluate whether the transmission quality of the path fluctuates abnormally when the network is still connected, thereby realizing rapid identification of high-latency faults.

[0055] Specifically, after completing the matching of the current routing node with the historical routing node, the system will extract the delay data of each current routing node one by one, and find the delay value of the corresponding historical routing node, calculate the difference between the two, and store the calculation results for subsequent comparison; during the calculation process, the system will not only pay attention to the delay changes of a single node, but also compare the cumulative delay on the entire path to determine whether there is a trend of overall performance degradation. The effect of this is that even if the network path remains reachable, the system can still accurately detect whether the delay is abnormal due to factors such as link congestion, equipment load or network policy adjustment, thereby discovering potential service quality degradation problems in advance, providing accurate data support for subsequent alarm triggering and operation and maintenance optimization, and ensuring the stability and efficiency of the core network.

[0056] Step 304: When any delay difference is greater than a preset delay threshold, it is determined that a delay anomaly exists.

[0057] In step 304, the core network integrated network management system immediately determines that there is a delay anomaly when it detects that any delay difference is greater than the preset delay threshold. This is because simple network connectivity judgment is not sufficient to fully reflect the severity of the fault. It is necessary to combine delay changes to detect potential network performance degradation to ensure rapid identification of high latency problems and alarm triggering.

[0058] Specifically, after the system calculates the delay difference between the current routing node and the historical routing node, it will compare the delay increment of each node with the preset delay threshold. If the delay difference of any node exceeds the threshold, the system will determine that there is a delay anomaly on the path and mark the abnormal node and the corresponding delay change in the fault record for subsequent processing. In order to prevent misjudgment, the system can also combine data from multiple historical cycles for trend analysis to ensure that the identified delay anomalies are continuous fluctuations, rather than anomalies caused by short-term jitter or measurement errors.

[0059] This design enables the system to accurately capture potential trends in service quality degradation even when the network is still reachable, providing operation and maintenance personnel with more comprehensive network status information so that preventive measures can be taken before a failure occurs, optimizing network scheduling and improving overall communication quality and service reliability.

[0060] Step 105: Determine the fault type according to the comparison result, and generate real-time alarm information including the fault type, source IP, and destination IP.

[0061] In step 105, the core network integrated network management system determines the fault type based on the comparison results and generates real-time alarm information including the fault type, source IP and destination IP. This is because relying solely on a single network connectivity or latency analysis cannot fully reflect the severity and impact scope of the fault. It is necessary to comprehensively classify various detection indicators in order to trigger the corresponding alarm processing process more quickly.

[0062] Specifically, after completing the comparison between the current network status information and the historical network status information, the system first confirms whether the current fault is a routing anomaly or a delay anomaly based on the judgment results of steps 301 to 304, and further combines other requests of the same fault type in the merged set to analyze whether the fault is an isolated incident or a large-scale fault trend; if the fault type meets the judgment criteria of "1510 scenario fault", "1510 scenario large-scale fault" or "packet domain registration failure", an alarm message is generated in a preset format, and key fields such as fault type, source IP, and destination IP are attached in the alarm content to ensure that the operation and maintenance personnel can quickly understand the specific situation of the fault.

[0063] The effect of this is that the system can not only accurately classify the fault as soon as it occurs and ensure that the alarm is reported within one minute, but it can also effectively distinguish the scope of impact at the business level, avoiding additional processing delays caused by false alarms or missed alarms, and providing an efficient and reliable foundation for subsequent alarm push, fault handling and automatic dispatch.

[0064] Step 106: Send the real-time alarm information to the administrator terminal within a preset time period.

[0065] In step 106, the core network integrated network management system sends real-time alarm information to the management personnel terminal within a preset time period because merely completing the determination of the fault type and generating alarm information is not sufficient to achieve the goal of rapid fault response. It is necessary to ensure that the alarm information can be accurately delivered to the on-duty personnel within the specified time to meet the "one-minute alarm reporting" operation and maintenance requirements.

[0066] Specifically, after the system completes the generation of the alarm information in step 105, it will immediately trigger the alarm push mechanism, determine the transmission path and priority of the alarm according to the severity and type of the fault, and ensure that high-risk faults can be handled with priority; the system will call the interface of the centralized alarm system to transmit the alarm information containing key fields such as fault type, source IP, destination IP, and request serial number, and attach the network connectivity, delay change, and historical alarm comparison results calculated in the previous steps to the alarm content, so that managers can quickly grasp the details of the fault. At the same time, in order to improve the efficiency of fault handling, the system will also map the alarm information to the operation and maintenance duty terminal, and attach a link for querying historical alarms and route tracking results, so that the operation and maintenance personnel can click the link to view detailed information as soon as they receive the alarm, or even directly perform one-key emergency operations.

[0067] This design not only ensures that the alarm information can reach the relevant maintenance personnel in the shortest time after the fault occurs, but also avoids the response delay caused by manual retrieval and secondary confirmation, greatly improving the automation and intelligence level of fault handling, and providing solid support for subsequent rapid handling, impact assessment and business recovery.

[0068] In a possible implementation, the method further includes the following steps: When the number of fault requests is greater than the preset first number, the real-time route tracing instructions and the periodic route tracing instructions initiated by the signaling system are processed concurrently on the primary and standby data communication equipment switches, wherein the priority of the real-time route tracing instructions is higher than the priority of the periodic route tracing instructions.

[0069] In this step, the core network integrated network management system concurrently processes the real-time routing tracing instructions and periodic routing tracing instructions initiated by the signaling system on the active and standby data communication equipment switches when the number of fault requests is greater than the preset first number, and ensures that the priority of the real-time routing tracing instructions is higher than that of the periodic routing tracing instructions. The main purpose is to efficiently complete network status detection in large-scale fault scenarios in a short time, avoid system response delays due to single-threaded execution of routing tracing instructions, and affect the timeliness of alarms and operation and maintenance efficiency.

[0070] Specifically, when the system detects that the number of fault requests in the same time window exceeds the preset threshold, it will trigger a high-concurrency route tracking scheduling mechanism and dynamically adjust the route tracking instruction execution strategy, so that the real-time fault requests of the signaling system can give priority to calling the primary and standby data communication equipment switches for route tracking operations, while the regular route tracking instructions configured within the system enter the queue with a lower priority, ensuring that operation and maintenance personnel can obtain key network status information in the shortest time. In order to avoid overloading the switch equipment, the system will also adopt a load balancing strategy when executing route tracking instructions concurrently, executing route tracking for different network elements in batches, and storing the results in the route result table after completing each route tracking instruction for subsequent comparison and analysis.

[0071] Through such a design, the system can take into account the efficient processing of batch fault requests while meeting the requirement of minute-level fault reporting, ensuring that even when large-scale faults break out, the detection of core network status can remain efficient and stable, improving the overall operation and maintenance response speed and reducing the impact of faults on business dialing and user experience.

[0072] In one possible implementation, refer to Figure 4 , Figure 4 FIG. 4 is a flow chart of the fault handling method of the voice dialing test provided by the present invention, as shown in FIG. Figure 4 As shown, the method further includes steps 401-404: Step 401: Map the source IP and destination IP to the corresponding network element name through the pre-established service IP and network element correspondence table.

[0073] Step 402: Search the preset historical alarm database according to the network element name to obtain historical alarm data.

[0074] Step 403: Generate a link for viewing the route tracking operation and historical alarm data.

[0075] Step 404: Add a link to the real-time alarm information.

[0076] In steps 401 to 404, the core network integrated network management system uses a pre-established service IP and network element correspondence table to achieve rapid mapping from source IP and destination IP to network element names, and further retrieves historical alarm data to enhance the accuracy of fault diagnosis. At the same time, it generates visual alarm information links to provide maintenance personnel with a convenient means of tracing and analysis.

[0077] In step 401, when the system receives a fault request, it will use the service IP and network element correspondence table to find the specific network element name to which the source IP and destination IP belong. This design can make up for the limitations of directly retrieving historical alarm data based on IP, because the historical alarm data of the core network integrated network management system is stored according to the network element dimension, rather than the IP dimension. Only by completing the mapping from IP to network element first can the relevant alarm information be matched efficiently.

[0078] In step 402, the system enters the preset historical alarm database based on the acquired source IP network element name and destination IP network element name, retrieves the alarm data within 24 hours before and 15 minutes after the alarm occurrence time, and archives the query results for subsequent comparison analysis and alarm information display; this process ensures that even if a network element does not currently have a real-time alarm, potential failure modes or fluctuation anomalies can be discovered based on historical trends.

[0079] In step 403, in order to improve the troubleshooting efficiency of maintenance personnel, the system will dynamically generate a visual access link for each alarm message. The link can jump to the alarm details page, which includes the current trace results, historical alarm comparisons, and key network indicators to support operation and maintenance personnel in conducting in-depth analysis and traceability verification.

[0080] In step 404, while the system pushes the alarm information to the centralized alarm system, it will attach the generated access link to the alarm content, so that after receiving the fault dispatch, the maintenance personnel can quickly obtain the complete historical alarm and trace analysis results by clicking the link, avoiding the time loss caused by manual retrieval, thereby improving the alarm response speed and fault handling efficiency. Through this complete processing link, the system completes the entire process from IP resolution, historical alarm matching, result archiving to visual alarm push within one minute, making fault location more accurate, operation and maintenance operations more efficient, and effectively supporting the intelligent and automated development of core network operation and maintenance.

[0081] Reference Figure 5 , Figure 5 It is a structural diagram of a fault handling system for voice dialing provided by the present invention, and the system includes: A receiving module is used to receive a fault request from a signaling system, where the fault request includes a source IP and a destination IP; A processing module, used to identify the fault type of the fault request within a preset cache period, and merge and compress the fault requests of the same fault type to obtain a merged set; The processing module is further used to determine the first fault request in the merged set, and perform a route tracing operation on the destination IP on the primary and standby data communication device switches corresponding to the source IP of the first fault request to obtain current network status information; The processing module is also used to determine whether there is a routing anomaly and a delay anomaly based on the current network status information and the historical network status information; The alarm generation module is used to determine the fault type according to the comparison result and generate real-time alarm information including the fault type, source IP and destination IP; The alarm sending module is used to send real-time alarm information to the management terminal within a preset time period.

[0082] In a possible implementation manner, the processing module is further configured to: Determine the current network connectivity status based on the route tracing result, wherein the route tracing result is obtained after executing the route tracing operation on the destination IP on the active and standby data communication device switches; When it is determined that the current network connectivity state is a connectivity state, the current delay value is obtained.

[0083] In a possible implementation manner, the processing module is further configured to: When it is determined that the route tracing result is that the destination IP address can be reached, or when there is no interruption node in the route tracing result, it is determined that the current network connectivity state is a connectivity state; When it is determined that the route tracing result is that the destination IP address cannot be reached, or when there is an interrupted node in the route tracing result, it is determined that the current network connectivity state is a disconnected state.

[0084] In a possible implementation manner, the processing module is further configured to: When it is determined that the current network connectivity state is a non-connectivity state, it is determined that there is a routing anomaly; When it is determined that the current network connectivity state is a connectivity state, searching the historical network status information for a corresponding historical routing node for each current routing node in the current network status information; Calculate the delay difference between the current delay value of each current routing node and the historical delay value of the corresponding historical routing node; When any delay difference is greater than a preset delay threshold, it is determined that a delay anomaly exists.

[0085] In a possible implementation manner, the processing module is further configured to: When the number of fault requests is greater than the preset first number, the real-time route tracing instructions and the periodic route tracing instructions initiated by the signaling system are processed concurrently on the primary and standby data communication equipment switches, wherein the priority of the real-time route tracing instructions is higher than the priority of the periodic route tracing instructions.

[0086] In a possible implementation manner, the processing module is further configured to: Map the source IP and destination IP to the corresponding network element name through the pre-established service IP and network element correspondence table; Search the preset historical alarm database according to the network element name to obtain historical alarm data; Generate links for viewing traceroute operations and historical alarm data; Add links to real-time alert messages.

[0087] It should be noted that the voice dialing fault handling system provided by the present invention can execute the voice dialing fault handling method of any of the above embodiments during specific operation, which will not be described in detail in this embodiment.

[0088] Figure 6 is a schematic diagram of the structure of the electronic device provided by the present invention, such as Figure 6 As shown, the electronic device may include: a processor 610 (processor), a communication interface 620 (CommunicationsInterface), a memory 630 (memory) and a communication bus 640 , wherein the processor 610 , the communication interface 620 , and the memory 630 communicate with each other through the communication bus 640 . The processor 610 can call the logic instructions in the memory 630 to execute the fault handling method of voice dialing, which includes: receiving a fault request from a signaling system, the fault request including a source IP and a destination IP; identifying the fault type of the fault request within a preset cache period, and merging and compressing the fault requests of the same fault type to obtain a merged set; determining the first fault request in the merged set, and performing a route tracking operation on the destination IP on the primary and standby data communication equipment switches corresponding to the source IP of the first fault request to obtain current network status information; judging whether there are routing anomalies and delay anomalies based on the current network status information and historical network status information; determining the fault type based on the comparison result, and generating real-time alarm information including the fault type, source IP and destination IP; and sending the real-time alarm information to the management terminal within a preset time period.

[0089] In addition, the logic instructions in the above-mentioned memory 630 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0090] On the other hand, the present invention also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer can execute the voice dialing fault handling method provided by the above-mentioned embodiments, and the method includes: receiving a fault request from a signaling system, the fault request including a source IP and a destination IP; identifying the fault type of the fault request within a preset cache period, and merging and compressing the fault requests of the same fault type to obtain a merged set; determining the first fault request in the merged set, and performing a route tracing operation on the destination IP on the primary and standby data communication equipment switches corresponding to the source IP of the first fault request to obtain current network status information; judging whether there are routing anomalies and delay anomalies based on the current network status information and the historical network status information; determining the fault type based on the comparison result, and generating real-time alarm information including the fault type, source IP and destination IP; sending the real-time alarm information to the management terminal within a preset time period.

[0091] On the other hand, the present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to execute the fault handling method for voice dialing provided in the above-mentioned embodiments, the method comprising: receiving a fault request from a signaling system, the fault request including a source IP and a destination IP; identifying the fault type of the fault request within a preset cache period, and merging and compressing the fault requests of the same fault type to obtain a merged set; determining the first fault request in the merged set, and performing a route tracing operation on the destination IP on the primary and standby data communication equipment switches corresponding to the source IP of the first fault request to obtain current network status information; judging whether there are routing anomalies and delay anomalies based on the current network status information and historical network status information; determining the fault type based on the comparison result, and generating real-time alarm information including the fault type, source IP and destination IP; and sending the real-time alarm information to the management terminal within a preset time period.

[0092] The system embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, i.e., they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art may understand and implement it without creative effort.

[0093] Through the description of the above implementation modes, those skilled in the art can clearly understand that each implementation mode can be implemented by means of software plus a necessary general hardware platform, or of course by hardware. Based on such an understanding, the above technical solution can essentially or in other words be embodied in the form of a software product that contributes to the prior art. The computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of each embodiment or some parts of the embodiment.

[0094] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A voice dialing fault handling method, characterized in that: include: Receive a fault request from a signaling system, wherein the fault request includes a source IP and a destination IP; Identify the fault type of the fault request within a preset cache period, and merge and compress the fault requests of the same fault type to obtain a merged set; Determine the first fault request in the merged set, and perform a route tracing operation on the destination IP on the primary and standby data communication device switches corresponding to the source IP of the first fault request to obtain current network status information; According to the current network status information and the historical network status information, determine whether there is a routing anomaly and a delay anomaly; Determine the fault type according to the comparison result, and generate real-time alarm information including the fault type, the source IP and the destination IP; The real-time alarm information is sent to the administrator terminal within a preset time period.

2. The voice dialing fault handling method according to claim 1, characterized in that: The current network status information includes the current network connectivity status and the current delay value; the route tracing operation of the destination IP is performed on the primary and standby data communication device switches corresponding to the source IP of the first fault request to obtain the current network status information, specifically including: Determine the current network connectivity status according to the route tracing result, wherein the route tracing result is obtained after performing a route tracing operation on the destination IP on the primary and standby data communication device switches; When it is determined that the current network connectivity state is a connectivity state, a current delay value is obtained.

3. The voice dialing fault handling method according to claim 2, characterized in that: Determining the current network connectivity status according to the route tracing result specifically includes: When it is determined that the route tracing result is that the destination IP address can be reached, or when there is no interruption node in the route tracing result, determining that the current network connectivity state is a connectivity state; When it is determined that the route tracing result is that the destination IP address cannot be reached, or when there is an interrupted node in the route tracing result, it is determined that the current network connectivity state is a disconnected state.

4. The voice dialing fault handling method according to claim 2, characterized in that: The determining whether there is a routing anomaly and a delay anomaly based on the current network status information and the historical network status information specifically includes: When it is determined that the current network connectivity state is a non-connectivity state, determining that a routing anomaly exists; When it is determined that the current network connectivity state is a connectivity state, searching the historical network status information for a corresponding historical routing node for each current routing node in the current network status information; Calculating the delay difference between the current delay value of each current routing node and the historical delay value of the corresponding historical routing node; When any of the delay differences is greater than a preset delay threshold, it is determined that a delay anomaly exists.

5. The voice dialing fault handling method according to claim 1, characterized in that: The method further comprises: When the number of fault requests is greater than a preset first number, the real-time route tracing instructions and the periodic route tracing instructions initiated by the signaling system are processed concurrently on the primary and standby data communication equipment switches, wherein the priority of the real-time route tracing instructions is higher than the priority of the periodic route tracing instructions.

6. The voice dialing fault handling method according to claim 1, characterized in that: The method further comprises: Map the source IP and destination IP to the corresponding network element name through the pre-established service IP and network element correspondence table; Searching a preset historical alarm database according to the network element name to obtain historical alarm data; generating a link for viewing the route tracing operation and the historical alarm data; The link is added to the real-time alert information.

7. A voice dialing fault handling system, characterized in that: include: A receiving module, used for receiving a fault request from a signaling system, wherein the fault request includes a source IP and a destination IP; A processing module, used to identify the fault type of the fault request within a preset cache period, and merge and compress the fault requests of the same fault type to obtain a merged set; The processing module is further used to determine the first fault request in the merged set, and perform a route tracing operation on the destination IP on the primary and standby data communication device switches corresponding to the source IP of the first fault request to obtain current network status information; The processing module is further used to determine whether there is a routing anomaly and a delay anomaly according to the current network status information and the historical network status information; An alarm generation module is used to determine the fault type according to the comparison result, and generate real-time alarm information including the fault type, the source IP and the destination IP; The alarm sending module is used to send the real-time alarm information to the management terminal within a preset time period.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that: When the processor executes the computer program, the fault handling method for voice dialing as described in any one of claims 1-6 is implemented.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the fault handling method for voice dialing as described in any one of claims 1 to 6 is implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the fault handling method for voice dialing as described in any one of claims 1 to 6 is implemented.

Images