CN117312307A

CN117312307A - Service data processing method, device, computer equipment and storage medium

Info

Publication number: CN117312307A
Application number: CN202311195619.8A
Authority: CN
Inventors: 陈世强
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2023-09-15
Filing date: 2023-09-15
Publication date: 2023-12-29

Abstract

The present application relates to a business data processing method, apparatus, computer device, storage medium and computer program product. The method comprises the following steps: responding to a service processing result display instruction, and acquiring a service type and a service identifier; configuring a corresponding service data splicing template according to the service type; acquiring service processing data to be spliced from each service data production system based on the service identification; and performing data splicing on each piece of service processing data to be spliced by using a service data splicing template to obtain and display service processing results. The method can improve flexibility and usability of service data splicing.

Description

Service data processing method, device, computer equipment and storage medium

Technical Field

The present invention relates to the field of big data processing technology, and in particular, to a service data processing method, apparatus, computer device, storage medium, and computer program product.

Background

With the continuous development of internet technology, the business transaction of the bank is gradually changed from an off-line transaction mode to an on-line transaction mode, and a user can complete the business transaction operation through convenience tools such as a bank terminal, a bank application program and the like.

Since general banking business transaction can be completed through linkage coordination of a plurality of business systems, business processing data of a plurality of business systems needs to be collected when a business processing result is displayed to a user. In the prior art, a fixed splicing method is generally used for splicing the data of different service systems, however, along with the requirements of service development, each service system can cause changes of a data model and the like when performing function construction, at the moment, the splicing logic when performing data splicing is correspondingly changed, and when the service system is changed or the splicing rule is changed, the traditional splicing method needs to modify the splicing template by means of modifying an engine code, so that the problems of inflexibility, workload and the like of data splicing are easily caused.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a service data processing method, apparatus, computer device, computer readable storage medium, and computer program product that can improve flexibility and usability of service data splicing.

In a first aspect, the present application provides a service data processing method, where the method includes:

Responding to a service processing result display instruction, and acquiring a service type and a service identifier;

configuring a corresponding service data splicing template according to the service type;

acquiring service processing data to be spliced from each service data production system based on the service identification;

and performing data splicing on the business processing data to be spliced by using the business data splicing template to obtain and display business processing results.

In one embodiment, the configuring the corresponding service data splicing template according to the service type includes:

acquiring a target splicing tool identifier corresponding to the service type and a service data splicing sequence according to the service type;

and configuring and obtaining a service data splicing template corresponding to the service type based on the target splicing tool identifier and the service data splicing sequence.

matching the service type with a preset service type in a preset template configuration table; the preset template configuration table comprises a corresponding relation between a preset service type and a splicing tool identifier and a service data splicing sequence;

When the preset template configuration table does not have the preset service type matched with the service type, acquiring a service data processing rule corresponding to the service type;

and obtaining a target splicing tool based on the service data processing rule, and generating a service data splicing template of the service type according to the target splicing tool.

In one embodiment, the obtaining the target splicing tool based on the business data processing rule includes:

performing rule abstraction analysis on the service data processing rule to obtain rule processing logic of the service data processing rule;

based on the rule processing logic, a calling tool generator generates a target stitching tool for executing the rule processing logic.

comparing the rule processing logic with each storage logic in a logic storage library;

determining a first rule processing logic and a storage logic which meet a merging condition, and determining a splicing tool of the storage logic as a target splicing tool of the first rule processing logic;

Determining a second rule processing logic that does not satisfy the merge condition;

based on the second rule processing logic, a calling tool generator generates a target stitching tool for executing the second rule processing logic.

In one embodiment, the method further comprises:

responding to a template updating instruction aiming at the service data splicing template, and displaying the service data splicing template on a user terminal in an editable way;

acquiring an updating data processing rule of the business data splicing template based on a template updating operation triggered by the business data splicing template;

generating an update stitching tool according to the update data processing rule;

and updating the business data splicing template based on the updating splicing tool to obtain an updated business data splicing template.

In a second aspect, the present application further provides a service data processing apparatus, where the apparatus includes:

the instruction response module is used for responding to the service processing result display instruction and acquiring the service type and the service identifier;

the template configuration module is used for configuring a corresponding service data splicing template according to the service type;

the data acquisition module is used for acquiring service processing data to be spliced from each service data production system based on the service identification;

And the data splicing module is used for carrying out data splicing on the business processing data to be spliced by using the business data splicing template to obtain and display business processing results.

