Data transmission method and apparatus, storage medium, and computer program product

Abstract

The application discloses a data transmission method and device, a storage medium and a computer program product, relates to the field of data transmission, and provides the method, which comprises the following steps: acquiring a business requirement of a third-party system, and configuring a core business script according to the business requirement; receiving an interface in-out parameter configuration instruction input by a user, and configuring an interface in-out parameter according to the interface in-out parameter configuration instruction; determining a third-party system connection mode based on the interface in-out parameter; and connecting the third-party system according to the interface in-out parameter, the third-party system connection mode and the core business script, and performing business data transmission. Through dynamic configuration of the interface in-out parameter, diversified core business scripts and flexible third-party system connection modes, efficient response to business changes among multiple systems, flexible adaptation to technical differences and safe and reliable data cooperation are realized, so that the dual technical targets of high efficiency and flexibility are achieved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data transmission, and particularly relates to a data transmission method and device, a storage medium and a computer program product. BACKGROUND

[0002] In the fields of medical treatment, finance and supply chain, the demand for data interaction and business collaboration among multiple systems is increasingly urgent, and efficient data interaction and business collaboration among different systems become the key to improving business efficiency and reducing operation and maintenance costs. Currently, the software connection on the market generally uses a hard coding method to define interface parameters, is limited to passively waiting for a third-party system to call an interface, or only supports simple timing task active calling, and lacks flexible switching capability between the two modes. Therefore, the data interaction and business collaboration among different systems cannot be solved, and the application cannot be applied to various scenarios requiring data transmission and integration with multiple third-party systems.

[0003] Therefore, how to realize efficient and flexible data transmission and business collaboration among multiple third-party systems becomes a problem to be solved by the present application.

[0004] The above content is only used to assist in understanding the technical solutions of the present application and does not represent the acknowledgement of the above content as prior art. SUMMARY

[0005] The main purpose of the present application is to provide a data transmission method, device, storage medium and computer program product, which aims to solve the problem of how to realize efficient and flexible data transmission and business collaboration among multiple third-party systems.

[0006] To achieve the above purpose, the present application provides a data transmission method applied to a data transmission device, wherein the data transmission device adopts a distributed full-stack dynamic integration architecture, and the data transmission method comprises the following steps:

[0007] Obtaining business requirements of a third-party system, and configuring a core business script according to the business requirements;

[0008] Receiving an interface in-out parameter configuration instruction input by a user, and configuring interface in-out parameters according to the interface in-out parameter configuration instruction;

[0009] Determining a third-party system connection mode based on the interface in-out parameters;

[0010] Connecting the third-party system according to the interface in-out parameters, the third-party system connection mode and the core business script, and performing business data transmission.

[0011] In an embodiment, the step of receiving an interface in-out parameter configuration instruction input by a user, and configuring interface in-out parameters according to the interface in-out parameter configuration instruction comprises the following steps:

[0012] receiving an interface access parameter configuration instruction input by a user in an interface mode, a file configuration mode or a database storage mode;

[0013] associating the interface access parameter configuration instruction with the service requirement, and configuring and adjusting interface access parameters according to the interface access parameter configuration instruction and the service scenario.

[0014] In an embodiment, the third-party system interfacing mode includes active interfacing and passive interfacing, and the step of interfacing the third-party system according to the interface access parameters, the third-party system interfacing mode and the core service script and performing service data transmission includes:

[0015] If the third-party system interfacing mode is passive interfacing, a callable interface is determined based on the interface access parameters, the core service script is parsed, and service data is sent to the third-party system through the callable interface;

[0016] If the third-party system interfacing mode is active interfacing, a third-party interface is periodically called based on the interface access parameters, the core service script is executed, and service data sent by the third-party system is received through the third-party interface.

[0017] In an embodiment, the step of determining a callable interface based on the interface access parameters, parsing the core service script and sending service data to the third-party system through the callable interface includes:

[0018] receiving an interface call request sent by the third-party system, and determining a callable interface according to the interface access parameters;

[0019] determining whether the interface call request is legal and whether the callable interface exists through a pre-filter;

[0020] If the interface call request is legal and the callable interface exists, it is determined whether to perform a signature verification operation on the interface call request according to the interface access parameters;

[0021] If the signature verification operation is performed and the signature verification operation is successful, the core service script is parsed, service data is determined according to the result of parsing the core service script, and the service data is encrypted using a preset encryption parameter;

[0022] The encrypted service data is sent to the third-party system through the callable interface.

[0023] In an embodiment, the step of periodically calling a third-party interface based on the interface access parameters, executing the core service script and receiving service data sent by the third-party system through the third-party interface includes:

[0024] configure a pre-service script, and execute the pre-service script based on the distributed full-stack dynamic integration architecture;

[0025] If the pre-service script is executed successfully, determine whether to perform a signing operation on the request data after the execution of the pre-service script based on the interface in-out parameter;

[0026] If the signing operation is performed and the signing operation is successful, initiate a call to a third-party interface request;

[0027] If the call to the third-party interface request is successful, execute the core service script, and receive business data sent by a third-party system through the third-party interface.

[0028] In an embodiment, before the step of connecting the third-party system based on the interface in-out parameter, the third-party system connection mode, and the core service script and performing data transmission, the method further comprises:

[0029] receiving an encryption algorithm configuration instruction, and selecting at least one encryption mode based on the encryption algorithm configuration instruction;

[0030] setting an encryption parameter according to the encryption mode and the encryption algorithm configuration instruction.

