Domestic software and hardware adaptation verification processing method and system

Abstract

The invention provides a domestic software and hardware adaptation verification processing method and system, and belongs to the technical field of data processing, and the method specifically comprises the steps: determining the circuit structure deviation conditions of a hardware device and a replacement target in different types of hardware modules according to the analysis data of the hardware device, determining hardware deviation coefficients of different types of hardware modules and concerned hardware modules by combining the hardware deviation conditions of the hardware modules, and when determining that the deviation conditions of the hardware device meet requirements according to the distribution data of the concerned hardware modules of the hardware device, taking a service type borne by the hardware device as a bearing service type; and the analysis results of the historical problem data of the different bearer service types and the involved hardware deviation coefficient of the concerned hardware module are utilized to determine compatibility verification strategies of the different bearer service types, so that the compatibility verification processing efficiency is improved.

Description

Technical Field

[0001] The present invention belongs to the field of data processing technology, and in particular relates to a domestic software and hardware adaptation verification processing method and system. Background Art

[0002] As the important business systems supporting the operation of the power grid are facing the risk of power outage and service suspension, the safe and stable operation of the energy and power system is seriously threatened. This makes the localization transformation of the energy and power system a technical problem that needs to be solved urgently.

[0003] In the process of adaptation verification processing of the existing technical solution, due to the different degrees of differences in the hardware structure and hardware composition of the hardware device and the replacement target, there are certain differences in the probability of compatibility problems occurring in different hardware devices when performing replacement processing. Therefore, if the compatibility debugging strategy cannot be determined according to the degree of difference, the accuracy of the adaptation verification processing results cannot be guaranteed.

[0004] In response to the above technical problems, the present invention provides a method and system for domestic software and hardware adaptation verification processing. Summary of the invention

[0005] To achieve the purpose of the present invention, the present invention adopts the following technical solutions: According to one aspect of the present invention, a method for domestic software and hardware adaptation verification processing is provided.

[0006] A domestic software and hardware adaptation verification processing method, specifically comprising: S1 determines the interactive hardware device with the hardware device based on the analysis data of the hardware device, and proceeds to the next step when it is determined that the abnormality of the compatibility problem of the hardware device meets the requirements based on the similarity between the composition data of the interactive hardware device and the historical compatibility data and the analysis result of the compatibility problem; S2 determines the circuit structure deviation between the hardware device and the replacement target in different types of hardware modules based on the analysis data of the hardware device, and determines the hardware deviation coefficients of different types of hardware modules and the hardware modules of interest based on the hardware deviation of the hardware modules; S3: When it is determined that the deviation of the hardware device meets the requirement according to the distribution data of the hardware module concerned by the hardware device, proceed to the next step; S4 takes the service type carried by the hardware device as the bearer service type, and uses the analysis results of historical problem data of different bearer service types and the hardware deviation coefficient of the concerned hardware module to determine the compatibility verification strategy of different bearer service types.

[0007] The beneficial effects of the present invention are: Based on the distribution data of the hardware modules of the hardware device, it is determined whether the deviation of the hardware device meets the requirements, thereby realizing the determination of the comprehensive deviation between the hardware device and the replacement target from the deviation of the hardware modules of the hardware device, and further laying the foundation for determining the compatibility verification strategy for different bearer service types of the hardware device according to the comprehensive deviation situation, which not only ensures the reliability of the compatibility verification processing, but also ensures the efficiency of the compatibility verification processing.

[0008] By utilizing the analysis results of historical problem data of different bearer service types and the hardware deviation coefficient of the concerned hardware modules, compatibility verification strategies for different bearer service types are determined, thereby achieving differentiated compatibility verification processing for different bearer service types. This takes into account both the historical problem situations of the bearer service types and the differences in the probabilities of compatibility anomalies caused by the hardware deviation situations of the concerned hardware modules, thereby achieving compatibility verification processing for hardware devices.

[0009] A further technical solution is that the interactive hardware device is another hardware device that has a data interaction relationship with the hardware device.

