Intelligent terminal mainboard function verification system based on multi-protocol compatibility

Abstract

The invention belongs to the technical field of intelligent terminal mainboard testing, and discloses an intelligent terminal mainboard function verification system based on multi-protocol compatibility. Comprising a data acquisition module used for performing benchmark testing on each communication protocol supported by the intelligent terminal mainboard to obtain a benchmark data set of the intelligent terminal mainboard; the analysis and sequence generation module is used for acquiring a resource consumption portrait of the intelligent terminal mainboard; generating a concurrent test instruction sequence based on a pre-constructed test sequence generation engine; the concurrent test and diagnosis module is used for acquiring a concurrent test operation log by executing the concurrent test instruction sequence; identifying a causal relationship between a protocol performance degradation event and a resource state abnormal event based on the concurrent test operation log, and forming a resource protocol conflict event record; and the diagnosis and report generation module is used for acquiring diagnosis results of the resource protocol conflict events and further analyzing and generating a comprehensive verification report, so that a clear decision basis is provided.

Description

Technical Field

[0001] This invention relates to the field of smart terminal motherboard testing technology, and more specifically, to a smart terminal motherboard functional verification system based on multi-protocol compatibility. Background Technology

[0002] With the rapid development of mobile communication, smart terminal devices need to support multiple communication protocols to meet the needs of different application scenarios. In order to ensure the stable operation of the device in various communication environments, the functional verification of the smart terminal motherboard has become a key step.

[0003] In existing technologies, the verification of smart terminal motherboards mainly adopts an independent testing method for a single protocol. This involves constructing isolated test environments for each communication protocol, performing benchmark performance tests on each protocol, and judging the compliance of the protocol functions by comparing them with technical specifications or compatibility standards. However, different communication protocols may compete for shared system resources when executed concurrently. Such competition often leads to intermittent degradation of protocol performance or abnormal fluctuations in system resource status. Existing technologies struggle to accurately identify the causal relationship between abnormal protocol data and abnormal motherboard resource data status. For example, during the verification process of a laptop motherboard, when the Wi-Fi 6 module and the USB 4.0 interface are simultaneously transferring large files, they may compete for shared chipset bus bandwidth or memory access channels, potentially causing periodic fluctuations in Wi-Fi 6 throughput or an increase in USB 4.0 data transmission latency. System monitoring can only record an overall increase in bus load or memory control unit utilization, making it difficult to attribute such performance degradation events to resource competition between specific protocols. This results in a lack of targeted suggestions for subsequent hardware optimization or driver debugging.

[0004] In view of this, the present invention proposes a multi-protocol compatible smart terminal motherboard function verification system to solve the above problems. Summary of the Invention

[0005] To overcome the aforementioned deficiencies of the prior art and to achieve the above objectives, the present invention provides the following technical solution: a multi-protocol compatible smart terminal motherboard function verification system, comprising: The data acquisition module is used to perform benchmark tests on each communication protocol supported by the smart terminal motherboard and obtain the benchmark dataset of the smart terminal motherboard. The analysis and sequence generation module is used to obtain a resource consumption profile of the smart terminal motherboard by analyzing the benchmark dataset; and to generate a concurrent test instruction sequence based on the analysis of the resource consumption profile using a pre-built test sequence generation engine. The concurrent testing and diagnostic module is used to obtain performance data of the communication protocol and resource status data of the smart terminal motherboard by executing a sequence of concurrent testing instructions to form a concurrent test run log; based on the concurrent test run log, it identifies the causal relationship between protocol performance degradation events and resource status abnormal events to form a resource protocol conflict event record; The diagnosis and report generation module is used to analyze the diagnostic results of various resource protocol conflict events and further analyze and generate a comprehensive verification report.

[0006] Furthermore, the process of obtaining the benchmark dataset of the smart terminal motherboard is as follows: Obtain all communication protocols supported by the smart terminal motherboard, as well as the corresponding technical specifications for each communication protocol; set up several test cases for each communication protocol, determine the test parameters and load levels for each test case based on the parameters in the technical specifications, and assign a unique identifier to each test case. For each communication protocol, execution begins with the test case at its lowest load level, collecting baseline performance data and baseline resource status data of the smart terminal motherboard corresponding to each test case; the baseline performance data and baseline resource status data of each test case are associated and aligned according to timestamps to form a baseline test record containing identifiers, timestamps, performance data, and resource status data; the baseline test records of all communication protocols are summarized to form a baseline dataset.

[0007] Furthermore, the process of obtaining a resource consumption profile of the smart terminal motherboard is as follows: Extract all benchmark test records corresponding to each communication protocol from the benchmark dataset; calculate the mean and peak values ​​of the benchmark resource status data in each benchmark test record; integrate the mean and peak values ​​under the same load level according to the load level of the test case to form the resource indicator statistics of each test case; perform correlation analysis on the benchmark performance data and benchmark resource status data of each test case of the communication protocol to determine the correlation metric between the benchmark resource status data and the benchmark performance data. The resource consumption feature vector is formed by integrating the resource metric statistics and related metrics corresponding to each test case of the communication protocol; the resource consumption feature vectors of all communication protocols are then integrated to form a resource consumption profile of the smart terminal motherboard.

