CN111179091A

CN111179091A - Business data processing method and device, electronic equipment and storage medium

Info

Publication number: CN111179091A
Application number: CN201911109346.4A
Authority: CN
Inventors: 刘瑞瑞
Original assignee: Taikang Insurance Group Co Ltd
Current assignee: Taikang Insurance Group Co Ltd; Taikang Pension Insurance Co Ltd
Priority date: 2019-11-13
Filing date: 2019-11-13
Publication date: 2020-05-19

Abstract

The invention provides a business data processing method and device, electronic equipment and a storage medium. The method comprises the following steps: receiving a service request initiated by a client; acquiring a target process set adapted to the service request; acquiring a target service type adapted to the service request from a preset service type library according to the service request and the target flow set; and calling an execution inlet of a target service node associated with the target service type from a preset service node library, and sequentially executing the target service node according to the execution sequence and the execution conditions of the target service node in the flow set so as to obtain the processing result of the service request. The technical problems that the existing entrusted system is simple and can not be customized in service processing, misoperation is easy to occur due to a large amount of manual operations, and service processing consumes a long time are solved, and the beneficial effects that the service processing efficiency and the accuracy are improved, and the dependence degree of the service processing process on manpower and material resources is reduced are achieved.

Description

Business data processing method and device, electronic equipment and storage medium

Technical Field

The present invention relates to the field of internet technologies, and in particular, to a method and an apparatus for processing service data, an electronic device, and a storage medium.

Background

Enterprise annuity business operations often involve the following four-party organization: a trusted organization, an account management line, a hosting line, and a commissioning line. The entrusted organization is mainly responsible for selecting, supervising and replacing accounts and managing lines for enterprises, collecting payment of employees and enterprises, carrying out treatment payment and the like. The account management line is a professional organization which receives the entrusted organization entrusts and is responsible for managing the annual fund account of the enterprise and keeping accounts. The hosting organization is a professional organization which receives the entrusted organization and safely stores the annual fund property of the enterprise. The operation means receiving the entrusted organization to invest and manage the property of the annual fund of the enterprise. Taking an enterprise as an example for paying annuity as a worker, the enterprise sends a payment application form to a trusted mechanism, the trusted mechanism informs an account management bank to carry out account keeping, after account keeping is finished, the trusted mechanism sends a payment notice to the enterprise and sends a collection notice to the account management bank, and after the enterprise pays the fee to the account management bank, the trusted mechanism sends the enterprise to an account certificate to inform the enterprise of payment to receive the money.

It can be seen that the trusted system used by the trusted organization is a core link in annual fund business operation, business processing flows in the system are in a diversified and complicated trend, interactive cooperation with service systems related to multi-party organizations is often required, and an entrusting party can set individualized requirements for the interactive processes between the trusted system and other three-party systems according to self requirements, so that the business process management of the trusted organization system and the business proficiency and strain capacity of personnel are seriously checked, a large amount of manpower and material resources are needed, errors caused by misoperation are easy to occur due to manual operation, and the time consumption of the business processing process is long.

Disclosure of Invention

Embodiments of the present invention provide a method and an apparatus for processing service data, an electronic device, and a storage medium, so as to solve the technical problems that the service processing of the existing trusted system is single and can not be customized, and a large amount of manual operations are easy to cause errors due to misoperation, which results in long time consumption in the service processing process.

In order to solve the technical problem, the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a method for processing service data, including:

receiving a service request initiated by a client;

acquiring a target process set adapted to the service request;

acquiring a target service type adapted to the service request from a preset service type library according to the service request and the target flow set;

and calling an execution inlet of a target service node associated with the target service type from a preset service node library, and sequentially executing the target service node according to the execution sequence and the execution conditions of the target service node in the flow set so as to obtain the processing result of the service request.

Optionally, the step of obtaining the target process set adapted to the service request includes:

searching a target flow set adapted to the service request in a preset flow set library;

if the target process set adaptive to the service request is not found in the process set library, constructing a target process set adaptive to the service request based on the service type library and the service node library according to service information associated with the service request;

the service information includes service requirement information of the entrusting party and/or service processing information of an account management line corresponding to the service request.

Optionally, the step of searching for the target process set adapted to the service request in a preset process set library includes:

if the service request belongs to a user-defined flow, searching a target flow set adapted to the service request in a preset flow set library according to the identifier of the entrusting party and/or the identifier of an account management line corresponding to the service request;

and if the service request belongs to a standard flow, searching the standard flow in the flow set library as a target flow set adapted to the service request.

Optionally, the step of constructing, according to the service information associated with the service request, a target process set adapted to the service request based on the service type library and the service node library includes:

acquiring a service type required for constructing a flow set adapted to the service information and a service node contained in the service type according to the service information;

constructing a flow set matched with the service information based on the service node and the service type, and storing the flow set into the flow set library;

if the service node library does not contain the execution entrance of the service node, adding the execution entrance of the service node into the service node library;

and if the service type is not contained in the service type library, adding the service type into the service type library.

Optionally, the step of obtaining, according to the service request and the target process set, a target service type adapted to the service request from a preset service type library includes:

acquiring the service type belonging to the target process set from the service type library as a first service type;

and acquiring a first service type consistent with the service type of the service request as a target service type adapted to the service request.

Optionally, before the step of obtaining the target process set adapted to the service request, the method further includes:

setting flow sets of different entrusters;

before the step of obtaining the target service type adapted to the service request from a preset service type library according to the service request and the target process set, the method further includes:

creating the service type library, and setting a process set to which each service type belongs in the service type library;

and aiming at each service type in the service type library, configuring the association relation between each service type and the service node in the service type library according to the service node contained in the flow set to which the service type belongs.

Optionally, if the service request is associated with a second service request before and after, after the step of calling an execution entry of a target service node associated with the target service type from a preset service node library, and sequentially executing the target service node according to an execution sequence and an execution condition of the target service node in the flow set to obtain a processing result of the service request, the method further includes:

if the processing result of the service request is successful, acquiring a second flow set adaptive to a second service request which is associated with the service request before and after;

acquiring a second service type adapted to the second service request from a preset service type library according to the second service request and the second process set;

and calling an execution inlet of a second service node associated with the second service type from a preset service node library, and sequentially executing the second service node according to the execution sequence and the execution conditions of the second service node in the second flow set so as to obtain the processing result of the second service request.

In a second aspect, an embodiment of the present invention further provides a service data processing apparatus, including:

the service request receiving module is used for receiving a service request initiated by a client;

a flow set obtaining module, configured to obtain a target flow set adapted to the service request;

a service type obtaining module, configured to obtain, according to the service request and the target flow set, a target service type adapted to the service request from a preset service type library;

and the service processing module is used for calling an execution inlet of a target service node associated with the target service type from a preset service node library, and sequentially executing the target service node according to the execution sequence and the execution conditions of the target service node in the flow set so as to obtain the processing result of the service request.

In a third aspect, an embodiment of the present invention additionally provides an electronic device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the business data processing method as described above.

In a fourth aspect, the embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements the steps of the service data processing method as described above.

In the embodiment of the invention, a service request initiated by a client is received; acquiring a target process set adapted to the service request; acquiring a target service type adapted to the service request from a preset service type library according to the service request and the target flow set; and calling an execution inlet of a target service node associated with the target service type from a preset service node library, and sequentially executing the target service node according to the execution sequence and the execution conditions of the target service node in the flow set so as to obtain the processing result of the service request. The technical problem that the service processing process is time-consuming and long due to the fact that a large amount of manual operations are prone to error caused by misoperation is solved, the service processing process capable of customizing the entrusted system according to requirements is achieved, the service processing efficiency and the accuracy are improved, and the dependence degree of the service processing process on manpower and material resources is reduced.

The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without inventive labor.

Fig. 1 is a flowchart illustrating steps of a service data processing method according to an embodiment of the present invention;

fig. 2 is a flowchart of steps of another service data processing method in the embodiment of the present invention;

fig. 3 is a schematic diagram of a service data processing flow in the embodiment of the present invention;

fig. 4 is a schematic structural diagram of a service data processing apparatus in an embodiment of the present invention;

fig. 5 is a schematic structural diagram of another service data processing apparatus in the embodiment of the present invention;

fig. 6 is a schematic diagram of a hardware structure of an electronic device in the embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Referring to fig. 1, a flowchart illustrating steps of a service data processing method according to an embodiment of the present invention is shown.

The method specifically comprises the following steps:

step 110, receiving a service request initiated by the principal.

In practical application, the entrusted organization can interact with a client to select, supervise and replace an account bank and a management bank for clients such as enterprises and the like, collect payment of employees and enterprises, carry out treatment payment and the like. Therefore, in the embodiment of the invention, when the entrusting party has the service requirement, the service request can be sent to the entrusted organization. In the embodiment of the present invention, the service request initiated by the principal may be received in any available manner, which is not limited to this embodiment of the present invention.

The service request may include a request for a service that any at least one trusted authority can handle for the trusted party, such as a service request for transferring a person in and out, a service request for transferring a person, a service request for paying a fee, and the like. Furthermore, the entrusting party may initiate the service request in any available manner, and the embodiment of the present invention is not limited thereto.

And step 120, acquiring a target process set adapted to the service request.

In practical application, the account management lines set by different consignors are not necessarily completely consistent, and the processing flows of different account management lines to the same business may be different. In addition, the processing requirements of different clients for the same service may be different.

For example, assume that the accounting line set by the principal a is a work line, and the accounting line set by the principal B is a farming line. When the processing member rolls out the business, the processing flow of the worker is the initiation application, the issuing management line carries out personal information change, the feedback with the issuing management line, and the processing flow of the farmer is the initiation application, the account translation and the completion of the issuing management line; or, when processing the payment service, the service requirement of the consignor a is to initiate payment for the parent company or the subsidiary company in one service request, and the service requirement of the consignor B is to initiate payment for the parent company and the subsidiary company in the next service request; and so on.

In view of the above, in the embodiment of the present invention, in order to avoid problems of a business processing error caused by a manual operation, a long time consumed by the business processing, and the like, a flow set may be set for each entrusting party in advance, and a flow of all businesses that a trusted organization can handle for a corresponding entrusting party may be included in the flow set. Then, after obtaining the service request initiated by the principal, in order to complete the service processing of the corresponding service request, a target flow set adapted to the currently received service request may be obtained.

And step 130, acquiring a target service type adapted to the service request from a preset service type library according to the service request and the target process set.

As mentioned above, the flow set may contain flows of all services that the trusted authority may handle for the corresponding trusted party, but the currently received service request may be only a request for an individual service, so after the target flow set is obtained by matching, the target service type adapted to the currently received service request may be further obtained. Specifically, the target service type adapted to the service request may be obtained from a preset service type library according to the service request and the target process set.

In practical applications, the processing flows for the same service type in different flow sets may be different, and therefore, in the embodiment of the present invention, the flow set to which each service type belongs may be set in a preset service type library. For example, the service type library may include a plurality of "member roll-out" service types, and one "member roll-out" service type may be set to belong to the flow set 1, and another "member roll-out" service type may belong to the flow set 2, at this time, the service flows specifically corresponding to the "member roll-out" service type of the flow set 1 and the "member roll-out" service type of the flow set 2 may not be identical, that is, the service nodes associated with the two service types may not be identical.

The obtained target service type belongs to the target flow set and is consistent with the service type requested by the currently received service request.

For example, if the currently received service request is a member roll-out request for a certain user, and the target flow set adapted to the currently received service request is the flow set 1, then at this time, the target service type adapted to the service request may be obtained as the above-mentioned "member roll-out" service type belonging to the flow set 1.

Step 140, invoking an execution entry of a target service node associated with the target service type from a preset service node library, and executing the target service node in sequence according to the execution sequence and the execution condition of the target service node in the flow set, so as to obtain the processing result of the service request.

After the target service type adapted to the currently received service request is obtained, an execution entry of a target service node associated with the target service type may be further called from a preset service node library, and then the target service nodes are sequentially executed according to an execution sequence and execution conditions of each target service node in the flow set, so as to obtain a processing result of the service request.

For example, if the target traffic type is the "member roll-out" traffic type described above that belongs to flow set 1. It is assumed that in the flow set 1, the service node whose service type is "member roll-out" and the execution sequence of each service node are as follows: the node of 'initiating application' is used for 'the accounting management line carries out personal information change' the node is used for 'the waiting accounting management line feeds back' the node is used for 'completing' the node. Then, at this time, the execution entries of the service nodes may be sequentially called in a preset service node library, and the corresponding service node operation is executed through the corresponding execution entry, so as to obtain the processing result of the service request.

For example, generally, the execution condition of the service node may include that the previous service node is successfully executed, if the previous service node is successfully executed, the next service node may be automatically triggered to be invoked and executed, and if the previous service node is not successfully executed, the previous service node may directly jump to the completion node and output the service processing result as the execution failure. Or, if the execution of a certain service node fails, the service node may be repeatedly executed again until the execution is successful or until the execution times of the corresponding service node reaches the preset upper limit, if the repeated execution is successful, the subsequent service node may be continuously executed, and if the execution times reaches the preset upper limit and is still the execution success, the node may be directly skipped to the completion node, and the service processing result is output as the execution failure.

Of course, in the embodiment of the present invention, the execution condition may not be set, and the execution of the next service node is automatically triggered after the execution of the previous service node is completed, so that whether the execution is successful is determined after all the service nodes are executed.

Of course, in the embodiment of the present invention, when the service node is executed to process the service request, service-related information for the service request currently initiated by the principal may also be required, for example, which members of the principal, member information related to the corresponding service request, service plan, provision, and target related to the service request, and the like. In practical application, the entrusting party may carry the service-related information when initiating the service request, and obtain information required when executing each target service node from the service-related information when executing the target service node.

In addition, in the embodiment of the present invention, the service node library includes each service node that can be invoked for execution, the service node included in each service type of the flow set is not a service node that can be directly executed, and more specifically, is an identifier of the service node, and information such as an execution sequence and an execution condition of the service node can be obtained through the flow set. And the service node associated with each service type library can be set in the service type library, so that the target service node to be called can be determined according to the target service type, and the corresponding target service node is called from the service node library and executed.

