Link fault positioning method, device and equipment and computer readable storage medium

Abstract

The application relates to the technical field of network security, and provides a link fault positioning method, device and equipment and a computer readable storage medium. The method comprises the following steps: obtaining a service request initiated by a client, and generating a tracking line of a network link corresponding to the service request; tracking and detecting the network link according to the tracking line; when detecting that a fault exists in the network link, obtaining a fault node set; and determining a target fault node according to the number of nodes in the fault node set. The link fault positioning method provided in the application embodiment generates a tracking line of a network link corresponding to a service request, can track and detect the service request based on the generated tracking line, realizes automatic detection of link nodes and positioning of fault nodes, and is beneficial to improving the troubleshooting efficiency of network link faults.

Description

Technical Field

[0001] This application relates to the field of network security technology, specifically to a link fault location method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] Currently, when using the GB28181 protocol to connect lower-level platforms such as video surveillance systems to upper-level platforms, or after connecting lower-level platforms to upper-level platforms, issues frequently arise such as lower-level platforms going offline, lower-level platform cameras going offline, and inability to provide live preview. Most companies currently assign maintenance personnel to check network problems or troubleshoot system issues, but they cannot automatically detect the network link status of the video surveillance system, let alone track problems for important and frequently used lower-level platforms, relying solely on manual troubleshooting. However, in practice, most problems are network-related. If a large number of lower-level platforms are connected, relying on manual troubleshooting undoubtedly consumes enormous labor costs and has low efficiency. Summary of the Invention

[0003] This application provides a link fault location method, apparatus, device, and computer-readable storage medium to solve the technical problems of high labor costs and low efficiency in existing manual network link troubleshooting methods.

[0004] In a first aspect, embodiments of this application provide a link fault location method, including:

[0005] Obtain the service request initiated by the client and generate the network link tracing line corresponding to the service request;

[0006] The network link is tracked and detected according to the tracking line. When a fault is detected in the network link, a set of faulty nodes is obtained.

[0007] The target fault node is determined based on the number of nodes in the set of fault nodes.

[0008] In one embodiment, the step of determining the target faulty node based on the number of nodes in the set of faulty nodes includes:

[0009] Obtain the historical number of failures for each link node in the network link, and count the total number of faulty nodes in the network link when each link node experiences a single failure;

[0010] Based on the historical number of failures and the total number of failure nodes, calculate the failure probability distribution corresponding to each of the link nodes;

[0011] The failure probability value corresponding to each link node in the set of failure nodes is determined based on the failure probability distribution.

[0012] Based on the fault probability value, each link node in the set of faulty nodes is investigated and detected to determine the target faulty node.

[0013] In one embodiment, the step of generating the network link tracing line corresponding to the service request includes:

[0014] Generate a tracking identifier and signaling message corresponding to the service request, and bind the signaling message and the tracking identifier;

[0015] Based on the tracking identifier and the signaling message, and according to the processing order of the service request by each link node in the network link, a tracking line for the network link corresponding to the service request is generated.

[0016] In one embodiment, the link node includes a service gateway, a session service node, and a session proxy node. The step of generating a tracking identifier and signaling message corresponding to the service request, and binding the signaling message and the tracking identifier, includes:

[0017] The service request is forwarded to the service gateway, and the service gateway is used to generate a tracking identifier corresponding to the service request;

[0018] The tracking identifier and the service request are sent to the session service node, the session service node is used to generate a signaling message corresponding to the service request, and the session identifier and flow identifier in the signaling message are bound to the tracking identifier respectively.

[0019] In one embodiment, the link nodes further include the client, the service platform, and the media service node. The step of generating the network link tracing line corresponding to the service request based on the tracking identifier and the signaling message, according to the processing order of the service request by each link node in the network link, includes:

[0020] Based on the processing order of the service request by each link node in the network link, and based on the tracking identifier, a first tracking branch of the network link corresponding to the service request is generated between the client, the service gateway, and the session service node;

[0021] Based on the dialogue identifier in the signaling message, a second tracing branch of the network link corresponding to the service request is generated between the session service node, the session proxy node, and the service platform;

