CN112269706B - Interface parameter verification method, device, electronic device and computer readable medium - Google Patents

Abstract

The application discloses an interface parameter verification method and device, relates to the technical field of cloud computing, and further relates to the fields of data testing and data communication. One embodiment of the method comprises the following steps: loading a parameter verification rule, wherein the parameter verification rule is used for verifying interface parameters of at least one interface; receiving an interface check request message in a network; extracting an interface name and an interface parameter to be checked in an interface check request message; and based on the parameter verification rule, verifying the interface parameters to be verified, and returning a verification result. This embodiment saves development costs.

Description

Interface parameter verification method, device, electronic device and computer readable medium

Technical Field

The present application relates to the field of cloud computing technology, specifically to the field of data testing and data communication, and in particular to an interface parameter verification method, device, electronic device, and computer-readable medium.

Background technique

Applications often need to implement specific business logic through interface calls, such as the "product management program" calling the interface provided by the "order management program" to obtain all related orders for a single product. When calling the interface, information is passed through the interface parameters. For example, in the above scenario, the product ID is an interface parameter passed from the "product management program" to the "order management program".

For each parameter in the interface call, the developer needs to write the corresponding verification logic. If there are many parameters in the interface call or the interface call needs to add or remove fields frequently, the developer's workload will be large and the development cost will be high.

Summary of the invention

Provided are an interface parameter verification method, device, electronic device, and computer-readable medium.

According to the first aspect, an interface parameter verification method is provided, which includes: loading parameter verification rules, the parameter verification rules are used to verify the interface parameters of at least one interface; receiving an interface verification request message in the network; extracting the interface name and the interface parameters to be verified in the interface verification request message; based on the parameter verification rules corresponding to the interface name, verifying the interface parameters to be verified, and returning the verification results.

According to the second aspect, an interface parameter verification device is provided, which includes: a loading unit, configured to load parameter verification rules, the parameter verification rules are used to verify the interface parameters of at least one interface; a receiving unit, configured to receive an interface verification request message in the network; an extraction unit, configured to extract the interface name and the interface parameters to be verified in the interface verification request message; a verification unit, configured to verify the interface parameters to be verified based on the parameter verification rules corresponding to the interface name, and return the verification result.

According to a third aspect, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method described in any implementation manner of the first aspect.

According to a fourth aspect, a non-transitory computer-readable storage medium storing computer instructions is provided, where the computer instructions are used to cause a computer to execute the method described in any implementation of the first aspect.

The interface parameter verification method and device provided by the embodiment of the present application first loads the parameter verification rules for verifying the interface parameters of at least one interface; secondly, receives the interface verification request message in the network; then, extracts the interface name and the interface parameters to be verified in the interface verification request message; finally, based on the parameter verification rules corresponding to the interface name, verifies the interface parameters to be verified, and returns the verification results. Thus, through the loaded parameter verification rules, all the interface parameters to be verified in the interface verification message can be verified, which improves the automation of interface parameter verification and saves the development cost of technicians in verifying each interface parameter to be verified.

It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present application.

FIG1 is a flow chart of an embodiment of an interface parameter verification method according to the present application;

2 is a flow chart of a method for extracting interface parameters to be verified in an interface verification request message of the present application;

FIG3 is a flow chart of the present application for verifying interface parameters to be verified;

FIG4 is a flow chart of another embodiment of the interface parameter verification method of the present application;

FIG5 is a schematic diagram of the structure of an embodiment of an interface parameter verification device according to the present application;

FIG6 is a block diagram of an electronic device for implementing the interface parameter verification method according to an embodiment of the present application.

Detailed ways

The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

FIG1 shows a process 100 of an embodiment of an interface parameter verification method according to the present application. The interface parameter verification method comprises the following steps:

Step 101, loading parameter verification rules.

The parameter verification rule is used to verify the interface parameters of at least one interface.

