CN115934770A

CN115934770A - Verification information generation method, device, equipment and medium

Info

Publication number: CN115934770A
Application number: CN202211615390.4A
Authority: CN
Inventors: 吴艺
Original assignee: Ant Blockchain Technology Shanghai Co Ltd
Current assignee: Ant Blockchain Technology Shanghai Co Ltd
Priority date: 2022-12-15
Filing date: 2022-12-15
Publication date: 2023-04-07

Abstract

The embodiment of the specification discloses a method, a device, equipment and a medium for generating verification information. The scheme comprises the following steps: acquiring a verification information configuration request; the verification information configuration request comprises a contract identifier of the intelligent contract to be verified; based on the contract identification, sending a corresponding rule configuration page to a user terminal; acquiring a verification field and a field verification rule provided by the user terminal based on the rule configuration page; and generating verification information aiming at the intelligent contract based on the verification field and the field verification rule.

Description

Verification information generation method, device, equipment and medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a medium for generating verification information.

Background

Blockchains are of great interest in the industry due to their decentralized, non-tamperable nature. An intelligent contract, i.e., a set of commitments defined in digital form, includes an agreement on which a contract participant can enforce these commitments. In short, it is a computer program stored in the blockchain, and executed automatically by the blockchain when a certain condition is satisfied.

With the development of intelligent contract technology, more and more services are executed by using intelligent contracts in the processing process. For example, in a business where resource flows exist, such as in the rental industry. In the prior art, the content to be checked in the service processing is usually checked manually by a staff of the resource side, for example, for a rental service, the information of the renter is usually checked manually by the lessee or the sponsor, and then the check result is linked to the blockchain to trigger execution of the corresponding intelligent contract. Thus, the processing efficiency of the service is low.

Therefore, how to check more efficiently is an urgent technical problem to be solved.

Disclosure of Invention

The embodiment of the specification provides a method, a device, equipment and a medium for generating verification information, so as to solve the problem of low efficiency of the existing verification method.

In order to solve the above technical problem, the embodiments of the present specification are implemented as follows:

an embodiment of the present specification provides a method for generating verification information, including:

acquiring a verification information configuration request; the verification information configuration request comprises a contract identification of the intelligent contract to be verified; the intelligent contracts to be checked comprise intelligent contracts deployed in a blockchain system;

based on the contract identification, sending a corresponding rule configuration page to a user terminal;

acquiring a verification field and a field verification rule provided by the user terminal based on the rule configuration page;

generating verification information aiming at the intelligent contract based on the verification field and the field verification rule; and the verification information is used for indicating that the parameter values corresponding to the verification fields are verified according to the field verification rules.

An apparatus for generating verification information provided in an embodiment of the present specification includes:

the request acquisition module is used for acquiring a verification information configuration request; the verification information configuration request comprises a contract identifier of the intelligent contract to be verified; the intelligent contracts to be checked comprise intelligent contracts deployed in a blockchain system;

the page sending module is used for sending the corresponding rule configuration page to the user terminal based on the contract identifier;

the information acquisition module is used for acquiring the verification field and the field verification rule provided by the user terminal based on the rule configuration page;

the verification information generating module is used for generating verification information aiming at the intelligent contract based on the verification field and the field verification rule; and the verification information is used for indicating that the parameter values corresponding to the verification fields are verified according to the field verification rules.

at least one processor; and (c) a second step of,

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

acquiring a verification information configuration request; the verification information configuration request comprises a contract identifier of the intelligent contract to be verified; the intelligent contracts to be checked comprise intelligent contracts deployed in a blockchain system;

Embodiments of the present specification provide a computer readable medium having stored thereon computer readable instructions executable by a processor to implement a method for generating verification information.

One embodiment of the present specification achieves the following advantageous effects:

in the embodiment of the specification, the corresponding rule configuration page can be sent to the user terminal according to the contract identifier contained in the verification information configuration request, the user can set the verification field and the field verification rule in the rule configuration page according to actual requirements, the rule configuration platform can generate the verification information aiming at the intelligent contract to be verified according to the verification field and the field verification rule provided by the user terminal, and then the verification information can be generated according to the field in the rule configuration page to verify the intelligent contract without manually verifying the information, so that the information verification efficiency can be improved.

On the other hand, some embodiments of the present disclosure may provide a visual rule configuration page for a user, and the user does not need to know a specific code of the verification information deployed in the blockchain system, which has a low technical requirement on the user, and is more beneficial to popularization of the blockchain technology and improvement of the processing efficiency of the service.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

Fig. 1 is a schematic view of an application scenario of a verification information generation method in an embodiment of the present specification;

fig. 2 is a schematic flowchart of a method for generating verification information according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a rule configuration page provided by an embodiment of the present specification;

FIG. 4 is a contract configuration page provided by an embodiment of the present description;

fig. 5 is a schematic structural diagram of a verification information generation apparatus provided in an embodiment of the present specification;

fig. 6 is a schematic structural diagram of a verification information generating device provided in an embodiment of this specification.

Detailed Description

To make the objects, technical solutions and advantages of one or more embodiments of the present disclosure more apparent, the technical solutions of one or more embodiments of the present disclosure will be described in detail and completely with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present specification, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from the embodiments given herein without making any creative effort fall within the scope of protection of one or more embodiments of the present specification.

The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.

In order to solve the defects in the prior art, the scheme provides the following embodiments:

fig. 1 is a schematic view of an application scenario of a verification information generation method in an embodiment of this specification. As shown in fig. 1, the application scenario may include a server 1 and a user terminal 2. The server 1 may be a server corresponding to the rule configuration platform, may obtain a verification information configuration request, and sends a rule configuration page corresponding to the request to the user terminal 2, and the user terminal 2 may display the rule configuration page. The user can fill in or select the verification fields and the field verification rules meeting the business requirements in the rule configuration page according to actual requirements, the server 1 can generate verification information aiming at the intelligent contract according to the verification fields and the field verification rules provided by the user terminal 2, and the verification information is deployed in the block chain system, so that the business data related to the intelligent contract which is deployed in the block chain system can be verified, and automatic verification is achieved.

Next, a method for generating verification information provided in an embodiment of the specification will be specifically described with reference to the accompanying drawings.

Fig. 2 is a schematic flow chart of a method for generating verification information according to an embodiment of the present disclosure. From the viewpoint of a program, the execution subject of the flow may be a program installed in an application server or an application client. The execution body may also be referred to as a rule configuration platform. It is to be understood that the rule configuration platform may be a program in a server or a program installed in a terminal. From the device perspective, the execution subject of the flow includes, but is not limited to, at least one of the following devices that can be the above-mentioned server or terminal: personal computers, medium and large-sized computers, computer clusters, mobile phones, tablet computers, intelligent wearable equipment, vehicle machines and the like.

As shown in fig. 2, the process may include the following steps:

step 202: acquiring a verification information configuration request; the verification information configuration request comprises a contract identifier of the intelligent contract to be verified; the intelligent contracts to be checked comprise intelligent contracts deployed in a blockchain system.

In practice, an intelligent contract may be a contract for handling a service, such as a rental service, credit service, and the like. The intelligent contract may be an intelligent contract that has been placed into a blockchain system that has not yet been executed. The contract identifier may be an identifier of information such as a company name, a service type, and a service name of a service corresponding to the intelligent contract, or may be a unique identifier of the intelligent contract, such as a contract ID corresponding to the intelligent contract.

Step 204: and sending the corresponding rule configuration page to the user terminal based on the contract identifier.

The configuration platform can determine a corresponding rule configuration page according to a contract identifier contained in the verification information configuration request, and sends the rule configuration page to the user terminal, so that the rule configuration page can be displayed in the user terminal, and a user can configure a corresponding verification rule through the visual rule configuration page.

Step 206: and acquiring a verification field and a field verification rule provided by the user terminal based on the rule configuration page.

Step 208: generating verification information aiming at the intelligent contract based on the verification field and the field verification rule; and the verification information is used for indicating that the parameter values corresponding to the verification fields are verified according to the field verification rules.

The configuration platform in the embodiment of the description can acquire the verification field and the field verification rule provided by the user in the rule configuration page, and generate verification information based on the acquired verification field and the field verification rule. The verification information can be understood as codes or scripts which can be deployed into a blockchain system to be executed, and can represent that parameter values corresponding to verification fields are verified according to field verification rules; the verification field can represent the service parameters needing verification in the service corresponding to the intelligent contract; the field check rule may indicate a rule for determining whether the check field meets a certain condition.

It should be understood that the order of some steps in the method described in one or more embodiments of the present disclosure may be interchanged according to actual needs, or some steps may be omitted or deleted.

In the embodiment of the specification, the corresponding rule configuration page can be sent to the user terminal according to the contract identifier contained in the verification information configuration request, the user can set the verification field and the field verification rule in the rule configuration page according to actual requirements, the rule configuration platform can generate the verification information aiming at the intelligent contract to be verified according to the verification field and the field verification rule provided by the user terminal, the verification information can be generated according to the configuration to verify the intelligent contract, manual information verification is not needed, and the information verification efficiency can be improved.

Moreover, in the embodiment, a visual rule configuration page can be provided for the user, the operation user does not need to know a specific code of the verification information which can be deployed in the block chain system, the technical requirement on the operation user is low, the popularization of the block chain technology is facilitated, and the service processing efficiency can be improved.

Based on the method of fig. 2, some specific embodiments of the method are also provided in the examples of this specification, which are described below.

The method in the embodiment of the present specification may further include: deploying the verification information into the blockchain system.

The corresponding relation between the verification information and the contract identification of the intelligent contract can be established, and the verification information can be deployed into a block chain system to which the intelligent contract to be verified belongs according to the corresponding relation, so that the parameter value of a field needing to be verified in the intelligent contract can be automatically verified along with the processing process of the service, and the compliance of service processing can also be ensured.

In order to facilitate the user to perform configuration operation, the rule configuration page may include some optional verification fields and field verification rules, the user may select the verification fields according to the requirement, and the displayed field content may also be provided to the user as reference content, which may also improve the efficiency of rule configuration.

Optionally, the rule configuration page in the embodiment of the present specification may include a plurality of to-be-selected check fields in an optional state and a plurality of to-be-selected field check rules in an optional state;

the acquiring of the verification field and the field verification rule provided by the user terminal based on the rule configuration page may specifically include:

acquiring the verification field selected by the user of the user terminal from the fields to be verified;

and acquiring the field verification rule selected by the user of the user terminal from the field verification rules to be selected.

In practical application, the rule configuration page may include an information display bit for displaying information such as the to-be-selected check field and the to-be-selected field check rule, the information display bit may include a control for displaying information such as the optional to-be-selected check field and the to-be-selected field check rule, and after the user clicks the control, the rule configuration page may display information content such as the optional to-be-selected check field and the to-be-selected field check rule.

The rule configuration page in the embodiment of the present specification may include a plurality of rule configuration items; the rule configuration item can comprise the verification field and the field verification rule; wherein, the check field can comprise at least one parameter information of checked field, comparison field and variable field; the field checking rule may include at least one of a checking relation rule and a parameter calculation rule.

The check relation rule may be used to check a preset relation between the checked field and the comparison field, for example, a relation greater than, less than, equal to, greater than or equal to, less than or equal to, etc.; the parameter calculation rule can be used for expressing the calculation relationship between the comparison field and the variable field, such as the calculation relationship of addition, subtraction, multiplication and division. The variable field may include a field indicating the number of units of the circulation resource involved in the service corresponding to the smart contract, such as monthly rent, annual rent, season rent, commodity unit price, and the like.

Fig. 3 is a schematic diagram of a rule configuration page provided in an embodiment of the present specification. As shown in fig. 3, the rule configuration page may include a plurality of configuration items, and the configuration items may include parameter items such as a source field, a check rule, a comparison field, a calculation rule, a variable, and an operation. Wherein the source field may represent said verified field.

The parameters in the configuration items in the embodiments of the present description may be provided by the user by way of filling in, or may provide the user with selectable items, among which the user selects. For example, for a source field, a user may click on a drop-down arrow control in a page in which parameter information may appear that may be selected. For another example, the selectable items corresponding to the verification rule may include parameters of relationships less than, greater than, equal to, and the like. The user can select the required parameter information according to the service requirement.

The rule configuration page in the embodiment of the present specification may further include a first control for performing an editing operation on the rule configuration item; the editing operation comprises at least one of enabling operation, disabling operation and modifying operation; and/or the rule configuration page further comprises a second control for adding a rule configuration item.

As shown in fig. 3, for each rule configuration item, a first control for performing an editing operation, such as a "disable" control and a "enable" control, may be corresponding, and if the user selects the "disable" control, the state of the verification information corresponding to the "disable" control may be marked as a disable state, that is, the verification information is not executed; if the user selects the "enable" control, the state of the check information corresponding to the "enable" control can be marked as the enable state, that is, the check field corresponding to the check information is required to execute the check information, the check information is required to be called and executed to check the parameter value of the corresponding check field in the execution process of the intelligent contract, so that the parameter value of the check field is ensured to meet the user requirement, and the intelligent contract can be enabled to be executed smoothly. In practical applications, the verification information can be deployed in the blockchain system, but when the system is in the non-enabled state, the verification information is not executed.

