Method and system for automated testing and fault detection of multi-node bus communication protocols

Abstract

The application discloses a multi-node bus communication protocol automation test and fault detection method and system, and relates to the technical field of communication protocol test and diagnosis. The multi-node bus communication protocol automation test and fault detection method and system comprises the following steps: S1: obtaining communication node state data and preprocessing; S2: measuring the communication disturbance intensity caused by node abnormality and recovery lag; S3: evaluating the communication structure stability based on connection state change and topology reconstruction deviation; and S4: judging the conduction intensity and the range of abnormal chain. The problems that the bus recovery process is uncontrollable due to the fact that the existing process parameters are fixed and lack of state feedback adjustment, and the communication structure is unstable and difficult to diagnose due to the reset storm under the error injection scene are solved.

Description

Technical Field

[0001] This invention relates to the field of communication protocol testing and diagnosis technology, specifically to an automated testing and fault detection method and system for multi-node bus communication protocols. Background Technology

[0002] With the widespread application of communication protocols in distributed networks and the Internet of Things (IoT), the protocol stack layer-by-layer parsing mechanism has become a crucial foundation for supporting multi-node data exchange. Process communication enables efficient interaction between different nodes, routing lookup improves addressing efficiency in dynamic topologies, and IoT routing management promotes collaborative interconnection of cross-domain devices. Meanwhile, network security communication protocols are constantly evolving to ensure the integrity and protection capabilities of data transmission. In multi-node bus environments, these technological advancements have led to greater complexity and real-time requirements in communication networks, highlighting the increasing demand for automated testing of protocol consistency and stability.

[0003] For example, invention patent CN102761445B discloses a method for processing the transmission delay of a substation network, including the following steps: recording the transmission information of packets transmitted by a virtual switch to obtain a forwarding delay table of the virtual switch; obtaining the packet forwarding delay according to the forwarding delay table; obtaining the packet sending delay according to the packet length and Ethernet port rate; obtaining the line transmission delay according to the line length configured on the virtual switch port; and obtaining the substation network transmission delay from the packet forwarding delay, the packet sending delay, and the line transmission delay. Using this method, the real-time synchronization requirements of message transmission in intelligent substations can be met.

[0004] For example, invention patent CN106452832B discloses a method for accurately obtaining configuration parameters for C-CMTS devices. This method involves C-CMTS devices, service switches, BRAS servers, routers, and DHCP / TFTP servers. The C-CMTS devices broadcast DHCP discovery request messages; the service switches configure the DHCP relay service VLAN tags for the C-CMTS devices; the BRAS servers convert the broadcast DHCP discovery request messages from the C-CMTS devices into DHCP unicast request messages and send them to the DHCP / TFTP server, and forward the DHCP / TFTP server response messages to a designated port on the service switch; the DHCP / TFTP server receives and matches the DHCP unicast request messages and accurately distributes pre-configuration files for different ports to the corresponding C-CMTS devices. This method is simple to operate, saves on-site operation time, reduces environmental requirements for on-site operations and the technical requirements for operators, and is suitable for the deployment, commissioning, operation, and maintenance of large numbers of C-CMTS devices.

[0005] Existing implementation methods mostly focus on single-node protocol function verification and error injection based on fixed rules. They generally suffer from limited test granularity, static reset strategies, and a lack of dynamic adjustment based on node feedback, making them difficult to adapt to complex fault scenarios in multi-node topologies. These methods often fail to effectively identify unstable regions in the communication structure and lack the ability to trace the anomaly propagation chain, resulting in a limited diagnostic scope and test results that cannot fully reflect the stability and reliability of the communication protocol in actual operation.

[0006] To address the above issues, there is an urgent need for automated testing and fault detection methods and systems for multi-node bus communication protocols. Summary of the Invention

[0007] Technical problems to be solved

[0008] To address the shortcomings of existing technologies, this invention provides an automated testing and fault detection method and system for multi-node bus communication protocols. It solves the problems of unstable communication structures and difficulty in diagnosis caused by reset storms in error injection scenarios, and the uncontrollable bus recovery process due to fixed process parameters and lack of state feedback adjustment in existing systems.

[0009] Technical solution

[0010] To achieve the above objectives, the present invention provides the following technical solution: an automated testing and fault detection method for multi-node bus communication protocols, comprising the following steps: S1: Collecting real-time response information, error injection feedback, and port status of each node in the communication bus, obtaining communication node status data and performing preprocessing; S2: Based on the preprocessing of communication node status data, measuring the intensity of communication disturbances caused by node anomalies and recovery lags, and performing graded reset adjustments to adjust the reset frequency, port execution permissions, and injection time point settings; S3: Based on the node connection status updated according to the reset adjustment results, assessing the stability of the communication structure based on connection status changes and topology reconstruction deviations, and controlling node connection permissions and data participation scope according to the assessment results; S4: When the structural stability assessment result is in an unstable state, determining the propagation intensity and impact range of the abnormal chain, determining the propagation level state based on propagation characteristics, and performing node shielding, recovery waiting, and test exclusion control based on the propagation level state, and dynamically adjusting the propagation chain processing.

[0011] Further, the real-time response information, error injection feedback, and port status of each node in the communication bus are collected, and the communication node status data is obtained and preprocessed. The specific steps are as follows: The process of collecting the real-time response information, error injection feedback, and port status of each node in the communication bus and obtaining the communication node status data includes: counting the nodes with CRC error fields and nodes with VPC error fields in the asynchronous stream messages collected in the current test cycle, deduplicating the set to obtain the number of error nodes; detecting the number of nodes that have not received a valid event response for multiple consecutive test cycles to obtain the number of disconnected nodes; recording the specific time of the node's response to the injected event to obtain the event response message timestamp; identifying the initial moment when the node enters the continuous unresponsive state to obtain the disconnection start timestamp; marking the time when the node regenerates a valid response to obtain the disconnection end timestamp; and tracking the time point when the node enters the first unresponsive state to obtain the disconnection start timestamp. The process involves: tracking the moment a node first establishes a valid communication connection to obtain a connection start timestamp; determining the time point after continuous and stable communication to obtain a connection stability timestamp; comparing the number of nodes whose connectivity changes within two adjacent test periods to obtain the connection state change count; summarizing the cumulative number of times a node fails to complete event responses in an interrupted state to obtain the interruption count; using periodic consistency detection and event response frequency filtering methods to eliminate false response data caused by unstable node connections, port disconnections, and incomplete resets; integrating CRC and VPC error records of the same node appearing in different time slices based on multi-source merging rules for error fields; using a window adaptive time aggregation method to merge and compress the event response sequence; combining a register state association constraint mechanism to perform layered filling and reconstruction of node data with missing or inconsistent register fields during the acquisition process; and performing standardization and normalization processing on the communication node state data.

[0012] Furthermore, based on the preprocessing of communication node status data, the specific steps for measuring the intensity of communication disturbances caused by node anomalies and recovery lags are as follows: Dynamically adjust the intensity and execution mode of the reset storm based on node status data; identify structural fluctuations and node response jitter caused by bus reset; control the reset rhythm and range; retrieve the event response message timestamp, disconnection start timestamp, number of erroneous nodes, and number of disconnected nodes from the communication node status data; calculate the recovery delay time by the difference between the timestamp of the first event response message generated after the disconnected node re-establishes connection in the unresponsive state and the disconnection start timestamp; add the number of erroneous nodes and the number of disconnected nodes in the current test cycle to obtain the total number of abnormal nodes; square the total number of abnormal nodes to obtain the cumulative disturbance intensity; take the recovery delay time and add one as the recovery baseline value; divide the cumulative disturbance intensity by the recovery baseline value to obtain the reset adjustment intensity value.

[0013] Furthermore, the specific steps for implementing tiered reset adjustment to modify the reset frequency, port execution permissions, and injection time point settings are as follows: Based on the reset adjustment intensity, tiered frequency control and error injection adjustment strategies are implemented: The reset adjustment intensity value and adjustment threshold are compared in real time, where the adjustment threshold includes a primary adjustment threshold and a secondary adjustment threshold. When the reset adjustment intensity value is greater than or equal to the primary adjustment threshold, the reset frequency is reduced, the reset interval is extended, and the reset source node port is prohibited from continuing to perform error injection operations. When the reset adjustment intensity value is greater than the secondary adjustment threshold but less than the primary adjustment threshold, the current reset frequency is maintained, and the connection status of the node with the highest response delay is written into the adjustment control. When the reset adjustment intensity value is less than or equal to the secondary adjustment threshold, the reset operation is paused, the error injection waiting time is shortened, and the error injection time point for the next round of test tasks is adjusted.

[0014] Furthermore, based on the node connection status updated according to the reset adjustment results, the specific steps for assessing the stability of the communication structure based on connection status changes and topology reconstruction deviations are as follows: The collected communication response status and inter-node connection relationships are structurally analyzed to reconstruct the communication topology change sequence during the reset process and locate the unstable regions of the communication structure; the node connection status is updated according to the reset adjustment results, including identifying whether the node port connection remains stable, whether the connection is interrupted or migrated, and indicating whether the current node is in a normal connection, disconnection isolation, or reconstruction waiting state, and adjusting the subsequent node test order and port enable configuration according to different states; simultaneously, the first effective response time of the node during the connection establishment process is recorded and compared with the connection start time. By comparing dynamic timestamps, the response delay offset is extracted as the node response offset feature; the connection state change, connection start timestamp, and connection stability timestamp are retrieved; the total time elapsed from the connection start timestamp to the connection stability timestamp after the communication topology is reset in this round of testing is calculated to obtain the reconstruction time; the reconstruction time of the communication topology in the stable state in historical tests is calculated and the reference maximum value is extracted to obtain the allowable delay upper limit; the number of connection state changes is squared to obtain the structural disturbance intensity; the difference between the reconstruction time and the allowable delay upper limit is calculated and the absolute value is taken, and one is added to the result as the adjustment benchmark for the delay deviation; the connection disturbance intensity is divided by the adjustment benchmark to finally calculate the structural connection fluctuation value.

[0015] Furthermore, the specific steps for controlling node connection permissions and data participation scope based on the assessment results are as follows: Node connection control strategies are determined based on the graded magnitude of structural connection fluctuations: The structural connection fluctuation value is compared with the structural stability threshold in real time; when the structural connection fluctuation value is greater than or equal to the structural stability threshold, ports are frozen for nodes whose connection status has changed in two consecutive rounds, prohibiting the establishment of connections and excluding response data from participating in topology reconstruction; when the structural connection fluctuation value is less than the structural stability threshold, dynamic connection permissions are opened, allowing connections to be established between previously disconnected nodes and newly online nodes, and the number of successful connections is counted.

[0016] Furthermore, when the structural stability assessment result is in an unstable state, the specific steps for determining the propagation strength and scope of the abnormal chain are as follows: Tracing back the communication anomaly propagation chain after the reset storm, accurately identifying the sequence of the first unstable node and the lost connection node; obtaining the number of interruptions, the end time stamp of the lost connection, and the start time stamp of the lost connection; calculating the difference between the end time stamp of the lost connection and the start time stamp of the lost connection for each node in the propagation path, and extracting the one with the longest duration to obtain the longest lost connection duration; multiplying the propagation modulation factor by the longest lost connection duration to obtain the propagation modulation product; taking the negative of the propagation modulation product as the exponent; calculating the exponential function value corresponding to the exponent term using the base of the natural logarithm as the base; adding one to the exponential function value to obtain the denominator; using the number of interruptions as the numerator, and performing a division operation between the denominator and the numerator to obtain the fault propagation strength value.

[0017] Further, the specific steps for determining the propagation level based on propagation characteristics are as follows: compare the fault propagation intensity value with propagation thresholds T1, T2, and T3, and obtain the corresponding propagation level based on the comparison results; when the fault propagation intensity value is greater than or equal to T3, it is rated as a critical chain isolation level; when the fault propagation intensity value is greater than or equal to T2 and less than T3, it is rated as a relay clearing level; when the fault propagation intensity value is greater than or equal to T1 and less than T2, it is rated as a temporary bypass level; when the fault propagation intensity value is less than T1, it is rated as an analysis skip level.

[0018] Furthermore, the specific steps for implementing node blocking, recovery waiting, and test exclusion control based on the propagation level status, and dynamically adjusting the propagation chain processing are as follows: When the propagation level is at the critical chain isolation level, port blocking and data removal operations are performed on the first abnormal node in the propagation path and the direct propagation nodes of the abnormal node to block the core path of the propagation chain and terminate the current error injection process; When the propagation level is at the relay clearing level, the disconnection time of each node is counted and the average value of the propagation chain nodes is calculated, and the average value of the propagation chain nodes is used as the longest waiting period; If the disconnection time of a node exceeds the longest waiting period, it is considered an unrecoverable node and removed from the subsequent test process; When the propagation level is at the temporary bypass level, a stable state confirmation period is inserted during the propagation chain construction process, allowing some recovered nodes to re-enter the test process, but not included in the calculation of the current fault propagation intensity value, while monitoring the stability of subsequent responses; When the propagation level is at the analysis skip level, it is determined that the propagation chain no longer has continuity, the current node configuration remains unchanged, the propagation chain analysis operation is paused and the relevant processing process is skipped, and the evaluation is re-entered after the propagation intensity increases again.

[0019] The second aspect of this invention provides an automated testing and fault detection system for multi-node bus communication protocols, comprising: a node data acquisition module, a reset adjustment execution module, a communication structure analysis module, and a fault path identification module. The node data acquisition module is used to acquire real-time response information, error injection feedback, and port status of each node in the communication bus, obtain communication node status data, and perform preprocessing. The reset adjustment execution module, based on the preprocessing of communication node status data, measures the intensity of communication disturbances caused by node anomalies and recovery lags, and performs graded reset adjustments to adjust the reset frequency, port execution permissions, and injection time point settings. The communication structure analysis module, based on the node connection status updated by the reset adjustment results, assesses the stability of the communication structure based on changes in connection status and topology reconstruction deviations, and manages node connection permissions and data participation scope according to the assessment results. The fault path identification module, when the structural stability assessment result is in an unstable state, determines the propagation intensity and scope of the abnormal chain, determines the propagation level state based on propagation characteristics, and performs node shielding, recovery waiting, and test exclusion control based on the propagation level state, while dynamically adjusting the propagation chain processing.

[0020] Beneficial effects

[0021] The present invention has the following beneficial effects:

[0022] (1) This invention improves the integrity and reliability of communication node status data by constructing a data structure covering multiple fields such as event response timestamp, error flag, and connection status, and by combining multi-source merging, register constraint completion and adaptive window compression methods, providing accurate support for subsequent intervention logic.

[0023] (2) This invention constructs a reset adjustment strength value by calculating the total number of faulty nodes, the number of disconnected nodes and the recovery delay. When dynamically adjusting the reset frequency and node port permissions, it can execute differentiated control logic accordingly, thereby enhancing the test process's adaptability to node jitter and structural fluctuations.

[0024] (3) The present invention combines the number of connection state changes and the time consumed by topology reconstruction to construct the structural connection fluctuation value, so that the control of node connection permissions and data participation scope has a quantifiable basis, and supports the automatic freezing of unstable nodes when structural disturbances intensify, thereby suppressing the spread of structural instability.

[0025] (4) The present invention constructs a propagation intensity value based on the number of interruptions and the longest disconnection time, and determines the propagation level by combining a set threshold. It automatically switches between multiple strategies such as shielding key nodes, excluding relay nodes, and observing by bypass nodes, which effectively improves the controllability of the test task and the ability to maintain local stability during the abnormal propagation process.

[0026] Of course, any product implementing this invention does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0027] Figure 1 This is a flowchart of the automated testing and fault detection method for the multi-node bus communication protocol of the present invention;

[0028] Figure 2 This is a structural diagram of the automated testing and fault detection system for the multi-node bus communication protocol of the present invention;

[0029] Figure 3 This is a distribution diagram of the reset adjustment intensity value of the present invention;

[0030] Figure 4 This is a diagram showing the duration of the loss of connection of nodes in the propagation chain of the present invention. Detailed Implementation

[0031] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0032] Please see Figures 1-4This invention provides a technical solution: an automated testing and fault detection method for multi-node bus communication protocols, comprising the following steps: S1: Collecting real-time response information, error injection feedback, and port status of each node in the communication bus, obtaining communication node status data and performing preprocessing; S2: Based on the preprocessing of communication node status data, measuring the intensity of communication disturbances caused by node anomalies and recovery lags, and performing graded reset adjustments to adjust the reset frequency, port execution permissions, and injection time point settings; S3: Based on the node connection status updated according to the reset adjustment results, assessing the stability of the communication structure based on connection status changes and topology reconstruction deviations, and controlling node connection permissions and data participation scope according to the assessment results; S4: When the structural stability assessment result is in an unstable state, determining the propagation intensity and impact range of the abnormal chain, determining the propagation level state based on propagation characteristics, and performing node shielding, recovery waiting, and test exclusion control based on the propagation level state, and dynamically adjusting the propagation chain processing.

