Information verification method and device, computer equipment and readable storage medium

Abstract

The invention relates to the technical field of computers and data processing, can be applied to the fields of medical treatment, finance and the like, and discloses an information verification method and device, computer equipment and a readable storage medium. The client responds to the information verification request to verify whether the local available rule set version number is the same as the first time point rule set version number of the server; if not, updating the local compilation script corresponding to the version number of the local available rule set by using a first time point rule set of the server, and caching the local compilation script as an updated compilation script; determining a local update rule set version number corresponding to the update compiling script according to the first time point rule set version number of the server; returning the version number of the local update rule set to the server for verification; and if a message that the local update rule set version number is successfully verified is received, calling the update compiling script to execute information verification on the information verification request. According to the method provided by the invention, zero-shutdown updating is realized, the coupling degree of the client and the server is reduced, and the information verification accuracy is improved.

Description

Technical Field

[0001] The present invention relates to the field of computers and data processing technology, and in particular to an information verification method, device, computer equipment and readable storage medium, which can be applied to the fields of medicine, finance and so on. Background Art

[0002] Traditional information verification typically uses static rules. For example, traditional health insurance customer information verification systems use static rules to verify users' historical health status and insurance information. Another example is traditional credit customer information verification systems, which use static rules to verify users' historical repayment status and basic information. Using static rules for information verification often leads to the following problems:

[0003] First, it affects business continuity. Since static rules require downtime for deployment when updated, static rule updates are relatively delayed and can cause business interruptions.

[0004] Second, poor fault tolerance. Since static rules lack dynamic compilation and version rollback mechanisms, exception handling is rigid and fault tolerance is poor.

[0005] Third, lack of flexibility. Since the verification logic of static rules is fixed on the client, the update flexibility of static rules is insufficient.

[0006] Therefore, there is an urgent need to propose an information verification method that can update verification rules in real time without any sense, decouple the high coupling between the client and the server, and conduct fast and accurate real-time verification. Summary of the Invention

[0007] The present invention provides an information verification method, device, computer equipment and readable storage medium, which realize information verification with real-time effectiveness of verification rule updates, high fault tolerance and strong flexibility.

[0008] In a first aspect, an information verification method is provided. The information verification method is applied to a client, the client is in communication with a server, and the information verification method includes:

[0009] Responding to the information verification request, obtaining a server-side rule set version number at a first time point from the server;

[0010] If the local available rule set version number is different from the server-side first-time point rule set version number, obtain the server-side first-time point rule set from the server, use the server-side first-time point rule set to update the local compiled script corresponding to the local available rule set version number and cache it as an updated compiled script, and determine the local updated rule set version number corresponding to the updated compiled script based on the server-side first-time point rule set version number;

[0011] Send the local update rule set version number to the server, so that the server verifies the local update rule set version number;

[0012] If the local update rule set version number verification success message is received, call the update compilation script to perform information verification on the information verification request.

[0013] In a second aspect, an information verification method is provided, which is applied to a server, the server being in communication connection with a client, and the information verification method comprising:

[0014] After the client responds to the information verification request, send the server first time point rule set version number;

[0015] After the client determines that the local available rule set version number and the server first time point rule set version number are different, send the server first time point rule set, so that the client updates the local compilation script corresponding to the local available rule set version number using the server first time point rule set and caches it as an update compilation script, and determines the local update rule set version number corresponding to the update compilation script according to the server first time point rule set version number;

[0016] Receive the local update rule set version number from the client, and verify the local update rule set version number;

[0017] If the local update rule set version number verification is successful, instruct the client to call the update compilation script to perform information verification on the information verification request.

[0018] In a third aspect, an information verification device is provided, which is deployed in a client, the client being in communication connection with a server, and the information verification device comprising:

[0019] The acquisition unit is configured to acquire the server first time point rule set version number from the server in response to an information verification request;

[0020] The update unit is configured to, if the local available rule set version number and the server first time point rule set version number are different, acquire the server first time point rule set from the server, update the local compilation script corresponding to the local available rule set version number using the server first time point rule set and cache it as an update compilation script, and determine the local update rule set version number corresponding to the update compilation script according to the server first time point rule set version number;

[0021] The reply unit is configured to send the local update rule set version number to the server, so that the server verifies the local update rule set version number;

[0022] The verification unit is configured to, if the local update rule set version number verification success message is received, call the update compilation script to perform information verification on the information verification request.

