Cross-system file transmission method, apparatus, device, storage medium, and program product

Abstract

This application provides a cross-system file transfer method, apparatus, device, storage medium, and program product, relating to the fields of information security and fintech. Addressing the problems of poor protocol compatibility between heterogeneous operating systems, unstable transmission connections, and insufficient security protection during file transfer, it proposes a cross-system transfer scheme that combines configuration information from both ends. This scheme obtains the migration list of the source system and the configuration of the target system, analyzes the configuration differences between the source and target ends to match the applicable transmission protocol, encrypts the file to be transferred before transmission, establishes an encrypted communication channel based on the determined protocol, and sends the encrypted file to the target system. Using this application can improve the protocol adaptability, security, and reliability of file transfer and system migration between heterogeneous systems, and reduce the risks of transmission interruption, data leakage, and migration loss of control.

Description

Technical Field

[0001] This application relates to the fields of information security and financial technology, and in particular to a cross-system file transfer method, apparatus, device, storage medium and program product. Background Technology

[0002] Migrating core business systems from conventional operating systems to specific operating systems presents challenges such as ensuring business continuity across platforms, secure transmission of massive amounts of data, and the complexity of operation and maintenance management. For example, the batch migration of branch office terminals requires rapid deployment via offline image files in a network-free environment; in cross-system file interaction scenarios, sensitive business files need to be transmitted frequently between conventional and specific operating systems, requiring end-to-end encryption, real-time verification, and anti-tampering capabilities; in large-scale cluster deployment scenarios, a centralized domain management platform is needed to achieve unified push of account policies, dynamic adaptation of permissions, and performance optimization to ensure that the operating efficiency of the migrated business systems is no lower than that of the original environment.

[0003] In existing technologies, cross-platform file transfer and system migration suffer from protocol version incompatibility issues and lack end-to-end encryption, making sensitive data easily exposed. Inaccurate permission mapping and complex firewall rule configurations significantly reduce deployment efficiency. While encryption ensures data security, the encryption overhead causes performance bottlenecks during large file transfers, and the lack of integrated integrity verification mechanisms makes it impossible to detect data deviations during transmission.

[0004] Therefore, when migrating from a conventional operating system to a specific operating system, existing technologies struggle to balance compatibility, security, and efficiency requirements in cross-heterogeneous operating system environment migration and file transfer, directly impacting business continuity and data security. Summary of the Invention

[0005] This application provides a cross-system file transfer method, apparatus, device, storage medium, and program product to solve the technical problem that, when migrating from a conventional operating system to a specific operating system, it is difficult to balance compatibility, security, and efficiency requirements during cross-heterogeneous operating system environment migration and file transfer, which directly affects business continuity and data security.

[0006] In a first aspect, this application provides a cross-system file transfer method, including:

[0007] Obtain the migration list of the source system and the configuration file of the target system. The migration list includes the source files and configuration files of the source system.

[0008] Based on the configuration files of the source system and the target system, determine the transmission protocol between the source system and the target system;

[0009] A transmission channel is constructed based on an encryption algorithm, and the source file is encrypted to obtain the encrypted source file.

[0010] An encrypted communication channel is established using a transmission protocol. The encrypted source file is then transmitted to the target system via the transmission protocol and the encrypted communication channel.

[0011] Secondly, this application provides a cross-system file transfer device, comprising:

[0012] The file acquisition module is used to acquire the migration list of the source system and the configuration file of the target system. The migration list includes the source files of the source system and the configuration file of the source system.

[0013] The protocol dynamic adaptation module is used to determine the transmission protocol between the source system and the target system based on the configuration files of the source system and the target system.

[0014] The file encryption module is used to build a transmission channel based on encryption algorithms, encrypt the source file, and obtain the encrypted source file.

[0015] The file transfer module is used to establish an encrypted communication channel through a transmission protocol, and then transfer the encrypted source file to the target system through the transmission protocol and the encrypted communication channel.

[0016] Thirdly, this application provides an electronic device, including: a processor and a memory communicatively connected to the processor;

[0017] The memory stores the instructions that the computer executes;

[0018] The processor executes computer-executable instructions stored in memory to implement any of the methods of the first aspect.

[0019] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method of any one of the first aspects.

[0020] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method of any one of the first aspects.

[0021] The cross-system file transfer method, apparatus, device, storage medium, and program products provided in this application improve the protocol compatibility between heterogeneous systems by obtaining the migration list of the source system and the configuration file of the target system, and determining the transmission protocol between the source system and the target system based on the configuration files of the source system and the target system; enhance the data security protection capability during file transfer by constructing a transmission channel based on an encryption algorithm and encrypting the source file; and further improve the stability, reliability, and operational controllability of cross-system file transfer and system migration by constructing an encrypted communication channel through the transmission protocol and combining the transmission protocol and the encrypted communication channel to transmit the encrypted source file to the target system. Attached Figure Description

[0022] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0023] Figure 1 A flowchart illustrating a cross-system file transfer method provided in an embodiment of this application;

[0024] Figure 2 A schematic diagram of an architecture for transitioning from a source system to a target system, provided for an embodiment of this application;

[0025] Figure 3 A schematic diagram illustrating a system transition and file transfer process provided in an embodiment of this application;

[0026] Figure 4 A schematic diagram of a cross-system file transfer device provided in this application embodiment;

[0027] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0028] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0029] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in any of the foregoing embodiments.

[0030] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant countries and regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation access points for users to choose to authorize or refuse.

[0031] Furthermore, the technical solution involved in this application, which involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.) and the use of artificial intelligence technology for automated decision-making, and makes decisions that have a significant impact on personal rights based on the results of automated decision-making, provides users with corresponding operation entry points for users to choose to agree to or reject the results of automated decision-making; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0032] It should be noted that the cross-system file transfer method, apparatus, device, storage medium and program products provided in this application can be used in the fields of information security and financial technology, as well as in any field other than information security and financial technology. The application fields of the cross-system file transfer method, apparatus, device, storage medium and program products in this application are not limited.

