WO2021233351A1

WO2021233351A1 - Data transfer method and device, and terminal and computer-readable storage medium

Info

Publication number: WO2021233351A1
Application number: PCT/CN2021/094701
Authority: WO
Inventors: 唐宗丽
Original assignee: 中兴通讯股份有限公司
Priority date: 2020-05-19
Filing date: 2021-05-19
Publication date: 2021-11-25
Also published as: CN112817932A

Abstract

The present application provides a data transfer method and device, and a terminal and a computer-readable storage medium. The data transfer method comprises: after a dual-system starting instruction is received, detecting a system state and data validity; and under the condition that the system state and the data validity satisfy a data transfer condition, transferring data to be transferred in a root system to a target system.

Description

Data transfer method and device, terminal and computer readable storage medium

Cross-references to related applications

This application claims the priority of Chinese patent application No. 202010426148.7 filed on May 19, 2020, and the content of the Chinese patent application is incorporated herein by reference in its entirety.

Technical field

This application relates to the field of terminal technology, in particular to data transfer methods and devices, terminals, and computer-readable storage media.

Background technique

Currently, most of the terminals on the market use a single system, and the promotion and use of dual-system-based terminals (such as mobile phones) in the industry brings a brand new experience to users. The single-system version can be directly upgraded to the dual-system version through a version upgrade.

However, after upgrading from a single system to a dual system, the original single system data is placed under the root system of the dual system, and the living system and work system directly used by the user cannot directly obtain the original single system data in the root system. That is, for the user, the original single system data is lost, which brings a bad experience to the user.

In order to solve the above problems and give users a better upgrade experience, it is necessary to save the original single system data to the system directly used by the user in the dual system. At present, the commonly used method is to use the backup and recovery function to back up the single system data before the system upgrade, and then perform the recovery operation in the system directly used by the user after the upgrade.

Both backup and restoration in the above scheme require additional operations by the user, and are time-consuming, the single-system data that can be restored is also very limited, and additional space for storing the backup data is required.

Public content

In the first aspect, an embodiment of the present application provides a data transfer method, including:

After receiving the dual system start command, check the system status and data validity;

When the system status and data validity meet the data transfer conditions, the data to be transferred in the root system is transferred to the target system.

In a second aspect, an embodiment of the present application provides a data transfer device, including:

The detection module is configured to detect the system status and data validity after receiving the dual-system start instruction;

The transfer module is configured to transfer the data to be transferred in the root system to the target system when the system status and data validity meet the data transfer conditions.

In a third aspect, an embodiment of the present application provides a terminal, and the terminal includes:

One or more processors;

Memory, configured to store one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the data transfer method in the embodiment of the present application.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium that stores a computer program that implements the data transfer method in the embodiment of the present application when the computer program is executed by a processor.

Regarding the above embodiments and other aspects of the application and their implementation manners, more descriptions are provided in the description of the drawings, the specific implementation manners, and the claims.

Description of the drawings

Figure 1 is a schematic flowchart of a data transfer method provided by this application;

Figure 2 is a schematic diagram of the single system upgrade dual system and user data transfer process provided by the application;

Figure 3 is a flow chart of the single system upgrade dual system provided by this application;

Fig. 4 is a flowchart of the method for judging whether the data transfer condition is satisfied provided by the present application;

Figure 5 is a schematic structural diagram of a data transfer device provided by this application; and

Fig. 6 is a schematic structural diagram of a terminal provided by the present application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present application clearer, the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. It should be noted that the embodiments in the application and the features in the embodiments can be combined with each other arbitrarily if there is no conflict.

The steps shown in the flowcharts of the drawings may be executed in a computer system such as a set of computer-executable instructions. And, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than here.

First, in this application, the dual system is briefly explained.

With the continuous enrichment of smart terminal functions, smart terminals play an indispensable role in people's daily life, and involve a lot of sensitive information and data, including personal privacy, payment security, etc. Therefore, in order to meet the requirements of security and other aspects, a terminal (such as a mobile phone) with a dual-system architecture has emerged as the times require.

A smart terminal has two systems visible to the user at the same time. Work and life are independent of each other. The system currently displayed on the terminal screen is the foreground system, and the other is the background system. The background system is also running and can receive messages. In addition, users can easily switch between the two systems, which not only meets the needs of users' lives and work without interfering with each other, but also is convenient and quick to use.