[0008] Furthermore, the specific process of pre-building the test sequence generation engine is as follows: A test sequence generation engine is constructed, comprising an analysis layer, a decision layer, and an output layer. The analysis layer is configured with resource consumption pattern recognition rules that classify test cases based on several resource-intensive pattern judgment thresholds, and resource conflict weight calculation rules that calculate the difference between statistical indicators of the same type of resource based on two test cases. The decision layer is configured with a test sequence optimization algorithm. The output layer stores executable test command templates corresponding to various communication protocols and load levels.

[0009] Furthermore, the specific process of generating the concurrent test instruction sequence is as follows: The resource consumption profile of the smart terminal motherboard is input into the analysis layer of the test sequence generation engine. Based on the resource consumption pattern recognition rules, test cases whose resource consumption feature vectors exceed the corresponding resource-intensive pattern judgment threshold are classified into various resource-intensive test case sets. Based on the resource conflict weight calculation rules, test cases in different resource-intensive test case sets are combined in pairs to obtain the resource conflict weight of each test case combination. The decision layer sorts all test case combinations in descending order according to resource conflict weights based on the test sequence optimization algorithm, and selects several test cases with the highest ranking to form a concurrent test sequence; the output layer calls the corresponding executable test command template based on the concurrent test sequence to generate a concurrent test command sequence containing protocol initialization instructions and test load triggering instructions.

[0010] Furthermore, the specific process for generating concurrent test run logs is as follows: A concurrent test execution environment is built based on the concurrent test instruction sequence. The corresponding protocol initialization instructions and test load triggering instructions are executed sequentially according to the timestamp order of the concurrent test instruction sequence. The performance data of each communication protocol and the resource status data of the smart terminal motherboard collected synchronously are associated with the identifier and communication protocol name of the corresponding test case to form a test case execution record. The execution records of all test cases during the testing process are summarized to form a concurrent test run log.

[0011] Furthermore, the specific process for creating a resource agreement conflict event record is as follows: Read the time series of protocol performance data and resource status data of all test case execution records in the concurrent test run log; determine the standard range of protocol performance data and resource status data based on the technical specifications of the smart terminal motherboard; The points in time when the protocol performance data time series and resource status data time series deviate from their corresponding standard ranges are marked as the starting points of the protocol performance degradation event and the resource status abnormal event, respectively, and the specific resource type corresponding to each resource status abnormal event is recorded; the starting points of time consecutive and belonging to the same test case are merged into one protocol performance degradation event; the starting points of time consecutive and belonging to the same resource type are merged into one resource status abnormal event. The causal relationship between protocol performance degradation events and resource status anomaly events is determined, and resource status anomaly events with causal relationship are combined with protocol performance degradation events to form a resource protocol conflict event record.

[0012] Furthermore, the specific process for determining the causal relationship between protocol performance degradation events and abnormal resource status events is as follows: For each protocol performance degradation event, all resource status anomaly events with a starting point earlier than or equal to the starting point of the protocol performance degradation event are selected. Based on the correlation metric established in the benchmark test by the test cases that generated the protocol performance degradation event, the correlation strength between the resource status anomaly event and the protocol performance degradation event is analyzed and determined. If the correlation strength reaches the preset strength threshold, it is determined that there is a causal relationship between the two; otherwise, there is no causal relationship.

[0013] Furthermore, the process of obtaining the diagnostic results of various resource protocol conflict events is as follows: For each resource protocol conflict event record, the nature of the conflict is determined based on the abnormal resource type corresponding to the abnormal resource status event; the magnitude of the deviation of protocol performance data from the standard range in the protocol performance degradation event is calculated to determine the impact intensity; and the risk level of the resource protocol conflict event record is determined based on the impact intensity; the nature of the conflict, the impact intensity, and the risk level of the resource protocol conflict event record are integrated to form a diagnostic result.

[0014] Furthermore, the process of generating the comprehensive verification report is as follows: The diagnostic results of all resource protocol conflict events are summarized, and the diagnostic results are grouped and statistically analyzed according to the communication protocol type to obtain statistical results including the distribution of conflict frequency, risk level, and conflict nature of each communication protocol. Based on the statistical results, a comprehensive verification report including protocol compatibility assessment and improvement suggestions is generated.

[0015] The technical effects and advantages of this invention, based on a multi-protocol compatible smart terminal motherboard function verification system, are as follows: 1. This invention constructs a benchmark dataset and generates a resource consumption profile, quantifying the resource consumption characteristics of various communication protocols under different loads and their correlation with performance. This provides a data-driven foundation for the generation of concurrent test instruction sequences. Through a pre-built test sequence generation engine, based on resource consumption pattern recognition rules and resource conflict weight calculation rules, it intelligently filters test case combinations with high resource conflict risk from the resource consumption profile and generates concurrent test instruction sequences. This process shifts the testing focus from broad protocol function coverage to targeted stress scenarios that expose compatibility defects with a high probability, significantly improving testing efficiency and problem discovery capabilities. 2. This invention acquires and generates concurrent test logs by executing a sequence of concurrent test instructions. It can automatically identify protocol performance degradation events and resource status anomalies, and make causal relationship judgments based on the correlation metrics established in benchmark tests, forming a record of resource protocol conflict events. This mechanism realizes automation and precision from observing concurrent failure phenomena to locating the root cause of internal resource conflicts. On this basis, the risk level is determined by analyzing the impact intensity and conflict nature of each conflict event, and statistical analysis is performed by grouping according to communication protocol type. The final comprehensive verification report can quantitatively present the protocol compatibility level of the motherboard, and provide root cause improvement suggestions based on the distribution of conflict nature, providing a clear decision-making basis for hardware resource allocation and driver optimization. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the smart terminal motherboard function verification system based on multi-protocol compatibility according to the present invention; Figure 2 This is a flowchart illustrating the generation of concurrent test instruction sequences in this invention; Figure 3 This is a flowchart for generating resource protocol conflict event records for this invention. Detailed Implementation

