Data transmission device and service processing system in butt joint with different manufacturer systems

Abstract

The invention provides a data transmission device in butt joint with different manufacturer systems and a service processing system. First configuration information for acquiring service data from a third-party manufacturer system and second configuration information for sending the service data to the third-party manufacturer system are configured in a configuration module of the device; the service data acquisition module acquires current service data provided by a third-party manufacturer system through a docking interface of the service docking scene; performing parameter conversion on the current business data by adopting a first interface parameter conversion rule to obtain business data meeting a business processing system data standard; and the service data sending module is used for carrying out parameter conversion on the service data to be sent by adopting a second interface parameter conversion rule aiming at any service data model to obtain the service data meeting the data standard of the third-party manufacturer system, and sending the service data to the third-party manufacturer system. According to the device, the online docking cost can be reduced, the customization development cost is reduced, and the online delivery efficiency is improved.

Description

Technical Field

[0001] This application relates to the technical field of data processing. Specifically, it relates to a data transmission device and a service processing system for docking systems of different manufacturers. Background Art

[0002] During the system go-live process, it is necessary to dock with multiple upstream and downstream systems. At different customer sites, the upstream and downstream system manufacturers may be different, and the docking interfaces provided by different manufacturers are also different, without a unified interface standard. Facing a wide variety of third-party interfaces, if the method of customized development is used to adapt the interfaces, it will be necessary to customize and develop the interface docking part for each site. The development cycle and go-live cycle will be lengthened, and the interface docking parts are not universal across sites. It is necessary to pull independent site branches, with one version for each site, increasing the complexity of version maintenance and going against the original intention of system productization.

[0003] Currently, the most commonly used docking method is database storage docking. By modifying the docking storage script at the customer site, the docking of the three-party systems is achieved. The disadvantage is that it cannot cover all docking scenarios. In many cases, a combination of database storage and customized development is required to achieve docking. If an exception occurs in the script, it will directly lead to abnormal system docking, affecting the normal flow of the business process, and the difficulty of troubleshooting exceptions is also relatively large.

[0004] It can be seen that the existing docking methods have problems such as high go-live docking costs, low reuse rate, low stability, and great difficulty in troubleshooting exceptions. Summary of the Invention

[0005] The purpose of the embodiments of this application is to provide a data transmission device and a service processing system for docking systems of different manufacturers, which can reduce the go-live docking cost, reduce the customized development cost, achieve a zero-development level, support configuration reuse between sites, and improve the go-live delivery efficiency.

[0006] In a first aspect, a data transmission device for docking systems of different manufacturers is provided. The device may include:

[0007] A configuration module, configured to configure first configuration information for obtaining service data from a third-party manufacturer's system and second configuration information for sending service data to the third-party manufacturer's system; the first configuration information includes: the business docking scenarios of the docking interface and the first interface parameter conversion rules for the corresponding scenarios; wherein, the business scope of the interface is summarized as the business docking scenarios of the interface; the second configuration information includes: the service data models involved in the docking interface and the second interface parameter conversion rules for the corresponding service data models;

[0008] A business data acquisition module, which is used for any business docking scenario. Through the docking interface of the business docking scenario, using the full upstream business data of the docking scenario as the parameters of the docking interface, and adopting the first interface parameter conversion rule to perform parameter conversion, a parameter model that meets the parameter standards of the third-party manufacturer's system is obtained, and the current business data provided by the third-party manufacturer's system is acquired;

[0009] A business data sending module, which is used for any business data model. Adopting the second interface parameter conversion rule, the business data to be sent is parameter-converted to obtain business data that meets the data standards of the third-party manufacturer's system, and is sent to the third-party manufacturer's system. The second interface parameter conversion rule is used to convert the sending result feedback by the third-party manufacturer's system to obtain a sending result recognizable by the business processing system.

[0010] In a possible implementation, the configuration module is specifically used to receive, through a visual configuration interface, the interface configuration information of different third-party manufacturer's systems input, and parse the received interface configuration information of each third-party manufacturer's system to obtain the input parameter data model and the output parameter data model of the business processing system with respect to each third-party manufacturer's system;

[0011] Based on the input parameter data model and the output parameter data model of the business processing system with respect to each third-party manufacturer's system, the first interface parameter conversion rule and the second interface parameter conversion rule of the corresponding docking interface are configured; wherein, the input parameter data model and the output parameter data model of the business processing system are data models that meet the data standards of the business processing system.

