## 7 Experiment and Analysis
### Experimental Protocol and Analysis
\begin{table}
\begin{tabular}{c c c c c c} \hline \hline \multirow{3}{*}{**Time (Minutes)**} & **Original Alarm Quantity (Canceling the Multi-Source Alarm Screening Step)** & **Compressed Alarm Volume (Adding Multiple Source Source Alarm Screening Step Request)** & **Cancel the Multi-Source Alarm Screening Step (ms)** \\ \hline T-10 & 58 & 5 & 8.6\% & 2030 & 174 \\ T-9 & 88 & 7 & 7.9\% & 2992 & 238 \\ T-8 & 73 & 6 & 8.2\% & 2701 & 198 \\ T-7 & 25 & 4 & 16\% & 873 & 136 \\ T-6 & 4248 & 131 & 3.1\% & 152,928 & 4847 \\ T-5 & 2658 & 97 & 3.6\% & 98,124 & 3492 \\ T-4 & 1118 & 86 & 7.7\% & 42,484 & 3096 \\ T-3 & 869 & 71 & 8.2\% & 38,642 & 2698 \\ T-2 & 2094 & 52 & 2.5\% & 81,608 & 1820 \\ T-1 & 150 & 11 & 7.3 & 5551 & 374 \\ T & 11,381 & 470 & 4.1\% & 427,933 & 17,073 \\ \hline \hline \end{tabular}
\end{table} 
Table 5: Data set received a total of 11,381 alarms, taking a total of 428 s. If the multi-source alarm screening step was added, the localization program received a total of 470 alarms at time T, taking a total of 17 s. Through comparison and verification, the alarm screening achieved an alarm compression ratio of 3.99%, with the time consumption falling from 428 s to 17 s, a reduction of 96%. This greatly improved the program's performance. Scenario 2: Remove some topological relationship data from the dynamic operation and maintenance map and run the positioning program. This experiment analyzed a total of nine failure case data covering four categories: network, system, database, and storage. Among them, the relationship data of aggregation switches were removed from test case 4 to construct test case 4#, the relationship data of core switches were removed from test case 5 to construct test case 5#, and the relationship data of cache were removed from test case 7 to construct test case 7#. The location program was then run. In this scenario, nine fault case datasets were employed, among which the datasets of Fault Case 4, 5, and 7 required repeated recording and playback, twice each. During the second playback of these fault cases, the topological data related to the dynamic map was excluded. Therefore, a total of 12 rounds of experiments were conducted, each lasting 15 min, to facilitate the analysis and comparison of experimental data. The test results are shown in Table 6.  
Test conclusion: From the 12 test cases, it can be verified that whether the test results are successfully located depends directly on whether the dynamic map provides the configuration topology data corresponding to the fault type. The type of dynamic map topology data directly determines the fault types covered by the location. (3) Experimental analysis conclusion  
In summary, the two key modules of this model--alarm screening and dynamic map addressing are extremely critical. Alarm screening effectively improves the timeliness of hits, while the completeness of the topology data type of the dynamic map directly determines the fault coverage and hit rate. The experimental results demonstrate the effectiveness of this model method. \begin{table}
\begin{tabular}{c c c c c c c c c c c c} \hline \hline