[0017] 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.

[0018] Example 1 Please see Figures 1-3 As shown in this embodiment, the main design background of the multi-protocol compatible smart terminal motherboard function verification system is as follows: Modern smart terminal motherboards need to integrate and support multiple communication protocols, such as Wi-Fi, Bluetooth, cellular networks, and GNSS, to achieve complex interconnection functions. In practical applications, these communication protocols often need to work simultaneously. However, when multiple protocols run concurrently, they compete for the limited hardware resources on the smart terminal motherboard, such as CPU computing power, memory bandwidth, and bus access permissions. This resource competition may cause a single protocol to perform normally when tested independently, but to experience severe performance degradation in multi-protocol concurrent scenarios, such as a sharp drop in throughput, a surge in transmission latency, or even communication link interruption. Such protocol compatibility issues caused by resource conflicts are highly concealed and difficult to reproduce.

[0019] Based on this, a multi-protocol compatible smart terminal motherboard functional verification system is designed, including: The data acquisition module is used to perform benchmark tests on each communication protocol supported by the smart terminal motherboard and obtain the benchmark dataset of the smart terminal motherboard.

[0020] The specific process of obtaining the benchmark dataset for the smart terminal motherboard is as follows: Obtain all communication protocols supported by the smart terminal motherboard, along with their corresponding technical specifications. Review the smart terminal motherboard's hardware design documents and product manuals, extracting the names of the communication protocols explicitly supported by the motherboard, and record all names to form a communication protocol list. For each communication protocol, extract parameter information related to the smart terminal motherboard's performance, including but not limited to transmission rate range, maximum number of connected devices, bandwidth requirements, operating frequency range, and bit error rate. Organize this parameter information into the corresponding technical specifications for each communication protocol, ensuring a one-to-one correspondence between the technical specifications and the protocol itself.

[0021] Several test cases are set up for each communication protocol. Based on the parameters in the technical specifications, the test parameters and load levels for each test case are determined, and a unique identifier is assigned to each test case. Each test case is used to verify a specific function or performance characteristic of the corresponding communication protocol. Using the technical specifications for each communication protocol, the test scenarios to be covered by each protocol are determined, and parameters related to that test scenario are selected as the test parameters for that test case.

[0022] Load level refers to the resource load level set for different test cases during the testing process; it is based on the test parameter values ​​of the test cases, for example, the load level is divided into three levels: low load level, medium load level, and high load level according to the high and low values ​​of the test parameters.

[0023] Each test case is assigned a unique identifier in the format of "Full Name of Communication Protocol - Test Case Number - Load Level".

[0024] For each communication protocol, execution begins with the test case at its lowest load level, collecting baseline performance data and baseline resource status data of the smart terminal motherboard for each test case. Baseline resource status data refers to the resource consumption of the smart terminal motherboard while running test cases; baseline performance data refers to the performance data of the smart terminal motherboard under different communication protocols and load levels during testing. Communication protocols are selected sequentially according to the list, and execution begins in ascending order of load level (low load level test cases are executed first, then medium load level test cases, and finally high load level test cases).

[0025] During the execution of each test case, baseline performance data (such as throughput, transmission latency, and bit error rate) for the current test case is read and recorded from the statistics interface of the communication protocol stack. Baseline resource status data (such as CPU utilization, memory usage, and bus bandwidth utilization) for the smart terminal motherboard are read and recorded from the operating system kernel resource manager of the smart terminal motherboard at the same time intervals. When the duration defined by the test case ends, data collection is stopped and the moment is recorded as the test end timestamp.

[0026] The baseline performance data and baseline resource status data of each test case are associated and aligned according to the timestamp to form a baseline test record containing identifiers, timestamps, performance data and resource status data; the baseline test records of all communication protocols are summarized to form a baseline dataset.

[0027] The analysis and sequence generation module is used to obtain a resource consumption profile of the smart terminal motherboard by analyzing the benchmark dataset; and to generate a concurrent test instruction sequence based on the analysis of the resource consumption profile using a pre-built test sequence generation engine.

[0028] The process of obtaining a resource consumption profile of a smart terminal motherboard is as follows: Extract all benchmark records corresponding to each communication protocol from the benchmark dataset; calculate the mean and peak values ​​of the benchmark resource status data in each benchmark record. Traverse each benchmark record in the benchmark dataset, and classify the benchmark record into its corresponding communication protocol according to the identifier and communication protocol name in each benchmark record. Calculate the average and maximum values ​​(i.e., peak values) of each resource (CPU utilization, memory usage, bus bandwidth utilization, motherboard power consumption) in the resource status data throughout the entire recording period.

