A trusted sis trusted boot performance test method and system

Abstract

The present application relates to the technical field of safety instrument, particularly relates to a kind of trusted SIS trusted start performance test method and system;Method includes expression editing count file, specify the number of times value and current restart number value that need to restart;Restart trusted SIS equipment, test service is automatically started with machine, execute script file;Read the system time of current equipment and current restart number value, until current restart number value is equal to the number of times value that system specifies restart, then test ends;According to test result, obtain the time of restart system trusted quality;Script file, technical file and test service are input into trusted SIS equipment, obtain the average time of all equipment start;Compare the average time of all equipment start, analysis and generate test report.The present application can effectively solve the problem that trusted SIS equipment cannot automatically record system start time when restarting, reduce the test cost caused by repetitive work and human factors.

Description

Technical Field

[0001] This invention relates to the field of safety instrument technology, and in particular to a reliable startup performance testing method and system for a reliable SIS (Safety Instrumented System). Background Technology

[0002] The domestically developed Trusted SIS system integrates trusted boot functionality. During the system startup phase, it performs step-by-step verification of the system's BIOS firmware, hardware platform, boot code, boot configuration, master boot program, master boot record, master boot configuration, kernel files, and initial disk files. When the verification is deemed untrustworthy, it prevents system startup or issues alarm messages according to the user-configured trusted policy. Because trusted boot involves a series of trusted measurements and verifications during the system startup phase, and employs multiple policy control methods, it requires repeated manual device restarts and timed restarts. This testing method is prone to errors and requires significant manpower and resources.

[0003] Prior art 1, Chinese Patent Application No. 202511620681.6, discloses an Android SoftPOS trusted application method and system. This method includes: the application client initiating an authentication request to an application authentication server, obtaining verification data and multiple random numbers; subsequently, performing device and application integrity verification, generating an integrity certificate and a hardware authentication certificate, and submitting them to the server; after successful server verification, issuing a device-specific secure communication certificate to the application client; and the application client establishing a secure communication channel with the server using this certificate. While this multi-stage verification and random number mechanism ensures that only trusted devices and applications can complete authentication, combined with dynamically issued certificates, it achieves end-to-end secure communication, significantly improving the confidentiality and integrity of payment data and reducing security risks; however, some extremely rare but potentially startup-failure transient hardware malfunctions or software race conditions may never occur within a limited testing time.

[0004] Prior art two, Chinese patent application number 202510471943.0, relates to the field of Internet of Things (IoT) technology, specifically providing a security management method, system, device, and storage medium for IoT devices. The method includes receiving authentication information from the IoT device; confirming with an authentication platform whether the IoT device is a trusted device based on the authentication information; confirming the IoT device is a trusted device and granting it a time-sensitive permission identifier, which is used to confirm the trustworthiness of business data uploaded by the trusted device; obtaining the trusted device's operational data and confirming its operational status based on the operational data; if the operational status is abnormal, revoking the permission identifier; the authentication information includes authentication certificates issued by the authentication platform to the IoT device. While this achieves lightweight security management of IoT devices and dynamic isolation of abnormal devices, the startup process may require operator confirmation or intervention, and the time and behavior involved are highly variable, making standardized testing difficult.

[0005] Prior art three, Chinese patent application number 202510848927.9, discloses a direct memory access control method, a device driver initialization method, and related devices. The direct memory access control method includes, when a direct memory access request from a trusted device is received, obtaining the device identifier and target input / output virtual address information of the trusted device from the direct memory access request; obtaining a secure device table entry for the trusted device based on the device identifier; obtaining the page table identifier of the encrypted nested page table of the secure virtual machine and the root address of the highest-level nested page table based on the secure device's secure device table entry; and traversing the encrypted nested page table based on the page table identifier, the root address of the highest-level nested page table, and encryption flags to map the target input / output virtual address to the corresponding host physical address. While enabling trusted devices to share the encrypted nested table of the secure virtual machine is beneficial for improving the security of trusted device data, code coverage and branch coverage are not entirely applicable in timing performance testing, and there is a lack of universally accepted and effective coverage metrics.

[0006] Currently, existing technologies 1, 2, and 3 suffer from problems such as difficulty in triggering long-tail effect faults, challenges in human-computer interaction, and difficulties in measuring test coverage. To address these issues, this invention provides a trusted SIS trusted startup performance testing method and system. Summary of the Invention

[0007] The main objective of this invention is to provide a trusted SIS trusted startup performance testing method and system to solve the problems of long-tail effect faults being difficult to trigger, human-computer interaction, and test coverage measurement in the prior art.

[0008] To achieve the above objectives, the present invention provides the following technical solution: A trusted SIS trusted startup performance testing method includes the following steps: Edit the count file, specifying the number of restarts required and the current restart count; restart the trusted SIS device, the test service starts automatically upon boot, and the script file is executed; read the current system time and current restart count of the device; The current restart count is compared with the system-specified restart count. If they are not equal, the current restart count in the counter file is incremented by one, and the device restarts are continued until the current restart count equals the system-specified restart count, at which point the test ends.

[0009] As a further improvement of the present invention, the process of executing the script file includes the following steps: A complete external power supply interruption and recovery operation is applied to the trusted SIS device, which forces all dynamic processes inside the trusted SIS device to enter a state of quiescence. When the external power supply is restored, the quiescent system loads basic functions step by step according to its fixed initial sequence until all functions are ready and enters a stable waiting state that accepts instructions. The stable waiting state is the ready state after the trusted SIS device restarts. In the ready state, a set of preset boot instructions are automatically triggered to unpack a series of scattered functional module packages in sequence. Based on the association rules defined in the functional module packages, they are autonomously assembled, mutually verified, and logically linked in memory. When all the defined key functional modules are assembled and form a closed loop, a complete test service function body is instantly activated, and the functional modules enter the standby state. The functional module reads the specified script file, which is converted into a series of operation steps with dependencies. It locks and executes the first step in the operation step sequence, and uses the successful execution result as the only credential to unlock and execute the next step. When the last step in the operation step sequence is completed and confirmed, the entire script file execution process ends, reaching the preset termination state. The termination state will be used to obtain the current system time and restart count.

[0010] As a further improvement of the present invention, the process until the current restart count is equal to the system-specified restart count includes the following steps: The specified number of system restarts is subtracted from the current number of restarts to obtain an integer deviation value. If the integer deviation value is not equal to zero, it is determined that there is a target deviation, and an iterative instruction is generated. If the integer deviation value is equal to zero, it is determined that the target has been reached, and a termination instruction is generated. When an iteration instruction is received, an atomic update transaction for the counter file is initiated. First, the current restart count value stored in the file is read, the current restart count value is converted into a numerical format and then incremented by one to obtain the new restart count value. The new restart count value is converted back to the storage format and completely overwritten to the original file position. After the update is successful, an update completion event notification containing the new restart count value is output. Once the update completion event notification is captured, the device reset process is triggered, forcibly clearing all dynamic operating states, followed by a complete power supply interruption and recovery operation. After power recovery, the trusted SIS device reloads according to its fixed sequence until the test service is automatically activated and the script file is executed. The script file will then read the current restart count value from the counter file again. The process automatically connects and triggers the integer deviation value quantization and judgment again. When the termination command is output, the iteration stops and the test process ends.