[0022] Based on the flow identifier in the signaling message, a third tracing branch of the network link corresponding to the service request is generated between the media service node, the service platform, and the session proxy node;

[0023] Generate a flow address corresponding to the flow identifier, and based on the flow address and the tracking identifier, generate a fourth tracking branch of the network link corresponding to the service request between the session service node, the service gateway, and the client;

[0024] By connecting the first tracing branch, the second tracing branch, the third tracing branch, and the fourth tracing branch in series, a full-link tracing line for the network link corresponding to the service request is generated.

[0025] In one embodiment, after the step of determining the target faulty node based on the number of nodes in the faulty node set, the method further includes:

[0026] Output early warning information, which includes the target fault node and the analysis results of the cause of the fault of the target fault node.

[0027] In one embodiment, the link fault location method further includes:

[0028] Obtain the number of times each preset camera is requested and the number of times it malfunctions, and determine the weight coefficient of each preset camera based on the number of times it is requested and the number of times it malfunctions.

[0029] The attention level of each preset camera is calculated based on the weighting coefficients.

[0030] The frequency of performing tracking and detection on the network links corresponding to each preset camera is determined based on the level of attention.

[0031] Secondly, embodiments of this application provide a link fault location device, comprising:

[0032] The tracing line configuration module is used to obtain the service request initiated by the client and generate the tracing line of the network link corresponding to the service request;

[0033] The fault tracking and detection module is used to track and detect the network link according to the tracking line, and when a fault is detected in the network link, obtain a set of fault nodes;

[0034] The fault node location module is used to determine the target fault node based on the number of nodes in the fault node set.

[0035] Thirdly, embodiments of this application provide an electronic device, including a processor and a memory storing a computer program, wherein the processor executes the program to implement the steps of the link fault location method described in the first aspect.

[0036] Fourthly, embodiments of this application provide a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the link fault location method described in the first aspect.

[0037] The link fault location method, apparatus, device, and computer-readable storage medium provided in this application generate a tracing line of the network link corresponding to a service request. Based on the generated tracing line, the service request can be tracked and detected, realizing automatic detection of link nodes and location of faulty nodes, which is beneficial to improving the efficiency of troubleshooting network link faults. Attached Figure Description

[0038] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 This is one of the flowcharts illustrating the link fault location method provided in the embodiments of this application;

[0040] Figure 2 This is one of the tracing line diagrams of the link fault location method provided in the embodiments of this application;

[0041] Figure 3 This is one of the structural schematic diagrams of the link fault location device provided in the embodiments of this application;

[0042] Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0044] Figure 1 This is one of the flowcharts illustrating the link fault location method provided in this application. (Refer to...) Figure 1 The link fault location method provided in this application embodiment may include:

[0045] Step 100: Obtain the service request initiated by the client and generate the network link tracing line corresponding to the service request;

[0046] The link fault location method provided in this application embodiment can be applied to platforms accessing network links using the GB28181 protocol, where GB28181 is based on the SIP (Session Initialization Protocol). In this embodiment, the network links of a platform accessing via the GB28181 protocol are tracked and analyzed. When a problem occurs at a node in the link, the faulty link node can be identified promptly, and the problem can be analyzed to facilitate timely fault resolution by maintenance personnel and improve maintenance efficiency. Specifically, a service request initiated by a user through a client is obtained, and a tracing line of the network link corresponding to that service request is generated. The tracing line can be generated based on the packet information of each link node in the network link, or it can be generated by storing the identification information corresponding to the service request in each link node; no limitation is made here. It is understood that a corresponding tracing line is generated for each service request so that when a fault occurs during the processing of that service request, the network link of that service request can be tracked and analyzed. Furthermore, in daily maintenance, tracing lines of the same service request can be statistically analyzed to provide a basis for subsequent network link fault diagnosis.

[0047] Step 200: Track and detect the network link according to the tracking line; when a fault is detected in the network link, obtain a set of faulty nodes.

[0048] Based on the generated tracing path, network links are tracked and detected. This can be done at regular intervals, upon receiving a service request, or when a service request fails, with no specific limitation on the method. When a fault is detected in a link, a set of faulty nodes is obtained, containing multiple faulty link nodes. Generally, if a node in a network link fails, subsequent nodes will also be unable to receive messages, leading to their own failure. Therefore, a fault in a link can trigger a chain reaction, causing one or more nodes to fail. All faulty nodes in the link are detected, forming a set of faulty nodes.

[0049] Step 300: Determine the target fault node based on the number of nodes in the set of fault nodes.

[0050] Based on the number of faulty nodes in the detected set of faulty nodes, the faulty node is determined, thereby locating the link fault. Specifically, based on prior analysis of each link node in the network link, the number of faulty nodes in the link when each node fails can be determined. Once the number of faulty nodes in the link is determined, the target faulty node of the actual fault can be quickly located.

[0051] Furthermore, step 300 may also include:

[0052] Step 301: Obtain the historical number of failures of each link node in the network link, and count the total number of faulty nodes in the network link when each link node experiences a single failure.

[0053] Step 302: Based on the number of historical failures and the total number of failure nodes, calculate the failure probability distribution corresponding to each of the link nodes;

[0054] Step 303: Determine the fault probability value corresponding to each link node in the fault node set according to the fault probability distribution;

[0055] Step 304: Based on the fault probability value, investigate and detect each link node in the fault node set to determine the target fault node.

[0056] When locating a target faulty node based on the number of faulty nodes, the first step is to obtain the historical failure counts of each link node in the network link. The total number of faulty nodes in the link when each node fails is then counted, and this total number corresponds to a single failure of a link node. Taking a target node in the link as an example, the total number of faulty nodes in the link refers to the total number of nodes in the link that fail, including the target node itself, when the target node fails. It is known that in a network link, upstream nodes affect downstream nodes; when an upstream node fails, downstream nodes will also fail. Therefore, the total number of faulty nodes can be the target node and its downstream nodes, or it can be a statistical value based on historical data showing the number of faulty nodes in the link when the target node fails multiple times. This statistical value includes the average, median, etc. Taking the average as an example, based on the historical failure data of the target node, the number of faulty nodes in the link when the target node fails each time is added together, and then divided by the historical failure count of the target node to obtain the total number of faulty nodes in the network link when the target node fails. Based on the historical number of failures of each link node and the total number of faulty nodes in the link when each node fails, the failure probability distribution of each link node is calculated. When troubleshooting link failures, the node with the link problem can be quickly identified based on this failure probability distribution, thereby improving the efficiency of tracking and analyzing network links.

[0057] It is known that when a node in a network link fails, subsequent nodes will also be unable to receive messages, leading to a cascading failure. Based on the order in which nodes process service requests, the number of all failed nodes in the link when one node fails is: m, m-1, m-2, ..., 2, 1. Based on prior analysis of each link node in the network link, combined with historical failure counts for each node, the number of failed nodes in the link when each node fails can be determined, thus obtaining the probability distribution of the corresponding number of failed nodes. Once the number of failed nodes in the link is determined, the probability value of each node's failure can be obtained based on this probability distribution. By checking in descending order of failure probability values, the truly faulty link node can be quickly identified, thereby accurately locating the link failure.

[0058] Furthermore, the failure probability distribution of each link node can be obtained based on the normal distribution. By combining the total number of failed nodes in the network link when each node fails with the historical failure count of each link node, and substituting this into the normal distribution function shown in Formula 1, we obtain the probability density function of each link node, i.e., the failure probability distribution:

[0059] (1)

[0060] Here, f(x) is the probability density function of the number of faulty nodes, π and e are constants, x is the total number of faulty nodes when a certain node fails, μ is the mean of x, and σ is the variance of x. Based on the characteristics of the normal distribution, the probability value is highest when x = μ. Furthermore, since the probability density function is symmetric about x = μ, when troubleshooting network link faults, we can start by investigating the node that causes the total number of faulty nodes to be μ (investigating upwards or downwards as needed), which can significantly improve troubleshooting efficiency. That is, after determining the number of faulty nodes in the network link (i.e., the number of nodes in the set of faulty nodes), we substitute this number of faulty nodes into the corresponding fault probability distribution function to obtain the fault probability value of each link node corresponding to this number of faulty nodes. By investigating the link node with the highest probability value in descending order, we can quickly locate the target faulty node.

[0061] After step 300, it may also include:

[0062] Step 400: Output early warning information, which includes the target fault node and the analysis results of the cause of the fault of the target fault node.

[0063] Furthermore, after locating the target faulty node, an early warning message is output. This message includes the faulty link node and the analysis results of the cause of the fault, so that maintenance personnel can quickly resolve the fault and improve the efficiency of fault investigation and resolution.

[0064] In this embodiment, by generating a network link tracing line corresponding to a service request, the service request can be tracked and detected based on the generated tracing line, thereby achieving automatic detection of link nodes and location of faulty nodes, which helps to improve the efficiency of troubleshooting network link faults.

[0065] Furthermore, when identifying the target fault node, a rapid comparison is performed based on the probability distribution of each link node, which further improves the efficiency of fault diagnosis.

[0066] In one embodiment, step 100 may include:

[0067] Step 101: Generate a tracking identifier and signaling message corresponding to the service request, and bind the signaling message and the tracking identifier;

[0068] Step 102: Based on the tracking identifier and the signaling message, and according to the processing order of the service request by each link node in the network link, generate the tracking line of the network link corresponding to the service request.

[0069] When generating the network link tracing path corresponding to a service request, the trace ID and signaling message corresponding to the service request are first generated. Based on the generated trace ID and signaling message, the corresponding tracing path is generated according to the processing order of the service request by each link node in the network link.

[0070] Step 101 may further include:

[0071] Step 1011: Forward the service request to the service gateway, and use the service gateway to generate a tracking identifier corresponding to the service request;

[0072] Step 1012: Send the tracking identifier and the service request to the session service node, use the session service node to generate a signaling message corresponding to the service request, and bind the session identifier and flow identifier in the signaling message to the tracking identifier respectively.

[0073] Furthermore, the following explanation uses a live streaming request as an example of a service request. The link nodes in the network link include the client, service gateway, session service node (SIP service node), and session proxy node (SIP proxy node), etc. When generating the trace ID and signaling message corresponding to the service request, the service request obtained from the client is first sent to the service gateway. The service gateway generates the trace ID and sends the trace ID and the service request to the SIP service node. The SIP service node generates the signaling message corresponding to the service request and binds the session ID call-ID and flow ID SSRC in the signaling message to the trace ID one-to-one.

[0074] Step 102 may also include:

[0075] Step 1021: Based on the processing order of the service request by each link node in the network link, and using the tracking identifier, generate the first tracking branch of the network link corresponding to the service request between the client, the service gateway, and the session service node;

[0076] Step 1022: Based on the dialogue identifier in the signaling message, generate a second tracing branch of the network link corresponding to the service request between the session service node, the session proxy node, and the service platform;

[0077] Step 1023: Based on the flow identifier in the signaling message, generate a third tracing branch of the network link corresponding to the service request between the media service node, the service platform, and the session proxy node;

[0078] Step 1024: Generate the flow address corresponding to the flow identifier; based on the flow address and the tracking identifier, generate a fourth tracking branch of the network link corresponding to the service request between the session service node, the service gateway, and the client.

[0079] Step 1025: Connect the first tracing branch, the second tracing branch, the third tracing branch, and the fourth tracing branch to generate the full-link tracing line of the network link corresponding to the service request.

[0080] Furthermore, the link nodes of the network link also include lower-level service platforms and media service nodes, as shown in the reference. Figure 2 , Figure 2 This is one of the schematic diagrams for tracing network links. Figure 2In this network link tracing diagram, multiple branches are involved. The first branch is the "Client -> Service Gateway -> SIP Service" tracing line, which is the tracing identifier tracing line. The second branch is the "SIP Service -> SIP Proxy -> Lower-level Service Platform" tracing line, which is the SIP message tracing line. The third branch is the "Lower-level Service Platform -> Media Service -> SIP Service" tracing line, which is the media data tracing line. The fourth branch is the "SIP Service -> Service Gateway -> Client" tracing line, which is also the tracing identifier tracing line. These tracing branches are then connected in series to form the network link tracing diagram.