[0012] In a possible implementation, for the first interface parameter conversion rule, the input parameter data model of the docking interface is the full upstream business data of the corresponding business docking scenario. The input parameter model is converted by the first interface parameter conversion rule into a parameter model that meets the parameter standards of the third-party manufacturer's system, and the output parameter data model is the expected target data of the corresponding business docking scenario;

[0013] For the second interface parameter conversion rule, the input parameter data model of the docking interface is the full business data of the business processing system of the corresponding business data model, and the output parameter data model is the expected target data of the third-party manufacturer's system of the corresponding business data model.

[0014] In a possible implementation, the configuration module is further used to configure the interface docking timing of each business data model;

[0015] The business data sending module is further used for any business data model to detect whether the interface docking timing of the business data model is met;

[0016] If it is satisfied, the second interface parameter conversion rule is adopted to perform parameter conversion on the service data to be sent, so as to obtain service data that meets the data standard of the third-party manufacturer's system, and send it to the third-party manufacturer's system. The second interface parameter conversion rule is used to convert the sending result feedback by the third-party manufacturer's system to obtain a sending result recognizable by the service processing system.

[0017] If it is not satisfied, the service data to be sent corresponding to the service data model is rejected from being sent.

[0018] In a possible implementation, the configuration module is further configured to receive, through a visual configuration interface, the data sending condition for any service data model;

[0019] The service data sending module is further configured to detect, for any service data model, whether the data sending condition of the service data model is satisfied;

[0020] If it is satisfied, the second interface parameter conversion rule is adopted to perform parameter conversion on the service data to be sent that meets the data sending condition, so as to obtain service data that meets the data standard of the third-party manufacturer's system, and send it to the third-party manufacturer's system. The second interface parameter conversion rule is used to convert the sending result feedback by the third-party manufacturer's system to obtain a sending result recognizable by the service processing system.

[0021] If it is not satisfied, the service data to be sent that meets the data sending condition is rejected from being sent.

[0022] In a possible implementation, the configuration module is further configured to configure new first configuration information and second configuration information according to the interface information of the new third-party manufacturer's system to be docked.

[0023] In a possible implementation, the interface types of the docking interface include: DATABASE type, WEBAPI type, WEBSERVICE type, and FTP type.

[0024] In a second aspect, a service processing system is provided, and the system may include:

[0025] A processor and the data transmission device for docking different manufacturer systems in any of the first aspects;

[0026] The processor is configured to send service data to the data transmission device for docking different manufacturer systems, and obtain service data from the data transmission device for docking different manufacturer systems.

[0027] In a third aspect, an electronic device is provided, and the electronic device includes a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete communication with each other through the communication bus;

[0028] A memory for storing a computer program;

[0029] A processor, when executing the program stored in the memory, implements any of the method steps described in the first aspect above.

[0030] In a fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements any of the method steps described in the first aspect above.

[0031] A data transmission device for docking systems of different manufacturers provided by an embodiment of the present application. The configuration module in the device obtains first configuration information for obtaining service data from a third-party manufacturer's system and second configuration information for sending service data to the third-party manufacturer's system; the first configuration information includes: the service docking scenario of the docking interface and the first interface parameter conversion rule for the corresponding scenario; the service scope of the interface is summarized as the service docking scenario of the interface; the second configuration information includes: the service data model involved in the docking interface and the second interface parameter conversion rule for the corresponding service data model; the service data acquisition module, for any service docking scenario, through the docking interface of the service docking scenario, uses the full upstream service data of the docking scenario as the parameter of the docking interface, and performs parameter conversion using the first interface parameter conversion rule to obtain a parameter model that meets the parameter standard of the third-party manufacturer's system, and obtains the current service data provided by the third-party manufacturer's system; the service data sending module, for any service data model, uses the second interface parameter conversion rule to perform parameter conversion on the service data to be sent, obtains service data that meets the data standard of the third-party manufacturer's system, and sends it to the third-party manufacturer's system. This device can reduce the online docking cost, reduce the customized development cost, achieve a zero development level, support the configuration reuse between different sites, and improve the online delivery efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings required to be used in the embodiments of the present application. It should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as limiting the scope. For those of ordinary skill in the art, without creative efforts, other related drawings can be obtained based on these drawings.

[0033] Figure 1 It is a schematic structural diagram of a data transmission device for docking systems of different manufacturers provided by an embodiment of the present application. DETAILED DESCRIPTION

[0034] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0035] The preferred embodiments of the present application will be described below with reference to the accompanying drawings of the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. And without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