[0031] In an embodiment, the interface in-out parameter and the encryption parameter are stored in a configuration database, log data generated by the connection to the third-party system is stored in a log database, the business data is stored in a business database, the business database is dynamically configured by multiple data sources, and the configuration database, the business database, and the log database are isolated from each other.

[0032] In addition, to achieve the above-mentioned purpose, the application further provides a data transmission device, which comprises:

[0033] a core service script logic configuration module configured to obtain business requirements of a third-party system and configure a core service script according to the business requirements;

[0034] an interface configuration module configured to receive an interface in-out parameter configuration instruction input by a user and configure an interface in-out parameter according to the interface in-out parameter configuration instruction;

[0035] a third-party system connection module configured to determine a third-party system connection mode based on the interface in-out parameter, connect the third-party system based on the interface in-out parameter, the third-party system connection mode, and the core service script, and perform business data transmission.

[0036] In addition, to achieve the above object, the present application also provides a storage medium, which is a computer readable storage medium, and a computer program is stored on the storage medium, and the computer program realizes the steps of the data transmission method when executed by a processor.

[0037] In addition, to achieve the above object, the present application also provides a computer program product, which comprises a computer program, and the computer program realizes the steps of the data transmission method when executed by a processor.

[0038] The one or more technical solutions provided by the present application have at least the following technical effects:

[0039] The business requirements of the third-party system are acquired, and a core business script is configured according to the business requirements; an interface in-out parameter configuration instruction input by a user is received, and an interface in-out parameter is configured according to the interface in-out parameter configuration instruction; a third-party system connection mode is determined based on the interface in-out parameter; and the third-party system is connected according to the interface in-out parameter, the third-party system connection mode and the core business script, and business data transmission is performed. First, diversified core business scripts are configured according to the business requirements of the third-party system, covering complex business logic. Second, dynamic configuration of the interface in-out parameter is realized according to the interface in-out parameter configuration instruction, supporting parallel connection of multiple systems, avoiding separate development of interfaces for each system, and solving the problems of difficult adjustment and poor flexibility of interface parameters. Further, different third-party system connection modes are suitable for different scenarios, which can actively connect the third-party system or provide interfaces for the third-party system to call, meeting the needs of different business scenarios, actively connecting to perform tasks during off-peak hours to avoid high concurrency pressure, and passively connecting to respond on demand to reduce invalid resource occupation. In summary, the present application constructs a standardized and scalable connection framework through dynamic configuration of the interface in-out parameter, diversified core business scripts and flexible third-party system connection modes, realizes efficient response to business changes, flexible adaptation to technical differences and safe and reliable data collaboration among multiple systems, and thus achieves the dual technical goals of efficiency and flexibility. BRIEF DESCRIPTION OF DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and serve to explain the principles of the present application together with the specification.

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced here. Obviously, for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

[0042] Figure 1 Flowchart provided for the first embodiment of the data transmission method of the present application;

[0043] Figure 2 Flowchart provided for the second embodiment of the data transmission method of the present application;

[0044] Figure 3 Schematic diagram of passive docking mode provided for the third embodiment of the present application;

[0045] Figure 4 Schematic diagram of active docking mode provided for the third embodiment of the present application;

[0046] Figure 5 Module structure schematic diagram of the data transmission device of the embodiment of the present application;

[0047] Figure 6 Device structure schematic diagram of the hardware running environment involved in the data transmission method of the embodiment of the present application.

[0048] The object implementation, functional features and advantages of the present application will be further explained with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0049] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application, and are not used to limit the present application.

[0050] In order to better understand the technical solutions of the present application, the following will be described in detail in combination with the drawings of the specification and specific embodiments.

[0051] The main solution of the embodiment of the present application is: obtaining the business requirement of the third-party system, and configuring the core business script according to the business requirement; receiving the interface input / output parameter configuration instruction input by the user, and configuring the interface input / output parameter according to the interface input / output parameter configuration instruction; determining the docking mode of the third-party system based on the interface input / output parameter, wherein the docking mode of the third-party system includes active docking and passive docking, if the docking mode of the third-party system is passive docking, providing the callable interface to the third-party system based on the interface input / output parameter and the core business script, and sending the business data to the third-party system through the callable interface; if the docking mode of the third-party system is active docking, periodically calling the third-party interface based on the interface input / output parameter and the core business script, and receiving the business data sent by the third-party system through the third-party interface.

[0052] In the embodiment, for the convenience of description, the following describes the data transmission device as the execution subject.

[0053] The embodiment of the application considers that in the fields of medical treatment, finance, supply chain and the like, the demand for data interaction and business collaboration among multiple systems is increasingly urgent, and efficient data interaction and business collaboration among different systems become the key to improving business efficiency and reducing operation and maintenance cost. However, the third-party system interfacing technology generally has limitations: the traditional scheme relies on hard coding to implement interface parameter setting, and cannot dynamically adjust according to business scenarios; and only supports a single interfacing mode, passively waits for third-party interface calling or actively acquires data through simple polling; and the core business processing logic usually only supports simple SQL queries or fixed scripts, and it is difficult to meet the needs of complex business scenarios.

[0054] Therefore, the application provides a solution to obtain the business requirements of a third-party system and configure a core business script according to the business requirements: receiving a user input interface in-out parameter configuration instruction, and configuring interface in-out parameters according to the interface in-out parameter configuration instruction; determining a third-party system interfacing mode based on the interface in-out parameters; and interfacing the third-party system and performing business data transmission according to the interface in-out parameters, the third-party system interfacing mode and the core business script. First, according to the business requirements of the third-party system, a diversified core business script is configured to cover complex business logic. Second, the dynamic configuration of the interface in-out parameters is realized according to the interface in-out parameter configuration instruction, supporting multi-system parallel interfacing, avoiding the development of interfaces for each system, and solving the problems of difficult interface parameter adjustment and poor flexibility. Further, different third-party system interfacing modes are suitable for different scenarios, which can either actively interface the third-party system or provide interfaces for the third-party system to call, meeting the needs of different business scenarios, actively interfacing to perform tasks during off-peak hours to avoid high concurrency pressure; passively interfacing to respond on demand to reduce invalid resource occupation. In summary, the application constructs a standardized and scalable interfacing framework through the dynamic configuration of interface in-out parameters, diversified core business scripts and flexible third-party system interfacing modes, realizes efficient response to business changes, flexible adaptation to technical differences and safe and reliable data collaboration among multiple systems, thereby achieving the dual technical goals of efficiency and flexibility.

[0055] It should be noted that the execution subject of the embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device, a multi-party data transmission device, etc. capable of realizing the above functions. The following will take the data transmission in the medical field as an example to describe the embodiment and the following embodiments.

[0056] Based on this, the embodiment of the application provides a data transmission method, which is described with reference to Figure 1 , Figure 1 The flowchart of the first embodiment of the data transmission method of the application is shown in the figure.

[0057] In the embodiment, the data transmission method is applied to a data transmission device adopting a distributed full-stack dynamic integration architecture, and the data transmission method comprises steps S10-S40.

[0058] In step S10, a business requirement of a third-party system is acquired, and a core business script is configured according to the business requirement.

[0059] The data transmission device adopts a distributed full-stack dynamic integration architecture, which is a springboot+redis+quartz+vue+Nashorn JavaScript technical architecture. Redis (RemoteDictionary Server) provides distributed cache and message queue functions, supports data sharing and horizontal expansion in a high-concurrency scenario, the timing task scheduling module of Quartz (Quartz: open source job scheduling framework) can coordinate multi-node tasks in a distributed environment, Vue (Vue.js: progressive JavaScript framework) is used to realize a user interaction interface, Spring Boot (Spring Boot: rapid development framework based on Spring framework) provides business logic processing, and Nashorn JavaScript (Nashorn JavaScript: JavaScript engine) supports dynamic business logic. The application adopts the above-mentioned distributed full-stack dynamic integration architecture, provides an efficient, stable running environment and good user experience, and has excellent performance in data processing, task scheduling, interface display and script execution, thereby providing strong support for the realization of multi-party software interfacing.

[0060] The business requirement of the third-party system is acquired, and the core business script is configured according to the business requirement. For example, the business requirement of the third-party system is a medical system patient file query, and the core business script for extracting specific fields or aggregated results from a database is configured according to the business requirement. For another example, the business requirement is a financial system transaction flow reconciliation, and the core business script for performing data cleaning, conversion or batch operation is configured according to the business requirement. It can be understood that the core business script can be configured according to the specific application scenario and specific business requirement of the third-party system, thereby flexibly adapting to multiple scenarios.

[0061] The core business script supports MyBatis SQL syntax configuration, stored procedures, Js (JavaScript: lightweight programming language) script configuration and the like, and is used to process business logic interfaced with the third-party system. For example, database query and operation can be performed through MyBatis SQL syntax, stored procedures can improve data processing efficiency, and js scripts can realize complex business logic judgment and processing.

[0062] Note that MyBatis is an excellent persistence layer framework that supports customized SQL, stored procedures, and advanced mapping; Js, JavaScript is a lightweight programming language, mainly used for web development, adding dynamic functions and interactivity to web pages, one of the core technologies of the Web, widely used in client-side scripting, and can be executed directly in the user's browser.

[0063] Step S20, receiving the interface input parameter configuration instruction input by the user, and configuring the interface input parameter according to the interface input parameter configuration instruction;

[0064] The interface input parameter includes interface address, request method, parameter format, etc. The user can input the parameter in the form of a form or a JSON editor through the user interface (Vue front end), and the interface input parameter configuration is stored in the configuration database SQLite in real time, and the configuration database supports version management and rollback. The interface address, protocol type and parameter format are dynamically configured through the interface input parameter configuration instruction input by the user, and the interface standards of different third-party systems are quickly adapted.

[0065] Specifically, the user inputs the JSON format request body template on the interface, and the data transmission device listens to the configuration change event through Spring BootActuator, dynamically refreshes the configuration cache of the interface service module, for example, after modifying the interface address, the new URL (uniform resource locator: uniform resource locator) takes effect immediately, without the need to restart the service; The data transmission device can also automatically detect parameter logic conflicts and prompt the user to correct them, and perform legality verification on the parameters input by the user, including: the interface address must comply with the URL specification, the request method must match the business logic, etc.

[0066] Step S30, determining the third-party system interfacing mode based on the interface input parameter;

[0067] According to the protocol type, request method and business scenario identifier in the interface input parameter, the applicable third-party system interfacing mode is automatically matched, and the third-party system interfacing mode includes passive interfacing mode and active interfacing mode, which means that the data transmission device can provide an interface for the third-party system to call, or actively call the third-party interface. The diversified interfacing mode meets the needs of different business scenarios, improves the universality and practicality of the software.

[0068] The trigger condition of the passive docking mode is that the interface parameter contains an externally exposed interface address and a request method, and the passive docking mode is suitable for a scenario of real-time response to a third-party request, and the data transmission device generates a standardized API for calling by the third-party; the trigger condition of the active docking mode is that the interface parameter contains a timing task trigger condition and a target interface address, and the active docking mode is periodic data pulling or batch processing, and generates a timing task scheduling rule, and actively calls the third-party interface.

[0069] In step S40, the third-party system is docked according to the interface in-out parameter, the third-party system docking mode and the core business script, and business data transmission is performed.

[0070] According to the protocol type and the request format in the interface in-out parameter, a standardized request template is dynamically generated, and the standardized request template includes two modes of HTTP and WebService. The third-party system is docked according to the standardized request template and the third-party system docking mode, and business data transmission is performed, wherein the execution logic of the passive docking mode is that, after receiving a third-party request, a core business script is called to process data, and a result is returned according to a response format defined by the interface parameter; the execution logic of the active docking mode is that a timing task is triggered by Quartz, request data is generated by calling a core script, and the request data is actively pushed to the third-party interface.

[0071] Further, the execution result of the core business script is automatically mapped to a field defined by the interface parameter, for example, a query result of a SQL script is directly filled into a JSON response body, and a business logic result dynamically generated in a JavaScript script is bound to a request body.

[0072] The data transmission device records the request parameter, the response state (success / failure) and the time consumption of each call, and stores the same into a log database. In the active docking scenario, business data is locked before the third-party interface is called, to prevent concurrent modification; in the passive docking scenario, a database transaction is used to ensure the atomicity of script execution and data updating.

[0073] It should be noted that the interface in-out parameter and an encryption parameter for subsequent security encryption are stored in a configuration database parameter, log data generated by docking the third-party system is stored in a log database, and business data is stored in a business database. The business database is dynamically configured by multiple data sources, and the configuration database, the business database and the log database are isolated from each other. Taking the medical field as an example, the multiple data source dynamic configuration means that a user can select a suitable data source according to the database type of a medical system.

[0074] The embodiment provides a data transmission method, acquires a service requirement of a third-party system, and configures a core service script according to the service requirement: receives an interface in-out parameter configuration instruction input by a user, and configures an interface in-out parameter according to the interface in-out parameter configuration instruction; determines a third-party system connection mode based on the interface in-out parameter; and connects the third-party system according to the interface in-out parameter, the third-party system connection mode and the core service script, and performs business data transmission. First, a diversified core service script is configured according to the service requirement of the third-party system, and complex business logic is covered. Secondly, the dynamic configuration of the interface in-out parameter is realized according to the interface in-out parameter configuration instruction, the parallel connection of multiple systems is supported, the interface of each system is avoided to be developed individually, and the problems of difficult adjustment and poor flexibility of the interface parameter are solved. Further, different third-party system connection modes are suitable for different scenes, the third-party system can be actively connected or an interface can be provided for the third-party system to call, the requirements in different business scenes are met, active connection can perform tasks in off-peak periods to avoid high concurrency pressure, passive connection responds on demand to reduce invalid resource occupation. In summary, the dynamic configuration of the interface in-out parameter, the diversified core service script and the flexible third-party system connection mode build a standardized and scalable connection framework, efficiently respond to business changes between multiple systems, flexibly adapt to technical differences and safely and reliably coordinate data, so that the dual technical goals of high efficiency and flexibility are achieved.

[0075] In a feasible implementation, step S20 can include steps S21-S22:

[0076] In step S21, an interface in-out parameter configuration instruction input by a user is received, and the interface in-out parameter configuration instruction is input in an interface mode, a file configuration mode or a database storage mode.

[0077] The interface in-out parameter configuration instruction is input in the interface mode, that is, a visual configuration interface is built through a Vue front end, the visual configuration interface provides a form input component, and an interface parameter is defined by a user through dragging or filling a field.

[0078] The file configuration mode input means that the data transmission device supports the uploading of a configuration file in a YAML or JSON format, verifies the syntax and legality of the file, parses the file content and maps the file content into an interface in-out parameter.

[0079] The database storage mode input means that a configuration database SQLite is directly operated through a SQL statement or an ORM framework to write an interface in-out parameter, and the configuration database records parameter modification history and supports time stamp query or rollback.

[0080] It can be understood that different instruction input modes can be selected according to the use habits and needs of different users, and the interface in-out parameter configuration instruction is not limited to the above three.

[0081] In step S22, the interface in-out parameter configuration instruction and the service requirement are associated, and the interface in-out parameter is configured and adjusted according to the interface in-out parameter configuration instruction and the service scene.

[0082] The interface in-out parameter configuration instruction and the service requirement are associated, a preset parameter template is loaded according to a label in the service requirement, for example, medical scene automatically strengthens safety parameters, financial scene optimizes high-frequency request configuration, and service matching degree is improved. The service requirement change drives the parameter automatic adjustment, so that the dynamic adjustment of the interface is realized, and the flexibility and adaptability are greatly improved.

[0083] Based on the first embodiment of the application, the second embodiment of the application is proposed. In the second embodiment of the application, the same or similar contents as the above embodiment one can be referred to the above introduction, and will not be repeated hereinafter.

[0084] On this basis, referring to Figure 2 , Figure 2 The second embodiment process schematic diagram provided by the application, in this embodiment, before the step S40 of the interface in-out parameter, the third-party system connection mode, the core business script connecting the third-party system and performing data transmission, still includes steps S01-S02:

[0085] Step S01, receiving an encryption algorithm configuration instruction, selecting at least one encryption mode based on the encryption algorithm configuration instruction;

[0086] The user can select the encryption algorithm type through the Vue front-end interface, input the encryption algorithm configuration instruction, and the data transmission device selects at least one encryption mode according to the encryption algorithm configuration instruction input by the user. The encryption modes that can be selected include SM2, an elliptic curve public key cryptography algorithm in the national cryptography standard, used for digital signature and key exchange; SM3, a hash algorithm in the national cryptography standard, used for data integrity check; AES algorithm, RSA algorithm, etc. The appropriate encryption algorithm is selected based on the specific user demand.

[0087] Step S02, setting encryption parameters according to the encryption mode and the encryption algorithm configuration instruction.

[0088] Further, the encryption parameters are set according to the encryption mode and the encryption algorithm configuration instruction. The SM2 algorithm is used for digital signature or key exchange, and the SM3 algorithm is used for data integrity verification. The encryption parameters include key length, signature mode, hash salt value and encrypted data range. The encryption key is generated based on the encryption parameters, and the key is stored in the isolated configuration database. At the same time, the key life cycle management rule is set, and the life cycle management includes key periodic rotation and automatic archiving of invalid keys.

[0089] Before transmitting data through the calling interface, the business data is encrypted or signed according to the encryption algorithm and the encryption parameters. If the SM2 algorithm is selected, the data is asymmetrically encrypted and a digital signature is generated. If the SM3 algorithm is selected, a hash digest is generated for the data and transmitted together with the original data. Exemplarily, the encryption parameters can be dynamically modified or the encryption algorithm can be switched through the user interface. The modified configuration takes effect in real time and does not need to restart the service.

[0090] In this embodiment, by receiving the encryption algorithm configuration instruction, the encryption mode is flexibly selected, the encryption parameters are dynamically configured according to the encryption mode and the encryption parameters, and the business data is encrypted or signed before calling the interface to transmit data, thereby ensuring the security of data transmission.

[0091] Based on the first embodiment and / or the second embodiment of the present application, the third embodiment of the present application is proposed. In the third embodiment of the present application, the same or similar contents as the above embodiments can be referred to the above introduction, and will not be described in detail hereinafter.

[0092] In this embodiment, the third-party system interfacing mode includes active interfacing and passive interfacing. Step S40 can include steps S41-S42.

[0093] In step S41, if the third-party system interfacing mode is passive interfacing, the callable interface is determined based on the interface in-out parameters, the core business script is parsed, and the business data is sent to the third-party system through the callable interface.

[0094] If the third-party system is passively connected, that is, the third-party system needs to actively acquire data or perform business processing, the data transmission device provides a callable interface to actively acquire data. In the case of passive connection, the data transmission device automatically generates a standardized interface according to the address (URL) and protocol type in the interface input and output parameters, and registers it to the server. The standardized interface includes an HTTP interface and a WebService interface. The HTTP interface dynamically creates a RESTful endpoint through the RestController annotation of SpringBoot. The WebService interface generates a WSDL file through the Apache CXF framework and publishes a SOAP service endpoint. The business data is sent to the third-party system through the callable interface.

[0095] Step S42, if the third-party system is actively connected, periodically call the third-party interface based on the interface input and output parameters, execute the core business script, and receive the business data sent by the third-party system through the third-party interface.

[0096] If the third-party system is actively connected, that is, actively calling the third-party interface, receiving the business data sent by the third-party interface. In the case of active connection, a timing task is triggered by a Quartz task scheduling to automatically call the core business script to generate request data. Similarly, the interface calling method supports HTTP and WebService methods.

[0097] In this embodiment, the interface calling method supports HTTP (lightweight and fast) and WebService (cross-platform reliable communication) methods, covering different third-party technology stacks; passive connection meets real-time interaction requirements, and active connection optimizes batch processing efficiency. Different processing is performed according to different connection methods, taking into account security and execution efficiency, solving the pain points of interface rigidity, poor scalability, and insufficient security in traditional solutions, and providing an efficient, flexible, and secure standardized solution for multi-system data interaction.

[0098] Specifically, referring to Figure 3 , Figure 3 The passive connection method provided by the third embodiment of the present application is shown in the schematic diagram. In one possible implementation, step S41 can include steps S411-S415:

[0099] Step S411, receiving the interface calling request sent by the third-party system, and determining the callable interface according to the interface input and output parameters;

[0100] The data transmission device receives an interface call request sent by a third-party system through Spring Boot, parses the interface call request, determines a request header, a request body and a URL path, and extracts key parameters including an interface address, a request method and a protocol type. According to the interface address and the request method, the interface register in the configuration database (SQLite) is queried to determine the interface that can be called by the third-party system.

[0101] In step S412, it is judged by the pre-filter whether the interface call request is legal and whether the callable interface exists.

[0102] Further, it is verified by the Redis cache whether the source IP of the interface call request is within the permitted range, the API Key is extracted from the request header, compared with the key record in the configuration database, and the Redis counter is enabled to limit the maximum number of requests per minute; it is verified whether the interface is registered in the configuration database and the state is “enabled”. If the interface does not exist or the request is illegal, a standard error code is returned, and a security log is recorded to the log database.

[0103] In step S413, if the interface call request is legal and the callable interface exists, it is judged according to the interface input and output parameters whether to perform a signature verification operation on the interface call request.

[0104] If the interface call request is legal and the callable interface exists, according to the security level identifier configured in the interface input and output parameters, it is determined whether to perform a signature verification operation on the interface call request. For example, the medical privacy data interface is marked as “high sensitivity” and must be verified; the ordinary log interface does not need to be verified.

[0105] The signature verification operation includes extracting the signature value from the request header, generating the hash value of the request data using the SM3 algorithm, decrypting the signature using the SM2 public key and comparing the hash.

[0106] In step S414, if the signature verification operation is performed and the signature verification operation is successful, the core business script is parsed, the business data is determined according to the result of parsing the core business script, and the business data is encrypted using the encryption parameter.

[0107] If the signature verification operation is required and the signature verification operation is successful, the core business script is parsed. Exemplarily, the core business script is a MyBatis SQL script, a SQL statement is dynamically generated according to the request parameter, and a database query is performed; a JavaScript script can execute dynamic logic through a Nashorn engine.

[0108] Furthermore, after executing the core business script and determining the business data that needs to be sent to the third-party system, the response data is encrypted using pre-generated encryption parameters: SM2 encryption, which uses the third-party public key to encrypt sensitive fields (such as diagnostic results); and SM3 hashing, which generates a data digest and appends it to the response header.

[0109] Step S415: Send encrypted business data to the third-party system through the callable interface.

[0110] Encrypted data is packaged according to the format defined by the interface input and output parameters, and the encrypted business data is sent to the third-party system through the callable interface. The adapted transmission protocols include HTTP protocol and WebService protocol.

[0111] like Figure 3 As shown, if any of the following occurs in the above steps: the interface call request is invalid, the callable interface does not exist, the signature verification operation fails, or the core business script parsing fails, an error will be reported directly, and the process will terminate. Only when all verifications pass will the business logic processing be executed and data returned. Log data generated by the third-party system is stored in the log database, and business data is stored in the business database. The business database is dynamically configured from multiple data sources, and the databases are isolated from each other.

[0112] Specifically, refer to Figure 4 , Figure 4 This is a schematic diagram of the active docking method provided in the third embodiment of this application. In one feasible embodiment, step S42 may include steps S421 to S424:

[0113] Step S421: Configure the pre-service script and execute the pre-service script periodically based on the distributed full-stack dynamic integration architecture;

[0114] The Vue interface allows configuration of front-end business scripts, supporting MyBatis SQL, stored procedures, or JavaScript scripts. Based on the distributed full-stack dynamic integration architecture of Quartz, the execution cycle is defined and registered with the scheduler. When a task is triggered, the Nashorn engine or MyBatis is called to execute the script, process the data, and generate request parameters.

[0115] Step S422: If the pre-processing business script is executed successfully, determine whether to perform a signature operation on the request data after the execution of the pre-processing business script based on the interface input and output parameters.

[0116] If the preceding business script executes successfully, it will determine whether to perform a signature operation on the requested data after execution based on the security level identifier in the interface input and output parameters. For example, if medical test data is marked as "highly sensitive", the signature will be automatically triggered.

[0117] Step S423, if the signing operation is performed and the signing operation is successful, initiating a call to a third-party interface request;

[0118] The signing operation includes generating an SM3 hash, generating a hash digest for the request data, or an SM2 signature, using a private key to encrypt the hash value to generate a signature. The signature generated by the signing is attached to the request header, and a call to a third-party interface request is initiated. The third-party interface request includes an HTTP request and a WebService request. For example, the HTTP request sends a POST request, and the request body is encrypted JSON data. The WebService request generates an XML message conforming to the SOAP standard, including an encrypted field.

[0119] Step S424, if the call to the third-party interface request is successful, the core business script is executed, and the business data sent by the third-party system is received through the third-party interface.

[0120] If the call to the third-party interface request is successful, the third-party system successfully responds, the returned business data of the third party is parsed, the signature is verified, and the core business script is called to update the local database state. Correspondingly, if the call to the third-party request fails, the corresponding failure business script is called.

[0121] As shown in Figure 4 If there is a response failure, a signing operation failure, or other conditions that affect the reception of business data in the above steps, an error log is recorded to the SQLite log database, including an error code, a timestamp, and original request data. The log data generated by the third-party system is stored in the log database, and the business data is stored in the business database. The business database is dynamically configured by multiple data sources, and the databases are isolated from each other. The multiple data source dynamic configuration means that users can select appropriate data sources according to the specific database type. The isolation between databases allows quick switching to a backup data source when the business database fails, ensuring the continuity of data transmission.

[0122] In order to better illustrate the data transmission method proposed in the present application, the following takes a medical system as a third-party system and the Medeek software as an example to illustrate the computer program product using the method described in the present application:

[0123] Interface configuration: the user enters the interface configuration module through the interface and sets the interface in-out parameters. For example, the interface address is set to a specific URL of the medical system, the request method is set to POST, and the parameter format is set to JSON. At the same time, the user can dynamically adjust the interface parameters as needed to adapt to different business scenarios.

[0124] Core business script logic configuration: According to the business requirements of the third-party system, users can choose the appropriate core business script logic configuration method. For example, use MyBatis syntax to configure the SQL statement for querying patient information, or use stored procedures to process statistical analysis of medical data. If complex business logic judgment is required, js script can be used for configuration, not only js syntax can be written, but also custom SQL statements can be written.

[0125] Third-party system interface: The medical bridge software can be connected with the third-party system in two ways. If the third-party system needs to actively obtain data or process business, it can call the interface provided by the medical bridge. If the medical bridge software needs to actively obtain data from the medical system, it can configure a timing task to periodically call the interface of the medical system. During the interface call process, HTTP or WebService communication method is selected according to the actual situation.

[0126] Database management: The medical bridge software supports multi-data source dynamic configuration of business database, and users can select appropriate data source according to the database type of the medical system. At the same time, the business database is isolated from the log database and the configuration database to ensure the safety of the data and the convenience of the management. For example, when the business database fails, it can quickly switch to the standby data source to ensure the continuity of data transmission.

[0127] Security encryption: When transmitting data through the interface, the medical bridge software uses the national encryption SM2, SM3, etc. to encrypt the data, ensuring the safety of sensitive data such as patient information. Users can dynamically configure encryption details through the interface, such as encryption algorithm parameters, key length, etc.

[0128] The application also provides a data transmission device, please refer to Figure 5 , the data transmission device comprises:

[0129] The core business script logic configuration module 10 is configured to obtain the business requirements of the third-party system and configure the core business script according to the business requirements.

[0130] The interface configuration module 20 is configured to receive the interface input and output parameter configuration instruction input by the user, and configure the interface input and output parameter according to the interface input and output parameter configuration instruction.

[0131] The third-party system interface module 30 is configured to determine the third-party system interface mode based on the interface input and output parameter, and interface the third-party system according to the interface input and output parameter, the third-party system interface mode and the core business script, and perform business data transmission.

[0132] The data transmission device provided in the present application adopts the data transmission method in the above embodiments, and can solve the technical problem of data transmission. Compared with the prior art, the data transmission device provided in the present application has the same beneficial effects as the data transmission method provided in the above embodiments, and other technical features in the data transmission device are the same as the features disclosed in the above embodiments, which will not be repeated here.

[0133] The present application provides a data transmission device, comprising: at least one processor; and a memory connected with the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the data transmission method in the above embodiment one.

[0134] Reference will be made to the following description of the embodiments of the present application, taken in conjunction with the accompanying drawings, in which Figure 6 which shows a structural diagram of a data transmission device suitable for implementing the embodiments of the present application. The data transmission device in the embodiments of the present application can include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. Figure 6 The data transmission device shown is only an example, and should not bring any limitation to the functions and use range of the embodiments of the present application.

[0135] As Figure 6As shown, the data transmission device can include a processing apparatus 1001 (for example, a central processor, a graphics processor, etc.), which can perform various appropriate actions and processes according to programs stored in a read-only memory 1002 or loaded from a storage apparatus 1003 into a random access memory 1004. In the random access memory 1004, various programs and data required for the operation of the data transmission device are also stored. The processing apparatus 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other through a bus 1005. An input / output interface 1006 is also connected to the bus. Generally, the following systems can be connected to the input / output interface 1006: an input apparatus 1007 including, for example, a touch panel, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output apparatus 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; the storage apparatus 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication apparatus 1009. The communication apparatus 1009 can allow the data transmission device to perform wireless or wired communication with other devices to exchange data. Although the data transmission device having various systems is shown in the figure, it should be understood that all the shown systems are not required to be implemented or possessed. More or less systems can be alternatively implemented or possessed.

[0136] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program codes for executing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network through the communication apparatus, or installed from the storage apparatus 1003, or installed from the read-only memory 1002. When the computer program is executed by the processing apparatus 1001, the above-mentioned functions defined in the methods of the embodiments disclosed in the present application are executed.

[0137] The data transmission device provided by the present application adopts the data transmission method in the above-mentioned embodiments, and can solve the technical problem of data transmission. Compared with the prior art, the data transmission device provided by the present application has the same beneficial effects as the data transmission method provided by the above-mentioned embodiments, and other technical features in the data transmission device are the same as the features disclosed in the previous embodiment method, which will not be described here.

[0138] It should be understood that parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0139] The above merely provides a specific implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0140] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer programs) for performing the data transmission method in the above embodiments.

[0141] The computer readable storage medium provided by the present application may, for example, be a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system or device, or any combination of the above. More specific examples of the computer readable storage medium can include, but are not limited to, an electric connection having one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM or flash memory), an optical fiber, a portable compact disk read only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present embodiment, the computer readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency), etc., or any suitable combination of the above.

[0142] The above computer readable storage medium can be contained in the data transmission device, or can exist separately without being assembled into the data transmission device.

[0143] The above computer readable storage medium carries one or more programs, which, when executed by the data transmission device, cause the data transmission device to: acquire a service requirement of a third party system, and configure a core service script according to the service requirement; receive an interface input / output parameter configuration instruction input by a user, and configure an interface input / output parameter according to the interface input / output parameter configuration instruction; determine a third party system interfacing mode based on the interface input / output parameter; and interface the third party system according to the interface input / output parameter, the third party system interfacing mode, and the core service script, and perform service data transmission.

[0144] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0145] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flow diagrams, and combinations thereof, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or combinations of special purpose hardware and computer instructions.

[0146] The modules involved in the embodiments of the present application can be implemented in software or hardware. In some cases, the names of the modules do not constitute a limitation on the modules themselves.

[0147] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e. computer programs) for executing the above data transmission method, and can solve the technical problem of data transmission. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the data transmission method provided by the above embodiments, which will not be repeated here.

[0148] The application further provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the data transmission method as described above.

[0149] The computer program product provided by the application can solve the technical problem of data transmission. Compared with the prior art, the beneficial effects of the computer program product provided by the application are the same as those of the data transmission method provided by the above-described embodiments, and are not described here.

[0150] The above only describes some embodiments of the application, and does not limit the patent scope of the application. Any equivalent structural transformation made by using the content of the specification and drawings, or direct / indirect application in other related technical fields under the technical concept of the application is included in the patent protection scope of the application.

Claims

1. A data transmission method, characterized in that, It is applied to a data transmission device, which adopts a distributed full-stack dynamic integration architecture, including a Redis remote dictionary service, a Quartz open-source job scheduling framework, a progressive JavaScript framework, a rapid development framework based on the Spring framework, and a JavaScript engine. The data transmission method includes: Obtain the business requirements of the third-party system and configure the core business scripts according to the business requirements; Receive user input of interface input / output parameter configuration instructions, and configure interface input / output parameters according to the interface input / output parameter configuration instructions; The method of connecting to the third-party system is determined based on the interface input and output parameters. Based on the interface input / output parameters, the third-party system integration method, and the core business script, the business data is integrated with the third-party system and transmitted, including: If the third-party system is connected passively, the callable interface is determined based on the interface input and output parameters, the core business script is parsed, and business data is sent to the third-party system through the callable interface. If the third-party system is connected via active connection, the third-party interface is called periodically based on the interface input and output parameters to execute the core business script and receive business data sent by the third-party system through the third-party interface, including: configuring the pre-business script and executing the pre-business script periodically based on the distributed full-stack dynamic integration architecture; If the pre-processing script is executed successfully, then based on the interface input and output parameters, it is determined whether to perform a signature operation on the request data after the execution of the pre-processing script. If the signature operation is performed and the signature operation is successful, then a request to call the third-party interface is initiated. If the request to call the third-party interface is successful, the core business script is executed, and business data sent by the third-party system is received through the third-party interface.

2. The data transmission method as described in claim 1, characterized in that, The step of receiving the interface input / output parameter configuration instruction from the user and configuring the interface input / output parameters according to the interface input / output parameter configuration instruction includes: Receive user input of interface input / output parameter configuration instructions, which can be input via interface, file configuration, or database storage. Associate the interface input / output parameter configuration instructions with the business requirements, and configure and adjust the interface input / output parameters according to the interface input / output parameter configuration instructions and business scenarios.

3. The data transmission method as described in claim 1, characterized in that, The steps of determining the callable interface based on the interface input / output parameters, parsing the core business script, and sending business data to the third-party system through the callable interface include: Receive interface call requests sent by third-party systems and determine the callable interfaces based on the interface input and output parameters; The pre-filter determines whether the interface call request is valid and whether the callable interface exists. If the interface call request is valid and the callable interface exists, then determine whether to perform a signature verification operation on the interface call request based on the interface input and output parameters; If a signature verification operation is performed and the signature verification operation is successful, the core business script is parsed, the business data is determined based on the result of parsing the core business script, and the business data is encrypted using preset encryption parameters. The encrypted business data is sent to a third-party system through the callable interface.

4. The data transmission method as described in claim 1, characterized in that, Before the step of connecting to the third-party system and transmitting data based on the interface input / output parameters, the third-party system integration method, and the core business script, the following is also included: Receive encryption algorithm configuration instructions, and select at least one encryption method based on the encryption algorithm configuration instructions; The encryption parameters are set according to the encryption method and the encryption algorithm configuration instructions.

5. The data transmission method as described in claim 4, characterized in that, The interface input / output parameters and the encryption parameters are stored in the configuration database. Log data generated by the third-party system is stored in the log database. The business data is stored in the business database. The business database is dynamically configured by multiple data sources. The configuration database, the business database, and the log database are isolated from each other.

6. A data transmission device, characterized in that, The data transmission device adopts a distributed full-stack dynamic integration architecture, which includes a Redis remote dictionary service, the Quartz open-source job scheduling framework, a progressive JavaScript framework, a rapid development framework based on the Spring framework, and a JavaScript engine. The data transmission device includes: The core business script logic configuration module is used to obtain the business requirements of third-party systems and configure the core business scripts according to the business requirements. The interface configuration module is used to receive interface input / output parameter configuration instructions from the user, and configure the interface input / output parameters according to the interface input / output parameter configuration instructions. The third-party system integration module is used to determine the integration method of the third-party system based on the interface input / output parameters, and to integrate with the third-party system and transmit business data according to the interface input / output parameters, the third-party system integration method, and the core business script. The module is also used to determine a callable interface based on the interface input / output parameters if the third-party system integration method is passive, parse the core business script, and send business data to the third-party system through the callable interface if the integration method is active, and periodically call the third-party interface based on the interface input / output parameters to execute the core business script and receive business data sent by the third-party system through the third-party interface. The module is also used to configure a pre-processing business script and periodically execute the pre-processing business script based on the distributed full-stack dynamic integration architecture. If the pre-processing business script executes successfully, it determines whether to perform a signature operation on the request data after the execution of the pre-processing business script based on the interface input / output parameters. If the signature operation is performed and successful, a request to call the third-party interface is initiated. If the request to call the third-party interface is successful, the core business script is executed, and business data sent by the third-party system is received through the third-party interface.

7. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the data transmission method as described in any one of claims 1 to 5.

8. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the data transmission method as described in any one of claims 1 to 5.

Images