[0033] This application specifically addresses file transfer and system migration between heterogeneous operating systems, particularly applicable to scenarios in finance, government, and energy, involving business file interaction, terminal environment migration, and cross-platform data flow between heterogeneous operating systems. Such scenarios typically consist of a source system, a target system, and the transmission link between them, requiring the cross-system transfer of files, configuration data, and runtime environments while maintaining business continuity.

[0034] Existing solutions typically employ network sharing, secure transmission, or virtualization to achieve cross-system file transfer and migration. For example, a sharing protocol establishes an access channel between the source and target systems, or a secure transmission protocol copies files from one end to the other. The basic principle is to complete file reading, writing, and data forwarding only if both systems support the corresponding protocols.

[0035] However, in practical applications, different operating systems have varying levels of support for protocol types and versions, which can easily lead to connection failures, negotiation anomalies, or transmission interruptions, making it difficult to establish stable transmission relationships between heterogeneous systems. At the same time, some solutions only provide limited link protection for sensitive files and lack data encryption mechanisms adapted to cross-system scenarios, leaving business files at risk of leakage or tampering during transmission.

[0036] Furthermore, when the transmitted data includes a large number of business files and configuration data related to the business environment, existing solutions often struggle to simultaneously ensure compatibility, security, and transmission efficiency. In cases of network fluctuations, massive data transmission, or significant differences in the target environment, transmission reliability may decrease, the migration process may become uncontrollable, and consequently, business continuity and subsequent operation and maintenance management may be affected.

[0037] In light of this, balancing protocol compatibility and file transfer security between heterogeneous operating systems has become a pressing technical challenge. To address this issue, a cross-system file transfer method is proposed. First, the migration list of the source system and the configuration file of the target system are obtained. Then, the transfer protocol between the source and target systems is determined based on their respective configuration files. A transmission channel is then constructed using an encryption algorithm to encrypt the source file. Finally, an encrypted communication channel is established through the transmission protocol to transmit the encrypted source file to the target system.

[0038] In a typical deployment architecture, the source system and the target system are connected via a network link or an offline import link. The source system stores the migration list and its configuration file, while the target system stores its configuration file. This technical approach allows for protocol determination during cross-platform transmission by combining configuration information from both ends, and ensures files remain encrypted before and after transmission. This improves the compatibility, security, and reliability of file transfer and system migration between heterogeneous systems.

[0039] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0040] Figure 1 This application provides a flowchart illustrating a cross-system file transfer method as shown in the embodiments. Figure 1 As shown, the method includes:

[0041] S101: Obtain the migration list of the source system and the configuration file of the target system.

[0042] In this embodiment of the application, the migration list includes the source files and configuration files of the source system.

[0043] In this application, the execution entity for this step can be a migration agent deployed on the source system side, a receiving agent deployed on the target system side, or a management server capable of simultaneously accessing both the source and target systems. The migration list carries the data content to be migrated from the source system. Its function is to structurally summarize the source files and source system configuration files, serving as the basic input for subsequent protocol determination and file transfer. Source files may include business documents, database export files, application installation packages, script files, log archives, and other file sets required for the migration task. The source system configuration files may include operating system type identifiers, version information, network protocol stack support, file system type, character encoding method, permission model, port open status, transmission service component status, and preset transmission constraints. The target system configuration files may include the target operating system type, kernel or distribution information, protocol support capabilities, receivable directories, disk space, decryption component status, network connectivity policies, and constraint parameters related to receiving.

[0044] In one possible embodiment, the process of obtaining the migration list includes the source system-side migration agent performing a deep scan of the preset migration directory, the specified business directory, and the configuration storage location; identifying the files to be migrated by traversing the directory tree; recording the path, filename, size, modification time, access permission identifier, and summary information of each file; and extracting configuration content related to the runtime environment from the source system registry, configuration center, local configuration directory, or service configuration interface. File data and configuration data are then uniformly written into a structured list file. This structured list can be stored in different formats such as key-value pair text or binary index, and includes at least a file entry area and an environment configuration area. For the target system's configuration file, the target system-side agent can read it from the local configuration directory, system command interface, or pre-set configuration template and send it back to the execution entity via the management server. In offline import scenarios, the target system's configuration file can also be pre-exported to a removable storage medium and then read by the source system as input.

[0045] In another possible embodiment, the migration list is not generated all at once, but rather a basic list is formed after the initial scan, and incremental verification is performed before formal transmission. If any files are added, deleted, or modified in the source system, the corresponding entries are updated to ensure that the subsequently transmitted objects are consistent with the actual source environment. For the source system's configuration files, system-level configurations and application-level configurations can be archived separately, and field mapping relationships can be established so that relevant fields can be extracted when the subsequent protocol is determined. The target system's configuration files can be stored using the same field system, thereby reducing parsing deviations caused by semantic differences in configurations between heterogeneous platforms.

[0046] Based on the above analysis, by obtaining both the migration list and the target system's configuration file before transmission, the content to be migrated from the source system and the constraints of the target environment can be uniformly included in the processing scope. This eliminates the need for repeated probing of the source file set and the target protocol capabilities during transmission, thus ensuring that protocol determination and file organization are based on verifiable data. It should be understood that the above example is merely illustrative and not limiting.

[0047] S102: Determine the transmission protocol between the source system and the target system based on the configuration files of the source system and the target system.