[0011] As a further improvement of the present invention, the process of converting the new restart count value back to the storage format and completely overwriting it to the original file location includes the following steps: Read the character sequence of the current restart count value from the count file. Based on the predefined symbol semantic lookup table, uniquely map the visual symbol of each character in the character sequence to an abstract mathematical concept value. Combine the values ​​according to positional weights to form an abstract numerical value for mathematical operations. Apply a unit recursive procedure to the abstract value, jump from the value state represented by the current abstract value to the next value state arranged in natural number order; output the value of the successor state. Abstract mathematical values ​​are re-encoded into storable visual symbols. Based on a symbol semantic lookup table, subsequent state values ​​are decomposed into multiple components weighted by position. The value corresponding to each component is then inversely mapped back to a special character symbol. The character symbols are combined sequentially to generate a new character sequence with incremented counts. This character sequence is the new restart count value, used to overwrite the original file position, and included in the update completion event notification.

[0012] As a further improvement of the present invention, the process of outputting the subsequent state value includes the following steps: The abstract numerical value is input as a coordinate parameter into the reference coordinate system; each integer scale point in the reference coordinate system uniquely corresponds to an accepted quantity state; by matching across the entire scale, the abstract numerical value is locked onto a scale point in the coordinate system that completely coincides with it; the locked scale point is output. Using the locked tick mark as a trigger condition, a regular pointer with a fixed operating distance is activated. The tip of the regular pointer always points to the next adjacent tick mark along the positive direction of the coordinate axis, separated by a fixed unit length. After the regular pointer is activated, it automatically swings from the locked tick mark and stably points to its adjacent target tick mark. Once the rule pointer stably points to an adjacent target tick point, the reading operation is initiated to identify the unique coordinate value represented by the adjacent target tick point in the reference coordinate system, and extract the unique coordinate value as a new mathematical quantity. The extracted quantity is the final output successor state quantity, marking the complete transition from the original state to the next state.

[0013] As a further improvement of the present invention, the process of locking an abstract numerical value onto a scale point in the coordinate system that completely coincides with it includes the following steps: The input abstract value is converted into a frequency signal according to scalar parameters, which is then transformed into an oscillating waveform with a frequency. The oscillating waveform carries all the information of the abstract value and serves as the excitation signal, outputting as the input waveform. The input waveform is applied to a wideband resonant cavity representing the full scale range, covering the resonant frequencies corresponding to all integer scale points from zero to positive infinity; when the frequency of the input waveform coincides with a certain frequency in the wideband resonant cavity, resonance is triggered at that frequency point; the output is the resonant frequency point that is uniquely and significantly excited in the resonant cavity. The obtained resonant frequency points are mapped one-to-one back to a spatial scale point with integer coordinates in the reference coordinate system through a frequency-space mapper. Through frequency-space mapping, the resonant frequency points are converted into a specific spatial location, which is the target scale point. The target scale point is a locked position that completely coincides with the initial abstract value.

[0014] As a further improvement of the present invention, the process of converting scalar parameters into frequency signals and then into an oscillating waveform with frequency includes the following steps: The abstract numerical value input is treated as an isolated element and embedded into an algebraic structure with total order relation through an injective mapping rule; the pivot element has a definite order position in the algebraic structure. Using the step size determined by the position of the reference element, starting from the zero element of the structure, continuous and equally spaced element-taking operations are performed to generate a periodic element sequence. Based on the fixed period of occurrence of elements in the element sequence, the length of its periodic interval is measured and quantified into a frequency value. Simultaneously, according to the inherent rules of the generating function, an amplitude variation pattern is assigned to the element distribution within each period. The frequency value and amplitude pattern together define an ideal periodic waveform, which is the output oscillation waveform.

[0015] As a further improvement of the present invention, the process of embedding into an algebraic structure having a total order relation includes the following steps: A base set containing infinitely ordered elements is set up by default, and there is a clear order relationship between any two elements, which constitutes a total order structure reference system; The input abstract numerical value is used as a filtering condition and applied to the total order structure reference system. An equivalence relation is defined on the total order structure reference system: if the order of an element in the total order structure reference system is equal to the abstract numerical value, it belongs to the target equivalence class. According to the definition of the equivalence relation, all elements in the reference system that satisfy the equation are assigned to the same target equivalence class, thus completing the filtering. The target equivalence class contains only one unique element. This unique element is extracted and defined as the representative element of the target equivalence class. The representative element is the embedding result of the abstract numerical value in the total order structure.

[0016] As a further improvement of the present invention, the time for restarting the trusted quality of the system is obtained based on the test results; a trusted SIS device environment is deployed; script files, technical documents and test services are input into the trusted SIS device to obtain the average startup time of all devices; the average startup time of all devices is compared, analyzed and a test report is generated.

[0017] To achieve the above objectives, the present invention also provides the following technical solution: A trusted SIS trusted startup performance testing system, used to implement the aforementioned trusted SIS trusted startup performance testing method, includes: The device information reading module is used to edit the count file, specify the number of restarts required and the current number of restarts; restart the trusted SIS device, the test service starts automatically upon power-on, and executes the script file; read the current system time and current number of restarts of the device; The test device information module is used to compare the current restart count with the system-specified restart count. When the two are not equal, the current restart count in the counter file is incremented by one, and the device restarts are continued until the current restart count is equal to the system-specified restart count, at which point the test ends. The test report generation module is used to determine the system's trusted quality time based on test results; deploy a trusted SIS device environment; input script files, technical documents, and test services into the trusted SIS device to obtain the average startup time of all devices; compare the average startup time of all devices, perform analysis, and generate a test report.

[0018] This invention achieves the following technical effects by integrating count file editing, restart loop control, and time-consuming data collection and comparative analysis: Automated verification of restart stability: By comparing preset restart counts with real-time counts, a closed-loop testing process is formed, ensuring the self-starting reliability of trusted SIS devices in continuous restart scenarios and eliminating human intervention errors; Precise quantification of system time consumption: Based on a unified environment deployment and scripted testing across multiple devices, the entire restart process time data is collected, and the average value is used to eliminate random fluctuations in single restarts, objectively reflecting the system startup performance baseline; Dynamic assessment of trustworthy quality: Relationship between restart time and system trustworthiness status is established. By comparing data from multiple devices horizontally, abnormal startup time nodes are identified, providing a quantitative assessment basis for the integrity and consistency of the system's trust chain; Reproducible and traceable testing process: The standardized script, count file, and service configuration test file embedding mechanism ensures the consistency of test conditions; Automatic test report generation function supports source analysis of performance degradation or abnormal scenarios; Resource and efficiency optimization: The loop testing mechanism automatically terminates after reaching the preset restart count, avoiding unnecessary test resource consumption; Centralized data analysis logic improves the scenario coverage efficiency of multi-device batch testing. Attached Figure Description