In a third aspect, the present application also provides a computer device comprising a memory storing a computer program and a processor implementing the steps of the above method when the processor executes the computer program.

In a fourth aspect, the present application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the above-described method.

In a fifth aspect, the present application also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the method described above.

According to the business data processing method, the business data processing device, the computer equipment, the storage medium and the computer program product, the business data processing system responds to the business processing result display instruction, the business type and the business identifier are obtained, the business data splicing template matched with the current business type is configured according to the business type, the business processing data to be spliced is obtained from each business data production system based on the business identifier, and the business processing data to be spliced are subjected to data splicing by using the business data splicing template, so that the business processing result is obtained and displayed. Because the service data splicing templates are dynamically configured according to the service types, when each service data production system changes or the data splicing rules change in the service processing process, the templates are only required to be configured again, and the flexibility and usability of service data splicing are effectively improved.

Drawings

FIG. 1 is an application environment diagram of a business data processing method in one embodiment;

FIG. 2 is a flow chart of a business data processing method in one embodiment;

FIG. 3 is a flowchart illustrating a step of configuring a corresponding service data splicing template according to a service type in one embodiment;

FIG. 4 is a flowchart illustrating steps for obtaining a target stitching tool based on business data processing rules in one embodiment;

FIG. 5 is a flow chart of a business data processing method according to another embodiment;

FIG. 6 is a block diagram of a business data processing system in one embodiment;

FIG. 7 is a flow chart of a method for processing service data according to another embodiment;

FIG. 8 is a block diagram of a business data processing device in one embodiment;

fig. 9 is an internal structural diagram of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

The service data processing method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the service data processing system 102 communicates with the user terminal 104 and each of the service data generating systems 106 via a network. The data storage system may store data that data processing system 102 needs to process. The data storage system may be integrated on data processing system 102 or may reside on a cloud or other network server. The user triggers a business process result presentation instruction based on the user terminal 104, and sends the business process presentation instruction to the data processing system 102. The data processing system 102 responds to the service processing result display instruction, acquires the service type and the service identifier, configures a corresponding service data splicing template according to the service type, acquires service processing data to be spliced from each service data generating system 106 based on the service identifier, and performs data splicing on each service processing data to be spliced by using the service data splicing template to obtain a service processing result. And sending the service processing result to the user terminal 104 for display. The user terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, etc. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The data processing system 102 and each of the business data generation systems 106 can be implemented as a single server or as a cluster of servers.

In one embodiment, as shown in fig. 2, a service data processing method is provided, and the method is applied to the data processing system in fig. 1 for illustration, and includes the following steps:

step 202, responding to the service processing result display instruction, and obtaining the service type and the service identification.

The service processing result display instruction is an instruction for indicating the data processing system to display the service processing result to the user after the service processing is completed. The service processing result display instruction can be triggered and generated by a user based on the service processing system integrated on the user terminal, for example, the user logs in the service processing system through the user terminal and clicks a result display button on the service processing system, so that the service processing result display instruction can be triggered and generated. The service processing result display instruction may also be triggered and generated by a preconfigured result display event in the service processing system. For example, when the service processing is completed, the generation of a service processing result display instruction can be triggered. It can be understood that the service result display instruction carries the service type and the service identifier.

The service type refers to a type to which the service for processing the service belongs, and the service type is different according to service scenes, for example, in a banking service scene, the service type can comprise a resource transfer type, a resource borrowing type, a resource value-added type and the like. The service identifier is the identification data marked by the service processing procedure. When a user triggers a service processing operation on a certain service, a unique service identifier, such as a service serial number, is correspondingly generated and used for marking the service processing process.

Specifically, the data processing system responds to a service processing result display instruction, wherein the service processing result display instruction comprises a service type and a service identifier of a service processing process corresponding to a user. The data processing system acquires the service type and the service identifier carried by the service processing result display instruction.

And 204, configuring a corresponding service data splicing template according to the service type.

The service data splicing template is template information for splicing the data later, and the service processing data is spliced through the service data splicing template, so that a unified service processing result meeting the user requirements can be obtained. It will be appreciated that the business data splice templates correspond to business types.

Specifically, after the data processing system acquires the service type corresponding to the service processing performed by the user, the data processing system dynamically configures a service data splicing template corresponding to the service type according to the service type.

And 206, acquiring service processing data to be spliced from each service data production system based on the service identification.

