CN113535553B - Parameter checking method, computer device and storage medium - Google Patents

Abstract

The application relates to a parameter checking method, computer equipment and a storage medium. The method comprises the steps of receiving a parameter verification request comprising values of a plurality of parameters to be verified, obtaining a verification rule corresponding to each parameter to be verified according to a preset corresponding relation between the verification parameters and the verification rules, and performing validity verification on the value of each parameter to be verified according to the type of each verification rule to obtain a verification result. According to the method, the value of the parameter to be verified is verified according to the type of the verification rule, and the corresponding relation between the verification parameter and the verification rule is established in advance, so that if the parameter to be verified input by a clinical engineer on the front end changes later, the verification can be realized only by updating the corresponding relation between the verification parameter and the verification rule, and the verification code corresponding to the changed parameter to be verified does not need to be revised again.

Description

Parameter verification method, computer equipment and storage medium

technical field

The present application relates to the field of computer technology, in particular to a parameter verification method, computer equipment and storage media.

Background technique

Digital subtraction angiography (Digital subtraction angiography, DSA) is used to digitally input two frames of X-ray images taken before and after injection of contrast agent into computer equipment, and through the process of subtraction, enhancement and re-imaging, bone and soft tissue on angiography images Image elimination to obtain clear pure vascular images is an inspection method that combines computer and conventional X-ray angiography.

In the control process of using DSA equipment for contrast imaging, the DSA system's process of verifying the front-end parameter information is a crucial link. At present, after clinical engineers input parameter information related to the control process such as parameter data content, parameter thresholds, and rule constraints at the front end, during the development process of the back-end control process, R&D engineers need to design corresponding rule verification for each parameter information Code, and then use the designed rule verification code to verify the parameters of each parameter information, so as to ensure the accuracy of the parameter information, and then ensure the normal operation of the DSA system.

However, if the required parameter information changes, the R&D engineer needs to redesign the rule verification code corresponding to the relevant parameter information, and then use the redesigned rule verification code to verify the parameter information. Such a verification method exists The problem of low calibration efficiency.

Contents of the invention

Based on this, it is necessary to provide a parameter verification method, computer equipment and storage medium that can effectively improve the verification efficiency.

In the first aspect, a parameter checking method, the method includes:

Receive a parameter verification request; the parameter verification request includes the values of multiple parameters to be verified;

Acquiring a verification rule corresponding to each of the parameters to be verified according to the preset correspondence between the verification parameter and the verification rule;

According to the type of each verification rule, the validity of each value of the parameter to be verified is verified to obtain a verification result.

In one of the embodiments, according to the type of each verification rule, the validity of each value of the parameter to be verified is verified, and the verification result is obtained, including:

judging whether the ignoring state of each parameter to be verified is a non-ignoring state;

If the ignoring state of the parameter to be verified is the non-ignorable state, then according to the preset correspondence between the type of verification rule and the verification strategy, determine the verification corresponding to the type of the verification rule strategy, and use the verification strategy to verify the validity of the value of the parameter to be verified.

In one of the embodiments, if the type of the verification rule is a basic rule or an application branch rule, then using the verification strategy to verify the validity of the value of the parameter to be verified includes:

Determine the verification index according to the verification rule corresponding to the parameter to be verified;

judging whether the value of the parameter to be verified reaches the verification index, if the verification index is reached, then determine that the value of the parameter to be verified is legal, and if it does not reach the verification index, then determine the value of the verification index The value of the parameter to be verified is illegal.

In one of the embodiments, if the type of the check item rule is the application branch rule, the method further includes:

According to the verification rule corresponding to the parameter to be verified and the value of the parameter to be verified, determine whether the parameter to be verified associated with the parameter to be verified can be ignored;

If the parameter to be verified associated with the parameter to be verified is negligible, then the ignore state of the parameter to be verified associated with the parameter to be verified is set to an ignorable state.

In one of the embodiments, if the type of the verification item rule is an application function rule, then using the verification strategy to verify the validity of the value of the parameter to be verified includes:

According to the verification rule corresponding to the parameter to be verified, determine a function parameter that has a functional relationship with the parameter to be verified;

Acquiring the value of the function parameter from the received values of the plurality of parameters to be verified;

Substituting the value of the function parameter and the value of the parameter to be checked into the functional relationship for calculation, and performing a legality check on the value of the parameter to be checked according to the calculation result.

In one embodiment, the method also includes:

judging whether the ignored state of the function parameter is a negligible state;

If the ignoring state of the function parameter is the ignorable state, then setting the ignoring state of the parameter to be verified as the ignorable state.

In one of the embodiments, if the type of the verification rule is an application ignore rule, then using the verification strategy to verify the validity of the value of the parameter to be verified includes:

The validity check is not performed on the value of the parameter to be checked, and the ignoring state of the parameter to be checked is set to an ignorable state.

In one of the embodiments, if the verification result is that the parameter to be verified is illegal, the method further includes:

Returning the illegal parameters to be checked to the front-end device, so as to instruct the front-end device to view and/or modify the illegal parameters to be checked.

In a second aspect, a computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the method described in the first aspect above when executing the computer program.

In a third aspect, a computer-readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, the method described in the above-mentioned first aspect is implemented.

The above parameter verification method, computer equipment and storage medium, by receiving a parameter verification request including the values of a plurality of parameters to be verified, and according to the corresponding relationship between the preset verification parameters and verification rules, obtain each of the parameters to be verified. Verify the verification rules corresponding to the parameters, and then perform a legality verification on the value of each parameter to be verified according to the type of each verification rule, and obtain the verification result. The above method is to verify the value of the parameter to be verified according to the type of the verification rule, and the corresponding relationship between the verification parameter and the verification rule is established in advance, so if the clinical engineer enters the value to be verified on the front end If the parameters change, the verification can be realized only by updating the corresponding relationship between the verification parameters and the verification rules, and there is no need to re-modify the verification code corresponding to the changed parameters to be verified. Therefore, the parameters disclosed in this embodiment The verification method can greatly improve the project development efficiency of clinical engineers, thereby speeding up the project development progress.

Description of drawings

Fig. 1 is a schematic structural diagram of an application system in an embodiment;

Fig. 2 is a schematic flow diagram of a parameter checking method in an embodiment;

FIG. 3 is a schematic flowchart of an implementation of S103 in the embodiment of FIG. 2;

FIG. 4 is a schematic flowchart of an implementation of S202 in the embodiment of FIG. 3;

Fig. 5 is a schematic flow chart of a parameter checking method in an embodiment;

FIG. 6 is a schematic flowchart of an implementation of S202 in the embodiment of FIG. 3;

Fig. 7 is a schematic flow chart of a parameter verification method in an embodiment;

Fig. 8 is a schematic flow chart of a parameter checking method in an embodiment;

Fig. 9 is a schematic flowchart of a parameter verification method in an embodiment;

Fig. 10 is a structural block diagram of a parameter verification device in an embodiment;

Fig. 11 is a structural block diagram of a parameter verification device in an embodiment;

Fig. 12 is a structural block diagram of a parameter verification device in an embodiment;

Fig. 13 is a structural block diagram of a parameter verification device in an embodiment;

Fig. 14 is a structural block diagram of a parameter verification device in an embodiment;

Fig. 15 is a structural block diagram of a parameter verification device in an embodiment;

Fig. 16 is a structural block diagram of a parameter verification device in an embodiment;

Figure 17 is a diagram of the internal structure of a computer device in one embodiment.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, and are not intended to limit the present application.

The parameter verification method provided by this application can be applied to the application system shown in Figure 1, the system includes a front-end device 110 and a terminal 120, wherein the front-end device 110 and the terminal 120 can be connected in a wired or wireless manner . Parameter verification is realized through data interaction between the front-end device 110 and the terminal 120 . Users (including engineers) can input the value of the parameter to be verified on the front-end device 110, and the front-end device 110 sends a message carrying the value of the parameter to be verified to the terminal 120, and the terminal 120 verifies the value of the parameter to be verified, Then the verification result is returned to the front-end device 110 . The front-end device 110 can be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers and portable wearable devices, and the terminal 120 can be realized by an independent server or a server cluster composed of multiple servers.

Those skilled in the art can understand that the structure shown in Figure 1 is only a block diagram of a partial structure related to the solution of this application, and does not constitute a limitation on the application system to which the solution of this application is applied. The specific application system can be More or fewer components than shown in the figures may be included, or some components may be combined, or have a different arrangement of components.

In one embodiment, as shown in FIG. 2, a parameter verification method is provided, and the method is applied to the terminal in FIG. 1 as an example for illustration, including the following steps:

S101. Receive a parameter verification request; the parameter verification request includes values of a plurality of parameters to be verified.

Among them, the parameters to be verified are relevant parameters input by the demand side such as clinical engineers on the front-end equipment for controlling the terminal to perform corresponding collection operations. For example, the parameters to be verified may include: frame rate data, collection type, collection mode, high voltage parameters, and the like. The value of the parameter to be verified may represent the value of the parameter to be verified, or the value range of the parameter to be verified, or the identifier of the parameter to be verified, and the like. The parameter verification request is a request message sent by the front-end device to the terminal after the clinical engineer inputs the value of the parameter to be verified on the front-end device.

Specifically, the clinical engineer can select the appropriate value of the parameter to be verified on the display operation interface of the front-end device, and edit and input it to the front-end device. After the front-end device obtains the value of the parameter to be verified, it will be packaged in the parameter verification The request is sent to the terminal to instruct the terminal to determine the acquisition method of the terminal according to the value of the parameter to be verified, so that the terminal performs the corresponding acquisition operation according to the acquisition method set by the clinical engineer.

S102. Acquire a verification rule corresponding to each parameter to be verified according to a preset correspondence between verification parameters and verification rules.

Among them, the corresponding relationship between the verification parameters and the verification rules can be pre-built and saved by the terminal, so that the terminal can obtain each input parameter to be verified by querying the corresponding relationship between the verification parameters and the verification rules Corresponding validation rules. For example, the terminal can record the corresponding relationship between the pre-built verification parameters and verification rules in the parameter information table, and save the parameter information table, and then the terminal can read the information in the parameter information table when querying information. data to get the desired information.

Specifically, when the terminal receives a parameter verification request based on the aforementioned steps, it can extract the parameters to be verified from it, and query the correspondence between the pre-built verification parameters and verification rules, and find out the parameters to be verified. Validation rule corresponding to the parameter. Specifically, when querying, the terminal can query the parameter information table that records the correspondence between the verification parameters and the verification rules, and find the verification rules corresponding to the parameters to be verified for later use.

S103, according to the type of each verification rule, perform a legality verification on the value of each parameter to be verified to obtain a verification result.

