CN113535553A - Parameter checking method, computer device and storage medium - Google Patents
Parameter checking method, computer device and storage medium Download PDFInfo
- Publication number
- CN113535553A CN113535553A CN202110741754.2A CN202110741754A CN113535553A CN 113535553 A CN113535553 A CN 113535553A CN 202110741754 A CN202110741754 A CN 202110741754A CN 113535553 A CN113535553 A CN 113535553A
- Authority
- CN
- China
- Prior art keywords
- parameter
- verified
- verification
- value
- rule
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
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 at 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 modified again.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a parameter verification method, a computer device, and a storage medium.
Background
Digital Subtraction Angiography (DSA) is used for inputting two frames of X-ray images taken before and after the injection of a contrast agent into a computer device through digitization, and bone and soft tissue images on an angiographic image are eliminated through subtraction, enhancement and re-imaging processes to obtain a clear pure blood vessel image, so that the DSA is an examination method combining an electronic computer and conventional X-ray angiography.
In the control flow of contrast imaging using a DSA apparatus, the DSA system is a crucial part of the process of verifying the parameter information of the front end. At present, after a clinical engineer inputs parameter information related to a control flow, such as parameter data content, parameter threshold values, rule constraints, and the like, at a front end, in a development process of a back-end control flow, a research and development engineer needs to design a corresponding rule check code for each parameter information, and then perform parameter check on each parameter information by using the designed rule check code, so that accuracy of the parameter information is ensured, and normal operation of a DSA system is ensured.
However, if the required parameter information changes, a research and development engineer needs to redesign the rule verification code corresponding to the relevant parameter information, and then the redesigned rule verification code is used to verify the parameter information, so that the verification method has the problem of low verification efficiency.
Disclosure of Invention
In view of the above, there is a need to provide a parameter verification method, a computer device and a storage medium, which can effectively improve the verification efficiency.
In a first aspect, a method for parameter verification, the method comprising:
receiving a parameter checking request; the parameter checking request comprises a plurality of values of parameters to be checked;
acquiring a calibration rule corresponding to each parameter to be calibrated according to a corresponding relation between preset calibration parameters and calibration rules;
and carrying out validity check on the value of each parameter to be checked according to the type of each check rule to obtain a check result.
In one embodiment, the performing, according to the type of each check rule, validity check on the value of each parameter to be checked to obtain a check result includes:
judging whether the neglected state of each parameter to be checked is a non-neglected state;
if the neglected state of the parameter to be verified is the non-neglected state, determining a verification strategy corresponding to the type of the verification rule according to the corresponding relation between the type of the preset verification rule and the verification strategy, and performing validity verification on the value of the parameter to be verified by adopting the verification strategy.
In one embodiment, if the type of the check rule is a basic rule or an application branch rule, the performing validity check on the value of the parameter to be checked by using the check policy includes:
determining a verification index according to a verification rule corresponding to the parameter to be verified;
and judging whether the value of the parameter to be checked reaches the check index, if so, determining that the value of the parameter to be checked is legal, and if not, determining that the value of the parameter to be checked is illegal.
In one embodiment, if the type of the check term rule is the application branch rule, the method further includes:
determining whether the parameter to be verified associated with the parameter to be verified can be ignored or not according to a verification rule corresponding to the parameter to be verified and the value of the parameter to be verified;
and if the parameter to be verified associated with the parameter to be verified is negligible, setting the neglected state of the parameter to be verified associated with the parameter to be verified as a negligible state.
In one embodiment, if the type of the check item rule is an application function rule, the performing validity check on the value of the parameter to be checked by using the check policy includes:
determining a function parameter in a functional relationship with the parameter to be verified according to a verification rule corresponding to the parameter to be verified;
obtaining the value of the function parameter from the received values of a plurality of parameters to be checked;
and substituting the value of the function parameter and the value of the parameter to be verified into the function relationship for calculation, and performing validity verification on the value of the parameter to be verified according to the calculation result.
In one embodiment, the method further comprises:
judging whether the neglected state of the function parameter is a neglected state;
and if the neglected state of the function parameter is the neglected state, setting the neglected state of the parameter to be verified as the neglected state.
In one embodiment, if the type of the check rule is an application omission rule, the performing validity check on the value of the parameter to be checked by using the check policy includes:
and not carrying out validity check on the value of the parameter to be checked, and setting the neglected state of the parameter to be checked as a neglected state.
In one embodiment, if the verification result is that the parameter to be verified is an illegal parameter to be verified, the method further includes:
and returning the illegal parameters to be checked to the front-end equipment to indicate the front-end equipment to check and/or modify the illegal parameters to be checked.
In a second aspect, a computer device comprises a memory and a processor, the memory storing a computer program, the processor implementing the method of the first aspect when executing the computer program.
In a third aspect, a computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method of the first aspect described above.
According to the parameter verification method, the computer equipment and the storage medium, the parameter verification request comprising the values of the parameters to be verified is received, the verification rules corresponding to the parameters to be verified are obtained according to the preset corresponding relation between the verification parameters and the verification rules, and then the legality of the value of each parameter to be verified is verified according to the type of each verification rule, so that the verification result is obtained. 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 at 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 modified again.
Drawings
FIG. 1 is a schematic diagram of an embodiment of an application system;
FIG. 2 is a flow chart illustrating a method for verifying parameters according to an embodiment;
FIG. 3 is a flowchart illustrating an implementation manner of S103 in the embodiment of FIG. 2;
FIG. 4 is a flowchart illustrating an implementation manner of S202 in the embodiment of FIG. 3;
FIG. 5 is a flow chart illustrating a method for verifying parameters according to an embodiment;
FIG. 6 is a flowchart illustrating an implementation manner of S202 in the embodiment of FIG. 3;
FIG. 7 is a flowchart illustrating a method for verifying parameters according to an embodiment;
FIG. 8 is a flowchart illustrating a method for verifying parameters according to an embodiment;
FIG. 9 is a flowchart illustrating a method for verifying parameters according to an embodiment;
FIG. 10 is a block diagram showing the construction of a parameter verifying apparatus according to an embodiment;
FIG. 11 is a block diagram showing the construction of a parameter verifying apparatus according to an embodiment;
FIG. 12 is a block diagram showing the construction of a parameter verifying apparatus according to an embodiment;
FIG. 13 is a block diagram showing the construction of a parameter verifying apparatus according to an embodiment;
FIG. 14 is a block diagram showing the construction of a parameter verifying apparatus according to an embodiment;
FIG. 15 is a block diagram showing the construction of a parameter verifying apparatus according to an embodiment;
FIG. 16 is a block diagram showing the construction of a parameter verifying apparatus according to an embodiment;
FIG. 17 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The parameter verification method provided by the present application may be applied to an application system as shown in fig. 1, where the system includes a front-end device 110 and a terminal 120, and the front-end device 110 and the terminal 120 may be connected in a wired or wireless manner. The front-end device 110 and the terminal 120 implement parameter verification through data interaction. A user (including an engineer) may input a value of a parameter to be verified on the front-end device 110, the front-end device 110 sends a message carrying the value of the parameter to be verified to the terminal 120, the terminal 120 verifies the value of the parameter to be verified, and then a verification result is returned to the front-end device 110. The front-end device 110 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the terminal 120 may be implemented by an independent server or a server cluster composed of a plurality of servers.
Those skilled in the art will appreciate that the architecture shown in fig. 1 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the applications to which the disclosed aspects may be applied, and that a particular application may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In an embodiment, as shown in fig. 2, a parameter checking method is provided, which is described by taking the method as an example applied to the terminal in fig. 1, and includes the following steps:
s101, receiving a parameter checking request; the parameter checking request comprises a plurality of values of the parameters to be checked.
The parameters to be verified are related parameters which are input by a clinical engineer and other demanders on the front-end equipment and are used for controlling the terminal to perform corresponding acquisition operation. For example, the parameters to be verified may include: frame frequency data, acquisition type, acquisition mode, high voltage parameters and the like. The value of the parameter to be verified may represent a value of the parameter to be verified, a value range of the parameter to be verified, or an identifier of the parameter to be verified. The parameter verification request is a request message sent by the front-end equipment to the terminal after the value of the parameter to be verified is input by the clinical engineer on the front-end equipment.
Specifically, the clinical engineer may select a suitable value of the parameter to be verified on a display operation interface of the front-end device, edit and input the value to the front-end device, and after the front-end device acquires the value of the parameter to be verified, encapsulate the value in a parameter verification request and send the parameter verification request to the terminal, so as 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 executes a corresponding acquisition operation according to the acquisition method set by the clinical engineer.
S102, acquiring a calibration rule corresponding to each parameter to be calibrated according to the corresponding relation between the preset calibration parameter and the calibration rule.
The corresponding relationship between the verification parameters and the verification rules can be pre-established and stored by the terminal, so that the terminal can obtain the verification rules corresponding to each input parameter to be verified by inquiring the corresponding relationship between the verification parameters and the verification rules. For example, the terminal may record a correspondence between a pre-constructed verification parameter and a verification rule in a parameter information table, store the parameter information table, and then read data in the parameter information table to obtain desired information when the terminal queries the information.
Specifically, when the terminal receives the parameter verification request based on the foregoing steps, the parameter to be verified can be extracted from the parameter verification request, the correspondence between the pre-established verification parameter and the verification rule is queried, and the verification rule corresponding to the parameter to be verified is found. Specifically, during the query, the terminal may query the parameter information table recorded with the correspondence between the verification parameters and the verification rules, and search for the verification rules corresponding to the parameters to be verified from the parameter information table for later use.
S103, according to the type of each check rule, carrying out validity check on the value of each parameter to be checked to obtain a check result.
The types of the check rules comprise basic rules, application branch rules, application function rules and application ignore rules. Different types of verification rules correspond to different verification methods. The correspondence between the type of the verification rule and the verification method may be determined in advance by the terminal and stored. Specifically, when the terminal acquires the verification rule corresponding to each parameter to be verified, the type of each verification rule may be further analyzed, and the corresponding verification method is determined according to the type of each verification rule, and then the verification method corresponding to the type of each verification rule may be adopted to perform validity verification on the value of each parameter to be verified, so as to obtain a verification result that the value of the parameter to be verified is a valid parameter to be verified or an invalid parameter to be verified.
The parameter verification method disclosed in the above embodiment receives a parameter verification request including values of a plurality of parameters to be verified, obtains a verification rule corresponding to each parameter to be verified according to a preset correspondence between the verification parameter and the verification rule, and performs 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 value of 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 modified again.
In practical application, 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, after the terminal performs step S103, the terminal further performs the following steps: and returning the illegal parameters to be checked to the front-end equipment to indicate the front-end equipment to check and/or modify the illegal parameters to be checked.
When the obtained verification result of the terminal is that the value of the parameter to be verified is an illegal parameter to be verified, it indicates that the verification does not pass, and the value of the parameter to be verified is problematic, and it may be that a front-end engineer wrongly inputs the value of the parameter to be verified when editing the value of the parameter to be verified, or the value of the parameter to be verified is wrong due to other reasons. Compared with the traditional verification process that an error occurs, the method only can return the code segment by the engineering personnel and modify the verification parameters in a code modification mode, the verification process is more efficient, the difficulty of the engineering personnel in modifying the verification parameters can be reduced, and the labor cost can be saved. Correspondingly, when the verification result obtained by the terminal is that the value of the parameter to be verified is the legal parameter to be verified, the verification is passed, in this case, the terminal can also transmit the verification passing message to the front end, so that the front end engineering personnel can also know the verification condition of each parameter to be verified by the terminal.
In an embodiment, a specific implementation manner of the foregoing S103 is provided, as shown in fig. 3, where the foregoing S103 "performs validity check on the value of each parameter to be checked according to the type of each check rule to obtain a check result", includes:
s201, judging whether the neglected state of each parameter to be checked is a non-neglected state.
The neglect state of the parameter to be verified comprises a neglect state and a non-neglect state. When the neglected state of the parameter to be verified is a non-neglected state, it is indicated that the parameter to be verified needs to be verified, and when the neglected state of the parameter to be verified is a neglected state, it is indicated that the change of the parameter to be verified does not have any influence on the development of the project, so that the parameter to be verified does not need to be verified. Therefore, before the terminal performs the validity check on each parameter to be checked, the neglected state of each parameter to be checked is judged, and then whether the parameter to be checked is subjected to the validity check is determined based on different judgment results, so that the validity check does not need to be performed on each parameter to be checked, and the checking efficiency can be greatly improved. It should be noted that, in determining whether the ignoring state of the parameter to be verified is the non-ignoring state, it may be determined by looking at the ignoring flag bit of the parameter to be verified, for example, if the ignoring flag bit of one parameter to be verified is set to 1, the ignoring state of the parameter to be verified is considered to be the ignoring state, and if the ignoring flag bit of one parameter to be verified is set to 0, the ignoring state of the parameter to be verified is considered to be the non-ignoring state.
S202, if the neglected state of the parameter to be verified is the non-neglected state, determining a verification strategy corresponding to the type of the verification rule according to the corresponding relation between the type of the preset verification rule and the verification strategy, and performing validity verification on the value of the parameter to be verified by adopting the verification strategy.
The verification rule comprises the content of an actual rule which needs to be met by the parameter to be verified. The verification policy is a generic name of the verification methods corresponding to various types of verification rules, that is, different verification methods executed for different verification rules, for example, when the verification rules include different types of rules such as a basic rule, a function rule, an application branch rule, an ignore rule, and the like, the verification policy for the branch rule is a method for determining whether the value of the parameter to be verified reaches the verification index, and then verifying the parameter to be verified according to the determination result. The corresponding relationship between the type of the verification rule and the verification policy may be pre-established and stored by the terminal, so that the terminal may obtain the verification policy corresponding to the type of the verification rule corresponding to each input parameter to be verified by querying the corresponding relationship between the type of the verification rule and the verification policy. The verification strategy can be realized by using a corresponding code segment, and the value of the parameter to be verified can be verified by calling the corresponding verification strategy in actual use.
The step described in this embodiment is directed to an application environment in which the neglected state of the parameter to be verified is the non-ignorable state, and based on this, when the terminal obtains the verification rule corresponding to the parameter to be verified based on the foregoing step, the type of the verification rule may be further determined, the correspondence between the type of the pre-established verification rule and the verification policy is queried, the verification policy corresponding to the type of the verification rule is found, and then the validity of the received value of the parameter to be verified is verified according to the verification method indicated in the verification policy.
Optionally, if the neglected state of the parameter to be verified is the neglected state, the validity of the value of the parameter to be verified is not directly verified, and whether the neglected state of the next parameter to be verified is the non-ignorable state is continuously determined, and then the subsequent steps are executed according to the determination result.
In practical application, the different types of the check rules correspond to different check policies, and when the type of the check rule is a basic rule or an application branch rule, in an embodiment, a specific implementation manner of the S202 is provided, that is, for the check policy corresponding to the type of the check rule, as shown in fig. 4, the "performing validity check on the value of the parameter to be checked by using the check policy" in the S202 includes:
s301, determining a verification index according to a verification rule corresponding to the parameter to be verified.
The verification index is used for verifying whether the value of the parameter to be verified is legal or not, namely the verification index is a correct index corresponding to the parameter to be verified; the check index includes a check threshold range or a check threshold. The check threshold value refers to a correct value range corresponding to the parameter to be checked if the parameter to be checked corresponds to the correct value range. In this embodiment, after the terminal determines the check rule corresponding to the parameter to be checked, the check index corresponding to the parameter to be checked may be extracted from the check rule, so as to determine whether the value of the parameter to be checked is legal according to the check index.
S302, judging whether the value of the parameter to be verified reaches the verification index, if so, executing step S303, and if not, executing step S304.
S303, determining that the value of the parameter to be checked is legal.
S304, determining that the value of the parameter to be checked is illegal.
When the terminal obtains the check index and the value of the parameter to be checked, the value of the parameter to be checked can be compared with the check index, whether the value of the parameter to be checked reaches the check index or not is determined, if the value of the parameter to be checked reaches the check index, the value of the parameter to be checked is legal, the parameter to be checked is checked to pass, if the value of the parameter to be checked does not reach the check index, the value of the parameter to be checked is illegal, namely errors possibly occur when the value of the parameter to be checked is input at the front end, the parameter to be checked is not checked, the terminal stops checking at the moment, the result of the check failure is returned to the front end, and the front end user inputs the value of the parameter to be checked again for checking until the check 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 may check whether the value of the parameter to be verified falls within the verification threshold range, if so, it indicates that the value of the parameter to be verified reaches the verification index, and if not, it indicates that the value of the parameter to be verified does not reach the verification index; if the check index comprises the check threshold, after the terminal obtains the value of the parameter to be checked, whether the value of the parameter to be checked is the same as the check threshold or not can be compared, if so, the value of the parameter to be checked reaches the check index, and if not, the value of the parameter to be checked does not reach the check index. The verification threshold value and the verification threshold value range are determined by the terminal according to actual application requirements when the verification rule is edited.
Further, when the type of the verification rule in the above embodiment is an application of a branch rule, the parameter verification method provided by the present application may further set an ignoring 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, determining whether the parameter to be verified related to the parameter to be verified can be ignored or not according to the verification rule corresponding to the parameter to be verified and the value of the parameter to be verified.
The parameter to be verified associated with the parameter to be verified is negligible, which means that the parameter to be verified associated with the parameter to be verified can be verified in a negligible manner when being verified, and the parameter to be verified associated with the parameter to be verified is non-negligible, which means that the parameter to be verified associated with the parameter to be verified can not be verified in a negligible manner when being verified. In practical application, 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 to be verified a is 1, the parameter to be verified B associated with the parameter to be verified can be ignored, and the parameter to be verified C associated with the parameter to be verified can not be ignored; if the value of the parameter to be verified is 2, the parameter to be verified B associated with the parameter to be verified is not negligible, and the parameter to be verified C associated with the parameter to be verified is negligible. The correspondence 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 number of the parameters to be checked related to the value of the parameter to be checked may be one or more, and is determined by the attribute of the parameter to be checked.
In this embodiment, after the terminal obtains the value of the parameter to be checked, the check rule may be queried to find out which parameters to be checked are associated with the parameter to be checked, and then, according to the value of the parameter to be checked, it is further determined which associated parameters to be checked can be checked to be ignored, and which associated parameters to be checked can not be checked to be ignored.
S402, if the parameter to be verified related to the parameter to be verified is negligible, setting the neglected state of the parameter to be verified related to the parameter to be verified to be a negligible state.
By inquiring the verification rule, when the parameter to be verified associated with the parameter to be verified is determined to be a negligible parameter to be verified, the terminal can set the neglected state of the parameter to be verified associated with the parameter to be verified to be a negligible state by setting the neglected flag bit, so that the terminal does not execute the verification operation when the associated parameter to be verified needs to be verified later, and the verification efficiency of the whole project is improved. And when the parameter to be verified associated with the parameter to be verified is determined to be the non-negligible parameter to be verified, no operation is executed. 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 includes a parameter B to be verified and a parameter C to be verified, and by querying the verification rule, it is found that when the value of the verification parameter a is 1, the corresponding associated parameter B to be verified is negligible, and the parameter C to be verified is non-negligible, the terminal sets the ignore status flag bit of the parameter B to be verified to be 0, which indicates that the parameter B to be verified is negligible, so that the terminal does not verify the parameter B to be verified later, thereby simplifying the verification step and further improving the verification efficiency.
In practical application, when the type of the check rule is an application function rule, in an embodiment, a specific implementation manner of the foregoing S202 is provided, that is, for a check policy corresponding to the check rule of the foregoing type, as shown in fig. 6, the "performing validity check on the value of the parameter to be checked by using the check policy" in the foregoing S202 includes:
s501, determining a function parameter in a functional relation with the parameter to be verified according to a verification rule corresponding to the parameter to be verified.
For example, if the parameter to be verified is C, then one function relationship related to the parameter to be verified is: and C is greater than D, and D is the function parameter in the functional relation with the parameter C to be verified. In this embodiment, after the terminal determines the calibration rule corresponding to the parameter to be calibrated, various functional relationships related to the parameter to be calibrated and various functional parameters in functional relationships with the parameter to be calibrated can be extracted from the calibration rule, so that the value of the parameter to be calibrated can be calibrated according to the functional parameters.
S502, obtaining the value of the function parameter from the received values of the plurality of parameters to be checked.
Since the plurality of parameters to be verified include the function parameter, when the terminal acquires the function parameter or the plurality of function parameters in the functional relationship with the parameter to be verified, the value of the function parameter can be further found from the values of the plurality of parameters to be verified received from the front end. For example, the plurality of parameters to be verified include a parameter C to be verified and a parameter D to be verified, and since C and D have a functional relationship (C > D), that is, the parameter D to be verified is a function parameter of the parameter C to be verified, 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 may use the value of the parameter D to be verified as the value of the function parameter of which the parameter C to be verified has the functional relationship.
And 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 validity verification 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 steps, the value of the function parameter and the value of the parameter to be verified can be substituted into the function relationship for calculation to obtain a calculation result, whether the calculation result is correct or not is determined, or whether the calculation result accords with the logic relationship presented by the function relationship, and if the calculation result is correct or the calculation result accords with the logic relationship presented by the function relationship, the value of the parameter to be verified is determined to be legal; and if the calculation result is incorrect or the calculation result does not conform to the logical relationship presented by the functional relationship, determining that the value of the parameter to be verified is illegal. For example, the parameter to be verified is C, and one function relationship related to the parameter to be verified is: c > D, and D is a function parameter in a functional relation with the parameter C to be verified. In one application, assuming that C is 5 and D is 4 acquired by the terminal, 5>4 is satisfied, that is, the functional relationship C > D is satisfied, and the value of the parameter C to be verified (C is 5) is proved to be legal. In another application, assuming that C is 2 and D is 3 acquired by the terminal, 2<3 is satisfied, that is, the functional relationship C > D is not satisfied, and the value of the parameter C to be verified (C is 2) is proved to be illegal.
Further, when the type of the verification rule is an application function rule, the parameter verification method provided by the application can also set the neglected 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, determining whether the ignoring state of the function parameter is an ignorable state, if the ignoring state of the function parameter is an ignorable state, executing step S602, and if the ignoring state of the function parameter is a non-ignorable state, executing step S603.
And S602, setting the neglected state of the parameter to be verified to be a neglected state.
S603, keeping the neglected state of the parameter to be checked as the current neglected state.
When the terminal acquires the function parameter in functional relationship with the parameter to be verified, it may further determine whether the ignoring state of the function parameter is an ignorable state by looking at the ignoring flag bit of the function parameter, and if the ignoring state of the function parameter is an ignorable state, it indicates that the change of the function parameter does not have any influence on the development of the project, and then the change of the parameter to be verified in functional relationship with the function parameter does not have any influence on the development of the project, in this case, the parameter to be verified in functional relationship with the function parameter may be set to be an ignorable state, for example, as in the above example, C is the parameter to be verified, D is the function parameter in functional relationship with C, and if the current ignoring flag bit of D is set to 1 (assuming that 1 indicates that the ignoring state of D is an ignorable state), the ignoring flag bit of C is also set to be 1 correspondingly, the ignore state, which represents C, is set to the ignore state.
If the neglected state of the function parameter is a non-neglected state, it is indicated that the change of the function parameter will affect the development of the project, and the change of the parameter to be verified which has a functional relationship with the function parameter will naturally affect the development of the project. For example, as in the example above, if the current ignore flag bit of D is set to 0 (assuming 0 indicates that the ignore state of D is a non-ignore state), then C is kept current ignore flag bit.
In practical application, when the type of the check rule corresponding to the parameter to be checked is an application omission rule, in an embodiment, a specific implementation manner of the step S202 is provided, that is, the step S202 "performing validity check on the value of the parameter to be checked by using a check policy" specifically includes: and carrying out no validity check on the value of the parameter to be checked, and setting the neglected state of the parameter to be checked to be a neglected state.
When the type of the check rule corresponding to one parameter to be checked determined by the terminal is an application omission rule, it is indicated that the change of the check parameter does not have any influence on the development of the project, so the check parameter does not need to be checked, in this scene, the terminal does not carry out legality check on the value of the parameter to be checked, and the neglected state of the parameter to be checked is set to be a neglected state, so that the parameter to be checked is directly ignored when the terminal receives the value of the parameter to be checked again later, resources do not need to be wasted to check the check parameter, and the efficiency of the terminal in carrying out parameter check is improved under the condition of effectively utilizing the resources.
The above embodiment is a parameter verification method at a terminal side, and the present application also provides a parameter verification method at a front-end device side.
In an embodiment, as shown in fig. 8, a parameter checking method is provided, which is described by taking the method as an example for being applied to the front-end device in fig. 1, and includes the following steps:
s701, acquiring the value of the parameter to be verified input by the user on the verification interface.
The user may be a clinical engineer or a technical developer. The verification interface may include an input interface corresponding to a plurality of values of the parameter to be verified, and the user may input the value of the parameter to be verified on the input interface corresponding to each value of the parameter to be verified in a text editing manner, or may input the value of the parameter to be verified in other manners, which is not limited herein. In this embodiment, the front-end device displays the verification interface, 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 acquire the value of the parameter to be verified according to the input operation of the user. Optionally, the user can also directly check the check result returned after the legitimacy check is performed on the value of the input parameter to be checked after the terminal is checked on the check interface, so that the check process is followed up in time, the check error is found and corrected, and the check efficiency is greatly improved.
S702, the value of the parameter to be verified is carried in the parameter verification request and sent to the terminal, so that the terminal is instructed to conduct validity verification on the value of the parameter to be verified according to the corresponding relation between the preset verification parameter and the verification rule, and a verification result is obtained.
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 foregoing steps, the value of the parameter to be verified may be further carried in the parameter verification request and sent to the terminal, and after the terminal receives the parameter verification request, the terminal further verifies the value of the parameter to be verified in the parameter verification request, the process of verifying the value of the parameter to be verified by the terminal is described in the foregoing embodiments of fig. 2 to 7, and for the details, refer to the foregoing description, which is not repeated herein.
With reference to all the above embodiments, the present application further provides a parameter checking method, which relates to a process of data interaction between a front-end device and a terminal, and as shown in fig. 9, the method includes:
s801, the front-end equipment acquires the value of the parameter to be verified, which is input by the user on the verification interface.
And S802, the front-end equipment carries the value of the parameter to be verified in the parameter verification request and sends the parameter to the terminal.
S803, the terminal receives the parameter checking request; the parameter checking request comprises a plurality of values of the parameters to be checked.
S804, the terminal obtains the verification rules corresponding to the parameters to be verified according to the corresponding relationship between the preset verification parameters and the verification rules.
S805, the terminal determines 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-ignoring state, then step S806 is executed, and if the ignoring state of the parameter to be verified is the ignoring state, then step S817 is executed.
S806, according to the corresponding relation between the type of the preset check rule and the check strategy, determining the check strategy corresponding to the type of the check rule, and performing validity check on the value of the parameter to be checked by adopting the check strategy.
S807, determining the type of each check rule, if the type of the check rule is a basic rule or an application branch rule, executing steps S808-S811, if the type of the check item rule is an application function rule, executing steps S812-S815, and if the type of the check item rule is an application ignore rule, executing step S817.
And S808, determining 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, and if so, determining that the value of the parameter to be verified is legal; and if the value does not reach the check index, determining that the value of the parameter to be checked is illegal.
And S810, determining whether the parameter to be verified related to the parameter to be verified can be ignored or not 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, setting the negligible state of the parameter to be verified associated with the parameter to be verified as the negligible state.
S812, determining a function parameter in a functional relationship with the parameter to be verified according to the verification rule corresponding to the parameter to be verified.
S813, obtaining 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 function relationship to calculate to obtain a calculation result, determining whether the calculation result is correct or not, or whether the calculation result accords with the logical relationship presented by the function relationship, and if the calculation result is correct or the calculation result accords with the logical relationship presented by the function relationship, determining that the value of the parameter to be verified is legal; and if the calculation result is incorrect or the calculation result does not conform to the logical relationship presented by the functional relationship, determining that the value of the parameter to be verified is illegal.
S815, judging whether the neglected state of the function parameter is a neglected state, and if the neglected state of the function parameter is the neglected state, setting the neglected state of the parameter to be verified as the neglected state; and if the neglected state of the function parameter is the non-ignorable state, keeping the ignore state of the parameter to be verified as the current ignore state.
And S816, not checking the legality of the value of the parameter to be checked, and setting the neglected state of the parameter to be checked to be a neglected state.
And S817, the validity of the value of the parameter to be verified is not verified.
And S818, when the check result obtained by the terminal includes that the value of the parameter to be checked is illegal, the terminal returns the illegal parameter to be checked to the front-end equipment so as to instruct the front-end equipment to check and/or modify the illegal parameter to be checked.
The above steps are described in the foregoing embodiments, and for details, refer to the foregoing description, which is not repeated herein.
It should be understood that although the various steps in the flow charts of fig. 2-9 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-9 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 10, there is provided a parameter checking apparatus including:
a receiving module 11, configured to receive a parameter verification request; the parameter checking request comprises a plurality of values of parameters to be checked;
the obtaining module 12 is configured to obtain a calibration rule corresponding to each parameter to be calibrated according to a correspondence between a preset calibration parameter and the calibration rule;
and the checking module 13 is configured to perform validity checking on the value of each parameter to be checked according to the type of each checking rule, so as to obtain a checking result.
In one embodiment, as shown in fig. 11, the verification module 13 includes:
a determining unit 131, configured to determine whether an ignoring state of each parameter to be verified is a non-ignoring state;
a checking unit 132, configured to determine, according to a correspondence between a type of a preset checking rule and a checking policy, a checking policy corresponding to the type of the checking rule when the neglected state of the parameter to be checked is the non-ignorable state, and perform validity checking on the value of the parameter to be checked by using the checking policy.
In an embodiment, as shown in fig. 12, when the type of the check rule is a basic rule or an application branch rule, the check unit 132 includes:
the first determining subunit 1321, configured to determine a verification index according to a verification rule corresponding to the parameter to be verified;
a determining subunit 1322 is configured to determine whether the value of the parameter to be verified reaches the verification index, determine that the value of the parameter to be verified is legal if the value of the parameter to be verified reaches the verification index, and determine that the value of the parameter to be verified is illegal if the value of the parameter to be verified does not reach the verification index.
In an embodiment, as shown in fig. 13, when the type of the check item rule is the application branch rule, the check unit 132 further includes:
a second determining subunit 1323, configured to determine, according to the verification rule corresponding to the parameter to be verified and the value of the parameter to be verified, whether the parameter to be verified associated with the parameter to be verified is negligible;
a setting subunit 1324, configured to, in a case that the parameter to be verified associated with the parameter to be verified is negligible, set a ignoring state of the parameter to be verified associated with the parameter to be verified to be a negligible state.
In an embodiment, as shown in fig. 14, when the type of the check term rule is an application function rule, the check unit 132 includes:
a third determining subunit 1325, configured to determine, according to a verification rule corresponding to the parameter to be verified, a function parameter that has a functional relationship with the parameter to be verified;
an obtaining subunit 1326, configured to obtain, from the received values of the multiple parameters to be verified, a value of the function parameter;
a calculating subunit 1327, configured to substitute the value of the function parameter and the value of the parameter to be verified into the functional relationship to calculate, and perform validity check on the value of the parameter to be verified according to the calculation result.
In an embodiment, as shown in fig. 15, the verification unit 132 further includes:
a second determining subunit 1328, configured to determine whether the ignoring state of the function parameter is an ignorable state;
a second setting subunit 1329, configured to set the ignoring state of the parameter to be verified to be the negligible state if the ignoring state of the function parameter is the negligible state.
In an embodiment, the verifying unit 132 is specifically configured to, when the type of the verification rule is an application omission rule, not perform validity verification on the value of the parameter to be verified, and set the omission state of the parameter to be verified to be an ignorable state.
In an embodiment, as shown in fig. 16, the parameter checking apparatus further includes:
a returning module 14, configured to return the parameter to be checked for invalidity to the front-end device, so as to instruct the front-end device to view and/or modify the parameter to be checked for invalidity.
For the specific definition of the parameter verification device, reference may be made to the above definition of the parameter verification method, which is not described herein again. The modules in the parameter checking device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram 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 by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a parameter checking method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 17 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
receiving a parameter checking request; the parameter checking request comprises a plurality of values of parameters to be checked;
acquiring a calibration rule corresponding to each parameter to be calibrated according to a corresponding relation between preset calibration parameters and calibration rules;
and carrying out validity check on the value of each parameter to be checked according to the type of each check rule to obtain a check result.
The implementation principle and technical effect of the computer device provided by the above embodiment are similar to those of the above method embodiment, and are not described herein again.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
receiving a parameter checking request; the parameter checking request comprises a plurality of values of parameters to be checked;
acquiring a calibration rule corresponding to each parameter to be calibrated according to a corresponding relation between preset calibration parameters and calibration rules;
and carrying out validity check on the value of each parameter to be checked according to the type of each check rule to obtain a check result.
The implementation principle and technical effect of the computer-readable storage medium provided by the above embodiments are similar to those of the above method embodiments, and are not described herein again.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for parameter verification, the method comprising:
receiving a parameter checking request; the parameter checking request comprises a plurality of values of parameters to be checked;
acquiring a calibration rule corresponding to each parameter to be calibrated according to a corresponding relation between preset calibration parameters and calibration rules;
and carrying out validity check on the value of each parameter to be checked according to the type of each check rule to obtain a check result.
2. The method according to claim 1, wherein said performing validity check on the value of each parameter to be checked according to the type of each check rule to obtain a check result comprises:
judging whether the neglected state of each parameter to be checked is a non-neglected state;
if the neglected state of the parameter to be verified is the non-neglected state, determining a verification strategy corresponding to the type of the verification rule according to the corresponding relation between the type of the preset verification rule and the verification strategy, and performing validity verification on the value of the parameter to be verified by adopting the verification strategy.
3. The method according to claim 2, wherein if the type of the verification rule is a basic rule or an application branch rule, the performing validity verification on the value of the parameter to be verified by using the verification policy includes:
determining a verification index according to a verification rule corresponding to the parameter to be verified;
and judging whether the value of the parameter to be verified reaches the verification index, if so, determining that the value of the parameter to be verified is legal, and if not, determining that the value of the parameter to be verified is illegal.
4. The method of claim 3, wherein if the type of the check term rule is the application branch rule, the method further comprises:
determining whether the parameter to be verified associated with the parameter to be verified can be ignored or not according to a verification rule corresponding to the parameter to be verified and the value of the parameter to be verified;
and if the parameter to be verified associated with the parameter to be verified is negligible, setting the neglected state of the parameter to be verified associated with the parameter to be verified as a negligible state.
5. The method according to claim 2, wherein if the type of the check item rule is an application function rule, the performing validity check on the value of the parameter to be checked by using the check policy includes:
determining a function parameter in a functional relationship with the parameter to be verified according to a verification rule corresponding to the parameter to be verified;
obtaining the value of the function parameter from the received values of a plurality of parameters to be checked;
and substituting the value of the function parameter and the value of the parameter to be verified into the function relationship for calculation, and performing validity verification on the value of the parameter to be verified according to the calculation result.
6. The method of claim 5, further comprising:
judging whether the neglected state of the function parameter is a neglected state;
and if the neglected state of the function parameter is the neglected state, setting the neglected state of the parameter to be verified as the neglected state.
7. The method according to claim 2, wherein if the type of the verification rule is an application skip rule, the performing validity verification on the value of the parameter to be verified by using the verification policy includes:
and not carrying out validity check on the value of the parameter to be checked, and setting the neglected state of the parameter to be checked as a neglected 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:
and returning the illegal parameters to be checked to the front-end equipment to indicate the front-end equipment to check and/or modify the illegal parameters to be checked.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of 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, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110741754.2A CN113535553B (en) | 2021-06-30 | 2021-06-30 | Parameter checking method, computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110741754.2A CN113535553B (en) | 2021-06-30 | 2021-06-30 | Parameter checking method, computer device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113535553A true CN113535553A (en) | 2021-10-22 |
| CN113535553B CN113535553B (en) | 2023-02-28 |
Family
ID=78097470
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110741754.2A Active CN113535553B (en) | 2021-06-30 | 2021-06-30 | Parameter checking method, computer device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535553B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1996036163A2 (en) * | 1995-05-08 | 1996-11-14 | Digimarc Corporation | Steganography systems |
| CN103888254A (en) * | 2012-12-21 | 2014-06-25 | 阿里巴巴集团控股有限公司 | Network information verification method and apparatus |
| CN106484590A (en) * | 2015-09-02 | 2017-03-08 | 阿里巴巴集团控股有限公司 | Data verification method and device |
| CN108363640A (en) * | 2018-03-01 | 2018-08-03 | 深圳市道通智能航空技术有限公司 | Data verification method and device, computer readable storage medium |
| CN110071911A (en) * | 2019-03-20 | 2019-07-30 | 北京龙鼎源科技股份有限公司 | The method and device of information transferring method and device, certificate update |
| CN111624958A (en) * | 2020-04-14 | 2020-09-04 | 吉利汽车研究院（宁波）有限公司 | Equipment state information monitoring method and device and storage medium |
| CN112181804A (en) * | 2020-08-31 | 2021-01-05 | 五八到家有限公司 | Parameter checking method, equipment and storage medium |
-
2021
- 2021-06-30 CN CN202110741754.2A patent/CN113535553B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1996036163A2 (en) * | 1995-05-08 | 1996-11-14 | Digimarc Corporation | Steganography systems |
| CN103888254A (en) * | 2012-12-21 | 2014-06-25 | 阿里巴巴集团控股有限公司 | Network information verification method and apparatus |
| CN106484590A (en) * | 2015-09-02 | 2017-03-08 | 阿里巴巴集团控股有限公司 | Data verification method and device |
| CN108363640A (en) * | 2018-03-01 | 2018-08-03 | 深圳市道通智能航空技术有限公司 | Data verification method and device, computer readable storage medium |
| CN110071911A (en) * | 2019-03-20 | 2019-07-30 | 北京龙鼎源科技股份有限公司 | The method and device of information transferring method and device, certificate update |
| CN111624958A (en) * | 2020-04-14 | 2020-09-04 | 吉利汽车研究院（宁波）有限公司 | Equipment state information monitoring method and device and storage medium |
| CN112181804A (en) * | 2020-08-31 | 2021-01-05 | 五八到家有限公司 | Parameter checking method, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 柳超等: "算量软件在建筑设备工程中的应用及问题探讨", 《中国给水排水》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113535553B (en) | 2023-02-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111078910A (en) | Medical image storage method, device, system, equipment and storage medium | |
| CN113940037B (en) | Resource subscription method, device, computer equipment and storage medium | |
| CN111192352B (en) | Map rendering method, map rendering device, computer equipment and storage medium | |
| CN111399833A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN111459541A (en) | Application program packaging method and device, computer equipment and storage medium | |
| CN111949262A (en) | Front-end project construction method and device, computer equipment and storage medium | |
| CN108172271B (en) | Image-text report processing method and device | |
| CN112527923A (en) | Unstructured data storage method and device, computer equipment and storage medium | |
| CN111931160A (en) | Authority verification method, device, terminal and storage medium | |
| CN110598025A (en) | Film reading method, system, device, equipment and storage medium | |
| CN113535553B (en) | Parameter checking method, computer device and storage medium | |
| CN113744843A (en) | Medical image data processing method and device, computer equipment and storage medium | |
| CN110827959B (en) | Medical image processing method, device and storage medium | |
| CN112365432B (en) | Fusion image display method and device and medical image system | |
| CN111192661A (en) | Method and system for acquiring medical electronic film | |
| CN109766084B (en) | Customized development method and device for payment application, computer equipment and storage medium | |
| CN111899167A (en) | Interpolation algorithm determination method, interpolation algorithm determination device, computer equipment and storage medium | |
| CN111131415A (en) | Information pushing method and device, computer equipment and storage medium | |
| CN104603787A (en) | System and method for retrieving and processing metadata | |
| CN111124932B (en) | Scheme verification method, system, device, computer equipment and storage medium | |
| CN114822782A (en) | Medical image analysis method, system, apparatus, medium, and program product | |
| CN113885863A (en) | Method, device, electronic equipment and storage medium for realizing SOA (service oriented architecture) service | |
| CN113094735A (en) | Method for training privacy model | |
| CN112416877A (en) | Medical data storage method and device, computer equipment and storage medium | |
| CN112861013A (en) | User portrait updating method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |