A method, device and readable storage medium for software cross-system migration

Abstract

The application provides a software cross-system migration method, device and equipment and a readable storage medium, relates to the technical field of computers, and comprises the following steps: obtaining hardware information of a target terminal; judging whether the target terminal meets a migration condition based on the hardware information; performing initial system resource reconfiguration and installing a target system in the case of meeting the migration condition; restarting the target terminal to enter the target system, mapping data of the initial system to the target system; verifying the data in the data mapping process; mounting the data of the initial system and completing software migration in the case of passing the data verification.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically, to a method, apparatus, device, and readable storage medium for cross-system software migration. Background Technology

[0002] In the field of information technology, replacing foreign commercial products with domestically developed ones has become a necessity for national strategic security. Currently, most software in my country's information systems is only available for Windows, making it difficult to adapt to domestically developed systems. During the current transition phase of domestic system adoption, switching from Windows to domestic systems can easily lead to software malfunctions, thus hindering work progress. Modifying the software to adapt to newly developed systems involves a lengthy modification cycle, and the software's functionality also requires real-time updates, which is time-consuming and difficult to meet production needs. Summary of the Invention

[0003] The purpose of this invention is to provide a method, apparatus, device, and readable storage medium for software cross-system migration, in order to improve the aforementioned problems. To achieve the above objective, the technical solution adopted by this invention is as follows:

[0004] In a first aspect, this application provides a method for cross-system software migration, comprising: obtaining hardware information of a target terminal; determining whether the target terminal meets migration conditions based on the hardware information; if the migration conditions are met, performing initial system resource reconfiguration and installing the target system; restarting the target terminal to enter the target system, and mapping the data of the initial system to the target system; verifying the data during the data mapping process; and if the data verification is successful, mounting the data of the initial system and completing the software migration.

[0005] Secondly, this application also provides an apparatus for cross-system software migration, comprising: an acquisition unit for acquiring hardware information of a target terminal; a judgment unit for judging whether the target terminal meets migration conditions based on the hardware information; a configuration unit for reconfiguring initial system resources and installing the target system when the migration conditions are met; a mapping unit for restarting the target terminal to enter the target system and mapping the data of the initial system to the target system; a verification unit for verifying the data during the data mapping process; and a data mounting unit for mounting the data of the initial system and completing the software migration when the data verification is successful.

[0006] Thirdly, this application also provides a device for software cross-system migration, comprising:

[0007] Memory, used to store computer programs;

[0008] A processor, used to execute the computer program, for implementing the steps of a method for migrating the software across systems.

[0009] Fourthly, this application also provides a readable storage medium storing a computer program that, when executed by a processor, implements the steps of the above-described method for cross-system migration of software.

[0010] The beneficial effects of this invention are as follows:

[0011] This invention involves reconfiguring the resources of the initial system on the target terminal and installing the target system; mapping the data of the initial system to the target system; mounting the data of the initial system; and completing the software migration. This eliminates the need for manual intervention and significant time spent modifying the software, allowing it to quickly adapt to newly developed systems, improving work efficiency, reducing development costs, and saving development time.

[0012] Other features and advantages of the invention will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing embodiments of the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0013] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a schematic diagram of the software migration method described in an embodiment of the present invention;

[0015] Figure 2 This is a schematic diagram of the software migration device structure described in an embodiment of the present invention;

[0016] Figure 3 This is a schematic diagram of the software migration device structure described in an embodiment of the present invention.

[0017] The diagram is labeled as follows: 1. Acquisition unit; 2. Judgment unit; 3. Configuration unit; 4. Mapping unit; 5. Verification unit; 6. Data mounting unit; 21. First judgment unit; 22. Second judgment unit; 23. Third judgment unit; 31. Mirroring unit; 32. Segmentation unit; 33. Installation unit; 41. Modification unit; 42. Driver unit; 43. Cloning unit; 800. Software migration device; 801. Processor; 802. Memory; 803. Multimedia component; 804. I / O interface; 805. Communication component. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0019] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this invention, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0020] Example 1:

[0021] This embodiment provides a method for software migration across systems.

[0022] See Figure 1 The figure shows that the method includes steps S100, S200, S300, S400, S500 and S600.

[0023] S100: Obtain the hardware information of the target terminal.

[0024] It should be noted that the target terminal can be a computer and / or virtual machine configured with at least one operating system, such as Windows, Mac, Linux, Chrome OS, etc. Hardware information may include: BIOS, initial system version, memory space, and hard disk space. In this embodiment, the target terminal is configured with a Windows system as an example.

[0025] S200, based on the hardware information, determine whether the target terminal meets the migration conditions.

[0026] In this embodiment, the hardware environment of the target terminal can be automatically detected to obtain the target terminal's hardware information. A migration assessment is then performed based on this hardware information to determine whether the target terminal meets the conditions for cross-system software migration.

[0027] S300 performs initial system resource reconfiguration and installs the target system if the migration conditions are met.

[0028] It should be noted that the target system can be at least one of Windows, Mac, Linux, Chrome OS, etc. In this embodiment, Linux is used as an example.

[0029] In this embodiment, the resource configuration of the initial system can be achieved by re-allocating the remaining disk space in the initial system, making reasonable use of the system's memory and hard disk resources, and reducing the problem of excessive resource consumption caused by the operation of dual systems.

[0030] S400, restart the target terminal and enter the target system, mapping the data of the initial system to the target system.

[0031] It should be noted that after the target system is installed, you can choose to and / or automatically restart the target terminal, which will automatically enter the target system after restarting.

[0032] In this embodiment, data can be mapped to the target system by modifying the registry in the initial system and driving the relevant configuration files.

[0033] S500, during the data mapping process, the data is verified.

[0034] It should be noted that during the data mapping process, data verification is required to ensure data consistency and integrity.

[0035] In this embodiment, the mapped data file can be converted into a virtual machine template file. Further, the virtual machine template file is copied to the virtual machine image directory, imported into the virtual machine program, the virtual machine hardware is configured, and the network mode is set.

[0036] If the data verification is successful, S600 mounts the data of the initial system and completes the software migration.

[0037] Specifically, in this application, step S200 includes steps S210, S220 and S230.

[0038] S210, confirm the BIOS boot mode of the target terminal and determine whether the CPU virtualization function in the BIOS is enabled.

[0039] In this embodiment, different systems correspond to different BIOS boot methods. Taking Windows as an example, Windows 7 / 8 systems only support the legacy+MBR boot method; while Windows 10 systems support both legacy+MBR and UEFI+GPT boot methods.

[0040] Furthermore, after determining the initial system's BIOS boot method, you can enable the CPU virtualization function in the BIOS.

[0041] S220, with virtualization enabled, determine whether the initial system version supports the RDP Remote APP sub-protocol.

[0042] S230, if supported, determine whether the remaining space of the memory space and the hard disk space meets the threshold.

[0043] It should be noted that the thresholds can be set freely according to specific circumstances. For example, the threshold for memory space is no less than 8GB, and the threshold for remaining disk space is no less than 72GB.

[0044] Specifically, in this application, step S300 includes steps S310, S320 and S330.

[0045] S310, import the initial system image.

[0046] S320, Select the installation disk of the target system, divide the remaining space of the disk, and set the partition capacity of the disk.

[0047] S330, Install the target system on the disk.

[0048] Specifically, in this application, step S400 includes steps S410, S420 and S430.

[0049] S410, Modify the registry of the initial system.