The verification information in the embodiments of the present specification may further include a state identifier indicating state information of the verification information, where the state identifier may be used to indicate whether the verification information is in an enabled state or in a disabled state; if in the enabled state, the verification information may be executed, and if in the disabled state, the verification information may not be executed. In practical applications, the verification information deployed to the blockchain system may also include a status identifier, where if the user changes the status of the configuration item in the rule configuration page through the configuration platform, the status of the verification information corresponding to the configuration item in the blockchain system may also be changed accordingly.

As shown in fig. 3, the rule configuration page may include a "new rule" control for adding a rule configuration item, and a user may add the rule configuration item by clicking the control. In the embodiment of the present description, the rule configuration item may represent a piece of verification information, and when the verification information of the service requirement is more, the service requirement may be satisfied by adding the configuration item.

In order to more fully meet the service requirements, the verification information in the example of the present specification may be generated according to user-defined verification conditions, in addition to the generation of each parameter information in the configuration items determined based on the rule template provided in the configuration page. As shown in fig. 3, the rule configuration page may include a custom area for custom checking conditions, and the user may customize the checking formula in the area. In this embodiment, the configuration platform may also generate verification information that can be deployed in the blockchain system according to a user-defined verification formula. As shown in fig. 3, the rule configuration page may further include operation controls for the custom formula, such as a confirmation control and a cancellation control. The confirmation control can represent that a user confirms to start the custom formula, and after the user clicks the confirmation control, the rule configuration platform can generate a corresponding verification code based on the custom formula in the page; if the user fills in the self-defined formula and selects the cancel control, the self-defined formula filled in by the user in the page can be deleted, and the verification code corresponding to the self-defined formula does not need to be generated or the verification code corresponding to the generated self-defined formula is deleted.

In practical application, a user may customize one or more pieces of customized verification information, and the rule configuration page may also include a control for adding a customized formula newly, such as the "+ new rule" control located below the customized formula area shown in fig. 3.

As shown in fig. 3, the rule configuration page may further include a submission control, where the submission control may be used to indicate that the verification information for the rule configuration page is sent to a blockchain system, or the verification information is sent to a server with a uplink function, so that the server uplink the verification information.

The verification information in the embodiments of the present specification may be understood as a code script that can be executed in a blockchain system. Optionally, in this embodiment of the present specification, the generating verification information for the intelligent contract based on the verification field and the field verification rule may specifically include:

determining a first code corresponding to the check field;

determining a second code corresponding to the field verification rule;

and generating a verification information script according to the first code and the second code and a preset coding format.

In this embodiment of the present specification, the verification field may include a field represented in a form of a character string, a word, or the like, and the first code may include a character string corresponding to the character string or the word, or may be a code capable of representing the character string or the word, where, for example, the verification field is "usertype", and the corresponding first code may include "usertype"; the field verification rule may include operations of addition, subtraction, multiplication and division of four elements, operations of greater than, less than, equal to and the like representing equality relations, and information such as calculation parameters, and the second code may include a code or a symbol representing the field verification rule, for example, a symbol in the field verification rule that "greater than" may correspond to a code ">".

In practical application, the configuration items in the rule configuration page may include a plurality of parameter information, and the code corresponding to each configuration item may be generated according to the display order of each parameter information in the configuration items. And generating a corresponding code script according to a preset script template so as to improve the accuracy and efficiency of script generation.

The preset encoding format may be an encoding format that can be deployed in the blockchain system, for example, the preset encoding format may be a Java format, or a JSON format, and the like, and the specific encoding format may be set according to actual requirements, which is not specifically limited herein.

The intelligent contracts in the embodiments of the present specification may include intelligent contracts generated based on contract configuration operations; the contract configuration operation is used to configure contract parameters needed by the intelligent contract. The server or the platform capable of generating the intelligent contract can generate the corresponding intelligent contract according to the contract configuration operation of the user.

Fig. 4 is a contract configuration page provided by an embodiment of the present specification. As shown in fig. 4, the contract configuration page may include sub-pages for parameter configuration such as inventory, customer information, order information, leaseholder commitment, sponsor commitment, audit loan, etc. Configuration items representing commodity information can be included in the commodity catalog, for example, for a contract of a rental vehicle, the commodity catalog can contain vehicle information such as vehicle model, number and the like of the rental vehicle. The user information may include information representing a lessee, such as a user login name, a user name, identification card information, a mobile phone number, and the like of the user on the rental platform. The order information may include information related to the order, such as an order number, a product ID corresponding to the order, a product name, a rental amount, a rental term, and the like. The lease party commitment can comprise commitment information representing a lease contract, and the commitment information can be commitment information which is achieved by two parties after the lease user makes a lease request, such as an order number, a grace period, a lease time payable, a lease payable, a return time, a late rate and the like. The sponsor commitment may include a commitment indicating the offerings provided by the sponsor, such as the amount of funds that should be provided, the time of funding, and the like. The audit can represent the content that needs to be audited by the platform or a third party so that the intelligent contract can be successfully executed, such as a tenant ID, an order number, a tenant phone number, a tenant name, a tenant identity document, or a credit line, etc.

Each sub-page can correspond to a plurality of editable configuration items. As shown in fig. 4, information about a tenant may be included in the user information configuration sub-page. Also, for example, an editable configuration item representing information such as a supplier name, a product ID, etc. may be included in the catalog subpage. Each configuration item may include at least one parameter information for indicating a parameter name, a parameter type, parameter description information, whether to fill in, and a parameter source.

The parameter name may represent a configuration object of this configuration item, such as the parameter name "userType", which may represent an identity type; the type may represent the representation of the configuration object in contract code, and may specifically be the content illustrated in the "example" column. For example, string may represent a parameter whose parameter type represented by the parameter name is a string or text type, unit may represent a number, u 16 may represent an unsigned 16bit integer, u 32 may represent an unsigned 32bit integer, unit8 may represent an unsigned 8bit integer, and int8 may represent a signed 8bit integer. The representation of the type may be determined according to the specific type of parameter name.

The contract parameters in the embodiment of the present specification may include business objects related to the business, and more specifically, may include parameters corresponding to parameter names in the contract configuration page. In order to facilitate the configuration of the verification information of the user for the intelligent contract, the optional verification field contained in the rule configuration page can be a contract parameter determined when the intelligent contract is configured. Optionally, the method in the embodiment of the present specification may further include:

determining the contract parameters contained in the intelligent contract;

and determining the to-be-selected check field based on the contract parameters.

The to-be-checked field may include contract parameters included in at least part of the intelligent contract. As shown in fig. 3, the optional field at the source field may contain "usertype" which may represent "usertype" in the user information subpage in the contract configuration page used to configure the smart contract. As another example, "payPeriod" at the source field of fig. 3 may represent "payPeriod" in a tenant commitment subpage in a contract configuration page.

Optionally, the contract parameters in this embodiment may include contract parameters displayed in a contract configuration page; the contract configuration page is used for representing a page for executing the contract configuration operation;

the determining the contract parameters included in the intelligent contract may specifically include:

acquiring contract parameters contained in the contract configuration page;

the determining the to-be-selected check field based on the contract parameter may specifically include:

establishing a linkage display relation between a first display position of the contract parameter in the contract configuration page and a second display position used for displaying a to-be-selected check field in the rule configuration page;

and based on the linkage display relationship, taking at least part of the contract parameters as the check field to be selected.

In the embodiment of the present specification, the platform providing the intelligent contract configuration service and the platform providing the verification rule configuration service may be the same platform or different platforms. Parameters in the contract configuration page can be displayed in the rule configuration page in a linkage mode, so that the intelligent contract can be configured in a targeted mode.

As shown in fig. 4, the contract parameter may be parameter information corresponding to a list of parameter names, and the first position may represent a corresponding parameter display position under the list of parameter names. The optional parameters corresponding to the source field as in fig. 3 may contain parameter information corresponding to the column of parameter names in fig. 4.

Wherein, the to-be-checked field may include a checked field, such as the source field shown in fig. 3; the to-be-selected verification field may also include a comparison field, such as the comparison field shown in fig. 3. The comparison field may also contain at least part of the contract parameters.

In practical applications, for the verification of some divisible parameters or parameters related to the total amount, such as total rent, amount of money paid, and the like, the calculation result between the comparison field and the variable may be compared with the source field to determine whether the calculation result between the source field and the comparison field and the variable satisfies the check rule. For example, if the source field is a field indicating a loan amount, the comparison field is a field indicating a lease, the variable is a field indicating a unit lease, the calculation rule is a rule indicating a multiplication, and the check rule is a rule indicating an equality, the corresponding check information may be verification information indicating whether the loan amount is equal to the lease multiplied by the unit lease.

