WO2024012195A1

WO2024012195A1 - Unified verification method and apparatus, and device and storage medium

Info

Publication number: WO2024012195A1
Application number: PCT/CN2023/102863
Authority: WO
Inventors: 陈浩; 余华森; 孙炜; 李伟
Original assignee: 苏宁易购集团股份有限公司
Priority date: 2022-07-14
Filing date: 2023-06-27
Publication date: 2024-01-18
Also published as: CN115390936A; CA3203549A1

Abstract

A unified verification method, comprising: acquiring system service information and field information of a currently accessed service system; acquiring corresponding verification configuration information according to the system service information and the field information; and verifying the field information according to the corresponding verification configuration information, and returning verification result information to the currently accessed service system.

Description

Unified verification methods, devices, equipment and storage media

Cross-references to related applications

This application claims priority to the Chinese patent application submitted to the China Patent Office on July 14, 2022, with the application number 202210831529.2 and the application title "Unified Verification Method, Device, Equipment and Storage Medium", the entire content of which is incorporated by reference. in this application.

Technical field

This application relates to a unified verification method, device, equipment and storage medium.

Background technique

Currently, the company's process of generating rebate fee orders based on its core business involves order creation, order modification, order confirmation, order reversal, order deletion, order batch import, single page processing, page batch processing and processing of rebate fee orders. Third-party interface empowerment, etc., the operations of each link need to be verified first. Since each enterprise may connect with multiple suppliers, each supplier may come from different channels, and the business data content of each channel will be different. Therefore, in the traditional implementation method, the verification platform needs to Business data is independently verified.

However, the inventor realized that using the above-mentioned method of separately verifying the business data of each channel, when the verification logic changes, it is necessary to follow the iteration of the version and go online, and the version will appear after multiple iterations. Inconsistency in verification logic between channels, and the multi-channel and multi-verification standard model may lead to inconsistent order processing results across different channels. Although batch import order confirmation is successful, the page confirmation fails and other abnormal situations occur, as well as the same The verification logic will be redundant. Since a timely response cannot be achieved after the verification logic is changed, the failure to respond quickly to business needs occurs.

Contents of the invention

According to various embodiments disclosed in this application, a unified verification method, device, equipment and storage medium are provided.

The first aspect is to provide a unified verification method, including:

Obtain the system business information and field information of the currently accessed business system;

Obtain corresponding verification configuration information based on system business information and field information; and

Verify the field information according to the corresponding verification configuration information, and return the verification result information to the currently accessed business system.

In the second aspect, a unified verification device is provided, including:

The acquisition module is used to obtain the system business information and field information of the currently accessed business system;

Configuration module, used to obtain corresponding verification configuration information based on system business information and field information; and

The verification module is used to verify the field information according to the corresponding verification configuration information, and return the verification result information to the currently accessed business system.

In a third aspect, a computer device is provided, including a memory and one or more processors. Computer readable instructions are stored in the memory. When the computer readable instructions are executed by the processor, the computer readable instructions cause the one to or multiple processors perform the following steps:

Obtain corresponding verification configuration information according to the system business information and the field information; and

The field information is verified according to the corresponding verification configuration information, and the verification result information is returned to the currently accessed business system.

A fourth aspect provides one or more non-volatile storage media storing computer-readable instructions. When executed by one or more processors, the computer-readable instructions cause one or more processors to perform the following steps:

The details of one or more embodiments of the application are set forth in the accompanying drawings and the description below. Other features and advantages of the application will be apparent from the description, drawings, and claims.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. Those of ordinary skill in the art can also obtain other drawings based on these drawings without exerting creative efforts.

Figure 1 is a system architecture diagram of a unified verification method according to one or more embodiments.

Figure 2 is a schematic flowchart of a unified verification method according to one or more embodiments.

Figure 3 is a schematic flowchart of step 203 in the unified verification method according to one or more embodiments.

Figure 4 is a block diagram of a unified verification device according to one or more embodiments.

Figure 5 is a block diagram of a computer device in accordance with one or more embodiments.

Detailed ways

The present application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described here are only used to explain the present application and are not used to limit the present application.

To facilitate understanding, the system to which this application is applicable is first described. The unified verification method provided by one embodiment of this application can be applied to the system architecture as shown in Figure 1. The system includes: access device 102-unified verification platform 104.

