Data docking system based on API

Abstract

The invention discloses a data docking system based on an API (Application Program Interface), which comprises a task management end, a task scheduling module, a data synchronization module, a data exchange module and a data persistence module, and is characterized in that the development process of system docking is simplified by using a reflection technology, dynamic type processing, an automatic mapping mechanism and an encryption technology through a modularized and standardized design thought, and the data docking efficiency is improved. The operation and maintenance cost is reduced, the data processing efficiency, accuracy and safety are improved, and efficient and safe data interaction between banks and insurance companies is achieved. The system provided by the invention not only improves the efficiency and security of data interaction, but also provides flexible expansibility and maintainability, and adapts to constantly changing business requirements. According to the invention, an insurance company can perform data interaction with different banks more conveniently and safely, and the business efficiency and customer satisfaction are improved.

Description

Technical Field

[0001] The present invention belongs to the field of data docking interaction, and in particular relates to an API-based data docking system. Background Art

[0002] With the rapid development of the financial industry, insurance companies and different banks are cooperating increasingly closely, and both sides have extensive cooperation needs in data exchange. However, due to the differences in the construction standards of various bank systems, traditional data interaction methods mainly rely on file transfer and manual processing, which have the following problems:

[0003] Inefficient data transmission: Traditional file transmission methods have many drawbacks. For example, data needs to be exported from the source system, converted into a file format, and then transmitted to the target system through the network. This series of steps not only increases the complexity of data processing, but also prolongs the total time of data transmission, seriously affecting the real-time and response speed of the business.

[0004] Poor security: Security cannot be guaranteed during file transmission, and data is vulnerable to cyber attacks, such as data being intercepted, tampered with, or leaked, which poses a serious threat to the business security of financial institutions. Especially in the financial field, data security is directly related to the customer's financial security and privacy protection. Therefore, it is crucial to improve the security of data interaction.

[0005] High error rate: Manual data processing is not only time-consuming but also prone to errors, especially when dealing with large amounts of complex data. Increased error rates can lead to business interruptions, customer complaints, and even legal disputes. Data accuracy is critical to the normal operation of financial services, and any data errors can result in immeasurable losses.

[0006] Insufficient flexibility: Traditional data interaction methods are difficult to adapt to rapidly changing business needs, and have poor scalability and flexibility. With the continuous innovation of financial services and the diversification of customer needs, data interaction methods need to be able to respond quickly to changes and support seamless connection of data in different formats and from different sources to meet the needs of business development.

[0007] High labor costs: Manual data processing requires a lot of human resources, which not only increases the operating costs of financial institutions, but also limits the ability to expand business. In the fiercely competitive financial market, reducing labor costs and improving automation levels are the key to improving competitiveness.

[0008] With the development of emerging technologies such as cloud computing, big data, and blockchain, the way of data exchange is also evolving. These technologies provide new possibilities for efficient and secure data interaction. API technology allows different systems to exchange data through standardized interfaces. By defining clear request and response formats, API can achieve efficient and reliable data transmission. However, existing API technology still has problems such as high complexity, lack of flexibility, high labor costs, and security risks, which makes it difficult to meet the needs of modern financial services. Summary of the invention

[0009] The purpose of the present invention is to provide an API-based data docking system, which simplifies the development process of system docking, reduces operation and maintenance costs, improves data processing efficiency, accuracy and security, and realizes efficient and secure data interaction between banks and insurance companies through modular and standardized design ideas and the use of reflection technology, dynamic type processing, automatic mapping mechanism and encryption technology.

[0010] The present invention provides an API-based data docking system, including a task management terminal, a task scheduling module, a data synchronization module, a data exchange module and a data persistence module;

[0011] The task management end is linked to the task scheduling module to manage and schedule data processing tasks; after the operator uses the task management end to input the task instruction, the task information is stored in the task queue; the task scheduling module triggers the task according to the information in the task queue and passes the task information to the data synchronization module; after the data synchronization module receives the task information, it inputs the information into the data exchange module; the data exchange module includes an encryption and decryption submodule connection, when the task information is received, the encryption and decryption submodule is used for encryption processing, the API is called to transfer the data, and the data obtained by the exchange is decrypted by the encryption and decryption submodule and then passed to the data synchronization module; the data synchronization module passes the received data to the data persistence module, the data persistence module persists the data and returns the result to the data synchronization module; finally, the data synchronization module records the data synchronization results and the data persistence results.