[0033] Specifically, the real-time response information, error injection feedback, and port status of each node in the communication bus are collected to obtain communication node status data and perform preprocessing. The specific steps are as follows: First, the response behavior of each node during the communication process is continuously monitored. The joint set of nodes with CRC error fields and nodes with VPC error fields in the asynchronous stream messages collected in the current test cycle is counted, and the number of error nodes is obtained after deduplication. Nodes that have not received valid event responses in multiple consecutive test cycles are detected synchronously, and their number is extracted as the number of disconnected nodes. The node response time of each injected event is recorded, the event response message timestamp is extracted, and the start time of the node entering the continuous unresponsive state is identified to obtain the disconnection start timestamp. If the node generates a valid response again, the disconnection end timestamp is recorded. The time point of the first entry into the unresponsive state is tracked as the disconnection start timestamp, and the connection start timestamp is obtained by combining it with the time of the first establishment of the communication connection. The connection stability timestamp is then extracted by combining it with the time node of subsequent stable maintenance. The number of connection status changes is obtained by comparing the changes in the node connectivity relationship in two adjacent test cycles. At the same time, the cumulative number of times all nodes have failed to complete event responses in the interrupted state is summarized to calculate the number of interruptions. To ensure data validity, periodic consistency checks and event response frequency filtering methods are used to eliminate false response data caused by unstable connections, port disconnections, and incomplete resets. Based on this, multi-source merging rules are constructed according to error fields to merge and compress CRC and VPC error records of the same node appearing in multiple time slices. A window-adaptive time aggregation method is used to process the event response sequence, improving the accuracy of the time-series representation after data compression. Combined with the correlation constraint logic of register fields, layered completion and structured reconstruction are performed on missing and contradictory field information. Finally, standardization and normalization processing are uniformly performed on various node status data to adapt to the input structure of subsequent algorithms.

[0034] This implementation scheme enables high-precision extraction and structured cleaning of communication node status data, significantly improving the accuracy of anomaly identification and the temporal integrity of response data. Through multi-source field fusion, anomaly filtering, and field completion processing, a status data set with consistency, continuity, and comparability is constructed, providing reliable data support for subsequent reset adjustments and topology evaluation.

[0035] Specifically, based on the preprocessing of communication node status data, the intensity of communication disturbances caused by node anomalies and recovery lags is measured. The specific steps are as follows: Based on the cleaned node status data, the intensity and execution mode of the reset storm are dynamically adjusted. By identifying the state fluctuations and response anomalies of nodes during the reset process, it is determined whether the bus reset causes structural fluctuations and node response jitter, and the reset rhythm and scope of action are controlled accordingly. Key fields such as event response message timestamps, disconnection start timestamps, number of erroneous nodes, and number of disconnected nodes are retrieved from the node status data. The time difference between the abnormal state and the recovery state of the node is extracted, and the recovery delay time required for the disconnected node to re-establish the communication connection in the unresponsive state is calculated. The number of erroneous nodes and the number of disconnected nodes in the current test period are summed to obtain the total number of abnormal nodes, and the total number is squared to characterize the cumulative disturbance intensity. The recovery delay time is taken and added to construct a recovery benchmark value. The cumulative disturbance intensity is divided by the recovery benchmark value, and finally the reset adjustment intensity value reflecting the degree of communication anomaly impact is calculated.

[0036] The specific calculation method for the reset adjustment intensity value is as follows:

[0037]

[0038] In the formula, Indicates the reset adjustment intensity value. Indicates the number of faulty nodes. Indicates the number of lost nodes. Indicates the recovery delay time.

[0039] Table 1 shows the reset adjustment intensity value data table provided in the embodiments of this application. The error node count for adjustment 1 is set to 1.00, the number of lost nodes is set to 1.00, and the recovery delay time is set to 2.00; the error node count for adjustment 2 is set to 2.00, the number of lost nodes is set to 1.00, and the recovery delay time is set to 1.00; the error node count for adjustment 3 is set to 2.00, the number of lost nodes is set to 2.00, and the recovery delay time is set to 3.00; the error node count for adjustment 4 is set to 3.00, the number of lost nodes is set to 2.00, and the recovery delay time is set to 2.00; and the error node count for adjustment 5 is set to 4.00, the number of lost nodes is set to 2.00, and the recovery delay time is set to 4.00.

[0040] Table 1. Data on Reset Adjustment Intensity Values

[0041]

[0042] like Figure 3 The figure shows the distribution of reset adjustment intensity values ​​provided in the embodiments of this application. According to the data in the image and table, the first-level adjustment threshold is 5.00, the second-level adjustment threshold is 2.50, and the reset adjustment intensity values ​​corresponding to the five sets of data fluctuate between 1.33 and 8.33, showing an overall increasing trend followed by a slight decrease. The reset adjustment intensity values ​​of adjustment 4 and adjustment 5 are 8.33 and 7.20 respectively, both exceeding the first-level adjustment threshold, indicating significant communication structure disturbance, requiring frequency reduction reset and port shielding operations. The intensity values ​​of adjustment 2 and adjustment 3 are 4.50 and 4.00 respectively, between the second-level and first-level adjustment thresholds, suggesting maintaining the current reset rhythm and focusing on the status of delayed nodes. The intensity value of adjustment 1 is 1.33, below the second-level adjustment threshold, indicating a relatively minor disturbance; reset can be paused and the injection strategy adjusted. This figure can be used to intuitively determine the strength level of the current communication disturbance, providing an auxiliary basis for subsequent implementation of different reset adjustment measures.

[0043] This implementation scheme enables a quantitative expression of the impact of abnormal nodes during communication. By combining the number of abnormal nodes with the recovery speed, a disturbance intensity assessment index can be constructed, which helps to dynamically determine the adjustment level and execution range of the reset operation and improve the adaptive control capability of the testing process against communication structure fluctuations.

