CN112799714A - Business data docking method and device, computer equipment and storage medium - Google Patents

Business data docking method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN112799714A
CN112799714A CN202110088385.1A CN202110088385A CN112799714A CN 112799714 A CN112799714 A CN 112799714A CN 202110088385 A CN202110088385 A CN 202110088385A CN 112799714 A CN112799714 A CN 112799714A
Authority
CN
China
Prior art keywords
service
processing
preset
component
service data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110088385.1A
Other languages
Chinese (zh)
Inventor
乔伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Pension Insurance Corp
Original Assignee
Ping An Pension Insurance Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Pension Insurance Corp filed Critical Ping An Pension Insurance Corp
Priority to CN202110088385.1A priority Critical patent/CN112799714A/en
Publication of CN112799714A publication Critical patent/CN112799714A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Technology Law (AREA)
  • Strategic Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

The application belongs to the technical field of data processing, and provides a service data docking method, a service data docking device, computer equipment and a computer-readable storage medium. According to the method and the device, the service data corresponding to the service to be processed is acquired, the service type corresponding to the service is identified according to the service data, the service processing workflow configuration corresponding to the service type is acquired according to the service type, the service data and the service processing workflow configuration are sent to the preset service butt-joint party, so that the service data are butt-jointed to the preset service butt-joint party, the preset service butt-joint party is enabled to process the service, the flexibility of the service processing workflow configuration corresponding to the service processing is improved, the light butt-joint of the service data in a complex butt-joint scene is realized, the efficiency of the service data butt-joint is improved, the service can be responded quickly, the maintenance efficiency of a service processing system can be improved, and the problems of more and more bloated service butt-joint and function overload are solved.

Description