[0019] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used together with the embodiments of the invention to explain the invention and do not constitute a limitation thereof. The drawings show... Figure 1 This is a flowchart of an embodiment of the trusted SIS trusted startup performance testing method of the present invention; Figure 2 This is a schematic diagram of an embodiment of the trusted SIS trusted startup performance testing method of the present invention; Figure 3 A flowchart of the execution script file for an embodiment of the trusted SIS trusted startup performance testing method of the present invention; Figure 4 This is a flowchart illustrating how the current number of reboots equals the number of reboots specified by the system, according to one embodiment of the trusted SIS trusted boot performance testing method of the present invention. Figure 5 This is a flowchart illustrating the time required to determine the trusted quality of the restarting system based on test results, as an embodiment of the trusted SIS trusted boot performance testing method of the present invention. Figure 6 This is a functional module diagram of an embodiment of the Trusted SIS Trusted Startup Performance Testing System of the present invention; Figure 7 This is a schematic diagram of the structure of an embodiment of the electronic device of the present invention; Figure 8 This is a schematic diagram of the structure of one embodiment of the storage medium of the present invention. Detailed Implementation

[0020] The technical solutions of the present invention will now be described with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.

[0021] Hereinafter, the terms "first," "second," etc., are used for descriptive convenience only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0022] In this invention, unless otherwise explicitly specified and limited, the term "connection" should be interpreted broadly. For example, "connection" can be a fixed mechanical connection, a detachable mechanical connection, or an integral part; or, "connection" can be a direct connection or an indirect connection through an intermediate medium. Furthermore, unless otherwise explicitly specified and limited, the term "coupling" should be interpreted broadly. For example, "coupling" can be a direct electrical connection, such as physical contact and electrical conduction between two components; it can also be understood as an electrical connection between different components in a circuit structure through physical lines capable of transmitting electrical signals, such as copper foil or wires on a printed circuit board (PCB), to transmit electrical signals; or, "coupling" can be an indirect electrical connection between two components through an intermediate medium; or, "coupling" can be an electrical connection between two components in a non-contact manner, such as an electrical connection between two components using capacitive coupling to transmit electrical signals.

[0023] In this embodiment of the invention, directional terms such as "up," "down," "left," and "right" may be defined relative to the orientation of the components shown in the accompanying drawings. It should be understood that these directional terms can be relative concepts, used for relative description and clarification, and can change accordingly depending on the orientation of the components in the accompanying drawings.

[0024] Example 1 shows as follows Figure 1 As shown, this embodiment provides an example of a trusted SIS trusted startup performance testing method. In this embodiment, the trusted SIS trusted startup performance testing method specifically includes the following steps: Step S1 involves editing the count file, specifying the number of restarts required and the current number of restarts; restarting the trusted SIS device, with the test service automatically starting upon power-on and executing the script file; and reading the current system time and current number of restarts of the device. Step S2 means comparing the current restart count with the system-specified restart count. If they are not equal, the current restart count in the counter file is incremented by one, and the device restarts are continued until the current restart count is equal to the system-specified restart count, at which point the test ends. Step S3 indicates the time required to restart the system based on the test results; deploying the trusted SIS device environment; inputting script files, technical documents, and test services into the trusted SIS device to obtain the average startup time of all devices; comparing the average startup time of all devices, performing analysis, and generating a test report.

[0025] Preferably, the testing method in this embodiment integrates count file editing, restart loop control, and time-consuming data collection and comparative analysis to achieve the following technical effects: Automated verification of restart stability; by comparing the preset number of restarts with real-time counts, a closed-loop testing process is formed, ensuring the self-starting reliability of trusted SIS devices in continuous restart scenarios and eliminating human intervention errors; Precise quantification of system time consumption; Based on multi-device unified environment deployment and scripted testing, the time consumption data of each restart process is collected, and the average value is used to eliminate random fluctuations in single startups, objectively reflecting the baseline of system startup performance; Dynamic evaluation of trustworthy quality; Correlation of restart time with system trustworthiness status; By comparing data from multiple devices horizontally, abnormal startup time nodes are identified, providing a quantitative evaluation basis for the integrity and consistency of the system's trust chain; Reproducible and traceable testing process; Standardized script, count file, and service configuration test file implantation mechanism ensures the consistency of test conditions; Automatic test report generation function supports source analysis of performance degradation or abnormal scenarios; Resource and efficiency optimization; The loop testing mechanism automatically terminates after reaching the preset number of restarts, avoiding ineffective test resource consumption; Centralized data analysis logic improves the scenario coverage efficiency of multi-device batch testing.

[0026] Combined with appendix Figure 2This embodiment specifically includes a test service representing the startup time of the test device, a shell script, and a counter file; editing the counter file to specify the number of system restarts required and the current restart count (0); restarting the trusted SIS device; after the device starts, the test service will automatically start upon boot, execute the script file, and read the current system time and current restart count of the device; comparing the current restart count with the system-specified restart count; if they are not equal, incrementing the current restart count in the counter file and continuing to restart the device until the current restart count equals the system-specified restart count, at which point the test ends; calculating the average startup time of the device based on the system time; and preparing the trusted SIS device environment, which includes information indicating that the trusted SIS device has been deployed. Trusted Startup functionality is implemented in several ways: the Trusted Startup module is enabled, and all Trusted Startup measurement objects are in a trusted state; the Trusted SIS device has Trusted Startup functionality deployed, the Trusted Startup module is in monitoring mode, and all Trusted Startup measurement objects are in a trusted state; the Trusted SIS device has Trusted Startup functionality deployed, the Trusted Startup module is in monitoring mode, and some Trusted Startup measurement objects are in an untrusted state; the Trusted SIS device has Trusted Startup functionality deployed, the Trusted Startup module is disabled (i.e., no Trusted Startup measurement objects); and the Trusted SIS device has not deployed Trusted Startup functionality. Test services, shell scripts, and counting files are uploaded to the Trusted SIS device to obtain the average startup time for all devices. The average startup time of all devices is compared, analyzed, and a test report is generated (see appendix for details). Figure 2 ).

[0027] In summary, this embodiment effectively solves the problem that trusted SIS devices cannot automatically record system startup time when restarting, and require manual device restart, thereby improving testing efficiency and accuracy and reducing testing costs caused by repetitive work and human factors.

[0028] Example 2 shows as follows Figure 3 As shown, the process of executing the script file in step S1 specifically includes the following steps: Step S11 indicates that a complete external power supply interruption and recovery operation is applied to the trusted SIS device. The interruption and recovery operation forces all dynamic processes inside the trusted SIS device to enter a state of quiescence. When the external power supply is restored, the quiescent system loads basic functions step by step according to its fixed initial sequence until all functions are ready and enters a stable waiting state that accepts instructions. The stable waiting state is the ready state after the trusted SIS device restarts. Step S12 indicates that the ready state automatically triggers a set of preset boot instructions, sequentially unpacks a series of scattered functional module packages, and performs autonomous splicing, mutual verification and logical linking in memory according to the association rules defined in the functional module packages; when all the defined key functional modules are spliced ​​together and form a closed loop, a complete test service function body is instantly activated and the functional modules enter the standby state. Step S13 indicates that the functional module reads the specified script file, converts the script file into a series of operation steps with sequential dependencies, locks and executes the first step in the operation step sequence, and uses the successful execution result as the only credential to unlock and execute the next step; when the last step in the operation step sequence is executed and confirmed, the entire script file execution process ends, reaching the preset termination state; the termination state will be used to obtain the current system time and restart count.

[0029] Preferably, this embodiment forms a complete, closed-loop, automated execution process with strong timing and state dependencies. Deterministic reset of the system state is achieved through external energy interruption and recovery operations (e.g., forcibly cutting off and restoring power to the device), eliminating the dynamic residual effects of historical operation processes and bringing the system into an initial ready state. Based on this, a fully functional and internally verified test service body is dynamically constructed through pre-set boot instructions and a modular loading mechanism, ensuring the reliability and integrity of function loading. Finally, by parsing the script into a sequence of operation steps with strict dependencies and using a serial execution mechanism where the successful result is the sole credential for unlocking the next step, the script execution process is non-jumpable, state traceable, and tamper-proof. The final state of the entire process is clear and determinable, providing a stable and reproducible benchmark environment for accurately obtaining the timestamps and restart counts after the system completes a specific operation sequence, thereby supporting reliable verification and analysis of system behavior and state.

[0030] Example 3, the process of converting the script file into a sequence of operation steps with dependencies in step S13 specifically includes the following steps: Step S131 means that the script file stored in the non-volatile medium is mapped and restored into a set of discrete basic instruction units with basic meanings one by one according to the predefined symbol correspondence rules, and the discrete instruction basic unit set is output. Step S132 indicates the activation of the relation resolution mechanism, which traverses each instruction basic unit in the discrete instruction basic unit set, identifies the reference identifiers or condition declarations of other instruction basic units contained in the discrete instruction basic unit, and establishes directional connection relationships between all discrete instruction basic units based on the identifiers or declarations; the discrete instruction basic units and the connection relationships together constitute a logical relationship map describing the constraints and flow between all external energy supply interruption and recovery operations.

[0031] Step S133 indicates that all instruction basics that do not depend on other instruction basic units are identified from the logical relationship graph as the entry point of the starting unit. The instruction basic units are sorted according to the direction specified by the connection relationship in the logical relationship graph. During the sorting process, if two or more instruction basic units can be selected, they are selected uniquely according to the priority rule. The two-dimensional logical relationship graph structure is flattened into a linear step sequence list. Finally, the linear step sequence list is output.

[0032] Preferably, this embodiment achieves a deterministic and structured transformation from static script files to dynamic executable operation sequences, constructing an instruction flow with strict logical dependencies and a clear execution path. First, by using symbol mapping rules, continuous symbol sequences are mapped to a set of discrete instruction basic units, completing the transformation of script content from storage format to parsable semantic units, providing structured input for logical analysis. Second, by using a relation resolution mechanism to identify references and condition declarations between instruction units and establish directional connections, a logical relation graph is formed, depicting the pre- and post-constraints and flow dependencies between all operations. This transforms implicit script logic into a traversable and verifiable graph structure, ensuring the logical completeness and consistency of the execution flow. Finally, by identifying entry points from the logical relation graph and generating a linear step sequence list based on connection relationships and priority rules, the two-dimensional dependency graph is transformed into a one-dimensional, deterministic execution sequence, eliminating ambiguity and uncertainty in parallel selection during execution, ensuring that the order of operation steps is unique and predictable in any execution instance.

[0033] In summary, this embodiment converts unstructured script files into a linear operation sequence with strict sequential dependencies, unambiguity, and static analysis capability, providing a precise input basis for the lock-execute-credential transfer serial control mechanism, thereby ensuring the predictability, repeatability, and state traceability of the entire script execution process.

[0034] Example 4, as Figure 4 As shown, step S2, the process until the current restart count equals the system-specified restart count, specifically includes the following steps: Step S21 means performing arithmetic subtraction between the system-specified number of restarts and the current number of restarts to obtain an integer deviation value; if the integer deviation value is not equal to zero, it is determined that there is a target deviation and an iterative instruction is generated; if the integer deviation value is equal to zero, it is determined that the target has been reached and a termination instruction is generated. Step S22 indicates that when the iterative instruction is received, an atomic update transaction for the counter file is started. First, the current restart count value stored in the file is read, the current restart count value is converted into a numerical format and then incremented by one to obtain the new restart count value after incrementing. The new restart count value is converted back to the storage format and completely overwritten to the original file position. After the update is successful, an update completion event notification containing the new restart count value is output. Step S23 indicates that the update completion event notification has been captured, triggering the device reset process, forcibly clearing all dynamic operating states, and then performing a complete energy supply interruption and recovery operation; after energy recovery, the trusted SIS device reloads according to its fixed sequence until the test service is automatically activated and the script file is executed, and the script file will read the current restart count value from the counter file again; automatically connect and trigger the integer deviation value quantization and judgment again; when the termination command is output, the iteration stops and the test process ends.