[0050] In this embodiment, taking the initial system as a Windows system as an example, the registry directory is [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\; further configure the key values ​​[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi], [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde], [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]; and change the driver mode to configure the hard drive as IDE mode.

[0051] S420, drive the relevant configuration files in the initial system and copy them to the target directory.

[0052] In this embodiment, taking the initial system as a Windows system as an example, the driver-related configuration files will be... Copy the .sys file to the windows\system32\driver directory.

[0053] S430 enables maintenance tools to pre-boot the initial system and clone the initial system data to the target system.

[0054] In this embodiment, taking the initial system as a Windows system as an example, WinPE is enabled to pre-boot the Windows system and clone the operating system. During the cloning process, the data is verified to achieve data consistency, and the cloned files are converted into virtual machine template files.

[0055] Furthermore, the virtual machine template file can be copied to the virtual machine image directory, imported into the virtual machine program, the virtual machine hardware can be configured, and the network can be set to NAT mode. A virtual machine agent plugin can be installed on the Windows virtual machine, and the data disk of the domestic operating system can be mounted to the Windows virtual machine as a network shared hard drive to achieve data interoperability between the Windows system and the domestic operating system and complete the software migration.

[0056] Example 2:

[0057] like Figure 2 As shown, this embodiment provides an apparatus for software migration across systems, the apparatus comprising:

[0058] Acquisition unit 1 is used to acquire the hardware information of the target terminal.

[0059] Judgment unit 2 is used to determine whether the target terminal meets the migration conditions based on the hardware information.

[0060] Configuration unit 3 is used to perform initial system resource reconfiguration and install the target system when the migration conditions are met.

[0061] Mapping unit 4 is used to restart the target terminal and enter the target system, and to map the data of the initial system to the target system.

[0062] Verification unit 5 is used to verify the data during the data mapping process.

[0063] The data mounting unit 6 is used to mount the data of the initial system and complete the software migration when the data verification is successful.

[0064] In some specific embodiments, the hardware information includes: BIOS, initial system version, memory space, and hard disk space; the determination unit 2 includes:

[0065] The first judgment unit 21 is used to confirm the BIOS boot mode of the target terminal and determine whether the CPU virtualization function in the BIOS is enabled.

[0066] The second judgment unit 22 is used to determine whether the initial system version supports the RDP Remote APP sub-protocol when virtualization is enabled.

[0067] The third judgment unit 23 is used to determine, when supported, whether the remaining space of the memory space and the hard disk space meets the threshold.

[0068] In some specific embodiments, configuration unit 3 includes:

[0069] Image unit 31 is used to import the initial system image.

[0070] The 32 partitioning unit is used to select the installation disk of the target system, divide the remaining space of the disk, and set the partitioning capacity of the disk.

[0071] 33 Installation unit, used to install the target system on the disk.

[0072] In some specific embodiments, the mapping unit 4 includes:

[0073] Modification unit 41 is used to modify the registry of the initial system.

[0074] The driver unit 42 is used to drive the relevant configuration files in the initial system and copy them to the target directory.

[0075] Cloning unit 43 is used to enable maintenance tools to pre-boot the initial system and clone the initial system data to the target system.

[0076] It should be noted that the specific manner in which each module performs its operation in the apparatus described in the above embodiments has been described in detail in the embodiments of the method, and will not be elaborated here.

[0077] Example 3:

[0078] Corresponding to the above method embodiments, this embodiment also provides a device for cross-system software migration. The device for cross-system software migration described below and the method for cross-system software migration described above can be referred to in correspondence.

[0079] Figure 3 This is a block diagram illustrating a software migration device 800 according to an exemplary embodiment. For example... Figure 3 As shown, the software migration device 800 may include a processor 801 and a memory 802. The software migration device 800 may also include one or more of a multimedia component 803, an I / O interface 804, and a communication component 805.

[0080] The processor 801 controls the overall operation of the device 800 for cross-system software migration to complete all or part of the steps in the aforementioned method for cross-system software migration. The memory 802 stores various types of data to support the operation of the device 800 for cross-system software migration. This data may include, for example, instructions for any application or method operating on the device 800 for cross-system software migration, as well as application-related data such as contact data, sent and received messages, images, audio, video, etc. The memory 802 can be implemented using any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The multimedia component 803 may include a screen and an audio component. The screen may be, for example, a touchscreen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signals may be further stored in the memory 802 or transmitted via the communication component 805. The audio component also includes at least one speaker for outputting audio signals. I / O interface 804 provides an interface between processor 801 and other interface modules, such as keyboards, mice, and buttons. These buttons can be virtual or physical. Communication component 805 is used for wired or wireless communication between device 800 (which is migrated across systems) and other devices. Wireless communication includes Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, or 4G, or a combination thereof. Therefore, the corresponding communication component 805 may include a Wi-Fi module, a Bluetooth module, or an NFC module.

[0081] In an exemplary embodiment, the software cross-system migration device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the software cross-system migration method described above.

[0082] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the software cross-system migration method described above. For example, the computer-readable storage medium may be the memory 802 including program instructions described above, which may be executed by the processor 801 of the software cross-system migration device 800 to complete the software cross-system migration method described above.

[0083] Example 4:

[0084] Corresponding to the above method embodiments, this embodiment also provides a readable storage medium. The readable storage medium described below can be referred to in conjunction with the software cross-system migration method described above.

[0085] A readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the software cross-system migration method described in the above method embodiments.

[0086] Specifically, the readable storage medium can be a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, or any other readable storage medium capable of storing program code.

[0087] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

[0088] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for software migration across systems, characterized in that, include: The hardware information of the target terminal is obtained by automatically detecting the hardware environment of the target terminal. Based on the hardware information, determine whether the target terminal meets the migration conditions; If the migration conditions are met, perform initial system resource reconfiguration and install the target system, including: Import the initial system image; Select the installation disk of the target system, divide the remaining space of the disk, and set the partition capacity of the disk; Install the target system on the disk; Reboot the target terminal to enter the target system, and map the data from the initial system to the target system; During the data mapping process, the data is verified; If the data verification passes, the data of the initial system is mounted, and the software migration is completed. The hardware information includes: BIOS, initial system version, memory space, and hard disk space. The determination of whether the target terminal meets the migration conditions based on the hardware information includes: Confirm the BIOS boot mode of the target terminal and determine whether the CPU virtualization function in the BIOS is enabled; With virtualization enabled, determine whether the initial system version supports the RDP Remote APP sub-protocol; If supported, determine whether the remaining space in the memory space and the hard disk space meets the threshold.

2. The method for cross-system software migration according to claim 1, characterized in that... The step of mapping the data from the initial system to the target system includes: Modify the registry of the initial system; Drive the relevant configuration files in the initial system and copy them to the target directory; Enable maintenance tools to pre-boot the initial system and clone the initial system data to the target system.

3. A device for cross-system software migration, characterized in that, include: The acquisition unit is used to acquire the hardware information of the target terminal by automatically detecting the hardware environment of the target terminal; The judgment unit is used to determine whether the target terminal meets the migration conditions based on the hardware information; The configuration unit, used to perform initial system resource reconfiguration and install the target system when migration conditions are met, includes: The image unit is used to import the initial system image; The partitioning unit is used to select the installation disk of the target system, divide the remaining space of the disk, and set the partitioning capacity of the disk; An installation unit for installing the target system on the disk; The mapping unit is used to restart the target terminal and enter the target system, and to map the data of the initial system to the target system. A verification unit is used to verify the data during the data mapping process; The data mounting unit is used to mount the data of the initial system and complete the software migration when the data verification is successful. The hardware information includes: BIOS, initial system version, memory space, and hard disk space; the judgment unit includes: The first judgment unit is used to confirm the BIOS boot mode of the target terminal and determine whether the CPU virtualization function in the BIOS is enabled. The second determination unit is used to determine whether the initial system version supports the RDP Remote APP sub-protocol when virtualization is enabled. The third judgment unit is used, if supported, to determine whether the remaining space of the memory space and the hard disk space meets the threshold.

4. The apparatus for cross-system software migration according to claim 3, characterized in that, The mapping unit includes: The modification unit is used to modify the registry of the initial system; The driver unit is used to drive the relevant configuration files in the initial system and copy them to the target directory; The cloning unit is used to enable maintenance tools to pre-boot the initial system and clone the initial system data to the target system.

5. A device for cross-system software migration, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the method for cross-system software migration as described in any one of claims 1 to 2 when executing the computer program.

6. A readable storage medium, characterized in that: The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method for software cross-system migration as described in any one of claims 1 to 2.

Images