The service data production system is each service system participating in the service processing process, the general service processing process can complete the service processing operation by the linkage cooperation of a plurality of service systems, and each service system can generate corresponding service processing data when participating in the service processing process. When generating the service processing result corresponding to the service processing, the service processing data generated by each service data production system is required to be spliced to obtain the complete service processing result.

In order to avoid the chaotic management of the data, when the corresponding service processing data is generated, each service data production system sets identification information consistent with the service identification for the service processing data so as to facilitate the subsequent searching of the service processing data according to the service identification and obtain the service processing data generated in the service processing process corresponding to the service identification.

Specifically, the data processing system acquires service processing data to be spliced from each service data production system based on the acquired service identifier. It can be appreciated that, in order to ensure data privacy, the data processing system may construct a private data transmission environment with each service data production system in advance, and the data processing system may acquire service processing data to be spliced from each service data production system through a preset data acquisition protocol.

And step 208, performing data splicing on the business processing data to be spliced by using a business data splicing template, and obtaining and displaying a business processing result.

The data splicing refers to the operation of intercepting key fields related to a service processing process from each service processing data provided by each service data production system and merging to obtain a service processing result. It will be appreciated that each business data production system corresponds to a respective data production rule and data production template, and that the business process data produced by each business data production system may include system information related to its own business system in addition to the key fields related to the business process.

When the service processing result is generated, if all the service processing data produced by each service data production system are combined, the whole combination process occupies a large amount of operation resources, the generation efficiency of the service processing result is reduced, and the obtained service processing result contains a large amount of irrelevant information, so that the use experience of a user is reduced. Therefore, the key information is intercepted from each service processing data to be spliced through data splicing operation, and the service processing result is obtained through splicing.

Specifically, after the data processing system dynamically configures a service data splicing template for the service type, the service data splicing template is used for carrying out data splicing on each piece of service processing data to be spliced, so that a service processing result containing key information of a service processing process can be obtained. And the data processing system sends the service processing result to the user terminal and displays the service processing result to the user.

In the service data processing method, the service data processing system responds to the service processing result display instruction, acquires the service type and the service identifier, configures a service data splicing template matched with the current service type according to the service type, acquires service processing data to be spliced from each service data production system based on the service identifier, and performs data splicing on each service processing data to be spliced by using the service data splicing template to obtain and display the service processing result. Because the service data splicing templates are dynamically configured according to the service types, when each service data production system changes or the data splicing rules change in the service processing process, the templates are only required to be configured again, and the flexibility and usability of service data splicing are effectively improved.

In one embodiment, configuring a corresponding service data splicing template according to a service type includes:

and acquiring a target splicing tool identifier corresponding to the service type and a service data splicing sequence according to the service type. And configuring and obtaining a service data splicing template corresponding to the service type based on the target splicing tool identifier and the service data splicing sequence.

The target splicing tool is used for realizing various data splicing rules. A developer can develop numerous splicing tools by using a development language, such as Java, and the like, and various data splicing rules are realized through the splicing tools. In order to realize dynamic configuration of the data splicing templates, each splicing tool needs to be independently developed and realized, and after the implementation, the same data splicing rules can be provided with services, for example, a trim splicing tool is generated to realize removal of left and right blank spaces in the data items.

In order to achieve reusability of the splicing tools and flexible configuration of the data splicing templates, a developer sets corresponding splicing tool identifiers for each splicing tool. Each splicing tool can be independent and decoupled from the data spelling template through the splicing tool identification, the same splicing tool can be used by a plurality of data splicing templates, and when the configured data splicing templates are stored, all splicing tools in the data splicing templates are not required to be stored together, only the target splicing tool identification of each target splicing tool in the data splicing templates is required to be stored with the data splicing templates, so that the storage pressure of a data processing system is effectively reduced.

The service data splicing sequence can be considered as the processing sequence of each data to be processed in the data splicing process. The service data splicing sequence can be generated according to the relation chain sequence of service data processing, for some fields in the service processing result, multiple data processing according to different rules may be needed, at this time, through the service data splicing sequence, the data processing system sequentially calls the relevant splicing tools, the result produced by the splicing tool called in the previous step is output as a parameter to the splicing tool called in the next step, and so on until all operations in the service data splicing sequence are completed, and the final result of the field is the final result.