In this embodiment, the parameter verification rule is a predetermined verification rule, which can verify all interface parameters of the interface currently required to be called. The parameter verification rule corresponds to at least one interface name, and each interface name can correspond to a parameter verification rule involving multiple interface parameter verifications.

Among them, checking the interface parameters includes: judging whether the interface parameters meet the requirements of their attributes (parameter type, parameter value size range, etc.). For example, the checking rules include: whether the interface parameters are empty, whether the type of the interface parameters meets the preset type requirements, whether the length of the interface parameters meets the preset length, etc.

Furthermore, since the interface call request containing interface parameters needs to meet the requirements of the network transmission protocol during the transmission process on the network (such as a local area network or the Internet), the interface parameter verification rules can also include verifying whether the interface call request containing the interface parameters meets the network transmission protocol of the interface parameters. Of course, the interface parameter verification rules can also be: after determining that the interface call request containing the interface parameters meets the network transmission protocol of the interface parameters, it can also be verified whether the interface parameters meet the requirements of their attributes.

Optionally, in this embodiment, the parameter verification rule for verifying the interface parameters may also include: first formatting the acquired interface parameters (for example, converting the interface parameters into a type corresponding to the interface parameters), and then determining whether the interface parameters after the actual format processing meet the requirements of the type corresponding to the interface parameters.

In this embodiment, the interface parameter verification method and the execution subject thereon can obtain parameter verification rules from the terminal in real time or from the database, and after loading the parameter verification rules, verify the interface parameters in the received verification request message based on the verification logic of the parameter verification rules.

Step 102: Receive an interface verification request message in the network.

In this embodiment, the network can be the Internet or a local area network. The interface verification request message is a message about interface parameters to be verified sent by an application to another application during the process of calling the interface of another application in order to implement specific business logic.

Specifically, the interface verification request message includes interface parameters to be verified, and the positions of the interface parameters to be verified in the interface verification request message are different based on different transmission protocols. For example, based on the HTTP (HyperText TransferProtocol, Hypertext Transfer Protocol) transmission protocol, the interface parameters to be verified can be located in the three positions of the corresponding protocol in the interface verification request message: Query (request line), Header (request header), and Body (request body).

Step 103: extract the interface name and interface parameters to be verified in the interface verification request message.

In this embodiment, after the execution subject receives the interface verification request message, the interface name and the interface parameters to be verified in the interface verification request message can be extracted through an interceptor (such as an Interceptor tool).

Optionally, before extracting the interface name and interface parameters to be verified in the interface verification request message, you can also pre-verify the business requirement information in the interface verification request message. The interface verification request message generally carries its own business requirement information, such as "obtain product details information based on the product ID". At this time, the request will carry a product ID, and the product ID is its own business requirement information. You can first verify the product ID. If the verification passes, the pre-verification is completed.

Step 104: based on the parameter verification rule corresponding to the interface name, verify the interface parameters to be verified and return the verification result.

In this embodiment, the parameter verification rules include at least one parameter verification rule corresponding to an interface name. Since different interface names have different parameter verification rules, the parameter verification rule corresponding to the interface name in the parameter verification rules can be searched and determined using the above-extracted interface name as an index.

Furthermore, the parameter verification rules corresponding to the interface name include at least one parameter verification rule corresponding to an interface parameter, and the interface parameters include: an interface parameter name and a parameter value corresponding to the interface parameter name. The interface parameter name can be used as an index to search and determine the parameter verification rules corresponding to the interface name and the parameter verification rules corresponding to the interface parameter to be verified.

In this embodiment, the interface parameter to be checked is a member of at least one interface parameter, and the interface parameter to be checked includes: a name of the interface parameter to be checked and a parameter value corresponding to the name of the interface parameter to be checked, as shown in Example 1.

Example 1:

"paramName":"emailAddress",

"apiName":"submitEmailAddress",

"position":"Query",

"using":"ture",

"type":"string",

"required":true,

"maxLength":100,

"minLength":5,

