Strategy verification method, system and device

Abstract

The embodiment of the invention provides a strategy verification method, system and device, and the method comprises the steps: obtaining a to-be-verified strategy and the strategy verification information of the to-be-verified strategy, and enabling the strategy verification information to comprise a verification field, a verification field value and a verification expectation result; based on the strategy verification information, test data of the to-be-verified strategy is constructed, and the test data comprises a test field and a test field value; testing the test data by using the to-be-verified strategy to obtain a test result; and determining a strategy verification result of the to-be-verified strategy according to the verification expected result and the test result. According to the strategy verification method and device, the test data of the to-be-verified strategy is automatically constructed and the test data is automatically tested, so that the strategy verification efficiency is improved, the test data is obtained based on the strategy verification information, the corresponding relation between the verification expected result and the test result can be ensured, and the accuracy of the strategy verification result is improved.

Description

Technical Field

[0001] The embodiments of the present specification relate to the field of computer technology, and in particular to a policy verification method, system, and device. Background Art

[0002] In the insurance industry, risk management strategy is a key factor in ensuring product risk management and project compliance. Risk management strategy refers to a series of plans and actions formulated by an enterprise or organization to identify, evaluate, prioritize and take measures to reduce the impact of potential risks on project objectives. With the continuous launch of insurance products, insurance companies need to configure and verify a large number of risk management strategies to ensure that these strategies can effectively manage risks.

[0003] Currently, risk control strategies can usually be verified through manual verification. However, the above method relies on manually generating test data and executing test scenarios, which is extremely inefficient and prone to errors. Therefore, an efficient and accurate strategy verification solution is urgently needed. Summary of the invention

[0004] In view of this, an embodiment of this specification provides a policy verification method. One or more embodiments of this specification also relate to a policy verification system, a policy verification device, a computing device, a computer-readable storage medium and a computer program product to solve the technical defects existing in the prior art.

[0005] According to a first aspect of an embodiment of this specification, a policy verification method is provided, including: Obtaining the policy to be verified and policy verification information of the policy to be verified, wherein the policy verification information includes a verification field, a verification field value, and an expected verification result; Based on the policy verification information, construct test data of the policy to be verified, wherein the test data includes a test field and a test field value; Using the strategy to be verified, test the test data to obtain the test results; Determine the policy verification result of the policy to be verified based on the expected verification result and the test result.

[0006] According to a second aspect of an embodiment of this specification, a policy verification system is provided, including a client and a server; The client is used to send the policy to be verified and the policy verification information of the policy to be verified to the server, wherein the policy verification information includes the verification field, the verification field value and the expected verification result; The server is used to construct test data of the policy to be verified based on the policy verification information, wherein the test data includes test fields and test field values; use the policy to be verified to test the test data to obtain test results; and determine the policy verification result of the policy to be verified based on the expected verification result and the test result.

[0007] According to a third aspect of the embodiments of this specification, a policy verification device is provided, including: A first acquisition module is configured to acquire a policy to be verified and policy verification information of the policy to be verified, wherein the policy verification information includes a verification field, a verification field value, and an expected verification result; A construction module is configured to construct test data of the policy to be verified based on the policy verification information, wherein the test data includes a test field and a test field value; The test module is configured to test the test data using the strategy to be verified and obtain the test result; The first determination module is configured to determine a policy verification result of the policy to be verified according to the expected verification result and the test result.

[0008] According to a fourth aspect of an embodiment of this specification, a computing device is provided, including: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer program / instructions are executed by the processor, the steps of the method provided in the first aspect are implemented.

[0009] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores a computer program / instruction, and when the computer program / instruction is executed by a processor, the steps of the method provided in the first aspect are implemented.

[0010] According to a sixth aspect of the embodiments of this specification, a computer program product is provided, comprising a computer program / instruction, which implements the steps of the method provided in the first aspect when executed by a processor.

[0011] A policy verification method provided by an embodiment of the present specification includes: obtaining a policy to be verified and policy verification information of the policy to be verified, wherein the policy verification information includes a verification field, a verification field value, and an expected verification result; constructing test data of the policy to be verified based on the policy verification information, wherein the test data includes a test field and a test field value; testing the test data using the policy to be verified to obtain a test result; and determining the policy verification result of the policy to be verified based on the expected verification result and the test result. By automatically constructing the test data of the policy to be verified and automatically testing the test data, the efficiency of policy verification is improved, and since the test data is obtained based on the policy verification information, the correspondence between the expected verification result and the test result can be guaranteed, thereby improving the accuracy of the policy verification result. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is an architecture diagram of a policy verification system provided by an embodiment of this specification; Figure 2 is a flow chart of a policy verification method provided by an embodiment of this specification; Figure 3 is a process flow chart of a policy verification method provided by an embodiment of this specification; Figure 4 This is a schematic diagram of a policy verification interface provided by an embodiment of this specification; Figure 5 It is a structural diagram of a strategy verification device provided by an embodiment of this specification; Figure 6 It is a structural block diagram of a computing device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0013] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

[0014] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0015] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0016] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0017] First, the terms involved in one or more embodiments of this specification are explained.

[0018] Two-core risk control: refers to the risk management of the two key links of underwriting and claims adjudication in the insurance industry. These two links are the core of insurance companies' control and prevention of risks, and are related to the operating safety and profitability of insurance companies.

[0019] Underwriting: Before the insurance contract is established, the insurance company evaluates the risk level of the insured object based on the insured's application and related information, and decides whether to insure and the specific conditions of underwriting (such as insurance premium rate, insurance amount, insurance period, etc.). Factors that need to be considered during the underwriting process include but are not limited to the insured's credit record, health status, past claims record, etc. The purpose of underwriting is to ensure that the insurance company can set reasonable prices and avoid taking excessive risks, thereby maintaining the company's financial stability.

[0020] Claims verification: It is the process by which the insurance company reviews the claim for compensation filed by the insured after an insurance accident occurs. This involves verifying the authenticity, legality and rationality of the claim materials to determine the amount of compensation. Claims verification not only protects the legitimate rights and interests of the insured, but also prevents false claims and insurance fraud, and protects the legitimate rights and interests of the insurance company from infringement.