[0048] In this application, a transmission protocol is used to carry file transfer between the source system and the target system. Its function is to determine the available transmission method based on the configuration files of both parties, and to subsequently establish an encrypted communication channel and complete the file transfer. In this step, the executing entity can extract information related to protocol usage from the configuration files of the source system and the target system, and determine the appropriate transmission protocol between the source and target systems based on the extraction results.

[0049] In one possible embodiment, the executing entity can pre-set multiple optional protocols and analyze the optional protocols in combination with the protocol enable status and port constraints in the source system's configuration file and the listening service status, receiving mode and directory write restrictions in the target system's configuration file, thereby determining the protocol used for this file transfer.

[0050] For example, the process of determining the transmission protocol can output protocol-related parameters for subsequent channel establishment and file transmission control. Based on the above analysis, this step, by analyzing the configuration files of the source system and the target system, determines the transmission protocol between the two systems, providing a clear basis for the connection method between heterogeneous operating systems, thereby supporting the continuous execution of subsequent encrypted transmission. It should be understood that the above example is merely illustrative and not limiting.

[0051] S103: Construct a transmission channel based on an encryption algorithm, encrypt the source file, and obtain the encrypted source file.

[0052] In this application, the encryption algorithm is used to encrypt the source file, and its function is to construct a transmission channel based on the algorithm and ensure the security of the source file during transmission. The transmission channel is used to encrypt the source file and support subsequent secure transmission, and its function is to connect the encryption algorithm with the file transmission process. In this step, after the transmission protocol is determined, the execution entity first initializes the encryption module, loads the encryption algorithm identifier, key length, working mode, initialization vector generation rules, and integrity verification method, and then reads the source files one by one according to the migration list, and completes the encryption process on the source system side. The encryption algorithm can be a combination of symmetric encryption algorithm, asymmetric encryption algorithm, and digest verification algorithm, wherein the symmetric key is used to encrypt the file body, the asymmetric mechanism is used to encapsulate the session key, and the digest algorithm generates the integrity verification value. Correspondingly, the transmission channel can consist of a file reading interface, an encryption processing buffer, a key management unit, a segmentation and encapsulation unit, and a pending transmission buffer queue. The file enters the encryption process before leaving the source system storage medium.

[0053] In one possible implementation, the executing entity generates a session key for this transmission task and obtains key protection parameters from the target system's public key certificate or pre-shared key information. Then, according to the file entries in the migration list, the source file content is read in blocks. Each block is processed by an encryption algorithm to form a ciphertext block, which is finally written to the encrypted file buffer to form the encrypted source file. For large files, streaming encryption can be used, encrypting and writing to the buffer queue simultaneously to reduce the source system's memory usage; for small files, whole-file encryption can be used, generating the complete ciphertext file locally before sending it all at once. If the source system's configuration file itself is included in the migration list, it is also processed according to the same encryption process, thus ensuring that file data and environment configuration data are transmitted under a unified protection mechanism.

[0054] In another possible embodiment, the transmission channel not only performs the encryption task but also records encryption metadata for each file, such as algorithm identifier, key encapsulation result, initialization vector, number of blocks, and original file digest. This metadata can be written into the encrypted file header or a separate index list can be generated and transmitted along with the encrypted file. For text configuration files containing sensitive fields, field normalization processing can be performed before full file encryption, such as standardizing newline characters and character encoding, to reduce parsing anomalies caused by differences in character sets across heterogeneous systems. For binary files and compressed files, encryption can be performed directly on a byte-stream basis without semantically rewriting their original content.

[0055] For example, encryption is completed before the source file leaves the source system. After encryption, the executing entity can record the encrypted source file digest value and file path mapping to facilitate subsequent reception and processing. Based on the above analysis, this step converts the plaintext source file to be transmitted into key-controlled ciphertext data, and organizes file reading, encryption, encapsulation, and caching into a continuous processing chain through the transmission channel. This ensures that even if subsequent relays or caching occur at the protocol layer, the encrypted source file remains unreadable. It should be understood that the above example is merely illustrative and not limiting.

[0056] S104: Establish an encrypted communication channel through the transmission protocol, and transmit the encrypted source file to the target system through the transmission protocol and the encrypted communication channel.

[0057] In this application, the encrypted communication channel is used as a communication link to achieve secure transmission over a transmission protocol. Its function is to enable the encrypted source file to be transmitted to the target system in a protected communication environment. In this step, the executing entity establishes a network connection or an offline export connection according to the protocol-related parameters output in S102, and completes authentication, parameter negotiation, session establishment, and data transmission preparation on this connection. If an online transmission method is used, the source system initiates a connection request to the target system, completes port access, certificate or credential verification, session parameter exchange, and connection confirmation according to the selected protocol, and forms an encrypted communication channel. If an offline import method is used, the executing entity writes the encrypted source file and task index to a controlled storage medium. When the target system imports the file, the local receiving agent parses the encapsulation structure and restores the receiving session semantics using the same protocol. Regardless of whether the method is online or offline, the transmission protocol is responsible for connection management, data segmentation, sequence control, retransmission control, and termination confirmation, while the encrypted communication channel is responsible for session-level protection, link integrity verification, and secure encapsulation during transmission.

[0058] In one possible embodiment, the executing entity splits the encrypted source file into multiple data packets according to the negotiated segment size on the source system side, and sends them to the target system segment by segment via a transmission protocol. The receiving agent on the target system side processes the received data and, after transmission, reassembles and verifies it using the task index. For batch file transfers, a queue-based task scheduling method can be used, sending files sequentially according to the order in the migration list or by file size, and updating the task status table after each file is transferred.