"pattern":"^[a-z0-9A-Z]+[-|a-z0-9A-Z._]+@([a-z0-9A-Z]+(-[a-z0-9A-Z]+)？\\.)+[a-z]{2,}$"}

The parameter verification rules corresponding to the interface name shown in Example 1 are as follows:

Verify the parameter name emailAddress of the interface name submitEmailAddress and the location Query. The maximum length of the parameter name is 100 and the minimum length is 5. The parameter value corresponding to the parameter name must satisfy the regular expression in the pattern part.

In this embodiment, the verification results include: passing the verification and failing the verification. When the verification result is passing the verification, the subsequent interface call mode can be performed. When the verification result is failing the verification, it is determined that the interface parameters to be verified are illegal, and an abnormal message or/and an alarm are issued.

The interface parameter verification method provided by the embodiment of the present application first loads the parameter verification rules for verifying the interface parameters of at least one interface; secondly, receives the interface verification request message in the network; then, extracts the interface name and the interface parameters to be verified in the interface verification request message; finally, based on the parameter verification rules corresponding to the interface name, verifies the interface parameters to be verified, and returns the verification results. Thus, through the loaded parameter verification rules, all the interface parameters to be verified in the interface verification message can be verified, which improves the automation of interface parameter verification and saves the development cost of technicians in verifying each interface parameter to be verified.

In this embodiment, the interface parameter to be verified includes: the interface parameter name to be verified and the parameter value corresponding to the interface parameter name to be verified. In some optional implementations of this embodiment, as shown in FIG. 2, the method for extracting the interface parameter to be verified in the interface verification request message includes the following steps:

Step 201: extract the name of the interface parameter to be verified from the interface verification request message.

In this optional implementation, after the execution subject receives the interface verification request message, the name of the interface parameter to be verified in the interface verification request message can be extracted through the interceptor.

Step 202: Verify the interface parameter name to be verified based on the parameter verification rule corresponding to the interface name.

In this optional implementation, the parameter verification rule corresponding to the interface name includes a parameter verification rule corresponding to at least one interface parameter. Since the interface parameter name to be verified has been determined, the parameter verification rule corresponding to the interface parameter name to be verified can be determined from the parameter verification rule corresponding to at least one interface parameter, and the interface parameter name to be verified is verified using the parameter verification rule corresponding to the interface parameter name to be verified. The specific verification process for verifying the interface parameter name to be verified can be based on the type and length of the interface parameter name to be verified.

Of course, verification can also be performed based on the position of the interface parameter name to be verified in the interface verification request message. In some optional implementation methods of the present embodiment, the interface parameter name to be verified is verified based on the parameter verification rules corresponding to the interface name, including: determining the position of the interface parameter name to be verified in the interface verification request message; determining the parameter verification rules corresponding to the parameter to be verified from the parameter verification rules corresponding to the interface name; in response to the position of the interface parameter name to be verified in the interface verification request message matching the position of the interface parameter name to be verified recorded in the parameter verification rules corresponding to the parameter to be verified, determining that the interface parameter name to be verified has passed the verification.

In this optional implementation, based on the interface verification request message of the HTTP transmission protocol, the interception tool can be used to extract the properties of the encoded data to obtain the parameters of the three parts of Query, Header, and Body in the interface verification request message, and save them separately, thereby determining the position of the interface parameter name to be verified in the interface verification request message. Further, the parameter verification rule corresponding to the parameter to be verified defines the position of the parameter name to be verified of the current interface, as shown in Example 2.

Example 2:

"paramName":"products.specification.price",

"apiName":"batchSubmitProduct",

"position":"Body",

"using":"true",

"type":"Float",

"required":true,

"maxDigital":5,

"minDigital":1

}

The parameter verification rules corresponding to the parameters to be verified shown in Example 2 are expressed as follows:

Verify the interface name batchSubmitProduct, location Body, and the interface parameter name products.specification.price to be verified. The maximum number of decimal places of the parameter value corresponding to the interface parameter name to be verified is 5, and the minimum number of decimal places is 1.