The access device 102 here can be multiple business systems. Each business system corresponds to a different supplier. Each business system needs to be connected to the unified verification platform 104 to complete unified verification of the services of each system; and each business The system is connected to the unified verification platform 104 in sequence. The unified verification platform 104 performs unified verification on the currently accessed business system. After the verification is completed, the next accessed business system is verified, and so on. This enables unified verification of each business system.

FIG. 2 is a flow chart of a unified verification method provided by one embodiment of the present application. This method can be executed by the unified verification platform 104 in the system shown in FIG. 1 . As shown in Figure 2, the method may include the following steps:

Step 201: Obtain system business information and field information of the currently accessed business system.

Specifically, the unified verification platform obtains the system business information and field information of the currently accessed business system through the Java reflection mechanism. The Java reflection mechanism means that in the running state of the program, you can construct objects of any class, you can understand the class to which any object belongs, you can understand the member variables and methods of any class, and you can adjust Use the properties and methods of any object. This function of dynamically obtaining program information and dynamically calling objects is called the reflection mechanism of the Java language, and this reflection is regarded as the key to dynamic languages.

What needs to be explained here is that since there are many business systems, they need to be connected to the unified verification platform one by one for verification. Therefore, when the unified verification platform performs verification operations, it needs to obtain the services currently connected to the unified verification platform. System-related information.

Step 203: Obtain corresponding verification configuration information based on system business information and field information.

Verification configuration information refers to the configuration information for verifying the field information contained in the current business system, which is the specific content information of the verification.

Specifically, the unified verification platform searches for the verification configuration information corresponding to the business system according to the system business information and field information to obtain the verification configuration information.

Step 205: Verify the field information according to the corresponding verification configuration information, and return the verification result information to the currently accessed business system.

Here, after obtaining the corresponding verification configuration information, the unified verification platform verifies the field information in the currently accessed business system based on the corresponding verification configuration information. After the verification is completed, regardless of whether the verification passes or not, The verification result information needs to be returned to the currently connected business system so that the business system can proceed with the next step.

It can be seen that one of the embodiments of the present application first obtains the system business information and field information of the currently accessed business system; secondly, obtains the corresponding verification configuration information according to the system business information and field information; finally, obtains the corresponding verification configuration information according to the corresponding verification Verify the field information by verifying the configuration information, and return the verification result information to the currently accessed business system. Through the above configuration settings, the data verification of the order circulation link of each business system can be unified and integrated to ensure the correctness and accuracy of the fee orders generated by the rebate system and the unity of multi-channel data, and it can improve the efficiency of order generation and quickly respond to needs. Effect.

In some embodiments, before obtaining the system service information and field information of the currently accessed service system, the following steps are included:

Configure the system business information, field information and verification logic of each business system correspondingly with the universal data model of the unified verification platform to obtain the corresponding verification configuration information corresponding to each business system, and combine each corresponding verification configuration information Synchronize to remote dictionary server.

Here, before the unified verification platform obtains the system business information and field information of the currently accessed business system, Some preparatory operations still need to be done. Since the unified verification platform will provide unified verification services for multiple systems and multiple services, taking specific services as the main line and supporting multi-system access, it can perform common logic verification and verification of the special logic of individual systems based on the configuration information of each business system. , therefore, you need to configure the page of the unified verification platform first.

Specifically, since the verification logic of each business system is basically different, each business system needs to agree on a verification data model with the unified verification platform. Both parties define the data structure and combine the field information of each business system with the unified verification platform. One-to-one correspondence with the common data model of the test platform. That is, the system business information, field information and verification logic of each business system are configured correspondingly with the universal data model of the unified verification platform, and a verification configuration corresponding to the system business information, field information and verification logic of each business system is obtained. information.

A universal data model defines and encapsulates the underlying data of sensors and their observations in a self-describing, semantically activated manner. More precisely, a common data model is used to define the representation, nature, structure, and encoding of data associated with sensors and their observations. The main purpose of this model is to realize sensor network interoperability, first at the syntax level, and later at the semantic level, so that sensors and their observation data can be better understood by machines and can be automatically processed in complex workflows. , can also be easily shared among smart sensor network nodes. The Common Data Model defines the underlying data model that allows users and/or servers to organize, encode, and transmit sensor data sets in a self-describing and semantically activated manner.

Here, after the unified verification platform obtains the corresponding verification configuration information, in order to achieve the persistence of the corresponding verification configuration information, each verification configuration information is stored and synchronized to the remote dictionary server using a relational database management system. In this way, when the order page changes and the verification configuration information is added, modified, or deleted, the remote dictionary server also needs to be synchronized to ensure the consistency of the corresponding verification configuration information.

The relational database management system can be Mysql (Structured Query Language). Mysql stores data in different tables instead of placing all data in a large warehouse, which increases the computer's operating speed and improves flexibility. And the SQL language used by MySQL is the most commonly used standardized language for accessing databases. Therefore, MySQL is generally chosen as the website database for the development of small, medium and large websites.

The remote dictionary server can be Redis (Remote Dictionary Server), and Redis can be used as database, cache and message middleware. It is a non-relational database based on high-performance Key-Value and provides APIs in multiple languages. However, unlike traditional databases, redis data is stored in memory, so the storage and writing speed is very fast.

Through the above operations, the unified verification platform can realize unified verification of each business system in the later stage based on the corresponding verification configuration information completed by each business system configuration and use mysql as the underlying data storage and redis as the application cache, which has the ability to improve reading Speed effect.

In some embodiments, with reference to Figure 3, the above step 203, that is, "obtaining corresponding verification configuration information based on system business information and field information", is described in detail.

System business information includes system name and business name, field information includes field names and field values; corresponding verification configuration information includes corresponding special verification configuration information and corresponding default verification configuration information.

Step 301: Obtain the corresponding special verification configuration information according to the system name, business name and field name; if the corresponding special verification configuration information is obtained, perform step 303, that is, verify the field information according to the corresponding special verification configuration information; if If the corresponding special verification configuration information is not obtained, step 305 is executed, that is, the corresponding default verification configuration information is obtained according to the business name and field name.

Here, since the system business information includes system name and business name, the field information includes field names and field values. The unified verification platform first obtains the corresponding special verification configuration information based on the system name, business name, and field name of the currently accessed business system, that is, to confirm whether the currently accessed business system has special verification requirements. If the corresponding special verification configuration information is obtained, it means that the currently accessed business system has special verification requirements, and the field information is verified based on the corresponding special verification configuration information. If the corresponding special verification configuration information is not obtained, it means that the currently accessed business system does not have special verification requirements, and then the corresponding default verification configuration information is obtained based on the business name and field name.

After step 305, if the corresponding default verification configuration information is obtained, step 307 is performed, that is, the field information is verified according to the corresponding default verification configuration information; if the corresponding default verification configuration information is not obtained, step 309 is performed. , that is, the field information contained in the currently accessed business system does not need to be verified.

Specifically, if the corresponding default verification configuration information is obtained, the field information is verified according to the corresponding default verification configuration information. That is, the field information contained in the business system still needs to be verified, but the corresponding default verification configuration is used. Information is uniformly verified. If the corresponding default verification configuration information is not obtained, the field information contained in the currently accessed business system does not need to be verified.

It should be noted that the above acquisition sequence is adopted because some suppliers have special requirements, so the corresponding special verification configuration information needs to be obtained first according to the business system; when it is confirmed that the supplier represented by the business system does not When there are special requirements, the corresponding default verification configuration information will be obtained; if the corresponding default verification configuration information is If the information cannot be obtained, it means that the field information contained in the currently accessed business system does not need to be verified. That is, through the above-mentioned progressive acquisition method, a comprehensive verification of each business system is achieved.

In some embodiments, the above step 303, that is, "if the corresponding special verification configuration information is obtained, verify the field information according to the corresponding special verification configuration information" is described in detail.

The corresponding special verification configuration information includes the corresponding special basic verification configuration information and the corresponding special other verification configuration information; the verification includes the special basic verification and special other verifications, and the special basic verification includes the length, format and legality of the field information Verification, etc.; special other verification logic includes the correctness of the business system interface and multi-field information correlation verification, etc.

In an implementable way, if the corresponding special basic verification configuration information is obtained, annotations and attributes are added to the field information according to the corresponding special basic verification configuration information to obtain special annotation information; and then the field information is processed based on the special annotation information. Special basic check.

Special annotation information includes special annotation label information and special annotation attribute information.

Here, after obtaining the corresponding special basic verification configuration information, the unified verification platform adds annotations to the field information according to the corresponding special basic verification configuration information to obtain special annotation annotation information; it assigns annotations to the field information according to the corresponding special basic verification configuration information. Attributes get special annotation attribute information.

Dynamically add annotations to field information according to the corresponding special basic verification configuration information to obtain special annotation annotation information. For example, @NotBlank and @NotNull both indicate non-empty, but the specific limited range is different. @Pattern indicates the content of the specific special verification logic that needs to be used for this field information. For example, the ten-digit number must start with two 0s, followed by 8 It cannot contain Chinese characters and the length of the field value must be 9 digits, etc. Of course, you can also customize special annotation information for field information. Assign annotation attributes to the field information according to the corresponding special basic verification configuration information to obtain special annotation attribute information. For example, message and regexp are error messages. When the verification fails, the error message will be returned to the connected business system.

Specifically, annotations are dynamically added to field information through Javaassist (Java programming Assistant, Java Assist) technology. Javassist is an open source library for analyzing, editing and creating Java bytecode. Its main advantage is that it is simple and fast. It can directly use java coding to dynamically change the structure of the class or dynamically generate the class. The purpose of using Javaassist technology is mainly to explain what kind of basic verification needs to be done on the current field information and what kind of logic should be used to perform basic verification.

The unified verification platform uses the Hibernate Validator method to perform basic verification on the field information contained in the current business system based on special annotation information. Hibernate Validator is an open source framework provided by Hibernate. It is very convenient to use annotations to implement server-side data verification. In daily development, Hibernate Validator is often used to validate fields based on annotations, which is convenient, fast and efficient. This is also the role of adding special annotation information. Only after adding special annotation information, Hibernate Validator will recognize the field information to verify the field information.

In another implementable manner, if the corresponding special verification configuration information is obtained, special verification is performed on the field information according to the corresponding special verification configuration information.

Here, when the unified verification platform obtains the corresponding special verification configuration information, it does not need to add special annotation information to the field information, and directly performs special verification on the field information based on the corresponding special verification configuration information.

It should be noted that although the corresponding special verification configuration information includes the corresponding special basic verification configuration information and the corresponding special other verification configuration information, and the verification includes special basic verification and special other verification; but the general basic verification is required. needs to be done, and other verifications can be determined according to specific needs.

In some embodiments, the above step 307, that is, "if the corresponding default verification configuration information is obtained, verify the field information according to the corresponding default verification configuration information" is described in detail.

The corresponding default verification configuration information includes the corresponding default basic verification configuration information and the corresponding default other verification configuration information; the verification includes the default basic verification and default other verifications.

In an implementable way, if the corresponding default basic verification configuration information is obtained, annotations and attributes are added to the field information according to the corresponding default basic verification configuration information to obtain the default annotation information; and then the field information is processed based on the default annotation information. Default basic verification.

Here, the operation after obtaining the corresponding default basic verification configuration information is the same as the above-mentioned operation after obtaining the corresponding special basic verification configuration information, except that the specific verification configuration information is different, and will not be repeated here.

In another implementable manner, if the corresponding default other verification configuration information is obtained, default other verification is performed on the field information according to the corresponding default other verification configuration information.

Here, the operation after obtaining the corresponding default other verification configuration information is the same as above to obtain the corresponding special other verification configuration information. The operations after verifying the configuration information are the same, only the specific verification configuration information is different, and will not be repeated here.

In some embodiments, the above step 205, that is, "verify the field information according to the corresponding verification configuration information, and return the verification result information to the currently accessed business system" is described in detail.

When the verification is special basic verification or default basic verification; when the verification fails, the special annotation information of the corresponding field information or the annotation attribute information in the default annotation information is returned to the currently accessed business system; when the verification If the verification passes, the automatically generated basic verification passing information of the corresponding field information will be returned to the currently accessed business system. When the verification is special other verification or default other verification; when the verification fails, the automatically generated other verification exception information of the corresponding field information will be returned to the currently accessed business system; when the verification passes, then Return other automatically generated verification information of the corresponding field information to the currently accessed business system.