Wherein, types of verification rules include basic rules, application branch rules, application function rules, and application ignore rules. Different types of verification rules correspond to different verification methods. The corresponding relationship between the type of verification rule and the verification method may be determined and stored by the terminal in advance. Specifically, when the terminal obtains the verification rule corresponding to each parameter to be verified, it can further analyze the type of each verification rule, and determine the corresponding verification method according to the type of each verification rule, and then The verification method corresponding to the type of each verification rule can be used to verify the validity of the value of each parameter to be verified, and it can be obtained whether the value of the parameter to be verified is a legal parameter to be verified or illegal The verification result of the parameter to be verified.

In the parameter verification method disclosed in the above embodiments, by receiving a parameter verification request including a plurality of values of the parameters to be verified, and according to the correspondence between the preset verification parameters and the verification rules, each parameter to be verified is obtained. The verification rules corresponding to the parameters, and then according to the type of each verification rule, the validity of each value of the parameter to be verified is verified to obtain the verification result. The above method is to verify the value of the parameter to be verified according to the type of the verification rule, and the corresponding relationship between the verification parameter and the verification rule is established in advance, so if the clinical engineer enters the value to be verified on the front end When the value of the parameter changes, the verification can be realized only by updating the corresponding relationship between the verification parameter and the verification rule, and it is not necessary to re-modify the verification code corresponding to the changed parameter to be verified. Therefore, this embodiment discloses The parameter verification method can greatly improve the project development efficiency of clinical engineers, thereby speeding up the project development progress.

In practical applications, based on the method described in the embodiment, when the terminal verifies the value of the parameter to be verified, and the obtained verification result is that the value of the parameter to be verified is an illegal parameter to be verified, the terminal executes After the above step S103 is completed, a step is further performed: returning the illegal parameters to be verified to the front-end device, so as to instruct the front-end device to view and/or modify the illegal parameters to be verified.

When the verification result obtained by the terminal is that the value of the parameter to be verified is an illegal parameter to be verified, it means that the verification fails, and there is a problem with the value of the parameter to be verified. It may be that the front-end engineer is editing The value of the parameter to be verified is incorrectly input, or other reasons cause the value of the parameter to be verified to be wrong. In this case, the terminal carries the invalid parameter to be verified in the feedback message and transmits it to the front end, then the The personnel can view the parameter to be verified that has an error, and then re-correct the value of the parameter to be verified, and return to the terminal for re-verification until the verification is passed. The above method provides a function that engineers and technicians can also modify parameters through data interaction between the front end and the terminal during the process of verifying parameters. Compared with the traditional verification process, when an error occurs, the engineer can only return the code segment. And modify the verification parameters by modifying the code, the method provided by the above embodiment makes the verification process more efficient, and can also reduce the difficulty of engineering personnel to modify the verification parameters and save labor costs. Correspondingly, when the verification result obtained by the terminal is that the value of the parameter to be verified is legal and the value of the parameter to be verified is legal, it means that the verification has passed. In this case, the terminal can also transmit the verification pass message to the front end , then the front-end engineering personnel can also know the verification status of the terminal for each parameter to be verified.

In one embodiment, a specific implementation of the above-mentioned S103 is provided. As shown in FIG. 3 , the above-mentioned S103 "perform a legality check on the value of each parameter to be checked according to the type of each check rule, Get the verification result", including:

S201. Determine whether the ignore state of each parameter to be verified is a non-ignorable state.

Wherein, the ignoring state of the parameter to be verified includes an ignorable state and a non-ignorable state. When the ignore state of the parameter to be verified is non-negligible, it means that the parameter to be verified needs to be verified. When the ignore state of the parameter to be verified is ignored, it means that the change of the parameter to be verified will not affect The development of the project has no effect, so the verification parameters do not need to be verified. Therefore, before the terminal checks the validity of each parameter to be checked, it first judges the ignore status of each parameter to be checked, and then determines whether to check the validity of the parameter to be checked based on different judgment results. It is necessary to perform legality verification for each parameter to be verified, which can greatly improve the verification efficiency. It should be noted that, when judging whether the ignored state of the parameter to be verified is a non-negligible state, it can be determined by checking the ignored flag bit of the parameter to be verified. For example, if the ignored flag bit of a parameter to be verified is set to 1, then The ignored state of the parameter to be verified is considered to be negligible. If the ignored flag of a parameter to be verified is set to 0, the ignored state of the parameter to be verified is considered to be non-negligible. The determination method is not limited to this In an embodiment, other methods may also be used to determine the ignore state of the parameter to be verified, which is not limited here.

S202. If the ignored state of the parameter to be verified is a non-negligible state, then according to the correspondence between the type of the preset verification rule and the verification strategy, determine the verification strategy corresponding to the type of the verification rule, and adopt The verification strategy verifies the validity of the value of the parameter to be verified.

Wherein, the verification rule includes content of actual rules that the parameters to be verified need to comply with. Verification strategy is a general term for verification methods corresponding to various types of verification rules, that is, different verification methods are implemented for different verification rules. For example, verification rules include basic rules, function rules, application branch rules, When ignoring rules and other different types of rules, the verification strategy for branch rules is to judge whether the value of the parameter to be verified reaches the verification index, and then verify the parameter to be verified according to the judgment result. The corresponding relationship between the type of verification rule and the verification strategy can be pre-built and saved by the terminal, so that the terminal can obtain each input to be verified by querying the corresponding relationship between the type of verification rule and the verification strategy. The verification policy corresponding to the type of verification rule corresponding to the verification parameter. The verification strategy can be implemented using corresponding code segments, which can be called in actual use to verify the value of the parameter to be verified according to the corresponding verification strategy.