[0081] Specifically, based on the processing order of the service request by each link node, a first tracing branch of the network link corresponding to the service request is generated between the client, service gateway, and SIP service node based on the generated trace ID; a second tracing branch of the network link is generated between the SIP service node, SIP proxy node, and lower-level service platform based on the call-ID in the generated signaling message; a third tracing branch of the network link corresponding to the service request is generated between the media service node, lower-level service platform, and SIP proxy node based on the flow identifier in the signaling message; then, the flow address corresponding to the flow identifier is generated, and a fourth tracing branch of the network link is generated between the SIP service node, service gateway, and client based on the generated flow address and trace ID; the generated tracing branches are then concatenated to obtain the corresponding network link tracing line.

[0082] Taking a live streaming request as an example, refer to... Figure 2 The diagram shown illustrates the process of generating a tracing line, and provides a detailed explanation of the process.

[0083] 1. First, the user initiates a live streaming request to the business gateway through the client;

[0084] 2. After the business gateway receives the live streaming request from the client, it generates a unique trace ID for this conversation and records it in the business gateway. Then, it forwards the live streaming request and the trace ID to the SIP service.

[0085] 3. After receiving the live streaming request and traceID, the SIP service stores the traceID in the SIP service. Then, according to the platform access protocol, such as GB28181, it generates a signaling message and forwards the signaling message and traceID to the SIP agent. After generating the signaling message, the call-ID and flow identifier SSRC in the signaling message are bound one-to-one with the traceID.

[0086] 4. After receiving the signaling message, the SIP agent records and stores the Call-ID in the SIP agent node and uses it as the unique identifier for this conversation. Then, it sends the signaling message to the lower-level service platform to complete the SIP signaling interaction between the SIP agent node and the lower-level service platform, thereby sending streaming media data to the media service node through the lower-level service platform.

[0087] 5. After receiving streaming media data sent by the lower-level business platform, the media service node first decapsulates the streaming media data, obtains the encapsulated stream identifier SSRC, uses this as the unique identifier of the streaming media data, and records and stores it in the media service node.

[0088] 6. The media service node reports the obtained SSRC stream identifier to the SIP service node. After confirming that the media service node has received the streaming media data, the SIP service node generates the corresponding stream address for the SIP service node to record and store the trace identifier (traceID).

[0089] 7. The SIP service node returns the flow address to the service gateway so that the service gateway can record and store the trace identifier (traceID);

[0090] 8. The flow address is returned to the client through the business gateway so that the client can use it to record and store the trace identifier (traceID).

[0091] The above process generates the tracing path corresponding to the live stream request. When tracing and detecting the network link, each node is sequentially queried for a unique identifier record. For example, the tracing identifier tracing path checks for a traceID record, the SIP message tracing path checks for its Call-ID record, and the streaming media tracing path checks for its SSRC record. If, during the link query, a traceID (and / or Call-ID and / or SSRC) is found to be missing, it indicates a problem with that node's link. The faulty node is located through analysis, and a warning is sent to the relevant operations and maintenance personnel.

[0092] In this embodiment, each link node of the network link is identified by the generated tracking identifier and signaling data, thereby generating a network link tracking line. Based on the generated tracking line, automatic detection and fault diagnosis of link nodes can be realized, which helps to improve the efficiency of troubleshooting network link faults.

[0093] In one embodiment, to further improve fault diagnosis efficiency, network links can be filtered, and different links can be given different levels of attention. For example, links that frequently fail can be selected as important links, and high-frequency full-link tracking analysis can be performed on important links. Links with different levels of attention can be set with different tracking and detection frequencies to reduce resource consumption. Based on this, the link fault location method provided in this embodiment may further include:

[0094] Step 001: Obtain the number of times each preset camera is requested and the number of times it fails; determine the weight coefficient of each preset camera based on the number of times it is requested and the number of times it fails.

[0095] Step 002: Calculate the attention level of each preset camera based on the weighting coefficients;

[0096] Step 003: Determine the frequency of tracking and detecting the network links corresponding to each preset camera based on the level of attention.

