WO2020259147A1

WO2020259147A1 - Field information checking method and apparatus

Info

Publication number: WO2020259147A1
Application number: PCT/CN2020/091658
Authority: WO
Inventors: 曲鸣; 江旻
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2019-06-28
Filing date: 2020-05-21
Publication date: 2020-12-30
Also published as: CN110287383A; CN110287383B

Abstract

A field information checking method and apparatus, applied to the field of financial technologies (Fintech), and used for solving the problem in the prior art of poor adaptability of field information checking. Said method comprises: acquiring configuration field information and service field information; using at least one configuration field in the configuration field information as a current configuration field combination; acquiring a corresponding preset field checking rule according to a preset operation; and using the preset field checking rule to check the service field information. The preset field checking rule matching the configuration field information is the most adaptable for checking the service field information. When no matched preset field checking rule is found, the preset field checking rule is rematched in the configuration field combination from which a configuration field is removed. In this way, the preset field checking rule adaptable to the field information can be found with maximum possibility, thereby improving the adaptability of the field information checking.

Description

Method and device for checking field information

Cross references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on June 28, 2019, the application number is 201910580581.3, and the application name is "a field information inspection method and device", the entire content of which is incorporated into this application by reference in.

Technical field

The invention relates to the field of financial technology (Fintech) and the field of information inspection, and in particular to a method and device for field information inspection.

Background technique

With the development of computer technology, more and more technologies (such as big data technology, distributed technology, blockchain technology, artificial intelligence technology, etc.) are applied in the financial field. The traditional financial industry is gradually turning to financial technology ( Fintech) transformation. At present, in the field of financial technology, some financial systems need to pass in fields through external service interfaces to realize financial transaction functions. Because financial transactions require high operational stability, it is necessary to verify the field information passed into the financial system.

In actual operation, the services of each access party are different, so the field information transmitted by each access party on the same external service interface may also be more or less different. For example, when platform 1 uses an interface, platform 1 needs to transmit three business fields A, B, and C to the interface, and when platform 2 also uses this interface, platform 2 needs to transmit three business fields A, C, and D to the interface. Field. In the prior art, the service fields of all access parties are checked according to the same general field check rule. However, for the same service field, different access parties may have different requirements for the service field. For example, the value range of business field A in platform 1 is required to be 0-100, and the value range in platform 2 is required to be 50-200. It is necessary to first determine whether it is from platform 1 or platform 2 when inspecting business field A, and then perform inspection according to the inspection requirements of the corresponding platform. Moreover, it is necessary to use this method to judge before verifying each business field in subsequent inspections. Obviously, the general field verification rules in the prior art have poor adaptability to field information verification of different access parties.

Summary of the invention

The present application provides a field information verification method and device to solve the problem that the general field verification rules in the prior art have poor adaptability to field information verification of different access parties.

In the first aspect, this application provides a field information verification method, including:

Obtain field information; the field information includes configuration field information and service field information, the configuration field information includes at least one configuration field; using the at least one configuration field as the current configuration field combination, and obtaining the current configuration field according to a preset operation The preset field check rule corresponding to the configuration field combination; wherein the preset operation is: match the current configuration field combination with a preset check rule table; the preset check rule table includes at least one field check Rule; if the field verification rule can be matched, the field verification rule is output as the preset field verification rule; if the field verification rule cannot be matched, and the current configuration field combination includes at least two configuration fields, Then remove one configuration field from the current configuration field combination, and re-use the configuration field combination after removing the one configuration field as the current configuration field combination, and return the combination of the configuration field and The step of matching a preset check rule table; check the business field information according to the preset field check rule.

In the above method, the configuration field information is first matched with the preset inspection rule table. Since the current configuration field combination is the configuration field information, the current configuration field combination can include the most configuration fields, so it matches the preset inspection rule table The obtained field inspection rules can best adapt to the field information inspection. When the match fails, the configuration field combination after removing a configuration field is re-used as the current configuration field combination and matched with the preset inspection rule table to be able to find Adapt to the preset field inspection rules of field information as much as possible to improve the adaptability of field information inspection.

In an optional implementation manner, the matching the current configuration field combination with a preset inspection rule table includes: mapping the current interface field combination into a string according to the preset mapping rule; Determine the sub-check rule table corresponding to the type of the character string in the preset check rule table; determine whether the character string has a corresponding field check rule in the sub-check rule table.