[0044] Specifically, a tiered reset adjustment is implemented to modify the reset frequency, port execution permissions, and injection timing. The specific steps are as follows: Based on the reset adjustment intensity, a tiered frequency control and error injection adjustment strategy is implemented. The current communication disturbance status is classified and managed through hierarchical thresholds. The reset adjustment intensity value is compared with the set primary and secondary adjustment thresholds in real time. When the reset adjustment intensity value is greater than or equal to the primary adjustment threshold, the current structural disturbance is considered to be large, and the reset frequency needs to be reduced and the reset interval extended. At the same time, the reset source node port is prohibited from operation to prevent further error injection from affecting structural stability. When the reset adjustment intensity value is between the secondary and primary adjustment thresholds, the existing reset frequency is maintained, and the connection status of the node with the longest response delay is written into the adjustment control for subsequent operation sequence optimization. When the reset adjustment intensity value is less than or equal to the secondary adjustment threshold, the current disturbance is considered to be weak, the reset operation is suspended to avoid excessive intervention, the waiting period before the next error injection is shortened, and the injection timing is reset to improve testing efficiency.

[0045] In this implementation scheme, the reset frequency, port permissions and injection rhythm are dynamically adjusted through a graded judgment mechanism of disturbance intensity, so that the reset operation is matched with the communication status, avoiding structural instability caused by excessive intervention and control lag, and enhancing the accuracy and process stability of reset adjustment.

[0046] Specifically, based on the node connection status updated by the reset adjustment results, the stability of the communication structure is evaluated based on the connection status changes and topology reconstruction deviations. The specific steps are as follows: First, the collected communication response status and the connection relationship between nodes are structurally analyzed to reconstruct the communication topology change sequence during the reset process, track the connection migration and breakage process, and locate structural regions that may become unstable. Based on the changes in the node connection status after the reset, it is determined whether the port connection of each node remains stable, whether there is an interruption, and whether the topology position has migrated. Based on this, the current node status is identified as normal connection, disconnection isolation, or reconstruction waiting. Further, the subsequent test sequence and port enable configuration are adjusted according to the node status. The first valid response during the connection establishment process is recorded simultaneously. The time is compared with the connection start timestamp to extract the response delay offset as the node response offset feature. At the same time, the connection state change number, connection start timestamp, and connection stabilization timestamp are called to calculate the total length of time it takes for the topology to complete connection stabilization after reset in this round of testing as the reconstruction time. Then, combined with the topology reconstruction time in the stable state of the structure in historical tests, the maximum reference value is extracted as the upper limit of allowable delay. The connection state change number is squared to obtain the structural disturbance intensity. The absolute value of the difference between the current reconstruction time and the upper limit of allowable delay is taken, and one is added to it as the adjustment benchmark for delay deviation. Finally, the structural disturbance intensity is divided by the adjustment benchmark to calculate the structural connection fluctuation value used to quantify structural stability.

[0047] The specific calculation method for structural connection fluctuation value is as follows:

[0048]

[0049] In the formula, Indicates the structural connection fluctuation value. This represents the number of connection state changes. Indicates the time taken for refactoring. This indicates the maximum allowed delay.

[0050] In this implementation plan, a structural connection fluctuation value is established by combining the magnitude of connection status changes and the deviation of reconstruction time. This value measures the stability of node connectivity and the degree of disturbance during the topology reconstruction process. It can determine whether the communication structure is unstable and adjust the scope of node participation and test order accordingly, thereby enhancing the accuracy of communication structure status identification and the pertinence of control.

[0051] Specifically, the node connection permissions and data participation scope are controlled based on the assessment results, and the specific steps are as follows: The node connection control strategy is determined according to the graded nature of structural connection fluctuations. The structural connection fluctuation value is compared with the structural stability threshold in real time, and the node's connectivity permissions and data processing scope are dynamically adjusted. When the structural connection fluctuation value is greater than or equal to the structural stability threshold, it indicates that the current communication structure is in an unstable state. For nodes whose connection status has continuously changed in two consecutive rounds, port freezing is implemented, prohibiting them from establishing communication connections with other nodes, and their response data is excluded from the topology reconstruction analysis to prevent further spread of disturbances. When the structural connection fluctuation value is lower than the structural stability threshold, the structure is considered to be stabilizing, and dynamic connection permissions are opened, allowing connections to be established between previously disconnected nodes and newly online nodes. Simultaneously, the actual number of successful connections is counted for subsequent assessment of reconstruction completion and node response recovery.

[0052] In this implementation plan, the node connectivity strategy is dynamically adjusted according to the degree of structural connection fluctuation. For unstable structural states, the connection permissions of nodes with high-frequency changes are restricted and their data is removed to avoid interfering with the topology reconstruction judgment. Under stable structural conditions, the connection permissions of lost nodes and new nodes are restored and their connection success status is statistically analyzed, thereby improving the control accuracy and node access effectiveness in the structural assessment stage.

[0053] Specifically, when the structural stability assessment result indicates an unstable state, the propagation strength and affected area of ​​the anomaly chain are determined. The specific steps are as follows: First, trace back the communication anomaly propagation chain that appeared after the reset storm, identify the location of the first occurrence of the anomaly and its evolution path, and accurately extract the sequence of the first unstable node and the consecutive disconnected nodes; obtain key propagation parameters, including the number of interruptions, the end time stamp of disconnection, and the start time stamp of disconnection for each node; calculate the duration of disconnection for each node, and extract the longest duration as the longest disconnection duration, which reflects the maximum risk point of chain breakage in the propagation chain. Multiply the longest disconnection duration by the propagation modulation factor to obtain the propagation modulation product. Construct a nonlinear adjustment function corresponding to the change in node disconnection duration, and extract the function growth rate in its sensitive section to obtain the propagation modulation factor, with a value range of 0.2-0.8. Take the negative of this product as the exponent term, and calculate its exponential function value with the base of the natural logarithm as the base. Add one to this value to construct the complete denominator. Then, with the number of interruptions as the numerator, use the above result as the denominator to perform a division operation, and finally obtain the fault propagation intensity value that characterizes the propagation chain diffusion intensity and the abnormal coverage area.

[0054] The specific calculation method for the fault propagation intensity value is as follows:

[0055]

[0056] In the formula, Indicates the fault propagation strength value. Indicates the number of interruptions. Indicates the longest period of no contact. This represents the propagation modulation factor.

[0057] In this implementation plan, key parameters such as interruption frequency and disconnection duration are extracted, a propagation modulation function is constructed, and the fault propagation intensity value is calculated to measure the transmission capability and impact range of the anomaly chain. This can reflect the speed and concentration of fault propagation in the communication structure, and provide a quantitative basis for subsequent propagation level determination and control strategy formulation.

[0058] Specifically, the propagation level is determined based on propagation characteristics, with the following steps: The calculated fault propagation intensity value is compared with the multi-level propagation thresholds T1, T2, and T3. Based on the attribution of propagation intensity in different intervals, the level of the abnormal propagation chain is determined. When the fault propagation intensity value is greater than or equal to T3, it is determined that the abnormal propagation has formed a concentrated diffusion trend and is rated as critical chain isolation level. When the fault propagation intensity value is between T2 and T3, it indicates that the propagation range has expanded but there is a possibility of interruption, and it is rated as relay clearing level. When the propagation intensity value is between T1 and T2, it indicates that the abnormal state is locally stagnant but still can be accessed for control, and it is rated as temporary bypass level. When the fault propagation intensity value is lower than T1, it indicates that the propagation chain is broken as a whole and its effect is weak, and it is rated as analysis skip level.

[0059] In this implementation plan, the diffusion level of the abnormal chain is determined based on the comparison results between the fault propagation intensity value and the multi-level threshold, so as to realize the hierarchical management of propagation risk. This can guide the differentiated execution of subsequent node screening, connection control and testing adjustment strategies, and enhance the accuracy of abnormal response and the hierarchical nature of adjustment logic.

[0060] Specifically, based on the propagation level status, node blocking, recovery waiting, and test exclusion controls are implemented, and the propagation chain processing is dynamically adjusted. The specific steps are as follows: When the propagation level is at the critical chain isolation level, it is determined that the propagation chain has formed a core diffusion. Port blocking and data removal operations are performed on the first abnormal node in the path and its directly propagating nodes to block the core propagation path and immediately stop the current error injection process to prevent expansion. When the propagation level is at the relay clearing level, the disconnection time of each node is counted and its average value is calculated. This average value is used as the longest waiting period. If the disconnection time of a node exceeds this period, it is determined to be an unrecoverable node and removed from the subsequent test process. When the propagation level is at the temporary bypass level, a stable state confirmation period is added during the propagation chain construction process, allowing some recovered nodes to reconnect to the test, but their data is not included in the current propagation intensity calculation, while monitoring the continuity of their subsequent responses. When the propagation level is at the analysis skip level, it is determined that the propagation chain has lost effective continuity. The existing node configuration remains unchanged, the current round of propagation chain processing is skipped, and it will only re-enter the evaluation after the propagation intensity rises again.

[0061] In this implementation plan, the handling method of abnormal nodes is dynamically adjusted according to the propagation level status. Port blocking, test rejection, delay waiting and status skipping operations are performed according to different levels. The participation boundaries of nodes and the scope of data retention are clearly defined, which helps to achieve refined diversion and phased intervention in the propagation control process, and improves test stability and anomaly handling efficiency.

[0062] like Figure 2The diagram shown is a structural schematic of the automated testing and fault detection system for multi-node bus communication protocols provided in this application embodiment. This system applies an automated testing and fault detection method for multi-node bus communication protocols and includes: a node data acquisition module, a reset and adjustment execution module, a communication structure analysis module, and a fault path identification module. The node data acquisition module is used to collect real-time response information, error injection feedback, and port status of each node in the communication bus, extract multi-dimensional status data containing error fields, response timing, and connection behavior, and perform preprocessing using filtering, compression, and completion strategies. The reset and adjustment execution module is used to, based on the preprocessing of the communication node status data, measure the impact of errors caused by faults in the communication bus. The system assesses the intensity of communication disturbances caused by node anomalies and recovery lags by constructing disturbance evaluation indicators and implementing graded reset adjustments accordingly. It dynamically adjusts reset frequency, port execution permissions, and error injection timing. A communication structure analysis module, based on the node connection status updated by reset adjustments and considering connection status changes and topology reconstruction deviations, constructs a structural connection fluctuation value to evaluate communication structure stability. Based on the evaluation results, it finely manages node connection permissions and data participation scope. A fault path identification module, when the structural stability evaluation result indicates an unstable state, calculates the fault propagation intensity by combining interruption frequency and disconnection duration, determines the propagation level, and implements node shielding, recovery waiting, and test exclusion controls based on the propagation level. It also dynamically adjusts the propagation chain processing strategy.

[0063] This implementation plan integrates the collection, adjustment, analysis and identification processes, and uses state data to drive reset control, structural evaluation and propagation handling to achieve continuous identification and dynamic response to communication anomalies, thereby improving the control accuracy and anomaly handling closed-loop capability in multi-node communication protocol testing.

[0064] like Figure 4 The figure shows the duration of node disconnection in the propagation chain provided in this embodiment of the application. The figure illustrates the start and end times of disconnection for five communication nodes and their corresponding durations. The horizontal axis represents time, and the vertical axis represents the node number. Node 1 disconnects between seconds 10 and 40, lasting 30 seconds; Node 2 disconnects between seconds 15 and 55, lasting 40 seconds; Node 3 disconnects between seconds 20 and 50, lasting 30 seconds; Node 4 disconnects between seconds 25 and 35, lasting 10 seconds; and Node 5 disconnects between seconds 30 and 70, lasting 40 seconds. Overall, nodes 2 and 5 have the longest disconnection times, both reaching 40 seconds, representing critical interruptions in the propagation chain; node 4 has the shortest disconnection time, only 10 seconds, indicating a relatively quick recovery. This figure can be used to assist in identifying persistently abnormal nodes in the propagation chain and to provide a time reference for calculating the fault propagation intensity value.