[0021] Groovy: is a dynamic programming language based on the Java platform. It provides powerful scripting capabilities and can be used in a variety of scenarios such as automated tasks, data processing, and build tools.

[0022] Taking the policy verification in the insurance industry as an example, currently, policy verification is usually carried out in the following ways. The first is manual verification: manually generating insurance policies, batch data, and claims data to cover all test scenarios, but the above process is cumbersome and time-consuming. The complexity of policy verification and manual intervention lead to low verification efficiency and prone to errors. The second is semi-automatic verification: semi-automatic verification tools are introduced, which can partially automatically generate test data and execute some test scenarios. However, verification tools usually lack flexibility and cannot flexibly configure verification scenarios and test data according to different policies.

[0023] In order to solve the problem that traditional policy verification methods are inefficient and prone to errors, and cannot meet the needs of rapid online and high-quality verification, the embodiment of this specification proposes a policy verification method, which obtains the policy to be verified and the policy verification information of the policy to be verified, wherein the policy verification information includes verification fields, verification field values, and expected verification results; based on the policy verification information, construct test data for the policy to be verified, wherein the test data includes test fields and test field values; use the policy to be verified to test the test data and obtain test results; determine the policy verification results of the policy to be verified based on the expected verification results and the test results. By automatically constructing the test data of the policy to be verified and automatically testing the test data, the efficiency of policy verification is improved, and because the test data is obtained based on the policy verification information, the correspondence between the expected verification results and the test results can be guaranteed, thereby improving the accuracy of the policy verification results and ensuring that the policy can meet project expectations.

[0024] In this specification, a policy verification method is provided. This specification also involves a policy verification system, a policy verification device, a computing device, a computer-readable storage medium and a computer program product, which are described in detail one by one in the following embodiments.

[0025] See also Figure 1 , Figure 1 An architecture diagram of a policy verification system provided by an embodiment of the present specification is shown. The policy verification system may include a client 100 and a server 200; The client 100 is used to send the policy to be verified and the policy verification information of the policy to be verified to the server 200, wherein the policy verification information includes the verification field, the verification field value and the expected verification result; The server 200 is used to construct test data of the policy to be verified based on the policy verification information, wherein the test data includes test fields and test field values; use the policy to be verified to test the test data to obtain test results; and determine the policy verification result of the policy to be verified based on the expected verification result and the test result.

[0026] In an optional embodiment of the present specification, the server 200 is further used to send a policy verification result to the client 100 ; the client 100 is further used to receive the policy verification result sent by the server 200 .

[0027] By applying the solution of the embodiments of this specification, the efficiency of policy verification is improved by automatically constructing test data for the policy to be verified and performing automated testing on the test data. Furthermore, since the test data is obtained based on policy verification information, the correspondence between the expected verification results and the test results can be guaranteed, thereby improving the accuracy of the policy verification results.

[0028] In practical applications, the policy verification system may include multiple clients 100 and a server 200. Multiple clients 100 may establish a communication connection through the server 200. In the policy verification scenario, the server 200 is used to provide policy verification services between multiple clients 100. Multiple clients 100 may serve as senders or receivers, respectively, and realize communication through the server 200. The client 100 may interact with the user through a graphical user interface. The user may interact with the server 200 through the client 100 to receive data sent by other clients 100, or send data to other clients 100, etc. In the policy verification scenario, the user may publish a data stream to the server 200 through the client 100, and the server 200 may generate a policy verification result based on the data stream, and push the policy verification result to other clients that have established communication. Among them, the client 100 and the server 200 are connected through a network. The network provides a medium for the communication link between the client 100 and the server 200. The network may include various connection types, such as wired, wireless communication links or optical fiber cables, etc. The data transmitted by the client 100 may need to be encoded, transcoded, compressed, etc. before being released to the server 200.

[0029] The client 100 can be a browser, an application (APP, Application), or a web application such as HyperText Markup Language Version 5 (H5, HyperText Markup Language5) application, or a light application (also known as a mini-program, a lightweight application) or a cloud application, etc. The client 100 can be based on the software development kit (SDK, Software Development Kit) of the corresponding service provided by the server 200, such as based on the real-time communication (RTC, Real Time Communication) SDK development and acquisition. The client 100 can be deployed in an electronic device and needs to rely on the device to run or some APPs in the device to run. For example, the electronic device can have a display screen and support information browsing, such as a personal mobile terminal such as a mobile phone, a tablet computer, a personal computer, etc. Various other types of applications can also be configured in the electronic device, such as human-computer dialogue applications, model training applications, text processing applications, web browser applications, shopping applications, search applications, instant messaging tools, mailbox clients, social platform software, etc.

[0030] The server 200 may include servers that provide various services, such as servers that provide communication services to multiple clients, servers for background training that support models used on clients, and servers that process data sent by clients. It should be noted that the server 200 can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. The server can also be a server of a distributed system, or a server combined with a blockchain. The server can also be a cloud server for basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks (CDN, Content Delivery Network), and big data and artificial intelligence platforms, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0031] It is worth noting that the policy verification method provided in the embodiments of this specification is generally executed by the server, but in other embodiments of this specification, the client may also have similar functions to the server, thereby executing the policy verification method provided in the embodiments of this specification. In other embodiments, the policy verification method provided in the embodiments of this specification may also be executed jointly by the client and the server.

[0032] See also Figure 2 , Figure 2 A flow chart of a policy verification method provided by an embodiment of this specification is shown, which specifically includes the following steps: Step 202: Obtain the policy to be verified and the policy verification information of the policy to be verified, wherein the policy verification information includes a verification field, a verification field value, and an expected verification result.