In this optional implementation, whether the interface parameter name to be checked is correctly checked is verified by judging whether the position of the interface parameter name to be checked in the interface verification request message matches the position of the interface parameter name to be checked recorded in the parameter verification rule corresponding to the parameter to be checked. For some interface verification request messages based on network transmission protocols, such as HTTP and RMI (Remote Method Invocation), since the position of each interface parameter is fixed, a valid result of the interface parameter name to be checked can be obtained, thereby ensuring the reliability of the verification result.

Step 203: In response to determining that the interface parameter name to be verified passes verification, extract the parameter value.

In this optional implementation, the parameter value corresponding to the interface parameter name to be verified in the interface verification request message can be extracted through an interceptor.

In this optional implementation method, the name of the interface parameter to be checked is first extracted from the interface verification request message, and the interface parameter name to be checked is verified based on the parameter verification rules corresponding to the interface name; finally, after the interface parameter name to be checked passes the verification, the parameter value is extracted. This method of extraction, verification, and then extraction ensures the reliability of the extraction of the interface parameter to be checked.

In another optional implementation of the present embodiment, since the interface parameter to be verified includes: the interface parameter name to be verified and the parameter value corresponding to the interface parameter name to be verified, the interface parameter name to be verified and the parameter value corresponding to the interface parameter to be verified in the interface verification request message can also be extracted in sequence, and then the interface parameter name to be verified and the parameter value corresponding to the interface parameter to be verified are verified in sequence. In some optional implementations of the present embodiment, as shown in FIG3, the method for verifying the interface parameter to be verified includes the following steps:

Step 301: Verify the interface parameter name to be verified based on the parameter verification rule corresponding to the interface name.

In this optional implementation, the parameter verification rule corresponding to the interface name includes at least one parameter verification rule corresponding to the interface parameter. Since the interface parameter name to be verified has been determined, the parameter verification rule corresponding to the interface parameter name to be verified can be determined from the parameter verification rule corresponding to the at least one interface parameter, and the interface parameter name to be verified is verified using the parameter verification rule corresponding to the interface parameter name to be verified. The specific verification process for verifying the interface parameter name to be verified can be based on the type and length of the interface parameter name to be verified.

In some optional implementations of the present embodiment, the above-mentioned interface parameter name to be checked is checked based on the parameter verification rules corresponding to the interface name, including: determining the position of the interface parameter name to be checked in the interface verification request message; determining the parameter verification rules corresponding to the parameter to be checked from the parameter verification rules corresponding to the interface name; in response to the position of the interface parameter name to be checked in the interface verification request message matching the position of the interface parameter name to be checked recorded in the parameter verification rules corresponding to the parameter to be checked, determining that the interface parameter name to be checked passes the verification.

In this optional implementation method, whether the interface parameter name to be checked is correctly checked is verified by judging whether the position of the interface parameter name to be checked in the interface verification request message matches the position of the interface parameter name to be checked recorded in the parameter verification rule corresponding to the parameter to be checked. For some interface verification request messages based on network transmission protocols, such as HTTP and RMI, since the position of each interface parameter is fixed, a valid result of the interface parameter name to be checked can be obtained, thereby ensuring the reliability of the verification result.

Step 302: In response to determining that the interface parameter name to be verified passes verification, verify the parameter value.

In this embodiment, the parameter verification rules corresponding to the interface name include the parameter verification rules corresponding to the parameter to be verified, and the parameter verification rules corresponding to the parameter to be verified may include: the data type of the parameter value corresponding to the interface parameter name to be verified, such as string, integer, floating point, Boolean, enumeration, list. The data type of the parameter value corresponding to the interface parameter name to be verified can be used to verify the parameter value corresponding to the interface parameter name to be verified.

In some optional implementations of this embodiment, the parameter verification rule corresponding to the parameter to be verified may include: a preset data type and a verification sub-rule for performing numerical verification on the parameter value, and the parameter value is verified, including:

The parameter value is converted into a data type according to a preset data type; in response to the data type of the converted parameter value being the same as the preset data type, whether the converted parameter value satisfies a check sub-rule is detected; in response to the detection result that the converted parameter value satisfies the check sub-rule, it is determined that the parameter value passes the check.

In this optional implementation, since the extracted parameter values are generally strings, which are not conducive to data type verification, the parameter values are first converted according to the preset data type. On the one hand, this is conducive to data type verification, and on the other hand, it can confirm whether the extracted parameter values are transmitted correctly in the interface verification request message.

In this optional implementation, the check sub-rule is used to check whether the specific value of the parameter value meets the requirements. For example, the regular expression in Example 1 and the maximum number of decimal places and the minimum number of decimal places in Example 2 are both check sub-rules.

The method for verifying parameter values provided by this optional implementation first converts the data type of the extracted parameter value into a data type preset in the parameter verification rule, and in response to the converted parameter value being the same as the preset data type, verifies whether the converted parameter value satisfies the verification sub-rule, thereby improving the reliability of the parameter value verification.

The method for verifying the interface parameters to be verified provided by this optional implementation method, after extracting the interface name, the name of the interface parameter to be verified and the parameter value corresponding to the interface parameter name to be verified, verifies the interface name, interface parameter name and parameter value in turn, thereby improving the reliability of the verification of the interface parameters to be verified.

In order to update the parameter verification rules, for all the above embodiments, the parameter verification rules can also be updated by reading the database. Referring to FIG. 4 , a process 400 of another embodiment of the interface parameter verification method of the present application is shown. The interface parameter verification method includes the following steps:

Step 401, loading preset parameter verification rules.

The parameter verification rule is used to verify the interface parameters of at least one interface.

In this embodiment, the preset parameter verification rule is a preset parameter verification rule, which can be placed in some applications or databases in advance, and the interface parameter verification method and the running subject thereon can obtain the preset parameter verification rule by calling the interface or accessing the database. Of course, the preset parameter verification rule can also be the same parameter verification rule as the parameter verification rule in the embodiment shown in Figure 1.

Step 402: Receive an interface verification request message in the network.

Step 403: extract the interface name and interface parameters to be verified in the interface verification request message.

Step 404: based on the parameter verification rule corresponding to the interface name, verify the interface parameters to be verified and return the verification result.

It should be understood that the operations and features in the above steps 401-404 correspond to the operations and features in steps 101-104, respectively. Therefore, the above descriptions of the operations and features in steps 101-104 are also applicable to steps 401-404 and will not be repeated here.

Step 405: Periodically read the parameter verification rules of the database.

In this embodiment, the time for periodically reading the parameter verification rules of the database can be set according to the needs of the execution entity, and all reading times covering the update time of the parameter verification rules in the database are within the protection scope of this embodiment.

Step 406 , in response to determining that the parameter verification rule of the database is different from the preset parameter verification rule, the preset parameter verification rule is replaced by the parameter verification rule of the database, and the process returns to step 401 .

In this embodiment, when the parameter verification rules of the database are different from the preset parameter verification rules, it means that the parameter verification rules of the database are already the latest parameter verification rules. By returning to step 401 to reload the latest parameter verification rules, it can be ensured that the version of the rules based on which the parameter verification method is based is always the latest version.

The interface parameter verification method provided in this embodiment periodically reads the parameter verification rules in the database. When the parameter verification rules in the database are different from the preset parameter verification rules, the parameter verification rules in the database are replaced with the preset parameter verification rules, thereby achieving regular updating of the parameter verification rules and ensuring the real-time performance of the interface parameter verification.

Further referring to FIG. 5 , as an implementation of the methods shown in the above figures, the present application provides an embodiment of an interface parameter verification device, which corresponds to the method embodiment shown in FIG. 1 , and can be specifically applied to various electronic devices.