[0010] A further technical solution is that the historical compatibility data is determined based on the analysis results of the compatibility data of the hardware device during the historical domestic substitution process.

[0011] A further technical solution is that the historical compatibility data includes the type of compatibility problem and the number of occurrences of different types of compatibility problems.

[0012] A further technical solution is to determine whether the abnormality degree of the compatibility problem of the hardware device meets the requirements, specifically including: Determine the similarity number of interactive hardware devices with different domestic substitution times based on the composition data of the interactive hardware device; Determine similarity coefficients with different domestic substitution times using the similarity quantity, and determine reference substitution times in the domestic substitution times according to the similarity coefficients; The total number of occurrences of the compatibility problem is determined based on the number of occurrences of the compatibility problem with different reference replacement times, and the total number of occurrences of the compatibility problem is used to determine whether the abnormality degree of the compatibility problem of the hardware device meets the requirement.

[0013] A further technical solution is that, when the total number of occurrences of the compatibility problem is greater than a preset number threshold, it is determined that the abnormality level of the compatibility problem of the hardware device does not meet the requirements.

[0014] A further technical solution is that the compatibility verification strategy is determined according to the call concurrency interval corresponding to the bearer service type, and specific different compatibility verification strategies include using different call concurrency intervals to perform verification processing on the bearer service type.

[0015] A further technical solution is that the preset verification strategy includes performing verification processing on the bearer service type in all call concurrency intervals.

[0016] In a second aspect, the present invention provides a computer system comprising: a memory and a processor that are communicatively connected, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the above-mentioned domestic software and hardware adaptation verification processing method when running the computer program.

[0017] Other features and advantages will be described in the following description, and partly become apparent from the description, or understood by practicing the invention. The purpose and other advantages of the invention are realized and obtained by the structures particularly pointed out in the description and the drawings.

[0018] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0020] Figure 1 It is a flow chart of a domestic software and hardware adaptation verification processing method; Figure 2 is a flow chart of a method for determining that the abnormality level of a compatibility problem of a hardware device satisfies a requirement; Figure 3 It is a flow chart of a method for determining a hardware deviation coefficient of a hardware module. DETAILED DESCRIPTION

[0021] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that the present invention will be comprehensive and complete and fully convey the concepts of the example embodiments to those skilled in the art. The same reference numerals in the figures represent the same or similar structures, and thus their detailed description will be omitted.

[0022] The terms "a", "an", "the", and "said" are used to indicate the presence of one or more elements / components / etc.; the terms "comprising" and "having" are used to express an open-ended inclusive meaning and mean that additional elements / components / etc. may be present in addition to the listed elements / components / etc.

[0023] Example 1 To solve the above problems, according to one aspect of the present invention, Figure 1 As shown, according to one aspect of the present invention, a method for verifying the localization of software and hardware adaptation is provided, which specifically includes: S1 determines the interactive hardware device with the hardware device based on the analysis data of the hardware device, and proceeds to the next step when it is determined that the abnormality of the compatibility problem of the hardware device meets the requirements based on the similarity between the composition data of the interactive hardware device and the historical compatibility data and the analysis result of the compatibility problem; S2 determines the circuit structure deviation between the hardware device and the replacement target in different types of hardware modules based on the analysis data of the hardware device, and determines the hardware deviation coefficients of different types of hardware modules and the hardware modules of interest based on the hardware deviation of the hardware modules; S3: When it is determined that the deviation of the hardware device meets the requirement according to the distribution data of the hardware module concerned by the hardware device, proceed to the next step; S4 takes the service type carried by the hardware device as the bearer service type, and uses the analysis results of historical problem data of different bearer service types and the hardware deviation coefficient of the concerned hardware module to determine the compatibility verification strategy of different bearer service types.

[0024] Furthermore, the interactive hardware device is another hardware device that has a data interaction relationship with the hardware device.

[0025] Specifically, the historical compatibility data is determined based on the analysis results of the compatibility data of the hardware device during the historical domestic substitution process.

[0026] It should be noted that the historical compatibility data includes the type of compatibility problem and the number of occurrences of different types of compatibility problems.