In the above method, the current interface field combination is mapped to a string according to the preset mapping rule, and in the sub-check rule table corresponding to the type of the string, it is determined whether there is a corresponding field check rule, so that the type of the string can be The corresponding sub-inspection rule table can be flexibly set to classify the field inspection rules.

In an optional implementation manner, each field inspection rule in the preset inspection rule table marks an expiration period attribute and/or an effective period attribute, and the expiration period attribute indicates that the field inspection rule cannot be matched at the current moment. The effective period attribute indicates that the field verification rule can be matched at the current moment; in specific implementation, the matching the current configuration field combination with the preset verification rule table also includes: combining the current configuration field combination with the first The aging inspection rule table is matched; the first aging inspection rule table is a combination of field inspection rules in the preset inspection rule table after the field inspection rules that mark the attribute of the expiration period are removed; and/or, the current The configuration field combination of is matched with the second aging inspection rule table; the second aging inspection rule table is a combination of field inspection rules marked with valid period attributes in the preset inspection rule table.

In the above method, by marking the invalidation period attribute and/or the effective period attribute of each field test rule in the preset test rule table, the current configuration field can be combined with the first aging test rule table and/or the second time period attribute. The aging inspection rule table is matched, which can increase the consideration of effective or invalid dimensions, and further increase the diversity and flexibility of the matched field inspection rules.

In an optional implementation manner, the verifying the business field information according to the preset field verification rule includes: if the preset field verification rule marks the first business field as the business information If the service information does not include the first service field, or the value of the first service field is empty, it is determined that the service information is illegal; for the second service field, The second service field is any service field that exists in both the service field information and the preset field check rule, if any one of the at least one check of the second service field is invalid , It is determined that the business information is illegal; the at least one check includes: whether the format of the value of the second business field conforms to the preset format of the second business field, if not, it is illegal ; Whether the length of the value of the second service field meets the preset length of the second service field, if not, it is illegal; if the preset field check rule marks the second service field as Optional field, it is determined whether the value of the second service field is within the preset value range of the optional field, if not, it is illegal.

The above method can judge whether the business information is illegal according to the first business field, and can judge whether the business information is illegal according to the second business field, and can also judge whether the business information is illegal when the second business field is an optional field.

In an optional implementation manner, if there is one and only one configuration field in the current configuration field combination, the default general field check rule in the preset check rule table is used as the preset field check rule.

The above method provides the field check rule when there is only one configuration field in the current configuration field combination, that is, the default general field check rule, so that the field information can match the preset field check rule with a greater probability.

In the second aspect, this application provides a field information verification device, including:

An obtaining module for obtaining field information; the field information includes configuration field information and service field information, and the configuration field information includes at least one configuration field;

The processing module is configured to use the at least one configuration field as the current configuration field combination, and obtain the preset field inspection rule corresponding to the current configuration field combination according to a preset operation; the preset operation is: The configuration field combination of is matched with a preset check rule table; the preset check rule table includes at least one field check rule; if the field check rule can be matched, the field check rule is output as the preset field check rule ; If the field verification rule cannot be matched, and the current configuration field combination includes at least two configuration fields, one configuration field is removed from the current configuration field combination, and after removing the one configuration field The combination of configuration fields is re-used as the current configuration field combination, and the step of matching the configuration field combination with the preset inspection rule table is returned; and the business field information is checked according to the preset field inspection rule. Perform inspection.

In an optional implementation manner, the processing module is specifically configured to: map the current interface field combination to a character string according to a preset mapping rule; determine the character string from the preset check rule table The sub-check rule table corresponding to the type; determine whether the character string has a corresponding field check rule in the sub-check rule table.

In an optional implementation manner, each field inspection rule in the preset inspection rule table marks an expiration period attribute and/or an effective period attribute, and the expiration period attribute indicates that the field inspection rule cannot be matched at the current moment. The effective period attribute indicates that the field inspection rule can be matched at the current moment; the processing module is further used to: match the current configuration field combination with the first aging inspection rule table; the first aging inspection rule table is the The combination of field inspection rules in the preset inspection rule table after removing the field inspection rules that mark the attributes of the expiration period; and/or, matching the current configuration field combination with the second aging inspection rule table; the second The time-effectiveness inspection rule table is a combination of field inspection rules marked with the effective period attribute in the preset inspection rule table.