[0059] In another possible embodiment, after receiving the encrypted source file, the target system performs decryption based on the key encapsulation information or preset key information transmitted with the file, restoring the ciphertext into a business file or configuration file that can be written to the target system. After decryption, the target system writes the file to the target directory according to the path mapping relationship in the migration list, and restores file access permissions, owner information, or application configuration location according to the permission or attribute information in the configuration file. If the file system semantics of the target system and the source system are different, the receiving agent completes path separator conversion, filename encoding conversion, and permission bit adaptation according to preset mapping rules before completing the disk writing. For scenarios where only transmission is required and decryption is not immediate, the target system can also first save the encrypted source file and its index, and then perform unified decryption and deployment when the business window allows.

[0060] Based on the above analysis, it can be seen that by constructing an encrypted communication channel through a transmission protocol and sending encrypted source files within this channel, a transmission mechanism combining protocol adaptation and data protection is effectively formed. The protocol layer ensures reachable connections and stable transmission based on the capabilities of the source and target systems. The file layer and channel layer respectively implement encryption protection for the transmitted objects and the session process. After receiving the data, the target system performs verification, decryption, and disk writing based on the task index, thereby completing cross-system file transfer between heterogeneous operating systems.

[0061] In one implementation scenario, Figure 2 This application provides an embodiment of an architecture diagram illustrating the transition from a source system to a target system. Figure 2 As shown, the transition architecture includes a migration preprocessing module, an environment cloning module, and an adaptation optimization module. The specific implementation includes: (1) Migration preprocessing module: deployed on the source system terminal, it obtains user files, application configurations, system preference settings and peripheral driver information through deep scanning, generates a standardized migration list, and supports user-defined filtering of migration content; it converts the source system driver based on the compatibility layer to generate a driver installation package adapted to the target system.

[0062] (2) Environment cloning module: Supports online / offline modes. In online mode, the complete environment data corresponding to the migration list is transmitted to the target system terminal through an encrypted tunnel. In offline mode, the pre-processed image file is imported through a removable storage medium. It integrates breakpoint resume and consistency verification mechanisms, ensures data integrity by comparing file hash values, and automatically resumes transmission progress when the network fluctuates.

[0063] (3) Adaptation and Optimization Module: Through the target system's centralized domain management platform within the financial institution, it provides a functional replacement for the source system's Active Directory domain, supporting unified account management, policy configuration distribution, compliance checks, peripheral device control, and software distribution; it adopts a headquarters-branch hierarchical architecture to achieve synergy between unified policy distribution and localized autonomous management. Based on the target system's kernel security framework, it performs permission adaptation for the migrated applications; it collects system performance data through performance tuning tools, intelligently adjusts resource allocation parameters, and ensures that the application's operating efficiency is no lower than that of the original source system environment.

[0064] File secure transmission and sharing mechanism: The mechanism includes a static address configuration module, a multi-protocol transmission adaptation module, a virtual file sharing module and a full-link security protection module: (1) Static address configuration module: Automatically assigns the same network segment static address to the source system and the target system terminal. The source system terminal automatically switches the network type to a private network and turns off the firewall. The target system terminal quickly configures the address and enables the network card through the command line without manual operation.

[0065] (2) Multi-protocol transmission adaptation module: Small file transmission: The application layer network transmission protocol is used to realize cross-system file drag and drop sharing. The source system terminal accesses the target system's shared folder through the network address and supports fine-grained permission control; Large file / folder transmission: The optimized protocol is used, combined with encryption algorithm, to reduce encryption overhead and increase the transmission rate by more than 30% under gigabit network; Supports file fragment transmission and batch packaging transmission of millions of small files; Real-time interactive scenario: The target system's directory is mapped to the source system's local drive through mounting technology to realize real-time file editing and access without repeated transmission.

[0066] (3) Virtual file sharing module: Construct a cross-system shared virtual file tree. The main system domain (target system) maintains the shared file node information and obtains the node mapping from the system domain (source system) through shared memory. It supports multiple permission tags such as normal mode, read-only mode, and privileged sharing mode, and realizes the compatibility conversion of file interfaces of different systems through a file simulator.

[0067] (4) Full-link security protection module: Before transmission: integrates anti-virus engine and data leakage prevention technology to identify sensitive information and intercept malicious files; During transmission: adopts encryption protocol to build dynamic encryption tunnel to achieve "one transmission, one encryption"; After transmission: file is encrypted on disk and generates a watermark containing user identifier and address, supports log retention for more than 6 months, and meets compliance requirements.

[0068] Figure 3 This application provides a schematic diagram of a system transition and file transfer process, as shown in the embodiments. Figure 3 As shown, the transition process may include:

[0069] Step 1: Deploy the migration preprocessing module on the source system terminal to complete environment scanning, driver conversion, and migration list generation.

[0070] Step 2: Select online / offline mode according to the application scenario, and realize the complete environment migration through the environment cloning module. Enable breakpoint resume and consistency verification during the migration process.

[0071] Step 3: Configure the domain management replacement module on the target system terminal to complete the account and policy migration and achieve centralized operation and maintenance.

[0072] Step 4: Complete application permission configuration and performance tuning through the adaptation and optimization module, and verify business continuity.

[0073] Step 5: Based on the secure file transfer mechanism, realize file interaction between the source system and the target system terminal, or complete data sharing after migration.

[0074] For example, there are two scenarios: online migration and offline migration. Scenario 1: The operation steps of the online migration scenario may include: (1) starting the migration preprocessing module of the source system terminal, scanning and generating a migration list containing office software and financial system configuration; (2) automatically assigning addresses through the static address configuration module, and the source system terminal automatically switching to a dedicated network; (3) using the online mode to transmit migration data through the environment cloning module, including business files and application configuration, and automatically recovering after network interruption; (4) configuring the domain management replacement module, creating department accounts and issuing security policies; (5) optimizing the performance of the financial system through tools; (6) using the application layer network transmission protocol to realize daily file sharing between the two terminals.