[0027] Optional, such as Figure 2 As shown, determining that the abnormality degree of the compatibility problem of the hardware device meets the requirements specifically includes: Determine the similarity number of interactive hardware devices with different domestic substitution times based on the composition data of the interactive hardware device; Determine similarity coefficients with different domestic substitution times using the similarity quantity, and determine reference substitution times in the domestic substitution times according to the similarity coefficients; The total number of occurrences of the compatibility problem is determined based on the number of occurrences of the compatibility problem with different reference replacement times, and the total number of occurrences of the compatibility problem is used to determine whether the abnormality degree of the compatibility problem of the hardware device meets the requirement.

[0028] Further, when the total number of occurrences of the compatibility problem is greater than a preset number threshold, it is determined that the abnormality degree of the compatibility problem of the hardware device does not meet the requirement.

[0029] In another embodiment, determining that the abnormality degree of the compatibility problem of the hardware device meets the requirement specifically includes: Determine the similarity number of interactive hardware devices with different domestic substitution times based on the composition data of the interactive hardware device; Determine similarity coefficients with different domestic substitution times using the similarity quantity, and determine reference substitution times in the domestic substitution times according to the similarity coefficients; The number of occurrences of the compatibility problem based on different reference replacement times is determined as a reference replacement number whose occurrence number is greater than the preset occurrence number, and the reference replacement number whose occurrence number is greater than the preset occurrence number is used to determine whether the abnormality of the compatibility problem of the hardware device meets the requirements.

[0030] Furthermore, when the abnormality degree of the compatibility problem of the hardware device does not meet the requirement, the compatibility verification strategy of the hardware device is determined according to the preset verification strategy for all bearer service types.

[0031] Optionally, determining whether the abnormality degree of the compatibility problem of the hardware device meets the requirement specifically includes: S11 determines the similarity number of the interactive hardware devices with different localization replacement times based on the composition data of the interactive hardware device, determines the similarity coefficient with different localization replacement times based on the similarity number, and determines the reference replacement number in the localization replacement times based on the similarity coefficient; Furthermore, before entering step S12, the following contents are also included: S111 obtains the number of occurrences of the compatibility problem in different reference replacement times. When the number of occurrences of the compatibility problem does not meet the required reference replacement times, it is determined that the abnormality of the compatibility problem of the hardware device does not meet the requirements. When the number of occurrences of the compatibility problem does not meet the required reference replacement times, the process proceeds to step S112. S112: Obtain the occurrence times of the compatibility problem in different reference replacement times. When there is a reference replacement time whose occurrence times are within the preset occurrence times interval, proceed to step S114; when there is no reference replacement time whose occurrence times are within the preset occurrence times interval, proceed to step S113; S113 determines the reference replacement times with compatibility problems according to the occurrence times of compatibility problems in different reference replacement times. When the proportion of the reference replacement times with compatibility problems is within the preset times proportion interval, it is determined that the abnormality degree of the compatibility problem of the hardware device meets the requirement. When the proportion of the reference replacement times with compatibility problems is not within the preset times proportion interval, the process proceeds to step S114. S114 When the proportion of the number of reference alternative times within the preset occurrence number interval does not meet the requirement, it is determined that the abnormality level of the compatibility problem of the hardware device does not meet the requirement. When the proportion of the number of reference alternative times within the preset occurrence number interval meets the requirement, proceed to step S12.

[0032] S12 determines the compatibility problem abnormality coefficients of different reference replacement times according to the occurrence times of different types of compatibility problems in different reference replacement times; Optionally, the above step S12 includes the following contents: S121 determines the compatibility problem abnormality coefficients of different reference replacement times according to the occurrence times of different types of compatibility problems in different reference replacement times, and when there is a reference replacement time with a compatibility problem abnormality coefficient within a preset abnormality coefficient interval, proceeds to step S122; when there is no reference replacement time with a compatibility problem abnormality coefficient within the preset abnormality coefficient interval, proceeds to step S13; S122: When the reference number of replacements of the compatibility problem abnormality coefficient within the preset abnormality coefficient interval does not meet the requirement, it is determined that the abnormality degree of the compatibility problem of the hardware device does not meet the requirement; when the reference number of replacements of the compatibility problem abnormality coefficient within the preset abnormality coefficient interval meets the requirement, the process proceeds to step S123; S123 obtains the reference number of replacements of the compatibility problem abnormality coefficient within the preset abnormality coefficient interval, and determines the interval abnormality coefficient within the preset abnormality coefficient interval in combination with the compatibility problem abnormality coefficient of the reference number of replacements of the compatibility problem abnormality coefficient within the preset abnormality coefficient interval. When the interval abnormality coefficient within the preset abnormality coefficient interval does not meet the requirements, it is determined that the abnormality degree of the compatibility problem of the hardware device does not meet the requirements. When the interval abnormality coefficient within the preset abnormality coefficient interval meets the requirements, proceed to step S13.

[0033] S13 determines a comprehensive problem abnormality coefficient based on the compatibility problem abnormality coefficients of different reference replacement times, and uses the comprehensive problem abnormality coefficient to determine whether the abnormality degree of the compatibility problem of the hardware device meets the requirements.

[0034] Furthermore, the hardware module includes a central processing unit module, a memory module, a chipset module, an I / O bus module, an I / O device module, a power module, a fan module, and a GPU module.

[0035] Specifically, the hardware deviation of the hardware module includes the deviation of the chip of the hardware module.

[0036] Specifically, Figure 3 As shown, the method for determining the hardware deviation coefficient of the hardware module is: Based on the circuit structure deviation of the hardware device and the replacement target in the hardware module, determining the circuit structure deviation of the hardware module, and determining the circuit structure deviation coefficient of the hardware module according to the circuit structure deviation; Determining the chip deviation of the hardware module based on the hardware deviation of the hardware module, and determining the chip deviation coefficient of the hardware module based on the chip deviation; The hardware deviation coefficient of the hardware module is determined by the chip deviation coefficient and the circuit structure deviation coefficient.

[0037] Furthermore, the hardware deviation coefficient of the hardware module is determined according to an average value of the chip deviation coefficient and the circuit structure deviation coefficient.

[0038] Optionally, when the hardware deviation coefficient of the hardware module is not within a preset deviation coefficient interval, the hardware module is determined to be a hardware module of interest.

[0039] In another embodiment, the method for determining the hardware deviation coefficient of the hardware module is: Based on the circuit structure deviation of the hardware device and the replacement target in the hardware module, determine the circuit structure deviation of the hardware module, and when the circuit structure deviation of the hardware module meets the requirements, determine that the hardware module does not belong to the hardware module of interest; The circuit structure deviation coefficient of the hardware module is determined based on the circuit structure deviation of the hardware module. When the circuit structure deviation coefficient of the hardware module is within a preset deviation coefficient range: Determine the deviation of the chip of the hardware module based on the hardware deviation of the hardware module, and when it is determined that the hardware module does not have a deviated chip based on the deviation of the chip of the hardware module, determine that the hardware module does not belong to the hardware module of interest; When the chip of the hardware module is determined to have a deviation by using the deviation of the chip of the hardware module: The number of chips with deviations in the hardware module is obtained. When the number of chips with deviations in the hardware module meets the requirement: The chip with deviation in the hardware module is regarded as the deviation chip, the role of different deviation chips in the hardware module is obtained, and the weight coefficients of different deviation chips are determined by using the role of different deviation chips in the hardware module. When there is no deviation chip whose weight coefficient does not meet the requirement, it is determined that the hardware module does not belong to the hardware module of interest; When the circuit structure deviation coefficient of the hardware module is not within the preset deviation coefficient range or the number of chips with deviations in the hardware module does not meet the requirements or there are deviation chips whose weight coefficients do not meet the requirements: Determine the chip deviation of the hardware module based on the hardware deviation of the hardware module, and determine the chip deviation coefficient of the hardware module in combination with weight coefficients of different deviation chips; The hardware deviation coefficient of the hardware module is determined by the chip deviation coefficient and the circuit structure deviation coefficient.