In the embodiment of the invention, a service request initiated by a client is received; acquiring a target process set adapted to the service request; acquiring a target service type adapted to the service request from a preset service type library according to the service request and the target flow set; and calling an execution inlet of a target service node associated with the target service type from a preset service node library, and sequentially executing the target service node according to the execution sequence and the execution conditions of the target service node in the flow set so as to obtain the processing result of the service request. The method and the system have the advantages that the business processing process of the trusted system can be customized according to requirements, the business processing efficiency and accuracy are improved, and the dependence degree of the business processing process on manpower and material resources is reduced.

Referring to fig. 2, in the embodiment of the present invention, the step 120 may further include:

and step 121, searching a target flow set adapted to the service request in a preset flow set library.

Step 122, if the target process set adapted to the service request is not found in the process set library, constructing a target process set adapted to the service request based on the service type library and the service node library according to the service information associated with the service request; the service information includes service requirement information of the entrusting party and/or service processing information of an account management line corresponding to the service request.

As described above, in the embodiment of the present invention, a flow set may be set for each consignor in advance, but in an actual application process, a new consignor may be continuously added, or a business requirement of an added consignor changes, or a business processing manner of an accounting line set by an added consignor changes, so that it is not possible to adapt to the flow set for each business request in time.

Therefore, in the embodiment of the present invention, after receiving the service request of the entrusting party, a target flow set adapted to the service request may be searched in a preset flow set library, and specifically, the target flow set adapted to the service request may be searched in the preset flow set library according to an identifier of the entrusting party corresponding to the service request and/or an identifier of an account management line corresponding to the service request. If the target flow set matched with the service request is found in the flow set library, the subsequent steps can be directly executed based on the currently found target flow set; and if the target process set adaptive to the service request is not found in the process set library, redefining a process set adaptive to the corresponding service request.

As described above, the business requirements of different clients may be different, and the business processing manners of different account management lines may also be different, so in the embodiment of the present invention, when creating a new flow set, a target flow set adapted to the business request may be specifically constructed based on the business type library and the business node library according to the business information associated with the business request. The service information includes service requirement information of the entrusting party and/or service processing information of an account management line corresponding to the service request. The service requirement information may include service requirement related information of the entrusting party for different services, service types required by the entrusting party, whether binding or precedence relationship exists between different service types, and the like; the business process information may include, but is not limited to, how the account management line processes different businesses, processing requirements, processing conditions, and the like.

Specifically, when a new flow set is created, the content specifically included in the service information may be preset according to a requirement, and the embodiment of the present invention is not limited thereto. In addition, the content specifically included in the service requirement information and the service processing information may also be preset according to the requirement, and the embodiment of the present invention is not limited thereto.

Optionally, in an embodiment of the present invention, the step 121 may further include:

step 1211, if the service request belongs to a custom flow, searching a target flow set adapted to the service request in a preset flow set library according to the identifier of the entrusting party and/or the identifier of the account management line corresponding to the service request;

step 1212, if the service request belongs to a standard flow, searching the standard flow in the flow set library as a target flow set adapted to the service request.

As mentioned above, in practical applications, a customized flow set can be set according to the personalized requirements of the consignor and/or the billing line. Of course, in practical applications, there may be a plurality of consignors or billing lines with the same service information, that is, a more general flow is adopted to execute various services, and at this time, at least one standard flow may be defined according to requirements. Therefore, in the embodiment of the present invention, in order to improve the utilization rate of the flow set, at least one standard flow set may be additionally set.

Then, if the service request belongs to a custom flow, a target flow set adapted to the service request can be searched in a preset flow set library according to the identifier of the entrusting party and/or the identifier of an account management line corresponding to the service request; and if the service request belongs to the standard flow, searching the standard flow in the flow set library as a target flow set adapted to the service request.

For example, a service node flow chart corresponding to a certain customized flow set service type being "payment" may be as follows: the method comprises the following steps of paying application input, checking for the acceptance of the general company service, paying to the account input, confirming for the payment to the account, matching for the transaction service, and finishing; in the standard process set, the service node flow chart corresponding to the service type "payment" may be as follows: the method comprises the following steps of payment application recording, to-be-checked business acceptance and verification of a head office, to-be-sent payment application, to-be-checked account feedback, to-be-checked operation and verification of the head office account management, to-be-checked sub-process circulation and completion.

Optionally, in an embodiment of the present invention, the step 122 further includes:

step 1221, according to the service information, obtaining a service type required for constructing a flow set adapted to the service information, and a service node included in the service type;

step 1222, based on the service node and the service type, constructing a flow set adapted to the service information, and storing the flow set in the flow set library;

step 1223, if the service node library does not include the execution entry of the service node, adding the execution entry of the service node to the service node library;

step 1224, if the service type is not included in the service type repository, adding the service type to the service type repository.

In the process of constructing the flow set, firstly, a service type required for constructing the flow set adapted to the service information and a service node included in the service type can be obtained according to the service information.