[0033] It should be noted that in the strategy verification task, the strategy to be verified refers to a strategy that has been designed or proposed, but needs to undergo a series of tests and verifications before formal implementation to ensure its effectiveness and reliability. The strategy to be verified can be a strategy in different scenarios, such as the resource allocation strategy in the resource allocation scenario, the risk control strategy in the insurance scenario, and so on. The strategy to be verified can also be different strategies in the same scenario, such as the investment risk control strategy in the insurance scenario, the dual-core risk control strategy, and so on. Taking the risk control strategy in the insurance scenario as an example, the risk control strategy may involve multiple aspects such as risk management, product pricing, and customer service processes. The purpose of verifying the strategy to be verified is to ensure that they can achieve the expected results in actual operation, and at the same time discover and correct potential problems or deficiencies. For example, the strategy to be verified can be "the number of historical policies is less than or equal to 3, and the policy amount is less than 500,000, and it can be insured."

[0034] The policy verification information of the policy to be verified refers to the information used to verify the policy to be verified, that is, the expected verification result in the policy verification information refers to the expected effect in actual operation. Through the policy verification information, it is possible to evaluate whether the policy to be verified can operate in the expected manner and whether it can achieve the expected goal in the actual application scenario. The verification field refers to the attribute information used to verify the policy to be verified. For example, in the insurance application process, the verification field can include the customer's age, health status, occupation type, etc. The verification field value refers to the specific value or range corresponding to the verification field. For example, if the verification field is "age", the verification field value can be "25 years old" or "less than or equal to 25 years old". The verification expected result is the expected result based on the given verification field and verification field value. For example, suppose the policy to be verified stipulates that an insurance policy can only be purchased by individuals between the ages of 18 and 65. Then, when the verification field is age and the verification field value is 70 years old, the verification expected result should be failure. When the verification field is age and the verification field value is 55 years old, the verification expected result should be pass.

[0035] It is worth noting that the number of verification fields can be one or more, and the specific selection is based on the actual situation. The embodiments of this specification do not impose any restrictions on this. If there are multiple verification fields, the policy verification information usually also includes the verification logic relationship between the multiple verification fields. Taking "The number of historical insurance policies is less than or equal to 3, and the insurance policy amount is less than 500,000, you can be insured" as an example, the verification fields include "the number of historical insurance policies" and "the insurance policy amount", and the verification logic relationship between these two verification fields is "and".

[0036] In practical applications, there are many ways to obtain the policy to be verified and the policy verification information of the policy to be verified, which are selected according to the actual situation, and the embodiments of this specification do not impose any restrictions on this. In one possible implementation of this specification, the policy to be verified and the policy verification information of the policy to be verified sent by the client can be received. In another possible implementation of this specification, the policy to be verified and the policy verification information of the policy to be verified can be read from other data acquisition devices or databases.

[0037] In an optional embodiment of the present specification, since the policy to be verified may be long or expressed in various ways, structured policy configuration information of the policy to be verified may be obtained, and the policy to be verified may be determined based on the policy configuration information. That is, the above-mentioned obtaining of the policy to be verified and the policy verification information of the policy to be verified may include the following steps: In response to the policy verification request, sending configuration guidance information to the client; Receiving policy configuration information sent by the client based on the configuration guidance information, wherein the policy configuration information includes a configuration field and a configuration field value; The policy to be verified is determined based on the policy configuration information, and policy verification information of the policy to be verified is obtained.

[0038] It should be noted that a policy verification request refers to a formal verification request initiated before the policy to be verified is implemented in order to ensure its correctness and effectiveness. Policy configuration information refers to the information provided by the client for defining and configuring the policy to be verified. Policy configuration information generally includes configuration fields, configuration field values, and other related parameters, which are used to guide the implementation and verification of the policy to be verified. Configuration fields refer to fields for configuring the policy to be verified. Configuration field values ​​refer to specific values ​​or ranges corresponding to the configuration fields. If the policy to be verified is "an insurance policy can only be purchased by individuals between the ages of 18 and 65", the configuration field is "age" and the configuration field value is "between 18 and 65 years old". The number of configuration fields can be one or more, which is selected according to the actual situation, and the embodiments of this specification do not impose any restrictions on this. If there are multiple configuration fields, the policy configuration information generally also includes the configuration logic relationship between the multiple configuration fields. The configuration logic relationship is used to define how multiple configuration fields are combined to form the policy to be verified.

[0039] Configuration guidance information refers to the guide or template provided by the server to the client to guide the client to correctly fill in and submit the policy configuration information. For example, the configuration guidance information can be "Please select the configuration field of the policy to be verified from the candidate field library, and fill in the configuration field value corresponding to the configuration field. In the case of multiple configuration fields, the configuration logical relationship between multiple configuration fields is defined through the logical relationship component." In response to the policy verification request, the configuration guidance information can be obtained before sending the configuration guidance information to the client.

[0040] By applying the solution of the embodiment of this specification, the client is guided to gradually complete the configuration of the policy configuration information in the policy to be verified by configuring the guidance information, which simplifies the configuration process and saves data transmission resources.

[0041] In actual applications, there are many ways to obtain the policy verification information of the policy to be verified, which are selected according to the actual situation. The embodiments of this specification do not impose any restrictions on this. In a possible implementation of this specification, the configuration field in the policy configuration information can be directly determined as the verification field, and the verification field value of the verification field can be generated. Based on historical verification experience, the expected verification result corresponding to each verification field value is determined.

[0042] In another possible implementation of the present specification, in order to ensure the accuracy of the expected verification result, the client may configure the expected verification result, that is, the above-mentioned acquisition of the policy verification information of the policy to be verified may include the following steps: Displaying a candidate field library to a client, wherein the candidate field library includes multiple candidate verification fields; Receive a validation field sent by a client, and generate a validation field value of the validation field, wherein the validation field is selected by the client from a candidate field library; Send the validation field value to the client; Receives the expected validation result sent by the client for the validation field value.

[0043] It should be noted that the candidate field library is a predefined set of candidate validation fields, which contain various attributes that may be used for policy validation. The candidate field library can provide clients with options for selecting and configuring validation fields, ensuring that clients can select appropriate fields for validation based on actual needs. The candidate field library can be dynamically expanded to support new candidate validation fields.