[0023] In a fourth aspect, an information verification device is provided, which is arranged on a server and is in communication connection with a client. The information verification device comprises:

[0024] a first sending unit configured to send a first time point rule set version number of the server after the client responds to an information verification request;

[0025] a second sending unit configured to send the first time point rule set of the server after the client determines that the local available rule set version number is different from the first time point rule set version number of the server, so that the client updates the local compiled script corresponding to the local available rule set version number by using the first time point rule set of the server and caches the updated compiled script as an updated compiled script, and determines a local updated rule set version number corresponding to the updated compiled script according to the first time point rule set version number of the server;

[0026] a verification unit configured to receive the local updated rule set version number from the client and verify the local updated rule set version number;

[0027] an instruction unit configured to instruct the client to execute information verification on the information verification request by using the updated compiled script if the local updated rule set version number is verified successfully.

[0028] In a fifth aspect, a computer device is provided, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor implements the steps of the above information verification method when executing the computer program.

[0029] In a sixth aspect, a computer readable storage medium is provided, which stores a computer program. The computer program is executable on a processor to implement the steps of the above information verification method.

[0030] In the above information verification method, device, computer device, and readable storage medium, the client downloads the latest rule set version in real time by interacting with the server, automatically compiles the rule set version into an executable script and loads the executable script into a cache, so that zero downtime update is achieved. The client returns the version number to the server, so that the consistency of the rule set versions of the client and the server is ensured. The client independently manages rule loading and execution, and the server focuses on rule distribution and version control, so that the coupling degree of the client and the server is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0031] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the description of the embodiments of the present application. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without any creative labor.

[0032] Figure 1 is a structural schematic diagram of an information verification system in an embodiment of the present application;

[0033] Figure 2 is a flowchart of an information verification method applied to a client in an embodiment of the present application;

[0034] Figure 3 is a flowchart of an information verification method applied to a server in an embodiment of the present application;

[0035] Figure 4 is a flowchart of an information verification method in another embodiment of the present application;

[0036] Figure 5 is a structural schematic diagram of an information verification device in an embodiment of the present application;

[0037] Figure 6 is a structural schematic diagram of an information verification device in another embodiment of the present application;

[0038] Figure 7 is a structural schematic diagram of a computer device in an embodiment of the present application;

[0039] Figure 8 is a structural schematic diagram of a computer device in another embodiment of the present application. DETAILED DESCRIPTION

[0040] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of the present application.

[0041] The information verification method provided by the embodiments of the present application can be applied in an information verification system such as Figure 1 , wherein the server and the client communicate through a network.

[0042] The client is used to indicate a user end that triggers information verification. The client can be, but is not limited to, a personal computer, a notebook computer, a smart phone, a tablet computer, a portable wearable device, and other devices with a display screen and an input device. The user triggers an information verification process based on sending an information verification request to the client in the process of business. The client verifies the information verification request based on interaction with the server. If the verification is passed, the user can continue the business; if the verification is not passed, the user cannot continue the business.

[0043] The service end can be implemented by an independent server or a service platform composed of multiple servers. The service end can store the latest service end rule set based on the configuration of the developer. The developer synchronously updates the version number each time the service end rule set is updated, so that the service end can always store the latest service end rule set and the corresponding version number.

[0044] In the information verification, the client obtains the service end first time point rule set version number from the service end in response to the information verification request; if the local available rule set version number is different from the service end first time point rule set version number, the client obtains the service end first time point rule set from the service end, updates the local compiled script corresponding to the local available rule set version number by using the service end first time point rule set and caches the updated compiled script as an updated compiled script, and determines the local updated rule set version number corresponding to the updated compiled script according to the service end first time point rule set version number; the client sends the local updated rule set version number to the service end, so that the service end verifies the local updated rule set version number; and if a message of successful verification of the local updated rule set version number is received, the client executes information verification on the information verification request by using the updated compiled script.

[0045] The application will be described in detail below with reference to specific embodiments.

[0046] Please refer to Figure 2 , as shown in the figure, Figure 2 A flowchart of an information verification method provided by an embodiment of the application. The method is applied to a client and includes the following steps:

[0047] Step S210: obtaining the service end first time point rule set version number from the service end in response to the information verification request.

[0048] After the client receives the information verification request, verification is triggered on whether the client is the latest rule set version number.