[0097] As we know, for a video surveillance system, each camera used to acquire streaming media data corresponds to a network link. Determining the level of attention given to different links is essentially determining the level of attention given to each preset camera. Specifically, first, influencing factors are determined, and based on these factors, the level of attention given to each preset camera is determined, thus selecting key cameras. Statistically, there are two main factors influencing camera attention: the number of times the camera is requested and the number of times the camera malfunctions. When selecting key cameras, it is also necessary to assign weight coefficients to each of these influencing factors.

[0098] Let x and y be the number of times the camera was requested and the number of times it malfunctioned, respectively, with weights of 1 and 2. If β, then:

[0099] , (2)

[0100] Where x and y represent the number of times each camera was accessed and the number of times it malfunctioned, based on historical data up to the time of this investigation. The access weight α and the malfunction weight β can be calculated from these values. The weight coefficients for these two values ​​differ depending on the number of accesses and the number of malfunctions.

[0101] Based on weighted coefficients, the level of attention given to each preset camera during this investigation is calculated to determine the frequency of tracking and detection for each preset camera. It's understandable that the tracking and detection frequency should not be too high, meaning the interval between two tracking and detection checks should not be too short, as this will affect detection efficiency, especially when there are many connected cameras. Conversely, the tracking and detection frequency should not be too low, meaning the interval between two tracking and detection checks should not be too long, as this will affect the detection results and thus operational efficiency. Furthermore, the link tracking and detection interval should be related to the number of plays and the number of failures. Therefore, different tracking and detection execution frequencies are set for links with different levels of attention. During the initial tracking and detection, a constant needs to be given: the weighted average of the number of plays and the number of failures for all cameras, a_0. The next link tracking execution time is t_0. Then, the time interval t between the next link tracking execution time and the current time is:

[0102] (3)

[0103] Where k is a customizable constant between 0 and 1, representing the gradient value of a_0 for each preset camera and the time interval between the next execution of link tracking; a is the weighted average of the number of times the current camera is used and the number of times it fails; t is the variable to be determined, i.e., the time interval between the next execution of link tracking and the current time. Different gradient values ​​k can be set for cameras with different levels of interest, thereby determining the tracking and detection time interval for network links with different levels of interest.

[0104] Furthermore, when selecting cameras for priority monitoring, a weighted average of the number of playbacks and failures for each camera is calculated based on the number of playbacks, the number of failures, and their weighting coefficients. This yields several weighted averages. These weighted averages are then sorted from largest to smallest, and the top n cameras are selected as priority monitoring cameras (where n is a constant that can be set based on detection performance). Alternatively, cameras with weighted averages greater than a set threshold are selected as priority monitoring cameras.

[0105] After identifying cameras that have received special attention, they are included in the full-link tracking and monitoring scope. The client request part, SIP signaling part, and streaming media transmission part are tracked separately. When any node in the link has a problem, the analysis results can be fed back to the operation and maintenance personnel in a timely manner.

[0106] In this embodiment, different network links corresponding to different cameras are given different levels of attention based on the number of times the camera is used and the number of times it fails. The links with different levels of attention are tracked and detected at different frequencies. This reduces the consumption of computing resources while ensuring the efficiency of fault diagnosis and operation and maintenance.

[0107] The link fault location device provided in the embodiments of this application is described below. The link fault location device described below can be referred to in correspondence with the link fault location method described above.

[0108] Reference Figure 3 The link fault location device provided in this application embodiment includes:

[0109] The tracing line configuration module 10 is used to obtain the service request initiated by the client and generate the tracing line of the network link corresponding to the service request;

[0110] The fault tracking and detection module 20 is used to track and detect the network link according to the tracking line, and when a fault is detected in the network link, obtain a set of fault nodes;

[0111] The fault node location module 30 is used to determine the target fault node based on the number of nodes in the fault node set.

[0112] In one embodiment, the fault node location module 30 is further configured to:

[0113] Obtain the historical number of failures for each link node in the network link, and count the total number of faulty nodes in the network link when each link node experiences a single failure;

[0114] Based on the historical number of failures and the total number of failure nodes, calculate the failure probability distribution corresponding to each of the link nodes;

[0115] The failure probability value corresponding to each link node in the set of failure nodes is determined based on the failure probability distribution.

[0116] Based on the fault probability value, each link node in the set of faulty nodes is investigated and detected to determine the target faulty node.