In practical applications, the parameters corresponding to the variables are also parameters included in the intelligent contract, and as shown in fig. 3, the rule configuration page in this embodiment may also include optional variable fields, where the optional variable fields may include at least part of the contract parameters of the intelligent contract. The variable field may also have a linking relationship with contract parameters in a contract configuration page of the intelligent contract, and at least part of the contract parameters may be displayed in the variable field for selection by a user.

Optional fields to be checked, optional variable fields and the like in the embodiments of the present description may be displayed in a rule configuration page in a hierarchical manner. Wherein the hierarchical division may be the same as the hierarchical division of parameter fields in the contract configuration page. For example, the first hierarchy may be a hierarchy of each business participant in the business and business transaction objects, such as a commodity catalog, user information, order information, and the like; the second level can be a detailed information level of each service participant and each service transaction object, for example, a commodity catalog contains detailed parameter information of commodity names and providers; the third level may be more detailed information corresponding to each parameter information in the second level, such as the address of the provider. In the embodiment of the present specification, the parameters of each hierarchy may be checked, and the comparison field corresponding to the checked field may be a field located at a different hierarchy from the checked field, so that multi-level checking may be implemented, and the accuracy of checking may be improved.

The optional verification field in the embodiments of the present description may be determined by the server or the rule configuration platform according to the historical rule configuration information. Optionally, the method in this embodiment of the present specification may further include:

acquiring a historical verification field corresponding to the historical verification information; the historical check information comprises historical check information corresponding to historical intelligent contracts which have the same service types as the intelligent contracts;

determining the to-be-selected check field based on the historical check field;

and/or the presence of a gas in the gas,

acquiring a historical field check rule corresponding to historical check information;

and determining the to-be-selected field verification rule based on the historical field verification rule.

The intelligent contracts in embodiments of this specification may be intelligent contracts generated for processing services based on service requirements. The server or the configuration platform may obtain, from the configuration event processed in the history, a history verification field having the same service type as the service type corresponding to the intelligent contract, and select at least part of the history verification field from the determined history verification field as a selectable to-be-selected verification field in the rule configuration.

Similarly, in the embodiment of the present specification, a historical field check rule corresponding to the historical check information may also be obtained, and at least part of the historical field check rule is used as an optional candidate field check rule in the rule configuration.

The rule configuration page can be generated based on the to-be-selected check field and the to-be-selected field check rule. The to-be-selected check field and the to-be-selected field check rule can be displayed in a rule configuration page for selection by a user.

In practical application, the configuration platform can also display the latest historical verification field and the historical verification information as the to-be-selected verification field and the to-be-selected field verification rule in the rule configuration page. For example, when using a configuration platform, a user is usually required to register as a user of the platform, and then log in the platform according to information such as a user name and a password to perform configuration operation. Assuming that the user a performs configuration of the verification information for the service a, after the configuration is completed, the user a needs to perform configuration of the verification information for the service b, and at this time, the configuration information used when the service a is processed may be displayed in the configuration page.

In order to enable the optional information in the configuration page to meet the user requirement, the default display or available configuration information in the configuration page may be configuration information of the same service type as the service corresponding to the rule configuration to be processed. As in the above example, it is assumed that the service c is the same type as the service b, and although the user is the service a processed after the service c is processed first, the configuration information such as the corresponding verification field and the field verification rule of the service c may be provided as optional configuration information to the user.

In practical application, optional configuration information such as a to-be-selected check field and a to-be-selected field check rule which can be displayed in the rule configuration page can be determined according to a pre-trained computer model.

The field verification rule in the embodiment of the present specification may include at least one operation manner of four arithmetic operations and SQL (structured query Language) statement operations.

The calculation rule items shown in fig. 3 may include four arithmetic operations of addition, subtraction, multiplication, division, and the like. And SQL statement operations such as sum, average avg and maximum max can be further included. The check rules may include rules indicating comparison relationships such as greater than, less than, equal to, greater than or equal to, and less than or equal to.

The check field in the embodiments of the present specification may include a checked field and a comparison field, where the field check rule is used to indicate whether the checked field and the comparison field meet the check rule.