[0049] The client stores a local available rule set version number. The local available rule set version number is used to indicate the rule set version that the client has updated based on interaction with the service end last time. That is, after the client forms the local available rule set version number, the client does not interact with the service end again for the rule set.

[0050] The client obtains the service end first time point rule set version number from the service end. The service end first time point rule set version number is used to indicate the rule set version stored by the service end at the time point when the client receives the information verification request. That is, during the period after the client forms the local available rule set version number and does not interact with the service end again for the rule set, the developer can update the service end rule set on the service end or can not update the service end rule set on the service end.

[0051] At the time point when the client receives the information verification request, it is not clear whether the local available rule set version number of the client is consistent with the service end first time point rule set version number of the service end, that is, it is not clear whether the local available rule set version number of the client is the latest rule set, and therefore verification is required.

[0052] In step S220, if the local available rule set version number and the service end first time point rule set version number are different, the service end first time point rule set is obtained from the service end, the local compiled script corresponding to the local available rule set version number is updated using the service end first time point rule set and cached as an updated compiled script, and the local updated rule set version number corresponding to the updated compiled script is determined according to the service end first time point rule set version number.

[0053] If the client determines that the local available rule set version number and the service end first time point rule set version number are different based on the comparison and matching, it indicates that the service end rule set is updated by the developer at the service end after the local available rule set version number is formed at the client and before the client interacts with the service end again for the rule set. Therefore, it is verified that the local rule set version number of the client is not the latest rule set version number.

[0054] The client needs to update the local available rule set version number locally. When updating, the client downloads the service end first time point rule set from the service end according to the service end first time point rule set version number. The client automatically updates the local compiled script according to the service end first time point rule set, forms an updated compiled script corresponding to the service end first time point rule set, and caches the updated compiled script. The client determines the local updated rule set version number corresponding to the updated compiled script according to the service end first time point rule set version number.

[0055] That is, before updating, the client stores: local available rule set version number-local compiled script. After updating, the client stores: local updated rule set version number (consistent with the service end first time point rule set version number)-updated compiled script (consistent with the service end first time point rule set).

[0056] In step S230, the local updated rule set version number is sent to the service end, so that the service end verifies the local updated rule set version number.

[0057] After the client forms the local updated rule set version number, the client sends the local updated rule set version number to the service end, triggering the service end to verify whether the local updated rule set version number is the latest rule set version number.

[0058] The local update rule set version number is formed by the client based on the server first time point rule set version number. During the script compiling process of the client, the developer may update the server rule set again on the server, or may not update the server rule set on the server.

[0059] At the time point when the client forms the local update rule set version number, it cannot be determined whether the local update rule set version number of the client is consistent with the server second time point rule set version number, that is, it cannot be determined whether the local update rule set version number of the client is the latest rule set version number, and therefore, verification needs to be performed again.

[0060] In step S240, if the local update rule set version number verification success message is received, the update compiled script is called to perform information verification on the information verification request.

[0061] If the server obtains the local update rule set version number and the server second time point rule set version number, and determines that the local update rule set version number and the server second time point rule set version number are the same based on comparison and matching, it indicates that the developer has not updated the server rule set on the server during the time period when the client forms the local update rule set version number (that is, script compiling). Therefore, it is verified that the local rule set version number of the client is the latest rule set version number. At this time, the server sends a message of local update rule set version number verification success to the client, and the client can call the update compiled script to perform information verification on the information verification request based on the instruction of the server.

[0062] As shown in the method shown in Figure 2 As can be seen from the information verification method provided by the present application, the server first time point rule set version number is obtained from the server in response to the information verification request; if the local available rule set version number and the server first time point rule set version number are different, the server first time point rule set is obtained from the server, the local compiled script corresponding to the local available rule set version number is updated by using the server first time point rule set and cached as an update compiled script, and the local update rule set version number corresponding to the update compiled script is determined according to the server first time point rule set version number; the local update rule set version number is sent to the server, so that the server verifies the local update rule set version number; and if the local update rule set version number verification success message is received, the update compiled script is called to perform information verification on the information verification request.

[0063] The client of the present application downloads the latest rule set version in real time through interaction with the server, automatically compiles it into an executable script and loads it into the cache, and realizes zero downtime update. The client of the present application returns the version number to the server, ensuring the consistency of the rule set versions of the client and the server. The client of the present application independently manages rule loading and execution, and the server focuses on rule distribution and version control, reducing the coupling degree of the client and the server.

