A parameter verification method, device, system, medium and product

Abstract

The application discloses a parameter verification method, device and system, medium and product, and the method applied to a business platform comprises the following steps: displaying a rule configuration page; acquiring rule configuration data entered in the rule configuration page, and generating a verification rule file according to the rule configuration data and a preset rule template; wherein the rule configuration data comprises a scene verification rule, an information verification object corresponding to network communication information and a parameter verification rule; and the verification rule file is published, so that a rule execution engine executes the verification rule file according to scene data to be verified and communication information to be verified sent by a client to obtain a parameter verification result, thereby solving the problem of low publishing efficiency of the verification rule file, and improving the accuracy and flexibility of the verification rule file.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of Internet technology, and in particular to a parameter verification method, device, system, medium and product. Background Technology

[0002] With the development of internet technology, clients need to validate an increasing amount of parameter data. Currently, validation rule files require manual compilation by developers, which not only makes the release of validation rule files inefficient but also fails to guarantee their accuracy. Summary of the Invention

[0003] This invention provides a parameter verification method, apparatus, system, medium, and product to solve the problem of low efficiency in publishing verification rule files and improve the accuracy and flexibility of verification rule files.

[0004] In a first aspect, embodiments of the present invention provide a parameter verification method applied to a business platform, the method comprising:

[0005] Display the rules configuration page;

[0006] Obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file based on the rule configuration data and the preset rule template; wherein, the rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules;

[0007] The verification rule file is published so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified sent by the client.

[0008] Secondly, embodiments of the present invention provide a parameter verification method applied to a client, the method comprising:

[0009] Obtain the verification rule file published by the business platform;

[0010] The scene data to be verified is determined according to the scene verification rules in the verification rule file;

[0011] Based on the list of verification objects, the communication information to be verified is determined; wherein, the list of verification objects contains at least one information verification object;

[0012] The scenario data to be verified and the communication information to be verified are sent to the rule execution engine, so that the rule execution engine can execute the verification rule file according to the scenario data to be verified and the communication information to be verified to obtain the parameter verification result;

[0013] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0014] Thirdly, embodiments of the present invention provide a parameter verification method applied to a rule execution engine, the method comprising:

[0015] Obtain the verification rule file published by the business platform;

[0016] Receive the scenario data and communication information to be verified sent by the client;

[0017] Based on the scenario data to be verified and the communication information to be verified, the verification rule file is executed to obtain the parameter verification result;

[0018] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0019] Fourthly, embodiments of the present invention provide a parameter verification device applied to a business platform, the device comprising:

[0020] The rule configuration page display module is used to display the rule configuration page;

[0021] The verification rule file generation module is used to obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file according to the rule configuration data and the preset rule template; wherein, the rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules;

[0022] The verification rule file publishing module is used to publish the verification rule file so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified sent by the client.

[0023] Fifthly, embodiments of the present invention provide a parameter verification device applied to a client, the device comprising:

[0024] The verification rule file acquisition module is used to acquire the verification rule files published by the business platform;

[0025] The module for determining the scene data to be verified is used to determine the scene data to be verified based on the scene verification rules in the verification rule file.

[0026] The communication information to be verified module is used to determine the communication information to be verified based on the verification object list; wherein the verification object list contains at least one information verification object;

[0027] The communication information sending module is used to send the scenario data to be verified and the communication information to be verified to the rule execution engine, so that the rule execution engine can execute the verification rule file according to the scenario data to be verified and the communication information to be verified to obtain the parameter verification result;

[0028] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0029] Sixthly, embodiments of the present invention provide a parameter verification device applied to a rule execution engine, the device comprising:

[0030] The verification rule file acquisition module is used to acquire the verification rule files published by the business platform;

[0031] The communication information receiving module to be verified is used to receive the scenario data and communication information to be verified sent by the client.

[0032] The parameter verification result determination module is used to execute the verification rule file to obtain the parameter verification result based on the scenario data to be verified and the communication information to be verified.

[0033] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0034] In a seventh aspect, embodiments of the present invention provide a parameter verification system, the system comprising: a business platform, a client communicatively connected to the business platform, and a rule execution engine communicatively connected to both the business platform and the client;

[0035] The business platform is used to display a rule configuration page, obtain the rule configuration data entered in the rule configuration page, generate a verification rule file based on the rule configuration data and a preset rule template, and publish the verification rule file.

[0036] The client is configured to determine the scene data to be verified according to the scene verification rules in the verification rule file, determine the communication information to be verified according to the verification object list, and send the scene data to be verified and the communication information to be verified to the rule execution engine.

[0037] The rule execution engine is used to execute the verification rule file to obtain parameter verification results based on the scenario data to be verified and the communication information to be verified.

[0038] The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0039] Eighthly, embodiments of the present invention also provide a computer-readable storage medium storing computer instructions that are used to cause a processor to execute the parameter verification method described in any embodiment of the present invention.

[0040] In a ninth aspect, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the parameter verification method described in any embodiment of the present invention.

[0041] The technical solution of this invention involves displaying a rule configuration page, obtaining the rule configuration data entered on the rule configuration page, generating a verification rule file based on the rule configuration data and a preset rule template, and publishing the verification rule file. This allows the rule execution engine to execute the verification rule file and obtain parameter verification results based on the scenario data and communication information to be verified sent by the client. The graphical interface rule entry combined with rule templates reduces the skill requirements for developers, solves the problem of low efficiency in publishing verification rule files, and improves the accuracy and flexibility of verification rule files. Attached Figure Description

[0042] The above and other features, advantages, and aspects of the various embodiments of the present invention will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0043] Figure 1 A flowchart illustrating a parameter verification method applied to a business platform, as provided in one embodiment of the present invention;

[0044] Figure 2 This is a schematic diagram illustrating a specific example of a rule configuration page provided in one embodiment of the present invention;

[0045] Figure 3 A flowchart illustrating another parameter verification method applied to a business platform, as provided in one embodiment of the present invention;

[0046] Figure 4A flowchart illustrating a parameter verification method applied to a client, as provided in one embodiment of the present invention;

[0047] Figure 5 A flowchart illustrating another parameter verification method applied to a client, as provided in one embodiment of the present invention;

[0048] Figure 6 A functional architecture diagram of another specific instance of a client provided in one embodiment of the present invention;

[0049] Figure 7 A flowchart illustrating a parameter verification method applied to a rule execution engine, as provided in an embodiment of the present invention;

[0050] Figure 8 The diagram illustrates the principle architecture of a specific example of a rule execution engine provided in one embodiment of the present invention.

[0051] Figure 9 This is a schematic diagram of a parameter verification device applied to a business platform according to an embodiment of the present invention;

[0052] Figure 10 This is a schematic diagram of a parameter verification device applied to a client according to an embodiment of the present invention;

[0053] Figure 11 This is a schematic diagram of a parameter verification device applied to a rule execution engine, provided in one embodiment of the present invention.

[0054] Figure 12 This is a schematic diagram of the structure of a parameter verification system provided in one embodiment of the present invention;

[0055] Figure 13 A system flowchart illustrating a specific example of a parameter verification system provided in one embodiment of the present invention;

[0056] Figure 14 This is a schematic diagram of the structure of an electronic device provided in one embodiment of the present invention. Detailed Implementation

[0057] Embodiments of the present invention will now be described in more detail with reference to the accompanying drawings. While some embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the invention. It should be understood that the accompanying drawings and embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the invention.

[0058] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0059] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0060] It should be noted that the concepts of "first" and "second" mentioned in this invention are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0061] It should be noted that the terms "a" and "a plurality of" used in this invention are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0062] The names of the messages or information exchanged between the multiple devices in the embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0063] It is understood that before using the technical solutions disclosed in the various embodiments of the present invention, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in the present invention and their authorization should be obtained in accordance with relevant laws and regulations through appropriate means.

[0064] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application program, server, or storage medium executing the operation of this invention, based on the prompt message.

[0065] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0066] It is understood that the above notification and user authorization process is merely illustrative and does not constitute a limitation on the implementation of the present invention. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present invention.

[0067] Figure 1 This is a flowchart illustrating a parameter verification method applied to a business platform according to an embodiment of the present invention. This embodiment is applicable to situations where parameters of network communication information initiated by a client are verified. The method can be executed by a parameter verification device, which can be implemented in hardware and / or software and can be configured within the business platform. Figure 1 As shown, the method includes:

[0068] S110, Display rule configuration page.

[0069] Specifically, the rule configuration page represents a graphical user interface (GUI) for configuring the rule content of validation rules. For example, the rule configuration page includes, but is not limited to, interactive elements such as text input boxes, drop-down menus, and checkboxes.

[0070] S120. Obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file based on the rule configuration data and the preset rule template.

[0071] In this embodiment, the rule configuration data includes scene verification rules, information verification objects corresponding to network communication information, and parameter verification rules. Specifically, scene verification rules represent the scene triggering conditions of parameter verification rules, information verification objects represent the information content in network communication information, and parameter verification rules represent the verification rules corresponding to the rule verification parameters in network communication information.

[0072] Specifically, scenario validation rules include scenario validation conditions within a rule validation scenario. For example, rule validation scenarios include, but are not limited to, user movement paths or order chains. A user movement path represents the behavioral path a user takes while browsing and operating within the client, and scenario data corresponding to the user movement path includes, but is not limited to, opening the client, browsing a specific page, and entering a product details page. An order chain represents the processing path an order takes from creation to completion in the business process, and scenario data corresponding to the order chain includes, but is not limited to, order creation, order payment, order delivery, and order receipt.

[0073] In one optional embodiment, the information type of the network communication information is either a network request or a routing schema. Specifically, when the information type of the network communication information is a network request, the network communication information is a network communication request sent by the client to the server; when the information type of the network communication information is a routing schema, the network communication information is a network routing schema defined by the server, which represents the routing mapping relationship between the request path in the network communication request and the processing program within the server.

[0074] Taking network communication requests as an example, the information verification objects include, but are not limited to, the request method, request protocol, request domain name, and request path in the network communication request. The request method includes, but is not limited to, GET, POST, PUT, or DELETE methods.

[0075] Specifically, parameter validation rules include the parameter validation conditions for the rule-validated parameters.

[0076] In this embodiment, the verification rule file follows the rule format of "IF - WHEN - THEN," meaning that if the scenario verification rule is satisfied, the parameter verification rule is executed when network communication information containing the information verification object is detected. The order of "IF" and "WHEN" is not limited here. For example, IF: the user triggers a bill of lading action from the video stream account; WHEN: initiates a network communication request containing the bill of lading verification object; THEN: verifies whether the bill of lading merchant parameter in the network communication request is not equal to null.

[0077] Based on the above embodiments, optionally, the rule configuration data also includes rule description data and / or an applicable client version range. The rule description data describes the verification functionality of the verification rule file, and the applicable client version range represents a version range consisting of at least one client version that can execute the verification rule file. For example, the client version range can be higher than a specified version number or lower than a specified version number.

[0078] Figure 2 This is a schematic diagram illustrating a specific example of a rule configuration page provided in one embodiment of the present invention. Specifically, Figure 2In this context, "Validation Object" represents the interactive element corresponding to the information validation object, "Rule Description" represents the interactive element corresponding to the rule description data, "Effective Version" represents the interactive element corresponding to the applicable client version range, and "Scenario Definition" represents the interactive element corresponding to the scenario validation rule. The "Validation Scenario," "Condition," and "Value" in the "Validation Definition" section together constitute the scenario validation rule. Similarly, "Rule Definition" represents the interactive element corresponding to the parameter validation rule, where the "Validation Parameter," "Condition," and "Value" in the "Rule Definition" section together constitute the parameter validation rule.

[0079] exist Figure 2 In the "Scene Definition" and "Scene ID" in "Rule Definition", the "ID" is defined as the rule association identifier between the scene validation rule and the parameter validation rule, which is used to identify the association relationship between the scene validation rule as the scene trigger condition of the parameter validation rule.

[0080] Understandable Figure 2 This is only used as an example to illustrate the rule configuration page and does not limit its functional layout. Any rule configuration page that can realize the entry of rule configuration data is included in the scope of this application.

[0081] In an optional embodiment, the method further includes: in response to an import operation on the rule configuration page, obtaining an import rule file corresponding to the import operation; performing a parsing operation on the import rule file, and entering the parsed rule configuration data into the rule configuration page accordingly.

[0082] Specifically, the imported rule file refers to the rule file maintained in other rule systems besides the business platform. The imported rule file defines at least one of the following configuration parameter data: scenario verification rules, information verification objects, and parameter verification rules.

[0083] The advantage of this setup is that it improves the efficiency of rule configuration data entry and broadens the application scenarios for parameter validation methods.

[0084] Specifically, the preset rule template represents a protocol-based rule template, which at least includes placeholder identifiers and placeholders corresponding to scenario verification rules, information verification objects, and parameter verification rules, respectively. For example, for scenario verification rules, the preset rule template includes placeholder identifiers corresponding to the rule association identifier, rule verification scenario, operator, and standard scenario parameter values ​​of the rule verification scenario, respectively. For information verification objects, the preset rule template includes placeholder identifiers corresponding to the information verification object and the information type of the network communication information to which the information verification object belongs, respectively. For parameter verification rules, the preset rule template includes placeholder identifiers corresponding to the rule association identifier, rule verification parameters, operator, and standard parameter values ​​corresponding to the rule verification parameters, respectively.

[0085] In one optional embodiment, the preset rule template further includes placeholder identifiers and placeholders corresponding to the applicable client version range. For example, the preset rule template includes placeholder identifiers corresponding to the smallest client version and the largest client version, respectively.

[0086] In an optional embodiment, generating a verification rule file based on rule configuration data and a preset rule template includes: extracting configuration parameters corresponding to placeholders from the rule configuration data according to placeholder identifiers in the preset rule template, and replacing the placeholders in the preset rule template with the configuration parameters to obtain the verification rule file.

[0087] S130. Publish the verification rule file so that the rule execution engine can execute the verification rule file to obtain the parameter verification results based on the scenario data and communication information to be verified sent by the client.

[0088] In one alternative embodiment, the validation rule file is published to both the client and the rule execution engine, or the validation rule file is published to the client so that the client sends the validation rule file to the rule execution engine.

[0089] Specifically, the scenario data to be verified represents the data consisting of the actual scenario parameter values ​​corresponding to the scenario verification scenario in the scenario verification rules. The communication information to be verified represents the network communication information intercepted by the client. The information type corresponding to the communication information to be verified is the same as the information type of the network communication information to which the information verification object belongs in the verification rules file.

[0090] For example, the parameter verification result includes, but is not limited to, timestamp, communication information to be verified, information type of communication information to be verified, rule verification scenario, verification result identifier, and verification details text, etc., wherein the verification result identifier is an identifier used to indicate whether the verification was successful or not.

[0091] The technical solution of this embodiment displays a rule configuration page, obtains the rule configuration data entered on the rule configuration page, generates a verification rule file based on the rule configuration data and a preset rule template, and publishes the verification rule file. This allows the rule execution engine to execute the verification rule file and obtain parameter verification results based on the scenario data and communication information to be verified sent by the client. The graphical interface rule entry combined with the rule template reduces the skill requirements for developers, solves the problem of low efficiency in publishing verification rule files, and improves the accuracy and flexibility of verification rule files.

[0092] Figure 3This is a flowchart illustrating another parameter verification method applied to a business platform according to an embodiment of the present invention. This embodiment further refines the parameter verification method applied to a business platform described in the above embodiment. For example... Figure 3 As shown, the method includes:

[0093] S210, Display rule configuration page.

[0094] In an optional embodiment, displaying a rule configuration page includes: displaying a business platform page; wherein the business platform page maintains at least one business space; in response to a display operation for a business space, displaying a business management page corresponding to the business space; and in response to a rule configuration operation in the business management page, displaying a rule configuration page for the business space.

[0095] Specifically, the business platform page represents the collection of entry points to the business platform, and the business spaces are identical to the business scenarios. For example, when the business scenario is a video stream product interaction scenario, the business spaces maintained on the business platform page include, but are not limited to, order tracking, video stream content, product search, product after-sales service, user movement, and extended service requirements. There are no restrictions on the business spaces here; they can be customized according to actual needs.

[0096] Specifically, the business management page represents a page used to manage business content related to the business space. In one optional embodiment, the business management page includes a business rules area. For example, the business rules area includes a list of rule files and a rule editor corresponding to each validation rule file. The rule file list displays at least one validation rule control corresponding to each validation rule file. For example, the rule editor includes functions for creating controls, modifying controls, validating controls, deleting controls, viewing controls, publishing controls, or renaming controls, etc.

[0097] Specifically, rule configuration operations refer to trigger operations used to implement parameter rule configurations that are the same as those in the business space. For example, rule configuration operations include, but are limited to, trigger operations for creating, modifying, or viewing controls, etc.

[0098] The advantage of this setup is that it improves the scalability of rule configuration and helps reduce the maintenance cost of parameter rules.

[0099] S220. Obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file based on the rule configuration data and the preset rule template.

[0100] S220 in this embodiment is the same as that in the above embodiment. Figure 1 The S120 shown is the same or similar, and will not be described again in this embodiment.

[0101] S230, Display rule verification page.

[0102] Based on the above embodiments, optionally, displaying the rule verification page includes: displaying the rule verification page in response to a trigger operation on the verification control in the business management page.

[0103] Specifically, the rule verification page represents a graphical user interface used to verify whether a rule file conforms to expected settings. In this embodiment, the rule verification page includes a request input area and a result display area. The request input area is used to collect network communication information entered by the user for verifying the rule file, and the result display area is used to display the parameter verification results.

[0104] S240. Send the verification communication information entered on the rule verification page to the rule execution engine so that the rule execution engine can execute the verification rule file and return the parameter verification result based on the verification communication information.

[0105] Specifically, the rule verification page also includes a verification confirmation control. Correspondingly, in response to the triggering operation of the verification confirmation control, the verification communication information entered on the rule verification page is sent to the rule execution engine.

[0106] Specifically, during the parameter verification process by the rule execution engine based on the verification communication information, in the scenario verification stage, since no verification scenario data corresponding to the verification communication information is received, it is assumed that the verification communication information meets the scenario verification rules in the verification rule file. The parameter verification rules associated with the scenario verification rules are used to perform parameter verification on the verification communication information and return the parameter verification result.

[0107] S250. Display the parameter verification results on the rule verification page.

[0108] Specifically, the parameter validation results will be displayed in the results display area on the rule validation page.

[0109] In one specific embodiment, the result verification identifier of the parameter verification result is displayed in the result display area of ​​the rule verification page. This setting improves the readability of the parameter verification results during the rule verification phase.

[0110] S260. Publish the verification rule file so that the rule execution engine can execute the verification rule file to obtain the parameter verification results based on the scenario data and communication information to be verified sent by the client.

[0111] In one optional embodiment, publishing the verification rule file includes: publishing the verification rule file to a content delivery network (CDN) so that clients can pull the verification rule file from the CDN and send the verification rule file to the rule execution engine. Here, a content delivery network (CDN) is an intelligent virtual network built on top of the existing internet infrastructure, constructed by placing node servers throughout the network.

[0112] The advantage of this setup is that it improves the efficiency of the client in obtaining the verification rule files published by the business platform and enhances the stability of the published verification rule files.

[0113] The technical solution of this embodiment, by displaying a rule verification page, sends the verification communication information entered on the rule verification page to the rule execution engine, so that the rule execution engine executes the verification rule file according to the verification communication information and returns the parameter verification result, and displays the parameter verification result on the rule verification page, thus solving the verification problem of the verification rule file and further ensuring the accuracy of the verification rule file.

[0114] Based on the above embodiments, the method may optionally further include: receiving a parameter verification result indicating verification failure uploaded by the client; wherein the parameter verification result is sent to the client by the rule execution engine; adding the parameter verification result to the monitoring dashboard; and displaying the monitoring dashboard in response to a display operation on the monitoring dashboard.

[0115] Based on the above embodiments, optionally, the method further includes: analyzing the verification results of parameters that indicate verification failure, obtaining the reason for the verification failure, and adding the reason for the verification failure to a problem dashboard; and displaying the problem dashboard in response to a display operation on the problem dashboard. For example, the reason for the verification failure may be a rule error in the verification rule file or an information error in the network communication information.

[0116] Based on the above embodiments, optionally, the method further includes: obtaining the problem handling status corresponding to the parameter verification result indicating verification failure, and updating the problem handling status in the problem dashboard. For example, the problem handling status may be pending analysis, under analysis, cause located, problem pending processing, problem resolved, etc.

[0117] Based on the above embodiments, optionally, after publishing the verification rule file, the method further includes: adding the verification rule file and the generated rule version to the rule dashboard; and displaying the rule dashboard in response to a display operation on the rule dashboard.

[0118] The advantage of this setup is that it enables the archiving of verification rule files and supports version rollback of verification rule files.

[0119] Figure 4 This is a flowchart illustrating a parameter verification method applied to a client, as provided in one embodiment of the present invention. This embodiment is applicable to situations where parameters of network communication information initiated by the client are verified. The method can be executed by a parameter verification device, which can be implemented in hardware and / or software and can be configured in the client. Figure 4 As shown, the method includes:

[0120] S310. Obtain the verification rule file published by the business platform.

[0121] In this embodiment, the verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0122] Specifically, the scenario verification rule represents the scenario triggering condition of the parameter verification rule, the information verification object represents the information content in the network communication information, and the parameter verification rule represents the verification rule corresponding to the rule verification parameter in the network communication information.

[0123] Specifically, scenario validation rules include scenario validation conditions within a rule validation scenario. For example, rule validation scenarios include, but are not limited to, user movement paths or order chains. A user movement path represents the behavioral path a user takes while browsing and operating within the client, and scenario data corresponding to the user movement path includes, but is not limited to, opening the client, browsing a specific page, and entering a product details page. An order chain represents the processing path an order takes from creation to completion in the business process, and scenario data corresponding to the order chain includes, but is not limited to, order creation, order payment, order delivery, and order receipt.

[0124] In one optional embodiment, the information type of the network communication information is either a network request or a routing schema. Specifically, when the information type of the network communication information is a network request, the network communication information is a network communication request sent by the client to the server; when the information type of the network communication information is a routing schema, the network communication information is a network routing schema defined by the server, which represents the routing mapping relationship between the request path in the network communication request and the processing program within the server.

[0125] Taking network communication requests as an example, the information verification objects include, but are not limited to, the request method, request protocol, request domain name, and request path in the network communication request. The request method includes, but is not limited to, GET, POST, PUT, or DELETE methods.

[0126] Specifically, parameter validation rules include the parameter validation conditions for the rule-validated parameters.

[0127] In this embodiment, the verification rule file follows the rule format of "IF - WHEN - THEN," meaning that if the scenario verification rule is satisfied, the parameter verification rule is executed when network communication information containing the information verification object is detected. The order of "IF" and "WHEN" is not limited here. For example, IF: the user triggers a bill of lading action from the video stream account; WHEN: initiates a network communication request containing the bill of lading verification object; THEN: verifies whether the bill of lading merchant parameter in the network communication request is not equal to null.

[0128] Based on the above embodiments, optionally, the rule configuration data also includes rule description data and / or an applicable client version range. The rule description data describes the verification functionality of the verification rule file, and the applicable client version range represents a version range consisting of at least one client version that can execute the verification rule file. For example, the client version range can be higher than a specified version number or lower than a specified version number.

[0129] The method for generating the verification rule file in this embodiment is the same as or similar to the method for generating the verification rule file in the above embodiments, and will not be repeated here.

[0130] In one optional embodiment, obtaining the verification rule file published by the business platform includes: pulling the verification rule file published by the business platform from the content delivery network. Here, a content delivery network (CDN) is an intelligent virtual network built on top of the existing internet infrastructure, constructed by placing node servers throughout the network.

[0131] The advantage of this setup is that it improves the efficiency of the client in obtaining the verification rule files published by the business platform and enhances the stability of the published verification rule files.

[0132] S320. Determine the scene data to be verified according to the scene verification rules in the verification rule file.

[0133] Specifically, obtain at least one actual scenario parameter value corresponding to the rule verification scenario in the scenario verification rules, and add each actual scenario parameter value to the scenario data to be verified.

[0134] For example, assuming the rule validation scenario is user movement, the scenario data to be validated includes behavioral paths such as opening the client, browsing a certain page, and entering the product details page.

[0135] S330. Determine the communication information to be verified based on the list of verification objects.

[0136] In this embodiment, the list of verification objects contains at least one information verification object.

[0137] In an optional embodiment, determining the communication information to be verified based on the verification object list includes: obtaining a verification object list corresponding to the information type; for each type of network communication information, if the network communication information contains information verification objects in the verification object list, then the network communication information is used as the communication information to be verified; wherein the information type is a network request or routing mode.

[0138] Specifically, the list of verification objects contains at least one information verification object corresponding to the information type. The process for determining the communication information to be verified can be implemented by interceptors set in the client. Specifically, the client sets up interceptors corresponding to network requests and interceptors corresponding to routing modes, with each interceptor corresponding to a separate list of verification objects.

[0139] S340. Send the scenario data to be verified and the communication information to be verified to the rule execution engine so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data to be verified and the communication information to be verified.

[0140] For example, the parameter verification result includes, but is not limited to, timestamp, communication information to be verified, information type of communication information to be verified, rule verification scenario, verification result identifier, and verification details text, etc., wherein the verification result identifier is an identifier used to indicate whether the verification was successful or not.

[0141] The technical solution of this embodiment obtains the verification rule file published by the business platform, determines the scenario data to be verified based on the scenario verification rules in the verification rule file, determines the communication information to be verified based on the verification object list, and sends the scenario data to be verified and the communication information to be verified to the rule execution engine. The rule execution engine then executes the verification rule file to obtain the parameter verification result based on the scenario data to be verified and the communication information to be verified. The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The graphical interface rule entry combined with the rule template reduces the skill requirements of developers, solves the problem of low efficiency in publishing verification rule files, and improves the accuracy and flexibility of verification rule files.

[0142] Figure 5 This is a flowchart illustrating another parameter verification method applied to a client, provided by an embodiment of the present invention. This embodiment further refines the parameter verification method applied to a client described in the above embodiment. For example... Figure 5 As shown, the method includes:

[0143] S410. Obtain the verification rule file published by the business platform.

[0144] S420. Determine the scene data to be verified according to the scene verification rules in the verification rule file.

[0145] S430. Determine the communication information to be verified based on the list of verification objects.

[0146] S440. Send the scenario data to be verified and the communication information to be verified to the rule execution engine, so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data to be verified and the communication information to be verified.

[0147] S410-S440 in this embodiment are the same as those in the above embodiments. Figure 4 The S310-S340 shown are the same or similar, and will not be described again in this embodiment.

[0148] S450: Receives the parameter verification results sent by the rule execution engine.

[0149] S460. If the parameter verification result indicates a verification failure, the parameter verification result is reported to the business platform according to the client's test attributes, so that the business platform can add the parameter verification result to the monitoring dashboard.

[0150] In one optional embodiment, the parameter verification result is uploaded to the business platform according to the client's test attributes, including: if the client's test attributes are offline testing, displaying an alarm pop-up window based on the parameter verification result, and responding to the reporting operation in the alarm pop-up window by reporting the parameter verification result to the business platform; if the client's test attributes are online deployment, reporting the parameter verification result as data points to the business platform.

[0151] Specifically, the offline testing client is used to identify as many parameter issues as possible before online deployment. The users of the offline testing client are primarily testers, and it typically runs in a test environment. In this embodiment, the offline testing client can be used for parameter verification of network communication information.

[0152] Specifically, an alarm pop-up is a user interface element used to display the parameter validation result indicating a validation failure. In one optional embodiment, the alarm pop-up includes a reporting control and a cancellation control.

[0153] Specifically, online deployed clients refer to clients with stable service performance running in a real production environment. The purpose of data tracking is to achieve seamless reporting of parameter validation results.

[0154] In one optional embodiment, the business platform includes an offline alarm response area corresponding to clients used in offline testing and an online alarm response area corresponding to clients deployed online. The offline alarm response area is used to collect and record parameter verification results reported by clients used in offline testing, while the online alarm response area is used to collect and record parameter verification results reported by clients deployed online.

[0155] Figure 6 This is a functional architecture diagram of another specific instance of a client provided in one embodiment of the present invention. Specifically, interceptor 1 intercepts network communication requests according to the verification object list corresponding to the network request, and sends the intercepted communication requests to be verified to the rule execution engine. Interceptor 2 intercepts network routing modes according to the verification object list corresponding to the routing mode, and sends the intercepted routing modes to be verified to the rule execution engine. The verification rule file and user movement are sent to the rule execution engine through a JavaScript Bridge (JSB) mechanism. The system receives the parameter verification results from the rule engine and, if the client's test attribute is offline testing, reports the parameter verification results to the business platform via an alarm pop-up; if the client's test attribute is online deployment, the parameter verification results are reported to the business platform via data entry point reporting.

[0156] The technical solution of this embodiment receives the parameter verification result sent by the rule execution engine. When the parameter verification result indicates that the verification failed, the parameter verification result is uploaded to the business platform according to the test attributes of the client. This solves the problem of reporting parameter verification results, enriches the reporting methods of parameter verification results, and broadens the applicable scenarios of parameter verification methods.

[0157] Figure 7 This is a flowchart illustrating a parameter verification method applied to a rule execution engine according to an embodiment of the present invention. This embodiment is applicable to situations where parameters of network communication information initiated by a client are verified. The method can be executed by a parameter verification device, which can be implemented in hardware and / or software and can be configured within the rule execution engine. Figure 7 As shown, the method includes:

[0158] S510. Obtain the verification rule file published by the business platform.

[0159] In this embodiment, the verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0160] Specifically, the scenario verification rule represents the scenario triggering condition of the parameter verification rule, the information verification object represents the information content in the network communication information, and the parameter verification rule represents the verification rule corresponding to the rule verification parameter in the network communication information.

[0161] Specifically, scenario validation rules include scenario validation conditions within a rule validation scenario. For example, rule validation scenarios include, but are not limited to, user movement paths or order chains. A user movement path represents the behavioral path a user takes while browsing and operating within the client, and scenario data corresponding to the user movement path includes, but is not limited to, opening the client, browsing a specific page, and entering a product details page. An order chain represents the processing path an order takes from creation to completion in the business process, and scenario data corresponding to the order chain includes, but is not limited to, order creation, order payment, order delivery, and order receipt.

[0162] In one optional embodiment, the information type of the network communication information is either a network request or a routing schema. Specifically, when the information type of the network communication information is a network request, the network communication information is a network communication request sent by the client to the server; when the information type of the network communication information is a routing schema, the network communication information is a network routing schema defined by the server, which represents the routing mapping relationship between the request path in the network communication request and the processing program within the server.

[0163] Taking network communication requests as an example, the information verification objects include, but are not limited to, the request method, request protocol, request domain name, and request path in the network communication request. The request method includes, but is not limited to, GET, POST, PUT, or DELETE methods.

[0164] Specifically, parameter validation rules include the parameter validation conditions for the rule-validated parameters.

[0165] In this embodiment, the verification rule file follows the rule format of "IF - WHEN - THEN," meaning that if the scenario verification rule is satisfied, the parameter verification rule is executed when network communication information containing the information verification object is detected. The order of "IF" and "WHEN" is not limited here. For example, IF: the user triggers a bill of lading action from the video stream account; WHEN: initiates a network communication request containing the bill of lading verification object; THEN: verifies whether the bill of lading merchant parameter in the network communication request is not equal to null.

[0166] Based on the above embodiments, optionally, the rule configuration data also includes rule description data and / or an applicable client version range. The rule description data describes the verification functionality of the verification rule file, and the applicable client version range represents a version range consisting of at least one client version that can execute the verification rule file. For example, the client version range can be higher than a specified version number or lower than a specified version number.

[0167] The method for generating the verification rule file in this embodiment is the same as or similar to the method for generating the verification rule file in the above embodiments, and will not be repeated here.

[0168] In one optional embodiment, obtaining the verification rule file published by the business platform includes: receiving a verification rule file sent by a client, wherein the verification rule file is published by the business platform to the content delivery network and retrieved by the client from the content delivery network. Here, a content delivery network (CDN) is an intelligent virtual network built on top of the existing internet infrastructure, constructed by placing node servers throughout the network.

[0169] The advantage of this setup is that it improves the efficiency of the client in obtaining the verification rule files published by the business platform and enhances the stability of the published verification rule files.

[0170] S520 receives the scenario data and communication information to be verified sent by the client.

[0171] Specifically, the scenario data to be verified represents the data consisting of the actual scenario parameter values ​​corresponding to the scenario verification scenario in the scenario verification rules. The communication information to be verified represents the network communication information intercepted by the client. The information type corresponding to the communication information to be verified is the same as the information type of the network communication information to which the information verification object belongs in the verification rules file.

[0172] S530. Based on the scenario data to be verified and the communication information to be verified, execute the verification rule file to obtain the parameter verification results.

[0173] In an optional embodiment, the parameter verification result is obtained by executing a verification rule file based on the scene data to be verified and the communication information to be verified, including: parsing the verification rule file to obtain rule verification instances and adding the rule verification instances to a verification instance pool; wherein, the rule verification instance includes information verification objects, scene verification rules, and parameter verification rules; obtaining a target verification instance that matches the communication information to be verified from the verification instance pool; and performing verification operations on the scene data to be verified and the communication information to be verified through the target verification instance to obtain the parameter verification result.

[0174] In an optional embodiment, obtaining a target verification instance that matches the communication information to be verified from the verification instance pool includes: for each rule verification instance in the verification instance pool, if the information verification object in the rule verification instance is contained in the communication information to be verified, then the rule verification instance is used as the target verification instance that matches the communication information to be verified.

[0175] In another optional embodiment, obtaining a target verification instance matching the communication information to be verified from the verification instance pool includes: obtaining the object to be verified in the communication information to be verified; for each rule verification instance in the verification instance pool, when the information type of the communication information to be verified is a network request, if the information verification object in the rule verification instance is the same as the object to be verified, then the rule verification instance is used as the target verification instance matching the communication information to be verified; when the information type of the communication information to be verified is a routing mode, if the information verification object in the rule verification instance is contained in the object to be verified, then the rule verification instance is used as the target verification instance matching the communication information to be verified.

[0176] In one optional embodiment, a parameter verification result is obtained by performing a verification operation on the scene data to be verified and the communication information to be verified through the target verification instance, including: performing scene verification on the scene data to be verified through the scene verification rules in the target verification instance to obtain a scene verification result; and if the scene verification result is a successful verification, performing parameter verification on the parameter values ​​in the communication information to be verified that correspond to the rule verification parameters through the parameter verification rules in the target verification instance to obtain a parameter verification result.

[0177] Specifically, it checks whether the scene data to be verified contains the standard scene parameter values ​​in the scene verification rules. If it does, the scene verification result is set to verification passed; otherwise, the scene verification result is set to verification failed. It also checks whether the parameter values ​​in the communication information to be verified, corresponding to the rule verification parameters, satisfy the parameter verification rules. If they satisfy the rules, the verification result flag in the parameter verification result is set to verification successful; otherwise, the verification result flag in the parameter verification result is set to verification failed.

[0178] Based on the above embodiments, the method may optionally further include: receiving verification communication information sent by the business platform; obtaining a verification instance matching the verification communication information from the verification instance pool; performing parameter verification on the parameter values ​​corresponding to the rule verification parameters in the verification communication information according to the parameter verification rules of the verification instance to obtain parameter verification results; and sending the parameter verification results to the business platform so that the business platform displays the parameter verification results on the rule verification page.

[0179] Specifically, the matching method of the verification instance is the same as or similar to the matching method of the target verification instance.

[0180] In this embodiment, during the execution of the rule verification instance, if the scene data is empty or no scene verification rule corresponding to the rule association identifier of the parameter verification rule is found, the scene verification result is set to pass.

[0181] The advantage of this setup is that it allows the business platform to implement the verification function of the verification rule file, further ensuring the accuracy of the verification rule file.

[0182] For example, the parameter verification result includes, but is not limited to, timestamp, communication information to be verified, information type of communication information to be verified, rule verification scenario, verification result identifier, and verification details text, etc., wherein the verification result identifier is an identifier used to indicate whether the verification was successful or not.

[0183] Figure 8 This is a schematic diagram illustrating the principle architecture of a specific instance of a rule execution engine provided in one embodiment of the present invention. Specifically, the rule manager obtains the verification rule file received through the JS bridging mechanism, parses the verification rule file to obtain rule verification instances, and records the rule verification instances in the verification instance pool. In the parameter verification process, the rule manager obtains the target verification instance by matching the communication information to be verified with the rule verification instances in the verification instance pool. In the execution process of the target verification instance, the scene verification rules in the target verification instance are used to perform scene verification on the scene data to be verified to obtain the scene verification result, and the scene verification result is fed back to the verification instance pool. If the scene verification result is a pass, the verification instance pool calls the parameter verification rules implemented based on parameter operators in the target verification instance to perform parameter verification on the parameter values ​​in the communication information to be verified that correspond to the rule verification parameters to obtain the parameter verification result, and the verification instance pool feeds back the parameter verification result to the rule manager.

[0184] For example, the validation content of parameter validation rules includes parameter type validation, parameter range validation, parameter format validation, and parameter existence validation. For example, the parameter operators corresponding to parameter type validation include, but are not limited to, int, string, boolean, array, or object; the parameter operators corresponding to parameter range validation include, but are not limited to, =, ! =, >, <, in, contain, or containAny; the parameter operators corresponding to parameter format validation include, but are not limited to, regex; and the parameter operators corresponding to parameter existence validation include, but are not limited to, notNull and notEmpty.

[0185] The technical solution of this embodiment obtains the verification rule file published by the business platform, receives the scenario data and communication information to be verified sent by the client, and executes the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified. The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The graphical interface rule entry combined with the rule template reduces the ability requirements of developers, solves the problem of low efficiency in publishing verification rule files, and improves the accuracy and flexibility of verification rule files.

[0186] The following are embodiments of the parameter verification device applied to a business platform provided by the present invention. This device and the parameter verification method applied to a business platform provided in the above embodiments belong to the same inventive concept. For details not described in detail in the embodiments of the parameter verification device, please refer to the content of the parameter verification method applied to a business platform in the above embodiments.

[0187] Figure 9 This is a schematic diagram of a parameter verification device applied to a business platform, provided as an embodiment of the present invention. Figure 9 As shown, the device includes: a rule configuration page display module 610, a verification rule file generation module 620, and a verification rule file publishing module 630.

[0188] Among them, the rule configuration page display module 610 is used to display the rule configuration page;

[0189] The verification rule file generation module 620 is used to obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file according to the rule configuration data and the preset rule template; wherein, the rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules;

[0190] The verification rule file publishing module 630 is used to publish the verification rule file so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified sent by the client.

[0191] The technical solution in this embodiment reduces the skill requirements for developers by combining rule input through a graphical interface with rule templates, solves the problem of low efficiency in publishing verification rule files, and improves the accuracy and flexibility of verification rule files.

[0192] In an optional embodiment, the device further includes:

[0193] The rule verification page display module generates a verification rule file based on the rule configuration data and preset rule template, and then displays the rule verification page.

[0194] The verification communication information entered in the rule verification page is sent to the rule execution engine, so that the rule execution engine executes the verification rule file and returns the parameter verification result according to the verification communication information;

[0195] The parameter verification results are displayed on the rule verification page.

[0196] In one optional embodiment, the rule configuration page display module 610 is specifically used for:

[0197] The business platform page is displayed; wherein, the business platform page maintains at least one business space;

[0198] In response to a display operation for the business space, the business management page corresponding to the business space is displayed;

[0199] In response to the rule configuration operation on the business management page, the rule configuration page of the business space is displayed.

[0200] The parameter verification device for business platforms provided in the embodiments of the present invention can execute the parameter verification method for business platforms provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0201] The following are embodiments of a parameter verification device applied to a client provided by the present invention. This device and the parameter verification method applied to a client provided in the above embodiments belong to the same inventive concept. For details not described in detail in the embodiments of the parameter verification device, please refer to the content of the parameter verification method applied to a client in the above embodiments.

[0202] Figure 10 This is a schematic diagram of a parameter verification device applied to a client, provided as an embodiment of the present invention. Figure 10 As shown, the device includes: a verification rule file acquisition module 710, a scene data determination module 720, a communication information determination module 730, and a communication information sending module 740.

[0203] Among them, the verification rule file acquisition module 710 is used to acquire the verification rule file published by the business platform;

[0204] The scene data determination module 720 is used to determine the scene data to be verified according to the scene verification rules in the verification rule file;

[0205] The communication information to be verified module 730 is used to determine the communication information to be verified based on the verification object list; wherein the verification object list contains at least one information verification object;

[0206] The communication information sending module 740 is used to send the scenario data to be verified and the communication information to be verified to the rule execution engine, so that the rule execution engine can execute the verification rule file according to the scenario data to be verified and the communication information to be verified to obtain the parameter verification result;

[0207] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0208] The technical solution in this embodiment reduces the skill requirements for developers by combining rule input through a graphical interface with rule templates, solves the problem of low efficiency in publishing verification rule files, and improves the accuracy and flexibility of verification rule files.

[0209] In an optional embodiment, the communication information to be verified determination module 730 is specifically used for:

[0210] Retrieve the list of validation objects corresponding to the information type;

[0211] For each type of network communication information, if the network communication information contains information verification objects in the verification object list, then the network communication information is used as the communication information to be verified.

[0212] The information type is either a network request or a routing pattern.

[0213] In an optional embodiment, the device further includes:

[0214] The parameter verification result reporting module is used to receive the parameter verification results sent by the rule execution engine;

[0215] If the parameter verification result indicates a verification failure, the parameter verification result is reported to the business platform according to the client's test attributes, so that the business platform can add the parameter verification result to the monitoring dashboard.

[0216] In one optional embodiment, the parameter verification result reporting module is specifically used for:

[0217] When the client's test attribute is offline testing, an alarm pop-up is displayed based on the parameter verification result, and in response to the reporting operation in the alarm pop-up, the parameter verification result is reported to the business platform.

[0218] If the client's test attribute is online deployment, the parameter verification result will be reported to the business platform as data from the event tracking point.

[0219] The parameter verification device for clients provided in this embodiment of the invention can execute the parameter verification method for clients provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0220] The following are embodiments of the parameter verification device for a rule execution engine provided by the present invention. This device and the parameter verification method for a rule execution engine provided in the above embodiments belong to the same inventive concept. For details not described in detail in the embodiments of the parameter verification device, please refer to the content of the parameter verification method for a rule execution engine in the above embodiments.

[0221] Figure 11 This is a schematic diagram of a parameter verification device applied to a rule execution engine, provided as an embodiment of the present invention. Figure 11 As shown, the device includes: a verification rule file acquisition module 810, a communication information receiving module 820 to be verified, and a parameter verification result determination module 830.

[0222] Among them, the verification rule file acquisition module 810 is used to acquire the verification rule file published by the business platform;

[0223] The communication information receiving module 820 is used to receive the scenario data to be verified and the communication information to be verified sent by the client.

[0224] The parameter verification result determination module 830 is used to execute the verification rule file to obtain the parameter verification result based on the scene data to be verified and the communication information to be verified.

[0225] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0226] The technical solution in this embodiment reduces the skill requirements for developers by combining rule input through a graphical interface with rule templates, solves the problem of low efficiency in publishing verification rule files, and improves the accuracy and flexibility of verification rule files.

[0227] In an optional embodiment, the parameter verification result determination module 830 includes:

[0228] The rule verification instance determination unit is used to parse the verification rule file to obtain rule verification instances and add the rule verification instances to the verification instance pool; wherein, the rule verification instance includes information verification objects, the scene verification rules, and parameter verification rules;

[0229] The target verification instance matching unit is used to obtain a target verification instance that matches the communication information to be verified from the verification instance pool;

[0230] The parameter verification result determination unit is used to perform verification operations on the scene data to be verified and the communication information to be verified through the target verification instance to obtain the parameter verification result.

[0231] In an optional embodiment, the parameter verification result determination unit is specifically used for:

[0232] The scene verification result is obtained by performing scene verification on the scene data to be verified using the scene verification rules in the target verification instance.

[0233] If the scenario verification result is successful, the parameter verification result is obtained by verifying the parameter values ​​corresponding to the rule verification parameters in the communication information to be verified according to the parameter verification rules in the target verification instance.

[0234] In an optional embodiment, the device further includes:

[0235] The communication information verification module is used to receive verification communication information sent by the service platform;

[0236] Obtain a verification instance that matches the verification communication information from the verification instance pool;

[0237] The parameter verification result is obtained by verifying the parameter values ​​corresponding to the rule verification parameters in the verification communication information using the parameter verification rules of the verification instance.

[0238] The parameter verification result is sent to the business platform so that the business platform can display the parameter verification result on the rule verification page.

[0239] The parameter verification device for rule execution engines provided in the embodiments of the present invention can execute the parameter verification method for rule execution engines provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0240] Figure 12This is a schematic diagram of a parameter verification system provided in one embodiment of the present invention. The parameter verification system in this embodiment can provide services for the parameter verification method in the above embodiments.

[0241] like Figure 12 As shown, the parameter verification system 900 includes a business platform 910, a client 920 communicating with the business platform 910, and a rule execution engine 930 communicating with both the business platform 910 and the client 920. The business platform 910 displays a rule configuration page, acquires the rule configuration data entered on the rule configuration page, generates a verification rule file based on the rule configuration data and a preset rule template, and publishes the verification rule file. The client 920 determines the scenario data to be verified based on the scenario verification rules in the verification rule file, determines the communication information to be verified based on the verification object list, and sends the scenario data and communication information to be verified to the rule execution engine 930. The rule execution engine 930 executes the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0242] Based on the above embodiments, optionally, the parameter verification system 900 also includes a content distribution network for implementing communication connections between the business platform 910 and the client 920.

[0243] Figure 13 This is a system flowchart illustrating a specific example of a parameter verification system provided in an embodiment of the present invention. Specifically, in the rule entry and maintenance phase, the business party creates a business space in the business platform 910 and enters rule configuration data in the rule configuration page corresponding to the business space. After generating a verification rule file based on the rule configuration data, in response to the detection of a rule verification operation, the verification rule file is verified, and the verified verification rule file is published to the content delivery network, while simultaneously recording the rule version of the published verification rule file.

[0244] During the parameter verification phase, the client 920 sends the scenario data to be verified, the communication information to be verified, and the verification rule file pulled from the content delivery network to the rule execution engine 930. The rule execution engine 930 parses the received verification rule file and obtains the target rule instance that matches the communication information to be verified from the rule instance pool. Through the target rule instance, it performs verification operations on the scenario data to be verified and the communication information to be verified to obtain the parameter verification result, and sends the parameter verification result to the client 920.

[0245] During the issue consumption phase, if the parameter validation result indicates validation failure, the parameter validation result is reported to the offline alarm response area in the business platform 910 via an alarm pop-up if the test attribute of client 920 is offline testing, or to the online alarm response area in the business platform 910 via event tracking if the test attribute of client 920 is online deployment. The business platform 910 collects the parameter validation results from both the offline and online alarm response areas and analyzes the results to determine the reason for the validation failure. If the failure is due to an error in the validation rule file, the validation rule file is modified through the rule configuration page. If the failure is due to an error in the network communication information, the logic for generating the network communication information is repaired. Simultaneously, the issue processing status during the above process is updated to the issue dashboard.

