Quickly transplantable supply chain finance platform information synchronization system and method

Abstract

This invention provides a rapidly portable supply chain finance platform information synchronization system and method, comprising: an identity authentication module: assigning unique identifiers to core enterprises, suppliers, and financial institutions using distributed ledger technology, and performing identity verification and access control for participants based on a private key signature mechanism; a basic field standardization module: pre-setting a standardized data system covering general basic fields, business-specific fields, and extended fields, serving as a unified semantic specification for data interaction between heterogeneous systems; an intelligent adaptation module: parsing participant interface documents using natural language processing technology, semantically mapping participant private fields to the standardized data system, and automatically generating integration code to call system interfaces; and an information synchronization scheduling module: listening to event trigger signals from business nodes, and distributing changed data to related participants according to preset synchronization priorities and conflict resolution strategies.

Description

Technical Field

[0001] This invention relates to, specifically, a rapidly portable supply chain finance platform information synchronization system and method. Background Technology

[0002] With the rapid development of supply chain finance, cross-domain collaboration and information sharing among core enterprises, multi-tiered suppliers, and financial institutions have become increasingly important. Currently, existing technologies for supply chain finance collaboration and data interoperability primarily focus on IoT data acquisition, edge computing processing, and hybrid blockchain storage. Conventional solutions typically combine underlying technologies such as consortium blockchains, lightweight node hybrid architectures, PBFT consensus algorithms, and AI scheduling to primarily achieve on-chain data storage and basic planning optimization in the logistics and production stages of the supply chain.

[0003] For example, Chinese patent application CN202010024044.3 discloses a blockchain-based agricultural supply chain financial service platform. This prior art design employs a multi-layered architecture comprising a data layer, a network and consensus layer, a smart contract layer, an interface layer, a management layer, and an application layer. Regarding the network and consensus mechanism, the scheme utilizes a hybrid consensus algorithm combining P2P networks and Delegated Proof-of-Stake (DPOS) with Byzantine Fault Tolerance (BFT), and supports data encryption and smart contracts. Furthermore, the platform generates unique identifiers for data through hash encryption to establish trusted channels, thereby achieving data immutability and privacy protection, and introduces cross-chain interaction and notary node functionality.

[0004] However, those skilled in the art have found through long-term practice that the aforementioned existing technologies still have the following obvious technical defects and shortcomings in actual industrial implementation and multi-entity promotion:

[0005] The existing technologies (such as the aforementioned patents) fail to address the high barriers to entry and long migration cycles caused by the heterogeneity of interfaces among multiple participants. While they establish a robust underlying blockchain network and basic interface layer, they do not provide automated solutions for the extremely complex differences in data semantics and interface formats between different enterprises (such as varying ERP and financial systems) and financial institutions. In practice, whenever a new participating institution is added or a new business line is expanded, developers still rely on extensive point-to-point code customization and hard-coding of interfaces. This "case-by-case" approach results in extremely high costs for repetitive development, making it impossible for the system to achieve rapid cross-platform and cross-industry migration and agile deployment.

[0006] Therefore, there is an urgent need in this field for a new supply chain finance platform information synchronization architecture that can overcome the above-mentioned defects, enable low-code and rapid access between heterogeneous systems, have intelligent field mapping capabilities, and ensure information security, real-time and consistent synchronization among multiple parties. Summary of the Invention

[0007] In view of the deficiencies in the existing technology, the purpose of this invention is to provide a rapidly portable supply chain finance platform information synchronization system and method.

[0008] According to one aspect of the present invention, a rapidly portable supply chain finance platform information synchronization system includes: Identity authentication module: Used to assign unique identity identifiers to core enterprises, suppliers and financial institutions through distributed ledger technology, and to perform identity verification and access control for participating parties based on private key signature mechanism; Basic Field Standardization Module: Used to pre-define a standardized data system covering general basic fields, business-specific fields, and extended fields, serving as a unified semantic specification for data interaction between heterogeneous systems; Intelligent Adaptation Module: Used to parse the participant's interface documents based on natural language processing technology, semantically map the participant's private fields to the standardized data system, and automatically generate integration code to call the system interface; Information synchronization and scheduling module: used to listen for event trigger signals of business nodes and distribute changed data to related participants according to preset synchronization priorities and conflict resolution strategies; Full business process integration module: used to drive all participating nodes to perform full-link transaction collaboration through the linkage information synchronization scheduling module.

[0009] Preferably, the identity authentication module includes: Identity registration module: Verifies the legal qualifications of participants, generates unique DID identifiers and keys, assigns role attributes based on the business needs of participants, and binds role attributes to DID identifiers; Identity verification module: Based on DID identifiers and keys, it performs identity verification and enables inter-party communication; Access control module: Assigns corresponding operation permissions based on role attributes; dynamically allocates and revokes operation permissions for participants based on supply chain collaboration scenarios.

[0010] Preferably, the basic field standardization module includes: Basic Field System Definition Module: Defines general basic fields, business-specific fields, and extended fields. The general basic fields include participant basic information, account information, and trade basic information. The participant basic information includes enterprise name and unified social credit code. The account information includes account name and account number. The trade basic information includes order number, contract number, and amount. The business-specific fields include order confirmation, bond certificate, financing application, and fund settlement. The order confirmation includes delivery date and acceptance status; the bond certificate includes certificate number and maturity date; the financing application includes financing amount and interest rate; and the fund settlement includes settlement serial number and receipt status. The extended fields include verification fields defined by the participants; Field attribute standardization module: Determines the data type, length limit, required / optional fields, validation rules, and default values ​​for each basic field. At the same time, it defines a synchronization identifier and a synchronization priority. The synchronization identifier is used to mark whether a field needs to be synchronized across participants, and the synchronization priority is used to specify the priority between fields.

[0011] Preferably, the intelligent adaptation module includes: Field intelligent mapping and rule generation module: builds a rule knowledge base and generates field mapping rules; Adaptation rule batch reuse and update module: Based on mapping rules, it generates a standardized rule template knowledge base, and adjusts and updates it in real time according to the information of the participants.

[0012] Interface adaptation automated deployment module: Based on the configured mapping rules and conversion logic, it generates interface code between the participating system and the device; based on the access code, it calls the system interface.

[0013] Preferably, the field intelligent mapping and rule generation module includes: Rule knowledge base construction module: Obtain mainstream industry supply chain business rules, core enterprise ERP interface documents, and bank financing interface documents to build a supply chain finance interface field knowledge base. The field knowledge base includes the semantics, format, relationship and historical mapping cases of fields in each system. Automated mapping module: Obtain the system interface documents of the participants, parse the field semantics and extract field attributes through NLP, and combine industry characteristics and knowledge base data to generate the mapping relationship of "participant field - basic field" to realize the access of the participants; Visual rule configuration module: Through a drag-and-drop human-computer interaction interface, you can calibrate mapping rules, configure data transformation logic, save or reuse rules, review historical rules, and manage versions.

[0014] Preferably, the adaptation rule batch reuse and update module includes: Rule template library construction module: Based on industry and participant type, mapping rules, transformation logic, and interface call parameters are encapsulated into standardized templates. These standardized templates are reused when new participants join, and special fields are calibrated. Dynamic update module: When the system interface of the participating party is adjusted, the module identifies the changes, compares the changes with the basic field system, and generates a rule update plan.

[0015] Preferably, the information synchronization and scheduling module includes: The synchronous triggering module includes: Event-driven triggering module: Based on a pre-set list of key events in the entire supply chain finance process, each event is bound to a corresponding set of synchronization fields; when a participant triggers an event, the changed data under the corresponding field is obtained, and information is synchronized based on the field synchronization identifier and priority identifier; Scheduled Incremental Scan Module: Based on the customized scheduled scan task, it incrementally captures changed data according to the synchronization representation and performs information synchronization based on the field synchronization identifier and priority identifier; Manually trigger the synchronization module: Data synchronization can be performed manually through the human-computer interaction interface; Synchronous transmission module, including: Real-time push module: Uses WebSocket to push high-priority data in real time; Message queue asynchronous transmission module: Uses RabbitMQ / Kafka message queues to asynchronously transmit low-priority data; Weak network adaptation and breakpoint resume module: Divide the data into multiple data segments for transmission, and record the transmission status through local caching. When the network is interrupted and reconnected, the unfinished segments are continued to be transmitted based on the transmission status recorded in the cache. Synchronization confirmation module: The "request-response-confirmation" three-stage strategy is used to transmit data. The "request-response-confirmation" three-stage strategy is configured as follows: After receiving the synchronization data, the receiver must return a confirmation receipt containing the data hash value within a predetermined time limit; if the sender does not receive the confirmation receipt or the synchronization fails, the receiver will resend the confirmation receipt. The synchronization conflict resolution module includes: Priority Strategy Module: Based on preset participant priority rules, in the event of a conflict, the data of the higher-priority participant shall prevail, the higher-priority data shall be automatically synchronized to other participants, and a conflict log shall be recorded. Negotiation Strategy Module: For core business data, it automatically pushes conflict alerts and conflict data to the administrator accounts of each participating party. After negotiating and confirming the correct data, it realizes full-link data update based on the resynchronization command initiated by the high-priority participating party. Log backtracking strategy module: Records all conflict data and resolution results in detailed logs, and uploads log summaries to the blockchain for evidence storage; The synchronization status monitoring and backtracking module includes: Real-time monitoring module: Acquires and displays the status of synchronization tasks, classifies and statistically analyzes the synchronization success rate by participants, business type, and time range, marks the reason for failure when synchronization fails, and responds to one-click retry instructions.

[0016] Synchronization Log Module: Records the source participant, target participant, synchronization time, data content, synchronization status, and transmission time for each synchronized data entry. It supports precise queries based on business order number, time range, participant, and other criteria. Synchronization logs are retained for a predetermined period, and summary information is uploaded to the blockchain for evidence storage.

[0017] Preferably, it also includes a blockchain-based evidence storage and traceability module: Based on the immutable nature of blockchain, the adaptation rules and key data in the information synchronization process during the rapid migration process are notarized; the notarized content specifically includes DID identity authentication records, adaptation rule summaries, trade document information summaries, debt instrument issuance and circulation records, financing application and approval records, fund settlement flow, synchronization log summaries, and conflict resolution records. The evidence storage mechanism is configured as follows: sensitive data is hashed to generate a digest and then written to the supply chain finance consortium blockchain; the corresponding evidence storage information is queried by business order number to verify whether the data has been tampered with; the evidence storage data is retained for 5 years after the business ends. Based on the business order number, query the full-chain evidence storage information and generate a traceability report.

[0018] Preferably, it also includes an operation and maintenance monitoring module: Device status monitoring module: Real-time monitoring of the operating status of each module, monitoring server CPU, memory and bandwidth usage, and automatically triggering alarms when abnormalities occur; Adaptation rule maintenance module: used for batch import or export of adaptation rules, version rollback, and restoration to a historical stable version when a rule is abnormal; it also automatically verifies the validity of rules periodically. System upgrade and backup module: used for online canary upgrades without affecting existing synchronous services during the upgrade process; performs daily full backups and real-time incremental backups of device configuration data, adaptation rules, and synchronization logs, with encrypted storage of backup data and support for disaster recovery; Access Support Tools Module: Provides a new participant access guide, a common problem troubleshooting manual, and an online customer service portal to assist participants in quickly completing the integration and deployment; supports remote assistance during the access process to improve the efficiency of rapid migration and implementation.

[0019] According to another aspect of the present invention, a rapidly portable supply chain finance platform information synchronization method includes: Identity authentication steps: Unique identity identifiers are assigned to core enterprises, suppliers and financial institutions through distributed ledger technology, and identity verification and access control are performed when participating parties access the system based on a private key signature mechanism; Basic field standardization steps: This is used to pre-define a standardized data system that covers general basic fields, business-specific fields, and extended fields, serving as a unified semantic specification for data interaction between heterogeneous systems; Intelligent adaptation steps: Based on natural language processing technology, the participant's interface document is parsed, the participant's private fields are semantically mapped to the standardized data system, and the integration code that calls the system interface is automatically generated; Information synchronization scheduling steps: Listen for event trigger signals from business nodes, and distribute changed data to relevant participants according to preset synchronization priorities and conflict resolution strategies; Full business process integration steps: Drive all participating nodes to perform full-link transaction collaboration by triggering information synchronization scheduling steps.

[0020] Compared with the prior art, the present invention has the following beneficial effects: This invention effectively overcomes the technical shortcomings of traditional supply chain finance platforms, such as high repetitive development costs and lengthy integration cycles caused by heterogeneous interfaces among multiple participants, by introducing an intelligent adaptation engine and standardized configuration of basic fields. The system uses natural language processing technology to automatically parse the private interface documents of participants and perform intelligent semantic mapping with a pre-set standardized data system, thereby automatically generating integration code that matches the host environment of the participating party. This lightweight, low-code access mechanism significantly lowers the technical transformation threshold for core enterprises, multi-level suppliers, and financial institutions, greatly shortening the integration and deployment cycle of new business nodes to one to three days, truly achieving agile deployment and rapid horizontal migration of solutions in heterogeneous environments.

[0021] This invention significantly improves the real-time performance and reliability of end-to-end data interaction by constructing an information synchronization and scheduling architecture based on event-driven, multi-channel dynamic transmission and automatic conflict resolution. The system configures event listeners at key nodes in supply chain finance operations. Once a state change is detected, it can flexibly invoke real-time push or asynchronous message queues for cross-node data distribution based on preset field synchronization identifiers and priorities. Combined with weak network interruption resumption technology, it ensures high transmission success rates in complex network environments. To address data inconsistencies that may arise from concurrent operations, the system relies on priority strategies and negotiation scheduling mechanisms for precise intervention and reconciliation. This completely establishes a closed-loop information flow from order confirmation, debt transfer, financing application to fund settlement, eliminating data lag and state silos inherent in traditional models. Attached Figure Description

[0022] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is an architecture diagram of a supply chain finance platform information synchronization system that can be quickly ported. Detailed Implementation

[0023] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0024] Example 1: This embodiment provides a rapidly portable supply chain finance platform information synchronization system, including: Identity authentication module: Used to assign unique identity identifiers to core enterprises, suppliers and financial institutions through distributed ledger technology, and to perform identity verification and access control for participating parties based on private key signature mechanism; Basic Field Standardization Module: Used to pre-define a standardized data system covering general basic fields, business-specific fields, and extended fields, serving as a unified semantic specification for data interaction between heterogeneous systems; Intelligent Adaptation Module: Used to parse the participant's interface documents based on natural language processing technology, semantically map the participant's private fields to the standardized data system, and automatically generate integration code to call the system interface; Information synchronization and scheduling module: used to listen for event trigger signals of business nodes and distribute changed data to related participants according to preset synchronization priorities and conflict resolution strategies; Full business process integration module: used to drive all participating nodes to perform full-link transaction collaboration through the linkage information synchronization scheduling module.

[0025] Based on the above solution, this rapidly portable supply chain finance platform information synchronization system solves core problems in supply chain finance, such as long integration cycles due to interface heterogeneity and data synchronization delays. It establishes a trusted mechanism for mutual identity recognition and tamper-proof data through an identity authentication module. A basic field standardization module defines a universal basic field system as translation middleware for heterogeneous interfaces. An intelligent adaptation module achieves rapid business integration within one to three days using natural language processing and other technologies. An information synchronization scheduling module clarifies the synchronization technology path after data changes, ensuring synchronization efficiency and stability. A full business process integration module integrates the collaboration between core enterprises, multi-level suppliers, and financial institutions, thereby creating a closed-loop information system from order to settlement. The system as a whole constructs a standardized, intelligent, and secure collaborative system.

[0026] In this embodiment, the identity authentication module includes: Identity registration module: Verifies the legal qualifications of participants, generates unique DID identifiers and keys, assigns role attributes based on the business needs of participants, and binds role attributes to DID identifiers; Identity verification module: Based on DID identifiers and keys, it performs identity verification and enables inter-party communication; Access control module: Assigns corresponding operation permissions based on role attributes; dynamically allocates and revokes operation permissions for participants based on supply chain collaboration scenarios.

[0027] Based on the above scheme, the identity authentication module replaces traditional authentication methods such as account passwords. The identity registration module generates identifiers and keys after the supply chain finance consortium chain nodes verify qualifications, uploading the public key to the chain while storing the private key locally. The identity verification module verifies identity through key signing during participant integration, eliminating the need for third-party intermediaries. The access control module supports dynamic allocation and revoke of permissions, adapting to complex supply chain collaboration scenarios and ensuring absolute control over data synchronization permissions. This design achieves end-to-end trust assurance from identity trust to transaction trust to financing trust, providing a secure foundation for rapid migration.

[0028] In this embodiment, the basic field standardization module includes: The basic field system definition module defines general basic fields, business-specific fields, and extended fields. The general basic fields include participant basic information, account information, and trade basic information. Participant basic information includes company name and unified social credit code; account information includes account name and account number; and trade basic information includes order number, contract number, and amount. The business-specific fields include order confirmation, bond certificates, financing applications, and fund settlement. Order confirmation includes delivery date and acceptance status; bond certificates include certificate number and maturity date; financing applications include financing amount and interest rate; and fund settlement includes settlement transaction number and receipt status. The extended fields include verification fields defined by the participants. Field attribute standardization module: Determines the data type, length limit, required / optional fields, validation rules, and default values ​​for each basic field. At the same time, it defines a synchronization identifier and a synchronization priority. The synchronization identifier is used to mark whether a field needs to be synchronized across participants, and the synchronization priority is used to specify the priority between fields.

[0029] Based on the above solution, the basic field system is designed in three categories to comprehensively cover the core needs of all integration scenarios. General basic fields handle various basic, account, and trade information. Business-specific fields are standardized for specific scenarios such as delivery date, acceptance status, and voucher number. Extended fields reserve custom interfaces to support the special risk control requirements of different industry supply chains. The field attribute standardization module provides fine-grained specifications at the field level for information synchronization by defining synchronization identifiers and synchronization priorities. High priority covers core data such as amount and deadline, while low priority covers auxiliary remarks data. This mechanism provides a solid and unified data standard for rapid mapping and information synchronization.

[0030] In this embodiment, the intelligent adaptation module includes: Field intelligent mapping and rule generation module: builds a rule knowledge base and generates field mapping rules; Adaptation rule batch reuse and update module: Based on mapping rules, it generates a standardized rule template knowledge base, and adjusts and updates it in real time according to the information of the participants.

[0031] Interface adaptation automated deployment module: Based on the configured mapping rules and conversion logic, it generates interface code between the participating system and the device; based on the access code, it calls the system interface.

[0032] Based on the above solution, the intelligent adaptation module, as the core engine for rapid portability, realizes automatic mapping and data conversion between the basic field system and heterogeneous interfaces. The intelligent field mapping and rule generation module lays the data foundation for automated matching by building a knowledge base. The batch reuse and update module for adaptation rules supports the batch application and update of mature adaptation rules, thereby significantly reducing the integration cost for new participants. The automated deployment module for interface adaptation, based on the generated integration code, supports containerized deployment to adapt to different environments such as cloud servers or local servers, achieving a plug-and-play rapid portability effect.

[0033] In this embodiment, the field intelligent mapping and rule generation module includes: Rule knowledge base construction module: Obtain mainstream industry supply chain business rules, core enterprise ERP interface documents, and bank financing interface documents to build a supply chain finance interface field knowledge base. The field knowledge base includes the semantics, format, relationship and historical mapping cases of fields in each system. Automated mapping module: Obtain the system interface documents of the participants, parse the field semantics and extract field attributes through NLP, and combine industry characteristics and knowledge base data to generate the mapping relationship of "participant field - basic field" to realize the access of the participants; Visual rule configuration module: Through a drag-and-drop human-computer interaction interface, you can calibrate mapping rules, configure data transformation logic, save or reuse rules, review historical rules, and manage versions.

[0034] Based on the above scheme, the rule knowledge base construction module extensively collects interface documents from various mainstream enterprise software and bank financing to build a deep field knowledge base. The automated mapping module processes the interface documents uploaded by new participants upon integration, automatically recommending one-to-one or one-to-many multi-dimensional mapping relationships using natural language processing technology. The visual rule configuration module provides a no-code drag-and-drop interface, allowing users to easily configure logic such as date format conversion or numerical unit conversion, and supports saving and reusing rule versions and historical retrospection.

[0035] In this embodiment, the adaptation rule batch reuse and update module includes: Rule template library construction module: Based on industry and participant type, mapping rules, transformation logic, and interface call parameters are encapsulated into standardized templates. These standardized templates are reused when new participants join, and special fields are calibrated. Dynamic update module: When the system interface of the participating party is adjusted, the module identifies the changes, compares the changes with the basic field system, and generates a rule update plan.

[0036] Based on the above solution, the rule template library construction module encapsulates rules from mature industries such as automotive manufacturing or electronics processing into standard templates, allowing new participants to significantly shorten configuration time by requiring only minor calibration of specific fields. The dynamic update module performs rule difference comparisons and automatically recommends update schemes when field names change or encryption methods are upgraded in the participating system interfaces. This module also supports batch updates of associated rules for multiple participants, avoiding a large amount of repetitive configuration work generated after adjustments to the core enterprise system.

[0037] The system according to claim 1, wherein the information synchronization scheduling module comprises: The synchronous triggering module includes: Event-driven triggering module: Based on a pre-set list of key events in the entire supply chain finance process, each event is bound to a corresponding set of synchronization fields; when a participant triggers an event, the changed data under the corresponding field is obtained, and information is synchronized based on the field synchronization identifier and priority identifier; Scheduled Incremental Scan Module: Based on the customized scheduled scan task, it incrementally captures changed data according to the synchronization representation and performs information synchronization based on the field synchronization identifier and priority identifier; Manually trigger the synchronization module: Data synchronization can be performed manually through the human-computer interaction interface; Synchronous transmission module, including: Real-time push module: Uses WebSocket to push high-priority data in real time; Message queue asynchronous transmission module: Uses RabbitMQ / Kafka message queues to asynchronously transmit low-priority data; Weak network adaptation and breakpoint resume module: Divide the data into multiple data segments for transmission, and record the transmission status through local caching. When the network is interrupted and reconnected, the unfinished segments are continued to be transmitted based on the transmission status recorded in the cache. Synchronization confirmation module: The "request-response-confirmation" three-stage strategy is used to transmit data. The "request-response-confirmation" three-stage strategy is configured as follows: After receiving the synchronization data, the receiver must return a confirmation receipt containing the data hash value within a predetermined time limit; if the sender does not receive the confirmation receipt or the synchronization fails, the receiver will resend the confirmation receipt. The synchronization conflict resolution module includes: Priority Strategy Module: Based on preset participant priority rules, in the event of a conflict, the data of the higher-priority participant shall prevail, the higher-priority data shall be automatically synchronized to other participants, and a conflict log shall be recorded. Negotiation Strategy Module: For core business data, it automatically pushes conflict alerts and conflict data to the administrator accounts of each participating party. After negotiating and confirming the correct data, it realizes full-link data update based on the resynchronization command initiated by the high-priority participating party. Log backtracking strategy module: Records all conflict data and resolution results in detailed logs, and uploads log summaries to the blockchain for evidence storage; The synchronization status monitoring and backtracking module includes: Real-time monitoring module: Acquires and displays the status of synchronization tasks, classifies and statistically analyzes the synchronization success rate by participants, business type, and time range, marks the reason for failure when synchronization fails, and responds to one-click retry instructions.

[0038] Synchronization Log Module: Records the source participant, target participant, synchronization time, data content, synchronization status, and transmission time for each synchronized data entry. It supports precise queries based on business order number, time range, participant, and other criteria. Synchronization logs are retained for a predetermined period, and summary information is uploaded to the blockchain for evidence storage.

[0039] Based on the above scheme, the information synchronization scheduling module acts as the central hub for end-to-end data transmission, ensuring accurate synchronization of any change. The event-driven triggering module, as the core method, captures change data such as order creation or approval in real time and triggers synchronization immediately. The timed incremental scanning module captures incremental data for older systems that cannot be triggered in real time to avoid bandwidth waste. The manual triggering synchronization module adapts to special urgent scenarios such as abnormal orders. The synchronization transmission module combines real-time push and asynchronous message queues to ensure transmission performance while using national cryptographic hash processing to prevent data tampering. The weak network adaptation and breakpoint resumption module splits large files such as invoices into smaller fragments to improve the synchronization success rate in weak network environments. The synchronization confirmation module's multiple retry and alarm mechanisms ensure an extremely high synchronization success rate. The synchronization conflict resolution module uses priority strategies and manual negotiation strategies to reconcile conflicts caused by concurrent modifications from multiple parties, thereby ensuring eventual data consistency. The synchronization status monitoring and backtracking module ensures full-process transparency, traceability, and accountability through a visual dashboard and long-term log on-chain storage.

[0040] In this embodiment, a blockchain-based evidence storage and traceability module is also included: Leveraging the immutability of blockchain, key data during the rapid migration process, including adaptation rules and information synchronization, are stored as evidence. This evidence includes DID authentication records, adaptation rule summaries, trade document information summaries, debt instrument issuance and transfer records, financing application and approval records, fund settlement records, synchronization log summaries, and conflict resolution records. The evidence storage mechanism is configured as follows: sensitive data is hashed to generate a summary, which is then written to the supply chain finance consortium blockchain; corresponding evidence information is queried by business order number to verify data tampering; evidence data is retained for 5 years after the business transaction ends; and a traceability report is generated by querying the entire chain of evidence information based on the business order number.

[0041] Based on the above solution, the blockchain-based evidence storage and traceability module provides absolutely credible legal and factual evidence for synchronous conflict resolution and business auditing. The stored evidence comprehensively covers all core aspects from identity authentication to rule mapping and fund settlement. By extracting sensitive data summaries and writing them to the consortium blockchain, the compliance risks associated with uploading all original privacy data to the blockchain are effectively avoided. This module not only supports verification of data tampering but also ensures that data retention periods comply with stringent financial regulatory requirements. The reports generated by the traceability function can also be integrated with regulatory systems to achieve real-time data reporting, significantly improving the overall compliance efficiency of the system.

[0042] In this embodiment, an operation and maintenance monitoring module is also included: Device status monitoring module: Real-time monitoring of the operating status of each module, monitoring server CPU, memory and bandwidth usage, and automatically triggering alarms when abnormalities occur; Adaptation rule maintenance module: used for batch import or export of adaptation rules, version rollback, and restoration to a historical stable version when a rule is abnormal; it also automatically verifies the validity of rules periodically. System upgrade and backup module: used for online canary upgrades without affecting existing synchronous services during the upgrade process; performs daily full backups and real-time incremental backups of device configuration data, adaptation rules, and synchronization logs, with encrypted storage of backup data and support for disaster recovery; Access Support Tools Module: Provides a new participant access guide, a common problem troubleshooting manual, and an online customer service portal to assist participants in quickly completing the integration and deployment; supports remote assistance during the access process to improve the efficiency of rapid migration and implementation.

[0043] Based on the above solutions, the operation and maintenance (O&M) and monitoring module provides strong underlying support for the stable operation of the entire system, effectively reducing long-term operating costs. The device status monitoring module ensures healthy system operation by tracking computing power usage and synchronization success rate in real time. The adaptation rules O&M module avoids widespread adaptation failures caused by unilateral changes to external interfaces through regular verification and version rollback mechanisms. The system upgrade and backup module adopts a canary upgrade and encrypted incremental backup strategy to support smooth system evolution and recovery from extreme disasters without user intervention. The access support tool module maximizes the potential for rapid migration and translates it into practical integration efficiency by integrating standard guidelines and remote assistance access points.

[0044] Based on the above solution, this synchronization method addresses the collaboration barriers in supply chain finance caused by numerous participants and heterogeneous interfaces at the execution level. The identity authentication step and the basic field standardization step together construct a secure and semantic foundation for information mutual recognition. The intelligent adaptation step utilizes natural language processing to automate the generation of interface code, significantly reducing the originally lengthy adaptation cycle and enabling low-cost portability. The information synchronization scheduling step ensures data flow within seconds and automatic conflict resolution through core technologies such as event-driven and multi-channel transmission. The full business process integration step links all upstream nodes, connecting logistics, capital flow, and information flow, thereby completely eliminating information silos and building a highly automated supply chain finance ecosystem.

[0045] Example 2: This embodiment provides a readily portable supply chain finance platform information synchronization device, mainly comprising: 1. DID Distributed Identity Authentication Module: This module primarily addresses the issues of identity authentication and trust transfer among core enterprises, multi-level suppliers, and financial institutions in supply chain finance. It replaces traditional authentication methods such as account passwords and USB tokens, achieving end-to-end trust assurance of "trustworthy identity - trustworthy transactions - trustworthy financing," and providing a secure foundation for rapid migration and information synchronization.

[0046] Deploying the DID system using a consortium blockchain (such as FISCO BCOS) complies with the regulatory requirements of the financial industry; it supports national cryptographic algorithms (SM2 / SM3) for encryption, ensuring the security of identity information.

[0047] 1) Identity Registration: Core enterprises, suppliers, and financial institutions submit their legal qualifications and apply for DID identity identifiers. After review by the supply chain finance consortium chain nodes, a unique DID identifier and key are generated (public key is uploaded to the chain, and private key is stored locally). DID-based role hierarchy is supported (such as core enterprise administrator, supplier, bank auditor, etc.).

[0048] 2) Identity verification: When participating parties connect, their identities are verified through DID key signature without the need for third-party intermediaries; when applying for financing, "multi-entity joint identity verification" is supported to achieve "point-to-point trust" and "credit penetration".

[0049] 3) Access Control: DID-based role-based access control refines operational permissions; supports dynamic allocation and revocation of permissions, adapts to supply chain collaboration scenarios, and ensures controllable permissions for data synchronization.

[0050] 2. Basic Field Standardization Module: This module mainly defines a "general basic field system" for interfacing with multiple participants in supply chain finance. It serves as a "translation middleware" for heterogeneous interfaces, resolving the issue of inconsistent fields. At the same time, it standardizes trade document and debt certificate fields, providing a unified data specification for rapid mapping and information synchronization.

[0051] Basic field system design (divided into 3 categories): 1) Common basic fields: core fields covering all docking scenarios, including basic information of participants (company name, unified social credit code, etc.), account information (account name, account number, etc.), and basic trade information (order number, contract number, amount, etc.).

[0052] 2) Business-specific fields: Fields for specific supply chain finance scenarios, such as order confirmation (delivery date, acceptance status), debt instruments (document number, maturity date, etc.), financing application (financing amount, interest rate, etc.), and fund settlement (settlement serial number, arrival status, etc.).

[0053] 3) Extended fields: Reserves a custom field interface to support the special needs of different industry supply chains; supports financial institutions to supplement custom verification fields according to risk control requirements.

[0054] Field attribute standardization: Clearly define the data type, length limit, required / optional fields, validation rules, and default values ​​for each basic field. Also define "synchronization flags" (marking whether a field needs to be synchronized across participants) and "synchronization priorities" (setting core fields such as amount and period to high priority, and auxiliary fields such as remarks to low priority) to provide field-level specifications for information synchronization.

[0055] 3. Intelligent Adaptation Engine Module: This module mainly realizes the automatic mapping, data conversion, and adaptation rule management between the "basic field system" and the heterogeneous interfaces of various participants. It is the core engine of "rapid migration" and supports the reuse and batch update of adaptation rules, reducing the integration cost for new participants.

[0056] Intelligent field mapping and rule generation Rule knowledge base construction: Collect mainstream industry supply chain business rules, core enterprise ERP interface documents (such as SAP, Yonyou), and bank financing interface documents (such as ICBC e-Enterprise Quick Loan, CCB Huidongni) to build a "Supply Chain Finance Interface Field Knowledge Base", which includes the semantics, format, relationship and historical mapping cases of fields in each system.

[0057] Automated mapping: When a new participant joins, they upload the system interface document (JSON / XML / Word). The engine uses NLP to parse the field semantics and extract field attributes. Combining industry characteristics and knowledge base data, it automatically recommends the mapping relationship between "participant fields and basic fields". It supports "one-to-one / one-to-many / many-to-one" mapping (such as the core enterprise's "accounts payable amount" mapping to the basic fields "principal of debt" and "amount to be settled").

[0058] 3) Visual rule configuration: Provides a drag-and-drop interface, allowing users to calibrate mapping rules and configure data conversion logic (such as converting between date formats "yyyy-MM-dd" and "yyyyMMdd", and converting numerical units "ten thousand yuan" and "yuan") without coding. It supports saving, reusing and version management of rules, and historical rules can be traced back.

[0059] Batch reuse and update of adaptation rules: Rule template library: Based on industry (automobile manufacturing, electronic processing, building materials supply, etc.) and participant type (core enterprise / state-owned bank / joint-stock bank / small and medium-sized supplier), mature mapping rules, transformation logic and interface call parameters are encapsulated into standardized templates (such as "Automobile Industry Core Enterprise Connection Template" and "State-owned Bank Financing Interface Template"). New participants can directly reuse the templates when connecting, and only need to perform a small amount of calibration on special fields, shortening the configuration time.

[0060] Dynamic update mechanism: When the system interface of the participating party is adjusted (such as field name change, new field addition, encryption method upgrade), the engine supports "rule difference comparison", which automatically identifies the changed content and compares it with the basic field system, and recommends a rule update solution; it supports batch update of the association rules of multiple participating parties (such as after the core enterprise ERP field is changed, the corresponding mapping rules of all cooperative suppliers are updated simultaneously) to avoid duplicate configuration.

[0061] Automated deployment of interface adaptation: Automatically generate interface code: Based on the configured mapping rules and conversion logic, generate interface code (SDK / API call examples) between the participating system and device with one click. It supports mainstream development languages ​​such as Java, Python, and Node.js and is compatible with the technology stacks of different participants.

[0062] Lightweight integration: Participants do not need to modify their core business systems. They only need to integrate the lightweight SDK (≤5MB in size) provided by the device and complete the connection with the device by calling the interface through 3-5 lines of code. It supports Docker containerized deployment and is compatible with different deployment environments such as cloud servers and local servers, achieving a "plug and play" rapid portability effect.

[0063] 4. Information Synchronization Scheduling Module: Primarily responsible for scheduling, triggering, transmission, and conflict resolution of information synchronization across the entire link, ensuring that data changes from any participant are synchronized to other related participants in real time and accurately; clarifying the synchronization technical path after data changes to ensure synchronization efficiency and stability.

[0064] Synchronous Trigger Mechanism (Change Awareness) – A “Detector” of Data Changes: 1) Event-Driven Triggering (Core Method): A pre-defined list of key events for the entire supply chain finance process (such as order creation / confirmation, invoice upload / verification, receivables issuance / transfer / splitting, financing application / approval / disbursement, funds arrival / clearing, etc.) is set up, and each event is bound to a corresponding set of synchronization fields. When any participant triggers an event (such as a core enterprise creating an order or a bank approving financing), the device captures the changed data in real time through the SDK, automatically marks the synchronization identifier and priority, and immediately triggers the synchronization process. For example, after the core enterprise confirms an order, the "order information" is automatically synchronized to the corresponding supplier and partner bank.

[0065] 2) Scheduled Incremental Scanning (Supplementary Method): For some older systems that cannot trigger events in real time (such as some standalone management systems of small and medium-sized suppliers), configure customizable scheduled scanning tasks (minimum interval of 1 minute) to incrementally capture changed data according to the "synchronization identifier" (only synchronize newly added / modified fields, do not transmit full data) to avoid inefficiency and bandwidth consumption caused by full data transmission.

[0066] 3) Manually trigger synchronization (emergency mode): Supports users to manually trigger the synchronization of specific business data (such as an abnormal order or a debt certificate that was missed in synchronization) in the visual interface, adapting to special business scenario requirements (such as resynchronization after data synchronization failure, and expedited synchronization of urgent business data).

[0067] Synchronous transmission technology (high efficiency and reliability) – the “transmission channel” for data synchronization: 1) Real-time push technology (high-priority data): WebSocket is used to push high-priority data (such as order confirmation, financing approval results, and fund arrival information) in real time, ensuring that changed data is synchronized to relevant participants within seconds (≤3 seconds); for scenarios with high security requirements such as financial institutions, TLS 1.3 encrypted transmission is added, and SM3 hash processing is performed before data transmission. The receiving end verifies the hash value to prevent data from being tampered with.

[0068] 2) Asynchronous transmission of message queues (low-to-medium priority data): RabbitMQ / Kafka message queues are used to process low-to-medium priority data (such as scanned invoices and remarks) to achieve asynchronous transmission and avoid system blocking in high-concurrency scenarios; persistent message storage is supported, and unfinished synchronous tasks can be recovered after abnormal system restart.

[0069] 3) Weak network adaptation and breakpoint resume (vendor-side adaptation): For weak network / network outage environments that may exist on the vendor side, a "data fragmentation + incremental synchronization" strategy is adopted to split large data volumes (such as multi-page invoice scans, batch order data) into small fragments of 100KB / s for transmission; by recording the transmission status locally, when the network is interrupted and reconnected, only the unfinished fragments are resumed, without having to repeat the transmission of the full data, thus improving the synchronization success rate in weak network environments.

[0070] 4) Synchronization confirmation mechanism: A three-stage transmission process of "request-response-confirmation" is adopted. After receiving the synchronization data, the receiver must return a confirmation receipt containing the data hash value within 5 seconds. If no confirmation receipt is received or synchronization fails, the device will automatically retry (the number of retries is ≤5, with intervals of 10 seconds, 30 seconds, 1 minute, 5 minutes, and 10 minutes respectively, which can be configured). An alarm notification (SMS + system message) will be triggered after a retry failure to ensure a synchronization success rate of ≥99.9%.

[0071] Synchronization conflict resolution (data consistency) – a “mediator” for data conflicts: Conflict detection: Conflicts are detected based on three dimensions: business primary key, timestamp, and synchronization priority. When the same business data (such as the amount of an order) is modified by multiple parties at the same time, conflicting data is automatically identified (such as the core enterprise modifying the order amount to 1 million, and the supplier modifying it to 1.05 million at the same time).

[0072] Conflict resolution strategies: 1) Priority Strategy (Default): Preset priority rules for participants (core enterprise priority > financial institutions > tier 1 suppliers > tier 2 suppliers). In case of conflict, the data of the higher priority participant shall prevail, and the higher priority data shall be automatically synchronized to other participants and the conflict log shall be recorded. For example, when the core enterprise and the supplier have a conflict in modifying the order amount, the data of the core enterprise shall prevail.

[0073] 2) Negotiation Strategy (Core Data): For conflicts in core business data (such as debt amount, financing amount, and clearing ratio), conflict reminders are automatically pushed to the administrator accounts of each participating party. The conflict data details (including modification time, modifier, and original data) can be viewed online. After the correct data is confirmed through negotiation, the high-priority participating party initiates a resynchronization to update the data across the entire chain.

[0074] 3) Log backtracking strategy: All conflict data and resolution results are recorded in detailed logs (including conflict content, detection time, resolution method, and operator). Log summaries are stored on the blockchain for evidence, supporting subsequent traceability and auditing, and ensuring that responsibility can be defined.

[0075] Synchronous status monitoring and backtracking: Real-time monitoring: A visual dashboard displays the status of synchronization tasks (pending synchronization / synchronizing / synchronization successful / synchronization failed), and provides statistics on synchronization success rate by participant, business type, and time range; when synchronization fails, the reason for failure is marked (network error / data format error / insufficient permissions / unresolved conflicts, etc.), and one-click retry is supported.

[0076] 2) Synchronization Log: Records the source participant, target participant, synchronization time, data content (de-identified), synchronization status, and transmission time for each synchronized data. It supports precise querying by business order number, time range, participant, and other conditions. The synchronization log is retained for 10 years, and the summary information is stored on the blockchain to ensure that it cannot be tampered with.

[0077] 5. Full Business Process Integration Module: This module integrates the entire supply chain finance business process, enabling collaborative linkage and fully automated processing among core enterprises, multi-level suppliers, and financial institutions, and establishing an information loop connecting "orders, receivables, financing, and settlement." Each business link is linked to an information synchronization and scheduling module, clearly defining the synchronization logic and technical implementation after data changes.

[0078] Scenario 1: Order Confirmation and Trade Document Verification Process: Core enterprise creates order → System converts to standardized format using intelligent adaptation engine → Pushes to supplier in real time via WebSocket (synchronous trigger: order creation event, synchronization priority: high) → Supplier confirms order and uploads invoice (supports PDF / image format) → Device extracts invoice information using OCR and converts to standardized format, verifies consistency between order and invoice (amount, contract number, product name) and invoice authenticity (interfacing with tax system API) → Verification result synchronized to core enterprise and supplier via WebSocket (synchronous trigger: invoice audit event) → Trade document information summary stored on blockchain.

[0079] Synchronization technology highlights: Invoice scans use "fragmented transmission + breakpoint resume transmission", which can be uploaded normally in weak network environments; the core fields (amount, quantity) of orders and invoices are synchronized with dual verification (local verification + blockchain evidence verification) to ensure data consistency.

[0080] Scenario 2: Issuance and multi-level transfer of core enterprise debt instruments Process: The core enterprise issues debt instruments based on the verified trade documents → standardizes the instrument information and generates a DID signature → synchronizes with the supplier via WebSocket (synchronization trigger: debt issuance event, synchronization priority: high) → after the supplier signs for it, it can be split and transferred to downstream secondary suppliers → each transfer operation triggers synchronization (synchronization trigger: debt transfer event), and the transfer record is asynchronously pushed to all participants (core enterprise, all levels of suppliers, and corresponding financial institutions) through a message queue → the transfer record is stored on the blockchain.

[0081] Synchronous technology highlights: The transfer of debt instruments adopts "event-driven + full-link push" to ensure that suppliers at all levels can obtain the status of instruments in real time; data changes during the transfer process (such as splitting amounts) automatically trigger conflict detection and use a priority strategy to resolve conflicts (core enterprises have the highest priority); sensitive information (such as the credit rating of core enterprises) is encrypted with TLS 1.3 to prevent leakage.

[0082] Scenario 3: Collaboration between Supplier Financing Application and Approval Process: Supplier selects debt instruments to apply for financing from the target financial institution → Device automatically integrates standardized trade documents, debt instruments, and supplier qualification materials → Pushes to the financial institution via encrypted WebSocket (synchronous trigger: financing application event, synchronization priority: high) → During the financial institution's review process, the approval progress is pushed to the supplier and core enterprise via timed incremental synchronization (synchronous trigger: approval status change event, synchronization frequency: every 30 minutes) → After approval / rejection, the result is synchronized to the supplier and core enterprise via WebSocket in seconds (synchronous trigger: approval completion event) → After successful financing, the funds arrival information is synchronized to the device via message queue and then pushed to the supplier (synchronous trigger: funds arrival event).

[0083] Synchronization technology highlights: Financing materials contain sensitive information, and the transmission adopts a dual guarantee of "encrypted push + receipt confirmation". If the receipt is not received, it will automatically retry; the approval progress adopts incremental synchronization, only pushing the status change content (such as "under review → approved"), reducing the amount of data transmission.

[0084] Scenario 4: Settlement upon maturity and fund distribution Process: 3 days before the debt matures, the device pushes a repayment reminder to the core enterprise via a message queue (synchronization trigger: maturity reminder event, synchronization priority: medium) → After the core enterprise deposits the funds into the designated account, the bank system synchronizes the fund arrival information to the device (synchronization trigger: fund arrival event, synchronization technology: WebSocket) → After the financial institution deducts the principal and interest of the loan, it initiates clearing → The device converts the clearing information into the payment information of each supplier according to the clearing rules and synchronizes it to each supplier via WebSocket (synchronization trigger: clearing completion event, synchronization priority: high) → Settlement transaction summary is uploaded to the blockchain for evidence storage.

[0085] Synchronization technology highlights: Settlement data adopts a dual mechanism of "real-time push + timed verification". After synchronization is completed, the consistency between the cleared amount and the debt amount is automatically verified within 10 minutes. The verification result is synchronized to financial institutions and core enterprises. If a discrepancy occurs, the conflict resolution process is triggered immediately.

[0086] 6. Blockchain Evidence Storage and Traceability Module: Utilizing the immutability of blockchain, this module stores evidence of adaptation rules during rapid migration and key data (trade documents, debt transfer, synchronization logs, conflict resolution records, etc.) during information synchronization, ensuring data authenticity and traceability; and providing credible evidence for synchronization conflict resolution and business auditing.

[0087] The evidence includes: DID identity authentication records, adaptation rule summaries (including mapping relationships and conversion logic), trade document information summaries (hash values ​​of key fields in orders / invoices), debt instrument issuance and transfer records, financing application and approval records, fund settlement flow records, synchronization log summaries, conflict resolution records, etc.

[0088] Evidence storage mechanism: The "summary on-chain + incremental evidence storage" model is adopted. Sensitive data is hashed to generate a summary and then written to the supply chain finance consortium blockchain (such as FISCO BCOS) to avoid putting all sensitive data on the blockchain; it supports quick query of corresponding evidence storage information by business order number to verify whether the data has been tampered with; the evidence storage data is retained for 5 years after the business ends, which complies with financial regulatory requirements.

[0089] Traceability Function: Provides a visual traceability interface, allowing users to query full-chain evidence information and generate traceability reports by entering business order numbers (such as order numbers, debt certificate numbers, and financing application numbers); supports integration with regulatory systems to achieve real-time reporting of regulatory data and improve compliance efficiency.

[0090] 7. Operation and Maintenance Monitoring Module: Provides operation and maintenance support for rapid migration and information synchronization, ensures stable operation of the device, and reduces operation and maintenance costs.

[0091] Device status monitoring: Real-time monitoring of the operating status of each module of the device (adaptation engine, synchronization scheduling, blockchain integration), monitoring of server CPU, memory and bandwidth usage, and automatic triggering of alarms (SMS + email + system message) when anomalies occur (such as CPU usage ≥80% or synchronization success rate ≤95%).

[0092] Adaptation rule maintenance: Supports batch import / export and version rollback of adaptation rules. When a rule is abnormal, it can be quickly restored to a historical stable version. Regularly and automatically verify the validity of the rules (compare with the interface of the participating parties) to avoid adaptation failure due to interface changes.

[0093] System upgrades and backups: Supports online canary upgrades without affecting existing synchronous services during the upgrade process; performs daily full backups and real-time incremental backups of device configuration data, adaptation rules, and synchronization logs, with encrypted storage of backup data and support for disaster recovery.

[0094] Access support tools: Provides access guides for new participants, troubleshooting manuals for common problems, and online customer service access to assist participants in quickly completing the integration and deployment; supports remote assistance during the access process to improve the efficiency of rapid migration and implementation.

[0095] Those skilled in the art will understand that, besides implementing the system and its various devices, modules, and units provided by this invention in the form of purely computer-readable program code, the same functions can be achieved entirely through logical programming of the method steps, making the system and its various devices, modules, and units of this invention function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices, modules, and units provided by this invention can be considered as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices, modules, and units for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0096] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A rapidly portable supply chain finance platform information synchronization system, characterized in that, include: Identity authentication module: Used to assign unique identity identifiers to core enterprises, suppliers and financial institutions through distributed ledger technology, and to perform identity verification and access control for participating parties based on private key signature mechanism; Basic Field Standardization Module: Used to pre-define a standardized data system covering general basic fields, business-specific fields, and extended fields, serving as a unified semantic specification for data interaction between heterogeneous systems; Intelligent Adaptation Module: Used to parse the participant's interface documents based on natural language processing technology, semantically map the participant's private fields to the standardized data system, and automatically generate integration code to call the system interface; Information synchronization and scheduling module: used to listen for event trigger signals of business nodes and distribute changed data to related participants according to preset synchronization priorities and conflict resolution strategies; Full business process integration module: used to drive all participating nodes to perform full-link transaction collaboration through the linkage information synchronization scheduling module.

2. The system according to claim 1, characterized in that, The identity authentication module includes: Identity registration module: Verifies the legal qualifications of participants, generates unique DID identifiers and keys, assigns role attributes based on the business needs of participants, and binds role attributes to DID identifiers; Identity verification module: Based on DID identifiers and keys, it performs identity verification and enables inter-party communication; Access control module: Assigns corresponding operation permissions based on role attributes; dynamically allocates and revokes operation permissions for participants based on supply chain collaboration scenarios.

3. The system according to claim 1, characterized in that, The basic field standardization module includes: Basic Field System Definition Module: Defines general basic fields, business-specific fields, and extended fields. The general basic fields include participant basic information, account information, and trade basic information. The participant basic information includes enterprise name and unified social credit code. The account information includes account name and account number. The trade basic information includes order number, contract number, and amount. The business-specific fields include order confirmation, bond certificate, financing application, and fund settlement. The order confirmation includes delivery date and acceptance status; the bond certificate includes certificate number and maturity date; the financing application includes financing amount and interest rate; and the fund settlement includes settlement serial number and receipt status. The extended fields include verification fields defined by the participants; Field attribute standardization module: Determines the data type, length limit, required / optional fields, validation rules, and default values ​​for each basic field. At the same time, it defines a synchronization identifier and a synchronization priority. The synchronization identifier is used to mark whether a field needs to be synchronized across participants, and the synchronization priority is used to specify the priority between fields.

4. The system according to claim 1, characterized in that, The intelligent adaptation module includes: Field intelligent mapping and rule generation module: builds a rule knowledge base and generates field mapping rules; Adaptation rule batch reuse and update module: Based on mapping rules, it generates a standardized rule template knowledge base, and adjusts and updates it in real time according to the information of the participants. Interface adaptation automated deployment module: Based on the configured mapping rules and conversion logic, it generates interface code between the participating system and the device; based on the access code, it calls the system interface.

5. The system according to claim 4, characterized in that, The field intelligent mapping and rule generation module includes: Rule knowledge base construction module: Obtain mainstream industry supply chain business rules, core enterprise ERP interface documents, and bank financing interface documents to build a supply chain finance interface field knowledge base. The field knowledge base includes the semantics, format, relationship and historical mapping cases of fields in each system. Automated mapping module: Obtain the system interface documents of the participants, parse the field semantics and extract field attributes through NLP, and combine industry characteristics and knowledge base data to generate the mapping relationship of "participant fields - basic fields" to realize the access of the participants; Visual rule configuration module: Through a drag-and-drop human-computer interaction interface, you can calibrate mapping rules, configure data transformation logic, save or reuse rules, review historical rules, and manage versions.

6. The system according to claim 4, characterized in that, The module for batch reuse and update of adaptation rules includes: Rule template library construction module: Based on industry and participant type, mapping rules, transformation logic, and interface call parameters are encapsulated into standardized templates. These standardized templates are reused when new participants join, and special fields are calibrated. Dynamic update module: When the system interface of the participating party is adjusted, the module identifies the changes, compares the changes with the basic field system, and generates a rule update plan.

7. The system according to claim 1, characterized in that, The information synchronization and scheduling module includes: The synchronous triggering module includes: Event-driven triggering module: Based on a pre-set list of key events in the entire supply chain finance process, each event is bound to a corresponding set of synchronization fields; when a participant triggers an event, the changed data under the corresponding field is obtained, and information is synchronized based on the field synchronization identifier and priority identifier; Scheduled Incremental Scan Module: Based on the customized scheduled scan task, it incrementally captures changed data according to the synchronization representation and performs information synchronization based on the field synchronization identifier and priority identifier; Manually trigger the synchronization module: Data synchronization can be performed manually through the human-computer interaction interface; Synchronous transmission module, including: Real-time push module: Uses WebSocket to push high-priority data in real time; Message queue asynchronous transmission module: Uses RabbitMQ / Kafka message queues to asynchronously transmit low-priority data; Weak network adaptation and breakpoint resume module: Divide the data into multiple data segments for transmission, and record the transmission status through local caching. When the network is interrupted and reconnected, the unfinished segments are continued to be transmitted based on the transmission status recorded in the cache. Synchronization confirmation module: The "request-response-confirmation" three-stage strategy is used to transmit data. The "request-response-confirmation" three-stage strategy is configured as follows: After receiving the synchronization data, the receiver must return a confirmation receipt containing the data hash value within a predetermined time limit; if the sender does not receive the confirmation receipt or the synchronization fails, the receiver will resend the confirmation receipt. The synchronization conflict resolution module includes: Priority Strategy Module: Based on preset participant priority rules, in the event of a conflict, the data of the higher-priority participant shall prevail, the higher-priority data shall be automatically synchronized to other participants, and a conflict log shall be recorded. Negotiation Strategy Module: For core business data, it automatically pushes conflict alerts and conflict data to the administrator accounts of each participating party. After negotiating and confirming the correct data, it realizes full-link data update based on the resynchronization command initiated by the high-priority participating party. Log backtracking strategy module: Records all conflict data and resolution results in detailed logs, and uploads log summaries to the blockchain for evidence storage; The synchronization status monitoring and backtracking module includes: Real-time monitoring module: Acquires and displays the status of synchronization tasks, classifies and statistically analyzes the synchronization success rate by participants, business type, and time range, marks the reason for failure when synchronization fails, and responds to one-click retry instructions. Synchronization Log Module: Records the source participant, target participant, synchronization time, data content, synchronization status, and transmission time for each synchronized data entry. It supports precise queries based on business order number, time range, participant, and other criteria. Synchronization logs are retained for a predetermined period, and summary information is uploaded to the blockchain for evidence storage.

8. The system according to claim 1, characterized in that, It also includes a blockchain-based evidence storage and traceability module: Based on the immutable nature of blockchain, the adaptation rules and key data in the information synchronization process during the rapid migration process are notarized; the notarized content specifically includes DID identity authentication records, adaptation rule summaries, trade document information summaries, debt instrument issuance and circulation records, financing application and approval records, fund settlement flow, synchronization log summaries, and conflict resolution records. The evidence storage mechanism is configured as follows: sensitive data is hashed to generate a digest and then written to the supply chain finance consortium blockchain; the corresponding evidence storage information is queried by business order number to verify whether the data has been tampered with; the evidence storage data is retained for 5 years after the business ends. Based on the business order number, query the full-chain evidence storage information and generate a traceability report.

9. The system according to claim 1, characterized in that, It also includes an operation and maintenance monitoring module: Device status monitoring module: Real-time monitoring of the operating status of each module, monitoring server CPU, memory and bandwidth usage, and automatically triggering alarms when abnormalities occur; Adaptation rule maintenance module: used for batch import or export of adaptation rules, version rollback, and restoration to a historical stable version when a rule is abnormal; it also automatically verifies the validity of rules periodically. System upgrade and backup module: used for online canary upgrades without affecting existing synchronous services during the upgrade process; performs daily full backups and real-time incremental backups of device configuration data, adaptation rules, and synchronization logs, with encrypted storage of backup data and support for disaster recovery; Access Support Tools Module: Provides a new participant access guide, a common problem troubleshooting manual, and an online customer service portal to assist participants in quickly completing the integration and deployment; It supports remote assistance during the integration process, improving the efficiency of rapid migration and deployment.

10. A rapidly portable method for synchronizing information on a supply chain finance platform, characterized in that: include: Identity authentication steps: Unique identity identifiers are assigned to core enterprises, suppliers and financial institutions through distributed ledger technology, and identity verification and access control are performed when participating parties access the system based on a private key signature mechanism; Basic field standardization steps: This is used to pre-define a standardized data system that covers general basic fields, business-specific fields, and extended fields, serving as a unified semantic specification for data interaction between heterogeneous systems; Intelligent adaptation steps: Based on natural language processing technology, the participant's interface document is parsed, the participant's private fields are semantically mapped to the standardized data system, and the integration code that calls the system interface is automatically generated; Information synchronization scheduling steps: Listen for event trigger signals from business nodes, and distribute changed data to relevant participants according to preset synchronization priorities and conflict resolution strategies; Full business process integration steps: Drive all participating nodes to perform full-link transaction collaboration by triggering information synchronization scheduling steps.

Images