[0012] The task management end links to the task scheduling module to manage and schedule data processing tasks, including the following functions:

[0013] Task creation: The operator enters the task information, interface information configuration and data persistence configuration through the user interface on the task management end, including the task name, task description, execution time, execution frequency, execution conditions, interface address and interface description; the task management end stores this information in the task queue and waits for scheduling; the task management end also has a task preview function, and the operator can preview the task information before creating the task;

[0014] Task editing: The created tasks have editable properties, and the execution time, execution frequency, execution conditions, interface address, and interface description information of the tasks can be modified; the task management end updates the modified task information to the task queue and waits for scheduling; the task management end has a real-time update function, and updates the task information in real time before the task is executed;

[0015] Task deletion: The created task has the attribute of being deletable. The task management end deletes the task information and removes the task from the task queue. The task management end has a task deletion confirmation function. Before deleting a task, you need to confirm the deletion of the task information.

[0016] Task priority setting: The created tasks support task priority setting, which enables tasks to be scheduled in order of priority;

[0017] Task retry: The task management module has a task retry mechanism. When a task fails to execute, the task management module automatically retries the corresponding task. At the same time, the task retry mechanism has a task retry confirmation function, and the task information needs to be confirmed before the task is retried.

[0018] The task scheduling module triggers tasks regularly according to the task information in the task queue and passes the tasks to the data synchronization module for execution; the task scheduling module has a task trigger confirmation function, and the operator needs to confirm the task information before triggering the task; if the last triggered task has not been completed, the current task will not be triggered.

[0019] The data synchronization module is responsible for data reception and transmission, data processing, status monitoring and error handling, and result recording, specifically:

[0020] Data reception and transmission: The data synchronization module receives task information from the task scheduling module, including task name, task description, execution time, execution frequency, execution conditions, interface address, and interface description; then verifies the received task information. If the task information verification fails, the error information is recorded and the task management end is notified; if the task information verification succeeds, the data synchronization process is started according to the task content; if the previous task has not been completed, the new task is not triggered to ensure the orderly execution of the tasks;

[0021] Data processing: Based on the task information content, use the data persistence module to extract or send the required data from the data source; verify the extracted data; the verification content includes data format, data range, and data consistency;

[0022] Status monitoring and error handling: The data synchronization module monitors the data transmission status in real time, including the progress of data transmission and the status of data processing; when abnormal conditions are detected, including data transmission failure and data format error, the preset error handling measures are adopted; error handling measures include retry, logging and alarm notification;

[0023] Result recording: The data synchronization module records the results obtained by the data persistence module, including the status of data transmission and the results of data processing.

[0024] The data persistence module is responsible for persisting and saving data, which includes the following steps:

[0025] Convert the instance class objects in the data into a preset format through reflection technology to obtain serialized data;

[0026] Save the serialized data to the database submodule.

[0027] The specific reflection technology is as follows: In .Net, the System.Type class is obtained by calling the Type() method on the instance class, and then the GetProperty or GetField function is called on this System.Type to return a PropertyInfo object or FieldInfo object, which contains detailed information about the property. Finally, the GetValue or SetValue function is called to get or set the value of the property, thus completing data serialization and deserialization in a round trip.

[0028] The automatic mapping mechanism is also applied in the persistence process, and the mapping relationship between the interface data fields and the serialized fields is established through configuration;

[0029] The data persistence module also includes a database submodule; the database submodule includes business information; the persistence results processed by the data persistence module are also stored in the database submodule.

[0030] The data exchange module is responsible for calling the API interface for data interaction and implementing the encryption and decryption operations of sending and receiving data; the operation of the data exchange module includes the following steps:

[0031] The encryption and decryption submodule in the data exchange module generates the keys required by the SM4 algorithm, including encryption keys and decryption keys; the encryption and decryption submodule uses the SM4 encryption algorithm to encrypt the data submitted by the data synchronization module to generate encrypted data;

[0032] Call the API interface to pass the encrypted data to the target system, including data format, data content, and data signature;

[0033] Obtain the target system's feedback on the encrypted data transmitted by the data exchange module to obtain response data; the response data includes processing results and error information; parse the response data according to the response data format to obtain response data information;

[0034] Use the SM4 decryption key to decrypt the response data information to obtain the decrypted data;

[0035] Pass the decrypted data to the data synchronization module.

[0036] The present invention discloses a data docking system based on API, which not only improves the efficiency and security of data interaction, but also provides flexible scalability and maintainability, and adapts to the ever-changing business needs. Through the present invention, insurance companies can more conveniently and safely interact with different banks to improve business efficiency and customer satisfaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 It is a schematic diagram of the structure of the system of the present invention. DETAILED DESCRIPTION

[0038] The present invention provides a data docking system based on API, the structural diagram of which is as follows Figure 1 As shown, it includes a task management terminal, a task scheduling module, a data synchronization module, a data exchange module and a data persistence module;

[0039] The task management end is linked to the task scheduling module to manage and schedule data processing tasks; after the operator uses the task management end to input the task instruction, the task information is stored in the task queue; the task scheduling module triggers the task according to the information in the task queue and passes the task information to the data synchronization module; after the data synchronization module receives the task information, it inputs the information into the data exchange module; the data exchange module includes an encryption and decryption submodule connection, when the task information is received, the encryption and decryption submodule is used for encryption processing, the API is called to transfer the data, and the data obtained by the exchange is decrypted by the encryption and decryption submodule and then passed to the data synchronization module; the data synchronization module passes the received data to the data persistence module, the data persistence module persists the data and returns the result to the data synchronization module; finally, the data synchronization module records the data synchronization results and the data persistence results.

[0040] The task management end links to the task scheduling module to manage and schedule data processing tasks, including the following functions:

[0041] Task creation: The operator enters the task information, interface information configuration and data persistence configuration through the user interface on the task management end, including the task name, task description, execution time, execution frequency, execution conditions, interface address and interface description; the task management end stores this information in the task queue and waits for scheduling; the task management end also has a task preview function, and the operator can preview the task information before creating the task;

[0042] Task editing: The created tasks have editable properties, and the execution time, execution frequency, execution conditions, interface address, and interface description information of the tasks can be modified; the task management end updates the modified task information to the task queue and waits for scheduling; the task management end has a real-time update function, and updates the task information in real time before the task is executed;

[0043] Task deletion: The created task has the attribute of being deletable. The task management end deletes the task information and removes the task from the task queue. The task management end has a task deletion confirmation function. Before deleting a task, you need to confirm the deletion of the task information.

[0044] Task priority setting: The created tasks support task priority setting, which enables tasks to be scheduled in order of priority;

[0045] Task retry: The task management module has a task retry mechanism. When a task fails to execute, the task management module automatically retries the corresponding task. At the same time, the task retry mechanism has a task retry confirmation function, and the task information needs to be confirmed before the task is retried.

[0046] The task scheduling module triggers tasks regularly according to the task information in the task queue and passes the tasks to the data synchronization module for execution; the task scheduling module has a task trigger confirmation function, and the operator needs to confirm the task information before triggering the task; if the last triggered task has not been completed, the current task will not be triggered.

[0047] The data synchronization module is responsible for data reception and transmission, data processing, status monitoring and error handling, and result recording, specifically:

[0048] Data reception and transmission: The data synchronization module receives task information from the task scheduling module, including task name, task description, execution time, execution frequency, execution conditions, interface address, and interface description; then verifies the received task information. If the task information verification fails, the error information is recorded and the task management end is notified; if the task information verification succeeds, the data synchronization process is started according to the task content; if the previous task has not been completed, the new task is not triggered to ensure the orderly execution of the tasks;

[0049] Data processing: Based on the task information content, use the data persistence module to extract or send the required data from the data source; verify the extracted data; the verification content includes data format, data range, and data consistency;

[0050] Status monitoring and error handling: The data synchronization module monitors the data transmission status in real time, including the progress of data transmission and the status of data processing; when abnormal conditions are detected, including data transmission failure and data format error, the preset error handling measures are adopted; error handling measures include retry, logging and alarm notification;

[0051] Result recording: The data synchronization module records the results obtained by the data persistence module, including the status of data transmission and the results of data processing.

[0052] The data persistence module is responsible for persisting and saving data, which includes the following steps:

[0053] Convert the instance class objects in the data into a preset format through reflection technology to obtain serialized data;

[0054] Save the serialized data to the database submodule.

[0055] The specific reflection technology is as follows: In .Net, the System.Type class is obtained by calling the Type() method on the instance class, and then the GetProperty or GetField function is called on this System.Type to return a PropertyInfo object or FieldInfo object, which contains detailed information about the property. Finally, the GetValue or SetValue function is called to get or set the value of the property, thus completing data serialization and deserialization in a round trip.

[0056] Reflection technology no longer relies on a fixed data model, allowing the persistence process to adapt to different data structure changes, reducing the coupling of the system. At the same time, it automatically adjusts the data model according to actual business needs, enhancing maintainability and scalability.

[0057] The automatic mapping mechanism is also applied in the persistence process, and the mapping relationship between the interface data fields and the serialized fields is established through configuration;

[0058] The system uses the reflection mechanism to automatically identify, fill and convert the corresponding data fields. This process significantly reduces the complexity of manual coding and improves development efficiency. In addition, through dynamic mapping, developers do not need to perform additional coding or maintain a large number of configuration files, thereby simplifying the development process and reducing the probability of errors.

[0059] The data persistence module also includes a database submodule; the database submodule includes business information; the persistence results processed by the data persistence module are also stored in the database submodule.

[0060] The data exchange module is responsible for calling the API interface for data interaction and implementing the encryption and decryption operations of sending and receiving data; the operation of the data exchange module includes the following steps:

[0061] The encryption and decryption submodule in the data exchange module generates the keys required by the SM4 algorithm, including encryption keys and decryption keys; the encryption and decryption submodule uses the SM4 encryption algorithm to encrypt the data submitted by the data synchronization module to generate encrypted data;

[0062] Call the API interface to pass the encrypted data to the target system, including data format, data content, and data signature;

[0063] Obtain the target system's feedback on the encrypted data transmitted by the data exchange module to obtain response data; the response data includes processing results and error information; parse the response data according to the response data format to obtain response data information;

[0064] Use the SM4 decryption key to decrypt the response data information to obtain the decrypted data;

[0065] Pass the decrypted data to the data synchronization module.

[0066] The present invention is further described below with reference to an embodiment:

[0067] The system needs to synchronize business information with the bank every day. The following is the workflow of the data synchronization module:

[0068] Task reception: The operator creates a data synchronization task through the task management terminal. The task content includes synchronization of business information, synchronization frequency of once a day, execution time of 23:30 every day, etc.

[0069] Task verification: After receiving the task, the data synchronization module verifies the legality and validity of the task.

[0070] Task execution: The data synchronization module checks whether there are any unfinished tasks. If not, it starts the data synchronization process.

[0071] Data preparation: Based on the task content, the data synchronization module uses the data persistence module to extract the business information that needs to be synchronized after deserialization from the database, including the policy number, effective date, policy status, etc.

[0072] Data verification: The data synchronization module verifies the extracted business information to ensure the integrity and accuracy of the data.

[0073] Data encryption: The data synchronization module passes the verified business information to the data exchange module, and the data exchange module uses the SM4 encryption algorithm to encrypt the data.

[0074] Data transmission: The data exchange module transmits the encrypted customer information to the target bank system through the API interface, and the request format is JSON.

[0075] Response reception: After the bank system processes the request, it returns the response data through the API interface.

[0076] Response parsing: The data exchange module parses the response data and extracts the processing results and error information.

[0077] Data decryption: The data exchange module uses the SM4 decryption algorithm to decrypt the response data and restore the original processing results.

[0078] Data processing: The data exchange module will process the decrypted data and pass it to the data synchronization module for subsequent processing.

[0079] Data transfer: The data synchronization module transfers the decrypted processing results to the data persistence module.

[0080] Data storage: The data persistence module uses reflection technology to dynamically identify and process data types, serialize data, and store the processing results in the local database.

[0081] Persistence result feedback: The data persistence module feeds back the persistence result to the data synchronization module, including information on storage success or failure.

Claims

1. A data docking system based on API, characterized in that: It includes task management terminal, task scheduling module, data synchronization module, data exchange module and data persistence module; The task management terminal is linked to the task scheduling module to manage and schedule data processing tasks. After the operator uses the task management terminal to input the task instructions, the task information is stored in the task queue. The task scheduling module triggers the task according to the information in the task queue and transmits the task information to the data synchronization module; after receiving the task information, the data synchronization module inputs the information into the data exchange module; the data exchange module includes an encryption and decryption submodule connection, when receiving the task information, the encryption and decryption submodule is used to encrypt the data, the API is called to transmit the data, and the data obtained by the exchange is decrypted by the encryption and decryption submodule and then transmitted to the data synchronization module; The data synchronization module passes the received data to the data persistence module, the data persistence module persists the data and returns the result to the data synchronization module; finally, the data synchronization module records the data synchronization result and the data persistence result.

2. The API-based data docking system according to claim 1, characterized in that: The task management end links to the task scheduling module to manage and schedule data processing tasks, including the following functions: Task creation: The operator enters the task information, interface information configuration and data persistence configuration through the user interface on the task management end, including the task name, task description, execution time, execution frequency, execution conditions, interface address and interface description; the task management end stores this information in the task queue and waits for scheduling; the task management end also has a task preview function, and the operator can preview the task information before creating the task; Task editing: The created tasks have editable properties, and the execution time, execution frequency, execution conditions, interface address, and interface description information of the tasks can be modified; The task management end updates the modified task information to the task queue and waits for scheduling; the task management end has a real-time update function, which updates the task information in real time before the task is executed; Task deletion: The created task has the attribute of being deletable. The task management end deletes the task information and removes the task from the task queue. The task management end has a task deletion confirmation function. Before deleting a task, you need to confirm the deletion of the task information. Task priority setting: The created tasks support task priority setting, which enables tasks to be scheduled in order of priority; Task retry: The task management module has a task retry mechanism. When a task fails to execute, the task management module automatically retries the corresponding task. At the same time, the task retry mechanism has a task retry confirmation function, and the task information needs to be confirmed before the task is retried.

3. The API-based data docking system according to claim 1, characterized in that: The task scheduling module triggers tasks regularly according to the task information in the task queue and passes the tasks to the data synchronization module for execution; The task scheduling module has a task trigger confirmation function. The operator needs to confirm the task information before triggering the task; if the last triggered task has not been completed, the current task will not be triggered.

4. The API-based data docking system according to claim 1, characterized in that: The data synchronization module is responsible for data reception and transmission, data processing, status monitoring and error handling, and result recording, specifically: Receiving and sending data: The data synchronization module receives task information from the task scheduling module, including task name, task description, execution time, execution frequency, execution condition, interface address, and interface description; then verifies the received task information. If the task information verification fails, the error information is recorded and the task management end is notified; If the task information is successfully verified, the data synchronization process is started according to the task content; If the previous task has not been completed, no new task will be triggered to ensure the orderly execution of tasks; Data processing: Based on the task information content, use the data persistence module to extract or send the required data from the data source; verify the extracted data; the verification content includes data format, data range, and data consistency; Status monitoring and error handling: The data synchronization module monitors the data transmission status in real time, including the progress of data transmission and the status of data processing; when an abnormal situation is detected, including data transmission failure and data format error, the preset error handling measures are adopted; Error handling measures include retry, logging, and alarm notification; Result recording: The data synchronization module records the results obtained by the data persistence module, including the status of data transmission and the results of data processing.

5. The API-based data docking system according to claim 1, characterized in that: The data persistence module is responsible for persisting and saving data, which includes the following steps: Convert the instance class objects in the data into a preset format through reflection technology to obtain serialized data; Save the serialized data to the database submodule.

6. The API-based data docking system according to claim 5, characterized in that: The specific reflection technology is as follows: In .Net, the System.Type class is obtained by calling the Type() method on the instance class, and then the GetProperty or GetField function is called on this System.Type to return a PropertyInfo object or FieldInfo object, which contains detailed information about the property. Finally, the GetValue or SetValue function is called to get or set the value of the property, thus completing data serialization and deserialization in a round trip. The automatic mapping mechanism is also applied in the persistence process, and the mapping relationship between the interface data fields and the serialized fields is established through configuration; The data persistence module also includes a database submodule; the database submodule includes business information; the persistence results processed by the data persistence module are also stored in the database submodule.

7. The API-based data docking system according to claim 1, characterized in that: The data exchange module is responsible for calling the API interface for data interaction and implementing the encryption and decryption operations of sending and receiving data; the operation of the data exchange module includes the following steps: The encryption and decryption submodule in the data exchange module generates the keys required by the SM4 algorithm, including encryption keys and decryption keys; the encryption and decryption submodule uses the SM4 encryption algorithm to encrypt the data submitted by the data synchronization module to generate encrypted data; Call the API interface to pass the encrypted data to the target system, including data format, data content, and data signature; Obtaining feedback from the target system on the encrypted data transmitted by the data exchange module, and obtaining response data; The response data includes processing results and error information; the response data information is obtained by parsing according to the response data format; Use the SM4 decryption key to decrypt the response data information to obtain the decrypted data; Pass the decrypted data to the data synchronization module.

Images