[0044] In actual applications, there are many ways to generate the verification field value of the verification field, including but not limited to fixed value generation, random value generation, acquisition from the Application Programming Interface (API) and custom generation by Groovy script. The specific selection is based on the actual situation, and the embodiments of this specification do not impose any restrictions on this. The method for generating the verification field value can be randomly selected or selected based on the specific configuration of the policy to be verified. When generating the verification field value, you can also consider configuring the field value so that the verification field value is more in line with the policy to be verified.

[0045] For example, assuming that the validation field is age, the configuration field value corresponding to the configuration field age is less than or equal to 30 years old. When the validation field value is generated by fixed value method, it can be separated from the configuration field value by a fixed value, such as the generated validation field value can be 10 years old, 20 years old, 30 years old, 40 years old, 50 years old. When the validation field value is generated by random value generation method, it can be randomly selected near the configuration field value, such as the generated validation field value can be 29 years old, 32 years old, 27 years old.

[0046] The solution of the embodiment of this specification is applied to provide a standardized and structured field selection mechanism to the client through the candidate field library, helping the client to quickly and accurately select and configure the verification field, thereby improving the efficiency and accuracy of policy verification. In addition, by generating verification field values ​​in different ways, the flexibility of policy verification information is improved.

[0047] In an optional embodiment of the present specification, when there are multiple verification fields, the verification logic relationship between the multiple verification fields can be determined. In a possible implementation of the present specification, the configuration logic relationship can be directly determined as the verification logic relationship.

[0048] In another possible implementation of this specification, the client can configure the corresponding verification logic relationship so that the verification logic relationship can include relationships other than the configured logic relationship, thereby increasing the verification scope. That is, the policy verification information also includes the verification logic relationship between the verification fields; the above-mentioned policy verification method can also include the following steps: Display multiple logical relationship components to the client; In response to the client's operation on the plurality of logical relationship components, a verification logical relationship is determined.

[0049] It should be noted that the verification logic relationship is used to define how multiple verification fields are combined together to determine the final verification result. Verification logic relationships generally include logical operators such as "AND", "OR", and "NOT". These logical operators are used to combine multiple verification fields to ensure that all conditions are met or at least one condition is met, or the conditions are not met. The server can provide a visual logic editor that allows users to define complex verification logic by dragging and dropping multiple logical relationship components. Logical relationship components generally include "AND" components, "OR" components, and "NOT" components. The client's operation methods for multiple logical relationship components include any of the following methods: click, double-click, touch, mouse hover, slide, long press, voice control, or shake, etc. The specific selection is based on the actual situation, and the embodiments of this specification do not impose any restrictions on this.

[0050] For example, assume that the verification fields are "Number of Historical Insurance Policies" and "Insurance Amount". The three components of "and", "or" and "not" are displayed to the client. In response to the client's operation on the "and" component, the verification logic relationship is determined to be "and".

[0051] By applying the solution of the embodiment of this specification, multiple logical relationship components are displayed to the client, ensuring that the client can flexibly select and configure the verification fields and their logical relationships, thereby building an accurate verification logical relationship.

[0052] In an optional embodiment of the present specification, since the policy configuration information may not conform to common sense, the policy configuration information may be preliminarily tested using the configuration conditions, that is, before determining the policy to be verified based on the policy configuration information and obtaining the policy verification information of the policy to be verified, the following steps may also be included: Get the configuration conditions corresponding to the policy configuration information; Determining the policy to be verified based on the policy configuration information and obtaining the policy verification information of the policy to be verified may include the following steps: When the policy configuration information meets the configuration condition, the policy to be verified is determined based on the policy configuration information, and policy verification information of the policy to be verified is obtained.

[0053] It should be noted that configuration conditions refer to a set of rules used to determine whether the policy configuration information meets the preset standards or requirements after receiving and parsing the policy configuration information. The configuration conditions ensure the validity and rationality of the policy configuration information, thereby ensuring that the subsequent policy verification process can proceed smoothly. For example, the configuration condition for the configuration field age is "need to be greater than 0 years old." There are many ways to obtain policy configuration information, and the specific selection is based on actual conditions. The embodiments of this specification do not impose any restrictions on this. In one possible implementation of this specification, the configuration conditions corresponding to the policy configuration information sent by the client can be received. In another possible implementation of this specification, the configuration conditions corresponding to the policy configuration information can be read from other data acquisition devices or databases.

[0054] In actual applications, after obtaining the configuration conditions corresponding to the policy configuration information, it can be determined whether the policy configuration information meets the configuration conditions. There are many ways to determine whether the policy configuration information meets the configuration conditions, which are selected according to the actual situation. The embodiments of this specification do not impose any restrictions on this. In one possible implementation of this specification, the policy configuration information can be directly compared to see whether it meets the configuration conditions to obtain a judgment result. For example, the policy configuration information is "age is -1000 years old", and the configuration condition is "need to be greater than 0 years old". By directly comparing the policy configuration information and the configuration condition, it can be obtained that the judgment result is that the policy configuration information does not meet the configuration conditions. In another possible implementation of this specification, a large model can be used to determine whether the policy configuration information meets the configuration conditions. A large model refers to a deep learning model with large-scale model parameters, which usually contains hundreds of millions, tens of billions, hundreds of billions, trillions, or even more than ten trillion model parameters. The large model can be called the foundation model. It is pre-trained with large-scale unlabeled corpus to produce a pre-trained model with more than 100 million parameters. This model can adapt to a wide range of downstream tasks and has good generalization capabilities, such as the large-scale language model (LLM), multi-modal pre-training model, etc.

[0055] Further, in the case where the policy configuration information does not meet the configuration conditions, it can be determined that the verification of the policy to be verified has failed, or policy configuration information confirmation information can be sent to the client to allow the client to reconfirm whether the policy configuration information is accurate. If the client determines that the policy configuration information is accurate, the policy to be verified is determined based on the policy configuration information, and the policy verification information of the policy to be verified is obtained. The policy to be verified is determined based on the policy configuration information, and the policy verification information of the policy to be verified is obtained. In the case where the policy configuration information meets the configuration conditions, the policy to be verified is determined based on the policy configuration information, and the policy verification information of the policy to be verified is obtained.