In an achievable way, Hibernate Validator technology is used to perform special basic verification or default basic verification on field information, including: field required, field length, field format, field legality, etc.; for example, date field format / must be used, the legality of the date field cannot exceed the range, etc. When the verification fails, the special annotation information of the corresponding field information or the annotation attribute information in the default annotation information is returned to the currently connected business system; the annotation attribute information is the above message information; when the verification passes, the The automatically generated basic verification of the corresponding field information is returned to the currently accessed business system through information, so that the business system can perform the next operation based on the returned information.

In another implementable way, when the verification is a special other verification or a default other verification; when the verification fails, the automatically generated other verification exception information of the corresponding field information is returned to the current access business system; when the verification passes, other automatically generated verification passing information of the corresponding field information will be returned to the currently accessed business system. Since other verifications do not require annotation information, the returned information is the verification result information automatically generated by the unified verification platform.

It should be understood that although various steps in the flowcharts of FIGS. 2 and 3 are shown in sequence as indicated by arrows, these steps are not necessarily executed in the order indicated by arrows. Unless explicitly stated in the application, the execution order of these steps is not strictly limited, and these steps can be executed in other orders. Moreover, at least some of the steps in Figures 2 and 3 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but may be executed at different times. These sub-steps or stage The order of execution is not necessarily sequential, but may be performed in turn or alternately with other steps or sub-steps of other steps or at least part of the stages.

Figure 4 is a schematic structural diagram of a unified verification device provided by one embodiment of the present application. The device can be installed on the unified verification platform in the system shown in Figure 1 to perform the methods shown in Figures 2-3 process. As shown in Figure 4, the device may include: an acquisition module 401, a configuration module 403 and a verification module 405. The main functions of each component module are as follows:

The acquisition module 401 is used to obtain the system business information and field information of the currently accessed business system;

Configuration module 403, used to obtain corresponding verification configuration information based on system business information and field information; and

The annotation module 405 is used to verify the field information according to the corresponding verification configuration information, and return the verification result information to the currently accessed business system.

In some embodiments, the device is also used to:

In some embodiments, the system service information includes system name and service name, and the field information includes field names and field values; the corresponding verification configuration information includes corresponding special verification configuration information and corresponding default verification configuration information; the configuration module 403 is also used to :

Obtain the corresponding special verification configuration information based on the system name, business name and field name;

If the corresponding special verification configuration information is obtained, the field information is verified according to the corresponding special verification configuration information;

If the corresponding special verification configuration information is not obtained, the corresponding default verification configuration information is obtained based on the business name and field name;

If the corresponding default verification configuration information is obtained, the field information is verified according to the corresponding default verification configuration information; and

If the corresponding default verification configuration information is not obtained, the field information contained in the currently accessed business system does not need to be verified.

In some embodiments, the corresponding special verification configuration information includes corresponding special basic verification configuration information and corresponding Special other verification configuration information; verification includes special basic verification and special other verification. Configuration module 403 is also used for:

If the corresponding special basic verification configuration information is obtained, add annotations and attributes to the field information according to the corresponding special basic verification configuration information to obtain special annotation information; then perform special basic verification on the field information based on the special annotation information; and

If the corresponding special verification configuration information is obtained, special verification is performed on the field information according to the corresponding special verification configuration information.

In some embodiments, the corresponding default verification configuration information includes the corresponding default basic verification configuration information and the corresponding default other verification configuration information; the verification includes the default basic verification and default other verifications, and the configuration module 403 is also used to:

If the corresponding default basic verification configuration information is obtained, add annotations and attributes to the field information according to the corresponding default basic verification configuration information to obtain the default annotation information; then perform default basic verification on the field information based on the default annotation information; and

If the corresponding default other verification configuration information is obtained, default other verification is performed on the field information according to the corresponding default other verification configuration information.

In some embodiments, the verification module 405 is also used to:

When the verification is special basic verification or default basic verification;

When the verification fails, the special annotation information of the corresponding field information or the annotation attribute information in the default annotation information is returned to the currently connected business system; and

When the verification passes, the automatically generated basic verification passing information of the corresponding field information is returned to the currently accessed business system.

In some embodiments, the verification module 405 is also used to:

When the verification is special other verification or default other verification;

When the verification fails, other automatically generated verification exception information corresponding to the field information will be returned to the currently accessed business system; and

When the verification passes, other automatically generated verification passing information of the corresponding field information is returned to the currently accessed business system.

According to the specific embodiments provided by this application, the technical solution provided by this application can have the following advantages:

1) Improve demand response speed, reduce development time and investment costs. Through the configured unified verification platform, most additions and changes of verification logic can be satisfied without changing the code, greatly reducing development time and testing. time, greatly improving R&D efficiency.

2) Implement unified verification logic across multiple channels and standardize order verification for each business system. No matter which channel is used to operate the order, the final processing result can be guaranteed to be consistent, ensuring the accuracy of the order result.

3) The verification logic is configurable and supports special verification logic for special channels. The two modes of general configuration + special configuration can be used to verify basic logic such as required fields, length, format, legality, etc., and can also be used with other configuration tables. Verify other verification logic.

It can be understood that implementing any method or product of the present application does not necessarily require achieving all the above advantages simultaneously.

The same and similar parts among the above embodiments can be referred to each other, and each embodiment focuses on its differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment.

It should be noted that one of the embodiments of this application may involve the use of user data. In actual applications, it can be done in compliance with the applicable laws and regulations of the country (for example, the user explicitly agrees, and the user is effectively notified). , the user's explicit authorization, etc.), the user's specific personal data will be used in the scenarios described in this article to the extent permitted by applicable laws and regulations.

According to one embodiment of the present application, a computer device and one or more non-volatile storage media storing computer-readable instructions are also provided.

As shown in Figure 5, it is a block diagram of a computer device according to one embodiment of the present application. Computer equipment is intended to mean any form of digital computer or mobile device. Digital computers may include desktop computers, portable computers, workstations, personal digital assistants, servers, mainframe computers, and other suitable computers. Mobile devices may include tablets, smartphones, wearable devices, etc.

As shown in Figure 5, the device 500 includes a computing unit 501, a ROM 502, a RAM 503, a bus 504, and an input/output (I/O) interface 505. The computing unit 501, the ROM 502, and the RAM 503 are connected to each other through the bus 504. Input/output (I/O) interface Y05 is also connected to bus 504.

The computing unit 501 can execute the application method according to computer instructions stored in the read-only memory (ROM) 502 or loaded from the storage unit 508 into the random access memory (RAM) 503. Various treatments in the method embodiment. Computing unit 501 may be a variety of general and/or special purpose processing components having processing and computing capabilities. The computing unit 501 may include, but is not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processors ( DSP), and any appropriate processor, controller, microcontroller, etc. In some embodiments, the methods provided by the embodiments of the present application can be implemented as computer software readable instructions, which are tangibly included in a non-volatile storage medium, such as the storage unit 508.

RAM 503 may also store various readable instructions and data required for operation of device 500. Some or all of the computer readable instructions may be loaded and/or installed onto device 500 via ROM 502 and/or communication unit 509.

The input unit 506, the output unit 507, the storage unit 508 and the communication unit 509 in the device 500 may be connected to the I/O interface 505. The input unit 506 may be a keyboard, a mouse, a touch screen, a microphone, etc.; the output unit 507 may be a display, a speaker, an indicator light, etc. The device 500 can exchange information, data, etc. with other devices through the communication unit 509.

It should be noted that the device may also include other components necessary for proper operation. It is also possible to include only the components necessary to implement the solution of the present application, and not necessarily include all the components shown in the figure.

Various implementations of the systems and techniques described herein may be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip implemented in a system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software and/or a combination thereof.

Computer instructions for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer instructions may be provided to the computing unit 501, so that when executed by the computing unit 501, such as a processor, the computer instructions cause the steps involved in the method embodiments of the present application to be executed.

The non-volatile storage medium provided by this application may be a tangible medium, which may contain or store computer instructions to execute the steps involved in the method embodiments of this application. Non-volatile storage media may include, but are not limited to, electronic, magnetic, optical, electromagnetic and other forms of storage media.

The above-mentioned specific embodiments do not constitute a limitation on the scope of protection of the present application. It will be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions are possible depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application shall be included in the protection scope of this application.

Claims

A unified verification method, characterized by including:

Obtain the system business information and field information of the currently accessed business system;

Obtain corresponding verification configuration information according to the system business information and the field information; and

The field information is verified according to the corresponding verification configuration information, and the verification result information is returned to the currently accessed business system.
The method according to claim 1, characterized in that before obtaining the system business information and field information of the currently accessed business system, the method includes:

Configure the system business information, field information and verification logic of each business system correspondingly with the universal data model of the unified verification platform to obtain the corresponding verification configuration information corresponding to each business system, and combine the corresponding verification Configuration information is synchronized to the remote dictionary server.
The method according to claim 1, characterized in that the system service information includes system name and service name, the field information includes field names and field values; the corresponding verification configuration information includes corresponding special verification configuration information and corresponding Default verification configuration information; obtaining the corresponding verification configuration information based on the system business information and the field information includes:

Obtain the corresponding special verification configuration information according to the system name, business name and field name;

If the corresponding special verification configuration information is obtained, the field information is verified according to the corresponding special verification configuration information;

If the corresponding special verification configuration information is not obtained, then the corresponding default verification configuration information is obtained according to the business name and the field name;

If the corresponding default verification configuration information is obtained, the field information is verified according to the corresponding default verification configuration information; and

If the corresponding default verification configuration information is not obtained, the field information contained in the currently accessed business system does not need to be verified.
The method according to claim 3, characterized in that the corresponding special verification configuration information includes corresponding special basic verification configuration information and corresponding special other verification configuration information; the verification includes special basic verification and special other Verification; if the corresponding special verification configuration information is obtained, then according to the corresponding special verification The configuration information verifies the field information, including:

If the corresponding special basic verification configuration information is obtained, add annotations and attributes to the field information according to the corresponding special basic verification configuration information to obtain special annotation information; and then add the field information according to the special annotation information. Perform special basic checks; and

If the corresponding special other verification configuration information is obtained, special other verification is performed on the field information according to the corresponding special other verification configuration information.
The method according to claim 3, characterized in that the corresponding default verification configuration information includes corresponding default basic verification configuration information and corresponding default other verification configuration information; the verification includes default basic verification and default other Verification; if the corresponding default verification configuration information is obtained, the field information is verified according to the corresponding default verification configuration information, including:

If the corresponding default basic verification configuration information is obtained, add annotations and attributes to the field information according to the corresponding default basic verification configuration information to obtain default annotation information; and then add labels and attributes to the field information according to the default annotation information. Perform default basic verification; and

If the corresponding default other verification configuration information is obtained, default other verification is performed on the field information according to the corresponding default other verification configuration information.
The method according to any one of claims 4-5, characterized in that the field information is verified according to the corresponding verification configuration information, and the verification result information is returned to the currently accessed service. systems, including:

When the verification is a special basic verification or a default basic verification;

When the verification fails, the special annotation information of the corresponding field information or the annotation attribute information in the default annotation information is returned to the currently connected business system; and

When the verification passes, the automatically generated basic verification passing information corresponding to the field information is returned to the currently accessed business system.
The method according to claim 6, wherein the step of verifying the field information according to the corresponding verification configuration information and returning the verification result information to the currently accessed business system further includes:

When the verification is a special other verification or a default other verification;

When the verification fails, other automatically generated verification exception information corresponding to the field information will be returned to the local Business systems previously connected; and

When the verification passes, other automatically generated verification passing information corresponding to the field information is returned to the currently accessed business system.
A unified verification device, characterized by including:

The acquisition module is used to obtain the system business information and field information of the currently accessed business system;

A configuration module configured to obtain corresponding verification configuration information based on the system business information and field information; and

A verification module, configured to verify the field information according to the corresponding verification configuration information, and return the verification result information to the currently accessed business system.
A computer device includes a memory and one or more processors. Computer-readable instructions are stored in the memory. It is characterized in that when the computer-readable instructions are executed by the processor, the one or more processors Each processor performs the following steps:

Obtain the system business information and field information of the currently accessed business system;

Obtain corresponding verification configuration information according to the system business information and the field information; and

The field information is verified according to the corresponding verification configuration information, and the verification result information is returned to the currently accessed business system.
One or more non-volatile storage media storing computer-readable instructions, characterized in that, when executed by one or more processors, the computer-readable instructions cause one or more processors to perform the following steps:

Obtain the system business information and field information of the currently accessed business system;

Obtain corresponding verification configuration information according to the system business information and the field information; and

The field information is verified according to the corresponding verification configuration information, and the verification result information is returned to the currently accessed business system.