[0246] The following is for reference. Figure 14 The diagram illustrates a structural schematic of an electronic device 1000 suitable for implementing embodiments of the present invention. The electronic device 1000 in these embodiments may be a terminal device equipped with the service platform, client, or rule execution engine of the parameter verification system 900 described above. The terminal device may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 14 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.

[0247] like Figure 14 As shown, the electronic device 1000 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1006 into a random access memory (RAM) 1003. The RAM 1003 also stores various programs and data required for the operation of the electronic device 1000. The processing unit 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0248] Typically, the following devices can be connected to the I / O interface 1005: input devices 1006 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 1007 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1006 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows electronic device 1000 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 14 An electronic device 1000 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0249] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 1009, or installed from a storage device 1006, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, it performs the functions defined in the methods of the embodiments of the present invention.

[0250] It should be noted that the computer-readable medium described above in this invention can be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0251] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol, such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0252] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0253] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: acquire at least two Internet Protocol (IP) addresses; send a node evaluation request including the at least two IP addresses to a node evaluation device, wherein the node evaluation device selects an IP address from the at least two IP addresses and returns it; and receive the IP address returned by the node evaluation device; wherein the acquired IP address indicates an edge node in a content delivery network.

[0254] Alternatively, the aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: receive a node evaluation request including at least two Internet Protocol (IP) addresses; select an IP address from the at least two IP addresses; and return the selected IP address; wherein the received IP address indicates an edge node in the content delivery network.

[0255] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0256] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0257] The units described in the embodiments of the present invention can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, the first acquisition unit can also be described as "a unit that acquires at least two Internet Protocol addresses".

[0258] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0259] In the context of this invention, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0260] According to one or more embodiments of the present invention, Example 1 provides a parameter verification method applied to a business platform, including:

[0261] Display the rules configuration page;

[0262] Obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file based on the rule configuration data and the preset rule template; wherein, the rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules;

[0263] The verification rule file is published so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified sent by the client.

[0264] According to one or more embodiments of the present invention, Example 2 is based on the method described in Example 1.

[0265] After generating a verification rule file based on the rule configuration data and preset rule template, the method further includes:

[0266] Display the rule verification page;

[0267] The verification communication information entered in the rule verification page is sent to the rule execution engine, so that the rule execution engine executes the verification rule file and returns the parameter verification result according to the verification communication information;

[0268] The parameter verification results are displayed on the rule verification page.

[0269] According to one or more embodiments of the present invention, Example 3, based on the method described in Example 1, includes a display rule configuration page comprising:

[0270] The business platform page is displayed; wherein, the business platform page maintains at least one business space;

[0271] In response to a display operation for the business space, the business management page corresponding to the business space is displayed;

[0272] In response to the rule configuration operation on the business management page, the rule configuration page of the business space is displayed.

[0273] According to one or more embodiments of the present invention, Example 4 provides a parameter validation method applied to a client, including:

[0274] Obtain the verification rule file published by the business platform;

[0275] The scene data to be verified is determined according to the scene verification rules in the verification rule file;

[0276] Based on the list of verification objects, the communication information to be verified is determined; wherein, the list of verification objects contains at least one information verification object;

[0277] The scenario data to be verified and the communication information to be verified are sent to the rule execution engine, so that the rule execution engine can execute the verification rule file according to the scenario data to be verified and the communication information to be verified to obtain the parameter verification result;

[0278] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0279] According to one or more embodiments of the present invention, Example 5 describes the method described in Example 4, wherein determining the communication information to be verified based on the verification object list includes:

[0280] Retrieve the list of validation objects corresponding to the information type;

[0281] For each type of network communication information, if the network communication information contains information verification objects in the verification object list, then the network communication information is used as the communication information to be verified.

[0282] The information type is either a network request or a routing pattern.

[0283] According to one or more embodiments of the present invention, Example 6 describes the method according to Example 4, the method further comprising:

[0284] Receive the parameter verification result sent by the rule execution engine;

[0285] If the parameter verification result indicates a verification failure, the parameter verification result is reported to the business platform according to the client's test attributes, so that the business platform adds the parameter verification result to the monitoring dashboard.

[0286] According to one or more embodiments of the present invention, Example 7, based on the method described in Example 6, includes reporting the parameter verification result to the business platform according to the test attributes of the client, comprising:

[0287] When the client's test attribute is offline testing, an alarm pop-up is displayed based on the parameter verification result, and in response to the reporting operation in the alarm pop-up, the parameter verification result is reported to the business platform.

[0288] If the client's test attribute is online deployment, the parameter verification result will be reported to the business platform as data from the event tracking point.

[0289] According to one or more embodiments of the present invention, Example 8 provides a parameter validation method applied to a rule execution engine, including:

[0290] Obtain the verification rule file published by the business platform;

[0291] Receive the scenario data and communication information to be verified sent by the client;

[0292] Based on the scenario data to be verified and the communication information to be verified, the verification rule file is executed to obtain the parameter verification result;

[0293] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0294] According to one or more embodiments of the present invention, Example 9, based on the method described in Example 8, includes the step of executing the verification rule file to obtain parameter verification results based on the scene data to be verified and the communication information to be verified, comprising:

[0295] The verification rule file is parsed to obtain rule verification instances, and the rule verification instances are added to the verification instance pool; wherein, the rule verification instance includes information verification objects, the scene verification rules, and parameter verification rules;

[0296] Obtain a target verification instance that matches the communication information to be verified from the verification instance pool;

[0297] The parameter verification result is obtained by performing verification operations on the scene data and communication information to be verified using the target verification instance.

[0298] According to one or more embodiments of the present invention, Example 10, based on the method described in Example 9, wherein performing a verification operation on the scene data to be verified and the communication information to be verified through the target verification instance to obtain a parameter verification result includes:

[0299] The scene verification result is obtained by performing scene verification on the scene data to be verified using the scene verification rules in the target verification instance.

[0300] If the scenario verification result is successful, the parameter verification result is obtained by verifying the parameter values ​​corresponding to the rule verification parameters in the communication information to be verified according to the parameter verification rules in the target verification instance.

[0301] According to one or more embodiments of the present invention, Example 11 describes the method according to Example 9, the method further comprising:

[0302] Receive verification communication information sent by the service platform;

[0303] Obtain a verification instance that matches the verification communication information from the verification instance pool;

[0304] The parameter verification result is obtained by verifying the parameter values ​​corresponding to the rule verification parameters in the verification communication information using the parameter verification rules of the verification instance.

[0305] The parameter verification result is sent to the business platform so that the business platform can display the parameter verification result on the rule verification page.

[0306] According to one or more embodiments of the present invention, Example 12 provides a parameter verification device applied to a business platform, comprising:

[0307] The rule configuration page display module is used to display the rule configuration page;

[0308] The verification rule file generation module is used to obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file according to the rule configuration data and the preset rule template; wherein, the rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules;

[0309] The verification rule file publishing module is used to publish the verification rule file so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified sent by the client.

[0310] According to one or more embodiments of the present invention, Example 13 provides a parameter verification device applied to a client, comprising:

[0311] The verification rule file acquisition module is used to acquire the verification rule files published by the business platform;

[0312] The module for determining the scene data to be verified is used to determine the scene data to be verified based on the scene verification rules in the verification rule file.

[0313] The communication information to be verified module is used to determine the communication information to be verified based on the verification object list; wherein the verification object list contains at least one information verification object;

[0314] The communication information sending module is used to send the scenario data to be verified and the communication information to be verified to the rule execution engine, so that the rule execution engine can execute the verification rule file according to the scenario data to be verified and the communication information to be verified to obtain the parameter verification result;

[0315] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0316] According to one or more embodiments of the present invention, Example 14 provides a parameter validation device applied to a rule execution engine, comprising:

[0317] The verification rule file acquisition module is used to acquire the verification rule files published by the business platform;