At present, dual-system terminals use container technology, share a core, and support the operation of two systems through lightweight virtualization technology. The living system and working system are isolated at the operating system layer, and the root file systems, processes and networks of the two systems Complete isolation. The dual-system terminal architecture is composed of three systems, a root system, a working system, and a living system. When the terminal starts, it first starts the root system, and then the root system prepares its own file systems for the working system and the living system. Finally, the root system starts the working system and the living system through container technology, and the root system is responsible for overall management and control system switching , Coordinate the work system and the life system to work together.

The location of the data area of the root system in the dual system is actually the same as the location of the data area of the single system, while the data areas of the living system and the working system are created for them by the root system, and both have their own storage locations. Therefore, if it is necessary to keep the single system data to the living system, it is to transfer the user data under the single system data area to the living system data area. Similarly, if it is necessary to retain single-system user data to the working system, transfer the user data under the single-system data area to the working system data area.

After a single system is upgraded to a dual system, the data of the single system is actually in the data area of the dual system root system. Therefore, in order to retain the data of the single system to the target system after the upgrade, it is actually to transfer user data in the data area of the dual system root system To the data area of the target system.

In one embodiment, this application provides a data transfer method, and FIG. 1 is a schematic flowchart of a data transfer method provided in this application. This method can be applied to the situation that the data of the single system is transferred to the system used by the user in the dual system in the process of upgrading the dual system of the single system. This method is executed by the data transfer device provided in this application, and the above data transfer device can be implemented by software and/or hardware.

In this embodiment, the data transfer method is applied to a terminal, which can be a mobile smart phone with an operating system, a tablet computer with an operating system, a wearable device with an operating system, and a smart electrical appliance with an operating system. In this embodiment, a mobile smart phone with an operating system is taken as an example for description.

It should be noted that this application is not only applicable to a single system upgrade dual Android system architecture, but also applicable to scenarios such as a single system upgrade multiple Android system architecture, or a heterogeneous dual system architecture upgrade. As long as the upgraded system includes an Android system, the solution of this application can be used to retain the user data of the previous single Android system in one of the Android subsystems during the upgrade process.

As shown in FIG. 1, the data transfer method provided by the embodiment of the present application mainly includes steps S10 and S20.

S10. After receiving the dual system start instruction, check the system status and data validity.

S20: When the system status and data validity meet the data transfer conditions, transfer the data to be transferred in the root system to the target system.

In this embodiment, the system may be an Android system, an IOS system, or other terminal operating systems, which is not limited in this embodiment. It should be noted that, in this embodiment, an Android system is taken as an example for description, that is, a single Android system is upgraded to a dual Android system as an example for description.

The dual-system startup instruction can be understood as an instruction that instructs the operating system in the terminal to start. Receipt of the dual system start instruction can be understood as receiving an instruction to instruct the operating system in the terminal to start.

Further, the dual-system startup instruction may be received after the single-system is upgraded to the dual-system, and the dual-system startup instruction is automatically received after the completion of the system upgrade is detected. Receipt of the dual-system start instruction may also be the detection that the user triggers the dual-system start button, and then the dual-system start instruction is received. The dual-system startup button can be a startup button set by the terminal, and the dual-system startup button can also be a restart button set by the terminal. It should be noted that, in this embodiment, only the receiving of the dual-system start instruction is described, but not limited.

The data to be transferred can be understood as the data transferred to the data area under the root system of the dual system after the single system data is upgraded, and it is the user data generated in the process of using the single system by the terminal. For example: the data to be transferred includes but is not limited to system application data (setting information of the application, text messages, mobile phone contacts, call records, alarm settings, etc.), installed third-party applications and data, and content in the built-in SD card (including shooting Pictures, videos, etc.), special information (such as lock screen password), etc.

The target system can be any system used by the user in the dual system, that is, it can be a working system or a living system.

In this embodiment, before detecting the system status and data validity, it also includes: after the single system data is upgraded, it is first transferred to the data area under the root system of the dual system, and transferred to the single system data in the data partition under the root system. This is the data to be transferred as described in this implementation.

In an exemplary implementation, the transferring the data to be transferred in the root system to the target system includes:

The data to be transferred in the root system is transferred to the target system in a mobile mode.

In this embodiment, the data transfer method adopts a mobile method to perform data transfer operations, which is faster than copying and reduces storage space occupation.