As shown in FIG5 , the interface parameter verification device 500 provided in this embodiment includes: a loading unit 501, a receiving unit 502, an extraction unit 503, and a verification unit 504. The loading unit 501 can be configured to load parameter verification rules, and the parameter verification rules are used to verify the interface parameters of at least one interface. The receiving unit 502 can be configured to receive an interface verification request message in the network. The extraction unit 503 can be configured to extract the interface name and the interface parameters to be verified in the interface verification request message. The verification unit 504 can be configured to verify the interface parameters to be verified based on the parameter verification rules corresponding to the interface name, and return the verification result.

In this embodiment, in the interface parameter verification device 500: the specific processing of the loading unit 501, the receiving unit 502, the extraction unit 503, and the verification unit 504 and the technical effects brought about by them can be respectively referred to the relevant descriptions of step 101, step 102, step 103, and step 104 in the corresponding embodiment of Figure 1, and will not be repeated here.

In some optional implementations of this embodiment, the interface parameters to be checked include: the interface parameter name to be checked and the parameter value corresponding to the interface parameter name to be checked, and the extraction unit 503 includes: a parameter extraction module (not shown in the figure), a parameter verification module (not shown in the figure), and a value extraction module (not shown in the figure). Among them, the parameter extraction module can be configured to extract the interface parameter name to be checked from the interface verification request message. The parameter verification module can be configured to verify the interface parameter name to be checked based on the parameter verification rules corresponding to the interface name. The value extraction module can be configured to extract the parameter value in response to determining that the interface parameter name to be checked passes the verification.

In some optional implementations of this embodiment, the interface parameter to be checked includes: the interface parameter name to be checked and the parameter value corresponding to the interface parameter name to be checked; the verification unit 504 includes: a parameter verification module (not shown in the figure), and a value verification module (not shown in the figure). The parameter verification module can be configured to verify the interface parameter name to be checked based on the parameter verification rule corresponding to the interface name. The value verification module can be configured to verify the parameter value in response to determining that the interface parameter name to be checked passes the verification.

In some optional implementations of the present embodiment, the parameter verification module includes: a positioning submodule (not shown in the figure), a determination submodule (not shown in the figure), and a verification submodule (not shown in the figure). Among them, the positioning submodule determines the position of the interface parameter name to be verified in the interface verification request message. The determination submodule can be configured to determine the parameter verification rule corresponding to the parameter to be verified from the parameter verification rule corresponding to the interface name. The verification submodule can be configured to determine that the interface parameter name to be verified passes the verification in response to the position of the interface parameter name to be verified in the interface verification request message matching the position of the interface parameter name to be verified recorded in the parameter verification rule corresponding to the parameter to be verified.

In some optional implementations of this embodiment, the parameter verification rules corresponding to the above-mentioned parameters to be verified include: a preset data type and a verification sub-rule for performing numerical verification on the parameter value, and the value verification module includes: a conversion sub-module (not shown in the figure), a detection sub-module (not shown in the figure), and a verification sub-module (not shown in the figure). Among them, the above-mentioned conversion sub-module can be configured to perform data type conversion on the parameter value according to the preset data type. The above-mentioned detection sub-module can be configured to detect whether the converted parameter value satisfies the verification sub-rule in response to the data type of the converted parameter value being the same as the preset data type. The above-mentioned verification sub-module can be configured to determine that the parameter value passes the verification in response to the detection result that the converted parameter value satisfies the verification sub-rule.

In some optional implementations of this embodiment, the apparatus 500 further includes: a reading unit (not shown in the figure), and a replacement unit (not shown in the figure). The reading unit may be configured to periodically read the parameter verification rules of the database. The replacement unit may be configured to replace the parameter verification rules with the parameter verification rules of the database in response to determining that the parameter verification rules of the database are different from the parameter verification rules.