[0056] By applying the solution of the embodiments of this specification, the validity and rationality of the policy configuration information can be detected by using the configuration conditions, so that the subsequent policy verification process can be ensured to proceed smoothly.

[0057] Step 204: construct test data for the policy to be verified based on the policy verification information, wherein the test data includes a test field and a test field value.

[0058] It should be noted that the test data of the policy to be verified refers to the data that will be tested by the policy to be verified. The test field refers to the attribute information that will be judged by the policy to be verified. For example, in the insurance application process, the test field may include the customer's age, health status, occupation type, etc. The test field value refers to the specific value or range corresponding to the test field. The number of test fields can be one or more, which is selected according to the actual situation, and the embodiments of this specification do not impose any restrictions on this. If there are multiple test fields, the test data usually also includes the test logical relationship between multiple test fields. The test logical relationship is used to define how multiple test fields are combined to be judged by the policy to be verified.

[0059] In practical applications, there are many ways to construct test data for the policy to be verified based on the policy verification information, which are selected according to the actual situation, and the embodiments of this specification do not impose any restrictions on this. In one possible implementation method of this specification, the test data of the policy to be verified can be screened out from multiple candidate test data stored in the test database based on the policy verification information. Among them, each candidate test data carries candidate policy verification information. The test data of the policy to be verified refers to the target candidate test data whose candidate policy verification information matches the policy verification information (the same or with high similarity) among multiple candidate test data. Since the candidate policy verification information of the target candidate test data matches the policy verification information, it can be explained that the stock policy corresponding to the candidate test data (the policy that is determined to be effective and reliable after policy verification) matches the policy to be processed, and the test data of the existing stock policy can be directly reused without regenerating the test data, which saves the test data generation time.

[0060] In an optional embodiment of the present specification, test data of the policy to be verified can be constructed in real time. That is, the construction of test data of the policy to be verified based on the policy verification information can include the following steps: Obtaining a method for generating test field and verification field values, wherein the test field at least includes the verification field; Generate a test field value corresponding to the test field based on the generation method.

[0061] It should be noted that the test field may include only the verification field, and may also include other fields besides the verification field. There are many ways to obtain the test field, and the specific selection is made according to the actual situation. The embodiments of this specification do not impose any restrictions on this. In one possible implementation of this specification, the verification field can be directly determined as the test field. In another possible implementation of this specification, on the basis of determining the verification field as the test field, the test field can also be extracted from the candidate field library.

[0062] In actual applications, when generating the test field value corresponding to the test field based on the generation method of the verification field value, assuming that the test field is age and the generation method of the verification field value is a fixed value generation method, the test field value can be 10, 20, 30, 40, and 50. Assuming that the test field is age and the generation method of the verification field value is a random value generation method, the test field value can be 29, 32, and 27.

[0063] By applying the solution of the embodiments of this specification, the test field value corresponding to the test field is generated based on the generation method of the verification field value, which can ensure that the expected verification result can accurately verify the test result, thereby improving the accuracy of the policy verification result.

[0064] In an optional embodiment of the present specification, there are multiple verification fields, and the policy verification information also includes a verification logic relationship between the verification fields; after the test field value corresponding to the test field is generated based on the generation method, the following steps may also be included: According to the verification logic relationship, the test logic relationship between the test fields is determined.

[0065] It should be noted that there are multiple ways to determine the test logical relationship between test fields based on the verification logical relationship, and the specific selection is based on the actual situation. The embodiments of this specification do not impose any restrictions on this. In one possible implementation of this specification, the verification logical relationship can be directly determined as the test logical relationship. In another possible implementation of this specification, on the basis of determining the verification logical relationship as the test logical relationship, other logical relationships other than the verification logical relationship can also be randomly selected as the test logical relationship, thereby improving the richness of the test data.

[0066] By applying the solution of the embodiment of this specification, the test logic relationship between the test fields is determined according to the verification logic relationship, so that the test data can cover a policy to be verified with richer content, thereby improving the flexibility of policy verification.

[0067] Step 206: Use the strategy to be verified to test the test data and obtain the test result.

[0068] It should be noted that the test result is used to describe the result obtained by running the test data under the strategy to be verified. The test result can be either pass or fail.

[0069] Step 208: Determine the policy verification result of the policy to be verified according to the expected verification result and the test result.

[0070] It should be noted that the policy verification result refers to the conclusion on the effectiveness and accuracy of the policy after the verification of the policy to be verified. The policy verification result may include the policy configuration information, policy verification information, test data and verification results of the policy to be verified, where the verification results include pass and fail (fail).

[0071] In actual applications, when determining the policy verification result of the policy to be verified based on the expected verification result and the test result, it is determined whether the test result is the same as the corresponding expected verification result. If so, the policy verification result is determined to be passed. If not, the policy verification result is determined to be failed or not passed.

[0072] For example, assume that the policy 1 to be verified is "If the number of historical policies is less than or equal to 3 and the policy amount is less than 500,000, you can be insured." Test field 1: number of historical policies and policy amount. Test field value 1: number of historical policies is 4 and policy amount is 450,000. Test result 1: passed. Verification field 1: number of historical policies and policy amount. Verification field value 1: number of historical policies is 4 and policy amount is 450,000. Verification expected result 1: failed. Since test result 1 is different from verification expected result 1, it means that the policy verification result 1 of policy 1 to be verified is failed.

[0073] Assume that policy 2 to be verified is "Individuals between the ages of 18 and 65 can purchase insurance policies." Test field 2: Age. Test field value 2: 55 years old. Test result 2: Passed. Verification field 2: Age. Verification field value 2: 55 years old. Verification expected result 2: Passed. Since test result 2 is the same as verification expected result 2, it means that policy verification result 2 of policy 2 to be verified is passed.

[0074] By applying the solution of the embodiments of this specification, the efficiency of policy verification is improved by automatically constructing test data for the policy to be verified and performing automated testing on the test data. Furthermore, since the test data is obtained based on policy verification information, the correspondence between the expected verification results and the test results can be guaranteed, thereby improving the accuracy of the policy verification results.