[0040] Optionally, determining whether the deviation of the hardware device meets the requirement specifically includes: Determine the number of the hardware modules of interest of the hardware device based on the distribution data of the hardware modules of interest of the hardware device, and determine the basic deviation coefficient of the hardware device based on the proportion of the number of the hardware modules of interest of the hardware device; According to the hardware deviation coefficients of the different hardware modules of interest of the hardware device, an average value of the hardware deviation coefficients of the different hardware modules of interest is determined, and the average value is used as the deviation coefficient average value; A comprehensive deviation coefficient is determined based on the basic deviation coefficient and the average value of the deviation coefficient, and the comprehensive deviation coefficient is used to determine whether the deviation of the hardware device meets the requirements.

[0041] Further, when the comprehensive deviation coefficient of the hardware device is not within a preset deviation coefficient range, it is determined that the deviation of the hardware device does not meet the requirements.

[0042] Specifically, when the deviation of the hardware device does not meet the requirement, the compatibility verification strategy of the hardware device is determined according to a preset verification strategy for all bearer service types.

[0043] Furthermore, the historical problem data is determined according to the number of different types of failures of the replacement target during the operation of the bearer service type.

[0044] Specifically, the method for determining the compatibility verification strategy of the bearer service type is: Determine the number of different types of failures corresponding to the bearer service type based on the analysis result of the historical problem data of the bearer service type, and determine the failure anomaly coefficient of the bearer service type according to the number of different types of failures; Determining a hardware device variation coefficient of the bearer service type according to a hardware deviation coefficient of a concerned hardware module involved in the bearer service type; A verification requirement coefficient of the bearer service type is determined based on the hardware device variation coefficient and the fault anomaly coefficient, and a compatibility verification strategy of the bearer service type is determined through the verification requirement coefficient.

[0045] Further, determining the compatibility verification strategy of the bearer service type by the verification requirement coefficient specifically includes: The preset verification strategy corresponding to the verification requirement coefficient is used to determine the compatibility verification strategy of the bearer service type.

[0046] Optionally, the compatibility verification strategy is determined according to the call concurrency interval corresponding to the bearer service type. Specifically, different compatibility verification strategies include using different call concurrency intervals to perform verification processing on the bearer service type.

[0047] Furthermore, the preset verification strategy includes performing verification processing on the bearer service type in all call concurrency intervals.

[0048] Example 2 In a second aspect, the present invention provides a computer system comprising: a memory and a processor that are communicatively connected, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the above-mentioned domestic software and hardware adaptation verification processing method when running the computer program.

[0049] Optionally, determining whether the deviation of the hardware device meets the requirement specifically includes: Determine the number of the concerned hardware modules of the hardware device based on the distribution data of the concerned hardware modules of the hardware device, and when the number or the proportion of the concerned hardware modules of the hardware device does not meet the requirement, determine that the deviation of the hardware device does not meet the requirement; When the number or proportion of the hardware modules of interest in the hardware device meets the requirements: Determine the basic deviation coefficient of the hardware device according to the number of concerned hardware modules of the hardware device and the proportion of the number of concerned hardware modules in the hardware device, and when the basic deviation coefficient of the hardware device does not meet the requirement, determine that the deviation of the hardware device does not meet the requirement; When the basic deviation coefficient of the hardware device meets the requirements: According to the hardware deviation coefficients of different concerned hardware modules of the hardware device, when the number of concerned hardware modules whose hardware deviation coefficients are greater than a preset deviation coefficient threshold does not meet the requirement, it is determined that the deviation of the hardware device does not meet the requirement; When the hardware deviation coefficient is greater than the preset deviation coefficient threshold, the number of concerned hardware modules meets the requirement: Determine the average value of the hardware deviation coefficients of different hardware modules of interest and use it as the average value of the deviation coefficients. When the average value of the deviation coefficients does not meet the requirements: When the basic deviation coefficient is within the preset deviation coefficient range, it is determined that the deviation of the hardware device does not meet the requirement; When the deviation coefficient average value meets the requirement or the basic deviation coefficient is within the preset deviation coefficient range: A comprehensive deviation coefficient is determined based on the basic deviation coefficient and the average value of the deviation coefficient, and the comprehensive deviation coefficient is used to determine whether the deviation of the hardware device meets the requirements.