Specifically, the data processing system acquires a corresponding target splicing tool identifier and a service data splicing sequence according to a service type corresponding to service processing. It can be appreciated that a developer may pre-determine a correspondence between a service type and a target splicing tool identifier, and a service data splicing order, generate a configuration mapping table according to the correspondence, and pre-store the configuration mapping table in the data processing system. When a service processing result is generated, the data processing system searches the configuration mapping table according to the service type, and further determines a target splicing tool identifier corresponding to the service type and a service data splicing sequence.

After the target splicing tool identifier and the service data splicing sequence are obtained, the data processing system can obtain a service data splicing template corresponding to the service type based on the target splicing tool identifier and the service data splicing sequence configuration, so that the flexibility and the usability of service data splicing are effectively improved.

In other embodiments, as shown in fig. 3, configuring a corresponding service data splicing template according to a service type includes:

step 302, matching the service type with a preset service type in a preset template configuration table; the preset template configuration table comprises the corresponding relation between the preset service type and the splicing tool identifier as well as the splicing sequence of the service data.

The preset template configuration table is a preset mapping table for representing the corresponding relation between the preset service type and the splicing tool identifier and the service data splicing sequence. The developer can generate a preset template configuration table in advance according to the corresponding relation among the service type, the splicing tool identification and the service data splicing sequence, and store the template configuration table in the service data processing system, so that the service data processing system can be conveniently called at any time.

Specifically, after the service data processing system acquires the service type, the service data processing system calls a preset template configuration table, matches the service type with the preset service type in the preset template configuration table, and determines whether the preset service type matched with the service type exists.

Step 304, when the preset service type matched with the service type does not exist in the preset template configuration table, acquiring a service data processing rule corresponding to the service type.

The service data processing rule is a data processing rule which is required to be used for generating a service processing result corresponding to the service type. And determining the splicing rule of the target field in the service processing result according to the service data processing rule.

Specifically, when determining that the preset template configuration table does not have the preset service type matched with the service type, the service data processing system indicates that a service processing result of a new service needs to be generated at the moment. And the splicing tool and the data splicing sequence corresponding to the service type do not exist in the current service processing system. In order to be able to configure a service data splicing template meeting the requirements of users, the data processing system acquires a service data processing rule corresponding to a service type.

And step 306, obtaining a target splicing tool based on the business data processing rule, and generating a business data splicing template of the business type according to the target splicing tool.

Specifically, since the target splicing tool is a splicing tool for implementing the service data splicing rule, the service data processing system extracts the service data splicing rule from the service data processing rule after obtaining the service data processing rule, and obtains the target splicing tool for performing data splicing subsequently according to the service data splicing rule. The service data processing system sets a target splicing tool identifier for the target splicing tool, generates a corresponding service data splicing sequence, binds the target splicing tool identifier, the service data splicing sequence and the service type, and generates a service data splicing template corresponding to the service type. It will be appreciated that the business data processing rules may be obtained by a user, or developer, uploading to the business data processing system based on the terminal.

In this embodiment, whether a preset service type matched with a service type exists in the preset template configuration table or not can be quickly determined through the preset template configuration table, that is, whether the service data processing system can dynamically configure a service data splicing template meeting the requirement of a user or not. When the preset template configuration table is determined to not have the preset service type matched with the service type, the service data processing system can also directly generate a corresponding target splicing tool according to the service data processing rule, so that the service data splicing template matched with the service type is configured, and the flexibility and the usability of service data splicing are effectively improved.

Further, in some embodiments, obtaining the target stitching tool based on the business data processing rules includes:

and carrying out rule abstraction analysis on the service data processing rule to obtain rule processing logic of the service data processing rule. Based on the rule processing logic, the calling tool generator generates a target stitching tool for executing the rule processing logic.

The rule abstract analysis is an effective means for making the data processing rule more specific. The rule abstract analysis refers to a process of analyzing the data processing rule through a language analysis technology and determining rule processing logic to be realized in the data processing rule.

Specifically, after the service data processing system acquires the service data processing rule corresponding to the service type, a preset abstract analysis method is used for carrying out rule abstract analysis on the service data processing rule to obtain rule processing logic of the service data processing rule. It may be appreciated that the preset abstract analysis method may be a rule processing logic that obtains keywords from a business data processing rule by using a keyword extraction method. The rule processing logic may also be obtained by performing semantic analysis on the business data processing rules using a neural network model, such as a semantic analysis model.