[0075] Scenario 2, Offline Migration Scenario: The hardware environment consists of a source system cluster (100 terminals) and a target system cluster (100 terminals), with no network connection. The operation steps include: (1) Deploying the migration preprocessing module on the source system management terminal to generate cluster migration image files in batches and storing them on an encrypted USB drive; (2) Importing the image files into the target system cluster in offline mode, with the environment cloning module supporting parallel deployment; (3) Configuring the domain management replacement module, with the branch responsible for local terminal maintenance; using the virtual file sharing module to achieve file sharing within the target system cluster, supporting cross-branch data access for privileged users; (4) After the migration is completed, transmitting the historical data of the legacy source system terminals in batches to the target system terminals via the network transmission protocol, with no errors in the consistency check.

[0076] In another implementation scenario, a financial institution needs to migrate a batch of source system office terminals distributed across multiple branches without network connectivity to a target system, ensuring that the migrated terminals can securely and efficiently exchange files with the headquarters server. The scenario involves migrating source system terminals from 100 branches of a provincial branch of a bank to the target system. These 100 source system terminals need to complete the migration in a network-free environment. After migration, the terminals need to transmit 1TB of sensitive business files, including customer files, transaction logs, customer information, and transaction records, to the headquarters server via an encrypted tunnel. The headquarters uses a centralized domain management platform to uniformly manage the account permissions and security policies of the branch terminals, and uniformly push security policies and dynamically adjust terminal permissions and performance parameters. Before the migration, a migration list for the source system and configuration files for the target system are obtained. The migration list contains source files and configuration files for the source system. A migration preprocessing module is deployed on each source system terminal to scan user files, including office software configurations and customer information databases; application configurations, including financial system settings; and peripheral drivers, including printer drivers.

[0077] After obtaining the source system data through scanning, the system parses the supported protocol types, versions, file interface definitions, and system adaptation parameters based on the source system's configuration file and the corresponding configuration file of the target system. This process detects compatibility information between the source and target systems, obtaining the matching relationships between various protocol types and versions. Simultaneously, based on the source and target system configuration files, a file simulator is used to simulate differences in file interfaces between the two systems, mapping the source system's file interfaces to compatible formats for the target system. During this mapping process, interface fields, call formats, directory structures, and file encapsulation methods are converted accordingly. The migration preprocessing module, based on the compatibility layer, converts the source system driver into a driver installation package adapted for the target system and generates a standardized migration list containing 50GB of business files and 10 application configurations. For example, the driver for a branch's financial system is converted to a compatible version for the target system, ensuring the printer functions correctly after migration. The migration list corresponds to complete environment data, including files, configurations, and driver installation packages, and is subsequently imported offline via encrypted storage media.

[0078] After obtaining compatibility information, a set of matching protocols is determined from the matching relationships of protocol types and versions. The protocol selection strategy is dynamically adjusted based on network environment parameters, including bandwidth, latency, and packet loss rate. For file interaction between a bank branch and its headquarters server, the current network environment parameters, compatibility information, and protocol operating characteristics can be input into a preset machine learning model. The model predicts matching protocols that meet preset conditions as the transmission protocol. Alternatively, based on historical transmission records, the usage frequency of each matching protocol can be statistically analyzed, and the matching protocol with a usage frequency greater than a preset frequency threshold can be selected as the transmission protocol. When multiple candidate protocols exist, the dynamically adjusted protocol selection strategy selects the protocol that meets the preset conditions from the set of matching protocols and determines it as the transmission protocol between the source system terminal and the headquarters server after migration. In small file scenarios, the multi-protocol transmission adaptation module uses an application-layer network transmission protocol to achieve cross-system drag-and-drop sharing of design drawings. In large file scenarios, an optimized network transmission protocol is used for 1TB-level customer files and 1TB transaction log files. In real-time interaction scenarios, mounting technology maps the target system directory to the source system's local drive. When a branch office transmits 1TB of transaction log files to headquarters, it uses a network transmission protocol under a gigabit network and combines encryption algorithms to handle encryption overhead.

[0079] In the environment cloning phase, an offline mode is used to import the complete environment data corresponding to the migration list into the target system terminal via an encrypted USB drive. During offline environment deployment, branch offices have no network connection, and the migration data is imported via encrypted storage media. The environment cloning module is deployed in parallel to 100 terminals, with a single-terminal migration taking 30 minutes. After the transmission protocol is determined, a transmission channel is constructed based on an encryption algorithm. The source file is encrypted to obtain the encrypted source file, and an encrypted communication channel is established through the determined transmission protocol. In this scenario, the encrypted communication channel can use a dynamic encryption tunnel, employing encryption algorithms in file content encryption. The encrypted source file is transmitted according to application-layer network transmission, network transmission protocols, or file transfer protocols. The encrypted source file is sent in the encrypted communication channel according to the transmission protocol, and a corresponding checksum is generated for each transmitted encrypted source file during transmission. The checksum is recorded in relation to the transmission progress to meet end-to-end encryption and real-time verification requirements.

[0080] If an interruption occurs during transmission, including interruptions due to USB drive insertion / removal during offline import, USB drive failure during image file import at a branch, or file transfer failure due to storage abnormalities at the branch terminal, the completed and incomplete portions are compared based on the generated checksum to locate the incomplete encrypted source file or file fragment. In the case of an interrupted image file import at a branch, the module automatically records the position of the transmitted data and resumes the transmission progress, automatically locating the incomplete 10GB data block and retransmitting it, without performing a full retransmission. In the case of failed business file transmission between headquarters and branches, the centralized domain management platform automatically triggers the breakpoint resume module to retransmit the damaged data block. After the encrypted communication channel is restored, the remaining content continues to be transmitted according to the location result until the encrypted source file is transmitted to the target system. When importing complete environment data to the target system terminal in an offline environment, the incomplete portion is also imported in the same way.

[0081] After migration, the terminals entered the adaptation, optimization, and performance tuning phase. Branch account creation and security policies were implemented through the domain management replacement module, including disabling external USB drive connections. Simultaneously, permission policies were adjusted based on the kernel security framework corresponding to the target system's security mechanisms, including restricting ordinary users' access to the financial system. Headquarters centrally managed the account permissions and security policies of 100 branch terminals through the domain management replacement module's centralized domain management platform, monitoring the operational status of all 100 terminals. Cross-system permission isolation was achieved through a virtual file sharing module, including allowing only administrators to access sensitive files. Meanwhile, performance tuning tools were used to collect system performance data, including CPU utilization and memory usage, and resource allocation parameters were intelligently optimized based on the collected results. After optimization, the CPU utilization of one branch's business system decreased from 75% to 40%, and the migrated business environment continued to run on the target system terminals.

[0082] During centralized operations and maintenance at headquarters, logs are retained for migration, transmission, permission granting, breakpoint resume triggering, retransmission of corrupted data blocks, and access to sensitive files. Logs are kept for at least six months to meet compliance requirements. The migrated target system terminals continue to support cross-system file transfer, drag-and-drop sharing, and directory mapping access with the headquarters server. Customer files, transaction logs, customer information, transaction records, design drawings, and financial system-related files are processed according to compatibility information, protocol type and version matching, file interface mapping results, and dynamically adjusted protocol selection strategies.

[0083] The cross-system file transfer method provided in this embodiment includes obtaining a migration list from the source system and a configuration file from the target system. The migration list includes source files and configuration files from the source system. Based on the configuration files of the source and target systems, a transmission protocol between the source and target systems is determined. A transmission channel is constructed based on an encryption algorithm, and the source files are encrypted to obtain encrypted source files. An encrypted communication channel is constructed using the transmission protocol, and the encrypted source files are transmitted to the target system via the transmission protocol and the encrypted communication channel. In this application, by sequentially connecting the acquisition of the migration list, configuration matching at both ends, construction of the encrypted channel, and encrypted communication transmission, a file transfer process for heterogeneous operating system environments is realized. The migration list provides a unified input for the information of the object to be migrated and the source environment; the configuration file matching result provides a basis for the selection of the transmission protocol; the encryption algorithm and the transmission channel ensure that the source files are converted into encrypted source files before leaving the source system; and the transmission protocol and the encrypted communication channel jointly ensure the reliable delivery of encrypted data between the source and target systems. This allows protocol compatibility processing and data security processing to be incorporated into the same transmission process, enabling cross-platform transfer of business files, configuration data, and related operating environment information in migration scenarios where heterogeneous operating systems coexist. It should be understood that the above examples are for illustrative purposes only and are not intended to be limiting.

[0084] Based on the foregoing embodiments, further, the transmission protocol between the source system and the target system is determined according to the configuration file of the source system and the configuration file of the target system, including: detecting compatibility information between the source system and the target system according to the configuration file of the source system and the configuration file of the target system, wherein the compatibility information includes the matching relationship between the protocol types and versions supported by the source system and the target system; determining a set of matching protocols according to the compatibility information, and selecting the matching protocol that meets the preset conditions from the set of matching protocols as the transmission protocol.

[0085] In the specific implementation, the configuration files of the source system and the target system can be stored in the local configuration directory or read through a remote interface, respectively. After reading, the system parses the protocol field, version field, and compatibility flag field, and establishes a correspondence matrix between protocol types and versions. When there is an overlap between the protocol types supported by the source system and the protocol types supported by the target system, the system further compares the version number range, eliminates protocol items that exceed the range supported by both parties, and marks the protocol items that can be recognized by both parties as matching protocol candidates, thereby forming a set of matching protocols.

[0086] After forming a set of matching protocols, the system selects candidate protocols based on preset conditions. These preset conditions may include transmission latency thresholds, handshake success rates, link persistence capabilities, and security negotiation capabilities. The system can comprehensively judge based on the candidate protocol's performance score in historical transmission records, the target system's support for encryption negotiation, and the source system's support for session multiplexing, and determine the protocol that meets the conditions as the transmission protocol. If multiple candidate protocols meet the conditions, the protocol that is suitable for the current network environment and service load can be selected as the final transmission protocol according to preset priority rules.

[0087] Using the above method, the system can perform protocol type and version compatibility checks based on the configuration files at both ends, and select a protocol that meets the transmission constraints from the available protocol range as the transmission protocol. This ensures that the protocol determination process is consistent with the actual support capabilities of the heterogeneous system. Since the transmission protocol is derived from qualified items in the set of matching protocols, the probability of protocol negotiation failure is reduced, and a stable protocol foundation is provided for the establishment of subsequent encrypted communication channels.

[0088] In one possible implementation, before selecting a matching protocol from the set of matching protocols that meets preset conditions as the transmission protocol, the method further includes: dynamically adjusting the protocol selection strategy based on network environment parameters, which are used to characterize network state indicators that affect the performance of the matching protocol, including bandwidth, latency, and packet loss rate.

[0089] When the bandwidth exceeds a preset threshold, the processing unit can prioritize matching protocols with high throughput characteristics; when the latency or packet loss rate exceeds the threshold, the processing unit can prioritize matching protocols with higher retransmission tolerance and stronger connection stability. If network environment parameters fluctuate continuously within a preset time window, the processing unit can also perform a sliding update on the protocol selection strategy to ensure that the current judgment conditions used to filter transmission protocols are consistent with the real-time network status. The above processing can be completed by a protocol control module running on the source system. The protocol control module includes a parameter acquisition unit, a policy update unit, and a protocol sorting unit. Data transfer between these units is completed through memory sharing or inter-process communication. In practical applications, this module can also adopt other implementation forms, which are not limited in this application.

[0090] In this way, the protocol selection strategy can be dynamically adjusted according to changes in bandwidth, latency and packet loss rate, so that the screening results of the matching protocol are adapted to the current network status, thereby making the subsequently selected transmission protocol more in line with the actual link conditions and maintaining the stability and continuity of cross-system file transfer.

[0091] In one possible implementation, the method further includes: based on the configuration files of the source system and the target system, using a file simulator to simulate the differences in file interfaces between the source system and the target system, and mapping the file interface of the source system to a file interface of a format compatible with the target system.

[0092] In practical implementation, the file simulator can be deployed in a file access intermediary layer between the source and target systems. It receives file interface descriptions from the source system and compatibility constraints from the target system. After parsing file paths, directory identifiers, read / write permission flags, and encoding identifiers, it generates a mapping table. Based on this mapping table, it converts the source system's file interface into a compatible file interface format recognizable by the target system. If the source system uses a different path separator, permission bit representation, or text encoding than the target system, the file simulator normalizes the corresponding fields and outputs an interface representation consistent with the target system's file processing logic, enabling subsequent file access to be parsed and invoked according to the target system's rules.

[0093] In practical deployments, the file emulator can be implemented by a software module or by an adaptation module integrated into the migration tool. The specific model can be selected according to the interface specifications of the target operating system to achieve cross-system adaptation while maintaining consistent interface semantics. In practical applications, other models can also be selected for this component, and this application does not limit this. Through the above mapping process, the file interface that was originally incompatible on the source system side is converted into a format that the target system can directly recognize, thereby enabling file transfer and subsequent access to be carried out under a unified interface semantics.

[0094] By adopting this method, file interface differences are identified and mapped in advance, and file access rules between the source system and the target system are unified. This resolves the interface mismatch problem in the cross-platform file interaction process, and improves the consistency and resolvability of file transfer and migration.

[0095] Based on the aforementioned embodiments, the encrypted source file is further transmitted to the target system via a transmission protocol and an encrypted communication channel, including: generating a verification value for the transmitted encrypted source file via the transmission protocol and the encrypted communication channel; and, in the event of a transmission interruption, locating the encrypted source file whose transmission was not completed based on the verification value and resuming the transmission.

[0096] In practical implementation, the source system can segment the encrypted source file according to a preset segment size during transmission and send each segment to the target system via a transmission protocol and encrypted communication channel. After receiving each segment of data, the target system generates a checksum for the currently received content and saves it locally. The checksum can be formed using a combination of hash digest, cyclic redundancy check (CRC) value, or segment digest. The checksum can record the reception status of each segment as well as the cumulative status of continuous transmission intervals, enabling the target system to determine the end position of the completed transmission based on the last valid checksum when there are link fluctuations, connection interruptions, or session anomalies.

[0097] When a transmission interruption occurs, the target system reads the saved checksum and compares it with the currently received encrypted file status to locate the incomplete file portion. Subsequently, based on the starting offset or fragment number of the incomplete portion, the target system initiates a transmission recovery request to the source system. The source system only retransmits the incomplete data segment, without retransmitting the completed segment. The recovered data continues to be transmitted to the target system along the original transmission protocol and encrypted communication channel, and a new checksum is generated at the receiving end for verification, ensuring continuity of the transmission state before and after the interruption.

[0098] This method enables transmission verification and breakpoint recovery to be completed within the same encrypted link, allowing for the recording of the status of transmitted content and the targeted resumption of incomplete content, thereby improving the continuity and integrity of cross-system file transfers.

[0099] In one possible implementation, selecting a matching protocol from the set of matching protocols that meets preset conditions as the transmission protocol includes: using a preset machine learning model to predict a matching protocol that meets the preset conditions as the transmission protocol; and / or, based on historical transmission records, selecting a matching protocol whose usage frequency is greater than a preset frequency threshold as the transmission protocol.

[0100] In its implementation, the system generates a set of matching protocols after obtaining compatibility information. The features of these protocols are then input into a pre-defined machine learning model, which outputs candidate protocols that meet pre-defined conditions. When a historical statistics mechanism is simultaneously enabled, the system summarizes the frequency of each protocol in historical transmission records and calculates its ratio to the total number of transmissions to obtain the corresponding usage frequency. Protocols exceeding a threshold are directly used as transmission protocols or as a verification criterion for the model's output. If the protocol output by the model matches a historically high-frequency protocol, it is directly identified as the transmission protocol. If they do not match, network environment parameters are used to constrain and filter the model results to obtain the final transmission protocol. This machine learning model can continuously update its parameters based on newly added historical transmission records during operation or be periodically retrained to ensure that the prediction results are consistent with the actual transmission environment. In practical applications, other algorithm structures can also be selected for this model, which is not limited in this application.

[0101] This approach incorporates both learning prediction and historical statistics during the protocol selection phase. This allows the transmission protocol to be determined by combining current environmental characteristics with past usage patterns, resulting in a more accurate match between the selected protocols and the actual transmission conditions between heterogeneous systems. It also enhances the stability and consistency of the protocol selection process. By limiting the protocols that meet preset conditions to the range of model predictions or high-frequency historical protocols, the selected transmission protocol is more likely to match the support capabilities of the target system, thus providing a reliable foundation for the subsequent establishment of encrypted communication channels and the transmission of source files.

[0102] Figure 4 A schematic diagram of a cross-system file transfer device provided in this application embodiment is shown below. Figure 4 As shown, the cross-system file transfer device 40 provided in this embodiment includes:

[0103] File acquisition module 401 is used to acquire the migration list of the source system and the configuration file of the target system. The migration list includes the source files of the source system and the configuration file of the source system.

[0104] The protocol dynamic adaptation module 402 is used to determine the transmission protocol between the source system and the target system based on the configuration files of the source system and the target system.

[0105] The file encryption module 403 is used to build a transmission channel based on an encryption algorithm, encrypt the source file, and obtain the encrypted source file.

[0106] The file transfer module 404 is used to establish an encrypted communication channel through a transmission protocol, and to transfer the encrypted source file to the target system through the transmission protocol and the encrypted communication channel.

[0107] In one possible implementation, the protocol dynamic adaptation module 402 is specifically used to: detect compatibility information between the source system and the target system based on the configuration files of the source system and the target system, the compatibility information including the matching relationship between the protocol types and versions supported by the source system and the target system; determine a set of matching protocols based on the compatibility information, and select the matching protocol that meets the preset conditions from the set of matching protocols as the transmission protocol.

[0108] In one possible implementation, the protocol dynamic adaptation module 402 is further specifically used to: dynamically adjust the protocol selection strategy according to network environment parameters, which are used to characterize network state indicators that affect the performance of the matching protocol, including bandwidth, latency and packet loss rate.

[0109] In one possible implementation, the cross-system file transfer device is further specifically used to: simulate the differences in file interfaces between the source system and the target system using a file simulator, based on the configuration files of the source system and the target system, and map the file interface of the source system to a file interface of a compatible format for the target system.

[0110] In one possible implementation, the file transfer module 404 is specifically used to: generate a verification value for the transmitted encrypted source file through a transmission protocol and an encrypted communication channel; and, in the event of a transmission interruption, locate the encrypted source file whose transmission was not completed based on the verification value and resume transmission.

[0111] In one possible implementation, the protocol dynamic adaptation module 402 is further specifically used to: use a preset machine learning model to predict a matching protocol that meets preset conditions as the transmission protocol; and / or, based on historical transmission records, select a matching protocol whose frequency of use is greater than a preset frequency threshold as the transmission protocol.

[0112] The cross-system file transfer device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0113] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device 50 may include a memory 501 and a processor 502. Optionally, the electronic device may also include a transceiver 503, wherein the memory 501 and the processor 502 communicate with each other; for example, the memory 501, the processor 502 and the transceiver 503 may communicate via a communication bus 504, the memory 501 is used to store a computer program, and the processor 502 executes the computer program to implement the method of the above embodiments.

[0114] Optionally, the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps in the method embodiments disclosed in this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0115] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the methods in any of the above method embodiments.

[0116] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the methods in any of the above method embodiments.

[0117] All or part of the steps in the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0118] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0119] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0120] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0121] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of this application and its equivalents, this application also intends to include these modifications and variations.

[0122] In this application, the term "comprising" and its variations can refer to non-limiting inclusion; the term "or" and its variations can refer to "and / or". The terms "first", "second", etc., in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. In this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0123] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0124] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0125] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0126] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or in the form of software program modules.

[0127] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0128] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0129] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0130] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0131] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope.

Claims

1. A cross-system file transfer method, characterized in that, The method includes: Obtain the migration list of the source system and the configuration file of the target system, wherein the migration list includes the source files of the source system and the configuration file of the source system; Based on the configuration files of the source system and the target system, the transmission protocol between the source system and the target system is determined; A transmission channel is constructed based on an encryption algorithm, and the source file is encrypted to obtain the encrypted source file. An encrypted communication channel is established using the aforementioned transmission protocol, and the encrypted source file is transmitted to the target system via the transmission protocol and the encrypted communication channel.

2. The method according to claim 1, characterized in that, The step of determining the transmission protocol between the source system and the target system based on the configuration file of the source system and the configuration file of the target system includes: Based on the configuration files of the source system and the target system, the compatibility information between the source system and the target system is detected. The compatibility information includes the matching relationship between the protocol types and versions supported by the source system and the target system. Based on the compatibility information, a set of matching protocols is determined, and a matching protocol that meets preset conditions from the set of matching protocols is selected as the transmission protocol.

3. The method according to claim 2, characterized in that, Before selecting a matching protocol from the set of matching protocols that meets preset conditions as the transmission protocol, the method further includes: The protocol selection strategy is dynamically adjusted based on network environment parameters, which are used to characterize network status indicators that affect the performance of the matching protocol, including bandwidth, latency, and packet loss rate.

4. The method according to claim 1, characterized in that, The method further includes: Based on the configuration files of the source system and the target system, a file simulator is used to simulate the differences in file interfaces between the source system and the target system, and to map the file interface of the source system to a file interface in a format compatible with the target system.

5. The method according to claim 1, characterized in that, The step of transmitting the encrypted source file to the target system via the transmission protocol and the encrypted communication channel includes: The verification value of the transmitted encrypted source file is generated using the transmission protocol and the encrypted communication channel. In the event of a transmission interruption, the encrypted source file whose transmission was incomplete is located and transmission is resumed based on the verification value.

6. The method according to claim 2, characterized in that, The step of selecting a matching protocol from the set of matching protocols that meets preset conditions as the transmission protocol includes: A preset machine learning model is used to predict matching protocols that meet preset conditions as the transmission protocol. And / or, based on historical transmission records, select a matching protocol with a frequency greater than a preset frequency threshold as the transmission protocol.

7. A cross-system file transfer device, characterized in that, The device includes: The file acquisition module is used to acquire the migration list of the source system and the configuration file of the target system. The migration list includes the source files of the source system and the configuration file of the source system. The protocol dynamic adaptation module is used to determine the transmission protocol between the source system and the target system based on the configuration file of the source system and the configuration file of the target system. The file encryption module is used to construct a transmission channel based on an encryption algorithm, encrypt the source file, and obtain the encrypted source file. The file transfer module is used to establish an encrypted communication channel through the transmission protocol, and to transfer the encrypted source file to the target system through the transmission protocol and the encrypted communication channel.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 6.

Images