In an exemplary embodiment, the transferring user data in the root system to a data area of the target system includes: transferring a designated directory containing user data in the root system to a data area directory of the target system.

The specified directory containing the data to be transferred in the root system is transferred to the target system.

In an exemplary embodiment, the designated directory includes one or more of the following:

Directory encrypted with user device encryption key;

Directory encrypted with user credential encryption key;

The directory where the global encryption key is used to encrypt and store the data to be transferred; and

The directory of unencrypted user data to be transferred.

In this embodiment, file-based encryption (FBE) is briefly introduced for the first time:

At present, the Android data partition adopts the FBE method, which can use different keys to encrypt different files, and can decrypt these files separately. File-level encryption is supported in Android 7.0 and higher.

In this embodiment, the designated directory containing the data to be transferred is a subdirectory of the data partition. Since the designated directory is a partition directory that uses file-level encryption, it is necessary to consider the impact of file-level encryption to ensure that the data can still be encrypted and decrypted normally after the data is transferred.

On a device with file-level encryption enabled, each user has two storage locations available for applications:

Credential Encryption (CE) storage space, which is the default storage location and is only available after the user unlocks the device; and

Device Encryption (DE) storage space is available during direct boot mode and after the user unlocks the device.

This distinction between storage locations can make work data more secure, and encryption is no longer only based on the activation password, so that multiple users can be protected at the same time.

For example, there are the following three types of keys in the Android system.

The first type is the global device encryption key. The key is placed in /data/unencryptd. In the implementation of the dual system, the three systems use a set of keys, and the key stored under the root system is used. Since the root system needs to access the directory encrypted with the key under the working system and the living system before the working system and the living system are started, such as /data/app, /data/misc, etc., the key is designed to be three The system is unified, and the key is installed and decrypted when the root system is started.

The second type is the user equipment encryption key. Take user 0 as an example. The key is placed in /data/misc/vold/user_keys/de/0. In the dual system, the three systems are independent, and each user creates and uses its own Key, the directories encrypted with the key are: /data/system_de/0, /data/misc_de/0, /data/user_de/0, etc. The key is installed and decrypted when each system starts.

The third type is the user credential encryption key. Taking user 0 as an example, the key is placed in /data/misc/vold/user_keys/ce/0. In the dual system, the three systems are independent, and each user creates and uses its own Key, the directories encrypted with the key are: /data/system_ce/0, /data/misc_ce/0, etc. The difference between this type of key and the previous two keys is that if the lock screen password is not set, the key installation and decryption will be performed when the system is started. If the lock screen password is set, the system needs to wait for the user to enter the lock screen. The key is installed and decrypted after the password. The key is actually encrypted and saved with the lock screen password. Therefore, when the user does not enter the lock screen password, the corresponding encrypted directory will not be available.

The global device key is installed and decrypted by the root system in the dual system, so its storage directory needs to be kept under the root system. The directory path is /data/unencryptd.

Since there is no Android system framework and application under the root system, the user-related directory is actually not needed, and this part contains user data, so the user device encryption key and user credential encryption key storage directory and encrypted directory are required Move to the target system.

In addition, directories encrypted with the global device encryption key and non-encrypted directories need to be moved to the target system if user data is stored.

Therefore, the directories that need to be moved include but are not limited to:

/data/misc/data/misc_ce/data/misc_de/data/system/data/system_ce/data/system_de/data/vendor/data/vendor_ce/data/vendor_de/data/data/data/user/data/user_de/data /media/data/apex data/app* (that is, all directories at the beginning of app).

It should be noted that the directory may change with the upgrade of the overall Android version or changes in requirements. For example, a new function needs to create a new directory under the data partition, and the data of this function needs to be upgraded and retained, and the directory needs to be added. Move, but the basic principle of confirming whether the directory needs to be moved remains the same.

Directory selection principle: The storage directory of user equipment encryption key and user credential encryption key, and the directory encrypted with these two types of keys need to be moved to the target system. The global device encryption key storage directory must be kept in the root system. The directories and non-encrypted directories encrypted with the global device encryption key need to be moved to the target system if user data is stored. Other directories do not need to be moved, such as the log directory can be kept in the root system.

In an exemplary implementation, the system status and data validity satisfying data transfer conditions include:

The dual system is started for the first time;

The first configuration of the target system; and

The data to be transferred is valid.