In an optional implementation manner, the processing module is specifically configured to: if the first service field is marked as a required field in the service information in the preset field check rule, and the service information does not include all The first business field, or the value of the first business field is empty, it is determined that the business information is illegal; for the second business field, the second business field is in the business field information and For any business field that exists in the preset field verification rules, if any one of the at least one verification of the second business field is not legal, it is determined that the business information is illegal; A test includes: whether the format of the value of the second service field conforms to the preset format of the second service field, if not, it is illegal; whether the length of the value of the second service field conforms If the preset length of the second business field does not match, it is illegal; if the second business field is marked as an optional field in the preset field inspection rule, the second business field is determined Whether the value is within the preset value range of the optional field, if not, it is illegal.

In an optional implementation manner, the processing module is further configured to: if there is one and only one configuration field in the current configuration field combination, use the default common field check rule in the preset check rule table as The preset field inspection rule.

For the beneficial effects of the foregoing second aspect and the various embodiments of the second aspect, reference may be made to the beneficial effects of the foregoing first aspect and the various embodiments of the first aspect, which will not be repeated here.

In a third aspect, the present application provides a computer device including a program or instruction, and when the program or instruction is executed, it is used to execute the above-mentioned method of the first aspect and each implementation manner of the first aspect.

In a fourth aspect, the present application provides a storage medium including a program or instruction, and when the program or instruction is executed, it is used to execute the method of the first aspect and the implementation manners of the first aspect.

Description of the drawings

FIG. 1 is a schematic diagram of the process flow of a method for verifying field information provided by an embodiment of this application;

FIG. 2 is a schematic flowchart of specific steps of a method for verifying field information provided by an embodiment of the application;

FIG. 3 is a schematic structural diagram of a field information checking device provided by an embodiment of this application;

Figure 4 is a schematic structural diagram of a computer device provided by an embodiment of the application.

Detailed ways

In order to better understand the above technical solutions, the above technical solutions will be described in detail below with reference to the drawings and specific implementations of the specification. It should be understood that the embodiments of the application and the specific features in the embodiments are detailed to the technical solutions of the application. Note, rather than limiting the technical solution of the present application, the embodiments of the present application and the technical features in the embodiments can be combined with each other if there is no conflict.

To facilitate the description, first introduce the keywords and abbreviations that appear in this application.

1. Configure field information.

The configuration field information in the embodiment of the present application is used to determine a preset field check rule that the field information matches, and the configuration field information may include at least one configuration field.

For example, the configuration field information may include one or more of the following:

MERCHANT_ID: refers to the ID number of the partner's platform to access the bank;

PS_CODE: refers to the product type;

TXN_ID: refers to the transaction code;

TXN_TYPE: refers to the transaction type.

2. Business field information.

The business field information in the embodiment of the present application refers to the combination of the fields to be checked in the field information, and the field checking rules for the business fields in the business field information depend on the configuration field information.

For example, the service field information can include one or more of the following:

APP_NO: refers to the application number;

NAME: refers to the name;

ID_TYPE: refers to the type of certificate submission.

During the operation of financial institutions (such as banking institutions, insurance institutions or securities institutions) (such as bank loan business, deposit business, etc.), some financial systems need to pass in fields through the external service interface to implement financial transaction functions. Because financial transactions have high requirements for operational stability, it is necessary to verify the field information passed into the financial system. However, due to the different services of each access party, the same external service interface may have more or less differences in field information. In the prior art, the service fields of all access parties are checked according to the same general field check rule. However, the same service field may have different requirements for different access parties, which leads to poor adaptability of the general field verification rules in the prior art to field information verification of different access parties. Obviously, this situation cannot meet the needs of banks and other financial institutions, which may affect the efficient operation of various businesses of financial institutions.

To this end, the embodiment of the present application provides a field information verification method to solve the technical problem that the general field verification rule in the prior art has poor adaptability to field information verification of different access parties.

Fig. 1 is a schematic flow chart of the steps of a method for verifying field information provided by an embodiment of the application. It should be noted that the applicable field information in the method shown in FIG. 1 may be an interface field when inputting an application system interface, or may also be field information in other scenarios, and the scenario is not limited here. The method shown in FIG. 1 can be used, for example, to perform differentiated configuration and management of a system interface, and can realize differentiated processing of the field information requirements sent by different access parties through quick configuration. As shown in Figure 1, the method includes:

Step 101: Obtain field information, where the field information includes configuration field information and service field information, and the configuration field information includes field information of at least one configuration field.