The interface parameter verification device provided by the embodiment of the present application firstly loads the parameter verification rules for verifying the interface parameters of at least one interface by the loading unit 501; secondly, the receiving unit 502 receives the interface verification request message in the network; then, the extraction unit 503 extracts the interface name and the interface parameters to be verified in the interface verification request message; finally, the verification unit 504 verifies the interface parameters to be verified based on the parameter verification rules corresponding to the interface name, and returns the verification result. Thus, through the loaded parameter verification rules, all the interface parameters to be verified in the interface verification message can be verified, which improves the automation of interface parameter verification and saves the development cost of technicians in verifying each interface parameter to be verified.

According to an embodiment of the present application, the present application also provides an electronic device and a readable storage medium.

As shown in Figure 6, it is a block diagram of an electronic device according to the interface parameter verification method of an embodiment of the present application. Electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers and other suitable computers. Electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown in this article, their connection and relationship, and their functions are only used as examples, and are not intended to limit the realization of the application described herein and/or required.

As shown in Figure 6, the electronic device includes: one or more processors 601, memory 602, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input/output device (such as a display device coupled to the interface). In other embodiments, if necessary, multiple processors and/or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). In Figure 6, a processor 601 is taken as an example.

The memory 602 is a non-transient computer-readable storage medium provided in the present application. The memory stores instructions executable by at least one processor to enable at least one processor to perform the interface parameter verification method provided in the present application. The non-transient computer-readable storage medium of the present application stores computer instructions, which are used to enable a computer to perform the interface parameter verification method provided in the present application.

The memory 602, as a non-transient computer-readable storage medium, can be used to store non-transient software programs, non-transient computer executable programs and modules, such as program instructions/modules corresponding to the interface parameter verification method in the embodiment of the present application (for example, the loading unit 501, the receiving unit 502, the extraction unit 503 and the verification unit 504 shown in FIG. 5). The processor 601 executes various functional applications and data processing of the server by running the non-transient software programs, instructions and modules stored in the memory 602, that is, implements the interface parameter verification method in the above method embodiment.

The memory 602 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the electronic device of the interface parameter verification method, etc. In addition, the memory 602 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 602 may optionally include a memory remotely arranged relative to the processor 601, and these remote memories may be connected to the electronic device of the interface parameter verification method via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

The electronic device of the interface parameter verification method may further include: an input device 603 and an output device 604. The processor 601, the memory 602, the input device 603 and the output device 604 may be connected via a bus 605 or other means, and FIG6 takes the connection via the bus 605 as an example.

The input device 603 can receive input digital or character information, and generate key signal input related to user settings and function control of the electronic device of the interface parameter verification method, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator rod, one or more mouse buttons, a trackball, a joystick and other input devices. The output device 604 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The display device may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display and a plasma display. In some embodiments, the display device may be a touch screen.

Various implementations of the systems and techniques described herein can be realized in digital electronic circuit systems, integrated circuit systems, dedicated ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and/or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for programmable processors and can be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and/or means (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and/or data to a programmable processor.

To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communications network). Examples of communications networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and virtual private servers (VPS) services.

It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution disclosed in this application can be achieved, and this document is not limited here.

The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims (10)

1. An interface parameter verification method, the method comprising:

loading a parameter verification rule, wherein the parameter verification rule is used for verifying interface parameters of at least one interface;

receiving an interface check request message in a network;

extracting an interface name and an interface parameter to be checked in the interface check request message; the interface parameters to be checked comprise: the method comprises the steps of checking an interface parameter name to be checked and a parameter value corresponding to the interface parameter name to be checked;

and verifying the interface parameters to be verified based on the parameter verification rules corresponding to the interface names, and returning a verification result comprises the following steps: determining the position of the interface parameter name to be checked in the interface check request message; determining a parameter verification rule corresponding to the parameter to be verified from the parameter verification rule corresponding to the interface name; determining that the to-be-verified interface parameter name passes verification according to the fact that the position of the to-be-verified interface parameter name in the interface verification request message is matched with the position of the to-be-verified interface parameter name recorded in a parameter verification rule corresponding to the to-be-verified parameter; and extracting the parameter value in response to determining that the interface parameter name to be checked passes the check.