[0035] Preferably, in the system restart test scenario of this embodiment, the above steps combine to construct an automated, highly reliable, and atomically guaranteed cyclic test framework; realizing a closed-loop automated test process, dynamic deviation detection and iterative control. Through integer deviation value calculation and judgment, the system can automatically identify the difference between the current state and the target number of restarts, forming a closed loop of detection-judgment-iteration-reset; the test process can be continuously driven without manual intervention until the preset number of restarts is reached, significantly improving test efficiency and consistency. The event-driven state synchronization mechanism, combining atomic update transactions with update completion event notifications, ensures that each restart action is triggered based on the latest count state; the event-driven design avoids state synchronization lag or loss, enabling the test process to have self-coordination capabilities. Ensuring data consistency and operational atomicity, the atomic update transactions of the count file can resist data half-write problems caused by process anomalies or power outages, ensuring that the count value remains complete and valid even in extreme cases. The bidirectional conversion mechanism between file storage format and memory numerical format adapts to both persistent storage requirements and memory operation efficiency, improving the system's compatibility with different storage media. Forced clearing of dynamic operating status and energy supply interruption and recovery operations realistically simulates the complete physical process of equipment restarting after an unexpected power outage in an industrial environment, covering key aspects such as hardware initialization, firmware loading, and service recovery. Relying on the reloaded firmware sequence of trusted SIS devices and automatic activation of test services verifies that the system can still restore business functions according to preset logic after repeated resets, making it particularly suitable for safety instrumented systems with extremely high reliability requirements. The update completion event notification output after each update includes the new restart count, providing a clear status node for external monitoring systems, facilitating log recording, anomaly alarms, or real-time dashboard display. The termination command generated when the integer deviation value is zero provides a clear and unambiguous test completion signal, avoiding over-testing or premature termination due to misjudgment of conditions.

[0036] In summary, this embodiment ensures accurate starting points for each iteration, avoiding count jumps or repeated executions; it establishes loosely coupled process connections, reduces inter-module dependencies, and facilitates the expansion or replacement of reset logic; it enables unattended long-term stability testing, and is particularly suitable for verifying the cumulative performance degradation of equipment after thousands of restarts. It is especially applicable to life testing, reset reliability verification, and fault recovery capability assessment of industrial control equipment, embedded systems, and safety-critical systems (such as SIS), providing a standardized testing methodology for mass production quality inspection or long-term operation and maintenance of high-reliability equipment.

[0037] Example 5, step S22, which involves converting the new restart count value back to the storage format and completely overwriting it in the original file location, specifically includes the following steps: Step S221 means reading the character sequence representing the current number of restarts from the count file, and according to the predefined symbol semantic lookup table, uniquely mapping the visual symbol of each character in the character sequence to an abstract mathematical concept value; combining the values ​​according to position weights to form an abstract numerical value for mathematical operations. Step S222 indicates that a unit recursive procedure is applied to the abstract value to jump from the value state represented by the current abstract value to the next value state arranged in natural number order; the subsequent value state is output. Step S223 means re-encoding the abstract mathematical value into a storable visual symbol. Based on the symbol semantic lookup table, the subsequent state value is decomposed into multiple components that are weighted according to their positions. The value corresponding to each component is inversely mapped back to a specific character symbol. The character symbols are combined in sequence to finally generate a new character sequence representing the incremented number of times. The character sequence is the new restart count value, which is used to overwrite the original file position and is included in the update completion event notification.

[0038] Preferably, in this embodiment, the character sequence is converted into an abstract numerical value based on a symbol semantic lookup table, achieving precise parsing of the stored data. Incremental calculations are performed on the abstract numerical value using a unit recursive procedure to ensure the continuity and order of numerical updates. The updated abstract numerical value is then re-encoded into a character sequence, completing the reverse conversion of the data format. Finally, the newly generated character sequence is overwritten into the original file, achieving persistent data updates. This embodiment ensures accurate connection between data reading, calculation, encoding, and writing, forming a closed-loop operation and ensuring reliable incrementing of the restart count record and storage consistency.

[0039] Example 6, the process of outputting the successor state value in step S222 specifically includes the following steps: Step S2221 means inputting the abstract numerical value as a coordinate parameter into the reference coordinate system; each integer scale point in the reference coordinate system uniquely corresponds to an accepted quantity state; by matching across the entire scale range, the abstract numerical value is locked onto a scale point in the reference coordinate system that completely coincides with it; the locked scale point is output. Step S2222 indicates that the obtained locked tick point is used as the trigger condition to activate a regular pointer with a fixed action distance. The tip of the regular pointer always points to the next adjacent tick point along the positive direction of the coordinate axis, with a fixed unit length interval. After the regular pointer is activated, it automatically swings from the locked tick point and stably points to its adjacent target tick point. Step S2223 indicates that after the rule pointer stably points to the adjacent target tick point, the reading operation is started to identify the unique coordinate value represented by the adjacent target tick point in the reference coordinate system, and the unique coordinate value is extracted as a new mathematical value; the extracted value is the successor state value of the final output, marking the complete transition from the original state to the next state.

[0040] Preferably, this embodiment maps abstract numerical values ​​to a reference coordinate system, achieving precise numerical positioning through full-scale matching; based on locking the tick point activation rule pointer, a fixed action distance and pointing mechanism are used to ensure the determinism and uniqueness of adjacent tick points; by identifying the coordinate value of the target tick point, new mathematical values ​​are extracted, completing the strict transition of the numerical state. This embodiment achieves precise control of numerical increment, ensuring the reliability and order of state transitions, and providing an accurate incremental data foundation for encoding and storage operations.

[0041] Example 7, the process of locking the abstract numerical value to a tick mark that completely coincides with it in step S2221 specifically includes the following steps: Step S22211 means converting the input abstract value into a frequency signal according to the scalar parameters, and then into an oscillating waveform with a specific frequency; the oscillating waveform carries all the information of the abstract value and serves as the excitation signal, outputting as the input waveform; Step S22212 means applying the input waveform to a broadband resonant cavity representing the full scale range, covering the resonant frequencies corresponding to all integer scale points from zero to positive infinity; when the frequency of the input waveform matches a certain frequency in the broadband resonant cavity, resonance at that frequency point is triggered; the output resonant frequency point that is the only one that is significantly excited in the resonant cavity. Step S22213 means that the obtained resonant frequency point is mapped one-to-one back to a spatial scale point with integer coordinates in the reference coordinate system through a frequency-space mapper; through frequency-space mapping, the resonant frequency point is converted into a specific spatial location, namely the target scale point; the target scale point is a locked position that completely coincides with the initial abstract value.

[0042] Preferably, in this embodiment, the process of locking abstract numerical values ​​to integer scale points in a reference coordinate system involves converting the abstract numerical values ​​into oscillating waveforms of a specific frequency, using a wideband resonant cavity for frequency matching, and employing frequency-space mapping to achieve positional localization. This ultimately achieves the technical effect of precisely mapping abstract information to specific spatial coordinates. This embodiment realizes a stable transformation of numerical information from the abstract domain to the spatial domain, ensuring the accuracy and uniqueness of the mapping. Simultaneously, the resonant response mechanism avoids ambiguity or deviation, thereby reliably locking the target scale point in the reference coordinate system.

[0043] Example 8, step S22211, the process of converting scalar parameters into a frequency signal and then into an oscillating waveform with a specific frequency, specifically includes the following steps: Step S222111 means that the input abstract value is treated as an isolated element and embedded into an algebraic structure with total order relation through an injective mapping rule; the pivot element has a definite order position in the algebraic structure. Step S222112 indicates that, with the step size determined by the position of the reference element, continuous and equally spaced element-taking operations are performed starting from the zero element of the structure to generate a periodic element sequence. Step S222113 involves measuring the length of the periodic intervals of elements in the element sequence based on the fixed period of their occurrence, and quantifying the length into a frequency value. Simultaneously, according to the inherent rules of the generating function, an amplitude variation pattern is assigned to the element distribution within each period. The frequency value and the amplitude pattern together define an ideal periodic waveform, which is the output oscillation waveform.

[0044] Preferably, in this embodiment, abstract numerical values ​​are embedded into a total-order algebra structure through injective mapping to establish the ordinal position of the reference element; elements are continuously and equally spaced starting from zero element with a step size determined by the ordinal position to generate a periodic element sequence; the period length is measured and quantized as a frequency value based on the fixed period of the elements in the sequence, and an amplitude variation pattern is assigned to the element distribution within the period according to the generating function rules. The frequency value and amplitude pattern together define the ideal periodic waveform, realizing the conversion of scalar parameters into an oscillating waveform with specific frequency and amplitude characteristics.

[0045] Example 9 illustrates the process of embedding the algorithm in step S222111 into an algebraic structure with a total order relation, specifically including the following steps: Step S2221111 indicates that a basic set containing infinitely ordered elements is preset, and there is a clear size order relationship between any two elements, forming a total order structure reference system; Step S2221112 means applying the input abstract value as a filtering condition to the total order structure reference system; defining an equivalence relation on the total order structure reference system, indicating that if the order of an element in the total order structure reference system is equal to the abstract value, it belongs to the target equivalence class; according to the definition of the equivalence relation, all elements in the reference system that satisfy the equation are grouped into the same target equivalence class, thus completing the filtering. Step S2221113 indicates that the target equivalence class contains only one unique element. This unique element is extracted and defined as the representative element of the target equivalence class. The representative element is the embedding result of the abstract numerical value in the total order structure.

[0046] Preferably, this embodiment constructs a total order structure reference system by pre-setting a basic set containing infinitely ordered elements, where any two elements have a clear order relationship. The input abstract numerical value is applied to this reference system as a filtering condition, defining an equivalence relation as the element's ordinal position being equal to the abstract numerical value. All elements satisfying this condition are grouped into the same target equivalence class. This target equivalence class contains only a unique element, which is extracted as a representative element. This embodiment uniquely and definitively maps any abstract numerical value to a specific ordinal position in the total order algebra structure, providing a precise reference point for ordinal-based step operations.

[0047] Furthermore, such as Figure 5 As shown, step S3, which involves determining the time required to restart the system based on the test results, specifically includes the following steps: Step S31 means that based on the completed multiple restart processes, the time interval experienced by each trusted SIS device from the start of external power supply recovery to the end of the script file execution reaching the final state is extracted; all successfully recorded time interval values ​​are collected to form a discrete time consumption observation point set containing multiple elements. Step S32 means inputting a quadratic cost calculation function, calculating a scalar cost based on the square of the difference between each discrete time-consuming observation point and an unknown, undetermined representative value; traversing all elements in the set of discrete time-consuming observation points, summing the independent cost scalars, and outputting an aggregate cost scalar; Step S33 means taking the aggregation cost scalar as the optimization objective and taking its first derivative with respect to the representative value to be determined. According to the necessary condition that the derivative of a function is zero at the extreme point in convex optimization, the expression of the first derivative is set to zero, resulting in a linear equation with respect to the representative value to be determined. The equation is solved directly to obtain a numerical solution. The solution is the unique value that minimizes the aggregation cost and is defined as the steady-state start-up time characterization value of the system, which is also the time to finally obtain the reliable quality of restarting the system.

[0048] In this embodiment, step S31 represents the extraction and aggregation of discrete time-consuming observation point sets:

[0049] In the formula, This represents a discrete time-consuming observation set, which is a collection of... A collection of elements; middle , indicating that it represents the first The time interval recorded during each restart is the duration from the restoration of external energy supply to the script reaching its final state. This represents the total number of successfully completed and recorded restart processes; it also represents the continuous time interval of multiple independently observed events. Collected into a finite set of data This set is the basic input for all subsequent statistical analyses. Its core principle comes from sample collection in mathematical statistics, that is, inferring the characteristics of the population through a finite number of independent observations (samples). This is the complete sample set for this test.

[0050] Step S32 represents the calculation of the aggregation cost scalar mathematical expression:

[0051] In the formula, This represents the aggregation cost scalar, which is a variable... The function; This represents the steady-state start-up time characteristic of the system to be determined, i.e., the value that best represents all observations. A single numerical value; This indicates that the content within the parentheses is from... arrive Perform a summation operation; Indicates the first Individual observations and representative values ​​to be determined The square of the difference between them; this formula is the mathematical embodiment of the core idea of ​​the least squares method. Its function is to evaluate any candidate value. The "good" or "bad" of a variable provides a quantitative benchmark; the squared term serves two purposes: 1) it eliminates the effect of positive and negative deviations canceling each other out, ensuring that all deviations are factored into the cost; 2) it imposes a greater penalty on large deviations (because the squaring operation amplifies them), making the final calculated value... For outliers (maximum or minimum) Less sensitive, thus more robust; the summation term accumulates the individual costs (squared deviations) of all observation points to form a total cost. ;therefore, The smaller the value, the more likely it is to be a candidate value. With all actual observations The smaller the overall deviation, the better. The better it represents this set of data; the goal is to find... The smallest one .

[0052] Step S33 represents the mathematical expression for solving the steady-state start-up time characterization value of the system: First derivative representation:

[0053] The optimization condition equation is expressed as follows:

[0054] The solution results are as follows:

[0055] In the formula, This represents the aggregation cost function. Regarding variables The first derivative describes Follow The instantaneous rate of change; This indicates that the aggregation cost is represented. The goal is to achieve the minimum, ultimately solved, optimal system steady-state startup time representation; to solve the minimum problem based on convex optimization theory; and to express the cost function using differentiation. Differentiation is the standard method for finding the extreme points (in this case, the minimum points) of a function using calculus. The result of differentiation. It is a linear expression; setting the derivative to zero indicates that due to the function It is about The quadratic function (an upward-opening parabola) is a convex function, and its global minimum point must occur where the first derivative is zero. This is an application of the necessary and sufficient condition in convex optimization where finding a local extremum is equivalent to finding the global extremum. Solving the equation by setting the derivative expression to zero and solving for:

[0056] (Expand the summation symbol)

[0057] Final solution The expression is mathematically equivalent to the formula for calculating the sample arithmetic mean; ultimately, the time to restart the system with reliable quality is defined as the sample arithmetic mean of the restart times of multiple observations. The principle behind this is that the least squares method is mathematically equivalent to finding the single estimate that best fits the observed data, and this value possesses good statistical properties such as unbiasedness and minimum variance, thus providing a stable and reliable quantitative indicator for performance evaluation.

[0058] Preferably, this embodiment forms a discrete time-consuming observation set by aggregating the time intervals from the restoration of external energy supply to the script reaching its final state during multiple successful restarts. Using a quadratic cost calculation function, the squares of the differences between each observation point and the representative value to be determined are calculated and summed to obtain an aggregate cost scalar. The first derivative of this aggregate cost with respect to the representative value to be determined is calculated, and a linear equation is established and solved based on the condition that the derivative at the extreme point of convex optimization is zero, obtaining a unique numerical solution that minimizes the aggregate cost. This process, based on the least squares principle, estimates the statistically optimal characterization value of the system's steady-state startup time from actual observation data, thereby objectively quantifying the reliable quality time index of the restart system.

[0059] like Figure 6 As shown, this embodiment also provides an embodiment of a trusted SIS trusted startup performance testing system. In this embodiment, the trusted SIS trusted startup performance testing system is applied to a trusted SIS trusted startup performance testing method. The trusted SIS trusted startup performance testing system includes a representation of... The device information reading module 1 is used to edit the count file, specify the number of restarts required and the current number of restarts; restart the trusted SIS device, the test service starts automatically upon power-on, and executes the script file; read the current system time and the current number of restarts of the device; The test device information module 2 is used to compare the current restart count with the system-specified restart count. When the two are not equal, the current restart count in the counter file is incremented by one, and the device restarts are continued until the current restart count is equal to the system-specified restart count, at which point the test ends. The test report generation module 3 is used to determine the system's trusted quality time based on the test results; deploy the trusted SIS device environment; input script files, technical documents, and test services into the trusted SIS device to obtain the average startup time of all devices; compare the average startup time of all devices, perform analysis, and generate a test report.

[0060] Preferably, this embodiment uses a count file in non-volatile storage to permanently store the specified number of restarts for the test target and the current number of restarts in the process state. This embodiment achieves breakpoint continuation and precise control of the test process. Regardless of whether the device restarts due to testing or experiences an unexpected power outage, it can resume from the last interrupted count point, ensuring the continuity and reliability of long-cycle testing. Simultaneously, it ensures that the test service, as a system daemon process, automatically starts with the device upon power-up, laying the foundation for fully automated testing. The current value is read and compared with the target value; if they are not equal, a count increment-triggered restart operation is performed. This embodiment achieves a fully automated testing process without manual intervention. High-intensity stress testing is performed; through programmed, mechanical, repeated restarts, extreme start-stop conditions that the equipment may experience during its lifecycle are simulated. This is crucial for verifying the firmware stability, hardware reliability, and robustness of the power management module of SIS equipment. The testing process is transformed into a measurable, comparable, and decision-making quality report. By calculating the average startup time of multiple devices and conducting comparative analysis, the report not only reflects the restart stability of a single device but also assesses the consistency of product batches, performance margins, and the presence of abnormal outliers at the system level, providing direct data support for product quality assessment and improvement.

[0061] In summary, this embodiment presents a complete workflow from state initialization and persistence to automated stress execution to data acquisition and analysis. Together, they transform a previously time-consuming, labor-intensive, and difficult-to-standardize manual test into an efficient, repeatable, and data-driven automated quality verification process, significantly improving the test coverage and evaluation objectivity for high-reliability industrial control equipment.

[0062] like Figure 7 As shown, this embodiment provides an embodiment of an electronic device 4, which includes a processor 41 and a memory 42 coupled to the processor 41.

[0063] The memory 42 stores program instructions for implementing the trusted SIS trusted startup performance testing method of any of the above embodiments.

[0064] The processor 41 is used to execute program instructions stored in the memory 42 to perform trusted SIS trusted boot performance testing.

[0065] The processor 41 can also be referred to as a CPU (Central Processing Unit). The processor 41 may be an integrated circuit chip with signal processing capabilities. The processor 41 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor.

[0066] Furthermore, Figure 8 This is a schematic diagram of the structure of a storage medium according to an embodiment of this application. The storage medium 5 of this embodiment stores program instructions 51 capable of implementing all the methods described above. These program instructions 51 can be stored in the storage medium in the form of a software product, including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, or terminal devices such as computers, servers, mobile phones, and tablets.

[0067] 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 a logical functional division, 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 an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0068] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units. The above are merely embodiments of the present invention and do not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

[0069] The specific embodiments of the invention have been described in detail above, but these are merely examples, and the invention is not limited to the specific embodiments described above. For those skilled in the art, any equivalent modifications or substitutions to the invention are also within the scope of this invention. Therefore, all equivalent transformations, modifications, and improvements made without departing from the spirit and principles of this invention should be included within the scope of this invention.

Claims

1. A trusted SIS trusted startup performance testing method, characterized in that, Includes the following steps: Edit the count file, specifying the number of restarts required and the current restart count; restart the trusted SIS device, the test service starts automatically upon boot, and the script file is executed; read the current system time and current restart count of the device; The current restart count is compared with the system-specified restart count. If they are not equal, the current restart count in the counter file is incremented by one, and the device restarts are continued until the current restart count equals the system-specified restart count, at which point the test ends.

2. The trusted SIS trusted startup performance testing method as described in claim 1, characterized in that, The process of executing a script file includes the following steps: A complete external power supply interruption and recovery operation is applied to the trusted SIS device, which forces all dynamic processes inside the trusted SIS device to enter a state of quiescence. When the external power supply is restored, the quiescent system loads basic functions step by step according to its fixed initial sequence until all functions are ready and enters a stable waiting state that accepts instructions. The stable waiting state is the ready state after the trusted SIS device restarts. In the ready state, a set of preset boot instructions are automatically triggered to unpack a series of scattered functional module packages in sequence. Based on the association rules defined in the functional module packages, they are autonomously assembled, mutually verified, and logically linked in memory. When all the defined key functional modules are assembled and form a closed loop, a complete test service function body is instantly activated, and the functional modules enter the standby state. The functional module reads the specified script file, which is converted into a series of operation steps with dependencies. It locks and executes the first step in the operation step sequence, and uses the successful execution result as the only credential to unlock and execute the next step. When the last step in the operation step sequence is completed and confirmed, the entire script file execution process ends, reaching the preset termination state. The termination state will be used to obtain the current system time and restart count.