[0036] The data transmission device for systems of different manufacturers provided by the embodiments of the present application can be set in the service processing system. The system can also include a processor, which is used to send service data to the data transmission device for docking systems of different manufacturers and obtain service data from the data transmission device for docking systems of different manufacturers. Among them, the data transmission device can propose the "Intelligent Docking Solution without Development for Systems of Different Manufacturers" to address the problems of a large variety of tripartite interface types and a long customized development cycle at different customer sites. Through visual configuration, intelligent parsing of tripartite system interface data is completed, all tripartite interfaces are configured and productized, the online docking cost is reduced, the customized development cost is reduced, the development degree reaches 0, configuration reuse between sites is supported, and the online delivery efficiency is improved.

[0037] As Figure 1 shown, the device can include: a configuration module, a service data acquisition module, and a service data sending module.

[0038] The configuration module acquires the first configuration information for acquiring service data from the third-party manufacturer's system and the second configuration information for sending service data to the third-party manufacturer's system.

[0039] The first configuration information can include: the service docking scenario of the docking interface and the first interface parameter conversion rule for the corresponding scenario; wherein, the service scope of the interface is summarized as the service docking scenario of the interface; the second configuration information includes: the service data model involved in the docking interface and the second interface parameter conversion rule for the corresponding service data model. The service docking scenario refers to the service scenario where service data docking needs to be performed.

[0040] The service data acquisition module is used for any service docking scenario, through the docking interface of the service docking scenario, using the full upstream service data of the docking scenario as the parameter of the docking interface, performing parameter conversion using the first interface parameter conversion rule, obtaining a parameter model that meets the parameter standard of the third-party manufacturer's system, and acquiring the current service data provided by the third-party manufacturer's system.

[0041] The business data acquisition module can focus on the actual business scenarios of the business processing system, classify the business scope of the interfaces to be docked into determined scenarios, take the scenarios as the entry points, and dispatch the interfaces for data flow through designing the input and output data models and setting the conversion relationships;

[0042] The same scenario can include the docking of one or more third-party vendor system interfaces, which can be flexibly combined according to the third-party vendor system interfaces to achieve the maximum compatibility with the third-party vendor system interfaces.

[0043] The business data sending module is used to perform parameter conversion on the business data to be sent for any business data model by adopting the second interface parameter conversion rule to obtain the business data that meets the data standards of the third-party vendor system, and send it to the third-party vendor system.

[0044] Based on the business data model of the business processing system, the business data sending module can be sent to the third-party vendor system in the form of a scheduled task according to the set conversion relationships and docking timings;

[0045] The same scheduled task can include the docking of one or more third-party vendor system interfaces, which can be flexibly combined according to the third-party vendor system interfaces to achieve the maximum compatibility with the third-party vendor system interfaces.

[0046] It should be noted that the configuration module, the business data acquisition module, and the business data sending module can all be implemented by software, or there can be independent modules, such as chip implementation, which is not limited in this application.

[0047] In some embodiments, the configuration module is specifically used to receive the interface configuration information of different third-party vendor systems through a visual configuration interface, and parse the received interface configuration information of each third-party vendor system to obtain the input data model and output data model of the business processing system with respect to each third-party vendor system;

[0048] Based on the input data model and output data model of the business processing system with respect to each third-party vendor system, configure the first interface parameter conversion rule and the second interface parameter conversion rule of the corresponding docking interface; wherein, the input data model and output data model of the business processing system are data models that meet the data standards of the business processing system.

[0049] Furthermore, for the first interface parameter conversion rule, the input data model of the docking interface is the full upstream business data of the corresponding business docking scenario, and the output data model is the expected target data of the corresponding business docking scenario;

[0050] For the second interface parameter conversion rule, the input parameter data model of the docking interface is the full business data of the business processing system corresponding to the business data model, and the output parameter data model is the expected target data of the third-party vendor system corresponding to the business data model.

[0051] In some embodiments, the configuration module is further configured to configure the interface docking timing of each business data model;

[0052] The business data sending module is further configured to detect, for any business data model, whether the interface docking timing of the business data model is satisfied;

[0053] If it is satisfied, the second interface parameter conversion rule is used to perform parameter conversion on the business data to be sent, and the business data that meets the data standard of the third-party vendor system is obtained.

[0054] If it is not satisfied, the business data to be sent corresponding to the business data model is rejected from being sent.