[0318] The communication information receiving module to be verified is used to receive the scenario data and communication information to be verified sent by the client.

[0319] The parameter verification result determination module is used to execute the verification rule file to obtain the parameter verification result based on the scenario data to be verified and the communication information to be verified.

[0320] The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0321] According to one or more embodiments of the present invention, Example 15 provides a parameter verification system, including: a business platform, a client communicatively connected to the business platform, and a rule execution engine communicatively connected to the business platform and the client respectively;

[0322] The business platform is used to display a rule configuration page, obtain the rule configuration data entered in the rule configuration page, generate a verification rule file based on the rule configuration data and a preset rule template, and publish the verification rule file.

[0323] The client is configured to determine the scene data to be verified according to the scene verification rules in the verification rule file, determine the communication information to be verified according to the verification object list, and send the scene data to be verified and the communication information to be verified to the rule execution engine.

[0324] The rule execution engine is used to execute the verification rule file to obtain parameter verification results based on the scenario data to be verified and the communication information to be verified.

[0325] The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

[0326] According to one or more embodiments of the present invention, Example 16 provides a computer-readable storage medium storing computer instructions for causing a processor to execute and implement the parameter verification method described in any one of Examples 1-3, 4-7 or 8-11.

[0327] According to one or more embodiments of the present invention, Example 17 provides a computer program product including a computer program that, when executed by a processor, implements the parameter verification method according to any one of Examples 1-3, 4-7 or 8-11.

[0328] The above description is merely a preferred embodiment of the present invention and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.

[0329] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the invention. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0330] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A method of parameter verification, characterized by, Applied to business platforms, including: Display the rules configuration page; Obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file based on the rule configuration data and the preset rule template; wherein, the rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules; The verification rule file is published so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified sent by the client.

2. The method of claim 1, wherein, After generating a verification rule file based on the rule configuration data and preset rule template, the method further includes: Display the rule verification page; The verification communication information entered in the rule verification page is sent to the rule execution engine, so that the rule execution engine executes the verification rule file and returns the parameter verification result according to the verification communication information; The parameter verification results are displayed on the rule verification page.

3. The method according to claim 1, characterized in that, The display rules configuration page includes: The business platform page is displayed; wherein, the business platform page maintains at least one business space; In response to a display operation for the business space, the business management page corresponding to the business space is displayed; In response to the rule configuration operation on the business management page, the rule configuration page of the business space is displayed.

4. A parameter verification method, characterized in that, Applied to the client side, including: Obtain the verification rule file published by the business platform; The scene data to be verified is determined according to the scene verification rules in the verification rule file; Based on the list of verification objects, the communication information to be verified is determined; wherein, the list of verification objects contains at least one information verification object; The scenario data to be verified and the communication information to be verified are sent to the rule execution engine, so that the rule execution engine can execute the verification rule file according to the scenario data to be verified and the communication information to be verified to obtain the parameter verification result; The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

5. The method according to claim 4, characterized in that, The step of determining the communication information to be verified based on the list of verification objects includes: Retrieve the list of validation objects corresponding to the information type; For each type of network communication information, if the network communication information contains information verification objects in the verification object list, then the network communication information is used as the communication information to be verified. The information type is either a network request or a routing pattern.

6. The method according to claim 4, characterized in that, The method further includes: Receive the parameter verification result sent by the rule execution engine; If the parameter verification result indicates a verification failure, the parameter verification result is reported to the business platform according to the client's test attributes, so that the business platform adds the parameter verification result to the monitoring dashboard.

7. The method according to claim 6, characterized in that, The step of reporting the parameter verification result to the business platform based on the client's test attributes includes: When the client's test attribute is offline testing, an alarm pop-up is displayed based on the parameter verification result, and in response to the reporting operation in the alarm pop-up, the parameter verification result is reported to the business platform. If the client's test attribute is online deployment, the parameter verification result will be reported to the business platform as data from the event tracking point.

8. A parameter verification method, characterized in that, Applied to rule enforcement engines, including: Obtain the verification rule file published by the business platform; Receive the scenario data and communication information to be verified sent by the client; Based on the scenario data to be verified and the communication information to be verified, the verification rule file is executed to obtain the parameter verification result; The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

9. The method according to claim 8, characterized in that, The step of obtaining parameter verification results by executing the verification rule file based on the scenario data to be verified and the communication information to be verified includes: The verification rule file is parsed to obtain rule verification instances, and the rule verification instances are added to the verification instance pool; wherein, the rule verification instance includes information verification objects, the scene verification rules, and parameter verification rules; Obtain a target verification instance that matches the communication information to be verified from the verification instance pool; The parameter verification result is obtained by performing verification operations on the scene data and communication information to be verified using the target verification instance.

10. The method according to claim 9, characterized in that, The step of performing a verification operation on the scene data to be verified and the communication information to be verified through the target verification instance to obtain the parameter verification result includes: The scene verification result is obtained by performing scene verification on the scene data to be verified using the scene verification rules in the target verification instance. If the scenario verification result is successful, the parameter verification result is obtained by verifying the parameter values ​​corresponding to the rule verification parameters in the communication information to be verified according to the parameter verification rules in the target verification instance.

11. The method according to claim 9, characterized in that, The method further includes: Receive verification communication information sent by the service platform; Obtain a verification instance that matches the verification communication information from the verification instance pool; The parameter verification result is obtained by verifying the parameter values ​​corresponding to the rule verification parameters in the verification communication information using the parameter verification rules of the verification instance. The parameter verification result is sent to the business platform so that the business platform can display the parameter verification result on the rule verification page.

12. A parameter verification device, characterized in that, Applied to business platforms, including: The rule configuration page display module is used to display the rule configuration page; The verification rule file generation module is used to obtain the rule configuration data entered in the rule configuration page, and generate a verification rule file according to the rule configuration data and the preset rule template; wherein, the rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules; The verification rule file publishing module is used to publish the verification rule file so that the rule execution engine can execute the verification rule file to obtain the parameter verification result based on the scenario data and communication information to be verified sent by the client.

13. A parameter verification device, characterized in that, Applied to the client side, including: The verification rule file acquisition module is used to acquire the verification rule files published by the business platform; The module for determining the scene data to be verified is used to determine the scene data to be verified based on the scene verification rules in the verification rule file. The communication information to be verified module is used to determine the communication information to be verified based on the verification object list; wherein the verification object list contains at least one information verification object; The communication information sending module is used to send the scenario data to be verified and the communication information to be verified to the rule execution engine, so that the rule execution engine can execute the verification rule file according to the scenario data to be verified and the communication information to be verified to obtain the parameter verification result; The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

14. A parameter verification device, characterized in that, Applied to rule enforcement engines, including: The verification rule file acquisition module is used to acquire the verification rule files published by the business platform; The communication information receiving module to be verified is used to receive the scenario data and communication information to be verified sent by the client. The parameter verification result determination module is used to execute the verification rule file to obtain the parameter verification result based on the scenario data to be verified and the communication information to be verified. The verification rule file is generated by the business platform based on the preset rule template and the rule configuration data entered in the rule configuration page. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

15. A parameter verification system, characterized in that, include: A business platform, a client communicating with the business platform, and a rule execution engine communicating with both the business platform and the client; The business platform is used to display a rule configuration page, obtain the rule configuration data entered in the rule configuration page, generate a verification rule file based on the rule configuration data and a preset rule template, and publish the verification rule file. The client is configured to determine the scene data to be verified according to the scene verification rules in the verification rule file, determine the communication information to be verified according to the verification object list, and send the scene data to be verified and the communication information to be verified to the rule execution engine. The rule execution engine is used to execute the verification rule file to obtain parameter verification results based on the scenario data to be verified and the communication information to be verified. The rule configuration data includes scenario verification rules, information verification objects corresponding to network communication information, and parameter verification rules.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the parameter verification method according to any one of claims 1-3, 4-7, or 8-11.

17. A computer program product comprising a computer program that, when executed by a processor, implements the parameter verification method according to any one of claims 1-3, 4-7, or 8-11.

Images