[0065] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0066] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A method for automated testing and fault detection of a multi-node bus communication protocol, characterized in that, The method comprises the following steps: S1: Collecting real-time response information, error injection feedback and port state of each node in the communication bus, obtaining communication node state data and preprocessing; S2: On the basis of completing the preprocessing of the communication node state data, measuring the communication disturbance intensity caused by node abnormalities and recovery lag, and performing reset adjustment in stages to adjust the reset frequency, port execution authority and injection time point setting; The specific steps of measuring the communication disturbance intensity caused by node abnormalities and recovery lag on the basis of completing the preprocessing of the communication node state data are as follows: Based on the node state data, the intensity and execution mode of the reset are dynamically adjusted to identify the structural fluctuations and node response jitter caused by the bus reset, and the reset rhythm and range are controlled; The event response message timestamp, disconnection start timestamp, error node number and disconnection node number are called from the communication node state data; The difference between the first event response message timestamp and the disconnection state start timestamp generated after the disconnection node reestablishes connection in the unresponsive state is calculated to obtain the recovery delay time; The error node number and the disconnection node number in the current test period are added to obtain the total amount of abnormal nodes; the total amount of abnormal nodes is squared to obtain the cumulative disturbance intensity; the recovery delay time is taken and one is added as the recovery reference value, and the cumulative disturbance intensity is divided by the recovery reference value to obtain the reset adjustment intensity value; S3: According to the node connection state updated by the reset adjustment result, the communication structure stability is evaluated based on the connection state change and the topology reconstruction deviation, and the node connection authority and data participation range are controlled according to the evaluation result; The topology reconstruction deviation is the reconstruction time consumption minus the upper limit of the allowed delay; S4: When the structure stability evaluation result is in an unstable state, the conduction intensity and the range of the abnormal chain are judged, the propagation level state is determined according to the propagation characteristics, and the processing process of the propagation chain is dynamically adjusted based on the propagation level state, including node shielding, waiting for recovery, test exclusion and control.

2. The multi-node bus communication protocol automated testing and fault detection method of claim 1, wherein: The specific steps of collecting real-time response information, error injection feedback and port state of each node in the communication bus, obtaining communication node state data and preprocessing are as follows: The real-time response information, error injection feedback and port state of each node in the communication bus are collected, and the communication node state data acquisition process comprises: obtaining the number of error nodes by removing duplicates from the joint set of nodes with CRC error fields and nodes with VPC error fields in the asynchronous stream messages collected in the current test period; obtaining the number of lost nodes by detecting the number of nodes that have not received valid event responses for a plurality of consecutive test periods; obtaining the event response message timestamp by recording the specific time at which the node responds to the injected event; obtaining the lost start timestamp by identifying the initial time at which the node enters the continuous non-response state; obtaining the lost end timestamp by marking the time at which the node generates a valid response again; obtaining the lost start timestamp by tracking the time point at which the node enters the first non-response state; obtaining the connection start timestamp by tracking the time at which the node first establishes a valid communication connection; obtaining the connection stable timestamp by judging the time node after the communication is continuously stable; obtaining the connection state change number by comparing the number of nodes whose connection relationship changes in adjacent two test periods; obtaining the interruption number by summing up the cumulative number of times that the node does not complete event response in the interruption state; Through the periodic consistency detection and event response frequency screening method, false response data caused by unstable node connection, port disconnection and incomplete reset are eliminated; based on the multi-source merging rule of error fields, the CRC and VPC error records of the same node appearing in different time slices are integrated; the window adaptive time aggregation method is used to merge and compress the event response sequence; combined with the register state association constraint mechanism, the node data with missing and inconsistent register fields in the collection process is filled and reconstructed in layers; the communication node state data is standardized and normalized.

3. The multi-node bus communication protocol automated testing and fault detection method of claim 1, wherein: The specific steps of the hierarchical reset adjustment to adjust the reset frequency, port execution authority and injection time point setting are as follows: According to the reset adjustment intensity, the frequency control and error injection adjustment strategy is executed in stages: real-time comparison of the reset adjustment intensity value and the adjustment threshold value, the adjustment threshold value comprising a first adjustment threshold value and a second adjustment threshold value; When the reset adjustment intensity value is greater than or equal to the first adjustment threshold value, the reset frequency is reduced, the reset interval is extended, and the error injection operation of the reset source node port is prohibited; When the reset adjustment intensity value is greater than the second adjustment threshold value and less than the first adjustment threshold value, the current reset frequency is maintained, and the connection state of the node with the highest response delay is written into the adjustment control; when the reset adjustment intensity value is less than or equal to the second adjustment threshold value, the reset operation is suspended, the error injection waiting time is shortened, and the error injection time point of the next test task is adjusted.

4. The multi-node bus communication protocol automated testing and fault detection method of claim 1, wherein: The specific steps of evaluating the communication structure stability based on the connection state change and topology reconstruction deviation according to the reset adjustment result updated node connection state are as follows: The collected communication response state and inter-node connection relationship are structured and analyzed, the communication topology change sequence in the reset process is reconstructed, and the communication structure instability area is located; the node connection state updated according to the reset adjustment result, including identifying whether the node port connection remains stable, whether the connection is interrupted or migrated, identifying whether the current node is in a normal connection, a disconnection isolation or a reconstruction waiting state according to the node connection state, and adjusting the subsequent node test order and port enable configuration according to different states; the first effective response time of the node in the connection establishment process is recorded and compared with the connection start timestamp, and the response delay offset is extracted as the node response offset feature; Call the connection state change, the connection start timestamp and the connection stable timestamp; The total length of time experienced by the communication topology structure after the reset is completed in the current test is obtained, from the connection start timestamp to the connection stable timestamp, to obtain the reconstruction time consumption; the reconstruction time consumption of the communication topology in the stable state of the structure in the historical test is counted and the reference maximum value is extracted to obtain the upper limit of the allowed delay; The connection state change number is squared to obtain the structure disturbance intensity; the difference between the reconstruction time consumption and the upper limit of the allowed delay is calculated and the absolute value is taken, and one is added to the result as the adjustment reference of the delay deviation; the structure connection fluctuation value is finally calculated by dividing the connection disturbance intensity by the adjustment reference.

5. The multi-node bus communication protocol automated testing and fault detection method of claim 1, wherein: The specific steps of controlling the node connection permission and data participation range according to the evaluation result are as follows: Determine the node connection control strategy according to the structure connection fluctuation amplitude: compare the structure connection fluctuation value with the structure stable threshold value in real time; when the structure connection fluctuation value is greater than or equal to the structure stable threshold value, execute port freezing for the nodes whose connection states change continuously in the last two rounds, prohibit connection establishment and exclude response data from participating in topology reconstruction; when the structure connection fluctuation value is less than the structure stable threshold value, open the dynamic connection permission, allow the establishment of connection between the last round of disconnection nodes and the current newly online nodes, and count the number of successful connections.

6. The multi-node bus communication protocol automated testing and fault detection method of claim 1, wherein: The specific steps of judging the conduction intensity and the range of the abnormal chain when the structure stability evaluation result is in an unstable state are as follows: Trace back the communication abnormal propagation chain after reset, accurately identify the first unstable node and the disconnection node sequence; obtain the number of interruptions, the disconnection end timestamp and the disconnection start timestamp; calculate the difference between the disconnection end timestamp and the disconnection start timestamp of each node in the propagation path, and extract the longest one from the difference to obtain the longest disconnection duration; Multiply the propagation modulation factor by the longest disconnection duration to obtain the propagation modulation product; take the opposite of the propagation modulation product as the exponential term; calculate the exponential function value corresponding to the exponential term with the base of the natural logarithm as the base; add one to the exponential function value to obtain the denominator; take the number of interruptions as the numerator, and divide the numerator by the denominator to obtain the fault propagation intensity value; The propagation modulation factor is obtained by constructing a nonlinear adjustment function corresponding to the change of the node disconnection duration and extracting the function growth rate in the sensitive section.

7. The multi-node bus communication protocol automated testing and fault detection method of claim 1, wherein: The specific steps of determining the propagation level state according to the propagation characteristics are as follows: The fault propagation intensity value is compared with the propagation thresholds T1, T2 and T3, and a corresponding propagation level is obtained according to the comparison result; When the fault propagation intensity value is greater than or equal to T3, the critical chain isolation level is evaluated; When the fault propagation intensity value is greater than or equal to T2 and less than T3, the relay clearing level is evaluated; When the fault propagation intensity value is greater than or equal to T1 and less than T2, the temporary storage bypass level is evaluated; When the fault propagation intensity value is less than T1, the analysis skipping level is evaluated.

8. The multi-node bus communication protocol automated testing and fault detection method of claim 1, wherein: The node shielding, recovery waiting and test exclusion control are performed based on the propagation level state, and the propagation chain processing is dynamically adjusted, and the specific steps are as follows: When the propagation level is in the critical chain isolation level, the port shielding and data rejection operation is performed on the first abnormal node and the direct propagation node of the abnormal node in the propagation path, the core path of the propagation chain is blocked, and the current error injection process is terminated; When the propagation level is in the relay clearing level, the disconnection time of each node is counted and the average value of the propagation chain nodes is calculated, and the average value of the propagation chain nodes is taken as the longest waiting period; if the disconnection time of a node exceeds the longest waiting period, the node is considered as an unrecoverable node and is removed from the subsequent test process; When the propagation level is in the temporary storage bypass level, a stable state confirmation period is inserted during the construction of the propagation chain, that is, when the propagation level is in the temporary storage bypass level, to determine whether the node is recovered, allowing part of the recovered nodes to re-enter the test process, but not counted in the calculation of the current fault propagation intensity value, while monitoring the stability of the subsequent response; When the propagation level is in the analysis skipping level, it is judged that the propagation chain has no continuity, the current node configuration is maintained unchanged, the propagation chain analysis operation is suspended and the related processing process is skipped, and after the propagation intensity is increased again, the evaluation is re-entered.

9. A multi-node bus communication protocol automated testing and fault detection system applying the multi-node bus communication protocol automated testing and fault detection method of any one of claims 1-8, comprising: The node data acquisition module, the reset adjustment execution module, the communication structure analysis module and the fault path identification module are characterized by: The node data acquisition module is used to collect real-time response information, error injection feedback and port state of each node in the communication bus, obtain communication node state data and perform preprocessing; The reset adjustment execution module is used to measure the communication disturbance intensity caused by node abnormality and recovery lag on the basis of completing the preprocessing of the communication node state data, and to perform reset adjustment in stages to adjust the reset frequency, port execution authority and injection time point setting; The communication structure analysis module is used to update the node connection state based on the reset adjustment result, evaluate the communication structure stability based on the connection state change and topology reconstruction deviation, and control the node connection authority and data participation range according to the evaluation result; The fault path identification module is used to judge the conduction intensity and spread range of the abnormal chain when the structure stability evaluation result is in the unstable state, determine the propagation level state according to the propagation characteristics, perform node shielding, recovery waiting and test exclusion control based on the propagation level state, and dynamically adjust the propagation chain processing.

Images