Business data docking method and device, computer equipment and storage medium
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method and an apparatus for service data docking, a computer device, and a computer-readable storage medium.
Background
In the development process of an application system, along with the development of services, the system is more and more complex, for example, in an endowment insurance service, an endowment insurance core system is frequently docked with a company at present, along with the increase of services, the functions of the core are more and more, the programs are more and more complex, the service docking is more and more bloated, the source of the problem is function overload, because each service has the particularity, the number of special treatments in the docking is large, and the coupling of a general function and a special function is high, the later maintenance and the expansion are particularly difficult, and the software maintenance efficiency is reduced.
Disclosure of Invention
The application provides a service data docking method, a service data docking device, a computer device and a computer readable storage medium, which can solve the problem of low service data docking efficiency caused by the fact that a system is too bulky and functions are overloaded in a service docking process in the prior art.
In a first aspect, the present application provides a service data interfacing method, including: acquiring service data corresponding to a service to be processed; identifying a service type corresponding to the service according to the service data; acquiring service processing workflow configuration corresponding to the service type according to the service type, wherein the service processing workflow configuration is used for describing a processing flow for processing the service and preset component information of a preset component adopted by the processing flow; and sending the service data and the service processing workflow configuration to a preset service butt-joint party to butt-joint the service data to the preset service butt-joint party, so that the preset service butt-joint party processes the service according to the service data and the service processing workflow configuration.
In a second aspect, the present application further provides a service data interfacing apparatus, including: the first acquisition unit is used for acquiring service data corresponding to a service to be processed; the identification unit is used for identifying the service type corresponding to the service according to the service data; a second obtaining unit, configured to obtain, according to the service type, a service processing workflow configuration corresponding to the service type, where the service processing workflow configuration is used to describe a processing flow for processing the service and preset component information of a preset component adopted by the processing flow; and the docking unit is used for sending the service data and the service processing workflow configuration to a preset service docking party so as to dock the service data to the preset service docking party, so that the preset service docking party processes the service according to the service data and the service processing workflow configuration.
In a third aspect, the present application further provides a computer device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the service data docking method when executing the computer program.
In a fourth aspect, the present application further provides a computer-readable storage medium storing a computer program, which when executed by a processor causes the processor to perform the steps of the business data interfacing method.
The application provides a service data docking method, a service data docking device, computer equipment and a computer readable storage medium. When the data butt joint between different processing parties in the service processing process is realized, the service data corresponding to the service to be processed is obtained, the service type corresponding to the service is identified according to the service data, the service processing workflow configuration corresponding to the service type is obtained according to the service type, the service data and the service processing workflow configuration are sent to a preset service butt joint party to butt joint the service data to the preset service butt joint party, so that the preset service butt joint party processes the service, the service processing workflow configuration corresponding to the service processing is formed by combining the processing flow of the service with components, and the service processing workflow configuration and the service data are sent to the preset service butt joint party, so that the data butt joint between the different processing parties of the service is realized, the subsequent service processing party processes the service according to the configuration of the service processing workflow, particularly under the conditions of increased service and more overstaffed service butt joint, compared with the traditional technology, aiming at the direct butt joint of service data between different processing parties in the service processing process, the application is developed towards the component, simultaneously decouples the processing flow of the service processing and the function of the component, improves the flexibility of the configuration of the service processing workflow corresponding to the service processing by fully utilizing the flexibility of the configuration of the processing flow, the flexibility of the development of the component and the repeated characteristic of calling the component, realizes the light butt joint of the service data under the complex butt joint scene, simplifies the complexity of the data butt joint between different processing parties of the service, improves the flexibility of the data butt joint between different processing parties of the service, and further improves the efficiency of the butt joint of the service data, the method can quickly respond to the service, can also improve the maintenance efficiency of the service processing system, and solves the problems of more and more overstaffed service butt joint and function overload.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a service data docking method according to an embodiment of the present application;
fig. 2 is a schematic view of a first sub-flow of a service data docking method according to an embodiment of the present application;
fig. 3 is a second sub-flow diagram of a service data docking method according to an embodiment of the present application;
fig. 4 is a third sub-flow diagram of a service data docking method according to an embodiment of the present application;
fig. 5 is a fourth sub-flow diagram of a service data docking method according to an embodiment of the present application;
fig. 6 is a fifth sub-flow diagram of a service data docking method according to an embodiment of the present application;
fig. 7 is a sixth sub-flow diagram of a service data docking method according to an embodiment of the present application;
fig. 8 is a schematic block diagram of a service data interfacing apparatus provided in an embodiment of the present application; and
fig. 9 is a schematic block diagram of a computer device provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. 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 application.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Referring to fig. 1, fig. 1 is a schematic flow chart of a service data interfacing method according to an embodiment of the present application. As shown in FIG. 1, the method includes the following steps S11-S14:
s11, acquiring service data corresponding to the service to be processed;
and S12, identifying the service type corresponding to the service according to the service data.
Specifically, in the processing of complex services, it is generally difficult to directly process service data corresponding to a service, and multiple parties are required to participate in the cooperative processing of the service, so that the service data needs to be docked between different processing parties, so that each processing party performs corresponding preset processing on the service data, and the whole processing process of the service is finally completed.
In the embodiment of the present application, when implementing service data interfacing between multiple processing parties, the services may be classified according to different attributes of the services to obtain service types, for example, the services may be classified according to service sources, channel sources, or service contents to obtain service types corresponding to the services. When different processing parties of a service carry out butt joint of service data, firstly, service data corresponding to the service to be processed is obtained, and the service data can comprise service information such as a service source, a channel source, service content and main body data of the handled service and the like corresponding to the service. And identifying the service type corresponding to the service according to the service data, for example, according to the service source, the channel source or the service content, so as to obtain the service type corresponding to the service. For example, in the endowment insurance services, the endowment insurance services can be classified according to the regional classification of the region where the endowment insurance applicant is located, or can be classified according to the channel source of the endowment insurance as an online source or an offline source, or can be classified according to whether the endowment applicant transacts insurance services or post-sale services, or can be classified according to whether the insured applicant transacts insurance services or post-sale services, each type of endowment insurance has a corresponding flow for transacting services, and the corresponding service type of the insuring services can be described by an insuring mode code, so that different flows of services of different service types can be processed.
S13, according to the service type, obtaining a service processing workflow configuration corresponding to the service type, wherein the service processing workflow configuration is used for describing a processing flow for processing the service and preset component information of a preset component adopted by the processing flow, and the service processing workflow configuration comprises a component workflow corresponding to a component and a component identifier.
Specifically, when a service is processed in a service processing process, each realized function is developed in a component form, each component realizes a corresponding preset function, so that different functions are modularized, different components process service data according to a certain processing flow, and thus the service is processed, and the components may include a general component and a functional component realizing a specific function. For example, in the endowment insurance business, aiming at the insurance business, different components can be called through a standardized flow frame component, different functional components are connected in series to realize the processing of the business, the trial calculation function can also be realized through the trial calculation component, the insurance function is realized through the insurance component, the payment confirmation function is realized through the payment confirmation component, and each component can be repeatedly called in different business processing processes.
And configuring service processing workflow configuration corresponding to each service type according to service processing flows of different service types aiming at the service type of each service, so as to describe which preset components of the service types process the service data according to which preset processing sequence, and thus, the service processing is completed. For example, in the pension insurance application service, the preset payment confirmation component, the preset insurance component and the preset security confirmation component can be sequentially called through the preset standardized flow frame component according to the sequence to realize the payment confirmation function, the insurance function and the security confirmation function of the pension insurance application service, so that the treatment of the pension insurance application service is completed.
After identifying the service type corresponding to the service to be processed, acquiring the service processing workflow configuration corresponding to the service type according to the service type, where the service processing workflow configuration is used to describe a processing flow for processing the service and preset component information of preset components corresponding to the processing flow, that is, what preset components are to be used to process the service according to what processing order, so as to combine the processing flow of the service and the components to form the service processing workflow configuration corresponding to the service processing, where only the configuration information of the service processing workflow configuration corresponding to the service processing is described here, compared with the conventional technology, aiming at performing direct docking of service data between different processing parties in the service processing process, in the embodiment of the present application, in order to implement a complex docking scenario, the method comprises the steps of carrying out light-weight butt joint on service data, simplifying the complexity of a butt joint system, realizing the butt joint of the service data among different service processing parties, combining a service processing flow and components according to a service type corresponding to a service to form service processing workflow configuration corresponding to the service processing, and processing the service according to the service processing workflow configuration by a subsequent service processing party.
S14, sending the service data and the service processing workflow configuration to a preset service butt-joint party to butt-joint the service data to the preset service butt-joint party, so that the preset service butt-joint party processes the service according to the service data and the service processing workflow configuration.
Specifically, after acquiring the service processing workflow configuration corresponding to the service type according to the service type, sending the service data and the service processing workflow configuration to a preset service butt-joint party to butt-joint the service data to the preset service butt-joint party, so as to realize butt-joint of the service data among different service processing parties, so that the preset service butt-joint party processes the service, after receiving the service data and the service processing workflow configuration, the preset service butt-joint party calls a corresponding preset component according to a corresponding processing flow and a corresponding adopted preset component according to the service processing workflow configuration, constructs a processing flow for processing the service data, and processes the service data according to the processing flow, so as to realize processing the service, compared with the conventional technology, according to the embodiment of the application, through the combination of the preset assembly and the processing flow, the butt joint of the configuration of the business processing workflow is carried out among different processing parties of business, so that the lightweight butt joint under a complex butt joint scene is realized, the flexibility and the butt joint efficiency of a butt joint system are improved, and the problem that the business butt joint is more and more bloated and the problem of function overload are solved. For example, in the pension insurance service, the pension insurance service may include an external system and a core system, where the external system is configured to receive service data, the core system is configured to process the service data, the service data may be docked between the external system and the core system, when the service data is docked, after the external system drops the service data to the core system, the core system may capture the requested service data through an asynchronous task, capture the requested service data, query a workflow step after capturing the requested service data, obtain an SDK _ ID (i.e., a component request path, which may invoke a corresponding component through the component request path), obtain a specific function request path through the SDK _ ID, then assemble request parameters, evolve the request, generate an initial workflow, push the workflow after the request is completed, push the data to the next step, and so on until the underwriting is completed.
In the embodiment of the application, when data butt joint between different processing parties is realized in a service processing process, by acquiring service data corresponding to a service to be processed, identifying a service type corresponding to the service according to the service data, and acquiring service processing workflow configuration corresponding to the service type according to the service type, wherein the service processing workflow configuration is used for describing a processing flow for processing the service and preset component information adopting a preset component corresponding to the processing flow, the service data and the service processing workflow configuration are sent to a preset service butt joint party to butt joint the service data to the preset service butt joint party, so that the preset service butt joint party processes the service, and the service processing flow and the component are combined to form service processing workflow configuration corresponding to the service processing, and the configuration of the business processing workflow and the business data are sent to a preset business butt-joint party to realize data butt-joint between different business processing parties, and a subsequent business processing party processes the business according to the configuration of the business processing workflow, especially under the conditions of increased business and more bloated business butt-joint, compared with the prior art, aiming at the direct butt-joint of the business data between different business processing parties in the business processing process, the application is developed towards components, and simultaneously decouples the processing flow of the business processing from the functions of the components, improves the flexibility of the configuration of the business processing workflow corresponding to the business processing by fully utilizing the flexibility of the configuration of the processing flow, the flexibility of the development of the components and the repeated characteristic of the calling of the components, realizes the light butt-joint of the business data in a complex butt-joint scene, and simplifies the complexity of the data butt-joint between different business processing parties, the flexibility of data butt joint between different service processing parties is improved, so that the efficiency of service data butt joint is improved, the service can be quickly responded, the maintenance efficiency of a service processing system can also be improved, and the problems of more and more overstocked service butt joint and function overload are solved.
Referring to fig. 2, fig. 2 is a schematic sub-flow chart of a service data interfacing method according to an embodiment of the present application. As shown in fig. 2, in this embodiment, the step of acquiring service data corresponding to a service to be processed includes:
s21, acquiring service data corresponding to each of a plurality of services based on a preset data landing standard entrance, and temporarily storing the service data to obtain temporarily stored service data;
s22, responding to a trigger instruction for butting the service data, and acquiring the temporary storage service data to obtain the service data corresponding to the service to be processed.
Specifically, a unified data landing standard inlet is provided for external data aiming at a complex docking scene of a plurality of service data corresponding to a plurality of services, the data landing standard inlet comprises data landing standards such as a data naming standard, a data definition standard and a data type definition rule, docking is carried out according to the data landing standards strictly for different service docking, and therefore in the complex docking scene, a component workflow configuration corresponding to service processing is formed on the basis of combination of a unified service processing flow and a unified component, and lightweight docking of the complex docking scene is achieved. Meanwhile, for a plurality of service data corresponding to a plurality of services in a complex docking scene, batch processing can be performed on the service data at regular time according to a preset time period, so that the service data corresponding to each of the plurality of services is obtained based on a preset data landing standard entry, the service data is temporarily stored, after the temporarily stored service data is obtained, the temporarily stored service data is obtained in response to a trigger instruction for docking the service data, so that the service data corresponding to the service to be processed is obtained, light-weight docking of the plurality of services in the complex scene is realized, and the docking efficiency of the service data in the complex scene can be improved.
Referring to fig. 3, fig. 3 is a schematic view of a second sub-flow of a service data interfacing method according to an embodiment of the present application. As shown in fig. 3, in this embodiment, the step of obtaining, according to the service type, a service processing workflow configuration corresponding to the service type includes:
s31, acquiring component workflow configuration corresponding to the service type according to the service type, wherein the component workflow configuration comprises a processing step for processing the service data and a processing sequence corresponding to the processing step;
and S32, acquiring the preset component identifier corresponding to the processing step according to the processing step, acquiring the processing sequence corresponding to the preset component identifier according to the processing sequence corresponding to the processing step, so as to call the preset component corresponding to the preset component identifier according to the preset component identifier, and taking the preset component identifier and the processing sequence corresponding to the preset component identifier as the service processing workflow configuration.
Specifically, for each service corresponding to each service type, according to a process of processing the service, a component workflow configuration corresponding to the service is preset, where the component workflow configuration is used for describing steps of processing the service data and a sequence corresponding to each step, so that a service data processing party knows where components should be called according to the component workflow configuration and in what sequence to process the service data. For example, in the pension insurance application service, the component workflow corresponding to the application service processing process may be configured as follows: step one, payment confirmation is carried out; step two, performing the underwriting; and step three, security confirmation is carried out, meanwhile, which preset components are used for processing the processing step can be determined according to each processing step, so that corresponding preset components are called to process the service data, for example, in the endowment insurance application service, if corresponding payment confirmation components are arranged for payment confirmation, payment confirmation can be carried out according to the step one described in the component workflow, and the payment confirmation step can be determined to be processed by the payment confirmation components.
Acquiring a component workflow configuration corresponding to a service type according to the service type after acquiring the service type corresponding to the service, wherein the component workflow configuration comprises a processing step of processing the service data and a processing sequence corresponding to the processing step, acquiring a preset component identifier corresponding to the processing step according to the processing step so as to subsequently call a preset component corresponding to the preset component identifier according to the preset component identifier, wherein the processing sequence corresponding to the processing step is a processing sequence of processing the service data by using the preset component, namely a sequence of processing the service data by using the preset component, and according to the processing sequence corresponding to the processing step, acquiring a processing sequence corresponding to the preset component identifier and taking the processing sequence corresponding to the preset component identifier and the preset component identifier as the service processing workflow configuration And the subsequent service data processing parties respectively call the corresponding preset components to process the service data according to the processing sequence corresponding to the preset component identification, namely the processing flow for processing the service data.
Referring to fig. 4, fig. 4 is a schematic view of a third sub-flow of a service data docking method according to an embodiment of the present application. As shown in fig. 4, in this embodiment, before the step of obtaining, according to the service type, a component workflow configuration corresponding to the service type, the method further includes:
s41, responding to a configuration instruction for configuring the component workflow corresponding to the service type, and displaying a preset component workflow configuration mode so that a configuration worker can select the preset component workflow configuration corresponding to the service type according to the service type;
s42, receiving preset component workflow configuration corresponding to the service type, and storing the service type and the preset component workflow configuration corresponding to the service type, so as to obtain component workflow configuration corresponding to the service type according to the preset component workflow configuration in the following.
Specifically, for a service type requiring configuration of component workflow configuration, no matter a new service type or an old service component workflow configuration is updated, the component workflow configuration may be set through a preset component workflow configuration mode, the content of the preset component workflow configuration mode may include a service type, a configuration name and a configuration code of the component workflow configuration corresponding to the service type, and a configuration identifier included in the component workflow configuration, and the specific content may be used to describe which steps are performed on service data and which components perform corresponding steps. For example, in the pension insurance service, whenever a new service type comes, a configurator may first perform service type maintenance on a counter, such as a new added insurance service, and the counter maintains an existing mode in which the service is going, such as selecting an existing benchmark policy division mode or a normal mode for configuration, or may newly establish a corresponding component workflow configuration mode, and then configure the newly established component workflow configuration mode, and then select contents included in the newly established component workflow configuration mode, such as a channel source, a service source, and components corresponding to processing steps and processing steps (which may be described in the form of a function ID or SDK-ID) included in the newly established component workflow configuration mode, and click to save when the insurance mode of the new service type is determined, and when the background subsequently processes the service of the new service type, generating a component step workflow according to the underwriting mode of the new service type.
Further, if some services have special function requirements, an SDK tool set can be newly added, the newly added SDK tool set is configured in component workflow configuration corresponding to the service type, a request path of the newly added SDK tool set is configured in a preset function component configuration table corresponding to the SDK, and the newly added SDK tool set can be called subsequently according to the service processing workflow configuration, so that the configuration flexibility of the component workflow configuration can be improved. For example, in the pension insurance service, when a configurator configures an underwriting mode, a newly added component workflow can be selected, sdk _ id corresponding to the newly added component workflow is selected, a set of complete underwriting workflow is configured and stored in the component workflow table, and then a corresponding underwriting flow can be realized according to the newly added component workflow, so that the requirements of processing flows of different service types can be met, functions and flows are decoupled, and the flexibility of service processing flow configuration is improved.
Referring to fig. 5, fig. 5 is a schematic view of a fourth sub-flow of the service data docking method according to the embodiment of the present application. As shown in fig. 5, in this embodiment, the step of obtaining, according to the service type, a component workflow configuration corresponding to the service type includes:
s51, determining a preset component workflow configuration table corresponding to the service type according to the service type;
s52, obtaining the component workflow configuration corresponding to the service type according to the preset component workflow configuration table.
Specifically, for a plurality of services corresponding to a plurality of service types, the component workflow configuration corresponding to each service type may be described by a preset component workflow configuration table, and a preset component identifier corresponding to the same preset component may be configured as different workflow steps in different component workflow configurations. The configuration table of the preset component workflow may also be multiple, and particularly, for a situation where multiple configuration tables of the preset component workflow exist, after a service type corresponding to a service is obtained, the configuration table of the preset component workflow corresponding to the service type is determined according to the service type, and then the configuration of the component workflow corresponding to the service type is obtained from the configuration table of the preset component workflow according to the service type and the configuration table of the preset component workflow. For example, in the application service, various modes of the underwriting process are configured in the component workflow table in advance, and the table includes workflow function calling orders of a standard policy division mode, a common standard mode, and the like, such as: the normal standard mode step one configures trial calculation sdk _ id, the step two configures underwriting sdk _ id, the step three pays confirmation sdk _ id, and the step four underwriting sdk _ id.
Referring to fig. 6, fig. 6 is a fifth sub-flow diagram of a service data docking method according to an embodiment of the present application. As shown in fig. 6, in this embodiment, the step of acquiring, according to the processing step, the preset component identifier corresponding to the processing step includes:
s61, determining a preset functional component configuration table corresponding to the processing step according to the processing step;
and S62, acquiring the preset component identification corresponding to the processing step according to the preset functional component configuration table.
Specifically, for a plurality of services corresponding to a plurality of service types, in a case that the services include a plurality of components, component information corresponding to each component may be described through a preset functional component configuration table, where the component information includes component functions, the component functions may be described by function IDs, the component functions are used to describe what functions the preset components are used to implement, the component functions corresponding to the components may be described by keywords, and the function IDs are used to describe function positions of the components implementing the functions, so that the corresponding components can be called according to the function positions in the following. For example, in the pension insurance service, common functions, such as a trial calculation function, an underwriting function, and a payment confirmation function, may be found out component information corresponding to a component that implements the trial calculation function through the trial calculation function ID, may be found out component information corresponding to a component that implements the underwriting function through the underwriting function ID, and may store the function ID and a corresponding component request path (which may be described by SDK _ ID) in a preset function component configuration table, and each component may be packaged with an SDK, each component SDK corresponds to one corresponding SDK _ ID, and invoking the corresponding component may be implemented through the SDK _ ID.
The preset functional component configuration table may be multiple, and particularly, for a situation where multiple preset functional component configuration tables exist, after a processing step corresponding to a service is obtained, according to the processing step, the preset functional component configuration table corresponding to the processing step is determined, then according to the processing step and the preset functional component configuration table, a preset component identifier corresponding to the processing step is obtained from the preset functional component configuration table, so that a preset component corresponding to the preset component identifier is called subsequently according to the preset component identifier, and the service data is processed by using the preset component, so that a processing flow corresponding to the service data is established according to a service processing workflow configuration corresponding to the service type, and the service data is processed.
Referring to fig. 7, fig. 7 is a fifth sub-flow diagram of a service data docking method according to an embodiment of the present application. As shown in fig. 7, in this embodiment, the step of acquiring the preset component identifier corresponding to the processing step according to the preset functional component configuration table includes:
s71, acquiring a preset function ID corresponding to the processing step;
and S72, acquiring a preset component request path corresponding to the preset function ID from the preset function component configuration table according to the preset function ID, so as to obtain a preset component identifier corresponding to the processing step.
Specifically, the processing step of processing the service data is described in a preset component workflow configuration table, where the processing step is used to describe what processing is performed on the service data and what function is correspondingly implemented, for example, in an endowment insurance application service, payment confirmation processing, underwriting processing, or security confirmation processing needs to be performed on the service data to respectively and correspondingly implement a payment confirmation function, an underwriting function, and a security confirmation function, and at the same time, where the processing step corresponding to what processing is performed on the service data is to obtain a component implementing the corresponding function can be described by using a preset function ID, so that the processing step and the preset function ID are associated, and the preset function ID corresponding to the processing step can be obtained according to the processing step.
In the preset functional component configuration table, component identifiers corresponding to the clear implementation of corresponding functions are described, the functions can be described by function IDs, and the component identifiers can be described by unique identifiers of components such as component request paths and the like, so that the preset component workflow configuration table is associated with the preset functional component configuration table, the clear implementation of the processing step where to request the corresponding components is described, the functions corresponding to the processing step are implemented, and the business data is processed. Thus, in a preset component workflow configuration table, the preset function ID corresponding to the processing step is obtained, and then in a preset function component configuration table, according to the preset function ID, a preset component request path corresponding to the preset function ID is obtained from the preset function component configuration table, so that the preset component identifier corresponding to the processing step can be obtained.
It should be noted that, the service data docking method described in each of the above embodiments may recombine the technical features included in different embodiments as needed to obtain the combined implementation, but all of them are within the protection scope claimed in the present application.
Referring to fig. 8, fig. 8 is a schematic block diagram of a service data interfacing apparatus according to an embodiment of the present application. Corresponding to the service data docking method, the embodiment of the present application further provides a service data docking device. As shown in fig. 8, the service data interfacing apparatus includes a unit for performing the service data interfacing method described above, and the service data interfacing apparatus may be configured in a computer device. Specifically, referring to fig. 8, the service data docking apparatus 80 includes a first obtaining unit 81, a recognition unit 82, a second obtaining unit 83, and a docking unit 84.
The first obtaining unit 81 is configured to obtain service data corresponding to a service to be processed;
an identifying unit 82, configured to identify, according to the service data, a service type corresponding to the service;
a second obtaining unit 83, configured to obtain, according to the service type, a service processing workflow configuration corresponding to the service type, where the service processing workflow configuration is used to describe a processing flow for processing the service and preset component information of a preset component adopted by the processing flow;
a docking unit 84, configured to send the service data and the service processing workflow configuration to a preset service dockee, so as to dock the service data to the preset service dockee, so that the preset service dockee processes the service according to the service data and the service processing workflow configuration.
In an embodiment, the first obtaining unit 81 includes:
the first acquiring subunit is used for acquiring service data corresponding to each of a plurality of services based on a preset data landing standard inlet, and temporarily storing the service data to obtain temporarily stored service data;
and the response subunit is used for responding to a trigger instruction for butting the service data, and acquiring the temporary storage service data so as to obtain the service data corresponding to the service to be processed.
In an embodiment, the second obtaining unit 83 includes:
a second obtaining subunit, configured to obtain, according to the service type, a component workflow configuration corresponding to the service type, where the component workflow configuration includes a processing step of processing the service data and a processing sequence corresponding to the processing step;
and the third obtaining subunit is configured to obtain the preset component identifier corresponding to the processing step according to the processing step, obtain the processing sequence corresponding to the preset component identifier according to the processing sequence corresponding to the processing step, and use the preset component identifier and the processing sequence corresponding to the preset component identifier as the configuration of the service processing workflow.
In an embodiment, the second obtaining unit 83 further includes:
the display subunit is used for responding to a configuration instruction for configuring the component workflow corresponding to the service type, and displaying a preset component workflow configuration mode so that a configuration worker can select the preset component workflow configuration corresponding to the service type according to the service type;
and the receiving subunit is used for receiving the preset component workflow configuration corresponding to the service type and storing the service type and the preset component workflow configuration corresponding to the service type.
In one embodiment, the second acquiring subunit includes:
the first determining subunit is configured to determine, according to the service type, a preset component workflow configuration table corresponding to the service type;
and the fourth obtaining subunit is configured to obtain, according to the preset component workflow configuration table, the component workflow configuration corresponding to the service type.
In one embodiment, the third acquiring subunit includes:
the second determining subunit is configured to determine, according to the processing step, a preset functional component configuration table corresponding to the processing step;
and a fifth obtaining subunit, configured to obtain, according to the preset functional component configuration table, the preset component identifier corresponding to the processing step.
In an embodiment, the fifth acquiring subunit includes:
a sixth obtaining subunit, configured to obtain a preset function ID corresponding to the processing step;
a seventh obtaining subunit, configured to obtain, according to the preset function ID, a preset component request path corresponding to the preset function ID from the preset function component configuration table, so as to obtain a preset component identifier corresponding to the processing step.
It should be noted that, as can be clearly understood by those skilled in the art, the specific implementation processes of the service data docking device and each unit may refer to the corresponding descriptions in the foregoing method embodiments, and for convenience and brevity of description, no further description is provided herein.
Meanwhile, the division and connection manner of each unit in the service data docking device are only used for illustration, in other embodiments, the service data docking device may be divided into different units as needed, and each unit in the service data docking device may also adopt different connection sequences and manners to complete all or part of the functions of the service data docking device.
The service data interfacing means may be implemented in the form of a computer program which can be run on a computer device as shown in fig. 9.
Referring to fig. 9, fig. 9 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 may be a computer device such as a desktop computer or a server, or may be a component or part of another device.
Referring to fig. 9, the computer device 500 includes a processor 502, a memory, which may include a non-volatile storage medium 503 and an internal memory 504, which may also be a volatile storage medium, and a network interface 505 connected by a system bus 501.
The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer program 5032, when executed, may cause the processor 502 to perform one of the above-described service data interfacing methods.
The processor 502 is used to provide computing and control capabilities to support the operation of the overall computer device 500.
The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503, and when the computer program 5032 is executed by the processor 502, the processor 502 can be enabled to execute a service data interfacing method as described above.
The network interface 505 is used for network communication with other devices. Those skilled in the art will appreciate that the configuration shown in fig. 9 is a block diagram of only a portion of the configuration associated with the present application and does not constitute a limitation of the computer device 500 to which the present application may be applied, and that a particular computer device 500 may include more or less components than those shown, or may combine certain components, or have a different arrangement of components. For example, in some embodiments, the computer device may only include a memory and a processor, and in such embodiments, the structures and functions of the memory and the processor are consistent with those of the embodiment shown in fig. 9, and are not described herein again.
Wherein the processor 502 is configured to run the computer program 5032 stored in the memory to implement the following steps: acquiring service data corresponding to a service to be processed; identifying a service type corresponding to the service according to the service data; acquiring service processing workflow configuration corresponding to the service type according to the service type, wherein the service processing workflow configuration is used for describing a processing flow for processing the service and preset component information of a preset component adopted by the processing flow; and sending the service data and the service processing workflow configuration to a preset service butt-joint party to butt-joint the service data to the preset service butt-joint party, so that the preset service butt-joint party processes the service according to the service data and the service processing workflow configuration.
In an embodiment, when the processor 502 implements the step of obtaining the service data corresponding to the service to be processed, the following steps are specifically implemented:
acquiring service data corresponding to each of a plurality of services based on a preset data landing standard inlet, and temporarily storing the service data to obtain temporarily stored service data;
and responding to a trigger instruction for butting the service data, and acquiring the temporary storage service data to obtain the service data corresponding to the service to be processed.
In an embodiment, when the processor 502 implements the step of obtaining the service processing workflow configuration corresponding to the service type according to the service type, the following steps are specifically implemented:
acquiring component workflow configuration corresponding to the service type according to the service type, wherein the component workflow configuration comprises a processing step of processing the service data and a processing sequence corresponding to the processing step;
and acquiring a preset component identifier corresponding to the processing step according to the processing step, acquiring a processing sequence corresponding to the preset component identifier according to the processing sequence corresponding to the processing step, and taking the preset component identifier and the processing sequence corresponding to the preset component identifier as the service processing workflow configuration.
In an embodiment, before implementing the step of obtaining, according to the service type, the component workflow configuration corresponding to the service type, the processor 502 further implements the following steps:
responding to a configuration instruction for configuring component workflows corresponding to the service types, and displaying a preset component workflow configuration mode so that a configuration worker can select the preset component workflow configuration corresponding to the service types according to the service types;
receiving preset component workflow configuration corresponding to the service type, and storing the service type and the preset component workflow configuration corresponding to the service type.
In an embodiment, when the processor 502 implements the step of obtaining the component workflow configuration corresponding to the service type according to the service type, the following steps are specifically implemented:
determining a preset component workflow configuration table corresponding to the service type according to the service type;
and acquiring the component workflow configuration corresponding to the service type according to the preset component workflow configuration table.
In an embodiment, when the processor 502 implements the step of obtaining the preset component identifier corresponding to the processing step according to the processing step, the following steps are specifically implemented:
determining a preset functional component configuration table corresponding to the processing step according to the processing step;
and acquiring a preset component identifier corresponding to the processing step according to the preset functional component configuration table.
In an embodiment, when the processor 502 implements the step of obtaining the preset component identifier corresponding to the processing step according to the preset functional component configuration table, the following steps are specifically implemented:
acquiring a preset function ID corresponding to the processing step;
and acquiring a preset component request path corresponding to the preset function ID from the preset function component configuration table according to the preset function ID so as to obtain a preset component identifier corresponding to the processing step.
It should be understood that in the embodiment of the present Application, the Processor 502 may be a Central Processing Unit (CPU), and the Processor 502 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will be understood by those skilled in the art that all or part of the processes in the method for implementing the above embodiments may be implemented by a computer program, and the computer program may be stored in a computer readable storage medium. The computer program is executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.
Accordingly, the present application also provides a computer-readable storage medium. The computer-readable storage medium may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium, the computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the steps of:
a computer program product which, when run on a computer, causes the computer to perform the steps of the business data interfacing method described in the embodiments above.
The computer readable storage medium may be an internal storage unit of the aforementioned device, such as a hard disk or a memory of the device. The computer readable storage medium may also be an external storage device of the device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. provided on the device. Further, the computer-readable storage medium may also include both an internal storage unit and an external storage device of the apparatus.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses, devices and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The storage medium is an entity and non-transitory storage medium, and may be various entity storage media capable of storing computer programs, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. 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 application.
In the several 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. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.
The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the application can be combined, divided and deleted according to actual needs. In addition, functional units in the embodiments of the present application 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 integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing an electronic device (which may be a personal computer, a terminal, or a network device) to perform all or part of the steps of the method according to the embodiments of the present application.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present application, and these modifications or substitutions should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A service data interfacing method is characterized by comprising the following steps:
acquiring service data corresponding to a service to be processed;
identifying a service type corresponding to the service according to the service data;
acquiring service processing workflow configuration corresponding to the service type according to the service type, wherein the service processing workflow configuration is used for describing a processing flow for processing the service and preset component information of a preset component adopted by the processing flow;
and sending the service data and the service processing workflow configuration to a preset service butt-joint party to butt-joint the service data to the preset service butt-joint party, so that the preset service butt-joint party processes the service according to the service data and the service processing workflow configuration.
2. The service data docking method according to claim 1, wherein the step of obtaining the service data corresponding to the service to be processed comprises:
acquiring service data corresponding to each of a plurality of services based on a preset data landing standard inlet, and temporarily storing the service data to obtain temporarily stored service data;
and responding to a trigger instruction for butting the service data, and acquiring the temporary storage service data to obtain the service data corresponding to the service to be processed.
3. The service data docking method according to claim 1, wherein the step of obtaining, according to the service type, the service processing workflow configuration corresponding to the service type includes:
acquiring component workflow configuration corresponding to the service type according to the service type, wherein the component workflow configuration comprises a processing step of processing the service data and a processing sequence corresponding to the processing step;
and acquiring a preset component identifier corresponding to the processing step according to the processing step, acquiring a processing sequence corresponding to the preset component identifier according to the processing sequence corresponding to the processing step, and taking the preset component identifier and the processing sequence corresponding to the preset component identifier as the service processing workflow configuration.
4. The service data docking method according to claim 3, wherein before the step of obtaining the component workflow configuration corresponding to the service type according to the service type, the method further comprises:
responding to a configuration instruction for configuring component workflows corresponding to the service types, and displaying a preset component workflow configuration mode so that a configuration worker can select the preset component workflow configuration corresponding to the service types according to the service types;
receiving preset component workflow configuration corresponding to the service type, and storing the service type and the preset component workflow configuration corresponding to the service type.
5. The service data docking method according to claim 3 or 4, wherein the step of obtaining the component workflow configuration corresponding to the service type according to the service type includes:
determining a preset component workflow configuration table corresponding to the service type according to the service type;
and acquiring the component workflow configuration corresponding to the service type according to the preset component workflow configuration table.
6. The service data docking method according to claim 3 or 4, wherein the step of acquiring the preset component identifier corresponding to the processing step according to the processing step includes:
determining a preset functional component configuration table corresponding to the processing step according to the processing step;
and acquiring a preset component identifier corresponding to the processing step according to the preset functional component configuration table.
7. The service data docking method according to claim 6, wherein the step of obtaining the preset component identifier corresponding to the processing step according to the preset functional component configuration table includes:
acquiring a preset function ID corresponding to the processing step;
and acquiring a preset component request path corresponding to the preset function ID from the preset function component configuration table according to the preset function ID so as to obtain a preset component identifier corresponding to the processing step.
8. A service data interfacing apparatus, comprising:
the first acquisition unit is used for acquiring service data corresponding to a service to be processed;
the identification unit is used for identifying the service type corresponding to the service according to the service data;
a second obtaining unit, configured to obtain, according to the service type, a service processing workflow configuration corresponding to the service type, where the service processing workflow configuration is used to describe a processing flow for processing the service and preset component information of a preset component adopted by the processing flow;
and the docking unit is used for sending the service data and the service processing workflow configuration to a preset service docking party so as to dock the service data to the preset service docking party, so that the preset service docking party processes the service according to the service data and the service processing workflow configuration.
9. A computer device, comprising a memory and a processor coupled to the memory; the memory is used for storing a computer program; the processor is adapted to run the computer program to perform the steps of the method according to any of claims 1-7.
10. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when being executed by a processor, realizes the steps of the method according to any one of claims 1 to 7.
CN202110088385.1A 2021-01-22 2021-01-22 Business data docking method and device, computer equipment and storage medium Pending CN112799714A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110088385.1A CN112799714A (en) 2021-01-22 2021-01-22 Business data docking method and device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110088385.1A CN112799714A (en) 2021-01-22 2021-01-22 Business data docking method and device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112799714A true CN112799714A (en) 2021-05-14