The steps described in this embodiment are aimed at the application environment where the ignored state of the parameter to be verified is a non-negligible state. Based on this, when the terminal obtains the verification rule corresponding to the parameter to be verified based on the foregoing steps, it can further determine the The type of the verification rule, and query the correspondence between the type of the pre-built verification rule and the verification strategy, find the verification strategy corresponding to the type of the verification rule, and then correspondingly according to the verification strategy The indicated check method checks the validity of the received value of the parameter to be checked.

Optionally, if the ignored state of the parameter to be verified is negligible, the validity of the value of the parameter to be verified is not checked directly, and the next step is to continue to judge whether the ignored state of the next parameter to be verified is not negligible , and then correspondingly execute subsequent steps according to the judgment result. For specific description, refer to the foregoing content, and details are not repeated here.

In practical applications, the above-mentioned different types of verification rules correspond to different verification strategies. When the types of verification rules are basic rules or application branch rules, in one embodiment, a specific implementation of the above-mentioned S202 is provided. That is, for the verification strategy corresponding to the above-mentioned types of verification rules, as shown in Figure 4, the "use the verification strategy to verify the validity of the value of the parameter to be verified" in the above S202 includes:

S301. Determine a verification index according to a verification rule corresponding to the parameter to be verified.

Wherein, the verification index is a verification index for verifying whether the value of the parameter to be verified is legal, that is, the verification index refers to a correct index corresponding to the parameter to be verified; the verification index includes a verification threshold range or a verification threshold. The verification threshold refers to the correct value corresponding to the parameter to be verified, and the verification threshold range refers to the correct value range corresponding to the parameter to be verified. In this embodiment, after the terminal determines the verification rule corresponding to the parameter to be verified, it can extract the verification index corresponding to the parameter to be verified from the verification rule, so as to determine the verification index corresponding to the verification index according to the verification index. Verify that the value of the parameter is legal.

S302, judging whether the value of the parameter to be verified reaches the verification index, if it reaches the verification index, execute step S303, and if it does not reach the verification index, execute step S304.

S303. Determine that the value of the parameter to be verified is legal.

S304. Determine that the value of the parameter to be verified is illegal.

After the terminal obtains the verification index and the value of the parameter to be verified, it can compare the value of the parameter to be verified with the verification index to determine whether the value of the parameter to be verified reaches the verification index. If it reaches the verification index, Indicates that the value of the parameter to be verified is legal, and then the parameter to be verified has passed the verification. If the verification index is not reached, it means that the value of the parameter to be verified is illegal, that is, the value of the parameter to be verified may be wrong when input at the front end , and then the parameter to be verified does not pass the verification, at this time, the terminal terminates the verification, and returns the result of the verification failure to the front-end, so that the front-end user re-inputs the value of the parameter to be verified for verification until the verification is passed.

Specifically, based on the above method, if the verification index includes the verification threshold range, after the terminal obtains the value of the parameter to be verified, it can check whether the value of the parameter to be verified falls within the verification threshold range. If it is within the verification threshold range, it means that the value of the parameter to be verified has reached the verification index. If it is not within the verification threshold range, it means that the value of the parameter to be verified has not reached the verification index; if the verification index includes When checking the threshold, when the terminal obtains the value of the parameter to be checked, it can compare whether the value of the parameter to be checked is the same as the check threshold. If they are the same, it means that the value of the parameter to be checked has reached the check index. Same, indicating that the value of the parameter to be verified has not reached the verification index. The verification threshold and the verification threshold range are determined by the terminal according to actual application requirements when editing the verification rules.

Further, when the type of the verification rule in the above embodiment is the application branch rule, the parameter verification method provided by the present application can also set the ignore state of the parameter to be verified. For example, based on the method described in the embodiment of FIG. 2, as shown in FIG. 5, the method further includes:

S401. Determine whether the parameter to be verified associated with the parameter to be verified is negligible according to the verification rule corresponding to the parameter to be verified and the value of the parameter to be verified.

Among them, the parameters to be verified associated with the parameters to be verified can be ignored, which means that the parameters to be verified associated with the parameters to be verified can be ignored when being verified, and the parameters to be verified associated with the parameters to be verified cannot be ignored. Indicates that the parameter to be verified associated with the parameter to be verified cannot be ignored when being verified. In practical applications, whether the parameter to be verified associated with the parameter to be verified can be ignored is determined by the value of the parameter to be verified. For example, if the value of the parameter A to be verified is 1, the parameter to be verified associated with the parameter to be verified The verification parameter B can be ignored, and the parameter C to be verified associated with the parameter to be verified cannot be ignored; if the value of the parameter to be verified is 2, the parameter B to be verified associated with the parameter to be verified Then it cannot be ignored, and the parameter C to be verified associated with the parameter to be verified can be ignored. The corresponding relationship between the value of the parameter to be verified and the ignored state of the associated parameter may be determined by a verification rule. The parameter to be verified associated with the value of the parameter to be verified can be one or more, which is determined by the attribute of the parameter to be verified.

In this embodiment, after the terminal obtains the value of the parameter to be checked, it can query the verification rule, find out which parameters to be checked are associated with the parameter to be checked, and further according to the value of the parameter to be checked, go to Determine which associated parameters to be verified can be ignored for verification, and which associated parameters to be verified cannot be ignored for verification.

S402. If the parameter to be verified associated with the parameter to be verified is negligible, set the ignore state of the parameter to be verified associated with the parameter to be verified to an ignorable state.