[0055] Furthermore, the configuration module is further configured to receive, through the visual configuration interface, the data sending conditions for any business data model;

[0056] The business data sending module is further configured to detect, for any business data model, whether the data sending conditions of the business data model are satisfied;

[0057] If it is satisfied, the business data to be sent that meets the data sending conditions is subjected to parameter conversion, and the business data that meets the data standard of the third-party vendor system is obtained.

[0058] If it is not satisfied, the business data to be sent that meets the data sending conditions is rejected from being sent.

[0059] In some embodiments, the configuration module is further configured to configure new first configuration information and second configuration information according to the interface information of the new third-party vendor system to be docked.

[0060] (1) For the docking interface involved in the business data acquisition module, it has the following characteristics:

[0061] A. Taking the actual business scenarios of the business processing system as units, the business scenarios of the business processing system are determined, and interfaces outside the business scope of the business processing system are not within the docking scope;

[0062] B. The range of input parameters of the interfaces that can be provided to the third-party vendor system for each business scenario is determined, that is, the upstream business data before the interface docking of each business scenario, and input parameters exceeding the upstream business data cannot be provided;

[0063] C. The target data model expected to be returned by each business scenario interface is determined, that is, the data model actually required by each business scenario. Data exceeding the target data model is not within the scope of docking.

[0064] D. For the docking interfaces provided by third-party vendor systems, the interface type, interface address, request type, request input parameters, and interface output parameters vary depending on the vendor being docked, which are uncertain factors.

[0065] The docking solution is as follows:

[0066] a. Package CALL_API with each business scenario as a unit. Each business unit is an independent CALL_API. The entry point for calling the docking interface is the CALL_API for each business scenario, achieving maximum compatibility with the interfaces of third-party vendor systems.

[0067] b. Configure the docking interface information provided by third-party vendor systems in the visual configuration interface to centrally manage the interfaces of third-party vendor systems uniformly, and configure the docking interface information and parameter conversion rules. Among them, the third-party vendors can be one vendor or multiple vendors.

[0068] c. Combine the interfaces of third-party vendor systems with each business scenario as a unit in the visual configuration interface, and configure the mapping rules between the output parameters of the third-party vendor system interfaces and the target data model expected to be returned by the business scenario interfaces.

[0069] d. Inside CALL_API, perform parameter conversion, unified interface scheduling, etc. according to the configured interface information, parameter conversion rules (including interface input parameter mapping rules and interface output parameter mapping rules), interface combination rules, etc., and return the final target data model.

[0070] e. One CALL_API can contain one or more third-party vendor interfaces, which can be flexibly combined according to the interfaces of third-party vendor systems, achieving maximum compatibility with the interfaces of third-party vendor systems.

[0071] For the business scenario of "application form list":

[0072] For the business scenario of "application form list":

[0073] a. The CALL_API for this scenario is getApplySheetList.

[0074] b. The input parameter model is the full upstream business data for this scenario, and the data model is as follows:

[0075]

[0076]

[0077] c. The output parameter model is the expected target data for this scenario, and the data model is as follows:

[0078]

[0079]

[0080] d. The interface provided by Vendor A for this scenario is getApplyList. We enter the relevant information of the getApplyList interface in the visual configuration interface, set the input parameter conversion rules, etc., and name it the "Get Application Form List" interface. At the same time, associate the "Get Application Form List" interface with the "Application Form List" scenario, and set the conversion rules for the return parameters of the third-party vendor and the expected target data of the scenario.

[0081] e. In the actual business scenario, call the getApplySheetList interface [CALL_API in this scenario]. The getApplySheetList internally reads the relevant configuration information, performs input parameter conversion and interface scheduling, and returns the converted expected target data of the scenario.

[0082] f. Achieve seamless scheduling in the business processing system with zero development.

[0083] (2) For the docking interfaces involved in the sending business data module, it has the following characteristics:

[0084] It is necessary to send data to the third-party vendor system for data sharing, and the interface sending result directly affects the business process flow of the third-party vendor system. The docking characteristics of such interfaces are:

[0085] A. Based on the actual data model of the business processing system, the range of input parameter data that the business processing system can provide to the third-party vendor system interface is determined, and the data model that can be provided to the third-party vendor system interface is determined;

[0086] B. The data range that can be provided to the third-party vendor system interface <= the actual data range;

[0087] E. For the docking interfaces provided by the third-party vendor, the interface type, interface address, request type, request input parameters, and interface output parameters vary depending on the docking vendor, which are uncertain factors.