[0064] In some optional embodiments, the method further comprises: if the first time point rule set version number of the server is failed to be acquired from the server, calling the local compiled script to perform the information verification; or, if the local available rule set version number is same as the first time point rule set version number of the server, calling the local compiled script to perform the information verification; or, if the first time point rule set of the server is failed to be acquired from the server, calling the local compiled script to perform the information verification; or, if the local compiled script is failed to be updated, calling the local compiled script to perform the information verification; or, if the message that the local updated rule set version number verification is successful cannot be received, calling the local compiled script to perform the information verification.

[0065] In the process of the information verification method shown in Figure 2 In the process of the information verification method shown in

[0066] In the process of the information verification method shown in Figure 2 In the process of the information verification method shown in

[0067] In the process of the information verification method shown in Figure 2 In the process of the information verification method shown in

[0068] In the process of the information verification method shown in Figure 2 In the process of the information verification method shown in

[0069] In the process of the information verification method shown in Figure 2If the message of the local update rule set version number verification success cannot be received (i.e., the message of the local update rule set version number verification failure also cannot be received) in the flow of the information verification method shown, it may indicate that the communication between the server and the client is abnormal, such as jitter. At this time, the client calls the local compiled script to perform information verification. That is, the client directly performs information verification based on the local compiled script.

[0070] When the information verification flow of the client of the present application is abnormal, the client automatically performs information verification by using the local compiled script (i.e., the last available version), thereby ensuring business continuity and preventing system crash.

[0071] In some optional embodiments, the above method further includes: if the message of the local update rule set version number verification failure is received, obtaining the server second time point rule set version number and the corresponding server second time point rule set from the server, updating the local update rule set version number corresponding update compiled script by using the server second time point rule set and caching the update compiled script as the latest compiled script, determining the local latest rule set version number corresponding to the latest compiled script according to the server second time point rule set version number; sending the local latest rule set version number to the server, so that the server verifies the local latest rule set version number; and if the local latest rule set version number verification is successful, calling the latest compiled script to perform information verification on the information verification request.

[0072] If the server verifies that the local update rule set version number is not successful, it indicates that the developer updates the server rule set again on the server during the period of compiling the update compiled script on the client (i.e., from the first time point to the second time point). Therefore, the local rule set version number of the client is not the latest.

[0073] The client needs to update the local update rule set again based on the received message of the local update rule set version number verification failure. When updating, the client downloads the server second time point rule set from the server according to the server second time point rule set version number. The client automatically updates the local update compiled script according to the server second time point rule set, forms the latest compiled script corresponding to the server second time point rule set, and caches the latest compiled script. The client determines the local latest rule set version number corresponding to the latest compiled script according to the server second time point rule set version number.

[0074] That is, before updating, the client stores: the local update rule set version number (consistent with the server first time point rule set version number)-the update compiled script (consistent with the server first time point rule set). After updating, the client stores: the local latest rule set version number (consistent with the server second time point rule set version number)-the latest compiled script (consistent with the server second time point rule set).

[0075] If the service end acquires the local latest rule set version number, and determines that the local latest rule set version number and the service end third time point rule set version number are the same based on comparison and matching, it indicates that the developer has not updated the service end rule set at the service end during the time period when the local latest rule set version number (i.e. script compilation) is formed at the client end. Therefore, it is verified that the local rule set version number at the client end is the latest. At this time, the latest compiled script is called to perform information verification on the information verification request.

[0076] If the service end acquires the local latest rule set version number, and determines that the local latest rule set version number and the service end third time point rule set version number are different based on comparison and matching, the local latest rule set version number needs to be further updated with the latest compiled script according to the above process. Details are not repeated here.

[0077] In each update process at the client end, if an abnormal situation occurs, the last available version of the compiled script (i.e. the local compiled script corresponding to the local available rule set version number) is automatically used to perform information verification. Details are not repeated here.

[0078] In some optional embodiments, performing information verification includes: determining target verification content according to the input parameter of the information verification request; determining the corresponding sub-compiled script from the compiled script according to the target verification content; and calling the sub-compiled script to perform information verification on the target verification content.

[0079] For different information verification requests, the information verification content that needs to be performed by the client end may be different. Therefore, the client end caches the latest compiled script for the latest rule set version number, or in the case of an abnormal situation using the last available version of the compiled script, the input parameter of the information verification request can be identified, and the target verification content is determined according to the field name of the information verification request. Based on the target verification content, the client end determines the corresponding sub-compiled script from the compiled script, and calls the sub-compiled script to perform information verification.