By querying the verification rules, when it is determined that the parameters to be verified associated with the parameters to be verified are negligible parameters to be verified, the terminal can set the ignore flag The ignore state is set to the ignore state, so that when the terminal needs to verify the associated parameters to be verified, the verification operation will not be performed, thereby improving the verification efficiency of the overall project. However, when it is determined that the parameter to be verified associated with the parameter to be verified is a non-negligible parameter to be verified, no operation is performed. For example, if the value of parameter A to be verified is 1, the parameters to be verified associated with the parameter to be verified include parameter B to be verified and parameter C to be verified. By querying the verification rules, it is found that when the parameter to be verified When the value of A is 1, the corresponding associated parameter B to be verified is negligible, while the parameter C to be verified is non-negligible, then the terminal sets the ignore status flag bit of the parameter B to be verified to 0, indicating that it is to be verified The parameter B can be ignored, so that the terminal does not need to verify the parameter B to be verified, thereby simplifying the verification step and improving the verification efficiency.

In practical applications, when the type of the verification rule is an application function rule, in one embodiment, a specific implementation of the above S202 is provided, that is, a verification strategy corresponding to the verification rule of the above type, as shown in FIG. 6 As shown, the "use a verification strategy to verify the validity of the value of the parameter to be verified" in the above S202 includes:

S501. Determine a function parameter that has a functional relationship with the parameter to be verified according to a verification rule corresponding to the parameter to be verified.

Wherein, give an example to illustrate the function parameters that are functionally related to the parameters to be verified. For example, if the parameter to be verified is C, then a functional relationship related to the parameters to be verified is: C>D, then D is the The test parameter C is a function parameter of a functional relationship. In this embodiment, after the terminal determines the verification rules corresponding to the parameters to be verified, it can extract various functional relationships related to the parameters to be verified from the verification rules, and the functional relationship with the parameters to be verified Various function parameters of , so that the value of the parameter to be verified can be verified according to the function parameter.

S502. Obtain the value of the function parameter from the received values of the plurality of parameters to be verified.

Since the multiple parameters to be verified will include function parameters, when the terminal obtains a function parameter or multiple function parameters that are functionally related to the parameters to be verified, it can further receive the multiple parameters to be verified from the front end. The value of the function parameter is found in the value of the test parameter. For example, a plurality of parameters to be verified include a parameter to be verified C and a parameter to be verified D, since there is a functional relationship between C and D (C>D), that is, the parameter D to be verified is a function of the parameter C to be verified parameters, then, if the front end receives the value of the parameter C to be verified and the value of the parameter D to be verified, the terminal can use the value of the parameter D to be verified as the value of the function parameter of the parameter C to be verified as a function .

S503. Substituting the value of the function parameter and the value of the parameter to be verified into the function relationship for calculation, and performing a legality check on the value of the parameter to be verified according to the calculation result.

When the terminal obtains the value of the function parameter and the value of the parameter to be verified based on the foregoing steps, it can substitute the value of the function parameter and the value of the parameter to be verified into the function relationship for calculation, obtain the calculation result, and then determine whether the calculation result is correct, or whether the calculation result conforms to the logical relationship presented by the functional relationship, if the calculation result is correct, or if the calculation result conforms to the logical relationship presented by the functional relationship, then it is determined that the value of the parameter to be verified is legal; if the calculation result is incorrect, Or the calculation result does not conform to the logical relationship presented by the functional relationship, then it is determined that the value of the parameter to be verified is illegal. To illustrate, for example, the parameter to be verified is C, and a functional relationship related to the parameter C to be verified is: C>D, then D is a function parameter that has a functional relationship with the parameter C to be verified. In one application, assuming that the terminal obtains C=5, and D=4, then 5>4, that is, conforms to the functional relationship C>D, then proves that the value of the parameter C to be verified (C=5) is legal . In another application, assuming that the terminal obtains C=2 and D=3, then 2<3, that is, does not meet the functional relationship C>D, then it is proved that the value of the parameter C to be verified (C=2) is Unlawful.

Further, when the type of the verification rule is an application function rule, the parameter verification method provided by the present application can also set the ignore state of the parameter to be verified. For example, based on the method described in the embodiment of FIG. 6, as shown in FIG. 7, the method further includes:

S601. Determine whether the ignored state of the function parameter is negligible. If the ignored state of the function parameter is ignored, execute step S602. If the ignored state of the function parameter is non-ignorable, execute step S603.

S602. Set the ignoring state of the parameter to be verified as an ignorable state.

S603. Keep the ignored state of the parameter to be verified as the current ignored state.

When the terminal obtains the function parameters that are functionally related to the parameters to be verified, it can further judge whether the ignore status of the function parameters is the ignore status by checking the ignore flag of the function parameters, if the ignore status of the function parameters is the ignore status , it means that the change of the function parameter will not have any impact on the development of the project, then the change of the parameter to be verified that is functionally related to the function parameter will not have any impact on the development of the project. In this case, The parameters to be verified that are functionally related to the function parameters can be set as negligible. For example, as in the above example, C is the parameter to be verified, and D is the function parameter that is functionally related to C. If D's current If the ignore flag bit is set to 1 (assuming that 1 indicates that the ignore state of D is negligible), then the corresponding ignore flag bit of C is also set to 1, indicating that the ignore state of C is set to be ignored.

If the ignore status of the function parameter is non-negligible, it means that the change of the function parameter will have an impact on the development of the project, and then the change of the parameter to be verified that is functionally related to the function parameter will naturally also have an impact on the development of the project , in this case, keep the ignored state of the parameter to be verified as the current ignored state, that is, do not reset the ignored state of the parameter to be verified, and set the ignored state of the parameter to be verified to be ignored originally. The ignoring state of the parameter to be verified is a negligible state. If the ignoring state of the parameter to be verified is originally a non-negligible state, the ignoring state of the parameter to be verified is also set to a non-negligible state. For example, as in the above example, if the current ignore flag of D is set to 0 (assuming that 0 indicates that the ignore state of D is not negligible), then the current ignore flag of C is maintained.

In practical applications, when the type of the verification rule corresponding to the parameter to be verified is an application ignore rule, in one embodiment, a specific implementation of the above S202 is provided, that is, the above step S202 "use the verification strategy to be verified Verifying the validity of the value of the parameter" specifically includes: not performing a legality verification on the value of the parameter to be verified, and setting the ignore state of the parameter to be verified to an ignorable state.

When the type of the verification rule corresponding to a parameter to be verified determined by the terminal is the application ignore rule, it means that the change of the verification parameter will not have any impact on the development of the project, so the verification parameter does not need to be verified. In this scenario, the terminal does not verify the validity of the value of the parameter to be verified, and sets the ignore state of the parameter to be verified to an ignorable state, so that when the terminal receives the value of the parameter to be verified, it directly ignores the value of the parameter to be verified. When the parameter to be verified is reached, there is no need to waste resources to verify the verification parameter, and in the case of effective use of resources, the efficiency of parameter verification by the terminal is improved.

The above-mentioned embodiment is a parameter verification method on the terminal side, and the present application also provides a parameter verification method on the front-end device side. The following embodiments illustrate the parameter verification method on the front-end device side.

In one embodiment, as shown in FIG. 8 , a parameter verification method is provided. The method is applied to the front-end equipment in FIG. 1 as an example, including the following steps:

S701. Obtain the value of the parameter to be verified input by the user on the verification interface.

Among them, users can be clinical engineers or technical developers. The verification interface can include multiple input interfaces corresponding to the values of the parameters to be verified. The user can input the value of the parameter to be verified by editing text on the input interface corresponding to the value of each parameter to be verified, or through Input the value of the parameter to be verified in other ways, which is not limited here. In this embodiment, the front-end device displays a verification interface, and the user can input the value of the parameter to be verified on the verification interface of the front-end device, and the front-end device can obtain the value of the parameter to be verified according to the user's input operation. Optionally, the user can also directly view the verification result returned by the terminal after verifying the validity of the value of the input parameter to be verified on the verification interface, and then follow up the verification process in time to find verification errors and correct them. The correction greatly improved the verification efficiency.

S702, carry the value of the parameter to be verified in the parameter verification request and send it to the terminal, so as to instruct the terminal to perform legality verification on the value of the parameter to be verified according to the correspondence between the preset verification parameter and the verification rule , get the verification result.

When the front-end device obtains the value of the parameter to be verified input by the user on the verification interface based on the aforementioned steps, it can further carry the value of the parameter to be verified in the parameter verification request and send it to the terminal, and the terminal receives the After the parameter verification request, the value of the parameter to be verified in the parameter verification request is further verified. The process of verifying the value of the parameter to be verified by the terminal is described in the aforementioned embodiments of Figures 2-7 There are instructions, please refer to the above description for details, and will not repeat them here.

Combining all the above embodiments, the present application also provides a parameter verification method, which involves the process of data interaction between the front-end device and the terminal, as shown in Figure 9, the method includes:

S801. The front-end device acquires the value of the parameter to be verified input by the user on the verification interface.

S802. The front-end device carries the value of the parameter to be verified in the parameter verification request and sends it to the terminal.

S803. The terminal receives a parameter verification request; the parameter verification request includes values of multiple parameters to be verified.

S804. The terminal acquires a verification rule corresponding to each parameter to be verified according to the preset correspondence between the verification parameter and the verification rule.

S805, the terminal judges whether the ignored state of each parameter to be verified is a non-negligible state, if the ignored state of the parameter to be verified is a non-negligible state, then perform step S806, if the ignored state of the parameter to be verified is a negligible state, Then execute step S817.

S806. According to the correspondence between the type of the preset verification rule and the verification strategy, determine the verification strategy corresponding to the type of the verification rule, and use the verification strategy to verify the validity of the value of the parameter to be verified. .

S807, determine the type of each verification rule, if the type of the verification rule is a basic rule or an application branch rule, then perform steps S808-S811, if the type of the verification item rule is an application function rule, then perform steps S812-S815 , if the type of the check item rule is an application ignore rule, step S817 is performed.

S808. Determine a verification index according to a verification rule corresponding to the parameter to be verified.

S809, judging whether the value of the parameter to be verified reaches the verification index, if the value of the parameter to be verified is reached, it is determined that the value of the parameter to be verified is legal; if the value of the parameter to be verified is not reached, it is determined that the value of the parameter to be verified is illegal.

S810. Determine whether the parameter to be verified associated with the parameter to be verified is negligible according to the verification rule corresponding to the parameter to be verified and the value of the parameter to be verified.

S811. If the parameter to be verified associated with the parameter to be verified is negligible, set the ignore state of the parameter to be verified associated with the parameter to be verified to an ignorable state.

S812. Determine a function parameter that has a functional relationship with the parameter to be verified according to a verification rule corresponding to the parameter to be verified.

S813. Obtain the value of the function parameter from the received values of the plurality of parameters to be verified.

S814, Substituting the value of the function parameter and the value of the parameter to be verified into the functional relationship for calculation, obtaining the calculation result, determining whether the calculation result is correct, or whether the calculation result conforms to the logical relationship presented by the functional relationship, if the calculation result is correct , or the calculation result conforms to the logical relationship presented by the functional relationship, then it is determined that the value of the parameter to be verified is legal; if the calculation result is incorrect, or the calculation result does not conform to the logical relationship presented by the functional relationship, then determine the value of the parameter to be verified The value of is illegal.