[0088] F. There are differences in the third-party vendor systems, interface docking conditions, interface docking timing, data ranges, etc. at different sites.

[0089] The docking solution is as follows:

[0090] a. Perform interface scheduling in the form of a scheduled task, with one data sharing scenario as one PLAN_TASK;

[0091] b. Configure the system interface information of third-party manufacturers in the visual configuration interface, centrally manage the system interfaces of third-party manufacturers, and configure the docking interface information and input parameter conversion rules. It can be one manufacturer or multiple manufacturers.

[0092] c. Set up scheduled tasks in the visual configuration interface, and configure interface call conditions, interface docking timing, data range, etc.

[0093] d. When the task execution conditions are met, execute PLAN_TASK. Inside PLAN_TASK, perform input parameter conversion, unified interface scheduling, etc. according to the configured interface information, interface input parameter rules, interface combination rules, interface data range, etc., and send the final target data.

[0094] f. One PLAN_TASK can contain one or more system interfaces of third-party manufacturers, and can be flexibly combined according to the system interfaces of third-party manufacturers to achieve the maximum compatibility with the system interfaces of third-party manufacturers.

[0095] Take the task of "examination information of patients with cardiovascular diseases" as an example;

[0096] a. Set up a scheduled task in the visual configuration interface, and the task name is "examination information of patients with cardiovascular diseases". Configure task information such as task conditions and task time. Among them, the task conditions can determine the docking timing of the docking interface.

[0097] b. The input parameter model is the full volume of business data in the business processing system, and the data model is as follows:

[0098]

[0099]

[0100] c. The interface provided by manufacturer A is pacsTotal. We enter the relevant information of the pacsTotal interface in the visual configuration interface, set the input parameter conversion rules, etc., and name it the "report submission for patients with cardiovascular diseases" interface. At the same time, associate the "report submission for patients with cardiovascular diseases" interface with the "examination information of patients with cardiovascular diseases" task.

[0101] d. When the execution conditions of the "examination information of patients with cardiovascular diseases" task are met, execute this scheduled task. Inside the task, perform input parameter conversion, unified interface scheduling, etc. according to the configured interface information, interface input parameter rules, interface combination rules, interface data range, etc., and send the final target data.

[0102] e. Achieve seamless scheduling and zero development in the business scenario of the business processing system.

[0103] In some embodiments, the interface types of the docking interface may include: DATABASE type, WEBAPI type, WEBSERVICE type, and FTP type.

[0104] The request types of the business data involved in this application may include: GET, POST, POST_XML, POST_JSON, and POST_FORM, etc.;

[0105] The database types of the business data involved in this application may include: SQLSERVER2000, SQLSERVER2005, SQLSERVER2008, SQLSERVER2012, ORACLE, MYSQL, DB2, SYBASE, and POSTSQL, etc.

[0106] The input parameter scripts involved in this application may include: JSON, FORMDATA, and FUNCTION, etc.;

[0107] The mapping scripts involved in this application may include: FUNCTION.

[0108] In addition, when the configuration data involved in this application is stored in the database, historical versions will be stored. If a configuration exception occurs, it can be immediately restored to the historical version to minimize the impact on the on-site business process. It supports configuration export and import to realize the reuse of the same manufacturer's and similar interface configurations in different sites, without the need to manage the configuration versions of the same manufacturer's and similar interfaces, saving the version management cost and improving the online delivery efficiency.

[0109] Those skilled in the art should understand that the embodiments in the embodiments of this application can be provided as methods, systems, or computer program products. Therefore, the embodiments in this application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments in this application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0110] The embodiments in the embodiments of this application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products in the embodiments of this application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate for realizing in the process Figure 1one or more processes and / or blocks Figure 1 means for the functions specified in one or more blocks

[0111] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce a manufacture including instruction means that implement the functions in the process Figure 1 one or more processes and / or blocks Figure 1 the functions specified in one or more blocks

[0112] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus, such that a series of operational steps are performed on the computer or other programmable apparatus to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions in the process Figure 1 one or more processes and / or blocks Figure 1 the steps of the functions specified in one or more blocks

[0113] Although the preferred embodiments in the embodiments of the present application have been described, those skilled in the art can make additional changes and modifications once they learn the basic creative concept. Therefore, the appended claims are intended to be construed to include the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application