[0080] Please refer to Figure 3 as shown, Figure 3 A flowchart of an information verification method provided by an embodiment of the present application. The method is applied to a service end, and includes the following steps:

[0081] Step S310, after the client end responds to the information verification request, the service end first time point rule set version number is sent.

[0082] Step S320: After the client determines that the local available rule set version number is different from the server's first-time-point rule set version number, the server's first-time-point rule set is sent, so that the client uses the server's first-time-point rule set to update the local compiled script corresponding to the local available rule set version number and cache it as an updated compiled script, and determines the local updated rule set version number corresponding to the updated compiled script based on the server's first-time-point rule set version number.

[0083] Step S330: Receive the local update rule set version number from the client, and verify the local update rule set version number.

[0084] Step S340: If the local update rule set version number is successfully verified, the client is instructed to call the update compilation script to perform information verification on the information verification request.

[0085] In some optional implementations, the local update rule set version number is verified, including: determining whether the local update rule set version number is consistent with the server's second time point rule set version number; if consistent, the verification is successful; if inconsistent, the verification is unsuccessful.

[0086] The information verification method applied to the server corresponds to the information verification method applied to the client. Therefore, the specific definition of the information verification method applied to the server can be found in the definition of the information verification method applied to the client above, and will not be repeated here.

[0087] See also Figure 4 As shown, Figure 4 This is a flow chart of an information verification method provided by another embodiment of the present invention. The method is implemented through interaction between a client and a server.

[0088] exist Figure 4 In the illustrated information verification method flow, the term "current" is used to indicate the state at the time of the corresponding step. That is, the "current server rule set version number" in step S402 and the "current server rule set version number" in step S412 correspond to the server rule set version number at the time of the corresponding step (which may be the same or different).

[0089] Step S401: The client receives an information verification request. The process then proceeds to step S402.

[0090] In step S402, the client obtains the current server rule set version number from the server. Then, the process goes to step S403.

[0091] In step S403, the client determines whether it has successfully obtained the server rule set version number from the server. If not, the process goes to step S404; if so, the process goes to step S405.

[0092] Step S404, the client calls the available compiling script execution information for verification.

[0093] Step S405, the client determines whether the current local rule set version number and the server rule set version number obtained from the server are the same. If yes, go to step S404; if no, go to step S406.

[0094] Step S406, the client obtains the corresponding server rule set from the server according to the server rule set version number obtained from the server. Go to step S407.

[0095] Step S407, the client determines whether the corresponding server rule set is successfully obtained from the server. If no, go to step S404; if yes, go to step S408.

[0096] Step S408, the client updates the compiling script by using the corresponding server rule set obtained from the server. Go to step S409.

[0097] Step S409, the client determines whether the compiling script is successfully updated. If no, go to step S404; if yes, go to step S410.

[0098] Step S410, the client updates the local rule set version number according to the server rule set version number obtained from the server, and sends the local rule set version number to the server. Go to step S411.

[0099] Step S411, the client determines whether the local rule set version number is successfully sent to the server. If no, go to step S404; if yes, go to step S412.

[0100] Step S412, the server determines whether the local rule set version number is the same as the current server rule set version number. If no, go to step S413; if yes, go to step S415.

[0101] Step S413, the server sends the local rule set version number verification unsuccessful message to the client. Go to step S414.

[0102] Step S414, the client determines whether the local rule set version number verification unsuccessful message is received. If no, go to step S404; if yes, go to step S402.

[0103] Step S415, the server sends the local rule set version number verification successful message to the client. Go to step S416.

[0104] Step S416, the client determines whether the local rule set version number verification successful message is received. If no, go to step S404; if yes, go to step S417.

[0105] Step S417, the client calls the update compiled script execution information verification.

[0106] The following specific embodiments of medical scenarios are listed to explain the information verification method proposed by the application.

[0107] Taking the health insurance system customer information verification as an example, no abnormal situation occurs in the verification process.

[0108] The client receives the information verification request sent by the user, and the information verification request includes the verification of the user's historical health condition and the verification of the user's insurance information.

[0109] The local rule set version number stored by the client is 1.1.1, which corresponds to the compiled script 1.1.1. The server rule set version number obtained by the client from the server is 1.1.2.