[0075] In an optional embodiment of the present specification, after determining the policy verification result of the policy to be verified according to the expected verification result and the test result, the following steps may also be included: When the policy verification result is a verification failure, the policy verification result is analyzed to generate a verification analysis report of the policy to be verified, wherein the verification analysis report includes at least one of a result view, a failure reason, and a modification suggestion.

[0076] It should be noted that if the policy verification result is a verification failure, it means that the policy to be verified cannot operate in the expected manner and cannot achieve the expected goal in the actual application scenario. The verification analysis report is a detailed analysis and summary of the policy verification results, which is intended to help understand the reasons for the verification failure and provide corresponding modification suggestions. The verification analysis report usually includes the following parts: result view, failure reasons, and modification suggestions.

[0077] The result view is a visual chart of the policy verification process. Through the result view, users can understand the overall verification status of the policy to be verified. The result view includes but is not limited to the following: total test data, number of passed test data, number of failed test data, pass rate (the ratio of the number of passed test data to the total number of test data), and failure rate (the ratio of the number of failed test data to the total number of test data). The failure cause is the specific reason that caused the verification of the policy to be verified to fail. The modification suggestion is a solution and improvement measure proposed for the failure cause, aiming to optimize the policy to be verified and ensure that it can pass the verification in future tests.

[0078] In practical applications, there are many ways to analyze the policy verification results and generate a verification analysis report for the policy to be verified. The specific method is selected according to the actual situation, and the embodiments of this specification do not impose any restrictions on this. In one possible implementation of this specification, an automated testing framework can be used to write a verification analysis script. In the event of a verification failure, the verification analysis script is used to automatically analyze the policy configuration information, policy verification information, and test data of the policy to be verified to generate a verification analysis report. In another possible implementation of this specification, the policy configuration information, policy verification information, and test data can be input into a verification analysis model to obtain a verification analysis report output by the verification analysis model. Among them, the verification analysis model can be a large model, or it can be a deep learning model trained based on sample policy configuration information, sample policy verification information, sample test data, and sample verification analysis report.

[0079] For example, when analyzing the strategy verification results and generating a verification analysis report for the strategy to be verified, the test results of all test data can be summarized to provide a comprehensive result view to help users understand the overall verification situation. Errors that occur during the verification process are automatically analyzed, and detailed error information and solution suggestions are provided to help users quickly locate and solve problems.

[0080] It is worth noting that the policy verification result can be analyzed not only when the policy verification result is verification failure, but also when the policy verification result is verification pass, to generate a verification analysis report for the policy to be verified. In this case, the verification analysis report does not include the failure reason, but may include at least one of the result view and optimization suggestions, so as to make the verification process clearer and provide users with optimization suggestions for the policy to be verified.

[0081] By applying the solution of the embodiments of this specification, a comprehensive analysis is performed on the policy verification results that failed verification, and a verification analysis report including key information such as pass rate, error details, and data coverage analysis can be generated. Intuitive statistical charts and visual reports are provided to enable users to intuitively understand the execution effect of the policy and help users evaluate the effectiveness and accuracy of the policy to be verified.

[0082] The following combination Figure 3 , taking the application of the strategy verification method provided in this specification in the dual-core risk control strategy verification scenario as an example, the strategy verification method is further explained. Figure 3 A process flow chart of a policy verification method provided by an embodiment of the present specification is shown. The policy verification method is applied to a policy verification system. The policy verification system includes a policy configuration information acquisition unit (used to acquire policy configuration information), a policy verification information acquisition unit (used to acquire policy verification information), a test data generation unit (used to generate test data), a test unit (used to generate test results), and a policy verification result generation unit (used to generate policy verification results). Next, these five units are described in detail.

[0083] Policy configuration information acquisition unit: The policy configuration information acquisition unit provides a friendly and intuitive graphical interface for the verification process of the two-core risk control policy, ensuring that users have a good experience when configuring and managing policy verification tasks. For example, the policy administrator of an insurance company can select the configuration fields of the two-core risk control policy through this interface and configure the configuration of the field values. In actual applications, in order to ensure the security of the policy verification system and the standardization of user operations, the policy configuration information acquisition unit can integrate the identity authentication unit and the authority management unit. In the identity authentication unit, the user's identity can be verified. Only when the identity authentication is passed can the user perform policy verification. The authority management unit configures different operation permissions in the system for different user roles. The policy configuration information acquisition unit also configures a wizard function, which guides the user to step by step complete the configuration, configuration field value, verification field value generation method, and configuration logical relationship configuration items through configuration guidance information, thereby simplifying the configuration process. At the same time, when the user enters or selects a configuration item, the policy configuration information acquisition unit can verify the correctness of the policy configuration information in real time, avoid policy configuration information errors, and improve the accuracy of the policy configuration information.

[0084] Policy verification information acquisition unit: Users can flexibly configure the policy verification information of the two-core risk control policy through the policy verification information acquisition unit, where the policy verification information includes verification fields, verification field values, and verification expected results. Users can select verification fields from a predefined candidate field library, which can be dynamically expanded to support new verification fields. In order to meet the needs of different policy verifications, the policy verification information acquisition unit supports multiple verification field value generation methods, including fixed values, random generation, acquisition from API interfaces, and custom generation by Groovy scripts, etc. Each generation method provides corresponding logic. The policy verification information acquisition unit also provides a visual logical relationship component, allowing users to define complex verification logical relationships through drag-and-drop operations and conditional settings, and supports simulation of verification logical relationships to ensure the correctness of logical configuration. For example, verify the accuracy and rationality of the policy under different user attribute combinations. The policy verification information of all two-core risk control policies can be stored in the database to ensure the persistence and reusability of the configuration.

[0085] Test data generation unit: The test data generation unit can automatically generate the test data required for the two-core risk control strategy based on the policy verification information in the policy verification information acquisition unit to ensure that all possible test scenarios are covered. For example, the test data generation unit can generate combined data of different ages, genders, and health conditions to verify the applicability and effectiveness of the two-core risk control strategy in different situations. The test data generation unit can efficiently generate large-scale test data through multi-threaded parallel generation technology. The system supports obtaining test data from multiple data sources (such as databases, files, APIs, etc.), and performs adaptive data conversion and cleaning to ensure the accuracy and consistency of test data. Specifically, the test data generation unit can automatically generate a test data set covering all possible test scenarios based on the verification field value generation method and verification logic relationship configured by the user, support data coverage analysis, and ensure the comprehensiveness of the test data. The generated test data can be stored in a database or file system, and a data management interface is provided to support data query, modification, and deletion operations, so as to facilitate user management and use of test data.

[0086] Test unit: The test unit can use multi-threading technology to perform parallel testing on test data to further improve verification efficiency. For existing strategies, existing test data can be reused directly without regenerating test data. In addition, the test unit supports policy version control and historical version rollback to determine a more effective dual-core risk control strategy. At the same time, the test unit can have a built-in exception handling mechanism to automatically capture and handle exceptions that occur during the verification process, and generate detailed error reports to help users quickly locate and solve problems.

[0087] Policy verification result generation unit: The policy verification result generation unit can conduct a comprehensive analysis of the policy verification results and generate a detailed verification report to help users evaluate the effectiveness and accuracy of the policy.

[0088] By applying the automated verification scheme for the two-core risk control strategy proposed in the embodiment of this specification, test data for the two-core risk control strategy is automatically constructed and automated testing of the test data is performed, thereby improving the efficiency of strategy verification. Furthermore, since the test data is obtained based on the strategy verification information, the correspondence between the expected verification results and the test results can be guaranteed, thereby improving the accuracy of the strategy verification results, greatly reducing manual intervention, and ensuring that the two-core risk control strategy can effectively manage risks and achieve the expected goals.

[0089] See also Figure 4 , Figure 4The following is a schematic diagram of an interface of a policy verification interface provided by an embodiment of the present specification. The policy verification interface is divided into an information configuration interface and a result display interface. The information configuration interface includes a configuration guide box, a candidate field library, an information input box, an "OK" control, and a "Cancel" control, wherein the configuration guide box is used to display configuration guide information. The result display interface includes a result display box.

[0090] Based on the configuration guidance information displayed by the client, the user selects a verification field from the candidate field library, enters the verification field in the information input box, and clicks the "OK" control. The server receives the verification field sent by the client, generates a verification field value for the verification field, and sends the verification field value to the client. The client enters the expected verification result configured for the verification field value in the information input box. Based on the policy verification information, the server constructs test data for the policy to be verified, where the test data includes test fields and test field values; uses the policy to be verified to test the test data and obtain test results; determines the policy verification result of the policy to be verified based on the expected verification result and the test result; and sends the policy verification result to the client. The client displays the policy verification result in the result display box.

[0091] In actual applications, users can operate controls by clicking, double-clicking, touching, hovering the mouse, sliding, long pressing, voice control, or shaking, etc. The selection is based on actual conditions, and the embodiments of this specification do not impose any limitations on this.

[0092] Corresponding to the above-mentioned strategy verification method embodiment, this specification also provides a strategy verification device embodiment, Figure 5 FIG. 1 shows a schematic diagram of a strategy verification device provided by an embodiment of the present specification. Figure 5 As shown, the device comprises: A first acquisition module 502 is configured to acquire the policy to be verified and policy verification information of the policy to be verified, wherein the policy verification information includes a verification field, a verification field value, and an expected verification result; A construction module 504 is configured to construct test data of the policy to be verified based on the policy verification information, wherein the test data includes a test field and a test field value; The testing module 506 is configured to test the test data using the strategy to be verified and obtain the test result; The first determination module 508 is configured to determine a policy verification result of the policy to be verified according to the expected verification result and the test result.

[0093] Optionally, the first acquisition module 502 is further configured to send configuration guidance information to the client in response to a policy verification request; receive policy configuration information sent by the client based on the configuration guidance information, wherein the policy configuration information includes configuration fields and configuration field values; determine the policy to be verified based on the policy configuration information, and obtain policy verification information of the policy to be verified.

[0094] Optionally, the device also includes: a second acquisition module, configured to obtain configuration conditions corresponding to the policy configuration information; the first acquisition module 502, further configured to determine the policy to be verified based on the policy configuration information when the policy configuration information meets the configuration conditions, and obtain policy verification information of the policy to be verified.

[0095] Optionally, the first acquisition module 502 is further configured to display a candidate field library to the client, wherein the candidate field library includes multiple candidate verification fields; receive the verification field sent by the client, and generate a verification field value for the verification field, wherein the verification field is selected by the client from the candidate field library; send the verification field value to the client; and receive the expected verification result sent by the client for the verification field value.

[0096] Optionally, the policy verification information also includes a verification logical relationship between verification fields; the device also includes: a display module configured to display multiple logical relationship components to the client; and determine the verification logical relationship in response to the client's operation on the multiple logical relationship components.

[0097] Optionally, the construction module 504 is further configured to obtain a generation method of a test field and a verification field value, wherein the test field at least includes a verification field; and generate a test field value corresponding to the test field based on the generation method.

[0098] Optionally, there are multiple verification fields, and the policy verification information also includes a verification logical relationship between the verification fields; the device also includes: a second determination module configured to determine a test logical relationship between the test fields according to the verification logical relationship.

[0099] Optionally, the device also includes: a generation model, which is configured to analyze the policy verification result and generate a verification analysis report for the policy to be verified when the policy verification result is a verification failure, wherein the verification analysis report includes at least one of a result view, a failure reason, and a modification suggestion.

[0100] By applying the solution of the embodiments of this specification, the efficiency of policy verification is improved by automatically constructing test data for the policy to be verified and performing automated testing on the test data. Furthermore, since the test data is obtained based on policy verification information, the correspondence between the expected verification results and the test results can be guaranteed, thereby improving the accuracy of the policy verification results.