[0050] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0051] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0052] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A domestic software and hardware adaptation verification processing method, characterized in that: Specifically include: Based on the analysis data of the hardware device, determine the interactive hardware device with the hardware device, and when it is determined that the abnormality of the compatibility problem of the hardware device meets the requirements based on the similarity between the composition data of the interactive hardware device and the historical compatibility data and the analysis result of the compatibility problem, proceed to the next step; Determine the circuit structure deviation between the hardware device and the replacement target in different types of hardware modules based on the analysis data of the hardware device, and determine the hardware deviation coefficients of different types of hardware modules and the hardware modules of interest based on the hardware deviation of the hardware modules; When it is determined according to the distribution data of the hardware module of interest of the hardware device that the deviation of the hardware device meets the requirement, proceed to the next step; The service type carried by the hardware device is taken as the bearer service type, and the compatibility verification strategy of different bearer service types is determined by utilizing the analysis results of historical problem data of different bearer service types and the hardware deviation coefficient of the concerned hardware module involved.

2. The method for verifying the localization of software and hardware adaptation according to claim 1, characterized in that: The interactive hardware device is another hardware device that has a data interaction relationship with the hardware device.

3. The domestic software and hardware adaptation verification processing method according to claim 1, characterized in that: The historical compatibility data is determined based on the analysis results of the compatibility data of the hardware device during the historical domestic substitution process.

4. The method for verifying the localization of software and hardware adaptation as claimed in claim 3, characterized in that: The historical compatibility data includes the type of compatibility problem and the number of occurrences of different types of compatibility problems.

5. The domestic software and hardware adaptation verification processing method as claimed in claim 1, characterized in that: Determining that the abnormality degree of the compatibility problem of the hardware device meets the requirements specifically includes: Determine the similarity number of interactive hardware devices with different domestic substitution times based on the composition data of the interactive hardware device; Determine similarity coefficients with different domestic substitution times using the similarity quantity, and determine reference substitution times in the domestic substitution times according to the similarity coefficients; The total number of occurrences of the compatibility problem is determined based on the number of occurrences of the compatibility problem with different reference replacement times, and the total number of occurrences of the compatibility problem is used to determine whether the abnormality degree of the compatibility problem of the hardware device meets the requirement.

6. The domestic software and hardware adaptation verification processing method as claimed in claim 5, characterized in that: When the total number of occurrences of the compatibility problem is greater than a preset number threshold, it is determined that the abnormality degree of the compatibility problem of the hardware device does not meet the requirement.

7. The domestic software and hardware adaptation verification processing method as claimed in claim 1, characterized in that: The method for determining the hardware deviation coefficient of the hardware module is: Based on the circuit structure deviation of the hardware device and the replacement target in the hardware module, determining the circuit structure deviation of the hardware module, and determining the circuit structure deviation coefficient of the hardware module according to the circuit structure deviation; Determining the chip deviation of the hardware module based on the hardware deviation of the hardware module, and determining the chip deviation coefficient of the hardware module based on the chip deviation; The hardware deviation coefficient of the hardware module is determined by the chip deviation coefficient and the circuit structure deviation coefficient.

8. The method for verifying the localization of software and hardware adaptation as claimed in claim 7, characterized in that: The hardware deviation coefficient of the hardware module is determined according to an average value of the chip deviation coefficient and the circuit structure deviation coefficient.

9. The method for verifying the localization of software and hardware adaptation according to claim 1, characterized in that: When the hardware deviation coefficient of the hardware module is not within a preset deviation coefficient interval, the hardware module is determined to be a focused hardware module.

10. A computer system comprising: A memory and a processor connected in communication, and a computer program stored in the memory and capable of running on the processor, characterized in that the processor executes a domestic software and hardware adaptation verification processing method as described in any one of claims 1-9 when running the computer program.

Images