S815, judging whether the ignored state of the function parameter is a negligible state, if the ignored state of the function parameter is a negligible state, then setting the ignored state of the parameter to be verified as a negligible state; if the ignored state of the function parameter is a non-negligible state , then keep the ignore state of the parameter to be verified as the current ignore state.

S816. Do not perform legality verification on the value of the parameter to be verified, and set the ignore state of the parameter to be verified to an ignorable state.

S817, Do not perform validity check on the value of the parameter to be checked.

S818, when the verification result obtained by the terminal includes the parameter to be verified whose value is illegal, the terminal returns the illegal parameter to be verified to the front-end device to instruct the front-end device to view and/or modify the illegality The parameters to be verified.

The above-mentioned steps are all described in the above-mentioned embodiments. For details, please refer to the above-mentioned description, and details are not repeated here.

It should be understood that although the various steps in the flow charts in FIGS. 2-9 are shown sequentially as indicated by the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least some of the steps in Figures 2-9 may include multiple steps or stages, these steps or stages are not necessarily executed at the same time, but may be executed at different moments, the execution of these steps or stages The sequence is not necessarily performed sequentially, but may be performed alternately or alternately with other steps or at least a part of steps or stages in other steps.

In one embodiment, as shown in Figure 10, a parameter verification device is provided, including:

The receiving module 11 is configured to receive a parameter verification request; the parameter verification request includes a plurality of values of parameters to be verified;

The obtaining module 12 is used to obtain the verification rules corresponding to each of the parameters to be verified according to the correspondence between the preset verification parameters and the verification rules;

The checking module 13 is configured to check the validity of each value of the parameter to be checked according to the type of each checking rule, and obtain a checking result.

In one embodiment, as shown in Figure 11, the verification module 13 includes:

A judging unit 131, configured to judge whether the ignored state of each parameter to be checked is a non-negligible state;

The verification unit 132 is configured to determine, according to the correspondence between the type of the verification rule and the verification strategy preset, when the ignored state of the parameter to be verified is the non-negligible state, determine the Verify the verification strategy corresponding to the type of the rule, and use the verification strategy to verify the validity of the value of the parameter to be verified.

In one embodiment, as shown in FIG. 12, when the type of the verification rule is a basic rule or an application branch rule, the verification unit 132 includes:

The first determining subunit 1321 is configured to determine a verification indicator according to a verification rule corresponding to the parameter to be verified;

The judging subunit 1322 is used to judge whether the value of the parameter to be verified reaches the verification index. If the value of the parameter to be verified reaches the verification index, then determine that the value of the parameter to be verified is legal. If the verification indicator is not used, it is determined that the value of the parameter to be verified is illegal.

In one embodiment, as shown in FIG. 13, when the type of the verification item rule is the application branch rule, the verification unit 132 further includes:

The second determining subunit 1323 is configured to determine whether the parameter to be verified associated with the parameter to be verified is negligible according to the verification rule corresponding to the parameter to be verified and the value of the parameter to be verified;

The setting subunit 1324 is configured to set the ignore state of the parameter to be verified associated with the parameter to be verified to an ignorable state if the parameter to be verified associated with the parameter to be verified is negligible.

In one embodiment, as shown in FIG. 14, when the type of the verification item rule is an application function rule, the verification unit 132 includes:

The third determining subunit 1325 is configured to determine a function parameter that has a functional relationship with the parameter to be verified according to the verification rule corresponding to the parameter to be verified;

An acquisition subunit 1326, configured to acquire the value of the function parameter from the received values of the multiple parameters to be verified;

Calculation subunit 1327, configured to substitute the value of the function parameter and the value of the parameter to be verified into the functional relationship for calculation, and check the validity of the value of the parameter to be verified according to the calculation result test.

In one embodiment, as shown in FIG. 15, the verification unit 132 further includes:

The second judging subunit 1328 is used to judge whether the ignored state of the function parameter is a negligible state;

The second setting subunit 1329 is configured to set the ignored state of the parameter to be verified as the ignored state if the ignored state of the function parameter is the ignored state.

In one embodiment, the verification unit 132 is specifically configured to not perform a legality verification on the value of the parameter to be verified when the type of the verification rule is an application ignore rule, and to check the validity of the value of the parameter to be verified The ignore status of the validation parameter is set to ignore status.

In one embodiment, as shown in FIG. 16, the above-mentioned parameter verification device further includes:

The return module 14 is configured to return the illegal parameters to be checked to the front-end equipment, so as to instruct the front-end equipment to view and/or modify the illegal parameters to be checked.

For specific limitations on the parameter verification device, refer to the above-mentioned limitations on the parameter verification method, which will not be repeated here. Each module in the above-mentioned parameter checking device can be fully or partially realized by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, and can also be stored in the memory of the computer device in the form of software, so that the processor can invoke and execute the corresponding operations of the above-mentioned modules.

In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure may be as shown in FIG. 17 . The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Wherein, the processor of the computer device is used to provide calculation and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, an operator network, NFC (Near Field Communication) or other technologies. When the computer program is executed by the processor, a parameter verification method is realized. The display screen of the computer device may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device may be a touch layer covered on the display screen, or a button, a trackball or a touch pad provided on the casing of the computer device , and can also be an external keyboard, touchpad, or mouse.

Those skilled in the art can understand that the structure shown in Figure 17 is only a block diagram of a partial structure related to the solution of this application, and does not constitute a limitation on the computer equipment on which the solution of this application is applied. The specific computer equipment can be More or fewer components than shown in the figures may be included, or some components may be combined, or have a different arrangement of components.

In one embodiment, a computer device is provided, including a memory and a processor, a computer program is stored in the memory, and the processor implements the following steps when executing the computer program:

Receive a parameter verification request; the parameter verification request includes the values of multiple parameters to be verified;

Acquiring a verification rule corresponding to each of the parameters to be verified according to the preset correspondence between the verification parameter and the verification rule;

According to the type of each verification rule, the validity of each value of the parameter to be verified is verified to obtain a verification result.

The implementation principle and technical effect of the computer device provided in the foregoing embodiments are similar to those of the foregoing method embodiments, and will not be repeated here.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

Receive a parameter verification request; the parameter verification request includes the values of multiple parameters to be verified;

Acquiring a verification rule corresponding to each of the parameters to be verified according to the preset correspondence between the verification parameter and the verification rule;

According to the type of each verification rule, the validity of each value of the parameter to be verified is verified to obtain a verification result.

The implementation principle and technical effect of the computer-readable storage medium provided by the foregoing embodiments are similar to those of the foregoing method embodiments, and details are not repeated here.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented through computer programs to instruct related hardware, and the computer programs can be stored in a non-volatile computer-readable memory In the medium, when the computer program is executed, it may include the processes of the embodiments of the above-mentioned methods. Wherein, any references to memory, storage, database or other media used in the various embodiments provided in the present application may include at least one of non-volatile memory and volatile memory. The non-volatile memory may include read-only memory (Read-Only Memory, ROM), magnetic tape, floppy disk, flash memory or optical memory, and the like. Volatile memory may include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM).

The technical features of the above embodiments can be combined arbitrarily. To make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be It is considered to be within the range described in this specification.

The above-mentioned embodiments only represent several implementation modes of the present application, and the description thereof is relatively specific and detailed, but it should not be construed as limiting the scope of the patent for the invention. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the scope of protection of the patent application should be based on the appended claims.

Claims (10)

1. A parameter verification method, characterized in that the method comprises: Receive a parameter verification request; the parameter verification request includes the values of multiple parameters to be verified; Acquiring a verification rule corresponding to each of the parameters to be verified according to the preset correspondence between the verification parameter and the verification rule; Determine the corresponding verification method according to the type of each verification rule, and use the verification method corresponding to the type of each verification rule to perform a legality verification on the value of each parameter to be verified, A verification result is obtained; wherein, the types of the verification rules include basic rules, application branch rules, application function rules, and application ignore rules. 2. The method according to claim 1, wherein the corresponding verification method is determined according to the type of each verification rule, and the verification method corresponding to the type of each verification rule is adopted Perform a legality check on the value of each parameter to be checked to obtain a check result, including: judging whether the ignoring state of each parameter to be verified is a non-ignoring state; If the ignoring state of the parameter to be verified is the non-ignorable state, then according to the preset correspondence between the type of verification rule and the verification strategy, determine the verification corresponding to the type of the verification rule strategy, and use the verification strategy to verify the validity of the value of the parameter to be verified. 3. The method according to claim 2, wherein if the type of the verification rule is the basic rule or the application branch rule, then the adoption of the verification strategy for the The value of the parameter is checked for legality, including: determining a verification indicator according to a verification rule corresponding to the parameter to be verified; judging whether the value of the parameter to be verified reaches the verification index, if the verification index is reached, then determining that the value of the parameter to be verified is legal, if not reaching the verification index, then determining the The value of the parameter to be verified is illegal. 4. The method according to claim 3, wherein if the type of the verification rule is the application branch rule, the method further comprises: According to the verification rule corresponding to the parameter to be verified and the value of the parameter to be verified, determine whether the parameter to be verified associated with the parameter to be verified can be ignored; If the parameter to be verified associated with the parameter to be verified is negligible, then the ignore state of the parameter to be verified associated with the parameter to be verified is set to an ignorable state. 5. The method according to claim 2, wherein if the type of the verification rule is the application function rule, then the use of the verification strategy to legalize the value of the parameter to be verified sex checks, including: According to the verification rule corresponding to the parameter to be verified, determine a function parameter that has a functional relationship with the parameter to be verified; Acquiring the value of the function parameter from the received values of the plurality of parameters to be verified; Substituting the value of the function parameter and the value of the parameter to be checked into the functional relationship for calculation, and performing a legality check on the value of the parameter to be checked according to the calculation result. 6. The method according to claim 5, further comprising: judging whether the ignored state of the function parameter is a negligible state; If the ignoring state of the function parameter is the ignorable state, then setting the ignoring state of the parameter to be verified as the ignorable state. 7. The method according to claim 2, wherein if the type of the verification rule is the application ignore rule, then the verification strategy is used to legalize the value of the parameter to be verified. sex checks, including: The validity check is not performed on the value of the parameter to be checked, and the ignoring state of the parameter to be checked is set to an ignorable state. 8. The method according to claim 1, wherein if the verification result is that the parameter to be verified is an illegal parameter to be verified, the method further comprises: Returning the illegal parameters to be checked to the front-end device, so as to instruct the front-end device to view and/or modify the illegal parameters to be checked. 9. A computer device, comprising a memory and a processor, the memory stores a computer program, wherein the processor implements the steps of the method according to any one of claims 1 to 8 when executing the computer program . 10. A computer-readable storage medium, on which a computer program is stored, wherein, when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images