[0114] Obviously, those skilled in the art can make various changes and variations to the embodiments in the embodiments of the present application without departing from the spirit and scope of the embodiments in the embodiments of the present application. Thus, if these modifications and variations of the embodiments in the embodiments of the present application fall within the scope of the claims of the embodiments of the present application and their equivalent technologies, the embodiments of the present application are also intended to include these changes and variations

Claims

1. A data transmission device for docking systems of different manufacturers, characterized in that, The device includes: A configuration module, configured to configure first configuration information for obtaining service data from a third-party vendor system and second configuration information for sending service data to the third-party vendor system; the first configuration information includes: the service docking scenario of the docking interface and the first interface parameter conversion rule for the corresponding scenario; wherein, the service scope of the interface is summarized as the service docking scenario of the interface; the second configuration information includes: the service data model involved in the docking interface and the second interface parameter conversion rule for the corresponding service data model; A service data acquisition module, configured to, for any service docking scenario, through the docking interface of the service docking scenario, use the full upstream service data of the docking scenario as the parameter of the docking interface, and perform parameter conversion using the first interface parameter conversion rule to obtain a parameter model that meets the parameter standard of the third-party vendor system, and obtain the current service data provided by the third-party vendor system; A service data sending module, configured to, for any service data model, use the second interface parameter conversion rule to perform parameter conversion on the service data to be sent to obtain service data that meets the data standard of the third-party vendor system, and send it to the third-party vendor system, and use the second interface parameter conversion rule to convert the sending result feedback by the third-party vendor system to obtain a sending result recognizable by the service processing system.

2. The device according to claim 1, characterized in that, The configuration module is specifically configured to receive, through a visual configuration interface, the interface configuration information of different third-party vendor systems input, and parse the received interface configuration information of each third-party vendor system to obtain the input parameter data model and the output parameter data model of the service processing system with respect to each third-party vendor system; Based on the input parameter data model and the output parameter data model of the service processing system with respect to each third-party vendor system, configure the first interface parameter conversion rule and the second interface parameter conversion rule of the corresponding docking interface; wherein, the input parameter data model and the output parameter data model of the service processing system are data models that meet the data standard of the service processing system.

3. The device according to claim 2, characterized in that, For the first interface parameter conversion rule, the input parameter data model of the docking interface is the full upstream service data of the corresponding service docking scenario, and the input parameter model is converted into a parameter model that meets the parameter standard of the third-party vendor system through the first interface parameter conversion rule, and the output parameter data model is the expected target data of the corresponding service docking scenario; For the second interface parameter conversion rule, the input parameter data model of the docking interface is the full service data of the service processing system of the corresponding service data model, and the output parameter data model is the expected target data of the third-party vendor system of the corresponding service data model.

4. The device according to claim 1, characterized in that, The configuration module is further configured to configure the interface docking timing of each service data model; The service data sending module is further configured to, for any service data model, detect whether the interface docking timing of the service data model is satisfied; If satisfied, adopt the second interface parameter conversion rule to convert the service data to be sent, obtain service data that meets the data standard of the third-party manufacturer's system, and send it to the third-party manufacturer's system. Adopt the second interface parameter conversion rule to convert the sending result feedback by the third-party manufacturer's system to obtain a sending result recognizable by the service processing system; If not satisfied, reject the service data to be sent corresponding to the service data model from being sent.

5. The device according to claim 4, characterized in that, The configuration module is further configured to receive, through the visual configuration interface, the data sending conditions for any service data model; The service data sending module is further configured to detect, for any service data model, whether the data sending conditions of the service data model are satisfied; If satisfied, adopt the second interface parameter conversion rule to convert the service data to be sent that meets the data sending conditions, obtain service data that meets the data standard of the third-party manufacturer's system, and send it to the third-party manufacturer's system. Adopt the second interface parameter conversion rule to convert the sending result feedback by the third-party manufacturer's system to obtain a sending result recognizable by the service processing system; If not satisfied, reject the service data to be sent that meets the data sending conditions from being sent.

6. The device according to claim 1, characterized in that, The configuration module is further configured to configure new first configuration information and second configuration information according to the interface information of the new third-party manufacturer's system to be docked.

7. The device according to claim 1, characterized in that, The interface types of the docking interface include: DATABASE type, WEBAPI type, WEBSERVICE type, and FTP type.

8. A service processing system, characterized in that, The system includes: a processor and the data transmission device for docking different manufacturer systems according to any one of claims 1-7; The processor is configured to send service data to the data transmission device for docking different manufacturer systems and obtain service data from the data transmission device for docking different manufacturer systems.

Images