[0029] Based on the load level of the test cases, the average and peak values ​​under the same load level are integrated to form the resource metric statistics for each test case.

[0030] For example, the benchmark test record for the test case "WiFi Protocol-1-Low" contains 10 benchmark test records. After calculating the mean and peak CPU utilization in each record, the mean and peak CPU utilization of these 10 records are averaged. Then, the mean and peak memory utilization and the mean and peak bus bandwidth utilization are averaged in turn to form the resource metric statistics for the corresponding test case.

[0031] Correlation analysis was performed on the baseline performance data and baseline resource status data for each test case of the communication protocol to determine the correlation metric between the baseline resource status data and the baseline performance data. The Pearson correlation coefficient between the baseline performance data and the baseline resource status data of the test case was calculated as the correlation metric between each pair of "performance data-resource status data (such as throughput and CPU utilization)".

[0032] Resource consumption feature vectors are formed by integrating the resource metric statistics and related metrics corresponding to each test case of the communication protocol. These feature vectors are then integrated to create a resource consumption profile of the smart terminal motherboard. Each test case's resource consumption feature vector includes the test case's load level, resource metric statistics, and all related metrics. The resource consumption feature vectors of all communication protocols are then structurally integrated according to protocol type, creating a data structure containing the communication protocol name, load level identifier, and resource consumption feature vector, thus forming the resource consumption profile of the smart terminal motherboard. This resource consumption profile quantifies the resource behavior patterns of each protocol under different loads.

[0033] The specific process of pre-building the test sequence generation engine is as follows: A test sequence generation engine is constructed, comprising an analysis layer, a decision layer, and an output layer. The analysis layer is configured with resource consumption pattern recognition rules that classify test cases based on several resource-intensive pattern determination thresholds. These rules analyze the resource consumption feature vectors of test cases and determine whether they belong to resource-intensive patterns. The type and number of resource-intensive pattern determination thresholds correspond to the resource types contained in the resource consumption feature vectors. For example, if the resource consumption feature vectors contain four resource types—CPU utilization, memory usage, bus bandwidth utilization, and motherboard power consumption—then four corresponding resource-intensive pattern determination thresholds are set: CPU-intensive pattern determination threshold, memory-intensive pattern determination threshold, bus-intensive pattern determination threshold, and power-intensive pattern determination threshold.

[0034] It should be explained that the thresholds for the aforementioned resource-intensive modes were determined based on the technical specifications of the smart terminal motherboard and statistical analysis of historical benchmark datasets.

[0035] And a resource conflict weight calculation rule based on the difference calculation of statistical quantities of the same type of resource based on two test cases; the resource conflict weight calculation rule is used to calculate the resource conflict weight of the combination of two test cases. After normalizing the statistical quantities of the same type of resource for the two test cases, the difference is calculated, and after taking the absolute value, the absolute values ​​of all resource types are added together to obtain the sum as the resource conflict weight.

[0036] The decision-making layer is configured with a test sequence optimization algorithm. The test sequence optimization algorithm is set to optimize the generated test sequences. Its purpose is to prioritize test case combinations with high resource conflict weights so as to ensure that concurrent tests can efficiently expose the most serious resource conflict problems.

[0037] The output layer stores executable test command templates corresponding to each communication protocol and load level. These templates are specific test instruction formats, storing initialization and load triggering instructions for each communication protocol and load level.

[0038] The specific process of generating a concurrent test instruction sequence is as follows: The resource consumption profile of the smart terminal motherboard is input into the analysis layer of the test sequence generation engine. Based on the resource consumption pattern recognition rules, test cases whose resource consumption feature vectors exceed the corresponding resource-intensive pattern judgment threshold are classified into various resource-intensive test case sets. The resource consumption pattern recognition rules traverse each resource consumption feature vector in the resource consumption profile of the smart terminal motherboard and perform the following judgment: if the mean or peak value of a certain baseline resource status data in the resource consumption feature vector exceeds the resource-intensive pattern judgment threshold set for that resource, then the test case corresponding to this resource consumption feature vector is marked as a resource-intensive test case, thus forming various resource-intensive test case sets.

[0039] For example: a certain resource consumption feature vector: average and peak CPU utilization (75%, 95%); average and peak memory utilization (3.2GB, 4.8GB); average and peak bus bandwidth utilization (70%, 72%); average and peak motherboard power consumption (18W, 25W). Resource-intensive mode determination thresholds: CPU-intensive mode determination threshold (average CPU utilization greater than 70% or peak CPU utilization greater than 85%); Memory-intensive mode determination threshold (average memory usage greater than 3.3GB or peak memory usage greater than 4.9GB); Bus-intensive mode determination threshold (average bus bandwidth utilization greater than 70% or peak bus bandwidth utilization greater than 80%); Power-intensive mode determination threshold (average motherboard power consumption greater than 19W or peak motherboard power consumption greater than 26W). Identification is performed using resource consumption pattern recognition rules: if the average CPU utilization rate in the resource consumption feature vector exceeds the CPU-intensive pattern judgment threshold of 70%, the test cases corresponding to this resource consumption feature vector are classified into the CPU-intensive test case set.