Step 102: Use the at least one configuration field as a current configuration field combination, and obtain a preset field check rule corresponding to the current configuration field combination according to a preset operation.

Step 103: Check the service field information according to the preset field check rule.

Exemplarily, Table 1 is a schematic table of a data structure of field information provided in an embodiment of the application:

Table 1

The specific data structure of the field information will be described in detail below in conjunction with Table 1. As shown in Table 1, in the data structure of the field information, the field item name of each row in rows 1 to 4 is a configuration field, and the field item names in rows 1 to 4 constitute the configuration field information. The column item name of each row in the 5th to 13th rows is a business field, and the column item names in the 5th to 13th rows constitute the business field information. Among them, R means required items, O means optional items.

It can be seen from Table 1 that for the interface with the transaction service code TXN_ID of 90032, there are two types of functions. When the transaction type is 0, the approval function is executed, and when the transaction type is 1, only information synchronization is performed. Shown in the field information, that is, the field information with TXN_ID 90032 can be divided into two types according to the transaction type TXN_TYPE. For the same interface, different transaction types have different requirements for fields, and each transaction type has different fields for different partners. For the same partner, different product category fields may also have differences. Therefore, field information can be classified according to configuration fields, and business fields can be checked according to corresponding field checking rules.

Exemplarily, in the foregoing step 102, the preset operation may specifically be:

The current configuration field combination is matched with at least one field inspection rule in the preset inspection rule table, and if the field inspection rule can be matched, the field inspection rule is output as the preset field inspection rule. If the field verification rule cannot be matched, and the current configuration field combination includes at least two configuration fields, one configuration field will be removed from the current configuration field combination, and the configuration field combination after removing one configuration field will be used as the current configuration field combination. And return to the step of matching the configuration field combination with the preset inspection rule table. Among them, removing a configuration field from the current configuration field combination can be specifically removed according to a preset priority order.

It should be noted that the preset operation may also include: if there is one and only one configuration field in the current configuration field combination, the default general field check rule in the preset check rule table is used as the preset field check rule.

For example, suppose there are 4 configuration fields in the configuration field combination: A, B, C, and D. The current configuration field combination is ABCD. First, ABCD is matched with the preset inspection rule table. If the field inspection rule cannot be matched, and the preset priority indicates that D is removed, the current configuration field combination is updated to ABC. Then ABC is matched with the preset inspection rule table. If the field inspection rule is still not matched, and the preset priority indicates that C is removed, the current configuration field combination is updated to AB. Then match AB with the preset inspection rule table. If the field inspection rule is still not matched, and the preset priority indicates that B is removed, the current configuration field combination is updated to A.

Exemplarily, the preset field inspection rule corresponding to the configuration field combination A can be determined through the following optional implementation manners:

If there is one and only one configuration field in the current configuration field combination, the default general field check rule in the preset check rule table is used as the preset field check rule. That is, when the current configuration field combination is A, the preset field verification rule is the default general field verification rule.

In the following, in conjunction with Table 1, an optional implementation manner for matching the current configuration field combination with the preset inspection rule table in step 102 is described with a specific example:

According to the preset mapping rules, map the current interface field combination to a string, determine the sub-inspection rule table corresponding to the type of the string from the preset inspection rule table, and determine whether the string has a corresponding field in the sub-inspection rule table testing regulations.

Assuming that the four fields of TXN_ID, TXN_TYPE, MERCHANT_ID, and PS_CODE are used as configuration field information, the corresponding preset field verification rules can be obtained according to the content of the upload. Exemplarily, Table 2 is a schematic table of a correspondence relationship between a character string and a sub-check rule table provided in an embodiment of the application.

Table 2

Among them, the INTERFACE_KEY column represents the string, and the INTERFACE_VALUE column represents the sub-inspection rule table when the type of the string is a string mapped by TXN_ID, TXN_TYPE, MERCHANT_ID, and PS_CODE. In addition, AVAILABLE indicates whether the field inspection rule in each row of the sub-inspection rule table exists, and Y means it exists.

Based on this KEY and VALUE interface configuration design, the KEY value can be flexibly combined in the key fields of TXN_ID, TXN_TYPE, MERCHANT_ID, PS_CODE. For example, under the same TXN_ID and TXN_TYPE, only different MERCHANT_IDs need to be distinguished by interface field differences. There is no difference between different PS_CODEs, so the KEY value only needs to include TXN_ID, TXN_TYPE, MERCHANT_ID. Similarly, if there is no difference between different MERCHANT_IDs under the same TXN_ID and TXN_TYPE, the KEY value only needs to include TXN_ID and TXN_TYPE. By analogy, if it is an interface field common to all partners and products, then only TXN_ID can be configured for the KEY value.

In the foregoing optional implementation manner, the most refined KEY value may be used for matching first to determine whether there is a corresponding interface verification rule configuration. In other words, map TXN_ID, TXN_TYPE, MERCHANT_ID, and PS_CODE to different strings. If the KEY value does not match the rule, continue matching according to TXN_ID, TXN_TYPE, and MERCHANT_ID. By analogy, if it fails to match, continue to use TXN_ID, TXN_TYPE or TXN_ID to match. When TXN_ID is used to match the field verification rules, it is actually equivalent to the caller without customizing the interface rules. , Using the default common interface verification rules.

Exemplarily, the method for verifying the field information can be continuously optimized in the future. For example, the effective period attribute and the expiration period attribute can be added to the preset field verification rule configuration, so that it can be configured in advance for some predictable changes, and the effective period of the new configuration item can be set to the required period. Configure the expiration period attribute locally, so that after the effective period or expiration period of the setting, the old field verification rule configuration automatically becomes invalid, and the service will automatically use the new effective field verification rule. Using this method can solve the limitation that the current field inspection change can only be changed at a specified time (for example, when the user cooperates with the change at the same time), making it more flexible in actual use.

Exemplarily, based on the effective period and the invalid period, another optional implementation manner of matching the current configuration field combination with the preset inspection rule table is as follows:

Each field inspection rule in the preset inspection rule table is used to mark the expiration period attribute and/or the effective period attribute. The expiration period attribute indicates that the field inspection rule cannot be matched at the current moment, and the effective period attribute indicates that the field inspection rule can be matched at the current moment. . In this way, matching the current configuration field combination with the preset inspection rule table may also include:

Match the current configuration field combination with the first aging inspection rule table, which is a combination of field inspection rules in the preset inspection rule table after removing the field inspection rules that mark the expiration period attribute; and/or ,

The current configuration field combination is matched with the second aging inspection rule table. The second aging inspection rule table is a combination of field inspection rules marked with the effective period attribute in the preset inspection rule table.

Exemplarily, after the above step 102, the legality of the business information of the system called by the transaction requester can also be verified in combination with the preset field verification rules. Among them, the preset field verification rules can be stored in an Extensible Markup Language (xml) format, or can be stored in other data storage files, such as excel. For example, design the dimensional control of the business fields corresponding to each type of transaction in the excel table, put the excel file under the application service project, and write a set of modules to analyze the file format and content of the excel table. When the application process starts, the configuration content is loaded into the memory by loading the module, and organized in a certain way, so that when the requester calls the interface, it matches the field information sent by the requester. The same effect can be achieved.

In this embodiment of the application, the preset field verification rule may include a verification rule for each business field in the business field. For example, each business field can have the following attributes:

fieldName: indicates the name of the business field;

fieldType: indicates the type of business field (such as String, BigDecimal, Array, etc.);

fmtRegular: indicates the length of the business field format;

fieldLevel: indicates the level (normally 1 level, if there is an array, the business fields in the array are 2 levels, and so on);

forceExist: indicates whether the business field is a required field (true indicates that the field must appear in the interface request message and have a value);

dic: Indicates that the service field is not required. If the service field needs to limit the value sent, configure dic. For example, the above example indicates that the value of this field can only be uploaded as normal (NORMAL) or computer command (SUSPEND), and other values are illegal.

The above is a detailed description of the verification rule of one of the business fields. A preset field verification rule is a collection of multiple such field verification rules.

Exemplarily, an optional implementation manner of the foregoing step 103 is as follows:

For the first business field, if the first business field is marked as a required field in the business information in the preset field check rule, and the business information does not include the first business field, or the value of the first business field is empty, then Determine that the business information is illegal.

For the second business field, if the second business field is any business field that exists in both the business field information and the preset field verification rules, if any one of at least one verification of the second business field is verified If the verification is illegal, the business information is determined to be illegal.

Among them, at least one test includes one or more of the following:

Whether the format of the value of the second business field conforms to the preset format of the second business field, if not, it is illegal;