2. The method of claim 1, wherein the extracting the interface parameter to be verified in the interface verification request message comprises:

extracting the interface parameter name to be checked from the interface check request message;

checking the interface parameter name to be checked based on a parameter checking rule corresponding to the interface name;

and extracting the parameter value in response to determining that the interface parameter name to be checked passes the check.

3. The method according to claim 1, wherein the parameter verification rule corresponding to the parameter to be verified includes: the method comprises the steps of presetting a data type and a check sub-rule for carrying out numerical check on the parameter value, wherein the step of checking the parameter value comprises the following steps:

carrying out data type conversion on the parameter value according to the preset data type;

detecting whether the converted parameter value meets the syndrome rule or not according to the fact that the data type of the converted parameter value is the same as the preset data type;

and responding to the detection result that the converted parameter value meets the syndrome rule, and determining that the parameter value passes the verification.

4. A method according to one of claims 1-3, the method further comprising:

periodically reading parameter verification rules of a database;

and in response to determining that the parameter check rule of the database is not identical to the loaded parameter check rule, replacing the parameter check rule of the database with the parameter check rule.

5. An interface parameter verification apparatus, the apparatus comprising:

the loading unit is configured to load parameter verification rules, and the parameter verification rules are used for verifying interface parameters of at least one interface;

a receiving unit configured to receive an interface check request message in a network;

an extracting unit, configured to extract an interface name and an interface parameter to be checked in the interface check request message, where the interface parameter to be checked includes: the method comprises the steps of checking an interface parameter name to be checked and a parameter value corresponding to the interface parameter name to be checked;

the verification unit is configured to verify the interface parameters to be verified based on the parameter verification rules corresponding to the interface names, and returns a verification result; the verification unit includes: the system comprises a parameter verification module and a value verification module, wherein the parameter verification module comprises: the positioning sub-module is configured to determine the position of the interface parameter name to be checked in the interface check request message; the determining submodule is configured to determine a parameter verification rule corresponding to a parameter to be verified from the parameter verification rules corresponding to the interface names; the verification sub-module is configured to determine that the to-be-verified interface parameter name passes verification according to the fact that the position of the to-be-verified interface parameter name in the interface verification request message is matched with the position of the to-be-verified interface parameter name recorded in a parameter verification rule corresponding to the to-be-verified parameter; the value verification module is configured to verify the parameter value in response to determining that the interface parameter name to be verified passes verification.

6. The apparatus of claim 5, wherein the extraction unit comprises:

the parameter extraction module is configured to extract the interface parameter name to be checked from the interface check request message;

the parameter verification module is configured to verify the interface parameter name to be verified based on a parameter verification rule corresponding to the interface name;

and a value extraction module configured to extract the parameter value in response to determining that the interface parameter name to be checked passes the check.

7. The apparatus of claim 5, wherein the parameter verification rule corresponding to the parameter to be verified comprises: the method comprises the steps of presetting a data type and a check sub-rule for carrying out numerical check on the parameter value, wherein the value check module comprises:

the conversion sub-module is configured to perform data type conversion on the parameter values according to the preset data types;

the detection sub-module is configured to respond to the fact that the data type of the converted parameter value is the same as the preset data type, and detect whether the converted parameter value meets the check sub-rule or not;

and the checking sub-module is configured to determine that the parameter value passes the check in response to the detection result that the converted parameter value meets the check sub-rule.

8. The apparatus according to one of claims 5-7, the apparatus further comprising:

a reading unit configured to periodically read a parameter verification rule of the database;

and a replacement unit configured to replace the parameter verification rule with the parameter verification rule of the database in response to determining that the parameter verification rule of the database is not identical to the loaded parameter verification rule.

9. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-4.

10. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-4.