Front-end and back-end product rule sharing configuration method and device, equipment and storage medium
By using the parsing engine to share and verify rules in front-end and back-end systems in the financial product configuration function, the problem of repeated definition of rules and consistency risks is solved, the scalability and flexibility of rules are improved, and complex rule configuration is supported.
Patent Information
- Application Number
- CN202411023526.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-29
- Publication Date
- 2024-12-06
AI Technical Summary
The existing configuration functions require the front and back-end systems to develop product rules, resulting in repeated definitions of rules and consistency risks. The rules of complex financial products are low in scalability, making it difficult to support complex product and rule configuration.
Through the configuration side, product and sales rules are configured, structured data is generated, and parsing engines are used to share and verify between front and back-end systems to reduce the risk of repeated definitions of rules and consistency, and improve the scalability of rules.
It realizes rule sharing and verification between front-end systems, reduces the risks of repeated definition and consistency of rules, improves the flexibility and scalability of rules, and supports complex rule configuration.
Smart Images

Figure CN119088351A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer application technology, and in particular to a front-end and back-end product rule sharing configuration method, device and storage medium. Background Art
[0002] In today's society, with the rapid development of the economy and the continuous improvement of people's living standards, people's demand for financial products is growing. Whether it is daily savings and investment, long-term retirement planning, or corporate financing needs, financial products play an indispensable role. Therefore, the promotion and marketing of financial products has become particularly important, which is directly related to the business expansion of financial institutions and the competition for market share.
[0003] In order to respond to this market demand in a timely manner, the configuration function of financial products came into being. This technology realizes the rapid creation, efficient management and convenient online and offline operations of financial products through flexible configuration on the management side. Specifically, financial institutions can use the configuration function to customize the development of new financial products according to market demand and customer preferences to meet diverse investment needs. At the same time, through a unified management platform, financial institutions can grasp the operating status and sales of products in real time and make timely strategy adjustments and optimizations.
[0004] The emergence of the configuration function has greatly improved the efficiency of financial product launches. The traditional financial product development and launch process is often cumbersome and complicated, involving multiple departments and multiple links, and is time-consuming and labor-intensive. The configuration function simplifies this process, greatly shortening the time from product idea to launch, and winning valuable market opportunities for financial institutions. In addition, the configuration function also enhances the flexibility and adaptability of financial products. As the market environment changes and customer needs shift, financial institutions can adjust product parameters and strategies at any time to adapt to new market conditions. This flexibility enables financial products to better meet customers' personalized needs and improve customer satisfaction and loyalty.
[0005] However, the existing configuration function requires the front-end and back-end systems to develop and process product rules respectively, resulting in repeated definitions of product rules in the front-end and back-end systems, which not only increases the development workload but also leads to consistency risks between the front-end and back-end. In addition, after the configuration of some complex financial products and product rules, the front-end and back-end systems need to develop corresponding codes for the products and process the product sales logic, resulting in low scalability of product rules and difficulty in supporting complex products and product rules. Therefore, how to provide an effective technical means to improve the existing configuration function is an urgent problem to be solved. Summary of the invention
[0006] To this end, the present invention provides a front-end and back-end product rule sharing configuration method, device and storage medium to solve at least one of the above-mentioned technical problems.
[0007] To achieve the above objectives, in a first aspect, the present invention provides a front-end and back-end product rule sharing configuration method, comprising:
[0008] Perform product configuration and product sales rule configuration through the configuration terminal, and generate structured data from the product configuration and sales rule configuration for storage;
[0009] A first parsing engine is configured, and when a user purchases a product through a first port, a request for obtaining data corresponding to the product to be purchased is triggered; the first port obtains structured data of the product and the product sales rules, and the structured data is parsed through the first parsing engine;
[0010] When the user submits a purchase request through the first port, the second port obtains the structured data of the product and the product sales rules through the first parsing engine, and parses the structured data to generate a verification code;
[0011] Verifying the verification code generated by the analysis with the data submitted by the user, and the second port determining the verification result;
[0012] If the verification is consistent, the decision is correct, and the purchase request of the user is further processed;
[0013] If the check is inconsistent, it is determined to be an error and an error result is returned to the first port.
[0014] Furthermore, the configuration of the first resolution engine includes: configuring and providing a centralized first product resolution engine, the first port and the second port jointly use the first product resolution engine or the first port and the second port are subject to rule agreement, and a second product resolution engine matching the first port and a third product resolution engine matching the second port are separately configured according to the agreed rules.
[0015] Furthermore, in the structured data of the product and the product sales rules obtained by the first parsing engine at the second port, the structured data of the product sales rules includes: page display information, user operation information and verification rules when the user purchases and submits.
[0016] Furthermore, the page display information includes: the product name and product title, pictures and videos of the product, specifications of the product, user reviews of the product, price and discount information of the product, after-sales service of the product, and brand and manufacturer information of the product.
[0017] In a second aspect, the present invention further provides a front-end and back-end product rule sharing configuration device, the device comprising: a configuration unit, a first parsing unit, a second parsing unit, and a verification unit;
[0018] The configuration unit is used to configure the product and the product sales rule through the configuration terminal, and generate structured data from the product configuration and the sales rule configuration for storage;
[0019] The first parsing unit is used to configure the first parsing engine, and when the user purchases a product through the first port, a request for obtaining data corresponding to the product to be purchased is triggered; the first port obtains structured data of the product and the product sales rules, and performs structured data parsing through the first parsing engine;
[0020] The second parsing unit is configured to, when the user submits a purchase request through the first port, obtain the structured data of the product and the product sales rules through the first parsing engine, and parse the structured data to generate a verification code;
[0021] The verification unit is used to verify the verification code generated by the analysis with the data submitted by the user, and the second port determines the verification result;
[0022] If the verification is consistent, the decision is correct, and the purchase request of the user is further processed;
[0023] If the check is inconsistent, it is determined to be an error and an error result is returned to the first port.
[0024] Furthermore, the configuration of the first resolution engine includes: configuring and providing a centralized first product resolution engine, the first port and the second port jointly use the first product resolution engine or the first port and the second port are subject to rule agreement, and a second product resolution engine matching the first port and a third product resolution engine matching the second port are separately configured according to the agreed rules.
[0025] Furthermore, in the structured data of the product and the product sales rules obtained by the first parsing engine at the second port, the structured data of the product sales rules includes: page display information, user operation information and verification rules when the user purchases and submits.
[0026] Furthermore, the page display information includes: the product name and product title, pictures and videos of the product, specifications of the product, user reviews of the product, price and discount information of the product, after-sales service of the product, and brand and manufacturer information of the product.
[0027] In a third aspect, the present invention provides a computing device, comprising:
[0028] A memory for storing program instructions;
[0029] The processor is used to call the program instructions stored in the memory and execute the above-mentioned front-end and back-end product rule sharing configuration method according to the obtained program instructions.
[0030] In a fourth aspect, the present invention provides a computer-readable storage medium, including computer-readable instructions. When a computer reads and executes the computer-readable instructions, the above-mentioned front-end and back-end product rule sharing configuration method is implemented. The readable medium may be multiple, and the multiple readable media can operate independently of each other.
[0031] Compared with the existing technology, this solution configures products and product sales rules through the configuration end, generates structured data for storage; configures the first parsing engine, and when the user purchases a product through the first port, triggers a request to obtain the corresponding data of the product to be purchased; the first port obtains the structured data of the product and sales rules, and parses the structured data through the first parsing engine; the user submits a purchase request through the first port, and the second port obtains the structured data of the product and sales rules through the first parsing engine, parses the structured data and generates a verification code; the verification code is verified with the data submitted by the user, and if successful, the user's purchase request is processed, otherwise an error is returned to the first port. Reduce the risk of duplicate definition and consistency of rules in the front-end and back-end systems, and at the same time improve the flexibility of rule expansion. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0033] Figure 1 A flow chart of an embodiment of the front-end and back-end product rule sharing configuration method provided by the present invention;
[0034] Figure 2 A framework diagram of an embodiment of the front-end and back-end product rule sharing configuration method provided by the present invention;
[0035] Figure 3 A structural block diagram of an embodiment of the front-end and back-end product rule sharing configuration device provided by the present invention. DETAILED DESCRIPTION
[0036] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present application.
[0037] It will be understood by those skilled in the art that, unless otherwise stated, the singular forms "a", "an" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.
[0038] In order to make the objectives, technical solutions and advantages of the present application more clear, the specific implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0039] The core of the present invention is to provide a front-end and back-end product rule sharing configuration method. Figure 1 FIG. 1 is a flow chart of a method for configuring front-end and back-end product rule sharing provided in this embodiment. Figure 2 The figure shows a framework diagram of the front-end and back-end product rule sharing configuration method provided in this embodiment. In order to better understand the method, Figure 1 and Figure 2 The technical solution of this embodiment is described in detail:
[0040] Step S1: configure the product and the product sales rule through the configuration terminal, and generate structured data from the product configuration and the sales rule configuration for storage.
[0041] In one embodiment, business personnel configure products and product sales rules through a product configuration terminal, and generate structured data that is stored in a product configuration system server.
[0042] Step S2: configure the first parsing engine. When a user purchases a product through the first port, a request for obtaining data corresponding to the product to be purchased is triggered; the first port obtains structured data of the product and the product sales rules, and performs structured data parsing through the first parsing engine.
[0043] In a preferred embodiment, through agreement among all parties, the product configuration system may provide a centralized product parsing engine or the front-end and back-end may each use agreed rules to implement a product parsing engine suitable for their own system.
[0044] Step S3: When the user submits a purchase request through the first port, the second port obtains the structured data of the product and the product sales rules through the first parsing engine, and parses the structured data to generate a verification code.
[0045] In a preferred embodiment, a customer purchases a product through the front-end system, triggering a request to obtain product data. The front-end system obtains structured data of the product and product sales rules, and parses the structured data through the product parsing engine to generate partial page display information and verification rules for customer operations and customer purchase submissions.
[0046] Step S4: verifying the verification code generated by the analysis with the data submitted by the user, and the second port determining the verification result;
[0047] If the verification is consistent, the decision is correct, and the purchase request of the user is further processed;
[0048] If the check is inconsistent, it is determined to be an error and an error result is returned to the first port.
[0049] In a preferred embodiment, when a customer submits a purchase request through the front-end system, the back-end system obtains structured data of the product and product sales rules, and after parsing, it can generate a verification code to verify the data submitted by the customer. If the back-end system verification is successful, the customer's purchase request is processed, otherwise an error is returned to the front-end system.
[0050] In a preferred embodiment, the configuration of the first resolution engine includes: configuring and providing a centralized first product resolution engine, the first port and the second port jointly use the first product resolution engine or the first port and the second port are subject to rule agreement, and a second product resolution engine matching the first port and a third product resolution engine matching the second port are separately configured according to the agreed rules.
[0051] In a preferred embodiment, in the structured data of the product and the product sales rules obtained by the first parsing engine at the second port, the structured data of the product sales rules includes: page display information, user operation information and verification rules when the user submits the purchase.
[0052] In a preferred embodiment, the page display information includes: the product name and product title, pictures and videos of the product, specifications of the product, user reviews of the product, price and discount information of the product, after-sales service of the product, and brand and manufacturer information of the product.
[0053] In the solution of this embodiment, product configuration and product sales rule configuration are performed through the configuration end, and the product configuration and sales rule configuration are generated into structured data for storage; the first parsing engine is configured, and when the user purchases the product through the first port, a request for obtaining the corresponding data of the product to be purchased is triggered; the first port obtains the structured data of the product and sales rules, and the structured data is parsed through the first parsing engine; the user submits a purchase request through the first port, and the second port obtains the structured data of the product and sales rules through the first parsing engine, and the structured data is parsed to generate a verification code; the verification code is verified with the data submitted by the user, and if successful, the user's purchase request is processed, otherwise an error is returned to the first port. Reduce the risk of duplicate rule definition and consistency of the front-end and back-end systems, while improving the flexibility of rule expansion and supporting complex rule configuration.
[0054] In one embodiment, a front-end and back-end product rule sharing configuration device is provided. Figure 3 The figure shows a structural block diagram of a front-end and back-end product rule sharing configuration device provided by this embodiment, the device comprises: a configuration unit 10, a first parsing unit 20, a second parsing unit 30, and a verification unit 40;
[0055] Configuration unit 10: configured to configure the product and the product sales rule through the configuration terminal, and generate structured data from the product configuration and the sales rule configuration for storage.
[0056] In one embodiment, business personnel configure products and product sales rules through a product configuration terminal, and generate structured data that is stored in a product configuration system server.
[0057] The first parsing unit 20 is used to configure the first parsing engine. When a user purchases a product through the first port, a request for obtaining data corresponding to the product to be purchased is triggered; the first port obtains structured data of the product and the product sales rules, and performs structured data parsing through the first parsing engine.
[0058] In a preferred embodiment, through agreement among all parties, the product configuration system may provide a centralized product parsing engine or the front-end and back-end may each use agreed rules to implement a product parsing engine suitable for their own system.
[0059] The second parsing unit 30 is used for, when the user submits a purchase request through the first port, the second port obtains the structured data of the product and the product sales rules through the first parsing engine, and parses the structured data to generate a verification code.
[0060] In a preferred embodiment, a customer purchases a product through the front-end system, triggering a request to obtain product data. The front-end system obtains structured data of the product and product sales rules, and parses the structured data through the product parsing engine to generate partial page display information and verification rules for customer operations and customer purchase submissions.
[0061] Verification unit 40: used to verify the verification code generated by the analysis with the data submitted by the user, and the second port determines the verification result;
[0062] If the verification is consistent, the decision is correct, and the purchase request of the user is further processed;
[0063] If the check is inconsistent, it is determined to be an error and an error result is returned to the first port.
[0064] In a preferred embodiment, when a customer submits a purchase request through the front-end system, the back-end system obtains structured data of the product and product sales rules, and after parsing, it can generate a verification code to verify the data submitted by the customer. If the back-end system verification is successful, the customer's purchase request is processed, otherwise an error is returned to the front-end system.
[0065] In a preferred embodiment, the configuration of the first resolution engine includes: configuring and providing a centralized first product resolution engine, the first port and the second port jointly use the first product resolution engine or the first port and the second port are subject to rule agreement, and a second product resolution engine matching the first port and a third product resolution engine matching the second port are separately configured according to the agreed rules.
[0066] In a preferred embodiment, in the structured data of the product and the product sales rules obtained by the first parsing engine at the second port, the structured data of the product sales rules includes: page display information, user operation information and verification rules when the user submits the purchase.
[0067] In a preferred embodiment, the page display information includes: the product name and product title, pictures and videos of the product, specifications of the product, user reviews of the product, price and discount information of the product, after-sales service of the product, and brand and manufacturer information of the product.
[0068] In the solution of this embodiment, product configuration and product sales rule configuration are performed through the configuration end, and the product configuration and sales rule configuration are generated into structured data for storage; the first parsing engine is configured, and when the user purchases the product through the first port, a request for obtaining the corresponding data of the product to be purchased is triggered; the first port obtains the structured data of the product and sales rules, and the structured data is parsed through the first parsing engine; the user submits a purchase request through the first port, and the second port obtains the structured data of the product and sales rules through the first parsing engine, and the structured data is parsed to generate a verification code; the verification code is verified with the data submitted by the user, and if successful, the user's purchase request is processed, otherwise an error is returned to the first port. Reduce the risk of duplicate rule definition and consistency of the front-end and back-end systems, while improving the flexibility of rule expansion and supporting complex rule configuration.
[0069] The front-end and back-end product rule sharing configuration device of this embodiment is used to implement the aforementioned front-end and back-end product rule sharing configuration method. Therefore, the specific implementation method of the front-end and back-end product rule sharing configuration device can be seen from the specific implementation method part of the front-end and back-end product rule sharing configuration method in the previous text. For example, the configuration unit 10 is used to implement step S1 in the above-mentioned front-end and back-end product rule sharing configuration method, and the first parsing unit 20 is used to implement step S2 in the above-mentioned front-end and back-end product rule sharing configuration method, etc. Therefore, its specific implementation method can refer to the description of the corresponding various partial embodiments. The device provided by the present invention is attached to the method provided by the present invention, and its specific effects can refer to the above-mentioned method, which will not be repeated here.
[0070] In one embodiment, a computing device is provided, comprising:
[0071] A memory for storing program instructions;
[0072] A processor is used to implement the steps of the front-end and back-end product rule sharing configuration method as described in any of the above when executing the computer program. A front-end and back-end product rule sharing configuration method of the present invention has obvious advantages and beneficial effects compared with the prior art. The configuration end performs product configuration and product sales rule configuration, and generates structured data for storage by configuring the product configuration and sales rule configuration; configures the first parsing engine, and when the user purchases the product through the first port, triggers the acquisition request for the corresponding data of the product to be purchased; the first port obtains the structured data of the product and sales rules, and performs structured data parsing through the first parsing engine; the user submits the purchase request through the first port, and the second port obtains the structured data of the product and sales rules through the first parsing engine, and parses the structured data to generate a verification code; the verification code is verified with the data submitted by the user, and the user's purchase request is processed if successful, otherwise an error is returned to the first port. Reduce the risk of duplicate definition and consistency of rules of the front-end and back-end systems, while improving the flexibility of rule expansion and supporting complex rule configuration.
[0073] In one embodiment, a computer-readable storage medium is provided, including computer-readable instructions. When a computer reads and executes the computer-readable instructions, the steps of the front-end and back-end product rule sharing configuration method described above are implemented. The front-end and back-end product rule sharing configuration method of the present invention has obvious advantages and beneficial effects compared with the prior art. The configuration end performs product configuration and product sales rule configuration, and the product configuration and sales rule configuration generate structured data for storage; the first parsing engine is configured, and when the user purchases the product through the first port, the acquisition request corresponding to the product to be purchased is triggered; the first port obtains the structured data of the product and the sales rule, and the structured data is parsed through the first parsing engine; the user submits the purchase request through the first port, and the second port obtains the structured data of the product and the sales rule through the first parsing engine, and the structured data is parsed to generate a verification code; the verification code is verified with the data submitted by the user, and the user's purchase request is processed if successful, otherwise an error is returned to the first port. Reduce the risk of repeated definition and consistency of rules of the front-end and back-end systems, while improving the flexibility of rule expansion and supporting complex rule configuration.
[0074] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the specific device can be divided into different functional modules to complete all or part of the functions described above.
[0075] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0076] In several embodiments covered by the present application, it should be understood that the disclosed devices, equipment and methods can be implemented in other ways. For example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another device, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, or it can be an electrical, mechanical or other form of connection.
[0077] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiments of the present application.
[0078] In addition, each functional module in each embodiment of the present application can be implemented in the form of hardware or in the form of software functional modules. If these functional modules are implemented in the form of software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application is essentially or part of the prior art that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a computer program product, which includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program product is stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, a computer instruction can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. The available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)).
[0079] The above contents are merely examples and explanations of the structure of the present invention. The technicians in this technical field may make various modifications or additions to the specific embodiments described or replace them in a similar manner. As long as they do not deviate from the structure of the invention or exceed the scope defined by the claims, they should all fall within the protection scope of the present invention.
Claims
1. A front-end and back-end product rule sharing configuration method, characterized in that: include: Perform product configuration and product sales rule configuration through the configuration terminal, and generate structured data from the product configuration and sales rule configuration for storage; A first parsing engine is configured, and when a user purchases a product through a first port, a request for obtaining data corresponding to the product to be purchased is triggered; the first port obtains structured data of the product and the product sales rules, and the structured data is parsed through the first parsing engine; When the user submits a purchase request through the first port, the second port obtains the structured data of the product and the product sales rules through the first parsing engine, and parses the structured data to generate a verification code; Verifying the verification code generated by the analysis with the data submitted by the user, and the second port determining the verification result; If the verification is consistent, the decision is correct, and the purchase request of the user is further processed; If the check is inconsistent, it is determined to be an error and an error result is returned to the first port.
2. The front-end and back-end product rule sharing configuration method according to claim 1 is characterized in that: The configuring of the first resolution engine includes: configuring and providing a centralized first product resolution engine, the first port and the second port jointly use the first product resolution engine or agree on rules between the first port and the second port, and separately configuring a second product resolution engine matching the first port and a third product resolution engine matching the second port according to the agreed rules.
3. The front-end and back-end product rule sharing configuration method according to claim 1 is characterized in that: In the structured data of the product and the product sales rules obtained by the first parsing engine at the second port, the structured data of the product sales rules include: page display information, user operation information and verification rules when the user purchases and submits.
4. The front-end and back-end product rule sharing configuration method according to claim 3 is characterized in that: The page display information includes: the product name and product title, the product pictures and videos, the product specifications, the product user reviews, the product price and discount information, the product after-sales service, and the product brand and manufacturer information.
5. A front-end and back-end product rule sharing configuration device, characterized in that: include: A configuration unit, a first parsing unit, a second parsing unit, and a verification unit; The configuration unit is used to configure the product and the product sales rule through the configuration terminal, and generate structured data from the product configuration and the sales rule configuration for storage; The first parsing unit is used to configure the first parsing engine, and when the user purchases a product through the first port, a request for obtaining data corresponding to the product to be purchased is triggered; the first port obtains structured data of the product and the product sales rules, and performs structured data parsing through the first parsing engine; The second parsing unit is configured to, when the user submits a purchase request through the first port, obtain the structured data of the product and the product sales rules through the first parsing engine, and parse the structured data to generate a verification code; The verification unit is used to verify the verification code generated by the analysis with the data submitted by the user, and the second port determines the verification result; If the verification is consistent, the decision is correct, and the purchase request of the user is further processed; If the check is inconsistent, it is determined to be an error and an error result is returned to the first port.
6. The front-end and back-end product rule sharing configuration device according to claim 5, characterized in that: The configuring of the first resolution engine includes: configuring and providing a centralized first product resolution engine, the first port and the second port jointly use the first product resolution engine or agree on rules between the first port and the second port, and separately configuring a second product resolution engine matching the first port and a third product resolution engine matching the second port according to the agreed rules.
7. The front-end and back-end product rule sharing configuration device according to claim 5, characterized in that: In the structured data of the product and the product sales rules obtained by the first parsing engine at the second port, the structured data of the product sales rules include: page display information, user operation information and verification rules when the user purchases and submits.
8. The front-end and back-end product rule sharing configuration device according to claim 7, characterized in that: The page display information includes: the product name and product title, the product pictures and videos, the product specifications, the product user reviews, the product price and discount information, the product after-sales service, and the product brand and manufacturer information.
9. A computing device, characterized in that include: A memory for storing program instructions; A processor is used to call the program instructions stored in the memory, and execute the method according to any one of claims 1 to 4 according to the obtained program instructions.
10. A computer-readable storage medium, characterized in that: It includes computer-readable instructions. When a computer reads and executes the computer-readable instructions, it implements the method as claimed in any one of claims 1 to 4. There can be multiple readable media, and the multiple readable media can operate independently of each other.