Whether the length of the value of the second business field meets the preset length of the second business field, if not, it is illegal;

If the second business field is marked as an optional field in the preset field verification rule, it is determined whether the value of the second business field is within the preset value range of the optional field, if not, it is illegal.

With reference to the schematic diagram of the data structure of the field information shown in Table 2, the specific process of the foregoing implementation manner may include:

(1) If there must be a business field whose (forceExist) configuration is true (true) in the preset field verification rules, if there is no or there is this business field but the value is empty in the field information sent by the caller , It will return the prompt of "verification failed, field cannot be empty".

(2) If the business field in the field information does not exist in the interface verification rule, the business field will be filtered out and will not enter the verification that participates in the preset field verification rule.

(3) If the business field in the field information exists in the interface verification rules, check whether the format of the field value is correct according to the field format (fieldType), if the format is correct, check whether the length of the field value is consistent; if the check fails, It returns the prompt of "The field format is incorrect".

(4) If there is a dic configuration item in the business field, it means that the value of the business field has a clear content range test. The value sent in the business field must be within the range of the dic configuration. If it is not in the range, the test fails and returns "The field value is incorrect" prompt.

In the above method, the configuration field information is first matched with the preset inspection rule table. Since the current configuration field combination is the configuration field information, the current configuration field combination can include the most configuration fields, so it matches the preset inspection rule table The obtained field inspection rules can best adapt to the field information inspection. When the match fails, the configuration field combination after removing a configuration field is re-used as the current configuration field combination and matched with the preset inspection rule table, so as to be able to do the best It is possible to find a preset field inspection rule that adapts to field information to improve the adaptability of field information inspection. In addition, the same field inspection rules can also be flexibly changed according to factors such as the user and business scenarios, so that the interface inspection rules can be quickly adapted and managed without requiring adjustments at the application layer.

The optional implementation manners in the field information verification method provided in the embodiments of the present application can be combined with each other. FIG. 2 exemplarily shows a schematic flowchart of a combined field information verification method provided by an embodiment of the present application. Among them, the first configuration field shown in FIG. 2 refers to TXN_ID, the second configuration field shown in FIG. 2 refers to TXN_TYPE, the third configuration field shown in FIG. 2 refers to MERCHANT_ID, and the fourth configuration field shown in FIG. 2 Refers to PS_CODE.

In view of the foregoing method, an embodiment of the present application also provides a field information checking device, and the specific implementation of the device can refer to the foregoing method.

FIG. 3 is a schematic structural diagram of a field information checking device provided by an embodiment of the application. As shown in FIG. 3, the device includes:

The obtaining module 301 is configured to obtain field information; the field information includes configuration field information and service field information, and the configuration field information includes at least one configuration field;

The processing module 302 is configured to use the at least one configuration field as a current configuration field combination, and obtain a preset field inspection rule corresponding to the current configuration field combination according to a preset operation;

Wherein, the preset operation is: matching the current configuration field combination with a preset inspection rule table; the preset inspection rule table includes at least one field inspection rule; if the field inspection rule can be matched, then The field check rule is output as the preset field check rule; if the field check rule cannot be matched, and the current configuration field combination includes at least two configuration fields, then one is removed from the current configuration field combination Configure fields, and re-use the configuration field combination after removing the one configuration field as the current configuration field combination, and return to the step of matching the configuration field combination with the preset inspection rule table; The preset field inspection rules are described, and the business field information is inspected.

In an optional implementation manner, the processing module 302 is specifically configured to:

According to a preset mapping rule, map the current interface field combination to a character string; determine the sub-check rule table corresponding to the type of the character string from the preset check rule table; determine that the character string is in the Whether there is a corresponding field inspection rule in the sub-inspection rule table.

In an optional implementation manner, each field inspection rule in the preset inspection rule table marks an expiration period attribute and/or an effective period attribute, and the expiration period attribute indicates that the field inspection rule cannot be matched at the current moment. The effective period attribute indicates that the field inspection rule can be matched at the current moment;

The processing module 302 is also used for:

The current configuration field combination is matched with the first aging inspection rule table; the first aging inspection rule table is the field inspection rule after the field inspection rule marking the invalidation period attribute is removed from the preset inspection rule table And/or, matching the current configuration field combination with a second aging inspection rule table; the second aging inspection rule table is a field inspection rule marked with an effective period attribute in the preset inspection rule table The combination.