After the rule processing logic of the service data processing rule is obtained, the service data processing system calls a tool generating program to generate a target splicing tool for executing the rule processing logic and realizing the processing effect which the service data processing rule wants to realize.

In this embodiment, by performing rule abstract analysis on the service data processing rule, the core processing logic of the service data processing rule can be determined more intuitively, so that the target splicing tool generated according to the rule processing logic can accurately realize the processing effect that the service data processing rule wants to realize, and the accuracy of service data processing is improved.

In other embodiments, as shown in FIG. 4, obtaining a target stitching tool based on business data processing rules includes:

and step 402, performing rule abstraction analysis on the business data processing rule to obtain rule processing logic of the business data processing rule.

Specifically, after the service data processing system acquires the service data processing rule corresponding to the service type, a preset abstract analysis method is used for carrying out rule abstract analysis on the service data processing rule to obtain rule processing logic of the service data processing rule.

At step 404, the rule processing logic is compared to each storage logic in the logic repository.

The logic repository is a storage database for storing rule processing logic corresponding to each splicing tool. Each storage logic in the logic storage library corresponds to one splicing tool.

Specifically, the business data processing system logically compares rule processing logic of the business data processing rule with each storage logic in the logic repository.

In step 406, the first rule processing logic and the storage logic that satisfy the merge condition are determined, and the splicing tool of the storage logic is determined as the target splicing tool of the first rule processing logic.

Wherein the merge condition is a decision rule that decides whether the first rule processing logic has storage logic that can merge. When any one storage logic in the first rule processing logic and the logic storage library meets the combination condition, the first rule processing logic can be considered to be the same as or similar to the storage logic, and can be combined to generate a logic processing rule capable of meeting the corresponding business data processing logic.

In some of these embodiments, the merge condition may be that the similarity of the first rule processing logic and the storage logic is greater than a preset threshold. The business data processing system can use a preset similarity analysis model to analyze the similarity of the first rule processing logic and the storage logic to obtain the similarity of the first rule processing logic and the storage logic, compare the similarity with a preset threshold, and when the similarity is larger than the preset threshold, the first rule processing logic and the storage logic can be considered to meet the merging rule and can be merged.

For example, if rule 1 is scol1= "… …", rule 2 is scol2= "456 …", where it can be seen that the value in scol1 quote includes 6 spaces, and similarly, scol2 includes 3 spaces on the right side, both rule 1 and rule 2 are required values that cannot include spaces, so rule 1 and rule 2 have the same processing logic, and a trim splicing tool can be used to perform space deletion work. So that the processing logic of rule 1, rule 2 may be merged.

At step 408, a second rule processing logic that does not satisfy the merge condition is determined.

It should be noted that, when rule merging is performed, the rule processing logic of merging cannot be excessively abstract, otherwise, the rule processing logic cannot be well implemented by subsequent development of a corresponding splicing tool.

For example, if rule 1 is tcol1=scol1+scol2, tcol1=trim (scol1) for rule 2, and several rules are different processing logic for rule 3 tcol=trim (scol2), and cannot be combined together.

Specifically, the business data processing system determines rule processing logic in the logic repository for which no storage logic is present as second rule processing logic that does not satisfy the merge condition.

Step 410, based on the second rule processing logic, the calling tool generator generates a target stitching tool for executing the second rule processing logic.

Specifically, since the second rule processing logic does not have the same or similar storage logic, the second rule processing logic does not have a splicing tool matched with the second rule processing logic, and the second rule processing logic needs to be generated by the service data processing system. The business data processing system generates a target stitching tool for executing the second rule processing logic based on the second rule processing logic by calling the tool generator.

In some embodiments, after obtaining the target splicing tool of the second rule processing logic, the service data processing system may also set a target splicing tool identifier, such as a tool number, a tool name, etc., for the target splicing tool. And binding and storing the corresponding relation between the target splicing tool identifier and the second rule processing logic, and storing the second rule processing logic into a logic storage library.

In the above embodiment, whether the combinable first rule processing logic exists is determined by combining the rules, and when the combinable first rule processing logic exists, the splicing tool corresponding to the storage logic of the first rule processing logic meeting the combining condition is determined as the target splicing tool of the first rule processing logic, so that the rule processing logic stored in the service data processing system can be effectively reduced, the storage pressure of the service data processing system is reduced, and the multiplexing rate of the rule processing logic can be improved.

In some of these embodiments, several common splicing tools are illustrated:

the template sample table obtained according to the splicing tool can be shown in the following table:

the target splice result (stored in the database of the business data processing system) has 100 fields (see the top row above) tcol, tcol2, tcol3. The atomic tool of the processing rule corresponding to each splice result field is described in the corresponding column (where N/a indicates that the data source system field is not applicable). The "Sys1" in Sys1.Scol1 is herein a system name or number that is used to distinguish which data source system this data item is. As can be seen here, more than one source field (tcol 100 corresponds to sys2.Scol2, sys3.Scol 3) may be configured for the value of one target field (tcol 100) in the configuration of the template. At the same time, one piece of result data (corresponding to tcol1, tcol2,..tcol 100) also corresponds to data of a plurality of systems of sys1, sys2, sys3,...

In the service processing process, the demands of users are various, and the service data processing templates corresponding to the service types also need to be updated and changed frequently so as to meet the changeable use demands of the users.

Based on this, in some embodiments, as shown in fig. 5, the service data processing method further includes:

step 502, responding to a template updating instruction for the business data splicing template, and displaying the business data splicing template on the user terminal in an editable way.

The template updating instruction is an instruction for instructing the service data processing system to update the service data splicing template corresponding to the current service type. The template updating instruction can be generated by a service personnel or a user based on terminal triggering, or can be generated by triggering a pre-configured updating event in the service data processing system, for example, the template updating instruction is automatically generated by triggering at an updating node of a service updating period of a service type.

Specifically, the service data processing system responds to a template updating instruction aiming at the service data splicing template, and the service data splicing template to be updated is displayed on the user terminal in an editable manner.

Step 504, based on the template updating operation triggered on the service data splicing template, the updating data processing rule of the service data splicing template is obtained.

Specifically, a service person or a user triggers a template updating operation based on a service data splicing template displayed on a user terminal. And the service data processing system acquires the updated data processing rule of the service data splicing template. For example, a user or a service person may determine, based on the displayed service data splicing template, a data rule to be updated, and upload, through a template updating component on the user terminal, the updated data rule of the service data splicing template to the service data processing system. Or, the user or the business personnel directly splice the template based on the displayed business data, and modify the data processing rule which can be realized by the template. And the service data processing system responds to the modification operation of the user and acquires the update data rule of the service data splicing template.

Step 506, generating an update stitching tool according to the update data processing rules.

Specifically, the service data processing system performs rule abstraction analysis on the update data processing rule according to the acquired update data processing rule to obtain rule processing logic of the update data processing rule, and calls a tool generating program to generate an update splicing tool for executing the rule processing logic of the update data processing rule based on the rule processing logic of the update data processing rule.

And step 508, updating the business data splicing template based on the updating splicing tool to obtain an updated business data splicing template.

Specifically, the service data processing system replaces the target splicing tool in the service data splicing template with the updating splicing tool to obtain an updated service data splicing template.

In this embodiment, when a template updating requirement exists, the service data processing system may generate an updating splicing tool according to an updating data processing rule required by a user, and update the service data splicing template based on the updating splicing tool, so that the updated service data splicing template can more meet the use requirement of the user. Dynamic change of the service data splicing template can be realized without stopping service, and stability and flexibility of service data splicing are improved.

In one embodiment, a service data processing method is provided, and the method is taken as an example for being applied to the service data processing system shown in fig. 6.

The business data processing system comprises a data reading module, a rule management module, a splicing tool module, a configuration template module, a configuration information reading module, a splicing engine, a result curing module and a data model management module.

Wherein, the data reading module: and the data processing module is used for reading the data transmitted by the data source system to be spliced so as to facilitate the splicing use of the subsequent splicing engine.

Rule management module: the main work is to carry out overall analysis and abstraction on the data processing rules and describe the concrete logic of the data processing rules. And then maintaining the data processing rules into the system for unified adding, deleting and modifying management.

And a splicing tool module: the method is to uniformly manage the developed splicing tools, and the managed information comprises tool names, tool codes, tool functions, which data processing rule is realized by the tools, parameters required by the tools during execution, tool version numbers, development maintenance personnel and the like.

And (3) configuring a template module: the method is mainly used for managing the mapping of the data source system field corresponding to each field in various transactions in a splicing target result table in the data splicing system and the splicing tool.

Configuration information reading module: and the configuration information is used for reading the configuration information for the splicing engine so as to facilitate the data splicing processing.