[0110] Since the local rule set version number 1.1.1 and the server rule set version number 1.1.2 are different, the client downloads the server rule set 1.1.2 corresponding to the server rule set version number 1.1.2 from the server.

[0111] The client updates the compiled script 1.1.1 corresponding to the local rule set version number 1.1.1 according to the server rule set 1.1.2, and determines that the updated local rule set version number is 1.1.2 based on the server rule set version number 1.1.2, which corresponds to the updated compiled script 1.1.2.

[0112] The client sends the updated local rule set version number 1.1.2 to the server. At this time, the server rule set version number of the server remains 1.1.2.

[0113] The server determines that the updated local rule set version number 1.1.2 and the server rule set version number 1.1.2 are the same, and sends the updated local rule set version number verification success message to the client.

[0114] According to the instructions of the server, the client calls the part of the updated compiled script 1.1.2 for the verification of the user's historical health condition and the verification of the user's insurance information to perform information verification.

[0115] The following specific embodiments of financial scenarios are listed to explain the information verification method proposed by the application.

[0116] Taking the credit system customer information verification as an example, no abnormal situation occurs in the verification process.

[0117] The client receives the information verification request sent by the user, and the information verification request includes the verification of the user's historical health condition and the verification of the user's insurance information.

[0118] The local rule set version number stored by the client is 1.1.1, corresponding to the compiled script 1.1.1. The server rule set version number obtained by the client from the server is 1.1.2.

[0119] Since the local rule set version number 1.1.1 and the server rule set version number 1.1.2 are different, the client downloads the server rule set 1.1.2 corresponding to the server rule set version number 1.1.2 from the server.

[0120] The client updates the compiled script 1.1.1 corresponding to the local rule set version number 1.1.1 according to the server rule set 1.1.2, and determines that the updated local rule set version number is 1.1.2 based on the server rule set version number 1.1.2, corresponding to the updated compiled script 1.1.2.

[0121] The client sends the updated local rule set version number 1.1.2 to the server. At this time, the server rule set version number of the server becomes 1.1.3 due to the update of the developer.

[0122] The server determines that the updated local rule set version number 1.1.2 and the server rule set version number 1.1.3 are different, and sends an updated local rule set version number verification unsuccessful message to the client.

[0123] The client downloads the server rule set 1.1.3 corresponding to the server rule set version number 1.1.3 from the server according to the instruction of the server.

[0124] The client updates the compiled script 1.1.2 corresponding to the local rule set version number 1.1.2 according to the server rule set 1.1.3, and determines that the re-updated local rule set version number is 1.1.3 based on the server rule set version number 1.1.3, corresponding to the updated compiled script 1.1.3.

[0125] The client sends the updated local rule set version number 1.1.3 to the server. At this time, the server rule set version number of the server remains 1.1.3.

[0126] The server determines that the re-updated local rule set version number 1.1.3 and the server rule set version number 1.1.3 are the same, and sends a re-updated local rule set version number verification successful message to the client.

[0127] The client calls the part of the re-updated compiled script 1.1.3 for information verification for verifying the historical repayment of the user and verifying the basic information of the user according to the instruction of the server.

[0128] In an embodiment, an information verification device is provided, which corresponds to the information verification method applied to the client in the above-mentioned embodiments. As shown inFigure 5 As shown, the information checking device 500 comprises:

[0129] The obtaining unit 510 is configured to obtain the service-side first time point rule set version number from the service side in response to an information checking request.

[0130] The updating unit 520 is configured to, if the locally available rule set version number and the service-side first time point rule set version number are different, obtain the service-side first time point rule set from the service side, update the locally available rule set version number corresponding to the local compiled script by using the service-side first time point rule set and cache the local compiled script as an updated compiled script, and determine a local updated rule set version number corresponding to the updated compiled script according to the service-side first time point rule set version number.

[0131] The feedback unit 530 is configured to send the local updated rule set version number to the service side, so that the service side verifies the local updated rule set version number.

[0132] The checking unit 540 is configured to, if a local updated rule set version number verification success message is received, invoke the updated compiled script to perform information checking on the information checking request.