In this embodiment, when the dual system is started for the first time, the target system is configured for the first time, and the data to be transferred is valid, it is determined that the system state and data validity meet the data transfer conditions.

Further, in this embodiment, it is first judged whether the dual system is started for the first time. If the dual system is started for the first time, it is judged whether the target system is configured for the first time. The subsequent process of system startup. If the target system is configured for the first time, it is determined whether the data to be transferred is valid. If the target system is not configured for the first time, it is determined that the system status does not meet the data transfer conditions, and the subsequent process of dual system startup is executed. If the data to be transferred is valid, it is determined that the system status and data validity meet the data transfer conditions. If the data to be transferred is invalid, it is determined that the validity of the data does not meet the data transfer conditions, and the subsequent process of dual system startup is executed.

Further, in this embodiment, the time to transfer data is selected after the upgrade operation is completed. When the dual system is started for the first time, the data partition is loaded successfully and the global device encryption key is installed. Before creating each subdirectory for the data partition, run The transfer operation is performed in a script.

Moving the directory is before the process of creating each subdirectory for the data partition, it can ensure that after the directory is moved, the missing directories in the root system will be automatically created again in the subsequent process to ensure the stability of the subsequent operation of the system.

In an exemplary embodiment, the determination of the first startup of the dual system includes:

After detecting the first boot logo, confirm that the dual system is booted for the first time;

Wherein, the first startup identifier includes one or more of the following: a directory created for the first startup of the dual system, a file created for the first startup of the dual system, and an attribute identifier set for the first startup of the dual system.

The first startup logo refers to a unique logo after the dual system is started.

In this implementation, the unique mark after dual system startup is judged. If it does not exist, the dual system is started for the first time, and subsequent judgments are continued. If the unique mark exists, it means that the dual system has been started and no moving operation is performed.

The unique mark can be a special directory or file created after the dual system is started, or it can be a special attribute set after the dual system is started, but it is not limited to these forms, as long as it can be identified as a sign that the dual system has started. Can.

After detecting the preset identification position, confirm that the dual system starts for the first time;

Wherein, the preset identification bit is set when the system upgrade module recognizes that the system to be upgraded is a dual system.

In this embodiment, when the single system recognizes that the version to be upgraded is a dual system during the upgrade, a flag bit is set. If the flag bit is read after the dual system is started, it means that the single system is upgraded and the dual system is started for the first time. Data movement operation can be performed. After the movement is completed, the flag bit is cleared. When the dual system is started next time, it will know that it is not the first time and no movement operation will be performed. Compared with the optimal solution, this alternative solution requires more modules to be modified, but it can also achieve judgment.

In an exemplary implementation, the determination of the first configuration of the target system includes:

When it is detected that the data to be transferred is not stored in the data area of the target system, it is determined that the target system is configured for the first time.

In an exemplary embodiment, the data to be transferred effectively includes:

The specified directory containing the data to be transferred exists and is valid in the root system.

In this embodiment, it is judged whether each subdirectory under the data partition exists and is valid. The existence and validity indicate that the data partition already has data when the dual system is started for the first time. These data must be generated by the single system before the upgrade, and you can confirm This is the first time the dual system starts after the single system is upgraded to the dual system, and data needs to be transferred. Otherwise, it means that the dual system is the first time to burn the version, or the whole machine is restored to factory settings, etc., these scenarios do not require data transfer operations

The technical solution provided in this embodiment is completed in the process of upgrading a single system to a dual system. When the dual system is started for the first time, the data under the root system is transferred to the data area of the target system to realize the retention of the single system data to the target system. When transferring, you need to make relevant judgments first, such as whether it is a single system upgrade to a dual system, whether user data is valid, etc., so that the terminal can upgrade from a single system version to the corresponding dual system version while retaining the user's data to the target In the system, it is easy to operate and does not increase the length of the upgrade process. With the upgrade process, it is automatically completed when the user is insensible. The retained user data is also complete. It does not rely on additional storage devices and networks, and the user experience is very good.

In an applicable implementation manner, a single-system upgrade dual-system user data transfer process is provided. Figure 2 is a structural schematic diagram of the single-system upgrade dual-system user data transfer process provided by the application. As shown in Figure 2, a single-system user After the data is upgraded, it is first transferred to the data partition under the dual-system root system, and then after the data transfer scheme provided by this application, part of the data is transferred from the root system to the data area of the target system to realize the single-system user data after the upgrade. Keep it under the target system of the dual system.

