Data processing method, device, electronic device and storage medium
By obtaining business demand information and calling corresponding business fields from the predefined rule database, the method of stitching and integrating the generation of customer portraits has been solved, and the problem of long development time and high change cost in the existing technology has been achieved, and flexibility and speed are achieved customer profile configuration and efficient development and operation.
Patent Information
- Application Number
- CN202211130845.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-16
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2042-09-16
AI Technical Summary
In the prior art, the development process of customer portraits in the financial industry has a long time cycle, and due to the high coupling of business rules and back-end code logic, the development and operation and maintenance costs for customer portraits are relatively high.
By obtaining business requirements information, calling the corresponding business fields based on the predefined rule base, and splicing the business fields into business rules that meet business needs, integrating the corresponding code statements, generating rule codes, configuring query statement templates, and finally generating a customer portrait.
It realizes flexible and quick configuration of customer portraits according to business needs. When it is necessary to modify customer portraits, you only need to modify the business fields corresponding to the business rules without modifying the code statements, which improves business flexibility, development efficiency, and reduces fortunes. Maintenance cost.
Smart Images

Figure CN115438240B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of behavior analysis, and in particular to a data processing method, device, electronic device and storage medium. Background Art
[0002] Since the financial industry has a huge number of customers, it uses a series of customer portraits to analyze the needs of different customer groups, and then develops specific services and recommended businesses for different customer groups.
[0003] In the existing technology, customer portraits in the financial industry are mostly generated directly based on business experience or simple logical rules. That is, by analyzing the needs raised by business personnel, developers write code, combine business rules with back-end logic code, and then generate customer portraits and put them online.
[0004] However, the development process of the above-mentioned customer portrait takes a long time, and due to the high coupling between business rules and back-end code logic, the development and operation and maintenance costs are high for changes to customer portraits. Summary of the invention
[0005] The present application provides a data processing method, device, electronic device and storage medium, which can flexibly and quickly configure the required customer portrait according to business needs. When the customer portrait needs to be modified, only the business field corresponding to the business rule needs to be modified, and the code statement corresponding to each business field does not need to be modified, thereby enhancing business flexibility, improving development efficiency and reducing operation and maintenance costs.
[0006] In a first aspect, the present application provides a data processing method, the method comprising:
[0007] Obtaining business requirement information, and calling corresponding business fields from a predefined rule library based on the business requirement information; each business field corresponds to an executable code statement;
[0008] The business fields are spliced to obtain business rules that meet the business demand information, and the code statements corresponding to the business fields are integrated to obtain rule codes;
[0009] A query statement template is configured based on the rule code, and a customer profile is generated based on the query statement template and the business rules.
[0010] Optionally, calling a corresponding business field from a predefined rule library based on the business requirement information includes:
[0011] Based on the business demand information, a corresponding business scenario is called from a predefined rule library; each business scenario is configured with business fields required for executing the business;
[0012] Determine whether there is a business field corresponding to the business scenario in the predefined rule base;
[0013] If yes, calling the corresponding business field from the predefined rule base based on the business requirement information;
[0014] If not, a writing requirement is sent to the developer's terminal device, so that the developer writes code statements corresponding to the business fields required by the business scenario based on the writing requirement, and the code statements written by the developer and the corresponding business fields are stored in the predefined rule library.
[0015] Optionally, generating a customer profile based on the query statement template and the business rule includes:
[0016] Obtaining a rule number corresponding to the business rule, and generating a page interface based on the rule number; the page interface is used for business personnel to call the corresponding business rule in a visual interface;
[0017] A connection relationship is established between the query statement template and the page interface, and the business fields of the business rules are called to generate a customer portrait.
[0018] Optionally, the code statements corresponding to the business fields are integrated to obtain rule codes, including:
[0019] For each business field, calling a rule engine to match the business field with the code statement in the predefined rule base to obtain a matching result;
[0020] Based on the matching result, the code statements corresponding to the business fields are obtained, and the code statements are integrated to obtain rule codes.
[0021] Optionally, the method further includes:
[0022] Importing the query statement template corresponding to the customer portrait into the database, and visually displaying the customer portrait so that the business personnel can perform touch operations on the visual interface to query the customer's business transaction data;
[0023] Among them, the content displayed on the visualization interface includes: customer portrait name, query field and query conditions.
[0024] Optionally, the method further includes:
[0025] In response to the touch operation of the business personnel on the visual interface, determining the query field and query condition corresponding to the customer portrait;
[0026] The query field and the query condition are concatenated to generate a query statement, and a query is performed in the database based on the query statement to obtain the customer's business transaction data.
[0027] Optionally, the method further includes:
[0028] Obtaining a target behavior instruction input by a business person, wherein the target behavior instruction includes an add behavior instruction, a delete behavior instruction, and a modify behavior instruction; the target behavior instruction is used to change the number and type of business fields included in the business rules;
[0029] Calling a corresponding execution code based on the target behavior instruction, and modifying a business rule corresponding to the customer profile based on the execution code to generate a new customer profile;
[0030] The new customer portrait is displayed visually so that business personnel can query the customer's business transaction data based on the new customer portrait in a visual interface.
[0031] In a second aspect, the present application provides a data processing device, the device comprising:
[0032] An acquisition module is used to acquire business demand information and call corresponding business fields from a predefined rule library based on the business demand information; each business field corresponds to an executable code statement;
[0033] A splicing module is used to splice the business fields to obtain business rules that meet business demand information, and integrate code statements corresponding to the business fields to obtain rule codes;
[0034] A generation module is used to configure a query statement template based on the rule code, and to generate a customer portrait based on the query statement template and the business rules.
[0035] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;
[0036] The memory stores computer-executable instructions;
[0037] The processor executes the computer-executable instructions stored in the memory to implement the method as described in any one of the first aspects.
[0038] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method as described in any one of the first aspects.
[0039] In a fifth aspect, the present application provides a computer program product, comprising a program code. When a computer runs the computer program, the program code executes the method as described in any one of the first aspects.
[0040] In summary, the present application provides a data processing method, device, electronic device and storage medium, which can obtain business demand information and call corresponding business fields from a predefined rule library based on the business demand information; further, the business fields are spliced to obtain business rules that meet the business demand information, and the code statements corresponding to the business fields are integrated to obtain rule codes; then, a query statement template is configured based on the rule code, and a customer profile is generated based on the query statement template and the business rules, wherein each business field corresponds to an executed code statement; in this way, according to business needs, the required customer profile can be flexibly and quickly configured, and when the customer profile needs to be modified, only the business field corresponding to the business rule needs to be modified, and the code statement corresponding to each business field does not need to be modified, which enhances business flexibility, improves development efficiency, and reduces operation and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0042] Figure 1 A schematic diagram of an application scenario provided for an embodiment of the present application;
[0043] Figure 2 A flowchart of a data processing method provided in an embodiment of the present application;
[0044] Figure 3 A flowchart of a specific data processing method provided in an embodiment of the present application;
[0045] Figure 4 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application;
[0046] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.
[0047] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0048] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0049] In order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with substantially the same functions and effects. For example, the first device and the second device are only used to distinguish different devices, and their order is not limited. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit them to be different.
[0050] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.
[0051] In the present application, "at least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.
[0052] The following is an explanation of the professional terms involved in the application:
[0053] Drools: It can refer to an open source business rule engine that is easy to access enterprise policies, easy to adjust, and easy to manage. It is implemented based on the Rete algorithm and is used to match facts (code statements) with business rules to infer the corresponding rule results.
[0054] Rule engine: It can refer to a component embedded in an application, used to separate business decisions from application code and write business decisions using predefined semantic modules. It can accept data input, interpret business rules, and make business decisions based on business rules. The business rules can be composed of two parts: conditions and actions, that is, when the conditions are met, the actions are executed.
[0055] Customer portrait: It refers to an effective tool for outlining target users, linking user demands with design directions, and used to analyze the transaction needs of different customer groups. It can develop specific services and recommended businesses for different customer groups.
[0056] Since the financial industry has a large number of business transactions every day, business personnel have an increasing demand for customer portraits. Faced with the ever-changing needs of customer portraits, such as an increasing preference for real-time data analysis, it is necessary to develop recommended businesses that better meet customer needs based on the needs of different current customer groups, thereby increasing corporate revenue.
[0057] The present application is introduced below with reference to the accompanying drawings. Figure 1 A schematic diagram of an application scenario provided in an embodiment of the present application. A data processing method provided in the present application can be applied to the following Figure 1 In the application scenario shown. The application scenario includes: a terminal device 101 of a business person and a business processing platform 102; wherein a customer portrait system is deployed in the business processing platform 102; specifically, when a business person needs to configure a customer portrait, he can send a business requirement to the business processing platform 102 through the terminal device 101. Further, the business processing platform 102 can call business rules that meet the business requirements from the rule library. The business rules are composed of multiple business fields, such as business fields including customer portrait name, date range, processing type, conditional operation type, etc., and then the business processing platform 102 can generate a customer portrait on the customer portrait display interface of the customer portrait system based on the selected business rules, so that the business person can click on the customer portrait on the portrait system display interface, select the displayed content, and query the corresponding data of the target customer group through the corresponding query statement template, so that the business person can dynamically and conveniently analyze the target customer group and formulate corresponding recommended business and service strategies for customers.
[0058] It should be noted that the business rules stored in the rule library correspond to corresponding execution codes, which are written in advance by Internet technology (IT) engineers, i.e., developers. When the corresponding business rules are determined, the corresponding execution codes are directly called; the business rules are rules written in advance by business analysts (business personnel) that meet various application scenarios.
[0059] In one possible implementation, customer portraits in the financial industry are mostly generated directly based on business experience or simple logical rules. That is, by analyzing the needs raised by business personnel, developers write code, combine business rules with back-end logic code, and then generate customer portraits and put them online.
[0060] However, the development process of the above customer portrait often takes several weeks or even months, and the communication between developers and business personnel and the analysis of business needs often take up most of the time period, resulting in a long time period. In addition, due to the high coupling between business rules and back-end code logic, the development and operation and maintenance costs are high for changes in customer portraits.
[0061] In response to the above problems, the present application provides a data processing method to help business personnel configure the customer portraits they need directly, flexibly and quickly according to business needs when configuring customer portraits; specifically, the corresponding business fields can be found from the rule library according to business needs, and then the code statements corresponding to each business field can be matched, and the business fields that meet the business needs can be spliced to obtain business rules. Correspondingly, the business rules including the code statements of the business fields are also integrated to obtain execution codes. Furthermore, a query statement template is configured based on the execution code, and the required customer portraits are generated according to the query statement templates and business rules. In this way, by separating the business rules from the back-end logic code, the business rule discussions between developers and business personnel are reduced, the time cycle is shortened, and the operation and maintenance costs are reduced. When the customer portrait needs to be modified, only the business field corresponding to the business rule needs to be modified, and the code statement corresponding to each business field does not need to be modified, thereby enhancing business flexibility.
[0062] The technical solution of the present application is described in detail with specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0063] Figure 2 A flowchart of a data processing method provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the data processing method comprises the following steps:
[0064] S201, obtaining business requirement information, and calling corresponding business fields from a predefined rule library based on the business requirement information; each business field corresponds to an executable code statement.
[0065] In an embodiment of the present application, a predefined rule base may refer to a rule base for storing business fields, wherein the business fields are used to construct business rules, such as business fields including customer portrait name, date range, processing type, conditional operation type, data granularity, etc. The customer portrait name is used to indicate the type and target content of the customer portrait, such as the deposit balance on a specified date, the number of credit cards held on that day, etc. The date range is used to indicate the storage time of the data corresponding to the customer portrait, such as one day, etc. The processing type is used to indicate the algorithm type for processing the data corresponding to the customer portrait, such as summation, etc. The conditional operation type is used to indicate the corresponding preset conditions when the customer portrait outputs the corresponding data, such as the balance is greater than 0, etc. The data granularity is used to indicate the type of the corresponding data output by the customer portrait, such as the customer name, card number, etc.
[0066] It should be noted that the embodiment of the present application does not specifically limit the type and number of business fields stored in the predefined rule base. The above is only an example, and the business fields are defined in advance according to different business scenarios.
[0067] In this step, the corresponding business fields are called from the predefined rule library based on the business demand information, that is, based on the business demand information proposed by the business personnel, the business fields corresponding to the business demand information are selected from the predefined rule library. For example, the business demand information is to generate a customer name that can be queried for a deposit balance greater than 10,000 before February 30, 2022. The business fields that can be called in the predefined rule library include customer portrait names: deposit balance on a specified date, date range before February 30, 2022, conditional operation type for deposit balance greater than 10,000, and data granularity as customer name. Each business field corresponds to a code statement that executes the corresponding logic, and the code statement is also a pre-defined code stored in the predefined rule library. The embodiment of the present application does not specifically limit the form and content of the code statement corresponding to each business field, which is used to implement the corresponding execution logic.
[0068] S202: splice the business fields to obtain business rules that meet business demand information, and integrate code statements corresponding to the business fields to obtain rule codes.
[0069] Exemplarily, the business rules composed of business fields may be as shown in Table 1:
[0070] Table 1
[0071]
[0072]
[0073] Among them, the first column corresponds to the rule number corresponding to the business rule, the second column corresponds to the customer portrait name corresponding to the business rule, the third column corresponds to the date range corresponding to the business rule, the fourth column corresponds to the processing type corresponding to the business rule, the fifth column corresponds to the conditional operation type corresponding to the business rule, the sixth column corresponds to the data granularity corresponding to the business rule, and the seventh column corresponds to other business fields corresponding to the business rule, which can be expanded according to the application scenario.
[0074] It should be noted that the embodiment of the present application does not specifically limit the type and number of business fields included in each business rule, and the business rules formed based on the business fields are only examples. Different business requirements correspond to different business fields, and then the business fields that meet the business requirements are spliced to obtain the required business rules.
[0075] In this step, the business fields are spliced to obtain business rules that meet the business demand information. Further, the code statements corresponding to the business fields are integrated to obtain rule codes, that is, the business fields that meet the business needs are spliced to obtain the required business rules, and then each business field in the predefined rule library is matched with the code statement through the Drools rule engine to obtain a matching result. The matching result is the code statement corresponding to the business field that meets the business needs, and the matching results are integrated to obtain the rule code corresponding to the business rule.
[0076] S203: configuring a query statement template based on the rule code, and generating a customer profile based on the query statement template and the business rules.
[0077] In an embodiment of the present application, a query statement template may refer to a query statement corresponding to a function corresponding to a customer profile, wherein the query statement template includes a plurality of different query types and query contents, and is used to query different customer data in a database, such as querying a customer's deposit balance within a certain period of time. The embodiment of the present application does not specifically limit the query type and query content corresponding to the query statement template.
[0078] In this step, a query statement template is configured based on the rule code, and a customer portrait is generated based on the query statement template and the business rules, that is, the matching result is converted into a corresponding query statement template and a corresponding front-end portrait based on matching the business rules with the corresponding code statements. Furthermore, the front-end portrait is generated on the front-end interface of the customer portrait system, and the query statement template corresponding to the front-end portrait is imported into the database, so that business personnel can perform touch operations on the front-end interface of the customer portrait system and call the corresponding query statement template to query the data of the target customer group.
[0079] Therefore, the present application provides a data processing method, which can obtain business demand information and call corresponding business fields from a predefined rule library based on the business demand information; further, the business fields are spliced to obtain business rules that meet the business demand information, and the code statements corresponding to the business fields are integrated to obtain rule codes; then, a query statement template is configured based on the rule code, and a customer profile is generated based on the query statement template and the business rules, wherein each business field corresponds to an executed code statement; in this way, according to business needs, the required customer profile can be flexibly and quickly configured, and when the customer profile needs to be modified, only the business field corresponding to the business rule needs to be modified, and the code statement corresponding to each business field does not need to be modified, which enhances business flexibility, improves development efficiency, and reduces operation and maintenance costs.
[0080] Optionally, calling a corresponding business field from a predefined rule library based on the business requirement information includes:
[0081] Based on the business demand information, a corresponding business scenario is called from a predefined rule library; each business scenario is configured with business fields required for executing the business;
[0082] Determine whether there is a business field corresponding to the business scenario in the predefined rule base;
[0083] If yes, calling the corresponding business field from the predefined rule base based on the business requirement information;
[0084] If not, a writing requirement is sent to the developer's terminal device, so that the developer writes code statements corresponding to the business fields required by the business scenario based on the writing requirement, and the code statements written by the developer and the corresponding business fields are stored in the predefined rule library.
[0085] In an embodiment of the present application, a business scenario may refer to a business scenario that is set to meet different business needs. Each business scenario includes business fields required to execute the business. The number and type of the business fields are defined in advance. The business scenarios and their corresponding business fields are stored in a predefined rule library for use. The embodiment of the present application does not specifically limit the number and type of business fields required to execute the business in each business scenario, which is set according to the needs of the business scenario.
[0086] In this step, the corresponding business scenario is called from the predefined rule library based on the business requirement information, that is, each business requirement information has a corresponding business scenario in the predefined rule library, and the business scenario is set based on different business requirements. Further, it is determined whether the business fields contained in the business scenario corresponding to the business requirement information in the predefined rule library meet the business requirement information, and then it is determined whether the required business fields can be directly called. If the business fields required in a certain business scenario do not partially exist in the predefined rule library, it is necessary to send a writing requirement to the developer's terminal device, so that the developer can write code statements corresponding to the partially non-existent business fields based on the writing requirement, and store the code statements written by the developer and the corresponding business fields in the predefined rule library, so that the corresponding business fields can be called from the predefined rule library based on the business requirement information.
[0087] It should be noted that one or more business fields corresponding to the business scenario do not exist in the predefined rule library, and business personnel are required to write business fields and developers are required to write code statements corresponding to the business fields, or all business fields and code statements corresponding to the business fields are written by developers. The embodiments of the present application do not make specific limitations on this.
[0088] Therefore, since the business needs of business analysts need to be frequently updated and changed, the embodiments of the present application can adaptively increase the business fields in the predefined rule base to meet different business scenarios, thereby complying with business demand information and improving the breadth of application.
[0089] Optionally, generating a customer profile based on the query statement template and the business rule includes:
[0090] Obtaining a rule number corresponding to the business rule, and generating a page interface based on the rule number; the page interface is used for business personnel to call the corresponding business rule in a visual interface;
[0091] A connection relationship is established between the query statement template and the page interface, and the business fields of the business rules are called to generate a customer portrait.
[0092] In an embodiment of the present application, the rule number may refer to an identification number corresponding to a business rule, and the rule number is used to mark different business rules. For example, if the business rule number is 01, the corresponding business rule is that the customer name and customer card number whose deposit balance is greater than 0 within 180 days before the current day can be queried. The embodiment of the present application does not specifically limit the representation form and content of the rule number. The above is only an example. It can be a number, a letter, or a combination of the two.
[0093] In this step, a page interface is generated based on the rule number, that is, the page interface is designed through business rules. The page interface can call business rules that meet business needs. Accordingly, the designed business rules are published to the predefined rule library. Based on the correspondence between business rules and page interfaces, business personnel can call corresponding business rules in the visual interface. Furthermore, a connection relationship is established between the query statement template and the page interface to facilitate the calling of business rules to generate customer portraits.
[0094] Therefore, the embodiment of the present application can call the corresponding business rules based on the corresponding page interface, improve the calling rate, reduce the possibility of errors, and facilitate use by business personnel.
[0095] Optionally, the code statements corresponding to the business fields are integrated to obtain rule codes, including:
[0096] For each business field, calling a rule engine to match the business field with the code statement in the predefined rule base to obtain a matching result;
[0097] Based on the matching result, the code statements corresponding to the business fields are obtained, and the code statements are integrated to obtain rule codes.
[0098] In this step, for each business field, the Drools rule engine can be used to match each code statement in the predefined rule library to obtain a matching result, which is whether there is a corresponding code statement for each business field. Furthermore, based on the matching result, the code statement corresponding to each business field is found, and the corresponding code statements are integrated to obtain the rule code, that is, the execution code corresponding to the business rule.
[0099] It can be understood that the code statements in the predefined rule library are written in advance by developers. If a code statement corresponding to a business field does not exist in the predefined rule library, a writing requirement will be sent to the developer's terminal device so that the developer can write the code statement corresponding to the business field based on the writing requirement. Further, the newly written code statement will be stored in the predefined rule library.
[0100] It should be noted that the embodiment of the present application does not specifically limit the way of integrating code statements, and the code statements can be integrated according to a pre-defined order or a priority order of the business fields.
[0101] Therefore, the embodiment of the present application can extract the business rules from the backend code logic through the rule engine, so that each business field corresponds to a code statement, solve the high coupling between business rules and code logic, and then generate business rules that meet business needs.
[0102] Optionally, the method further includes:
[0103] Importing the query statement template corresponding to the customer portrait into the database, and visually displaying the customer portrait so that the business personnel can perform touch operations on the visual interface to query the customer's business transaction data;
[0104] Among them, the content displayed on the visualization interface includes: customer portrait name, query field and query conditions.
[0105] In an embodiment of the present application, business transaction data may refer to basic data about customers stored in a database in a customer portrait system, and the basic data may be used to formulate different recommended businesses and service strategies. The query fields and query conditions are generated based on a query statement template. The query fields may refer to field types of business transaction data in a database that can be queried by business personnel, such as transaction amounts, transaction records, etc. The query conditions may refer to preset conditions for outputting business transaction data in a database that can be queried by business personnel, such as querying business transaction data from 2011 to 2012, and business transaction data with a transaction amount greater than 100,000. The embodiment of the present application does not limit the specific content corresponding to the query fields and query conditions, which are based on customer portraits generated in different application scenarios.
[0106] In this step, the query statement template corresponding to the customer portrait can be imported into the database, and the customer portrait can be visualized on the front-end interface of the customer portrait system. In this way, the business personnel can click on the customer portrait on the front-end interface and select the displayed content, such as the customer portrait name, query fields and query conditions, etc. Furthermore, through the corresponding query statement template, the back-end database is connected to query, and the query results are returned to the front-end interface for business personnel to view and analyze, so as to facilitate business personnel to dynamically and conveniently analyze the target customer groups and formulate corresponding recommended businesses and service strategies for customers.
[0107] Therefore, the embodiment of the present application visualizes the customer portrait and provides query operations for business personnel, thereby facilitating data analysis for business personnel and providing convenience for business personnel.
[0108] Optionally, the method further includes:
[0109] In response to the touch operation of the business personnel on the visual interface, determining the query field and query condition corresponding to the customer portrait;
[0110] The query field and the query condition are concatenated to generate a query statement, and a query is performed in the database based on the query statement to obtain the customer's business transaction data.
[0111] In this step, in response to the touch operations such as click operations performed by the business personnel on the front-end interface of the customer portrait system, the query fields and query conditions corresponding to the customer portrait are determined. Furthermore, through the corresponding query statement template, the query fields and query conditions are spliced into a specific query statement, and based on the query statement, the back-end database is connected to perform business transaction data query to obtain the query results.
[0112] Therefore, the embodiments of the present application can query the required business transaction data based on the query fields and query conditions, which not only improves the convenience of use for business personnel, but also increases the rate of querying data.
[0113] Optionally, the method further includes:
[0114] Obtaining a target behavior instruction input by a business person, wherein the target behavior instruction includes an add behavior instruction, a delete behavior instruction, and a modify behavior instruction; the target behavior instruction is used to change the number and type of business fields included in the business rules;
[0115] Calling a corresponding execution code based on the target behavior instruction, and modifying a business rule corresponding to the customer profile based on the execution code to generate a new customer profile;
[0116] The new customer portrait is displayed visually so that business personnel can query the customer's business transaction data based on the new customer portrait in a visual interface.
[0117] In an embodiment of the present application, an add behavior instruction may refer to an instruction to increase the type and / or quantity of business fields included in a certain business scenario. Based on the add behavior instruction, the business rules formed in the business scenario can be modified. The type of the business field may refer to the corresponding designable field type in different business scenarios, which is used to provide different business services and thus meet business needs. The embodiment of the present application does not specifically limit the type and quantity corresponding to the business field.
[0118] It should be noted that deleting a behavior instruction and modifying a behavior instruction are similar to adding a behavior instruction. For details, please refer to the description of adding a behavior instruction, which will not be repeated here.
[0119] In this step, the business personnel can input the target behavior instruction on the front-end interface of the customer portrait system, such as an increase behavior instruction for increasing the number of business fields included in a business rule. Further, based on the increase behavior instruction, the corresponding execution code is called, and based on the execution code, the number of business fields in the business rule corresponding to the customer portrait is increased to generate a new customer portrait; and the new customer portrait is displayed on the front-end interface of the customer portrait system, so that the business personnel can use the generated new customer portrait to query the required business transaction data.
[0120] Therefore, the data processing method based on the rule engine provided in the embodiment of the present application not only has easy-to-understand rule logic, but also has a low learning threshold for business personnel to write business rules. There is no need for developers to modify the back-end code logic. Business personnel only need to modify the business fields corresponding to the business rules to achieve the addition, modification, and deletion of customer profiles, which shortens the development cycle of new customer profiles, improves the efficiency of customer profile launch, reduces the cost required to modify business logic, and adapts to the diversity and complexity of customer profiles.
[0121] In combination with the above embodiments, Figure 3 A flow chart of a specific data processing method provided in an embodiment of the present application is as follows: Figure 3 As shown, the process of the data processing method includes the following steps:
[0122] Step A: Preliminary preparation, i.e. writing of business rules. Business analysts write business rules (multiple business fields), and IT engineers write code statements corresponding to business rules. IT engineers can also process data in the back-end database to facilitate the call of processed data. Furthermore, the written business rules and code statements can be stored in the rule library (predefined rule library).
[0123] Step B: Obtain business demand information, call the corresponding business fields from the rule library based on the business demand information, and for each business field, match each code statement in the rule library through the Drools rule engine to obtain the matching result, and convert it into the corresponding query statement template and the corresponding customer portrait based on the matching result. Accordingly, generate the customer portrait on the customer portrait display interface of the customer portrait system, and import the query statement template corresponding to the customer portrait into the back-end database. The back-end database is used to provide portrait query data to the customer portrait display interface, and the customer portrait display interface is used to display various types of customer portraits to business analysts.
[0124] Step C: Based on step B, the business analyst can click on the customer portrait on the customer portrait display interface and select the content to be displayed. In response to the business analyst's operation, the corresponding query statement template is called, the query fields and conditions are spliced into a specific query statement, the backend database is connected for query, and the query results are returned to the customer portrait display interface for the business analyst to view and analyze.
[0125] The present application provides a data processing method, including four modules, namely, a rule library, a rule engine, a database, and a customer portrait display module, so that business personnel can dynamically and conveniently add, modify, and delete business rules based on the four modules. At the same time, by separating the business rules from the back-end code logic, the development and operation and maintenance costs can be reduced. When configuring customer portraits, there is no need for developers to modify the back-end code logic. Instead, business personnel can add, delete, and modify the business fields in the business rules, which enhances business flexibility, shortens the development cycle of customer portraits, and reduces the cost of modifying business logic.
[0126] In the foregoing embodiments, the data processing method provided by the embodiments of the present application is introduced, and in order to implement the various functions in the method provided by the embodiments of the present application, the electronic device as the execution subject may include a hardware structure and / or a software module, and the above functions are implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a certain function of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
[0127] For example, Figure 4 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, the device includes: an acquisition module 410, a splicing module 420 and a generation module 430; wherein the acquisition module 410 is used to acquire business demand information, and call corresponding business fields from a predefined rule library based on the business demand information; each business field corresponds to an executed code statement;
[0128] The splicing module 420 is used to splice the business fields to obtain business rules that meet business demand information, and integrate code statements corresponding to the business fields to obtain rule codes;
[0129] The generation module 430 is used to configure a query statement template based on the rule code, and generate a customer profile based on the query statement template and the business rules.
[0130] Optionally, the acquisition module 410 is specifically configured to:
[0131] Based on the business demand information, a corresponding business scenario is called from a predefined rule library; each business scenario is configured with business fields required for executing the business;
[0132] Determine whether there is a business field corresponding to the business scenario in the predefined rule base;
[0133] If yes, calling the corresponding business field from the predefined rule base based on the business requirement information;
[0134] If not, a writing requirement is sent to the developer's terminal device, so that the developer writes code statements corresponding to the business fields required by the business scenario based on the writing requirement, and the code statements written by the developer and the corresponding business fields are stored in the predefined rule library.
[0135] Optionally, the generating module 430 is specifically configured to:
[0136] Obtaining a rule number corresponding to the business rule, and generating a page interface based on the rule number; the page interface is used for business personnel to call the corresponding business rule in a visual interface;
[0137] A connection relationship is established between the query statement template and the page interface, and the business fields of the business rules are called to generate a customer portrait.
[0138] Optionally, the splicing module 420 is specifically used for:
[0139] For each business field, calling a rule engine to match the business field with the code statement in the predefined rule base to obtain a matching result;
[0140] Based on the matching result, the code statements corresponding to the business fields are obtained, and the code statements are integrated to obtain rule codes.
[0141] Optionally, the device further comprises a display module, wherein the display module is used to:
[0142] Importing the query statement template corresponding to the customer portrait into the database, and visually displaying the customer portrait so that the business personnel can perform touch operations on the visual interface to query the customer's business transaction data;
[0143] Among them, the content displayed on the visualization interface includes: customer portrait name, query field and query conditions.
[0144] Optionally, the device further includes a query module, wherein the query module is configured to:
[0145] In response to the touch operation of the business personnel on the visual interface, determining the query field and query condition corresponding to the customer portrait;
[0146] The query field and the query condition are concatenated to generate a query statement, and a query is performed in the database based on the query statement to obtain the customer's business transaction data.
[0147] Optionally, the device further comprises a modification module, wherein the modification module is configured to:
[0148] Obtaining a target behavior instruction input by a business person, wherein the target behavior instruction includes an add behavior instruction, a delete behavior instruction, and a modify behavior instruction; the target behavior instruction is used to change the number and type of business fields included in the business rules;
[0149] Calling a corresponding execution code based on the target behavior instruction, and modifying a business rule corresponding to the customer profile based on the execution code to generate a new customer profile;
[0150] The new customer portrait is displayed visually so that business personnel can query the customer's business transaction data based on the new customer portrait in a visual interface.
[0151] The specific implementation principle and effects of a data processing device provided in an embodiment of the present application can be found in the relevant descriptions and effects corresponding to the above embodiments, and will not be elaborated here.
[0152] The present application also provides a schematic diagram of the structure of an electronic device. Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, the electronic device may include: a processor 501 and a memory 502 communicatively connected to the processor; the memory 502 stores a computer program; the processor 501 executes the computer program stored in the memory 502, so that the processor 501 executes the method described in any of the above embodiments.
[0153] The memory 502 and the processor 501 may be connected via a bus 503 .
[0154] An embodiment of the present application further provides a computer-readable storage medium, which stores computer program execution instructions. When the computer program execution instructions are executed by a processor, they are used to implement the method described in any of the aforementioned embodiments of the present application.
[0155] An embodiment of the present application further provides a chip for executing instructions, wherein the chip is used to execute the method described in any of the aforementioned embodiments as executed by an electronic device in any of the aforementioned embodiments of the present application.
[0156] An embodiment of the present application further provides a computer program product, which includes a program code. When a computer runs the computer program, the program code executes the method described in any of the aforementioned embodiments as executed by an electronic device in any of the aforementioned embodiments of the present application.
[0157] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.
[0158] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.
[0159] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.
[0160] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
[0161] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the method described in each embodiment of the present application.
[0162] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the application may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.
[0163] The memory may include high-speed random access memory (RAM), and may also include non-volatile memory (NVM), such as at least one disk storage, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a disk or an optical disk, etc.
[0164] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.
[0165] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special computer.
[0166] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic device or a main control device.
[0167] The above is only a specific implementation of the embodiment of the present application, but the protection scope of the embodiment of the present application is not limited thereto, and any changes or replacements within the technical scope disclosed in the embodiment of the present application should be included in the protection scope of the embodiment of the present application. Therefore, the protection scope of the embodiment of the present application should be based on the protection scope of the claims.
Claims
1. A data processing method, characterized in that: The method comprises: Acquire business requirement information, and call corresponding business fields from a predefined rule base based on the business requirement information; each business field corresponds to an executable code statement, the predefined rule base is a rule base for storing business fields and code statements corresponding to the business fields, and the business fields are used to form business rules; The business fields are spliced to obtain business rules that meet the business demand information, and the code statements corresponding to the business fields are integrated to obtain rule codes; Configure a query statement template based on the rule code, and generate a customer profile based on the query statement template and the business rules; Generating a customer profile based on the query statement template and the business rules includes: Obtaining a rule number corresponding to the business rule, and generating a page interface based on the rule number; the page interface is used for business personnel to call the corresponding business rule in a visual interface; Establishing a connection relationship between the query statement template and the page interface, and calling the business field of the business rule to generate a customer portrait; The method further comprises: Obtaining a target behavior instruction input by a business person, wherein the target behavior instruction includes an add behavior instruction, a delete behavior instruction, and a modify behavior instruction; the target behavior instruction is used to change the number and type of business fields included in the business rules; The corresponding execution code is called based on the target behavior instruction, and the business rules corresponding to the customer profile are changed based on the execution code to generate a new customer profile.
2. The method according to claim 1, characterized in that Based on the business requirement information, the corresponding business field is called from the predefined rule library, including: Based on the business demand information, a corresponding business scenario is called from a predefined rule library; each business scenario is configured with business fields required for executing the business; Determine whether there is a business field corresponding to the business scenario in the predefined rule base; If yes, calling the corresponding business field from the predefined rule base based on the business requirement information; If not, a writing requirement is sent to the developer's terminal device, so that the developer writes code statements corresponding to the business fields required by the business scenario based on the writing requirement, and the code statements written by the developer and the corresponding business fields are stored in the predefined rule library.
3. The method according to claim 1, characterized in that The code statements corresponding to the business fields are integrated to obtain rule codes, including: For each business field, calling a rule engine to match the business field with the code statement in the predefined rule base to obtain a matching result; Based on the matching result, the code statements corresponding to the business fields are obtained, and the code statements are integrated to obtain rule codes.
4. The method according to claim 1, characterized in that The method further comprises: Importing the query statement template corresponding to the customer portrait into the database, and visually displaying the customer portrait so that the business personnel can perform touch operations on the visual interface to query the customer's business transaction data; Among them, the content displayed on the visualization interface includes: customer portrait name, query field and query conditions.
5. The method according to claim 4, characterized in that The method further comprises: In response to the touch operation of the business personnel on the visual interface, determining the query field and query condition corresponding to the customer portrait; The query field and the query condition are concatenated to generate a query statement, and a query is performed in the database based on the query statement to obtain the customer's business transaction data.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The new customer portrait is displayed visually so that business personnel can query the customer's business transaction data based on the new customer portrait in a visual interface.
7. A data processing device, characterized in that: The device comprises: An acquisition module is used to acquire business demand information, and based on the business demand information, call corresponding business fields from a predefined rule base; each business field corresponds to an executable code statement, and the predefined rule base is a rule base for storing business fields and code statements corresponding to the business fields, and the business fields are used to form business rules; A splicing module is used to splice the business fields to obtain business rules that meet business demand information, and integrate code statements corresponding to the business fields to obtain rule codes; A generation module, configured to configure a query statement template based on the rule code, and generate a customer profile based on the query statement template and the business rules; The generating module is specifically used for: Obtaining a rule number corresponding to the business rule, and generating a page interface based on the rule number; the page interface is used for business personnel to call the corresponding business rule in a visual interface; Establishing a connection relationship between the query statement template and the page interface, and calling the business field of the business rule to generate a customer portrait; The acquisition module is further used to acquire target behavior instructions input by business personnel, wherein the target behavior instructions include adding behavior instructions, deleting behavior instructions, and modifying behavior instructions; the target behavior instructions are used to change the number and type of business fields included in the business rules; The generation module is also used to call the corresponding execution code based on the target behavior instruction, and to change the business rules corresponding to the customer profile based on the execution code to generate a new customer profile.
8. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 6.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method according to any one of claims 1 to 6.
10. A computer program product, characterized in that The computer program comprises a program code, and when a computer runs the computer program, the program code executes the method according to any one of claims 1 to 6.
Citation Information
Patent Citations
Service rule generation method and system based on natural language processing
CN110196719A