The source field entry as shown in fig. 3 may represent a verified field and the contrast field entry may represent a contrast field. The field check rule may be used to indicate whether the checked field and the comparison field meet the check rule. When the verification result is in accordance with the verification rule, the verified field can be indicated to pass the verification, and the subsequent intelligent contract script of the corresponding verified field can be continuously executed to process the service; if the verification fails, the business cannot be processed continuously, and the intelligent contract can be aborted or terminated. In practical application, if the verification fails, the server or the configuration platform may further generate a prompt message to prompt the relevant participant about the problem in the service processing.

In the embodiment, for the field to be checked, a check identifier may be further added to the field in the intelligent contract, and when the parameter value corresponding to the check field is changed, the check information may be called for checking. Optionally, the method in the embodiment of the present specification may further include: and adding a check identifier to the parameter code representing the check field in the intelligent contract so as to trigger the execution of the check information based on the check identifier.

The corresponding relation between the verification information and the contract identification corresponding to the intelligent contract can be established, and the corresponding verification information can be called in the execution process of the intelligent contract according to the corresponding relation. The contract identification has a unique correspondence with the intelligent contract, which may be understood as the ID of the intelligent contract, and information related to the service may be associated with the contract identification.

In the embodiment of the present specification, the service related data may correspond to a service identifier or an intelligent contract identifier, and each participant in the service may directly or indirectly upload the service data that is processed by the participant to the blockchain system based on the service identifier, so that the service data corresponding to the intelligent contract may be obtained in the blockchain system, and then the service data provided by each participant is automatically checked by using the checking information, thereby ensuring the compliance of service processing.

In practical application, the server or the blockchain system may obtain a parameter value provided by the participant, such as a repayment amount, determine a check field corresponding to the parameter value, where the check field may be understood as a key and the parameter value may be understood as a corresponding value, check the parameter value using check information corresponding to the check field, and determine whether the parameter value meets requirements.

The intelligent contract in the embodiment of the specification can be used for processing the service to be processed; the service to be processed may include any one of a financing service, a leasing service, a financing leasing service, or a financing service. The generated verification information may be information for verifying the service parameters in the service.

In practical application, the rule configuration page may also include some default verification items that must be verified, for example, whether the identity ID of the renter is consistent with the identity ID of the renter acquired by the sponsor; whether the leasing party meets basic leasing conditions, such as whether the age is greater than 12 years, and the like. For the check item that must be checked by default, the user cannot perform the editing operation.

In the embodiment of the present specification, the verification result indicating that the audit is passed or not passed may also be saved in the blockchain system for subsequent query or use.

Based on the same idea, the embodiment of the present specification further provides a device corresponding to the above method. Fig. 5 is a schematic structural diagram of a verification information generation apparatus provided in an embodiment of the present specification. As shown in fig. 5, the apparatus may include:

a request obtaining module 502, configured to obtain a verification information configuration request; the verification information configuration request comprises a contract identifier of the intelligent contract to be verified; the intelligent contracts to be checked comprise intelligent contracts deployed in a blockchain system;

a page sending module 504, configured to send a corresponding rule configuration page to the user terminal based on the contract identifier;

an information obtaining module 506, configured to obtain a verification field and a field verification rule provided by the user terminal based on the rule configuration page;

a verification information generating module 508, configured to generate verification information for the intelligent contract based on the verification field and the field verification rule; and the verification information is used for indicating that the parameter value corresponding to the verification field is verified according to the field verification rule.

Optionally, the apparatus in this embodiment of the present specification may further include: and the uplink module is used for deploying the verification information into the block chain system.

Based on the same idea, the embodiment of the present specification further provides a device corresponding to the method.

Fig. 6 is a schematic structural diagram of a verification information generating device provided in an embodiment of this specification. As shown in fig. 6, the apparatus 600 may include:

at least one processor 610; and the number of the first and second groups,

a memory 630 communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory 630 stores instructions 620 executable by the at least one processor 610 to cause the at least one processor 610 to:

Based on the same idea, the embodiment of the present specification further provides a computer-readable medium corresponding to the above method. The computer readable medium has stored thereon computer readable instructions executable by the processor to implement the above-described generation method of the verification information.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus shown in fig. 6, since it is substantially similar to the method embodiment, the description is relatively simple, and reference may be made to the partial description of the method embodiment for relevant points.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose logic functions are determined by programming the device by a user. A digital character system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate a dedicated integrated circuit chip. Furthermore, nowadays, instead of manually making an integrated circuit chip, such programming is often implemented by "logic compiler" (software), which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as ABEL (advanced library expression Language), AHDL (alternate Language description Language), traffic, CUPL (computer unified programming Language), HDCal, jhddl (java description Language), lang, lola, HDL, las, software, rhigh (hardware description Language), and vhigh-Language, which are currently used by hardware-Language (hardware description Language). It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC625D, atmelAT SAM, microchip pic18F26K20, and silicon labsc8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, apparatuses, modules or units described in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, respectively. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information which can be accessed by a computing device. As defined herein, computer readable media does not include transitory computer readable media (transmyedia) such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A generation method of verification information comprises the following steps:

acquiring a verification information configuration request; the verification information configuration request comprises a contract identifier of the intelligent contract to be verified; the intelligent contracts to be checked comprise intelligent contracts deployed in a block chain system;

generating verification information aiming at the intelligent contract based on the verification field and the field verification rule; and the verification information is used for indicating that the parameter value corresponding to the verification field is verified according to the field verification rule.

2. The method according to claim 1, wherein the rule configuration page includes a plurality of fields to be checked in an optional state and a plurality of rules to be checked in an optional state;

the acquiring of the verification field and the field verification rule provided by the user terminal based on the rule configuration page specifically includes:

acquiring the audit field selected by the user of the user terminal from the to-be-selected audit field;

3. The method according to claim 1, wherein generating the verification information for the smart contract based on the verification field and the field verification rule specifically comprises:

determining a first code corresponding to the check field;

determining a second code corresponding to the field verification rule;

4. The method of claim 2, the intelligent contract comprising an intelligent contract generated based on a contract configuration operation; the contract configuration operation is used for configuring contract parameters required by the intelligent contract;

the method further comprises the following steps:

determining the contract parameters contained in the intelligent contract;

5. The method of claim 4, the contract parameters comprising contract parameters displayed in a contract configuration page; the contract configuration page is used for representing a page for executing the contract configuration operation;

the determining the contract parameters included in the intelligent contract specifically includes:

acquiring contract parameters contained in the contract configuration page;

the determining the to-be-selected check field based on the contract parameter specifically includes:

6. The method of claim 2, further comprising:

acquiring a historical verification field corresponding to the historical verification information; the historical verification information comprises historical verification information corresponding to historical intelligent contracts which have the same service types as the intelligent contracts;

determining the to-be-selected check field based on the historical check field;

and/or the presence of a gas in the gas,

acquiring a historical field check rule corresponding to the historical check information;

7. The method of claim 1, wherein the field validation rules include a representation of at least one of four arithmetic operations and SQL statement operations.

8. The method of claim 1, wherein the verification field comprises a verified field and a comparison field, and the field verification rule is used for indicating whether the verified field and the comparison field are determined to conform to the verification rule.

9. The method of claim 1, wherein the smart contract includes a parameter code representing the verification field;

the method further comprises the following steps:

adding a verification identifier to the parameter code representing the verification field in the intelligent contract so as to trigger the execution of the verification information based on the verification identifier.

10. The method of claim 1, the rule configuration page including a rule configuration item; the rule configuration item comprises the verification field and the field verification rule; the verification field comprises at least one parameter information of a verified field, a comparison field and a variable field; the field checking rule comprises at least one rule parameter information of a checking relation rule and a parameter calculation rule.

11. The method of claim 10, the rule configuration page further comprising a first control for performing an editing operation on the rule configuration item; the editing operation comprises at least one of enabling operation, disabling operation and modifying operation;

and/or the presence of a gas in the gas,

the rule configuration page further comprises a second control for adding a rule configuration item.

12. The method of claim 1, further comprising:

deploying the verification information to the blockchain system.

13. The method of claim 1, the intelligent contract is used to process pending traffic; the service to be processed comprises any one of a financing service, a leasing service, a financing leasing service and a financing service.

14. An apparatus for generating verification information, comprising:

the request acquisition module is used for acquiring a verification information configuration request; the verification information configuration request comprises a contract identifier of the intelligent contract to be verified; the intelligent contracts to be checked comprise intelligent contracts deployed in a block chain system;

the verification information generating module is used for generating verification information aiming at the intelligent contract based on the verification field and the field verification rule; and the verification information is used for indicating that the parameter value corresponding to the verification field is verified according to the field verification rule.

15. A generation device of verification information, comprising:

at least one processor; and the number of the first and second groups,

16. A computer readable medium having stored thereon computer readable instructions executable by a processor to implement the method of generating verification information of any of claims 1 to 13.