[0133] In some optional embodiments, in the above device 500, the checking unit 510 is further configured to, if the service-side first time point rule set version number fails to be obtained from the service side, invoke the local compiled script to perform information checking; or, if the locally available rule set version number and the service-side first time point rule set version number are the same, invoke the local compiled script to perform information checking; or, if the service-side first time point rule set fails to be obtained from the service side, invoke the local compiled script to perform information checking; or, if the local compiled script fails to be updated, invoke the local compiled script to perform information checking; or, if the local updated rule set version number verification success message fails to be received, invoke the local compiled script to perform information checking.

[0134] In some optional embodiments, in the above device 500, the obtaining unit 510 is further configured to, if a local updated rule set version number verification failure message is received, obtain the service-side second time point rule set version number and the corresponding service-side second time point rule set from the service side; the updating unit 520 is further configured to update the updated compiled script corresponding to the local updated rule set version number by using the service-side second time point rule set and cache the updated compiled script as a latest compiled script, and determine a local latest rule set version number corresponding to the latest compiled script according to the service-side second time point rule set version number; the feedback unit 530 is further configured to send the local latest rule set version number to the service side, so that the service side verifies the local latest rule set version number; and the checking unit 540 is further configured to, if a local latest rule set version number verification success message is received, invoke the latest compiled script to perform information checking on the information checking request.

[0135] In some optional embodiments, in the apparatus 500 described above, the checking unit 540 is specifically configured to: determine target checking content according to an input parameter of the information checking request; determine a corresponding sub-compilation script from the compilation script according to the target checking content; and invoke the sub-compilation script to perform information checking on the target checking content.

[0136] In an embodiment, an information checking apparatus is provided, which corresponds to the information checking method applied to the server in the above embodiments. As shown in the figure, the information checking apparatus 600 comprises: Figure 6

[0137] The first sending unit 610 is configured to send a server first time point rule set version number after the client responds to the information checking request.

[0138] The second sending unit 620 is configured to send a server first time point rule set after the client determines that the local available rule set version number and the server first time point rule set version number are different, so that the client updates the local compilation script corresponding to the local available rule set version number by using the server first time point rule set and caches the updated compilation script as an updated compilation script, and determines a local updated rule set version number corresponding to the updated compilation script according to the server first time point rule set version number.

[0139] The verification unit 630 is configured to receive the local updated rule set version number from the client and verify the local updated rule set version number.

[0140] The instruction unit 640 is configured to instruct the client to invoke the updated compilation script to perform information checking on the information checking request if the local updated rule set version number is verified successfully.

[0141] In some optional embodiments, in the apparatus 600 described above, the verification unit 630 is specifically configured to: determine whether the local updated rule set version number is consistent with a server second time point rule set version number; if the local updated rule set version number is consistent with the server second time point rule set version number, the verification is successful; and if the local updated rule set version number is not consistent with the server second time point rule set version number, the verification is unsuccessful.

[0142] For specific limitations of the information checking apparatus applied to the client, refer to the limitations of the information checking method applied to the client in the above, which will not be repeated here. For specific limitations of the information checking apparatus applied to the server, refer to the limitations of the information checking method applied to the server in the above, which will not be repeated here.

[0143] The various units in the information checking apparatus described above can be all or partially realized by software, hardware and combinations thereof. The various units described above can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory in the computer device in software form, so as to be called and executed by the processor to perform the operations corresponding to the various units. ​

[0144] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as follows: Figure 7 As shown. The computer device includes a processor, memory, network interface, display screen, and input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements the functions or steps of the client side of the information verification method.

[0145] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, memory, network interface and database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client via a network connection. When the computer program is executed by the processor, it implements the functions or steps on the server side of the information verification method.

[0146] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the computer program implements the above-mentioned information verification method applied to the client or the information verification method applied to the server.

[0147] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or computer device can be found in the relevant descriptions of the client side and the server side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0148] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to memory, storage, database or other medium used in the embodiments of the present application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration but not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0149] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above-mentioned division of functional units and modules is exemplified. In actual application, the above-mentioned functions can be completed by different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the above-described functions.

[0150] The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, but not to limit it. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features. Such modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.

Claims

1. An information verification method, characterized in that: The information verification method is applied to a client, the client is in communication with a server, and the information verification method includes: Responding to the information verification request, obtaining a server-side rule set version number at a first time point from the server; If the locally available rule set version number is different from the server-side first-time-point rule set version number, obtaining the server-side first-time-point rule set from the server, using the server-side first-time-point rule set to update the local compiled script corresponding to the locally available rule set version number and caching it as an updated compiled script, and determining the local updated rule set version number corresponding to the updated compiled script based on the server-side first-time-point rule set version number; Sending the local update rule set version number to the server, so that the server verifies the local update rule set version number; If the local update rule set version number verification success message is received, the update compilation script is called to perform information verification on the information verification request.