[0117] In one embodiment, the tracking line configuration module 10 is further configured to:

[0118] Generate a tracking identifier and signaling message corresponding to the service request, and bind the signaling message and the tracking identifier;

[0119] Based on the tracking identifier and the signaling message, and according to the processing order of the service request by each link node in the network link, a tracking line for the network link corresponding to the service request is generated.

[0120] In one embodiment, the link node includes a service gateway, a session service node, and a session proxy node, and the tracing line configuration module 10 is further configured to:

[0121] The service request is forwarded to the service gateway, and the service gateway is used to generate a tracking identifier corresponding to the service request;

[0122] The tracking identifier and the service request are sent to the session service node, the session service node is used to generate a signaling message corresponding to the service request, and the session identifier and flow identifier in the signaling message are bound to the tracking identifier respectively.

[0123] In one embodiment, the link node further includes the client, the service platform, and the media service node, and the tracking line configuration module 10 is further configured to:

[0124] Based on the processing order of the service request by each link node in the network link, and based on the tracking identifier, a first tracking branch of the network link corresponding to the service request is generated between the client, the service gateway, and the session service node;

[0125] Based on the dialogue identifier in the signaling message, a second tracing branch of the network link corresponding to the service request is generated between the session service node, the session proxy node, and the service platform;

[0126] Based on the flow identifier in the signaling message, a third tracing branch of the network link corresponding to the service request is generated between the media service node, the service platform, and the session proxy node;

[0127] Generate a flow address corresponding to the flow identifier, and based on the flow address and the tracking identifier, generate a fourth tracking branch of the network link corresponding to the service request between the session service node, the service gateway, and the client;

[0128] By connecting the first tracing branch, the second tracing branch, the third tracing branch, and the fourth tracing branch in series, a full-link tracing line for the network link corresponding to the service request is generated.

[0129] In one embodiment, the link fault location device further includes an early warning module, used for:

[0130] Output early warning information, which includes the target fault node and the analysis results of the cause of the fault of the target fault node.

[0131] In one embodiment, the link fault location device further includes an automatic filtering configuration module, used for:

[0132] Obtain the number of times each preset camera is requested and the number of times it malfunctions, and determine the weight coefficient of each preset camera based on the number of times it is requested and the number of times it malfunctions.

[0133] The attention level of each preset camera is calculated based on the weighting coefficients.

[0134] The frequency of performing tracking and detection on the network links corresponding to each preset camera is determined based on the level of attention.

[0135] Figure 4 Example: A schematic diagram of the physical structure of an electronic device, such as... Figure 4 As shown, the electronic device may include: a processor 410, a communication interface 420, a memory 430, and a communication bus 440, wherein the processor 410, the communication interface 420, and the memory 430 communicate with each other via the communication bus 440. The processor 410 can call a computer program in the memory 430 to execute the steps of the link fault location method, such as including:

[0136] Obtain the service request initiated by the client and generate the network link tracing line corresponding to the service request;

[0137] The network link is tracked and detected according to the tracking line. When a fault is detected in the network link, a set of faulty nodes is obtained.

[0138] The target fault node is determined based on the number of nodes in the set of fault nodes.

[0139] Furthermore, the logical instructions in the aforementioned memory 430 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0140] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can perform the steps of the link fault location method provided in the above embodiments, such as including:

[0141] Obtain the service request initiated by the client and generate the network link tracing line corresponding to the service request;

[0142] The network link is tracked and detected according to the tracking line. When a fault is detected in the network link, a set of faulty nodes is obtained.

[0143] The target fault node is determined based on the number of nodes in the set of fault nodes.

[0144] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing a processor to perform the steps of the methods provided in the above embodiments, such as including:

[0145] Obtain the service request initiated by the client and generate the network link tracing line corresponding to the service request;

[0146] The network link is tracked and detected according to the tracking line. When a fault is detected in the network link, a set of faulty nodes is obtained.

[0147] The target fault node is determined based on the number of nodes in the set of fault nodes.

[0148] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0149] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0150] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0151] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A link fault location method, characterized in that, include: Obtain the service request initiated by the client and generate the network link tracing line corresponding to the service request; The network link is tracked and detected according to the tracking line. When a fault is detected in the network link, a set of faulty nodes is obtained. The target fault node is determined based on the number of nodes in the set of fault nodes; The step of determining the target fault node based on the number of nodes in the set of fault nodes includes: Obtain the historical number of failures for each link node in the network link, and count the total number of faulty nodes in the network link when each link node experiences a single failure; Based on the historical number of failures and the total number of failure nodes, calculate the failure probability distribution corresponding to each of the link nodes; The failure probability value corresponding to each link node in the set of failure nodes is determined based on the failure probability distribution. Based on the fault probability value, each link node in the set of faulty nodes is investigated and detected to determine the target faulty node.

2. The link fault location method according to claim 1, characterized in that, The step of generating the network link tracing line corresponding to the service request includes: Generate a tracking identifier and signaling message corresponding to the service request, and bind the signaling message and the tracking identifier; Based on the tracking identifier and the signaling message, and according to the processing order of the service request by each link node in the network link, a tracking line for the network link corresponding to the service request is generated.

3. The link fault location method according to claim 2, characterized in that, The link nodes include a service gateway, a session service node, and a session proxy node. The step of generating a tracking identifier and signaling message corresponding to the service request, and binding the signaling message and the tracking identifier, includes: The service request is forwarded to the service gateway, and the service gateway is used to generate a tracking identifier corresponding to the service request; The tracking identifier and the service request are sent to the session service node, and the session service node is used to generate a signaling message corresponding to the service request. The session identifier and the flow identifier in the signaling message are then bound to the tracking identifier.

4. The link fault location method according to claim 3, characterized in that, The link nodes also include the client, service platform, and media service nodes. The step of generating the network link tracing line corresponding to the service request based on the tracking identifier and the signaling message, according to the processing order of the service request by each link node in the network link, includes: Based on the processing order of the service request by each link node in the network link, and based on the tracking identifier, a first tracking branch of the network link corresponding to the service request is generated between the client, the service gateway, and the session service node; Based on the dialogue identifier in the signaling message, a second tracing branch of the network link corresponding to the service request is generated between the session service node, the session proxy node, and the service platform; Based on the flow identifier in the signaling message, a third tracing branch of the network link corresponding to the service request is generated between the media service node, the service platform, and the session proxy node; Generate the flow address corresponding to the flow identifier, and based on the flow address and the tracking identifier, generate a fourth tracking branch of the network link corresponding to the service request between the session service node, the service gateway, and the client; By connecting the first tracing branch, the second tracing branch, the third tracing branch, and the fourth tracing branch in series, a full-link tracing line for the network link corresponding to the service request is generated.

5. The link fault location method according to claim 1, characterized in that, After the step of determining the target fault node based on the number of nodes in the set of fault nodes, the method further includes: Output early warning information, which includes the target fault node and the analysis results of the cause of the fault of the target fault node.

6. The link fault location method according to any one of claims 1 to 5, characterized in that, The link fault location method further includes: Obtain the number of times each preset camera is requested and the number of times it malfunctions, and determine the weight coefficient of each preset camera based on the number of times it is requested and the number of times it malfunctions. The attention level of each preset camera is calculated based on the weighting coefficients. The frequency of performing tracking and detection on the network links corresponding to each preset camera is determined based on the level of attention.

7. A link fault location device, characterized in that, include: The tracing line configuration module is used to obtain the service request initiated by the client and generate the tracing line of the network link corresponding to the service request; The fault tracking and detection module is used to track and detect the network link according to the tracking line, and when a fault is detected in the network link, obtain a set of fault nodes; The fault node location module is used to obtain the historical number of faults of each link node in the network link, and to count the total number of fault nodes in the network link when each link node fails once. Based on the historical number of failures and the total number of failure nodes, calculate the failure probability distribution corresponding to each of the link nodes; The failure probability value corresponding to each link node in the set of failure nodes is determined based on the failure probability distribution. Based on the fault probability value, each link node in the set of faulty nodes is investigated and detected to determine the target faulty node.

8. An electronic device comprising a processor and a memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the link fault location method according to any one of claims 1 to 6.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the link fault location method according to any one of claims 1 to 6.

Images