Family

ID=75811189

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110088385.1A Pending CN112799714A (en) 2021-01-22 2021-01-22 Business data docking method and device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112799714A (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105844422A (en) * 2016-04-01 2016-08-10 阿里巴巴集团控股有限公司 Business flow execution method and device
CN109726018A (en) * 2018-02-07 2019-05-07 中国平安财产保险股份有限公司 Method for processing business, device, equipment and computer readable storage medium
CN110413286A (en) * 2019-07-31 2019-11-05 阿里巴巴集团控股有限公司 A kind of application dispositions method, device and equipment
CN110704095A (en) * 2019-09-03 2020-01-17 深圳壹账通智能科技有限公司 Workflow-based configuration processing method and device, computer equipment and storage medium
CN111064621A (en) * 2019-12-25 2020-04-24 南京三百云信息科技有限公司 Service data docking method and device
CN111104182A (en) * 2019-12-17 2020-05-05 深圳前海环融联易信息科技服务有限公司 Method and device for quickly arranging business based on componentization, computer equipment and storage medium
CN111221793A (en) * 2019-12-31 2020-06-02 新华网股份有限公司 Data mining method, platform, computer equipment and storage medium
CN111861718A (en) * 2020-07-24 2020-10-30 招商局通商融资租赁有限公司 Data processing method, server and storage medium based on collaboration platform

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105844422A (en) * 2016-04-01 2016-08-10 阿里巴巴集团控股有限公司 Business flow execution method and device
CN109726018A (en) * 2018-02-07 2019-05-07 中国平安财产保险股份有限公司 Method for processing business, device, equipment and computer readable storage medium
CN110413286A (en) * 2019-07-31 2019-11-05 阿里巴巴集团控股有限公司 A kind of application dispositions method, device and equipment
CN110704095A (en) * 2019-09-03 2020-01-17 深圳壹账通智能科技有限公司 Workflow-based configuration processing method and device, computer equipment and storage medium
CN111104182A (en) * 2019-12-17 2020-05-05 深圳前海环融联易信息科技服务有限公司 Method and device for quickly arranging business based on componentization, computer equipment and storage medium
CN111064621A (en) * 2019-12-25 2020-04-24 南京三百云信息科技有限公司 Service data docking method and device
CN111221793A (en) * 2019-12-31 2020-06-02 新华网股份有限公司 Data mining method, platform, computer equipment and storage medium
CN111861718A (en) * 2020-07-24 2020-10-30 招商局通商融资租赁有限公司 Data processing method, server and storage medium based on collaboration platform

Similar Documents

Publication Publication Date Title
CN108346028B (en) Business approval processing method, device and system
CN112132548A (en) Approval transfer method and device, electronic equipment and storage medium
CN111507674B (en) Task information processing method, device and system
CN109933626B (en) Financial business data processing method and device and financial transaction terminal
CN110880100A (en) Business approval processing method, device and system
CN112035344A (en) Multi-scenario test method, device, equipment and computer readable storage medium
US10318612B2 (en) System and method for implementing screen capture
CN105005481A (en) Method and system for processing workflow to-do task
CN111539683A (en) Contract signing method, device, equipment and medium
CN111190750A (en) Data processing method and system
CN110532810B (en) Information processing method and device, electronic equipment and readable storage medium
CN112799714A (en) Business data docking method and device, computer equipment and storage medium
US7370010B2 (en) Automated semi-deterministic trading system
CN111651494A (en) Data processing method, device, equipment and computer readable storage medium
CN111522617A (en) Method and device for maintaining system and electronic equipment
CN110941658A (en) Data export method, device, server and storage medium
CN112950191A (en) Service data processing method and device based on fee refunding service and computer equipment
CN115358761A (en) After-sale processing method and device, after-sale processing equipment and storage medium
CN114971785A (en) Order processing method and device, electronic equipment and storage medium
CN102981889A (en) Virtual machine creating method and device for virtual machine creation
CN114036250A (en) High-precision map task processing method and device, electronic equipment and medium
CN113312190A (en) Cooperative processing method and device for government affair service business
CN112650911A (en) Service message issuing method, device, computer equipment and storage medium
CN112650598A (en) Multi-application access method for workflow system
CN113516523A (en) Order data processing method and order receiving system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination