General cooperative channel video file processing method, system and device

Abstract

The application provides a general cooperative channel image file processing method, system and device. The system comprises: a business access interface, configured to receive a file processing request initiated by at least one business invoker, and call back a system processing result to the corresponding business invoker; a unified gateway module, configured to authenticate, limit flow and route distribute the received file processing request; a core service module, configured to receive the file processing request routed and distributed by the unified gateway module, acquire an image file from a cooperative channel party system according to the file processing request, and perform file processing on the image file; an adaptation module, configured to provide the core service module with a unified service call and file processing interface for communication with different cooperative channel party systems; and a storage module, connected with the core service module and the adaptation module, configured to centrally store image files, signature files and structured data required for system operation.

Description

Technical Field

[0001] This invention relates to the field of financial technology, and more specifically, to a method, system, and apparatus for processing image files in a general cooperative channel. Background Technology

[0002] Currently, when businesses connect with banks and financial institutions to exchange image documents (such as contracts, images, and vouchers), they typically use a decentralized approach. Specifically, for each partner, the business needs to develop its own separate module for document acquisition, signature processing, and document return. This point-to-point, customized development model results in high system development costs and long implementation cycles. More importantly, when a business needs to add new partner channels, it must repeat the aforementioned customized development work, making rapid system expansion difficult and resulting in poor overall scalability. Summary of the Invention

[0003] In view of the deficiencies of the prior art, the present invention provides a universal collaborative channel image file processing method, system and apparatus, which can achieve universal adaptation and file processing for different collaborative channels.

[0004] On one hand, embodiments of the present invention provide a universal collaborative channel image file processing system, which includes: The business access interface is used to: receive file processing requests initiated by at least one business caller, wherein the request parameters carried by the file processing request include at least channel identifier, business number, file type, authentication parameters, and callback address; and to send the system processing result back to the corresponding business caller. The unified gateway module is connected to the service access interface and is used to authenticate, limit the rate, and route the received file processing requests. The core service module, connected to the unified gateway module, is used to receive the file processing request routed and distributed by the unified gateway module, obtain image files from the cooperative channel system according to the file processing request, and perform file processing on the image files; The adapter module connects to the core service module and multiple different cooperative channel systems respectively, so as to provide the core service module with a unified service call and file processing interface for communicating with different cooperative channel systems; The storage module, connected to the core service module and the adapter module, is used to centrally store image files, signed files, and structured data required for system operation.

[0005] In some implementations, the unified gateway module includes: The interface authentication unit is used to store the key information of each business caller and verify the authentication parameters carried in the file processing request to confirm the legitimacy of the business party's identity. The request rate limiting unit is used to configure an independent call threshold for each business caller and to execute a rate limiting strategy when the number of requests exceeds the call threshold within a unit of time. The request routing unit is used to distribute the file processing request to the core service module according to the channel identifier in the file processing request. The logging unit is used to record the request parameters, response results, call time, time consumed, and calling IP of the file processing request for troubleshooting and auditing. The exception interception unit is used to capture and standardize the processing of various exceptions during system operation and return standard error information.

[0006] In some implementations, the core service module includes independently decoupled channel configuration management submodule, file acquisition submodule, contract signing submodule, file return submodule, and task management submodule.

[0007] The task management submodule is configured to: receive file processing requests forwarded by the unified gateway module and create file processing tasks; generate a globally unique identifier for the task and initialize the task status; during the execution of the file processing tasks by the file acquisition submodule, contract signing submodule, and file return submodule, update and record the current status of the task, the completion time of each submodule, and the results in real time; and, according to the callback address, send the task processing results back to the business caller through the business access interface.

[0008] In some implementations, the task management submodule is also configured to perform at least one of the following processes: providing task details based on user input, initiating retry for failed tasks, and terminating operations on tasks that are currently being executed.

[0009] In some implementations, the channel configuration management submodule is used to store configuration information for each cooperating channel, the configuration information including at least file acquisition method, signature rules and file return method.

[0010] In some implementations, the file acquisition submodule is used to perform the file processing task, including: Based on the channel identifier, obtain the corresponding file acquisition method from the channel configuration management submodule; According to the file acquisition method described above, the image file is retrieved from the corresponding partner channel system through the adaptation module. Perform pre-entry checks on the retrieved image files, including format verification, size verification, and integrity verification. The image files are renamed according to the unified naming rules, and the image files are deduplicated based on the channel identifier, business number, and file type. The verified and deduplicated image files are uploaded to the original file directory of the storage module.

[0011] In some implementations, the contract signing submodule is used to perform the document processing task, including: The image file is obtained from the storage module and transmitted by the file acquisition submodule, and the image file is uniformly converted into a standard format file by the adaptation module. According to the signature rules in the channel configuration management submodule, perform electronic signature operations on the standard format file; Upload the signed document to the signed document directory of the storage module.

[0012] In some implementations, the file return submodule is used to perform the file processing task, including: The system retrieves the signed document from the contract signing submodule from the storage module, and sends the document back to the corresponding cooperating channel system through the adaptation module according to the file return method in the channel configuration management submodule, and verifies the return result; if the return fails, it automatically retryes according to the configured number of retries and interval.

[0013] In some implementations, the core service module further includes a monitoring and alarm submodule, which is used to: monitor the operational health status and task status of the system in real time, and trigger alarm processing for tasks that exceed a preset threshold in the number of timeouts or failures; record alarm information and system operation logs, and generate monitoring reports that can be exported.

[0014] In some implementations, the adapter module includes: API (Application Programming Interface) adapters are used to uniformly adapt API interfaces from different cooperation channels; An SFTP (SSH File Transfer Protocol) adapter is used to uniformly adapt the connection, file retrieval, and upload logic of different SFTP servers. A file format adapter is used to convert image files of different formats into standard format files.

[0015] On the other hand, embodiments of the present invention provide a general cooperative channel image file processing method, applicable to the system described in any embodiment of the present invention, which includes the following steps: Receive file processing requests initiated by business callers through the business access interface; The unified gateway module authenticates and limits the file processing requests, and then routes them to the core service module after authentication and rate limiting. According to the file processing request, the core service module obtains the image file from the cooperative channel system through the adaptation module and performs file processing on the image file. The adaptation module provides the core service module with a unified service call and file processing interface for communicating with different cooperative channel systems. After processing is complete, the processing result is sent back to the business caller through the business access interface.

[0016] Furthermore, embodiments of the present invention provide a computer program product comprising a computer program that, when executed by a processor, implements the steps of the method described in any embodiment of the present invention.

[0017] In addition, embodiments of the present invention also provide a computer device, which includes: A memory on which computer programs are stored; A processor that, when executing the computer program, implements the steps of the method described in any embodiment of the present invention.

[0018] According to the embodiments of the present invention, the present invention can achieve the following beneficial effects: The system of this invention, through an adaptation module (including an API adapter, an SFTP adapter, and a file format adapter), shields the differences in interface and file format between different cooperation channels, uniformly connecting to the systems of different cooperation channels. This enables "one-time development, multi-channel adaptation," eliminating the need for custom development when adding new cooperation channels. Integration can be completed simply by configuring relevant parameters through the channel configuration management submodule, significantly reducing development cycle and maintenance costs. Furthermore, business users do not need to concern themselves with the underlying interface details; they only need to input core parameters to trigger the entire process. Furthermore, the system of this invention automates the entire process of file acquisition, format verification, signing, return, and task management through its core service module, eliminating the need for manual intervention. Moreover, by setting up monitoring and alarm sub-modules and task management sub-modules, it records log information of the entire file processing process in real time, monitors task execution status and system health status, and automatically triggers a retry mechanism and alarm handling when an anomaly occurs, facilitating timely handling by relevant personnel and solving the problems of difficult anomaly troubleshooting and untimely handling in existing technologies. Furthermore, the sub-modules of the core service module are independently decoupled, allowing for the expansion of individual modules according to business needs (such as adding a signing mode or a return method), facilitating adaptation to future business expansion requirements.

[0019] The above aspects, features, advantages, etc. of the present invention will be described in detail below with reference to the accompanying drawings. Attached Figure Description

[0020] Figure 1 This is a schematic block diagram illustrating a general cooperative channel image file processing system according to an embodiment of the present invention.

[0021] Figure 2 This is a schematic block diagram illustrating a unified gateway module according to an embodiment of the present invention.

[0022] Figure 3 This is a schematic block diagram illustrating the core service modules of an embodiment of the present invention.

[0023] Figure 4 This is a schematic block diagram illustrating the adapter module of an embodiment of the present invention.

[0024] Figure 5 This is a schematic flowchart illustrating a general cooperative channel image file processing method according to an embodiment of the present invention.

[0025] Figure 6 This is a schematic block diagram illustrating a computer device according to an embodiment of the present invention. Detailed Implementation

[0026] The exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be understood that the present invention can be implemented in various forms and is not limited to the specific embodiments described herein or shown in the accompanying drawings.

[0027] It should be understood that the terms “comprising,” “including,” and “having,” etc., are used herein to indicate the presence of certain features, steps, operations, elements, and / or components, but do not exclude the presence or addition of other features, steps, operations, elements, components, or combinations thereof. Unless explicitly defined by the context, the terms “first,” “second,” and similar terms do not indicate any priority or order, but are used only to distinguish different elements in the description.

[0028] To further clarify, the term "connection" and related terms used in this document refer to the direct or indirect connection between two components. Such connections can include electrical connections or communication connections, etc.

[0029] Reference Figure 1 The present invention provides a universal collaborative channel image file processing system. The system includes a business access interface 210, a unified gateway module 220, a core service module 230, an adaptation module 240, and a storage module 250.

[0030] In this embodiment of the invention, the service access interface 210 is configured to: receive file processing requests initiated by at least one service caller, wherein the request parameters carried by the file processing request include at least a channel identifier, a service number, a file type, authentication parameters, and a callback address; and to callback the system processing result to the corresponding service caller. The service access interface 210 constitutes the interaction entry point between the system of this invention and the service caller, and can adopt a standardized API interface design, configured to support parallel access by multiple service callers, and provide both synchronous and asynchronous request modes.

[0031] In some implementations, the service access interface 210 receives a file processing request (which may include parameters such as channel ID, service number, file type, and callback address) from a service caller and forwards the request to the unified gateway module 220. Simultaneously, it receives the task processing result returned by the core service module 230 and, according to the callback address specified by the service caller, sends the result back to the corresponding service caller. In some implementations, the service access interface 210 is configured with an IP whitelist to allow only service callers on the whitelist to access the interface, thereby improving interface security.

[0032] In this embodiment of the invention, the unified gateway module is connected to the service access interface and is used to authenticate, limit, and route the received file processing requests.

[0033] In some implementations, refer to Figure 2 The unified gateway module 220 includes an interface authentication unit 221, used to store the key information of each service caller and verify the authentication parameters carried in the file processing request to confirm the legitimacy of the service caller's identity. For example, the interface authentication unit 221 is configured to: store the AppKey and AppSecret of the service caller; after receiving a request forwarded by the service access interface 210, verify the X-AppKey, X-Sign, and X-Timestamp parameters in the request header to confirm the legitimacy of the service caller's identity and reject illegal requests. Illegal requests include requests that fail verification according to the authentication parameters.

[0034] Furthermore, the unified gateway module 220 includes a request rate limiting unit 222, used to configure an independent call threshold for each service caller and execute a rate limiting strategy when the number of requests exceeds the call threshold within a unit of time. For example, the request rate limiting unit 222 is configured such that, with a call threshold of 100 times / minute configured for each service caller, subsequent requests from a service caller are rejected when the number of calls from a certain service caller exceeds the threshold. This effectively prevents malicious calls and sudden high-concurrency traffic, avoiding system overload.

[0035] In addition, the unified gateway module 220 further includes: a request routing unit 223, used to distribute the file processing request to the core service module according to the channel identifier in the file processing request; a log recording unit 223, used to record the request parameters, response results, call time, time consumption, and call IP of the file processing request for troubleshooting and auditing; and an anomaly interception unit 224, used to capture and standardize the processing of various anomalies during system operation (such as parameter errors, authentication failures, module call anomalies, etc.), and return standard error information to facilitate troubleshooting by business users.

[0036] In this embodiment of the invention, the core service module 230 is connected to the unified gateway module 220, and is used to receive the file processing request routed and distributed by the unified gateway module 220, obtain image files from the cooperating channel system according to the file processing request, and perform file processing on the image files. The adaptation module 240 is connected to the core service module 230 and multiple different cooperating channel systems respectively, to provide the core service module 230 with a unified service call and file processing interface for communication with different cooperating channel systems.

[0037] In some implementations, refer to Figure 4 The adaptation module 240 includes an API adapter 241, an SFTP adapter 242, and a file format adapter 243.

[0038] The API adapter 241 is used to uniformly adapt API interfaces of different cooperation channels. Specifically, the API adapter 241 is configured to: unify request parameters and response formats, handle exceptions such as timeouts and interface errors during API calls; support at least GET and POST request methods, automatically parse response data from the API of the cooperation channel's system, and extract file download addresses or return results.

[0039] The SFTP adapter 242 is used to uniformly adapt the connection, file retrieval, and upload logic of different SFTP servers. Specifically, the SFTP adapter 242 is configured to adapt to different SFTP server configurations (the configuration includes port, authentication method (password / private key)); handle SFTP connection failures, file read errors, and file upload failures; after retrieving a file, move the remote file to a backup directory, and query the backup directory first when retrieving a file again to avoid repeated retrieval; after uploading a file, verify whether the file was successfully uploaded. The verification process includes: reconnecting to the SFTP server to query the target directory to check if the file exists; comparing the sizes of the local and remote files; calculating and matching the MD5 values ​​of the local and remote files to ensure the file is intact and undamaged; attempting to perform a read-only open operation on the remote file to confirm that the file is not locked and can be accessed normally; if all the above verifications pass, the upload is considered successful; if any verification fails, the upload is considered failed and automatic retry is triggered.

[0040] In some implementations, handling SFTP connection failures may include: before establishing a connection, the SFTP adapter 242 verifies the validity of the IP address, port, username, password, or private key format in the channel configuration; after successful verification, it initiates the connection and sets a connection timeout; if a connection is rejected, times out, network error occurs, or authentication error occurs, the SFTP adapter 242 retryes according to the configured number of retries and an increasing interval; if a connection still cannot be established after retries, it automatically implements circuit breaker protection for the channel, suspends subsequent SFTP operations on the channel to avoid the accumulation of invalid requests, generates an exception log, and triggers an alarm notification.

[0041] In some implementations, the handling of file read anomalies includes: before reading a file, the SFTP adapter checks whether the remote directory exists, whether the file exists, and whether read permissions are available; if the file does not exist or the path is incorrect, the status is recorded and the system waits for the next scheduling cycle without triggering an anomaly alarm; if the file is read incompletely due to network interruption or server disconnection, the breakpoint resume mechanism is automatically enabled, and the file length and MD5 value are checked after the read is completed; if the file is corrupted, has insufficient permissions, or is locked, the file is marked as read abnormal, moved to the abnormal directory, and not proceeded to the subsequent signing process, while the task status is updated synchronously.

[0042] In some implementations, handling of file upload anomalies includes: if a network interruption, connection loss, or upload timeout occurs during file upload, the SFTP adapter supports resuming interrupted uploads to avoid re-uploading from the beginning; if insufficient disk space, lack of write permissions, or duplicate file names are detected on the target server, the upload is terminated and the reason is recorded; duplicate files are automatically renamed according to rules and uploaded again to ensure file uniqueness and write security.

[0043] In some implementations, the SFTP adapter is also configured to perform resource release and stability handling. Specifically, after each SFTP operation is completed, the SFTP adapter forcibly closes the file stream and disconnects the SFTP connection, releasing session resources and preventing connection leakage; it also supports a maximum concurrent connection limit to prevent multiple tasks from simultaneously occupying the SFTP channel, which could lead to channel service abnormalities and ensure long-term stable system operation.

[0044] The file format adapter 243 is used to uniformly convert image files of different formats into standard format files. For example, it converts JPG, PNG, and other image format files into the PDF standard format to ensure compatibility for signing and storage. Furthermore, the file format adapter 243 is configured to identify corrupted files and report this to the core service module 230, marking them as files that failed to acquire. Specifically, the file format adapter 243 reads the file header identifier to determine the format validity, verifies the file length and data stream integrity, attempts to decode and render the file normally, and detects whether the file is empty, truncated, encrypted, or contains garbled data. Files that cannot be read normally, fail to decode, or have invalid format verification are determined to be corrupted files.

[0045] In this embodiment of the invention, the storage module 250 is connected to the core service module 230 and the adaptation module 240, and is used to centrally store image files, signed files, and structured data required for system operation. In some embodiments, the storage module 250 includes a file storage unit and a data storage unit. The file storage unit uses MinIO object storage to store original image files, signed files, and backup files, and is configured to: receive user input requests for uploading, downloading, deleting, and querying files, and perform corresponding operations; archive files according to the path "channel ID-file type-year-month"; control file access and other operations according to preset user permissions; and perform file backups at predetermined time intervals. The data storage unit uses a MySQL database with a master-slave architecture to store structured data, including channel configuration information, task information, operation logs, business configuration information, alarm logs, etc. The data storage unit uses AES encryption to store sensitive information (such as SFTP passwords and API keys). In addition, the data storage unit also performs regular backups and restores to ensure data reliability.

[0046] In an embodiment of the present invention, reference is made to Figure 3The core service module 230 includes independently decoupled channel configuration management submodule 231, file acquisition submodule 232, contract signing submodule 233, file return submodule 234, and task management submodule 235. The task management submodule 235 is used to: receive file processing requests forwarded by the unified gateway module 220 and create file processing tasks; generate a globally unique identifier for the task (e.g., the format of which is: TASK_timestamp_random 6-digit number); and initialize the task status (e.g., initialized to "processing"); during the execution of the file processing tasks by the file acquisition submodule 232, contract signing submodule 233, and file return submodule 234, it updates and records the current status of the task (processing → signing → return → success / failure), the completion time and result of each submodule in real time; and, according to the callback address, sends the task processing result back to the business caller through the business access interface 210. In some implementations, the task management submodule 250 is further configured to perform at least one of the following processes: providing task details based on user input (e.g., supporting querying task details by task identifier, channel identifier, business number, etc.), initiating retry for failed tasks, and terminating operations on tasks currently being executed. Furthermore, the task management submodule 250 is also configured to archive completed tasks, set an expiration date, and automatically clean up expired tasks.

[0047] In some embodiments, the channel configuration management submodule 231 is used to store the configuration information of each cooperating channel, which includes at least file acquisition method, signature rules, and file return method. In some embodiments, the channel configuration management submodule 231 is configured to: store the configuration information of all cooperating channels, for example, including basic channel configuration (channel identifier, channel name, status), file acquisition configuration (acquisition method, API address / SFTP parameters), signature configuration (signature image path, location, mode), and return configuration (return method, number of retries, alarm switch); make corresponding changes to the configuration information according to the add, modify, delete, and query operation requests, and make the configuration changes take effect in real time without restarting the device; for new configurations, automatically verify the legality of parameters (such as SFTP connection test, API connectivity test) to avoid invalid configurations.

[0048] In some implementations, the file acquisition submodule 232 is used to perform the file processing task, including: obtaining the corresponding file acquisition method from the channel configuration management submodule 231 according to the channel identifier; pulling image files from the corresponding cooperative channel system through the adaptation module 240 (e.g., API adapter 241, SFTP adapter 242) according to the file acquisition method; performing pre-entry verification on the pulled image files, including format verification (e.g., supporting PDF, JPG, PNG), size verification (e.g., allowing a maximum file size of 100MB), and integrity verification (e.g., comparing MD5 values); renaming the image files according to a unified naming rule (e.g., naming format: channel ID_business number_file type_timestamp.suffix), and deduplicating the image files based on the channel identifier, business number, and file type; and uploading the verified and deduplicated image files (which are still the original image files at this time) to the original file directory of the storage module 250.

[0049] In some implementations, the contract signing submodule 233 is used to perform the document processing task, including: obtaining the image file transmitted by the file acquisition submodule 232 from the storage module 250, and converting the image file into a standard format file through the adaptation module 240 (specifically, the file format adapter 243) (e.g., converting a non-PDF format file into a PDF standard format); performing an electronic signing operation on the standard format file according to the signing rules in the channel configuration management submodule; and uploading the signed file to the signing file directory of the storage module.

[0050] In some embodiments, the electronic signature operation performed by the contract signing submodule 233 includes: selecting a fixed coordinate signing method or a keyword positioning signing method according to the signing rules, and affixing an electronic signature at a specified location. The electronic signature is, for example, a PNG transparent image, which can be stored in the storage module 250. The contract signing submodule 233 supports both fixed coordinate and keyword positioning methods, avoiding errors from manual positioning. The file verification module automatically completes format, size, and integrity verification, reducing human error. Compared with existing systems, file processing efficiency is improved by more than 60%, and the error rate is reduced by 90%. Further, in some embodiments, the contract signing submodule 233 is configured to: generate a signature verification code (bound to the file content and signature information) after signing, add an anti-tampering watermark; upload the signed file to the signature file directory of the storage module, record the signing log, and simultaneously call the task management submodule 235 to update the task status to "uploading".

[0051] In some embodiments, the file return submodule 234 is used to perform the file processing task, including: obtaining the signed document transmitted by the contract signing submodule 234 from the storage module 250, and according to the file return method in the channel configuration management submodule 231, returning the file to the corresponding cooperative channel system through the adaptation module 240 (specifically through the API adapter 241 or the SFTP adapter 242), and verifying the return result (for example, if API return is used, verifying the response status code; if SFTP return is used, verifying the file size and MD5 value); and automatically retrying according to the configured number of retries and intervals when the return fails. Further, in some embodiments, the file return submodule 234 triggers an alarm after a retry failure, records the return result and the reason for failure, and updates the task status to "failed".

[0052] In some implementations, the core service module 230 further includes a monitoring and alarm submodule, used to: monitor the operational health status of the system (operational status of each module, database connection status, storage module status, channel connection status) and task status in real time, and trigger alarm processing for tasks that time out (e.g., more than 30 minutes) or fail more than a preset threshold (e.g., 5 times); record alarm information and system operation logs, and generate exportable monitoring reports, such as those that support daily, weekly, or monthly export.

[0053] In some implementations, the system further includes an alarm module connected to the core service module 230 (specifically, the monitoring and alarm submodule), and configured to support three alarm methods: email, WeChat / DingTalk robot, and WebHook. The alarm module is configured with alarm recipients and alarm levels (normal / urgent). When it receives an alarm signal from the monitoring and alarm submodule, it pushes alarm information (including task identifier, channel identifier, failure reason, number of retries, etc.) to the alarm recipient according to the configured alarm method, so that relevant personnel can handle the anomaly promptly. Furthermore, the alarm module also records the alarm processing status, the handler, and the processing time for easy traceability.

[0054] According to the system described above, an exemplary processing flow is as follows: The business caller initiates a file processing request by passing parameters such as channel ID, business number, and file type through the business access interface 210; the unified gateway module 220 authenticates and limits the request, and after successful verification, routes the request to the task management submodule 235 of the core service module 230; the task management submodule 235 creates a task, generates a task ID, initializes the status to "processing", and synchronously returns the task status to the business caller; the file acquisition submodule 232 queries the channel configuration based on the channel ID, and pulls the image file from the cooperative channel system through the API adapter or SFTP adapter of the adaptation module 240; the file acquisition submodule 232 completes file verification and naming. The process involves several steps: First, deduplication is performed, and the original file is uploaded to storage module 250, updating the task status to "Signing". Second, the contract signing submodule 233 adapts the file format using file format adapter 243, completes the signing according to the signing rules, generates a verification code and anti-tampering watermark, and uploads the signed file to storage module 250, updating the task status to "Returning". Third, the file return submodule 234 uses adapter module 240 to return the signed file to the partner system, verifies the return result, and updates the task status to "Success" or "Failure". Fourth, the task management submodule 235 sends the task processing result back to the business caller through business access interface 210. If an anomaly occurs, the monitoring and alarm submodule triggers the alarm module, pushes alarm information, and supports manual retries of failed tasks. All operation logs, task information, and alarm information are stored in the storage module, supporting querying, tracing, and report export.

[0055] In addition, refer to Figure 5 The present invention also provides a general cooperative channel image file processing method, applicable to the system described in any embodiment of the present invention, which includes the following steps: S10, receive file processing requests initiated by business callers through the business access interface; S20, the file processing request is authenticated and rate-limited through the unified gateway module, and then routed to the core service module after authentication and rate-limiting. S30, according to the file processing request, the core service module obtains the image file from the cooperative channel system through the adaptation module and performs file processing on the image file, wherein the adaptation module provides the core service module with a unified service call and file processing interface for communicating with different cooperative channel systems; S40. After processing is completed, the processing result is returned to the business caller through the business access interface.

[0056] In another implementation, the general cooperative channel image file processing method includes: receiving a request: the business access interface receives a file processing request from the business caller and forwards it to the unified gateway module. After authentication and rate limiting, the unified gateway module routes the request to the task management submodule; creating a task: upon receiving the request, a file processing task is created, a unique task ID is generated, the task status is initialized to "processing", and the task status is synchronously returned to the business caller; file acquisition: the channel configuration is obtained according to the channel number passed in the request, the image files of the cooperative channel system are pulled through the adaptation module, file verification, naming, and deduplication are completed, and the original files are stored in the storage module. The task status is updated to "Signing"; Contract signing: The original document is signed, the file format is adapted through the file format adapter, the signing operation is completed according to the signing rules configured by the channel, a verification code and anti-tampering watermark are generated, the signed file is stored in the storage module, and the task status is updated to "Returning"; File return: The signed file is returned to the cooperative channel system through the adaptation module, and the return result is verified, and the task status is updated to "Success" or "Failure"; Result feedback and exception handling: The task processing result is returned to the business caller; The task status and system status are monitored in real time through the monitoring and alarm submodule, and the alarm module is triggered when an exception occurs, supporting retry of failed tasks. In addition, the general cooperative channel image file processing method also includes data archiving, that is, the task management submodule archives the completed tasks, the storage module saves all files and data, and supports querying, tracing and report export.

[0057] As can be seen from the above implementation methods, the system of the present invention, through a layered architecture design, sets up a unified adaptation layer (i.e., adaptation module), a core service layer (i.e., core service module), and a storage layer (i.e., storage module), to achieve universal adaptation for different cooperation channels, full automation of file processing, and real-time monitoring. The system mainly includes a business access interface, a unified gateway module, a core service module, an adaptation module, a storage module, and an alarm module. The adaptation module masks the differences in interface between different channels; the core service module automates the execution of file acquisition, signing, and return; the storage module ensures secure storage of files and data; and the alarm module provides timely alerts for anomalies. Therefore, the present invention can solve the problems of poor channel compatibility, low automation, and poor monitorability in existing technologies, achieving the effects of reducing development costs, improving file processing efficiency, facilitating anomaly investigation, and ensuring file security. Simultaneously, it allows for the integration of new channels without customized development, requiring only parameter configuration.

[0058] It should be understood that the steps, processes, and operations described in the above embodiments can be implemented by computer software programs. Therefore, the embodiments of the present invention also relate to a computer program product, which includes a computer program that, when executed by a processor, implements the steps, processes, or operations described in any embodiment of the present invention. In some embodiments, program code for executing the computer program of the embodiments of the present invention can be written in any combination of one or more programming languages. For example, the computer program can be written using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on a personal computing device, partially on a personal computing device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the personal computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0059] It should also be understood that the computer program product may be stored on a computer-readable storage medium, such as hard disks, floppy disks, magnetic tapes, optical disks, solid-state drives, flash memory, etc.

[0060] Furthermore, it can be understood that the method of any embodiment of the present invention can be executed by a computer device. Accordingly, embodiments of the present invention also relate to a computer device comprising: a memory storing a computer program thereon; and a processor that, when executing the computer program, implements the steps (processing, operations, etc.) of the method or system described or system in any embodiment of the present disclosure.

[0061] Figure 6 An exemplary structure of a computer device is shown. Figure 6As shown, the computer device 100 may include at least a processor 101 and a memory 102, wherein the memory 102 may be or include a storage medium storing a computer program (or computer-readable instructions). The processor 101 executes the computer program to perform some or all of the operations described in any embodiment of this disclosure, including but not limited to: S10, receiving a file processing request initiated by a service caller through a service access interface; S20, authenticating and rate-limiting the file processing request through a unified gateway module, and routing it to the core service module after authentication and rate-limiting; S30, according to the file processing request, the core service module obtains an image file from a cooperating channel system through an adaptation module and performs file processing on the image file, wherein the adaptation module provides the core service module with a unified service call and file processing interface for communicating with different cooperating channel systems; S40, after processing is completed, the processing result is returned to the service caller through the service access interface.

[0062] In some embodiments, the computer device 100 may further include a data storage device 103, a display 104, a speaker 105, and a communication module 106. The processor 101, memory 102, and data storage device 103 communicate with each other via a bus and interact with peripheral devices, such as the display 104 and communication module 106, via the bus and I / O module 107.

[0063] Specifically, data storage device 103 can store application programs and their various configuration files and data. Memory 102 stores computer programs. Processor 101 executes the computer programs to perform various processes, operations, or steps in any embodiment of the present invention. Display 104 can be used to display various data, images, etc.

[0064] In optional embodiments, the communication module 106 may be omitted where communication with the other systems, devices, or equipment is not required. In some embodiments, the computer device 100 may further include a speaker 105 for voice output.

[0065] In some implementations, processor 101 may include any suitable semiconductor-based electronic processing unit, chip, microchip, or integrated circuit (IC). Memory 102 is a programmable memory, which may include any suitable electronic storage device configured to store instructions and be reprogrammable. For example, programmable memory may include an erasable programmable read-only memory (EPROM) device. Data storage device 103 may be a persistent storage device, which may include any suitable electronic storage device configured to retain stored information as power cycles. For example, data storage device 103 may include a hard disk drive, solid-state drive (SSD), flash memory drive, hybrid drive, etc., or any combination thereof.

[0066] Therefore, processor 101 can control the output of information on I / O module 107 by storing information in memory and / or executing programs / instructions stored in memory. For example, several aspects of the methods described herein can be executed by processor 101 according to programs / instructions stored in memory (e.g., memory 102 and / or data storage device 103).

[0067] Furthermore, the processor 101 can electronically communicate with the I / O module 107 and / or the communication module 106 to receive or send relevant instructions and information. The I / O module 107 may include any suitable mechanical or virtual user interface configured to enable a user to interact with the computer device 100 or to allow the user to perform one or more functions of the computer device 100 itself, such as a graphical user interface (GUI) on a screen or other display. In some instances, the user interface may include a voice interface capable of speech recognition, through which an operator can provide voice commands to the processor.

[0068] The communication module 106 may include any suitable devices and / or structures configured to facilitate information exchange between the computer device 100 and external electronic devices. The communication module 106 may include devices configured to send and / or receive wireless or wired information with other devices. For example, the communication module 106 may include an antenna, a transceiver, a connector for wired reception and / or transmission of data, a data exchange device, etc., or any combination thereof. The communication module 106 may also include ancillary components, such as filtering circuitry, encryption / decryption circuitry, and / or integrated circuit (IC) chips (e.g., Bluetooth® chips) for processing signals. In some embodiments, the communication module 106 may include a WiFi device configured to connect to a local wireless network.

[0069] In some embodiments, computer device 100 may include a smartphone, wearable computer, portable / mobile electronic device, tablet computer, smartwatch, personal digital assistant (PDA), personal computer (PC), desktop computer, laptop computer, server, etc. Computer device 100 may include or have installed one or more application programs (APPs), one of which is configured to perform various processes, steps, or operations described herein or in the system.

[0070] Although not shown, it should be understood that the computer device 100 also includes a power supply component, which may include any suitable device and / or structure configured to provide an electrical interface between the computer device 100 and a power source. The power source may include any suitable source of electrical energy, such as a battery, socket, capacitor, fuel cell, etc., or any combination thereof. Additionally or optionally, the power source may be included within the power supply component. For example, a battery or battery pack may be included within the computer device 100. In some embodiments, the battery may be rechargeable, for example, charged via a cable or an interface provided by the power supply component. In some embodiments, the power supply component may share features with or repeat features of the communication module 106. For example, a USB or micro-USB cable connector may be included in the computer device 100, so that power supply or data communication is performed by the same component.

[0071] Those skilled in the art should understand that although specific values ​​are mentioned in the embodiments, the present invention is not limited thereto. Those skilled in the art can modify the relevant values ​​according to actual applications, and such modified embodiments are also embodiments of the present invention.

[0072] Those skilled in the art should also understand that the above disclosure is merely illustrative of embodiments of the present invention, and the scope of patent protection claimed in this application is not limited thereto. Various modifications, alterations, substitutions, and other changes can be made to the disclosed embodiments without departing from the spirit of the invention, and such changes are within the scope covered by the claims of this application.

Claims

1. A universal collaborative channel image file processing system, characterized in that, include: The business access interface is used to receive file processing requests initiated by at least one business caller. The request parameters carried by the file processing request include at least the channel identifier, business number, file type, authentication parameters, and callback address. And the system will send the processing results back to the corresponding business caller; The unified gateway module is connected to the service access interface and is used to authenticate, limit the rate, and route the received file processing requests. The core service module, connected to the unified gateway module, is used to receive the file processing request routed and distributed by the unified gateway module, obtain image files from the cooperative channel system according to the file processing request, and perform file processing on the image files; The adapter module connects to the core service module and multiple different cooperative channel systems respectively, so as to provide the core service module with a unified service call and file processing interface for communicating with different cooperative channel systems; The storage module, connected to the core service module and the adapter module, is used to centrally store image files, signed files, and structured data required for system operation.

2. The system according to claim 1, characterized in that, The unified gateway module includes: The interface authentication unit is used to store the key information of each business caller and verify the authentication parameters carried in the file processing request to confirm the legitimacy of the business party's identity. The request rate limiting unit is used to configure an independent call threshold for each business caller and to execute a rate limiting strategy when the number of requests exceeds the call threshold within a unit of time. The request routing unit is used to distribute the file processing request to the core service module according to the channel identifier in the file processing request. The logging unit is used to record the request parameters, response results, call time, time consumed, and calling IP of the file processing request for troubleshooting and auditing. The exception interception unit is used to capture and standardize the processing of various exceptions during system operation and return standard error information.

3. The system according to claim 1, characterized in that, The core service module includes an independently decoupled channel configuration management submodule, file acquisition submodule, contract signing submodule, file return submodule, and task management submodule; The task management submodule is configured to: receive file processing requests forwarded by the unified gateway module and create file processing tasks; generate a globally unique identifier for the task and initialize the task status; during the execution of the file processing tasks by the file acquisition submodule, contract signing submodule, and file return submodule, update and record the current status of the task, the completion time of each submodule, and the results in real time; and, according to the callback address, send the task processing results back to the business caller through the business access interface.

4. The system according to claim 3, characterized in that, The task management submodule is also configured to perform at least one of the following processes: provide task details based on user input, initiate retries for failed tasks, and terminate operations on tasks that are currently being executed.

5. The system according to claim 3, characterized in that, The channel configuration management submodule is used to store the configuration information of each cooperating channel, and the configuration information includes at least the file acquisition method, signature rules and file return method.

6. The system according to claim 5, characterized in that, The file acquisition submodule is used to perform the file processing task, including: Based on the channel identifier, obtain the corresponding file acquisition method from the channel configuration management submodule; According to the file acquisition method described above, the image file is retrieved from the corresponding partner channel system through the adaptation module. Perform pre-entry checks on the retrieved image files, including format verification, size verification, and integrity verification. The image files are renamed according to the unified naming rules, and the image files are deduplicated based on the channel identifier, business number, and file type. The verified and deduplicated image files are uploaded to the original file directory of the storage module.

7. The system according to claim 6, characterized in that, The contract signing submodule is used to perform the document processing task, including: The image file is obtained from the storage module and transmitted by the file acquisition submodule, and the image file is uniformly converted into a standard format file by the adaptation module. According to the signature rules in the channel configuration management submodule, perform electronic signature operations on the standard format file; Upload the signed document to the signed document directory of the storage module.

8. The system according to claim 7, characterized in that, The file return submodule is used to perform the file processing task, including: The system retrieves the signed document from the contract signing submodule from the storage module, and, according to the file return method in the channel configuration management submodule, returns the file to the corresponding partner channel system via the adaptation module, and verifies the return result. And when the return transmission fails, it will automatically retry according to the configured number of retries and interval.

9. The system according to claim 8, characterized in that, The core service module also includes a monitoring and alarm submodule, used for: The system monitors the operational health and task status in real time, and triggers alarm processing for tasks that time out or fail more than a preset threshold. Record alarm information and system operation logs, and generate monitoring reports that can be exported.

10. The system according to claim 1, characterized in that, The adaptation module includes: API adapters are used to uniformly adapt API interfaces from different cooperation channels; An SFTP adapter is used to uniformly adapt the connection, file retrieval, and upload logic of different SFTP servers. A file format adapter is used to convert image files of different formats into standard format files.

11. A method for processing image files from a general cooperative channel, applied to the system described in claim 1, characterized in that, Includes the following steps: Receive file processing requests initiated by business callers through the business access interface; The unified gateway module authenticates and limits the file processing requests, and then routes them to the core service module after authentication and rate limiting. According to the file processing request, the core service module obtains the image file from the cooperative channel system through the adaptation module and performs file processing on the image file. The adaptation module provides the core service module with a unified service call and file processing interface for communicating with different cooperative channel systems. After processing is complete, the processing result is sent back to the business caller through the business access interface.

12. A computer program product comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method of claim 11.

13. A computer device, characterized in that, include: A memory on which computer programs are stored; A processor that, when executing the computer program, implements the steps of the method of claim 11.

Images