2. The information verification method according to claim 1, characterized in that: The method further comprises: If the server fails to obtain the rule set version number of the server at the first time point from the server, calling the local compiled script to perform information verification; or, If the locally available rule set version number is the same as the server-side rule set version number at the first time point, calling the local compiled script to perform information verification; or, If obtaining the server-side first time point rule set from the server fails, calling the local compiled script to perform information verification; or, If the local compiled script fails to be updated, calling the local compiled script to perform information verification; Alternatively, if the local update rule set version number verification success message cannot be received, a local compilation script is called to perform information verification.

3. The information verification method according to claim 1, wherein: The method further comprises: If the local update rule set version number verification failure message is received, obtaining the server-side second time point rule set version number and the corresponding server-side second time point rule set from the server; Using the server-side second-time-point rule set to update the updated compiled script and cache it as the latest compiled script, determining the local latest rule set version number corresponding to the latest compiled script based on the server-side second-time-point rule set version number, and sending the local latest rule set version number to the server, so that the server verifies the local latest rule set version number; If a message indicating that the local latest rule set version number has been successfully verified is received, the latest compilation script is called to perform information verification on the information verification request.

4. The information verification method according to any one of claims 1 to 3, characterized in that: The execution information verification includes: Determine the target verification content according to the input parameters of the information verification request; Determining a corresponding sub-compile script from the compile script according to the target verification content; The sub-compile script is called to perform information verification on the target verification content.

5. An information verification method, characterized in that: The information verification method is applied to a server, which is in communication with a client. The information verification method includes: After the client responds to the information verification request, sending the server a rule set version number at the first time point; After the client determines that the local available rule set version number is different from the server-side first-time-point rule set version number, the client sends the server-side first-time-point rule set, so that the client uses the server-side first-time-point rule set to update the local compiled script corresponding to the local available rule set version number and cache it as an updated compiled script, and determines the local updated rule set version number corresponding to the updated compiled script according to the server-side first-time-point rule set version number; receiving the local update rule set version number from the client, and verifying the local update rule set version number; If the local update rule set version number is successfully verified, the client is instructed to call the update compilation script to perform information verification on the information verification request.

6. The information verification method according to claim 5, characterized in that: The verifying the version number of the local update rule set includes: Determine whether the local updated rule set version number is consistent with the server-side rule set version number at the second time point; If they are consistent, the verification is successful; If they are inconsistent, the verification fails.

7. An information verification device, characterized in that: The information verification device is deployed on the client, and the client is connected to the server for communication. The information verification device includes: an acquiring unit, configured to acquire, from the server, a version number of a rule set at a first time point on the server in response to an information verification request; an updating unit configured to, if the locally available rule set version number is different from the server-side first-time-point rule set version number, obtain the server-side first-time-point rule set from the server, use the server-side first-time-point rule set to update the local compiled script corresponding to the locally available rule set version number and cache the script as an updated compiled script, and determine the local updated rule set version number corresponding to the updated compiled script based on the server-side first-time-point rule set version number; a receipt unit, configured to send the local update rule set version number to the server, so that the server verifies the local update rule set version number; The verification unit is configured to, upon receiving a message indicating that the local update rule set version number has been successfully verified, call the update compilation script to perform information verification on the information verification request.

8. An information verification device, characterized in that: The information verification device is deployed on the server side, and the server side is in communication with the client side. The information verification device includes: A first sending unit, configured to send a rule set version number of a first time point of the server after the client responds to the information verification request; a second sending unit, configured to send the server-side first-time-point rule set after the client determines that the locally available rule set version number is different from the server-side first-time-point rule set version number, so that the client uses the server-side first-time-point rule set to update the local compiled script corresponding to the locally available rule set version number and cache it as an updated compiled script, and determine the local updated rule set version number corresponding to the updated compiled script according to the server-side first-time-point rule set version number; a verification unit, configured to receive the local update rule set version number from the client and verify the local update rule set version number; An instruction unit is configured to instruct the client to call the update compilation script to perform information verification on the information verification request if the local update rule set version number verification is successful.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the information verification method according to any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the information verification method according to any one of claims 1 to 6 are implemented.

Images