It should be noted that the other system is a system other than the target system and the root system under the dual system, and the data in the target system is the data after the transfer of the data to be transferred in the root system.

In an applicable implementation manner, a process for upgrading a single system to a dual system is provided. FIG. 3 is a flowchart of the single system upgrading dual system provided by this application. As shown in FIG. 3, the single system upgrading dual system provided by this application The flow of the system mainly includes steps S31, S32, S33, and S34.

S31. The single-system upgrade module detects the dual-system upgrade package and performs an upgrade operation.

S32. The upgrade module restarts the terminal.

S33. The dual system is started. After the data partition of the root system is successfully loaded and the global device encryption key is installed, the data check and movement process is performed before the subdirectory is created. The process will perform a series of judgment checks. When the checks pass, data movement operations will be performed; otherwise, S34 will be executed directly.

S34. The dual system continues the follow-up process, including creating missing subdirectories under the data partition, and starting the work and life systems.

In an applicable implementation manner, a method for judging whether the data transfer condition is met is provided. FIG. 4 is a flowchart of the method provided by this application for judging whether the data transfer condition is met. As shown in FIG. 4, the method provided by this application The process of the method for determining whether the data transfer condition is met mainly includes steps S41, S42, S43, and S44.

S41. Determine whether it is the first startup of the dual system, that is, determine whether the unique mark after the dual system is started (such as the unique directory that will be created after the dual system is started, the unique attribute set, etc.), if the unique mark exists after the dual system is started, Note that it is not the first startup of the dual system, then execute S45, if it is the first startup, execute S42.

S42. Determine whether the target system is created for the first time, that is, whether there is a data directory in the data area of the target system. If there is a data directory in the data area of the target system, it means that the target system already has data and the data transfer operation cannot be performed, then execute S45, if If it is the first time to create, go to S43.

S43. Determine whether the subdirectory to be moved under the data partition is valid, such as whether the user device encryption key and user credential encryption key storage directory exists, whether the directory to be moved exists, etc., if the directory does not exist or is invalid, execute S45 . If the directories are all valid, it means that the data to be restored in these single systems is valid, the check is passed, and S44 is executed.

S44. Perform the data transfer operation, and the directory path to be moved is configured in advance.

S45. The dual system continues the follow-up process and starts the working system and the living system.

In one embodiment, this application provides a data transfer device, and FIG. 5 is a schematic structural diagram of a data transfer device provided in this application. The device can be suitable for the situation that the data of the single system is transferred to the system used by the user in the dual system in the process of upgrading the single system to the dual system. The data transfer device can be implemented by software and/or hardware.

As shown in FIG. 5, the data transfer device provided by the embodiment of the present application mainly includes a detection module 51 and a transfer module 52.

The detection module 51 is configured to detect the system status and data validity after receiving the dual system start instruction.

The transfer module 52 is configured to transfer the data to be transferred in the root system to the target system when the system status and data validity meet the data transfer conditions.

Directory encrypted with user device encryption key;

Directory encrypted with user credential encryption key;

The directory of unencrypted user data to be transferred.

The dual system is started for the first time;

The first configuration of the target system; and

The data to be transferred is valid.

In an exemplary embodiment, the data to be transferred effectively includes:

The data transfer device provided in this embodiment can execute the data transfer method provided in any embodiment of the present disclosure, and has the corresponding functional modules and beneficial effects for executing the method. For technical details that are not described in detail in this embodiment, please refer to the data transfer method provided in any embodiment of the present disclosure.

It is worth noting that, in the embodiment of the data transfer device, the units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, each The specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the present application.

An embodiment of the present application also provides a terminal. FIG. 6 is a schematic structural diagram of a terminal provided by the present application. As shown in FIG. 6, the terminal includes a processor 61, a memory 62, an input device 63, and an output device 64; The number of processors 61 can be one or more. In Figure 6, one processor 61 is taken as an example; the processor 61, the memory 62, the input device 63 and the output device 64 in the terminal can be connected by a bus or other means. Take the bus connection as an example in 6.

As a computer-readable storage medium, the memory 62 can be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the data transfer method in the embodiment of the present application (for example, the detection module in the data transfer device). 51 and transfer module 52). The processor 61 executes various functional applications and data processing of the terminal by running software programs, instructions, and modules stored in the memory 62, that is, implements any method provided in the embodiments of the present application.