If the first service field is marked as a required field in the service information in the preset field check rule, and the service information does not include the first service field, or the value of the first service field If it is empty, it is determined that the business information is illegal;

For the second business field, the second business field is any business field that exists in both the business field information and the preset field verification rule, if at least one of the second business fields is verified If any item of verification is illegal, it is determined that the business information is illegal;

The at least one check includes: whether the format of the value of the second service field conforms to the preset format of the second service field, if not, it is illegal; the value of the second service field is Whether the length meets the preset length of the second service field, if not, it is illegal; if the second service field is marked as an optional field in the preset field check rule, the second service field is determined Whether the value of the field is within the preset value range of the optional field, if not, it is illegal.

In an optional implementation manner, the processing module 302 is further configured to:

If there is one and only one configuration field in the current configuration field combination, the default general field check rule in the preset check rule table is used as the preset field check rule.

Based on the same technical concept, the embodiment of the present invention provides a computer device. As shown in FIG. 4, it includes at least one processor 401 and a memory 402 connected to the at least one processor. The embodiment of the present invention does not limit the processor. For the specific connection medium between the 401 and the memory 402, the connection between the processor 401 and the memory 402 in FIG. 4 is taken as an example. The bus can be divided into address bus, data bus, control bus, etc.

In the embodiment of the present invention, the memory 402 stores instructions that can be executed by at least one processor 401, and the at least one processor 401 can execute the steps included in the aforementioned field information verification method by executing the instructions stored in the memory 402.

Among them, the processor 401 is the control center of the terminal device, which can use various interfaces and lines to connect to various parts of the terminal device, and realize data by running or executing instructions stored in the memory 402 and calling data stored in the memory 402. deal with. Optionally, the processor 401 may include one or more processing units, and the processor 401 may integrate an application processor and a modem processor. The application processor mainly processes an operating system, a user interface, and an application program. The adjustment processor mainly handles issuing instructions. It can be understood that the foregoing modem processor may not be integrated into the processor 401. In some embodiments, the processor 401 and the memory 402 may be implemented on the same chip, and in some embodiments, they may also be implemented on separate chips.

The processor 401 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array or other programmable logic devices, discrete gates or transistors Logic devices and discrete hardware components can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiment of checking with field information can be directly embodied as executed and completed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

The memory 402, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The memory 402 may include at least one type of storage medium, for example, it may include flash memory, hard disk, multimedia card, card-type memory, random access memory (Random Access Memory, RAM), static random access memory (Static Random Access Memory, SRAM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic memory, disk , CD, etc. The memory 402 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory 402 in the embodiment of the present invention may also be a circuit or any other device capable of realizing a storage function for storing program instructions and/or data.

The embodiment of the present application provides a storage medium including a program or instruction, and when the program or instruction is executed, it is used to execute a field information verification method and any optional method provided in the embodiment of the present application.

Finally, it should be noted that those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, equipment (systems), and computer program products according to this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the scope of the application. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these modifications and variations.

Claims

A method for checking field information, which is characterized in that it comprises:

Obtaining field information; the field information includes configuration field information and service field information, and the configuration field information includes at least one configuration field;

The at least one configuration field is used as the current configuration field combination, and the preset field verification rule corresponding to the current configuration field combination is obtained according to a preset operation; the preset operation is: combining the current configuration field combination with The preset check rule table is matched; the preset check rule table includes at least one field check rule; if the field check rule can be matched, the field check rule is output as the preset field check rule; if it cannot be matched Field verification rules, and the current configuration field combination includes at least two configuration fields, then one configuration field is removed from the current configuration field combination, and the configuration field combination after the one configuration field is removed is renewed As the current configuration field combination, and return to the step of matching the configuration field combination with the preset inspection rule table;

According to the preset field check rule, check the service field information.
8. The method of claim 1, wherein the matching the current configuration field combination with a preset inspection rule table comprises:

According to the preset mapping rule, map the current interface field combination into a string;

Determine the sub-check rule table corresponding to the type of the character string from the preset check rule table;

It is determined whether the character string has a corresponding field check rule in the sub check rule table.
The method according to claim 1, wherein each field inspection rule in the preset inspection rule table marks an expiration period attribute and/or an effective period attribute, and the expiration period attribute indicates that the field inspection rule is at the current moment. Unmatchable, the effective period attribute indicates that the field verification rule can be matched at the current moment;

The matching the current configuration field combination with the preset inspection rule table further includes:

The current configuration field combination is matched with the first aging inspection rule table; the first aging inspection rule table is the field inspection rule after the field inspection rule marking the invalidation period attribute is removed from the preset inspection rule table The combination;

And/or, matching the current configuration field combination with a second aging inspection rule table; the second aging inspection rule table is a combination of field inspection rules marked with an effective period attribute in the preset inspection rule table.
The method according to any one of claims 1 to 3, wherein the checking the service field information according to the preset field checking rule comprises:

If the first service field is marked as a required field in the service information in the preset field check rule, and the service information does not include the first service field, or the value of the first service field If it is empty, it is determined that the business information is illegal;

For the second business field, the second business field is any business field that exists in both the business field information and the preset field verification rule, if at least one of the second business fields is verified If any one of the checks is illegal, it is determined that the service information is illegal; the at least one check includes: whether the value format of the second service field meets the preset format of the second service field, If not, it is illegal; whether the length of the value of the second service field meets the preset length of the second service field, if it does not, it is illegal;

If the second business field is marked as an optional field in the preset field verification rule, it is determined whether the value of the second business field is within the preset value range of the optional field, if not, Is not legal.
The method according to any one of claims 1-3, wherein the preset operation further comprises:

If there is one and only one configuration field in the current configuration field combination, the default general field check rule in the preset check rule table is used as the preset field check rule.
A field information checking device is characterized in that it comprises:

An obtaining module for obtaining field information; the field information includes configuration field information and service field information, and the configuration field information includes at least one configuration field;

The processing module is configured to use the at least one configuration field as the current configuration field combination, and obtain the preset field inspection rule corresponding to the current configuration field combination according to a preset operation; the preset operation is: The configuration field combination of is matched with a preset check rule table; the preset check rule table includes at least one field check rule; if the field check rule can be matched, the field check rule is output as the preset field check rule ; If the field verification rule cannot be matched, and the current configuration field combination includes at least two configuration fields, one configuration field is removed from the current configuration field combination, and after removing the one configuration field The combination of configuration fields is re-used as the current configuration field combination, and the step of matching the configuration field combination with the preset inspection rule table is returned; and the business field information is checked according to the preset field inspection rule. Perform inspection.
The device according to claim 6, wherein the processing module is specifically configured to:

According to the preset mapping rule, map the current interface field combination into a string;

Determine the sub-check rule table corresponding to the type of the character string from the preset check rule table;

It is determined whether the character string has a corresponding field check rule in the sub check rule table.
The device according to claim 6, wherein each field inspection rule in the preset inspection rule table marks an expiration period attribute and/or an effective period attribute, and the expiration period attribute indicates that the field inspection rule is at the current moment. Unmatchable, the effective period attribute indicates that the field check rule can be matched at the current moment, and the processing module is further configured to:

The current configuration field combination is matched with the first aging inspection rule table; the first aging inspection rule table is the field inspection rule after the field inspection rule marking the invalidation period attribute is removed from the preset inspection rule table The combination;

And/or, matching the current configuration field combination with a second aging inspection rule table; the second aging inspection rule table is a combination of field inspection rules marked with an effective period attribute in the preset inspection rule table.
The device according to any one of claims 6-8, wherein the processing module is specifically configured to:

If the first service field is marked as a required field in the service information in the preset field check rule, and the service information does not include the first service field, or the value of the first service field If it is empty, it is determined that the business information is illegal;

For the second business field, the second business field is any business field that exists in both the business field information and the preset field verification rule, if at least one of the second business fields is verified If any one of the checks is illegal, it is determined that the service information is illegal; the at least one check includes: whether the value format of the second service field meets the preset format of the second service field, If not, it is illegal; whether the length of the value of the second service field meets the preset length of the second service field, if it does not, it is illegal;

If the second business field is marked as an optional field in the preset field verification rule, it is determined whether the value of the second business field is within the preset value range of the optional field, if not, Is not legal.
8. The device according to any one of claims 6-8, wherein the processing module is further configured to:

If there is one and only one configuration field in the current configuration field combination, the default general field check rule in the preset check rule table is used as the preset field check rule.
A computer device characterized by comprising a program or an instruction, and when the program or an instruction is executed, the method according to any one of claims 1 to 5 is executed.
A storage medium, characterized by comprising a program or instruction, and when the program or instruction is executed, the method according to any one of claims 1 to 5 is executed.