3. The trusted SIS trusted startup performance testing method as described in claim 1, characterized in that, The process of until the current restart count equals the system's specified restart count includes the following steps: The specified number of system restarts is subtracted from the current number of restarts to obtain an integer deviation value. If the integer deviation value is not equal to zero, it is determined that there is a target deviation, and an iterative instruction is generated. If the integer deviation value is equal to zero, it is determined that the target has been reached, and a termination instruction is generated. When an iteration instruction is received, an atomic update transaction for the counter file is initiated. First, the current restart count value stored in the file is read, the current restart count value is converted into a numerical format and then incremented by one to obtain the new restart count value. The new restart count value is converted back to the storage format and completely overwritten to the original file position. After the update is successful, an update completion event notification containing the new restart count value is output. Once the update completion event notification is captured, the device reset process is triggered, forcibly clearing all dynamic operating states, followed by a complete power supply interruption and recovery operation. After power recovery, the trusted SIS device reloads according to its fixed sequence until the test service is automatically activated and the script file is executed. The script file will then read the current restart count value from the counter file again. The process automatically connects and triggers the integer deviation value quantization and judgment again. When the termination command is output, the iteration stops and the test process ends.

4. The trusted SIS trusted startup performance testing method as described in claim 3, characterized in that, The process of converting the new restart count value back to the storage format and completely overwriting it to the original file location includes the following steps: Read the character sequence of the current restart count value from the count file. Based on the predefined symbol semantic lookup table, uniquely map the visual symbol of each character in the character sequence to an abstract mathematical concept value. Combine the values ​​according to positional weights to form an abstract numerical value for mathematical operations. Apply a unit recursive procedure to the abstract value, jump from the value state represented by the current abstract value to the next value state arranged in natural number order; output the value of the successor state. Abstract mathematical values ​​are re-encoded into storable visual symbols. Based on a symbol semantic lookup table, subsequent state values ​​are decomposed into multiple components weighted by position. The value corresponding to each component is then inversely mapped back to a special character symbol. The character symbols are combined sequentially to generate a new character sequence with incremented counts. This character sequence is the new restart count value, used to overwrite the original file position, and included in the update completion event notification.

5. The trusted SIS trusted startup performance testing method as described in claim 4, characterized in that, The process of outputting the successor state value includes the following steps: The abstract numerical value is input as a coordinate parameter into the reference coordinate system; each integer scale point in the reference coordinate system uniquely corresponds to an accepted quantity state; by matching across the entire scale, the abstract numerical value is locked onto a scale point in the coordinate system that completely coincides with it; the locked scale point is output. Using the locked tick mark as a trigger condition, a regular pointer with a fixed operating distance is activated. The tip of the regular pointer always points to the next adjacent tick mark along the positive direction of the coordinate axis, separated by a fixed unit length. After the regular pointer is activated, it automatically swings from the locked tick mark and stably points to its adjacent target tick mark. Once the rule pointer stably points to an adjacent target tick point, the reading operation is initiated to identify the unique coordinate value represented by the adjacent target tick point in the reference coordinate system, and extract the unique coordinate value as a new mathematical quantity. The extracted quantity is the final output successor state quantity, marking the complete transition from the original state to the next state.

6. The trusted SIS trusted startup performance testing method as described in claim 5, characterized in that, The process of locking an abstract numerical value onto a tick mark that perfectly coincides with it in a coordinate system includes the following steps: The input abstract value is converted into a frequency signal according to scalar parameters, which is then transformed into an oscillating waveform with a frequency. The oscillating waveform carries all the information of the abstract value and serves as the excitation signal, outputting as the input waveform. The input waveform is applied to a wideband resonant cavity representing the full scale range, covering the resonant frequencies corresponding to all integer scale points from zero to positive infinity; when the frequency of the input waveform coincides with a certain frequency in the wideband resonant cavity, resonance is triggered at that frequency point; the output is the resonant frequency point that is uniquely and significantly excited in the resonant cavity. The obtained resonant frequency points are mapped one-to-one back to a spatial scale point with integer coordinates in the reference coordinate system through a frequency-space mapper. Through frequency-space mapping, the resonant frequency points are converted into a specific spatial location, which is the target scale point. The target scale point is a locked position that completely coincides with the initial abstract value.

7. The trusted SIS trusted startup performance testing method as described in claim 6, characterized in that, The process of converting scalar parameters into a frequency signal and then into an oscillating waveform with a frequency includes the following steps: The abstract numerical value input is treated as an isolated element and embedded into an algebraic structure with total order relation through an injective mapping rule; the pivot element has a definite order position in the algebraic structure. Using the step size determined by the position of the reference element, starting from the zero element of the structure, continuous and equally spaced element-taking operations are performed to generate a periodic element sequence. Based on the fixed period of the occurrence of elements in the element sequence, the length of its periodic interval is measured and quantified into a frequency value; at the same time, according to the inherent rules of the generating function, an amplitude variation pattern is assigned to the element distribution within each period; the frequency value and the amplitude pattern together define an ideal periodic waveform, which is the output oscillation waveform.

8. The trusted SIS trusted startup performance testing method as described in claim 7, characterized in that, The process of embedding into an algebraic structure with a total order relation includes the following steps: A base set containing infinitely ordered elements is set up by default, and there is a clear order relationship between any two elements, which constitutes a total order structure reference system; The input abstract numerical value is used as a filtering condition and applied to the total order structure reference system. An equivalence relation is defined on the total order structure reference system: if the order of an element in the total order structure reference system is equal to the abstract numerical value, it belongs to the target equivalence class. According to the definition of the equivalence relation, all elements in the reference system that satisfy the equation are assigned to the same target equivalence class, thus completing the filtering. The target equivalence class contains only one unique element. This unique element is extracted and defined as the representative element of the target equivalence class. The representative element is the embedding result of the abstract numerical value in the total order structure.

9. The trusted SIS trusted startup performance testing method as described in claim 1, characterized in that, The time required to restart the system's reliable quality is determined based on the test results; Deploy a trusted SIS device environment; input script files, technical documents, and test services into the trusted SIS device to obtain the average startup time of all devices; compare the average startup time of all devices, perform analysis, and generate a test report.

10. A trusted SIS trusted startup performance testing system, used to implement the trusted SIS trusted startup performance testing method as described in any one of claims 1 to 9, characterized in that, include: The device information reading module is used to edit the count file, specifying the number of restarts required and the current number of restarts. Reboot the trusted SIS device. The test service will start automatically upon system boot and execute the script file; read the current system time and current reboot count of the device. The test device information module is used to compare the current restart count with the system-specified restart count. When the two are not equal, the current restart count in the counter file is incremented by one, and the device restarts are continued until the current restart count is equal to the system-specified restart count, at which point the test ends. The test report generation module is used to determine the time required to restart the system based on the test results; Deploy a trusted SIS device environment; input script files, technical documents, and test services into the trusted SIS device to obtain the average startup time of all devices; compare the average startup time of all devices, perform analysis, and generate a test report.

Images