[0101] The above is a schematic scheme of a policy verification device of this embodiment. It should be noted that the technical scheme of the policy verification device and the technical scheme of the above policy verification method belong to the same concept, and the details not described in detail in the technical scheme of the policy verification device can be referred to the description of the technical scheme of the above policy verification method.

[0102] Figure 6 The block diagram of a computing device provided by an embodiment of the present specification is shown. The components of the computing device 600 include but are not limited to a memory 610 and a processor 620. The processor 620 is connected to the memory 610 via a bus 630, and the database 650 is used to store data.

[0103] The computing device 600 also includes an access device 640 that enables the computing device 600 to communicate via one or more networks 660. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 640 may include one or more of any type of network interface (e.g., a network interface card (NIC)) of wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a world microwave interconnection access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.

[0104] In one embodiment of the present specification, the above components of the computing device 600 and Figure 6 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 6 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0105] The computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 600 may also be a mobile or stationary server.

[0106] The processor 620 is used to execute a computer program / instruction, which implements the steps of the above-mentioned policy verification method when executed by the processor.

[0107] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the above-mentioned policy verification method belong to the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the above-mentioned policy verification method.

[0108] An embodiment of the present specification further provides a computer-readable storage medium storing a computer program / instruction, which implements the steps of the above-mentioned policy verification method when executed by a processor.

[0109] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the above-mentioned policy verification method belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the above-mentioned policy verification method.

[0110] An embodiment of the present specification also provides a computer program product, including a computer program / instruction, which implements the steps of the above-mentioned policy verification method when executed by a processor.

[0111] The above is a schematic scheme of a computer program product of this embodiment. It should be noted that the technical scheme of the computer program product and the technical scheme of the above-mentioned policy verification method belong to the same concept, and the details not described in detail in the technical scheme of the computer program product can be referred to the description of the technical scheme of the above-mentioned policy verification method.

[0112] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0113] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0114] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0115] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0116] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to only the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can well understand and use this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. A strategy verification method, characterized in that: include: Acquire a policy to be verified and policy verification information of the policy to be verified, wherein the policy verification information includes a verification field, a verification field value, and an expected verification result; Based on the policy verification information, construct test data of the policy to be verified, wherein the test data includes a test field and a test field value; Using the strategy to be verified, testing the test data to obtain a test result; A policy verification result of the policy to be verified is determined according to the expected verification result and the test result.

2. The method according to claim 1, characterized in that: The obtaining of the policy to be verified and the policy verification information of the policy to be verified includes: In response to the policy verification request, sending configuration guidance information to the client; Receiving policy configuration information sent by the client based on the configuration guidance information, wherein the policy configuration information includes a configuration field and a configuration field value; The policy to be verified is determined based on the policy configuration information, and policy verification information of the policy to be verified is obtained.

3. The method according to claim 2, characterized in that Before determining the to-be-verified policy based on the policy configuration information and obtaining the policy verification information of the to-be-verified policy, the method further includes: Obtaining configuration conditions corresponding to the policy configuration information; The determining the policy to be verified based on the policy configuration information and obtaining policy verification information of the policy to be verified includes: In a case where the policy configuration information meets the configuration condition, the policy to be verified is determined based on the policy configuration information, and policy verification information of the policy to be verified is acquired.

4. The method according to claim 2, characterized in that: The obtaining of the policy verification information of the policy to be verified includes: Presenting a candidate field library to the client, wherein the candidate field library includes a plurality of candidate verification fields; receiving a verification field sent by the client, and generating a verification field value of the verification field, wherein the verification field is selected by the client from the candidate field library; Sending the verification field value to the client; Receive the expected verification result sent by the client for the verification field value.

5. The method according to claim 3, characterized in that: The policy verification information also includes the verification logic relationship between the verification fields; the method further includes: Displaying multiple logical relationship components to the client; The verification logical relationship is determined in response to the client's operation on the plurality of logical relationship components.

6. The method according to claim 1, characterized in that The step of constructing test data for the strategy to be verified based on the strategy verification information includes: Acquire a method for generating a test field and a verification field value, wherein the test field at least includes the verification field; Based on the generating method, a test field value corresponding to the test field is generated.

7. The method according to claim 6, characterized in that There are multiple verification fields, and the policy verification information also includes a verification logic relationship between the verification fields; After generating the test field value corresponding to the test field based on the generating method, the method further includes: According to the verification logic relationship, the test logic relationship between the test fields is determined.

8. The method according to any one of claims 1 to 7, characterized in that: After determining the policy verification result of the policy to be verified according to the expected verification result and the test result, the method further includes: In the case that the policy verification result is a verification failure, the policy verification result is analyzed to generate a verification analysis report of the policy to be verified, wherein the verification analysis report includes at least one of a result view, a failure reason, and a modification suggestion.

9. A policy verification system, characterized in that: Including client and server; The client is used to send the policy to be verified and policy verification information of the policy to be verified to the server, wherein the policy verification information includes a verification field, a verification field value, and an expected verification result; The server is used to construct test data for the policy to be verified based on the policy verification information, wherein the test data includes test fields and test field values; use the policy to be verified to test the test data to obtain test results; and determine the policy verification result of the policy to be verified based on the expected verification result and the test result.

10. A strategy verification device, characterized in that: include: A first acquisition module is configured to acquire a policy to be verified and policy verification information of the policy to be verified, wherein the policy verification information includes a verification field, a verification field value, and an expected verification result; A construction module, configured to construct test data of the policy to be verified based on the policy verification information, wherein the test data includes a test field and a test field value; A testing module is configured to test the test data using the strategy to be verified to obtain a test result; The first determination module is configured to determine a policy verification result of the policy to be verified according to the expected verification result and the test result.

11. A computing device, characterized in that: include: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer program / instructions are executed by the processor, the steps of the method according to any one of claims 1 to 8 are implemented.

12. A computer-readable storage medium, characterized in that: It stores a computer program / instruction, which implements the steps of the method described in any one of claims 1 to 8 when executed by a processor.

13. A computer program product, characterized in that The method comprises a computer program / instruction which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.

Images