[0040] It should be explained that if a resource consumption feature vector meets the judgment results of multiple resource-intensive mode judgment thresholds, then the test cases corresponding to the resource consumption feature vector will be classified into the set of qualified resource-intensive test cases.

[0041] Based on the resource conflict weight calculation rules, test cases from different resource-intensive test case sets are paired up to obtain the resource conflict weight for each test case pair. The resource conflict weight represents the degree of conflict caused by competition for the same resource between test cases. Test cases are paired up to generate test case pairs from different resource-intensive test case sets (e.g., selecting one test case from the CPU-intensive test case set and one test case from the memory-intensive test case set to form a test case pair). For each test case pair, the difference between the statistics of each resource indicator in the two resource consumption feature vectors is calculated, and then the differences are summed to obtain the resource conflict weight of the test case pair.

[0042] The decision-making layer sorts all test case combinations in descending order according to resource conflict weights based on the test sequence optimization algorithm, and selects several test case combinations with the highest ranking to form a concurrent test sequence. The test sequence optimization algorithm selects the combination with the highest resource conflict weight from the descending test case combinations according to the set optimization objectives (e.g., maximizing the coverage of different communication protocol pairs and the coverage of conflict scenarios of different resource types within a limited test time) and constraints (the total number of test case combinations finally selected must not exceed a preset upper limit). When the number of selected test case combinations reaches the preset upper limit, the selection stops, thus forming a concurrent test sequence.

[0043] The output layer calls the corresponding executable test command template based on the concurrent test sequence to generate a concurrent test command sequence containing protocol initialization instructions and test load triggering instructions. The output layer locates the corresponding executable test command template based on the unique identifier of each test case in the concurrent test sequence, generating two instructions for each test case: a protocol initialization instruction and a test load triggering instruction. All protocol initialization instructions and test load triggering instructions for all test case combinations are organized into groups, and each instruction is assigned an execution timestamp, ultimately forming the concurrent test command sequence.

[0044] The concurrent testing and diagnostic module is used to obtain performance data of the communication protocol and resource status data of the smart terminal motherboard by executing a sequence of concurrent testing instructions to form a concurrent test run log; based on the concurrent test run log, it identifies the causal relationship between protocol performance degradation events and resource status abnormal events to form a resource protocol conflict event record.

[0045] The specific process for generating concurrent test run logs is as follows: A concurrent test execution environment is built based on a concurrent test instruction sequence. The corresponding protocol initialization instructions and test load triggering instructions are executed sequentially according to the timestamp order of the concurrent test instruction sequence. The concurrent test execution environment refers to the test environment built to ensure that multiple test cases can be executed simultaneously without interfering with each other, including hardware connection setup and software configuration initialization. The protocol initialization instructions are used to start and configure the communication protocol of the test target device. The test load triggering instructions are used to simulate the load under real application scenarios to test the performance of the smart terminal motherboard under different load conditions.

[0046] The concurrent test execution environment is configured to parse the execution timestamp of each instruction in the concurrent test instruction sequence. These instructions are sent to and executed sequentially to the smart terminal motherboard in the order of timestamps. First, the protocol initialization instruction is executed to complete the protocol preparation, and then the test load trigger instruction is executed to realize the concurrent testing of multiple protocols.

[0047] The performance data of each communication protocol and the resource status data of the smart terminal motherboard collected synchronously are associated with the identifiers and communication protocol names of the corresponding test cases to form a test case execution record. Based on the executed test load triggering command, the performance data of each communication protocol (such as throughput, transmission latency, bit error rate, etc.) are collected synchronously. The resource status data of the smart terminal motherboard (such as CPU utilization, memory usage, bus bandwidth utilization, and motherboard power consumption) are read at the same time interval. For each set of performance data and resource status data collected at the same time, the identifier of the corresponding test case and the name of the communication protocol that generated the performance data are attached, and these are compiled into a complete test case execution record.

[0048] The execution records of all test cases during the testing process are summarized to form a concurrent test run log. The concurrent test run log records all data throughout the entire concurrent testing process.

[0049] The specific process for creating a resource protocol conflict event log is as follows: Read the time series of protocol performance data and resource status data from the execution records of all test cases in the concurrent test run log; determine the standard range of protocol performance data and resource status data based on the technical specifications of the smart terminal motherboard; the standard range refers to the normal value range of protocol performance data and resource status data; read the performance index standards of each communication protocol in the technical specifications of the smart terminal motherboard (e.g., the standard transmission rate range of WiFi protocol is 2.0-3.0Gbps, and the standard latency range is 1-5ms), and the normal working range of hardware resources in the technical specifications of the smart terminal motherboard (e.g., the maximum allowable CPU utilization rate is 95%, and the maximum allowable memory utilization rate is 90%), and determine the standard range of protocol performance data and resource status data respectively.

[0050] The points in time when the time series of protocol performance data and the time series of resource status data deviate from their corresponding standard ranges are marked as the starting points of protocol performance degradation events and resource status anomaly events, respectively. The specific resource type corresponding to each resource status anomaly event is also recorded. Protocol performance degradation events refer to events that occur when the performance data of a certain communication protocol deviates from the standard range during concurrent testing. Resource status anomaly events refer to events that occur when the usage status of a certain resource deviates from the standard range during concurrent testing.

[0051] The values ​​at each time point in the protocol performance data time series and resource status data time series are checked one by one. If a value deviates from the corresponding standard range, this time point is marked as the starting point of the protocol performance degradation event or the resource status abnormal event.

[0052] For example, if the CPU utilization rate rises to 96% (above the 95% limit) in a certain second, mark that time point as the starting point and record the resource type as "CPU".

[0053] Merge the start points of consecutive test cases into a single protocol performance degradation event; merge the start points of consecutive timestamps (i.e., the time interval between two consecutive start points is less than or equal to a preset merging time window, such as 1 second) that belong to the same test case into a single protocol performance degradation event, with the first start point as the start time and the last start point as the end time.

[0054] Merge consecutive start points belonging to the same resource type into a single resource status exception event; merge consecutive start points belonging to the same specific resource type into a single resource status exception event, with the first start point as the start time and the last start point as the end time.

[0055] Causal relationships are determined between protocol performance degradation events and resource status anomaly events. Resource status anomaly events with a causal relationship are combined with protocol performance degradation events to form a resource protocol conflict event record. The resource protocol conflict event record includes the protocol performance degradation event, the resource status anomaly event, the causal relationship, the occurrence time, the duration, and the test case identifier.

[0056] The specific process for determining the causal relationship between protocol performance degradation events and abnormal resource status events is as follows: For each protocol performance degradation event, all resource status anomaly events with a start time earlier than or equal to the start time of the protocol performance degradation event are filtered out. The start time, performance index type, and test case identifier are extracted from the protocol performance degradation events. Using the start time of the currently processed protocol performance degradation event as the time filtering benchmark, all resource status anomaly events are traversed, and resource status anomaly events with a start time earlier than or equal to the start time of the target protocol performance degradation event are filtered out to form a candidate resource status anomaly event list.

[0057] Based on the correlation metrics established in benchmark tests for the test cases that generated the protocol performance degradation event, the correlation strength between the abnormal resource status event and the protocol performance degradation event is analyzed and determined. From the resource consumption profile of the smart terminal motherboard, the resource consumption feature vector corresponding to the test case is found, and the corresponding correlation metric is extracted from it. The absolute value of this correlation metric is used as the correlation strength between the abnormal resource status event and the protocol performance degradation event.

[0058] If the correlation strength reaches a preset strength threshold, then a causal relationship is determined between the two; otherwise, no causal relationship exists.

[0059] For example, if the correlation strength threshold is 0.7 and the extracted Pearson correlation coefficient is -0.85, with an absolute value of 0.85, then 0.85 > 0.7, indicating a causal relationship between the abnormal resource status event and the protocol performance degradation event; if the extracted Pearson correlation coefficient is 0.65, with an absolute value of 0.65, then 0.65 < 0.7, indicating no causal relationship.

[0060] It should be noted that this intensity threshold is set based on the statistical analysis results of the correlation metrics in the benchmark dataset.

[0061] The diagnosis and report generation module is used to analyze the diagnostic results of various resource protocol conflict events and further analyze and generate a comprehensive verification report.

[0062] The process of obtaining the diagnostic results of various resource protocol conflict events is as follows: For each resource protocol conflict event record, the nature of the conflict is determined based on the abnormal resource type corresponding to the abnormal resource status event. The specific resource type corresponding to the abnormal resource status event is directly defined as the conflict nature of that resource protocol conflict event record. For example, when the abnormal resource type is a CPU resource, the conflict nature is determined to be a CPU resource conflict; when the abnormal resource type is a memory resource, the conflict nature is determined to be a memory resource conflict; when the abnormal resource type is a bus resource, the conflict nature is determined to be a bus resource conflict; and when the abnormal resource type is a power resource, the conflict nature is determined to be a power resource conflict.

[0063] The impact intensity is determined by the magnitude of the deviation of protocol performance data from the standard range in the protocol performance degradation event. The impact intensity is used to represent the degree to which the protocol performance data deviates from the standard range. The abnormal performance index type and abnormal value in the protocol performance degradation event record are read, the absolute value of the difference between the abnormal value and the standard range boundary is calculated, the absolute value of the difference is divided by the standard range width for normalization, and the percentage of deviation is obtained as the impact intensity.

[0064] For example, if the abnormal throughput value is 2.0Gbps, the lower limit of the standard range is 2.1Gbps, the absolute value of the difference is 0.1Gbps, and the width of the standard range is 0.8Gbps (2.9-2.1), then the deviation of the protocol transmission rate is 12.5%, and the determination of the impact intensity is 12.5%.

[0065] The risk level of the resource protocol conflict event record is determined based on the impact intensity; two impact intensity thresholds are set to divide the impact intensity into three risk levels, and the two thresholds are defined as a high-risk threshold (representing severe performance degradation) and a medium-risk threshold (representing significant performance degradation). The impact intensity and impact intensity thresholds are judged using the following logic: If the impact intensity is greater than or equal to the high-risk threshold, the risk level of the resource protocol conflict event is determined to be high-risk; if the medium-risk threshold is less than or equal to the impact intensity but less than the high-risk threshold, the risk level of the resource protocol conflict event is determined to be medium-risk; if the impact intensity is less than the medium-risk threshold, the risk level of the resource protocol conflict event is determined to be low-risk.

[0066] The nature of the conflict, the intensity of its impact, and the risk level recorded in the resource agreement conflict event are integrated to form a diagnostic result.

[0067] The process of analyzing and generating a comprehensive verification report is as follows: The diagnostic results of all resource protocol conflict event records are summarized, and the diagnostic results are grouped and statistically analyzed according to the communication protocol type to obtain statistical results including the conflict frequency distribution, risk level distribution, and conflict nature distribution of each communication protocol. Each diagnostic result is grouped according to the communication protocol name corresponding to the protocol performance degradation event, and the number of resource protocol conflict event records corresponding to each communication protocol type is counted to form the conflict frequency distribution of each communication protocol.

[0068] For each type of communication protocol, the number and proportion of high-risk, medium-risk, and low-risk levels in the statistical diagnostic results are calculated to form the risk level distribution of each communication protocol; the number distribution of CPU resource conflicts, memory resource conflicts, bus resource conflicts, and power resource conflicts in the resource protocol conflict event records of each communication protocol are calculated; and the various distribution data are integrated to form a statistical result that includes the conflict frequency distribution, risk level distribution, and conflict nature distribution of each communication protocol.

[0069] A comprehensive verification report, including protocol compatibility assessment and improvement suggestions, is generated based on the statistical results. Protocol compatibility assessment refers to a comprehensive evaluation of the stability and coordination of various communication protocols running simultaneously on the smart terminal motherboard. The assessment logic is as follows: if any high-risk record exists in the communication protocol, it is assessed as "serious compatibility risk"; if no high-risk record exists but a medium-risk record exists, it is assessed as "moderate compatibility risk"; if all records are low-risk, it is assessed as "good compatibility".

[0070] Based on statistical results and protocol compatibility assessments, specific improvement suggestions are generated for each communication protocol. For example, when a communication protocol has a high proportion of CPU conflicts, it is recommended to optimize the CPU resource scheduling algorithm; when memory conflicts have a high proportion, it is recommended to increase the memory buffer capacity; when bus conflicts have a high proportion, it is recommended to optimize the bus arbitration mechanism; and when power consumption conflicts have a high proportion, it is recommended to improve the power management strategy.

[0071] In this embodiment, by constructing a benchmark dataset and generating a resource consumption profile, the resource consumption characteristics of each communication protocol under different loads and their correlation with performance are quantified. This provides a data-driven basis for the generation of concurrent test instruction sequences. Through a pre-built test sequence generation engine, based on resource consumption pattern recognition rules and resource conflict weight calculation rules, test case combinations with high resource conflict risk are intelligently selected from the resource consumption profile, and concurrent test instruction sequences are generated. This process shifts the testing focus from broad protocol function coverage to targeted stress scenarios that expose compatibility defects with a high probability, significantly improving testing efficiency and problem discovery capabilities. By executing a sequence of concurrent test instructions to acquire and generate concurrent test logs, the system can automatically identify protocol performance degradation events and resource status anomalies. Based on the correlation metrics established in benchmark testing, it can determine causal relationships and form resource protocol conflict event records. This mechanism automates and precisely locates the root causes of internal resource conflicts from observing concurrent fault phenomena. On this basis, by analyzing the impact intensity and nature of each conflict event, the risk level is determined, and statistics are grouped by communication protocol type. The final comprehensive verification report can quantitatively present the motherboard's protocol compatibility level and provide root cause improvement suggestions based on the distribution of conflict nature, providing a clear decision-making basis for hardware resource allocation and driver optimization.

[0072] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0073] In the several embodiments provided by this invention, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only one method, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0074] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention.

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

Claims

1. A multi-protocol compatible intelligent terminal motherboard function verification system, characterized in that, The multi-protocol compatible smart terminal motherboard function verification system includes: The data acquisition module is used to perform benchmark tests on each communication protocol supported by the smart terminal motherboard and obtain the benchmark dataset of the smart terminal motherboard. The analysis and sequence generation module is used to obtain a resource consumption profile of the smart terminal motherboard by analyzing the benchmark dataset; and to generate a concurrent test instruction sequence based on the analysis of the resource consumption profile using a pre-built test sequence generation engine. The concurrent testing and diagnostic module is used to obtain performance data of the communication protocol and resource status data of the smart terminal motherboard by executing a sequence of concurrent testing instructions to form a concurrent test run log; based on the concurrent test run log, it identifies the causal relationship between protocol performance degradation events and resource status abnormal events to form a resource protocol conflict event record; The diagnosis and report generation module is used to analyze the diagnostic results of various resource protocol conflict events and further analyze and generate a comprehensive verification report.

2. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 1, characterized in that, The process of obtaining the benchmark dataset of the smart terminal motherboard is as follows: Obtain all communication protocols supported by the smart terminal motherboard, as well as the corresponding technical specifications for each communication protocol; set up several test cases for each communication protocol, determine the test parameters and load levels for each test case based on the parameters in the technical specifications, and assign a unique identifier to each test case. Based on each communication protocol, the test cases are executed starting from the lowest load level, and the baseline performance data and baseline resource status data of the smart terminal motherboard corresponding to each test case are collected. The baseline performance data and baseline resource status data of each test case are associated and aligned according to the timestamp to form a baseline test record containing identifiers, timestamps, performance data and resource status data; The benchmark test records of all communication protocols are compiled to form a benchmark dataset.

3. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 2, characterized in that, The process of obtaining the resource consumption profile of the smart terminal motherboard is as follows: Extract all benchmark test records corresponding to each communication protocol from the benchmark dataset; calculate the mean and peak values ​​of the benchmark resource status data in each benchmark test record; integrate the mean and peak values ​​under the same load level according to the load level of the test case to form the resource indicator statistics of each test case; perform correlation analysis on the benchmark performance data and benchmark resource status data of each test case of the communication protocol to determine the correlation metric between the benchmark resource status data and the benchmark performance data. The resource consumption feature vector is formed by integrating the resource metric statistics and related metrics corresponding to each test case of the communication protocol; the resource consumption feature vectors of all communication protocols are then integrated to form a resource consumption profile of the smart terminal motherboard.

4. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 1, characterized in that, The specific process of the pre-built test sequence generation engine is as follows: A test sequence generation engine is constructed, comprising an analysis layer, a decision layer, and an output layer. The analysis layer is configured with resource consumption pattern recognition rules that classify test cases based on several resource-intensive pattern determination thresholds, and resource conflict weight calculation rules that calculate the difference between statistical indicators of the same type of resource based on two test cases. The decision layer is configured with a test sequence optimization algorithm. The output layer stores executable test command templates corresponding to various communication protocols and load levels.

5. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 3, characterized in that, The specific process for generating the concurrent test instruction sequence is as follows: The resource consumption profile of the smart terminal motherboard is input into the analysis layer of the test sequence generation engine. Based on the resource consumption pattern recognition rules, test cases whose resource consumption feature vectors exceed the corresponding resource-intensive pattern judgment threshold are classified into various resource-intensive test case sets. Based on the resource conflict weight calculation rules, test cases in different resource-intensive test case sets are combined in pairs to obtain the resource conflict weight of each test case combination. The decision layer sorts all test case combinations in descending order according to resource conflict weights based on the test sequence optimization algorithm, and selects several test cases with the highest ranking to form a concurrent test sequence; the output layer calls the corresponding executable test command template based on the concurrent test sequence to generate a concurrent test command sequence containing protocol initialization instructions and test load triggering instructions.

6. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 5, characterized in that, The specific process for generating concurrent test run logs is as follows: A concurrent test execution environment is built based on the concurrent test instruction sequence. The corresponding protocol initialization instructions and test load triggering instructions are executed sequentially according to the timestamp order of the concurrent test instruction sequence. The performance data of each communication protocol and the resource status data of the smart terminal motherboard collected synchronously are associated with the identifier and communication protocol name of the corresponding test case to form a test case execution record. The execution records of all test cases during the testing process are summarized to form a concurrent test run log.

7. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 6, characterized in that, The specific process for forming resource protocol conflict event records is as follows: Read the time series of protocol performance data and resource status data of all test case execution records in the concurrent test run log; determine the standard range of protocol performance data and resource status data based on the technical specifications of the smart terminal motherboard; The time points when the protocol performance data time series and resource status data time series deviate from their corresponding standard ranges are marked as the starting points of the protocol performance degradation event and the resource status abnormal event, respectively, and the specific resource type corresponding to each resource status abnormal event is recorded. Merge the starting points of consecutive test cases into a single protocol performance degradation event; Merge consecutive starting points belonging to the same resource type into a single resource status exception event; The causal relationship between protocol performance degradation events and resource status anomaly events is determined, and resource status anomaly events with causal relationship are combined with protocol performance degradation events to form a resource protocol conflict event record.

8. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 7, characterized in that, The specific process for determining the causal relationship between protocol performance degradation events and abnormal resource status events is as follows: For each protocol performance degradation event, filter out all resource status abnormal events whose starting point is earlier than or equal to the starting point of that protocol performance degradation event; Based on the correlation metrics established in benchmark tests for the test cases that generated the protocol performance degradation event, the correlation strength between the abnormal resource status event and the protocol performance degradation event is analyzed and determined. If the correlation strength reaches a preset strength threshold, then a causal relationship is determined between the two; otherwise, no causal relationship exists.

9. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 7, characterized in that, The process of obtaining the diagnostic results of each resource protocol conflict event is as follows: For each resource protocol conflict event record, the nature of the conflict is determined based on the abnormal resource type corresponding to the abnormal resource status event; The magnitude of the deviation of protocol performance data from the standard range in a protocol performance degradation event is used to determine the intensity of the impact. The risk level of the resource protocol conflict event record is determined based on the intensity of its impact. The nature of the conflict, the intensity of its impact, and the risk level recorded in the resource agreement conflict event are integrated to form a diagnostic result.

10. The intelligent terminal motherboard function verification system based on multi-protocol compatibility according to claim 9, characterized in that, The process of generating a comprehensive verification report through analysis is as follows: The diagnostic results of all resource protocol conflict events are summarized, and the diagnostic results are grouped and statistically analyzed according to the communication protocol type to obtain statistical results including the distribution of conflict frequency, risk level, and conflict nature of each communication protocol. Based on the statistical results, a comprehensive verification report including protocol compatibility assessment and improvement suggestions is generated.

Images