The memory 62 may mainly include a program storage area and a data storage area. The program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the terminal, and the like. In addition, the memory 62 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some examples, the memory 62 may further include a memory remotely provided with respect to the processor 61, and these remote memories may be connected to the terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

The input device 63 can be used to receive inputted digital or character information, and generate key signal input related to user settings and function control of the terminal. The output device 64 may include a display device such as a display screen.

An embodiment of the present application also provides a computer-readable storage medium containing computer-executable instructions that, when executed by a computer processor, perform a data transfer method, and the data transfer method includes:

After receiving the dual system start command, check the system status and data validity; and

Of course, for the computer-readable storage medium containing computer-executable instructions provided by the embodiments of the present application, the computer-executable instructions are not limited to performing the operations described above, and can also perform the data transfer method provided by any embodiment of the present application Related operations in.

Through the above description of the implementation manners, those skilled in the art can clearly understand that this application can be implemented by software and general hardware, of course, it can also be implemented by hardware, but in many cases the former is a better implementation. Based on this understanding, the technical solution of this application essentially or the part that contributes to the related technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, Read-Only Memory (ROM), Random Access Memory (RAM), Flash memory (FLASH), hard disk or optical disk, etc., including several instructions to make a computer device (which can be a personal computer, A server, or a network device, etc.) execute the method described in each embodiment of the present application.

The foregoing descriptions are only exemplary embodiments of the present application, and are not used to limit the protection scope of the present application.

Those skilled in the art should understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

In general, the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

The embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code written in any combination of one or more programming languages or Object code.

The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function optical discs) DVD or CD) etc. Computer-readable media may include non-transitory storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), programmable logic devices (FGPA) And processors based on multi-core processor architecture.

By way of exemplary and non-limiting examples, a detailed description of the exemplary embodiments of the present application has been provided above. However, considering the accompanying drawings and claims, various modifications and adjustments to the above embodiments are obvious to those skilled in the art, but they do not deviate from the scope of the present disclosure. Therefore, the proper scope of the present disclosure will be determined according to the claims.

Claims

A method of data transfer including:

After receiving the dual system start command, check the system status and data validity;

When the system status and data validity meet the data transfer conditions, the data to be transferred in the root system is transferred to the target system.
The method according to claim 1, wherein the transferring the data to be transferred in the root system to the target system comprises:

The data to be transferred in the root system is transferred to the target system in a mobile mode.
The method according to claim 1 or 2, wherein the transferring the data to be transferred in the root system to the target system comprises:

The specified directory containing the data to be transferred in the root system is transferred to the target system.
The method according to claim 3, wherein the designated directory includes one or more of the following:

Directory encrypted with user device encryption key;

Directory encrypted with user credential encryption key;

The directory where the global encryption key is used to encrypt and store the data to be transferred; and

The directory of unencrypted user data to be transferred.
The method according to claim 1, wherein the system status and data validity satisfying data transfer conditions comprises:

The dual system is started for the first time;

The first configuration of the target system; and

The data to be transferred is valid.
The method according to claim 5, wherein the determination of the first startup of the dual system comprises:

After detecting the first boot logo, confirm that the dual system is booted for the first time;

Wherein, the first startup identifier includes one or more of the following: a directory created for the first startup of the dual system, a file created for the first startup of the dual system, and an attribute identifier set for the first startup of the dual system.
The method according to claim 5, wherein the determination of the first startup of the dual system comprises:

After detecting the preset identification position, confirm that the dual system starts for the first time;

Wherein, the preset identification bit is set when the system upgrade module recognizes that the system to be upgraded is a dual system.
The method according to claim 5, wherein the determination of the first configuration of the target system comprises:

When it is detected that the data to be transferred is not stored in the data area of the target system, it is determined that the target system is configured for the first time.
The method according to claim 5, wherein the data to be transferred effectively comprises:

The specified directory containing the data to be transferred exists and is valid in the root system.
A data transfer device includes:

The detection module is configured to detect the system status and data validity after receiving the dual system start instruction; and

The transfer module is configured to transfer the data to be transferred in the root system to the target system when the system status and data validity meet the data transfer conditions.
A terminal, including:

One or more processors;

Memory, configured to store one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method according to any one of claims 1-9.
A computer-readable storage medium with a computer program stored thereon, and when the computer program is executed by a processor, the method according to any one of claims 1-9 is realized.