A splicing engine: and the data of the data reading module is received, the splicing tool is dynamically called for carrying out data processing according to the configuration information read by the configuration information reading module, and the data is integrated according to the splicing main key.

And (3) a result curing module: and (3) the result data which is spliced and integrated by the splicing engine is written into a database result table to be subjected to result solidification.

And the data model management module: the data source system and the data model of the data splicing system are managed, and the data source system and the data model of the data splicing system comprise a system name, a system number, a field name, a field type, a field value description and the like, so that a rule management module and a splicing tool module can perform reference management according to the data source system and the data model.

Specifically, the splicing tool module and the rule management module are managed by developers, PO and other color personnel as required (added and deleted when needed), and related information in the two modules needs to be read when the splicing tool module and the rule management module are configured in the configuration template module. After the configuration, the configuration information can be read by the configuration information reading module and output to the splicing engine. Meanwhile, the data reading module also reads the data of each data source system to be spliced and outputs the data to the splicing engine. After receiving the data to be spliced, the splicing engine dynamically calls a corresponding splicing tool according to the received configuration information transmitted by the configuration information reading module, the splicing tool generates target data according to the configuration rule, integrates the data of each field according to the main key value to form one item of target data, and finally transmits the item of target data to the result solidification module to write the item of target data into a target table of a target database. The data model management module is mainly used for managing a target data model of the data splicing system and a data model of the data source system, and providing reference basis for design and realization of the rule management module, the splicing tool module and the configuration template.

As shown in fig. 7, the service data processing method specifically includes the following steps:

step 701, regular carding. Specifically, the data processing rules of the relevant fields in the splicing target table are combed. Such as tcol1=sys1.scol1, tcol2=trim (sys2.scol2), etc., in any case the most primitive data processing rules are carded out.

And step 702, merging rules. Specifically, the data processing rules carded in step 701 are compared with rules in the rule management module, which are existing rules are identified, which are new rules, and the rules carded in step 701 are marked correspondingly.

At step 703, splice tool development intent is identified. Specifically, it is determined whether the splicing tool needs to be newly developed or a tool combination relationship chain can be performed according to the flag in step 702.

Step 704, a stitching tool is developed. Specifically, the development of the splicing tool is performed according to the decision of step 703, a java tool class (or library function of C) is developed and formed, and the newly developed splicing tool is registered in the splicing tool module.

Step 705, setting a tool combination relationship chain. Specifically, the splicing tools are set according to the decision of step 703 to have a call relationship in an order according to the data processing sequence logic, where it refers to which splicing tools are called and the call order. This information is also registered with the splice tool module.

Step 706, a configuration template is set. Specifically, the target field to be configured in the read data model management module is put into the configuration template, and template configuration is carried out according to the information in the rule management module and the splicing tool module.

Step 707, reading the data to be spliced. Specifically, this step is to read the data of each system that needs to be spliced (the data has been pushed to the data splicing system by each system) and pass it to the splicing engine.

Step 708, the configuration information is read. Specifically, after the splicing engine receives the data to be spliced, the splicing engine reads the configuration data in the configuration template module according to the transaction type field and resides in the memory for subsequent use.

Step 709, data stitching. Specifically, according to the data received in steps 707 and 708 and the configuration information, the splicing tool is dynamically called to process the data in the data items to be spliced, the processed result is temporarily stored in the memory, and after all the data processing rules call the splicing tool to process, each result data in the memory is integrated into a complete data, including the main key and each data item.

And step 710, the spliced result falls into a library. Specifically, the splicing engine calls the api interface of the result curing module to store the spliced result data in step 709 into the database result table, and the round of splicing is completed.

Step 711, loop stitching. And performing data splicing in sequence according to the steps 707 to 710 until no data to be spliced is available in the step 707.

The service data splicing method in the embodiment can support the dynamic change of the number of the splicing parties without modifying a program, such as more or less. Because the program is not required to be modified, the corresponding development and testing workload of developers and testers is saved, the flexibility of the system is improved, the development and testing workload can be effectively reduced, and the usability and service continuity of the system are improved. All data processing logic is configurable, reducing the risk of problems with data quality.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a service data processing device for implementing the service data processing method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of one or more service data processing devices provided below may refer to the limitation of the service data processing method in the above description, which is not repeated here.

In one embodiment, as shown in fig. 8, there is provided a service data processing apparatus 800 comprising: an instruction response module 801, a template configuration module 802, a data acquisition module 803, and a data stitching module 804, wherein:

the instruction response module 801 is configured to obtain a service type and a service identifier in response to a service processing result display instruction.

The template configuration module 802 is configured to configure a corresponding service data splicing template according to the service type.

The data acquisition module 803 is configured to acquire service processing data to be spliced from each service data production system based on the service identifier.

The data splicing module 804 is configured to use a service data splicing template to splice data of each service processing data to be spliced, obtain a service processing result, and display the service processing result.

According to the service data processing device, the service data processing system responds to the service processing result display instruction, the service type and the service identification are obtained, the service data splicing template matched with the current service type is configured according to the service type, the service processing data to be spliced is obtained from each service data production system based on the service identification, and the service data splicing template is used for carrying out data splicing on each service processing data to be spliced, so that the service processing result is obtained and displayed. Because the service data splicing templates are dynamically configured according to the service types, when each service data production system changes or the data splicing rules change in the service processing process, the templates are only required to be configured again, and the flexibility and usability of service data splicing are effectively improved.

In some embodiments, the template configuration module is further to: acquiring a target splicing tool identifier corresponding to the service type and a service data splicing sequence according to the service type; and configuring and obtaining a service data splicing template corresponding to the service type based on the target splicing tool identifier and the service data splicing sequence.

In some embodiments, the template configuration module is further to: matching the service type with a preset service type in a preset template configuration table; the preset template configuration table comprises a corresponding relation between a preset service type and a splicing tool identifier and a service data splicing sequence; when the preset template configuration table does not have the preset service type matched with the service type, acquiring a service data processing rule corresponding to the service type; and obtaining a target splicing tool based on the service data processing rule, and generating a service data splicing template of the service type according to the target splicing tool.

In some embodiments, the template configuration module is further to: carrying out rule abstract analysis on the business data processing rule to obtain rule processing logic of the business data processing rule; based on the rule processing logic, the calling tool generator generates a target stitching tool for executing the rule processing logic.

In some embodiments, the template configuration module is further to: carrying out rule abstract analysis on the business data processing rule to obtain rule processing logic of the business data processing rule; comparing the rule processing logic with each storage logic in the logic storage library; determining a first rule processing logic and a storage logic which meet the merging condition, and determining a splicing tool of the storage logic as a target splicing tool of the first rule processing logic; determining a second rule processing logic that does not satisfy the merge condition; based on the second rule processing logic, the calling tool generator generates a target stitching tool for executing the second rule processing logic.

In some embodiments, the service data processing apparatus further comprises:

and the display module is used for responding to the template updating instruction aiming at the business data splicing template and displaying the business data splicing template on the user terminal in an editable way.

The updating rule acquisition module is used for acquiring the updating data processing rule of the business data splicing template based on the template updating operation triggered by the business data splicing template.

And the tool updating module is used for generating an updating splicing tool according to the updating data processing rule.

And the template updating module is used for updating the business data splicing template based on the updating splicing tool to obtain an updated business data splicing template.

The various modules in the service data processing device described above may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server integrated with a business data processing system, and the internal structure of which may be as shown in fig. 9. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer equipment is used for storing data such as service types, service identifiers, service data splicing templates, service processing data, service processing results and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business data processing method.

It will be appreciated by those skilled in the art that the structure shown in fig. 9 is merely a block diagram of a portion of the structure associated with the present application and is not limiting of the computer device to which the present application applies, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.

In an embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of a specific embodiment of the above-described business data processing method when executing the computer program.

In one embodiment, a computer readable storage medium is provided, on which a computer program is stored which, when executed by a processor, implements the steps of the specific embodiments of the business data processing method described above.

In an embodiment a computer program product is provided comprising a computer program which, when executed by a processor, implements the steps of the specific embodiments of the business data processing method described above.

It should be noted that, user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims

1. A method for processing service data, the method comprising:

2. The method of claim 1, wherein configuring the corresponding service data splice template according to the service type comprises:

3. The method of claim 1, wherein configuring the corresponding service data splice template according to the service type comprises:

4. A method according to claim 3, wherein said obtaining a target stitching tool based on said business data processing rules comprises:

5. A method according to claim 3, wherein said obtaining a target stitching tool based on said business data processing rules comprises:

6. The method according to any one of claims 2 to 5, further comprising:

7. A traffic data processing apparatus, the apparatus comprising:

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.

9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.