For example, if the flow set is set according to the client, the service information at this time includes service requirement information of the client. It is assumed that the acquired service type required for constructing the flow set adapted to the current service information includes a 'payment' service type, and the service type includes the following service nodes, and the execution sequence of each service node is as follows: the method comprises the following steps of payment application input, service acceptance and verification of a head office, payment to account input, payment to account confirmation, service matching to be paid and the like.

Then, in constructing a flow set adapted to the service information, the flow chart including the service node corresponding to the service type "payment" may be: the method comprises the following steps of payment application input, service acceptance and verification of a head office, payment to account input, payment to account confirmation, service matching to be paid and the like.

After the new process set is created, the new process set can be further stored in a process set library, so that a target process set of a video can be directly obtained when a service request sent by the same consignor is subsequently received.

In addition, in order to facilitate the subsequent invoking of the corresponding execution entry of the service node according to the service type included in the newly created flow set, it may be further determined whether the execution entry of the service node is included in the service node library or not, and whether the corresponding service type is included in the service type library or not, for any service type required by the flow set adapted to the service information and any service node included in the service type. If the service node library does not include the execution entry of the service node, the execution entry of the service node may be added to the service node library, and if the service type library does not include the service type, the service type may be added to the service type library. Moreover, according to the service node included in the service type, the association relationship between the newly added service type and each service node in the service node library can be set in the service type library, that is, the service node associated with the newly added service type is set, so that the execution entry of the service node can be conveniently searched according to the association relationship.

In the embodiment of the present invention, the flow set library may also only include the identifier of each flow set, and then after the target flow set adapted to the current service request is determined, a target service type that belongs to the target flow set and is consistent with the service type of the current service request may be further obtained in the service type library according to the identifier of the target flow set, and then an execution entry of the target service node associated with the target service type is called from the service node library according to the association relationship between the service type and the service node.

Referring to fig. 2, in an embodiment of the present invention, the step 130 may further include:

step 131, obtaining the service type belonging to the target process set from the service type library as a first service type;

step 132, obtaining a first service type consistent with the service type of the service request as a target service type adapted to the service request.

As mentioned above, in practical applications, the service type library may include a plurality of the same service types, but since the service types belong to different process sets, the service nodes included in the same service type belonging to different process sets may not be identical. Therefore, in the embodiment of the present invention, the service type library may include a plurality of identical service types, but the flow sets to which the plurality of identical service types belong are different from each other.

At this time, when the target service type adapted to the currently received service request is obtained from the service type library, the service type belonging to the target flow set may be obtained from the service type library first, and then the first service type consistent with the service type of the service request may be obtained, and is used as the target service type adapted to the service request.

Of course, in the embodiment of the present invention, the first service type consistent with the service type of the service request may also be obtained from the service type library, and then the service type belonging to the target process set is obtained from the first service type as the target service type. The embodiment of the present invention is not limited thereto.

Referring to fig. 2, in the embodiment of the present invention, before the step 120, the method may further include:

step 150, set up the flow sets of different consignors.

As described above, in the embodiment of the present invention, the flow sets of different consignors may be preset according to requirements, and the service types included in the flow set of each consignor may be set.

The setting manner of the flow is similar to that in step 122 or steps 1221 to 1222, and at this time, the flow set of the consignor may be set according to the service information of the consignor, which may specifically refer to the above steps and is not described herein again.

Referring to fig. 2, in the embodiment of the present invention, before the step 130, the method may further include:

step 160, creating the service type library, and setting a process set to which each service type belongs in the service type library;

step 170, for each service type in the service type library, configuring an association relationship between each service type and a service node in the service type library according to the service node included in the flow set to which the service type belongs.

In the embodiment of the present invention, a service type library may also be created in advance, a flow set to which each service type belongs is set in the service type library, and for each service type in the service type library, an association relationship between each service type and a service node is configured in the service type library according to a service node included in the flow set to which the service type belongs. Therefore, after the service request is received and the flow set is obtained, the execution inlet of the target service node associated with the flow set can be called through the target service type corresponding to the flow set and the service request, so that the service processing can be performed on the corresponding service request.

In addition, in the embodiment of the present invention, a service node library may also be created in advance, and the service node may include an execution entry of each service node, so as to facilitate the execution entry to execute the service operation corresponding to the corresponding service node.

As shown in fig. 3, in the embodiment of the present invention, a service node library is pre-established, a service type library is pre-established, service nodes associated with different service types are configured, a flow set library (a standard flow set established according to a standard flow, a flow set established according to an account management row flow, a flow set established according to an entrusting party flow such as an enterprise, and the like) is pre-established, and service types corresponding to different flow sets are respectively selected. After a contract is signed and a corresponding product is established and completed based on the contract, a flow set adapted to the contract can be selected for service processing, namely, after a service request initiated by a client corresponding to the corresponding product is received, a corresponding target service type is searched in the service type, and an execution inlet of a service node related to the target service type is called from a service node library to execute the corresponding service node and perform corresponding service processing; and if no matched flow set exists, one more flow set can be customized.

Referring to fig. 2, in the embodiment of the present invention, if the service request is associated with a second service request before and after, after step 140, the method may further include:

step 180, if the processing result of the service request is successful, acquiring a second flow set adapted to a second service request associated with the service request;

step 190, obtaining a second service type adapted to the second service request from a preset service type library according to the second service request and the second process set;

step 1110, invoking an execution entry of a second service node associated with the second service type from a preset service node library, and sequentially executing the second service node according to an execution sequence and an execution condition of the second service node in the second flow set, so as to obtain a processing result of the second service request.

In addition, in practical application, there may be a case where two service operations need to be bound and executed, that is, in order to implement a certain service, multiple service requests need to be performed, and each service request is sequentially associated in a front-to-back manner.

For example, an operation to transfer a member of the principal from accounting line a to accounting line B. If account line A and account line B support account translation, then the member can be translated directly from account line A to account line B; alternatively, to complete the operation, the member needs to be transferred out of the accounting line a and then into the accounting line B. For the second case, if the account row a and the account row B correspond to different process sets, two service applications need to be performed to complete member transfer. One of the service applications is a service request transferred from the accounting line a by the member, and the other service application is a service request transferred from the accounting line B by the member, and at this time, the first service request and the second service request may be considered to be related to each other.

Then, after obtaining a processing result of a previous service request in two service requests associated with each other, if the processing result of the service request is successful, the next service request, that is, a second service request, may be further processed, specifically, a second flow set adapted to the second service request associated with the service request may be obtained, and according to the second service request and the second flow set, a second service type adapted to the second service request may be obtained from a preset service type library; and calling an execution inlet of a second service node associated with the second service type from a preset service node library, and sequentially executing the second service node according to the execution sequence and the execution conditions of the second service node in the second flow set so as to obtain the processing result of the second service request. The specific implementation of the steps 180-1110 is similar to the steps 120-140, and reference is made to the above description, which is not repeated herein.

Of course, in the embodiment of the present invention, if there is a need, the total service processing result may be obtained comprehensively according to the service processing results of the two service requests related in the front and back, and the service processing result may also be returned to the client, or the service processing results of the two service requests related in the front and back may also be returned to the client, which is not limited in the embodiment of the present invention.

Of course, in the embodiment of the present invention, if the execution sequence between two service requests associated in front and back is not particularly limited, the front and back sequence of the above steps 120 to 140 and steps 180 to 1110 may not be controlled, which is not limited in the embodiment of the present invention, that is, the second service request may also be processed first. Executing another service request under the condition that the processing result of the second service request is successful; or, a plurality of associated service requests can be executed simultaneously; and so on.

In the embodiment of the invention, a target flow set adapted to the service request is searched in a preset flow set library; if the target process set adaptive to the service request is not found in the process set library, constructing a target process set adaptive to the service request based on the service type library and the service node library according to service information associated with the service request; the service information includes service requirement information of the entrusting party and/or service processing information of an account management line corresponding to the service request. In addition, if the service request belongs to a custom flow, searching a target flow set adapted to the service request in a preset flow set library according to the identifier of the entrusting party and/or the identifier of an account management line corresponding to the service request; and if the service request belongs to a standard flow, searching the standard flow in the flow set library as a target flow set adapted to the service request. The method and the device can improve the adaptation efficiency of the process set and the matching degree between the process set and the current business requirements, and further improve the business processing efficiency and the accuracy of the business processing result.

Moreover, in the embodiment of the present invention, a service type required for constructing a flow set adapted to the service information and a service node included in the service type may also be obtained according to the service information; constructing a flow set matched with the service information based on the service node and the service type, and storing the flow set into the flow set library; if the service node library does not contain the execution entrance of the service node, adding the execution entrance of the service node into the service node library; and if the service type is not contained in the service type library, adding the service type into the service type library. Therefore, the process set can be quickly created, the process set library, the service type library and the service node library are updated according to the created process set, the completeness of each material library is improved, the execution entries of the required service nodes are convenient to be called in time for subsequent service application, the service process corresponding to the service request is executed, and therefore the service processing efficiency and the accuracy of the processing result are improved.

In addition, in the embodiment of the present invention, a service type belonging to the target process set may also be obtained from the service type library as a first service type; and acquiring a first service type consistent with the service type of the service request as a target service type adapted to the service request. Therefore, the adaptation efficiency of the service type and the accuracy of the obtained target service type can be improved.

Secondly, in the embodiment of the invention, the flow sets of different consignors can be set. Creating the service type library, and setting a flow set to which each service type belongs in the service type library; and aiming at each service type in the service type library, configuring the association relation between each service type and the service node in the service type library according to the service node contained in the flow set to which the service type belongs. Therefore, the process set can call the execution inlet of the currently required service node through the service type library conveniently to execute each service node to finish service processing, and the interference information when the execution inlet of the service node is called can be reduced through a layer-by-layer calling mode, so that the service processing efficiency and accuracy are improved.

Further, in the embodiment of the present invention, if the service request is associated with a second service request before and after, and if the processing result of the service request is successful, a second flow set adapted to the second service request associated with the service request before and after is obtained; acquiring a second service type adapted to the second service request from a preset service type library according to the second service request and the second process set; and calling an execution inlet of a second service node associated with the second service type from a preset service node library, and sequentially executing the second service node according to the execution sequence and the execution conditions of the second service node in the second flow set so as to obtain the processing result of the second service request. Therefore, the service processing for the next service request associated with the current service request can be automatically triggered, and the service processing efficiency and the user experience are improved.

Referring to fig. 4, a schematic structural diagram of a service data processing apparatus in the embodiment of the present invention is shown.

The service data processing device of the embodiment of the invention comprises: a service request receiving module 210, a flow set obtaining module 220, a service type obtaining module 230 and a service processing module 240.

The functions of the modules and the interaction relationship between the modules are described in detail below.

A service request receiving module 210, configured to receive a service request initiated by a principal;

a flow set obtaining module 220, configured to obtain a target flow set adapted to the service request;

a service type obtaining module 230, configured to obtain, according to the service request and the target process set, a target service type adapted to the service request from a preset service type library;

a service processing module 240, configured to invoke an execution entry of a target service node associated with the target service type from a preset service node library, and execute the target service node in sequence according to an execution sequence and an execution condition of the target service node in the flow set, so as to obtain a processing result of the service request.

Referring to fig. 5, in the embodiment of the present invention, the flow set obtaining module 220 may further include:

the flow set searching submodule 221 is configured to search a preset flow set library for a target flow set adapted to the service request;

a flow set creating sub-module 222, configured to, if a target flow set adapted to the service request is not found in the flow set library, create a target flow set adapted to the service request based on the service type library and the service node library according to service information associated with the service request; the service information includes service requirement information of the entrusting party and/or service processing information of an account management line corresponding to the service request.

Optionally, in this embodiment of the present invention, the flow set searching sub-module 221 further includes:

a first searching unit, configured to search, if the service request belongs to a user-defined flow, a target flow set adapted to the service request in a preset flow set library according to an identifier of the principal and/or an identifier of an account management line corresponding to the service request;

and the second searching unit is used for searching a standard flow in the flow set library to serve as a target flow set adapted to the service request if the service request belongs to the standard flow.

Optionally, in this embodiment of the present invention, the flow set creation sub-module 222 further includes:

a flow element obtaining unit, configured to obtain, according to the service information, a service type required for constructing a flow set adapted to the service information, and a service node included in the service type;

a flow set creating unit, configured to create a flow set adapted to the service information based on the service node and the service type, and store the flow set in the flow set library;

a service node library updating unit, configured to add an execution entry of the service node to the service node library if the service node library does not include the execution entry of the service node;

and the service type base updating unit is used for adding the service type to the service type base if the service type is not contained in the service type base.

Referring to fig. 5, in the embodiment of the present invention, the service type obtaining module 230 further includes:

a first service type obtaining sub-module 231, configured to obtain, from the service type library, a service type belonging to the target process set as a first service type;

the second service type obtaining sub-module 232 is configured to obtain the first service type consistent with the service type of the service request, as a target service type adapted to the service request.

Referring to fig. 5, in an embodiment of the present invention, the apparatus may further include:

and a flow set setting module 250, configured to set flow sets of different consignors.

a service type library creating module 260, configured to create the service type library, and set a flow set to which each service type belongs in the service type library;

and a service node association module 270, configured to configure, for each service type in the service type library, an association relationship between each service type and a service node in the service type library according to the service node included in the flow set to which the service type belongs.

Referring to fig. 5, in the embodiment of the present invention, if the service request is associated with a second service request before and after, the apparatus may further include:

a second flow set obtaining module 280, configured to obtain a second flow set adapted to a second service request associated with the service request before and after the service request if the processing result of the service request is successful;

a second service type obtaining module 290, configured to obtain, according to the second service request and the second process set, a second service type adapted to the second service request from a preset service type library;

the second service processing module 2110 is configured to invoke an execution entry of a second service node associated with the second service type from a preset service node library, and sequentially execute the second service node according to an execution sequence and an execution condition of the second service node in the second flow set, so as to obtain a processing result of the second service request.

The service data processing apparatus provided in the embodiment of the present invention can implement each process implemented in the method embodiments of fig. 1 to fig. 2, and is not described herein again to avoid repetition.

Fig. 6 is a schematic diagram of a hardware structure of an electronic device implementing various embodiments of the present invention.

The electronic device 500 includes, but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, a processor 510, and a power supply 511. Those skilled in the art will appreciate that the electronic device configuration shown in fig. 6 does not constitute a limitation of the electronic device, and that the electronic device may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the electronic device includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 501 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 510; in addition, the uplink data is transmitted to the base station. In general, radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 501 can also communicate with a network and other devices through a wireless communication system.

The electronic device provides wireless broadband internet access to the user via the network module 502, such as assisting the user in sending and receiving e-mails, browsing web pages, and accessing streaming media.

The audio output unit 503 may convert audio data received by the radio frequency unit 501 or the network module 502 or stored in the memory 509 into an audio signal and output as sound. Also, the audio output unit 503 may also provide audio output related to a specific function performed by the electronic apparatus 500 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 503 includes a speaker, a buzzer, a receiver, and the like.

The input unit 504 is used to receive an audio or video signal. The input Unit 504 may include a Graphics Processing Unit (GPU) 5041 and a microphone 5042, and the Graphics processor 5041 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 506. The image frames processed by the graphic processor 5041 may be stored in the memory 509 (or other storage medium) or transmitted via the radio frequency unit 501 or the network module 502. The microphone 5042 may receive sounds and may be capable of processing such sounds into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 501 in case of the phone call mode.

The electronic device 500 also includes at least one sensor 505, such as light sensors, motion sensors, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 5061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 5061 and/or a backlight when the electronic device 500 is moved to the ear. As one type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the posture of an electronic device (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), and vibration identification related functions (such as pedometer, tapping); the sensors 505 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.

The display unit 506 is used to display information input by the user or information provided to the user. The Display unit 506 may include a Display panel 5061, and the Display panel 5061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 507 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device. Specifically, the user input unit 507 includes a touch panel 5071 and other input devices 5072. Touch panel 5071, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., operations by a user on or near touch panel 5071 using a finger, stylus, or any suitable object or attachment). The touch panel 5071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 510, and receives and executes commands sent by the processor 510. In addition, the touch panel 5071 may be implemented in various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 5071, the user input unit 507 may include other input devices 5072. In particular, other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

Further, the touch panel 5071 may be overlaid on the display panel 5061, and when the touch panel 5071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 510 to determine the type of the touch event, and then the processor 510 provides a corresponding visual output on the display panel 5061 according to the type of the touch event. Although in fig. 6, the touch panel 5071 and the display panel 5061 are two independent components to implement the input and output functions of the electronic device, in some embodiments, the touch panel 5071 and the display panel 5061 may be integrated to implement the input and output functions of the electronic device, and is not limited herein.

The interface unit 508 is an interface for connecting an external device to the electronic apparatus 500. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 508 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the electronic apparatus 500 or may be used to transmit data between the electronic apparatus 500 and external devices.

The memory 509 may be used to store software programs as well as various data. The memory 509 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 509 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The processor 510 is a control center of the electronic device, connects various parts of the whole electronic device by using various interfaces and lines, performs various functions of the electronic device and processes data by running or executing software programs and/or modules stored in the memory 509 and calling data stored in the memory 509, thereby performing overall monitoring of the electronic device. Processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 510.

The electronic device 500 may further include a power supply 511 (e.g., a battery) for supplying power to various components, and preferably, the power supply 511 may be logically connected to the processor 510 via a power management system, so as to implement functions of managing charging, discharging, and power consumption via the power management system.

In addition, the electronic device 500 includes some functional modules that are not shown, and are not described in detail herein.

Preferably, an embodiment of the present invention further provides an electronic device, including: the processor 510, the memory 509, and a computer program stored in the memory 509 and capable of running on the processor 510, where the computer program, when executed by the processor 510, implements each process of the foregoing service data processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program implements each process of the foregoing service data processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for processing service data is characterized by comprising the following steps:

receiving a service request initiated by a client;

acquiring a target process set adapted to the service request;

2. The method of claim 1, wherein the step of obtaining the target process set adapted to the service request comprises:

3. The method according to claim 2, wherein the step of searching the preset process set library for the target process set adapted to the service request comprises:

4. The method according to claim 2, wherein the step of constructing a target process set adapted to the service request based on the service type library and the service node library according to the service information associated with the service request comprises:

5. The method according to any one of claims 1 to 4, wherein the step of obtaining, according to the service request and the target process set, a target service type adapted to the service request from a preset service type library includes:

6. The method according to any of claims 1-4, wherein before the step of obtaining the target flow set adapted to the service request, further comprising:

setting flow sets of different entrusters;

7. The method according to any one of claims 1 to 4, wherein if the service request is associated with a second service request before and after, after the step of calling an execution entry of a target service node associated with the target service type from a preset service node library, and executing the target service node in sequence according to an execution sequence and an execution condition of the target service node in the flow set to obtain a processing result of the service request, the method further comprises:

8. A service data processing apparatus, comprising:

9. An electronic device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the business data processing method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the business data processing method according to any one of claims 1 to 7.