[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN115080505A - Data migration method, terminal, storage medium, and program product - Google Patents

Data migration method, terminal, storage medium, and program product Download PDF

Info

Publication number
CN115080505A
CN115080505A CN202111048320.0A CN202111048320A CN115080505A CN 115080505 A CN115080505 A CN 115080505A CN 202111048320 A CN202111048320 A CN 202111048320A CN 115080505 A CN115080505 A CN 115080505A
Authority
CN
China
Prior art keywords
file
migrated
terminal
target path
path
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202111048320.0A
Other languages
Chinese (zh)
Other versions
CN115080505B (en
Inventor
毛成琨
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honor Device Co Ltd
Original Assignee
Honor Device Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Honor Device Co Ltd filed Critical Honor Device Co Ltd
Priority to CN202111048320.0A priority Critical patent/CN115080505B/en
Publication of CN115080505A publication Critical patent/CN115080505A/en
Application granted granted Critical
Publication of CN115080505B publication Critical patent/CN115080505B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/11File system administration, e.g. details of archiving or snapshots
    • G06F16/119Details of migration of file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/13File access structures, e.g. distributed indices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/168Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

An embodiment of the application provides a data migration method, a terminal, a storage medium and a program product, wherein the method comprises the following steps: receiving a target path sent by a second terminal, wherein the target path indicates a final storage position of a file to be migrated in the second terminal; generating a file path mapping relation according to the target path and the information of the file to be migrated, wherein the file path mapping relation comprises a corresponding relation between the target path and the information of the file to be migrated; and sending migration data to the second terminal, wherein the data structure of the migration data comprises a destination address field and a user data field, the user data field is used for bearing the file to be migrated, and the destination address field is used for bearing a target path corresponding to the file to be migrated. In the embodiment of the application, when the first terminal sends the migration data to the second terminal, the destination address of the migration data can be dynamically adjusted, so that the file to be migrated is directly stored in the corresponding destination address, secondary write-in operation in the second terminal is avoided, and system overhead is saved.

Description

Data migration method, terminal, storage medium, and program product
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data migration method, a terminal, a storage medium, and a program product.
Background
With the development of terminal technology, the updating speed of terminals such as mobile phones and tablet computers is faster and faster. In the process of replacing the terminal, a user does not want all data on the old terminal to disappear along with the replacement of the terminal, and wants to want part or all of the data originally stored on the old terminal to be continuously and normally used on the new terminal, so that a plurality of terminal suppliers and application markets provide related functions such as data backup, data migration and the like, that is, the user can copy the data, software, setting and the like on the old terminal to the new terminal without any change, and convenience is provided for the user in the process of replacing the terminal.
In the related art, a data migration scheme is to store a file to be migrated on an old terminal in a temporary folder on a new terminal, and then move the file to be migrated in the temporary folder to a corresponding target path.
However, according to the scheme, the file to be migrated needs to be written twice, so that the data migration speed is reduced, and the system overhead is increased.
Disclosure of Invention
In view of this, the present application provides a data migration method, a terminal, a storage medium, and a program product, so as to solve the problem that in the prior art, two write operations need to be performed on a file to be migrated, thereby increasing the system overhead.
In a first aspect, an embodiment of the present application provides a data migration method, which is applied to a first terminal, and the method includes:
receiving a target path sent by a second terminal, wherein the target path indicates a final storage position of a file to be migrated in the second terminal;
generating a file path mapping relation according to the target path and the information of the file to be migrated, wherein the file path mapping relation comprises a corresponding relation between the target path and the information of the file to be migrated, and the information of the file to be migrated corresponds to the file to be migrated;
and sending migration data to the second terminal, wherein a data structure of the migration data comprises a destination address field and a user data field, the user data field is used for bearing the file to be migrated, and the destination address field is used for bearing a target path corresponding to the file to be migrated.
Preferably, the receiving the target path sent by the second terminal includes: receiving M target paths sent by a second terminal, wherein the M target paths are the final storage positions of N files to be migrated in the second terminal, M is more than or equal to 2, and N is more than or equal to 2;
generating a file path mapping relation according to the target path and the information of the file to be migrated, wherein the file path mapping relation comprises: generating a file path mapping relation according to the M target paths and the N pieces of information of the files to be migrated, wherein the file path mapping relation comprises the corresponding relation between the M target paths and the N pieces of information of the files to be migrated;
the sending migration data to the second terminal includes: and sending migration data corresponding to each file to be migrated to the second terminal.
Preferably, before the receiving the target path sent by the second terminal, the method further includes:
sending the description information of the file to be migrated to the second terminal,
the file description information to be migrated comprises size information, type information and/or source path information of the file to be migrated.
Preferably, the target path is allocated according to size information, type information and/or source path information of the file to be migrated.
Preferably, the method further comprises the following steps:
packaging two or more files to be migrated, wherein the two or more files to be migrated are smaller than or equal to a preset size threshold value, and generating file packages corresponding to the two or more files to be migrated;
the sending migration data to the second terminal includes: and sending migration data corresponding to the file packet to the second terminal, wherein a user data field of the migration data is used for bearing the file packet, and a destination address field of the migration data is used for bearing a temporary path corresponding to the file packet.
Preferably, the file to be migrated includes application data corresponding to an application program file, and the target path includes a target path corresponding to the application data;
before the receiving the target path sent by the second terminal, the method further includes:
and sending migration data corresponding to the application program file to the second terminal, wherein a user data field of the migration data is used for bearing the application program file, and a destination address field of the migration data is used for bearing a target path or a temporary path corresponding to the application program file.
In a second aspect, an embodiment of the present application provides a data migration method, which is applied to a second terminal, and the method includes:
sending a target path to a first terminal, wherein the target path is a final storage position of a file to be migrated in a second terminal;
receiving migration data sent by the first terminal, wherein a data structure of the migration data comprises a destination address field and a user data field, the user data field is used for bearing the file to be migrated, and the destination address field is used for bearing a target path corresponding to the file to be migrated;
and storing the file to be migrated in a target path corresponding to the file to be migrated.
Preferably, the sending the target path to the first terminal includes: sending M target paths to a first terminal, wherein the M target paths are final storage paths of N files to be migrated in a second terminal, M is more than or equal to 2, and N is more than or equal to 2;
the receiving migration data sent by the first terminal includes: receiving migration data corresponding to each file to be migrated, which is sent by the first terminal;
the storing the file to be migrated in the target path corresponding to the file to be migrated includes: and storing each file to be migrated in a target path corresponding to each file to be migrated.
Preferably, before the sending the target path to the first terminal, the method further includes:
receiving description information of a file to be migrated, which is sent by the first terminal, wherein the description information of the file to be migrated comprises size information, type information and/or source path information of the file to be migrated;
and determining a target path corresponding to the file to be migrated according to the description information of the file to be migrated.
Preferably, the determining, according to the description information of the file to be migrated, a target path corresponding to the file to be migrated includes:
when the description information of the file to be migrated comprises size information of the file to be migrated, allocating a target path for the file to be migrated according to the size information, wherein a storage space corresponding to the target path is larger than or equal to the size of the file to be migrated;
when the description information of the file to be migrated comprises the type information of the file to be migrated, allocating a target path matched with the type information for the file to be migrated;
and when the description information of the file to be migrated comprises a source path of the file to be migrated, allocating a target path which is the same as the source path to the file to be migrated.
Preferably, the method further comprises the following steps:
receiving migration data which is sent by the first terminal and corresponds to a file packet, wherein a user data field of the migration data is used for bearing the file packet, and a destination address field of the migration data is used for bearing a temporary path corresponding to the file packet;
storing the file package in a temporary path corresponding to the file package;
the file package comprises two or more files to be migrated, wherein the two or more files to be migrated are smaller than or equal to a preset size threshold.
Preferably, the file to be migrated includes application data corresponding to an application program file, and the target path includes a target path corresponding to the application data;
before the sending the target path to the first terminal, the method further includes:
receiving migration data which is sent by the second terminal and corresponds to the application program file, wherein a user data field of the migration data is used for bearing the application program file, and a destination address field of the migration data is used for bearing a target path or a temporary path corresponding to the application program file;
installing the application program file;
and determining a target path corresponding to the application data according to the installation directory of the application program file.
In a third aspect, an embodiment of the present application provides a first terminal, including:
one or more processors;
a memory;
and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions which, when executed by the first terminal, cause the first terminal to perform the method of any of the first aspects.
In a fourth aspect, an embodiment of the present application provides a second terminal, including:
one or more processors;
a memory;
and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions which, when executed by the second terminal, cause the second terminal to perform the method of any of the second aspects.
In a fifth aspect, the present application provides a computer-readable storage medium, where the computer-readable storage medium includes a stored program, where the program, when executed, controls an apparatus in which the computer-readable storage medium is located to perform the method of any one of the first aspects.
In a sixth aspect, the present application provides a computer-readable storage medium, where the computer-readable storage medium includes a stored program, where the program, when executed, controls an apparatus in which the computer-readable storage medium is located to perform the method of any one of the second aspects.
In a seventh aspect, the present application provides a computer program product, where the computer program product contains executable instructions, and when the executable instructions are executed on a computer, the computer is caused to execute the method of any one of the first aspect.
In an eighth aspect, the present application provides a computer program product, which contains executable instructions that, when executed on a computer, cause the computer to perform the method of any one of the second aspects.
In the embodiment of the application, when the first terminal sends the migration data to the second terminal, the destination address of the migration data can be dynamically adjusted, so that the file to be migrated is directly stored in the corresponding destination address, secondary write-in operation in the second terminal is avoided, and system overhead is saved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;
FIG. 2 is a diagram illustrating a data migration scheme according to the related art;
fig. 3 is a schematic flow chart of a data migration method according to an embodiment of the present application;
fig. 4 is a schematic diagram of a file path mapping relationship provided in an embodiment of the present application;
fig. 5 is a schematic diagram of another file path mapping relationship provided in the embodiment of the present application;
fig. 6 is a schematic data structure diagram of migration data according to an embodiment of the present application;
fig. 7 is a schematic diagram of a data migration scenario provided in an embodiment of the present application;
fig. 8 is a schematic flow chart of another data migration method according to an embodiment of the present application;
fig. 9 is a schematic flow chart of another data migration method according to an embodiment of the present application;
FIG. 10 is a schematic flow chart diagram illustrating another data migration method according to an embodiment of the present application;
fig. 11 is a block diagram of a software structure of an electronic device according to an embodiment of the present application;
fig. 12 is a schematic flow chart of another data migration method according to an embodiment of the present application;
FIG. 13 is a schematic view of a document selection and reception interface provided in an embodiment of the present application;
fig. 14 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
For better understanding of the technical solutions of the present application, the following detailed descriptions of the embodiments of the present application are provided with reference to the accompanying drawings.
It should be understood that the embodiments described are only a few embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be understood that the term "and/or" as used herein is merely one type of associative relationship that describes an associated object, meaning that three types of relationships may exist, e.g., A and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Referring to fig. 1, a schematic view of an application scenario provided in the embodiment of the present application is shown. In fig. 1, two terminal devices, a new handset and an old handset, are shown. The old mobile phone can be understood as a mobile phone used by the user in daily life, and the new mobile phone can be understood as a mobile phone newly purchased by the user. The old mobile phone stores more user data, and the user needs to transfer all or part of the user data in the old mobile phone to the new mobile phone, so that the user can use the new mobile phone conveniently, namely, the old mobile phone performs data transfer to the new mobile phone.
It should be noted that fig. 1 illustrates a terminal according to an embodiment of the present application by taking a mobile phone as an example, and should not be taken as a limitation of the scope of the present application. In addition to the mobile phone, the terminal may also be a tablet computer, a Personal Computer (PC), a Personal Digital Assistant (PDA), a smart watch, a netbook, a wearable electronic device, an Augmented Reality (AR) device, a Virtual Reality (VR) device, an in-vehicle device, a smart car, a smart audio, a robot, smart glasses, a smart television, or the like.
In addition, the new and old devices performing data migration may be the same type of terminal device, and may also be different types of terminal devices, which is not specifically limited in this embodiment of the present application.
Referring to fig. 2, a schematic diagram of a data migration scheme in the related art is shown. Fig. 2 shows two terminal devices, namely a new mobile phone and an old mobile phone, where a user needs to migrate a file to be migrated in the old mobile phone to the new mobile phone. Firstly, files to be migrated on the old mobile phone are stored in a temporary folder on the new mobile phone, and then the files to be migrated in the temporary folder are moved to a corresponding target path, so that data migration is realized. The temporary folder is a temporary storage position of the file to be migrated in the new mobile phone, and the target path is a final storage position of the file to be migrated in the new mobile phone. Different files to be migrated may have different target paths, for example, the target paths corresponding to the video file, the document file, and the picture file are different.
However, in the data migration scheme shown in fig. 2, two write operations are required to be performed on the file to be migrated. Specifically, a write-in operation is performed in the process of storing the file to be migrated in the temporary folder; and carrying out write-in operation once in the process of moving the file to be migrated from the temporary folder to the target path. This process may increase system overhead, such as occupying more data processing resources, outputting storage resources, and extending data migration time.
Based on the problem, embodiments of the present application provide a data migration method, a terminal, a storage medium, and a program product, so as to facilitate solving the problem that in the prior art, two write operations need to be performed on a file to be migrated, and thus system overhead is increased.
Referring to fig. 3, a schematic flow chart of a data migration method according to an embodiment of the present application is provided. The method can be applied to the application scenario shown in fig. 1. The first terminal can be understood as an old mobile phone, i.e., a data migration end or a data export end, and the second terminal can be understood as a new mobile phone, i.e., a data migration end or a data import end. As shown in fig. 3, it mainly includes the following steps.
Step S301: the second terminal sends the target path to the first terminal.
In the embodiment of the application, after the first terminal serving as the data migration end and the second terminal serving as the data migration end establish a communication connection, the second terminal sends the target path to the first terminal, that is, notifies the first terminal of the storage location of the file to be migrated. It can be understood that the target path is a final storage location of the file to be migrated in the second terminal. The target path may be allocated by the second terminal after receiving the file description information to be migrated of the first terminal, or may be a plurality of target paths specified in advance by the second terminal system.
The files to be migrated in different types, sizes or source paths may have different target paths, for example, the target paths corresponding to different types of files, such as video files, document files and picture files, are different. The second terminal may also specify a target path according to the service logic, for example, different target paths may be provided for the same type of file in data of different applications. In a possible implementation manner, the sending, by the second terminal, the target path to the first terminal specifically includes: and the second terminal sends M target paths to the first terminal, wherein M is more than or equal to 2. That is, the second terminal sends a plurality of target paths to the first terminal so as to correspond to the files to be migrated under a plurality of types or source paths of the first terminal; the sent information may also include a corresponding relationship between the description information of the plurality of files to be migrated and the plurality of target paths.
It should be noted that, the second terminal may send multiple target paths to the first terminal at the same time, or may send the multiple target paths to the first terminal sequentially, which is not limited in this embodiment of the application.
Step S302: and the first terminal generates a file path mapping relation according to the target path and the information of the file to be migrated.
Specifically, after receiving a target path sent by a second terminal, a first terminal generates a file path mapping relationship according to the target path and corresponding information of a file to be migrated, where the file path mapping relationship includes a corresponding relationship between the target path and the information of the file to be migrated. Specifically, the second terminal may allocate a corresponding target path to the file to be migrated according to the type, size, or source path of the file to be migrated, that is, establish a mapping relationship between the file to be migrated and the target path. It can be understood that the information of the file to be migrated corresponds to the file to be migrated, and after the corresponding relationship between the target path and the information of the file to be migrated is determined, the corresponding relationship between the target path and the file to be migrated can be determined. The information of the file to be migrated may be identification information of the file to be migrated, for example, a name, a category, and the like of the file to be migrated, which is not specifically limited in this embodiment of the application.
In a possible implementation manner, the number of the target paths is M, the number of the files to be migrated is N, M is greater than or equal to 2, and N is greater than or equal to 2. In the application scenario, a file path mapping relationship needs to be generated according to the M target paths and the N files to be migrated, where the file path mapping relationship includes a correspondence between the M target paths and information of the N files to be migrated, that is, a correspondence between each target path and a file to be migrated is established.
Referring to fig. 4, a schematic diagram of a file path mapping relationship provided in the embodiment of the present application is shown. Fig. 4 shows 3 target paths and 3 pieces of file information to be migrated (the file information to be migrated is used to match the corresponding file to be migrated). As shown in fig. 4, in the file path mapping relationship, the first target path corresponds to the information of the second file to be migrated, that is, the second file to be migrated corresponding to the information of the second file to be migrated needs to be stored in the storage area corresponding to the first target path; the second target path corresponds to the information of the third file to be migrated, that is, the third file to be migrated corresponding to the information of the third file to be migrated needs to be stored in the storage area corresponding to the second target path; the third target path corresponds to the first file information to be migrated, that is, the first file to be migrated corresponding to the first file information to be migrated needs to be stored in the storage area corresponding to the third target path.
It should be noted that fig. 4 is only one possible implementation manner listed in the present application, and should not be taken as a limitation to the scope of the present application. For example, in one possible implementation, the target path and the information of the file to be migrated may not be in a one-to-one relationship.
Referring to fig. 5, another file path mapping relationship diagram provided in the embodiment of the present application is shown. In fig. 4, 3 target paths and 4 file information to be migrated are shown. The second target path corresponds to the third file information to be migrated and the fourth file information to be migrated respectively, that is, the third file to be migrated corresponding to the third file information to be migrated and the fourth file to be migrated corresponding to the fourth file information to be migrated are both stored in the storage area corresponding to the second target path.
Step S303: the first terminal sends the migration data to the second terminal.
Fig. 6 is a schematic data structure diagram of migration data according to an embodiment of the present application. As shown in fig. 6, the migration data includes a destination address field and a user data field, where the user data field is used to carry a file to be migrated, such as a video file, a picture file, and/or a document file. The destination address field is used for bearing a target path corresponding to the file to be migrated. It is noted that the destination address is used to characterize the storage location in the second terminal after transmission of the user data to the second terminal.
In the embodiment of the application, when the migration data is transmitted, the destination address field is set as the target path corresponding to the file to be migrated, and the second terminal directly stores the file to be migrated in the target path corresponding to the second terminal after receiving the file to be migrated. That is, data migration is completed only by one write operation, and system performance overhead is reduced.
Specifically, when two or more files to be migrated exist, migration data corresponding to each file to be migrated is sequentially sent to the second terminal. If the bandwidth allows, a plurality of files to be migrated and corresponding migration data can be sent to the second terminal at the same time.
Step S304: and the second terminal stores the file to be migrated in the target path corresponding to the file to be migrated.
Referring to fig. 7, a schematic view of a data migration scenario provided in the embodiment of the present application is shown. The data migration scenario corresponds to the file path mapping relationship shown in fig. 5, and as shown in fig. 7, the first terminal sequentially sends migration data corresponding to the first file to be migrated, the second file to be migrated, and the third file to be migrated to the second terminal. Specifically, in migration data corresponding to the first file to be migrated, the destination address field is set as a third target path, the migration data is sent to the second terminal, and after the second terminal receives the migration data, the first file to be migrated is stored in the storage area corresponding to the third target path according to the third target path in the destination address field. Similarly, the second file to be migrated is stored in the storage area corresponding to the first target path, and the third file to be migrated is stored in the storage area corresponding to the second target path.
In the embodiment of the application, when the first terminal sends the migration data to the second terminal, the destination address of the migration data can be dynamically adjusted to provide corresponding destination addresses for different files to be migrated, instead of placing all files in a uniform target path, so that the files to be migrated are directly stored in the corresponding destination addresses, secondary write-in operation in the second terminal is avoided, and system overhead is saved.
In some possible implementation manners, the target path sent by the second terminal to the first terminal may be a path preset by the second terminal according to different file types. For example, the storage location of the picture file is preset as a first target path, the storage location of the video file is preset as a second target path, and the storage location of the document file is preset as a third target path.
In another possible implementation manner, before performing the data migration, the first terminal and the second terminal may determine the target path through data negotiation.
Referring to fig. 8, a schematic flow chart of another data migration method provided in the embodiment of the present application is shown. As shown in fig. 8, the method further includes the following steps before S301 on the basis of the embodiment shown in fig. 3.
Step S801: and the first terminal sends the description information of the file to be migrated to the second terminal.
In this embodiment of the present application, after a first terminal and a second terminal establish a communication connection, the first terminal first sends description information of a file to be migrated, for example, size information, type information, and/or source path information of the file to be migrated, to the second terminal.
The size information refers to the size of the data size of the file to be migrated, and may be, for example, 50M, 1G, or the like. It can be understood that the storage space of the target path corresponding to the file to be migrated should be greater than or equal to the data size, so as to prevent the storage of the file to be migrated from failing to be completed. That is to say, the size information may facilitate the second terminal to allocate a target path that meets the requirement of the storage space for the file to be migrated.
The type information refers to the type of the file to be migrated, and the same or similar target paths may be allocated to the file to be migrated of the same type. In some possible implementations, the file to be migrated may be divided into a picture file, a video file, and a document file. It should be noted that in different application scenarios, the classification modes of the files to be migrated are different, and the specific types of the files to be migrated are not limited in the embodiment of the present application.
The source path information refers to a storage path of the file to be migrated in the first terminal. According to the method and the device, the first terminal sends the source path information to the second terminal, and the second terminal preferentially determines the target path according to the source path information, so that after data migration is completed, the storage position of the file to be migrated conforms to the original use habit of a user as much as possible.
Step S802: and the second terminal determines a target path according to the description information of the file to be migrated.
After receiving the description information of the file to be migrated, the second terminal may allocate a target path meeting the requirement for the file to be migrated according to the description information of the file to be migrated, and may further send the target path and a corresponding relationship between the target path and the description information of the file to be migrated to the first terminal. Because the file to be migrated is matched with the file description information to be migrated, the corresponding relationship between the target path and the file to be migrated, that is, the file path mapping relationship, can be determined according to the corresponding relationship between the target path and the file description information to be migrated.
In practical application, the first terminal may reserve the corresponding relationship between the target path sent by the second terminal and the description information of the file to be migrated, or modify the corresponding relationship, and generate the file path mapping relationship according to the mapping rule of the second terminal, which is not limited in the embodiment of the present application.
For example, the target path meets one or a combination of the following conditions:
1. and when the description information of the file to be migrated comprises the size information of the file to be migrated, allocating a target path for the file to be migrated according to the size information, wherein the storage space corresponding to the target path is larger than or equal to the size of the file to be migrated.
2. And when the description information of the file to be migrated comprises the type information of the file to be migrated, allocating a target path matched with the type of the file to be migrated. For example, if the file to be migrated is a picture file, and the picture file is stored in the first target path in the second terminal, the first target path is allocated to the file to be migrated.
3. When the description information of the file to be migrated includes the source path of the file to be migrated, it may be considered that a target path identical to the source path is allocated to the file to be migrated preferentially. If the second terminal does not have the target path which is the same as the source path, other target paths are allocated to the file to be migrated.
It should be noted that the above description information of the file to be migrated is only one possible implementation manner listed in the embodiment of the present application, and a person skilled in the art may set other description information of the file to be migrated according to actual needs, which is not limited in the embodiment of the present application.
By adopting the technical scheme provided by the embodiment of the application, the first terminal and the second terminal carry out data negotiation before data migration, and then a target path which is more in line with an actual application scene can be determined.
It can be understood that, by using the above data migration scheme, for each file to be migrated, a target path needs to be sent from the second terminal to the first terminal, then a file path mapping relationship is established according to the target path, and then migration data corresponding to each file to be migrated is sent to the second terminal in sequence.
However, in practical applications, there may be some smaller files to be migrated, for example, the size of the file to be migrated may be only "small files" of several KB or several MB, and it is obvious that the above data processing manner for each "small file" may increase the system overhead. Based on the method, the embodiment of the application also provides another data migration method.
Referring to fig. 9, a schematic flow chart of another data migration method provided in the embodiment of the present application is shown. The method further includes the following steps based on the embodiment shown in fig. 3.
Step S901: the first terminal packs two or more files to be migrated to generate a file package corresponding to the two or more files to be migrated.
In specific implementation, a threshold of the size of a file may be preset, two or more files to be migrated that are less than or equal to the threshold of the size may be packaged, a corresponding file package may be generated, and data migration may be performed in the form of a file package, where the file package may be a compressed package.
It should be noted that for the file to be migrated that is less than or equal to the size threshold, a target path and a file path mapping relationship do not need to be configured in advance in the first terminal, so that system overhead can be saved.
Step S902: and the first terminal sends the migration data corresponding to the file packet to the second terminal.
Since the file package includes a plurality of files to be migrated, the file package needs to be stored in the temporary folder of the second terminal, and then the files to be migrated in the file package need to be moved to corresponding target paths respectively. Specifically, a user data field of the migration data is set to carry a file package, a destination address field of the migration data is set to carry a temporary path corresponding to the file package, the destination address can be determined by the second terminal and then sent to the first terminal, and different temporary paths can be designated for different types of file packages of files to be migrated.
Step S903: and the second terminal stores the file package in a temporary path corresponding to the file package.
Since the destination address in the migration data is the temporary path corresponding to the file package, after receiving the file package, the second terminal stores the file package in the temporary path, that is, in the folder corresponding to the temporary path.
Step S904: and the second terminal moves the file to be migrated in the file package to a target path corresponding to the file to be migrated.
After the file package is stored in the temporary folder, the second terminal may respectively move the files to be migrated in the file package to the corresponding target paths. The target path may be a path allocated by the second terminal according to the type of the file to be migrated or other information; alternatively, the path information carried in the migration data may also be used. This is not particularly limited by the embodiments of the present application.
In a specific implementation, if the file packet is a compressed packet, the compressed packet needs to be decompressed, and then the decompressed file to be migrated is moved to a target path corresponding to the file to be migrated.
In the embodiment of the application, the files to be migrated with small data volume are packed, and data migration is performed in a file package mode, so that the configuration of the mapping relation between the target path and the file path of each small file is avoided, and the system overhead can be saved.
In one possible application scenario, the file to be migrated may include an application file and application data corresponding to the application file. The application program file can be understood as an installation package corresponding to an application program of a user in a terminal, such as a mailbox; application data may be understood as specific data generated by a user when using an application, such as mail in a mailbox.
The application data may be migrated in the manner shown in fig. 3. However, since the application data is usually stored under the installation directory of the application file, before the application data migration is performed in the manner shown in fig. 3, it is necessary to perform data migration on the application file first, then install the application in the second terminal, and further determine the target path corresponding to the application data.
Referring to fig. 10, a schematic flow chart of another data migration method according to the embodiment of the present application is provided. In this implementation manner, the file to be migrated includes application data corresponding to the application program file, and the target path includes a target path corresponding to the application data, and before step S301 shown in fig. 3, the following steps are further included.
Step S1001: and the first terminal sends the migration data corresponding to the application program file to the second terminal. Before migration of application data is performed, application files are migrated first. Since the application file needs to be installed, the application file may be stored in a temporary folder, that is, the destination address field of the migration data is set as a temporary path corresponding to the application file, and in addition, the user data field of the migration data is set as the application file. Of course, the application program file may also be stored in other locations of the second terminal, which is not particularly limited in this embodiment of the application.
Step S1002: the second terminal installs the application program file.
And the second terminal installs the application program after receiving the application program file. It will be appreciated that after installation is complete, a corresponding installation catalog is generated.
Step S1003: and the second terminal determines a target path corresponding to the application data according to the installation directory of the application program file.
Typically, the application data needs to be stored under the installation directory of the application program file, i.e. at the corresponding location of the installation directory. Therefore, after the installation directory of the application program file is generated, the target path corresponding to the application data is determined according to the installation directory.
In the subsequent step, the migration of the application data is realized by the method in the embodiment shown in fig. 3.
Referring to fig. 11, a block diagram of a software structure of an electronic device according to an embodiment of the present application is provided. The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android (Android) system is divided into four layers, an application layer, a framework layer, a hardware abstraction layer, and a kernel layer from top to bottom.
An Application layer (App) may comprise a series of Application packages. For example, the application package may include a data migration application. In particular, the application layer may be further divided into an application interface (UI) and application logic. The application interface of the data migration application comprises a file selection interface and a file receiving interface, wherein a user can select a file to be migrated on the file selection interface and trigger the file to be migrated to be transmitted; and displaying the file to be migrated and the storage position of the file to be migrated, which are received by the terminal, on a file receiving interface, so that a user can conveniently check the data migration state. The application logic of the data migration application comprises a sending module, a receiving module, a backup service module and a file path management module, wherein the sending module and the receiving module are respectively used for sending and receiving migration data or data related to the migration data; the backup service module is used for backup management of the file to be migrated; the file path management module is used for managing a target path of the file to be migrated and a mapping relation of the file path.
The Framework layer (FWK) provides an Application Programming Interface (API) and a programming Framework for applications at the application layer, including some predefined functions.
A Hardware Abstraction Layer (HAL) is an interface layer between the operating system kernel and the hardware circuitry, which is intended to abstract the hardware. It hides the hardware interface details of specific platform, provides virtual hardware platform for operation system, makes it have hardware independence, and can be transplanted on several platforms.
The kernel layer is a layer between hardware and software. For example, the core layer includes a display driver, a camera driver, an audio driver, a sensor driver, and the like.
Referring to fig. 12, a schematic flow chart of another data migration method according to the embodiment of the present application is provided. The method shown in fig. 12 includes a first terminal and a second terminal, where the first terminal is a data migration device, that is, an old terminal; the second terminal is a data migration device, i.e. a new terminal. Both the first terminal and the second terminal can adopt the software structure shown in fig. 11, as shown in fig. 12, which mainly includes the following steps.
Step S1201: and the user selects the file to be migrated on a file selection interface of the first terminal.
In the embodiment of the application, the first terminal is a data migration terminal, and a user can select a file to be migrated in a file selection interface of the first terminal and trigger a file to be migrated selection instruction.
Referring to fig. 13, a schematic diagram of a file selection and receiving interface provided in the embodiment of the present application is shown. As shown in fig. 13(a) in fig. 13, a list of a plurality of files (file 1, file 2, file 3, file 4, file 5, and file 6) is stored in the first terminal, and may be selected according to file types, source paths, and sizes, or may be selected according to specific files, and a user may select a file to be migrated, that is, a file to be migrated to the second terminal, from the files stored in the first terminal. For example, the user may select file 2 as the file to be migrated by triggering the area where file 2 is located. Certainly, the user may also select multiple files as the files to be migrated at the same time, for example, all the files in a certain path, which is not specifically limited in this embodiment of the present application.
Step S1202: and sending a file selection instruction to be migrated to a file path management module of the first terminal.
After the user selects the file to be migrated through the file selection interface, the file to be migrated selection instruction is sent to the file path management module. The file to be migrated may include selected file description information to be migrated, where the file to be migrated may be size information, type information, and/or source path information of the file to be migrated.
For example, if the file 2 in (a) in step 13 is selected as the file to be migrated, the file to be migrated description information in the file to be migrated selection instruction may include size information, type information, and/or source path information of the file 2.
Step S1203: and the file path management module of the first terminal sends a target path request instruction to the sending module.
After receiving the selection instruction of the file to be migrated, the file path management module of the first terminal sends a target path request instruction to the sending module, so that the sending module sends the target path request instruction to the second terminal.
The target path request instruction comprises description information of a file to be migrated.
Step S1204: and the sending module of the first terminal sends a target path request instruction to the receiving module of the second terminal.
And after receiving the target path request instruction, the sending module of the first terminal sends the target path request instruction to the receiving module of the second terminal.
Step S1205: and the receiving module of the second terminal sends a target path request instruction to the file path management module.
After receiving the target path request instruction, the receiving module of the second terminal sends the target path request instruction to the file path management module of the second terminal, so that the file path management module determines a target path according to the description information of the file to be migrated in the target path request instruction.
Step S1206: and the file path management module of the second terminal determines the target path.
After receiving the target path request instruction, the file path management module of the second terminal may determine the target path according to the description information of the file to be migrated in the target path request instruction.
For example, when the description information of the file to be migrated includes size information of the file to be migrated, a target path is allocated to the file to be migrated according to the size information, and a storage space corresponding to the target path is greater than or equal to the size of the file to be migrated.
And when the description information of the file to be migrated comprises the type information of the file to be migrated, allocating a target path matched with the type of the file to be migrated. For example, if the file to be migrated is a picture file, and the picture file is stored in the first target path in the second terminal, the first target path is allocated to the file to be migrated.
When the description information of the file to be migrated includes the source path of the file to be migrated, it may be considered that a target path that is the same as the source path is allocated to the file to be migrated at the second terminal in priority. If the second terminal does not have the target path which is the same as the source path, other target paths are allocated to the file to be migrated.
Step S1207: and the file path management module of the second terminal sends the target path to the sending module.
After the file path management module of the second terminal completes the allocation of the target path, the file path management module may send the target path to the sending module, so that the sending module sends the target path to the first terminal.
It should be noted that the target path may be one or more. That is, multiple target paths corresponding to multiple files to be migrated may be determined at the same time, where the sending information includes the target paths corresponding to the description information of the multiple files to be migrated, which is not limited in this embodiment of the present application.
Step S1208: and the sending module of the second terminal sends the target path to the receiving module of the first terminal.
After receiving the target path, the sending module of the second terminal sends the target path corresponding to the plurality of file description information to be migrated to the first terminal, and specifically, sends the target path to the receiving module of the first terminal.
Step S1209: and the receiving module of the first terminal sends the target path to the file path management module.
After receiving the target path, the receiving module of the first terminal sends the target path corresponding to the description information of the plurality of files to be migrated to the file path management module, so that the file path management module generates a corresponding file path mapping relationship according to the target path.
Step 1210: and the file path management module of the first terminal generates a file path mapping relation.
And after receiving the target path, the file path management module of the first terminal generates a file path mapping relation according to the corresponding relation between the target path and the description information of the file to be migrated. The file path mapping relationship comprises a corresponding relationship between a target path and information of a file to be migrated, and the description information of the file to be migrated can be the size, the type or the source path of the file, and can also be the name, the identification and the like of the file.
Step S1211: and the user triggers a file transmission instruction to be migrated on the file selection interface.
After the file path mapping relation is generated, the file to be migrated can be transmitted. Specifically, the user may trigger a file to be migrated transmission instruction on the file selection interface.
Step S1212: and sending a file transmission instruction to a backup service module of the first terminal.
After the user triggers the file transmission instruction to be migrated on the file selection interface, the file transmission instruction to be migrated is sent to the backup service module.
Step S1213: and the file path management module of the first terminal sends the file path mapping relation to the backup service module.
When the file to be migrated is sent, the destination address corresponding to the file to be migrated needs to be determined according to the file path mapping relationship, and therefore the file path mapping relationship needs to be sent to the backup service module.
Of course, the backup service module may also query, according to the file to be migrated, a target path corresponding to the file to be migrated in the file path management module, which is not specifically limited in this embodiment of the application.
Step S1214: and the backup service module of the first terminal determines a destination address corresponding to the file to be migrated according to the file path mapping relation.
The backup service module may determine a destination address corresponding to the file to be migrated according to the file path mapping relationship, and may also query the file path management module for a target path corresponding to the file to be migrated, which is not specifically limited in the embodiment of the present application.
The destination address is a target path corresponding to the file to be migrated. For example, in the file path mapping relationship shown in fig. 4, the first target path corresponds to the second file to be migrated, and the destination address corresponding to the second file to be migrated is the first target path.
Step S1215: and the sending module of the first terminal sends the migration data to the receiving module of the second terminal.
In the embodiment of the application, the data structure of the migration data comprises a destination address field and a user data field, the user data field of the migration data is set as a file to be migrated, and the destination address field of the migration data is set as a target path corresponding to the file to be migrated.
Step S1216: and the receiving module of the second terminal stores the file to be migrated to the target path corresponding to the destination address.
That is, after receiving the file to be migrated, the second terminal directly stores the file to be migrated in the corresponding target path, and completes data migration only by performing write-in operation once, thereby reducing system performance overhead.
Step S1217: and the receiving module of the second terminal sends the migration information of the file to be migrated to the file receiving interface.
In a specific implementation, after receiving the file to be migrated, the receiving module may send the migration information of the file to be migrated to the receiving interface, so that the user can know the data migration state. The migration information may be a file name, a file thumbnail, or file migration progress, which has been completed by the migration, and this is not specifically limited in the embodiment of the present application.
Referring to fig. 13(b) in fig. 13, the file receiving interface corresponds to the file selection interface shown in fig. 13(a), the user selects files 2 and 4 as files to be migrated in the file selection interface shown in fig. 13(a), and after the file migration is completed, icons of files 2 and 4 are displayed in the file receiving interface of the second terminal shown in fig. 13(b) to notify the user of the completed data migration state, so as to improve user experience.
In the embodiment of the application, when the first terminal sends the migration data to the second terminal, the destination address of the migration data can be dynamically adjusted, so that the file to be migrated is directly stored in the corresponding destination address, secondary write-in operation in the second terminal is avoided, and system overhead is saved.
Corresponding to the embodiment of the method, the application also provides a first terminal, and the first terminal comprises one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions which, when executed by the first terminal, cause the first terminal to perform some or all of the steps of the method embodiments described above at the first terminal side.
Corresponding to the above method embodiment, the present application further provides a second terminal, where the second terminal includes one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions which, when executed by the second terminal, cause the second terminal to perform some or all of the steps of the above method embodiments at the second terminal side.
Referring to fig. 14, a schematic structural diagram of a terminal provided in an embodiment of the present application is shown. The terminal may be the first terminal and/or the second terminal in the above embodiments, as shown in fig. 14, the terminal 1500 may include a processor 1510, an external memory interface 1520, an internal memory 1521, a Universal Serial Bus (USB) interface 1530, a charging management module 1540, a power management module 1541, a battery 1542, an antenna 1, an antenna 2, a mobile communication module 1550, a wireless communication module 1560, an audio module 1570, a speaker 1570A, a receiver 1570B, a microphone 1570C, an earphone interface 1570D, a sensor module 1580, a button 1590, a motor 1591, an indicator 1592, a camera 1593, a display 1594, and a Subscriber Identity Module (SIM) card interface 1595, and the like. The sensor module 1580 may include a pressure sensor 1580A, a gyroscope sensor 1580B, an air pressure sensor 1580C, a magnetic sensor 1580D, an acceleration sensor 1580E, a distance sensor 1580F, an approaching light sensor 1580G, a fingerprint sensor 1580H, a temperature sensor 1580J, a touch sensor 1580K, an ambient light sensor 1580L, a bone conduction sensor 1580M and the like.
It is to be understood that the illustrated structure of the embodiments of the present invention is not to be specifically limited to the terminal 1500. In other embodiments of the present application, terminal 1500 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
Processor 1510 may include one or more processing units, such as: the processor 1510 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), among others. Wherein, the different processing units may be independent devices or may be integrated in one or more processors.
The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.
A memory may also be provided in the processor 1510 for storing instructions and data. In some embodiments, the memory in the processor 1510 is a cache memory. The memory may hold instructions or data that have just been used or recycled by processor 1510. If the processor 1510 needs to reuse the instruction or data, it may be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 1510, thereby increasing the efficiency of the system.
In some embodiments, processor 1510 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.
The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 1510 may include multiple sets of I2C buses. The processor 1510 may be respectively coupled with the touch sensor 1580K, the charger, the flash, the camera 1593, and the like through different I2C bus interfaces.
The I2S interface may be used for audio communication. In some embodiments, processor 1510 may include multiple sets of I2S buses. Processor 1510 may be coupled to audio module 1570 via an I2S bus enabling communication between processor 1510 and audio module 1570.
The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, audio module 1570 and wireless communication module 1560 may be coupled by a PCM bus interface.
The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is typically used to connect the processor 1510 with the wireless communication module 1560.
The MIPI interface may be used to connect the processor 1510 to peripheral devices such as a display screen 1594 and a camera 1593. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 1510 and camera 1593 communicate over a CSI interface to enable the capture functionality of terminal 1500. The processor 1510 and the display screen 1594 communicate through the DSI interface to implement the display function of the terminal 1500.
The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, GPIO interfaces may be used to connect the processor 1510 with the camera 1593, the display 1594, the wireless communication module 1560, the audio module 1570, the sensor module 1580, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.
The USB interface 1530 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 1530 can be used to connect a charger to charge the terminal 1500, and can also be used to transmit data between the terminal 1500 and peripheral devices.
It should be understood that the connection relationship between the modules shown in the embodiment of the present invention is only an exemplary illustration, and does not limit the structure of the terminal 1500. In other embodiments of the present application, the terminal 1500 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.
The charge management module 1540 is configured to receive a charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 1540 may receive charging inputs from a wired charger through the USB interface 1530. In some wireless charging embodiments, the charging management module 1540 can receive wireless charging input through the wireless charging coil of the terminal 1500. While the charging management module 1540 charges the battery 1542, power may be supplied to the terminal through the power management module 1541.
The power management module 1541 is configured to connect the battery 1542, the charging management module 1540, and the processor 1510. The power management module 1541 receives input from the battery 1542 and/or the charging management module 1540 and provides power to the processor 1510, the internal memory 1521, the display 1594, the camera 1593, the wireless communication module 1560, and the like. Power management module 1541 may also be used to monitor parameters such as battery capacity, battery cycle count, and battery state of health (leakage, impedance).
The wireless communication function of the terminal 1500 may be implemented by the antenna 1, the antenna 2, the mobile communication module 1550, the wireless communication module 1560, a modem processor, a baseband processor, and the like.
The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in terminal 1500 can be configured to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.
The mobile communication module 1550 can provide a solution including 2G/3G/4G/5G wireless communication applied on the terminal 1500. The mobile communication module 1550 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 1550 may receive the electromagnetic wave from the antenna 1, filter, amplify, and transmit the received electromagnetic wave to the modem processor for demodulation. The mobile communication module 1550 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate the electromagnetic waves. In some embodiments, at least some of the functional modules of the mobile communication module 1550 may be disposed in the processor 1510. In some embodiments, at least some of the functional blocks of the mobile communication module 1550 may be disposed in the same device as at least some of the blocks of the processor 1510.
The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 1570A, the receiver 1570B, etc.) or displays images or video through the display screen 1594.
The wireless communication module 1560 may provide a solution for wireless communication applied to the terminal 1500, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 1560 may be one or more devices that integrate at least one communication processing module. The wireless communication module 1560 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering on the electromagnetic wave signal, and transmits the processed signal to the processor 1510. The wireless communication module 1560 may also receive signals to be transmitted from the processor 1510, modulate the frequency of the signals, amplify the signals, and convert the signals to electromagnetic waves via the antenna 2 for radiation.
In some embodiments, antenna 1 of terminal 1500 is coupled to mobile communication module 1550 and antenna 2 is coupled to wireless communication module 1560 such that terminal 1500 can communicate with networks and other devices via wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).
The terminal 1500 implements a display function via the GPU, the display screen 1594, and the application processor, etc. The GPU is a microprocessor for image processing and is connected with a display screen 1594 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 1510 may include one or more GPUs that execute program instructions to generate or alter display information.
The display screen 1594 is used to display images, video, and the like. The display screen 1594 includes a display panel. The display panel may be a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, the terminal 1500 may include 1 or N display screens 1594, N being a positive integer greater than 1.
The terminal 1500 may implement a photographing function through the ISP, the camera 1593, the video codec, the GPU, the display 1594, the application processor, and the like.
The ISP is used to process the data fed back by the camera 1593. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. I is
The camera 1593 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. In some embodiments, the terminal 1500 may include 1 or N cameras 1593, N being a positive integer greater than 1.
The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the terminal 1500 selects in a frequency bin, the digital signal processor is used for performing fourier transform and the like on the frequency bin energy.
Video codecs are used to compress or decompress digital video. Terminal 1500 can support one or more video codecs. In this way, the terminal 1500 can play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.
The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. The NPU can realize applications such as intelligent recognition of the terminal 1500,
the external memory interface 1520 may be used to connect an external memory card, such as a Micro SD card, to implement the storage capability of the expansion terminal 1500. The external memory card communicates with the processor 1510 through an external memory interface 1520 to implement data storage functions. For example, files such as music, video, etc. are saved in an external memory card.
The internal memory 1521 may be used to store computer-executable program code, which includes instructions. The internal memory 1521 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The stored data area may store data (e.g., audio data, a phonebook, etc.) created during use of the terminal 1500, and the like. In addition, the internal memory 1521 may include a high-speed random access memory, and may also include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like. The processor 1510 executes various functional applications of the terminal 1500 and data processing by executing instructions stored in the internal memory 1521 and/or instructions stored in a memory provided in the processor.
Terminal 1500 can implement audio functionality via audio module 1570, speaker 1570A, receiver 1570B, microphone 1570C, headset interface 1570D, and application processor, among others. Such as music playing, recording, etc.
Audio module 1570 is configured to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. Audio module 1570 may also be used to encode and decode audio signals.
The speaker 1570A, also known as a "horn," is used to convert electrical audio signals into sound signals. The terminal 1500 can listen to music or listen to a hands-free call through the speaker 1570A.
The receiver 1570B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the terminal 1500 answers a call or voice information, it can answer a voice by bringing the receiver 1570B close to the human ear.
Microphone 1570C, also known as a "microphone," converts sound signals into electrical signals. When making a call or sending voice information, the user can input a voice signal to the microphone 1570C by making a sound by approaching the microphone 1570C with the mouth. The terminal 1500 may be provided with at least one microphone 1570C.
The headset interface 1570D is used to connect wired headsets. The earphone interface 1570D may be a USB interface 1530 or may be a 3.5mm open mobile platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.
The pressure sensor 1580A is used for sensing a pressure signal and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 1580A may be disposed on the display screen 1594. The pressure sensors 1580A can be of a wide variety, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 1580A, the capacitance between the electrodes changes. The terminal 1500 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 1594, the terminal 1500 detects the intensity of the touch operation according to the pressure sensor 1580A. The terminal 1500 may also calculate the position of the touch from the detection signal of the pressure sensor 1580A.
The gyroscope sensor 1580B may be used to determine the motion attitude of the terminal 1500. In some embodiments, the angular velocity of terminal 1500 about three axes (i.e., x, y, and z axes) may be determined by gyroscope sensor 1580B. The gyro sensor 1580B can be used for photographing anti-shake.
The air pressure sensor 1580C is used for measuring air pressure. In some embodiments, the terminal 1500 calculates altitude, aiding positioning and navigation through barometric pressure values measured by the barometric pressure sensor 1580C.
The magnetic sensor 1580D includes a hall sensor. The terminal 1500 may detect the opening and closing of the flip holster using the magnetic sensor 1580D.
The acceleration sensor 1580E can detect the magnitude of acceleration of the terminal 1500 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the terminal 1500 is stationary. The method can also be used for recognizing the terminal gesture, and is applied to horizontal and vertical screen switching, pedometers and other applications.
And a distance sensor 1580F for measuring a distance. The terminal 1500 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, terminal 1500 may utilize range sensor 1580F to range for fast focus.
The proximity light sensor 1580G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal 1500 emits infrared light to the outside through a light emitting diode. Terminal 1500 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the terminal 1500.
The ambient light sensor 1580L is used to sense ambient light brightness. The terminal 1500 may adaptively adjust the brightness of the display 1594 based on the perceived ambient light level.
The fingerprint sensor 1580H is used to collect a fingerprint. The terminal 1500 can utilize the collected fingerprint characteristics to realize fingerprint unlocking, access to an application lock, fingerprint photographing, fingerprint incoming call answering and the like.
The temperature sensor 1580J is used for detecting temperature. In some embodiments, terminal 1500 implements a temperature processing strategy using the temperature detected by temperature sensor 1580J.
The touch sensor 1580K is also referred to as a "touch device". The touch sensor 1580K may be disposed on a display screen 1594, and the touch sensor 1580K and the display screen 1594 form a touch screen, which is also referred to as a "touch screen". The touch sensor 1580K is used to detect a touch operation applied thereto or nearby. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided via the display screen 1594. In other embodiments, the touch sensor 1580K can be disposed on a surface of the terminal 1500 at a location different from the display screen 1594.
Bone conduction sensor 1580M may acquire a vibration signal. In some embodiments, the bone conduction sensor 1580M may acquire a vibration signal of the human voice vibrating a bone mass. The bone conduction sensor 1580M can also be in contact with human body pulse to receive blood pressure pulsation signals.
The keys 1590 include a power-on key, a volume key, and the like. The keys 1590 may be mechanical keys. Or may be touch keys. The terminal 1500 may receive a key input, and generate a key signal input related to user setting and function control of the terminal 1500.
The motor 1591 may generate a vibration cue. The motor 1591 may be used for incoming call vibration prompts, as well as for touch vibration feedback.
The indicator 1592 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.
The SIM card interface 1595 is for connecting to a SIM card. The SIM card can be attached to and detached from the terminal 1500 by being inserted into the SIM card interface 1595 or being pulled out of the SIM card interface 1595. The terminal 1500 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 1595 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 1595 may be inserted with multiple cards at the same time. The types of the plurality of cards may be the same or different. The terminal 1500 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the terminal 1500 employs eSIM, namely: an embedded SIM card.
In a specific implementation manner, the present application further provides a computer storage medium, where the computer storage medium may store a program, and when the program runs, the computer storage medium controls a device in which the computer readable storage medium is located to perform some or all of the steps in the foregoing embodiments. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).
In a specific implementation, an embodiment of the present application further provides a computer program product, where the computer program product includes executable instructions, and when the executable instructions are executed on a computer, the computer is caused to perform some or all of the steps in the foregoing method embodiments.
In the embodiments of the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, and means that there may be three relationships, for example, a and/or B, and may mean that a exists alone, a and B exist simultaneously, and B exists alone. Wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" and similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, and c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.
Those of ordinary skill in the art will appreciate that the various elements and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided by the present invention, any function, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention or a part thereof which substantially contributes to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only an embodiment of the present invention, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the protection scope of the present invention. The protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (16)

1. A data migration method is applied to a first terminal, and the method comprises the following steps:
receiving a target path sent by a second terminal, wherein the target path indicates a final storage position of a file to be migrated in the second terminal;
generating a file path mapping relation according to the target path and the information of the file to be migrated, wherein the file path mapping relation comprises a corresponding relation between the target path and the information of the file to be migrated, and the information of the file to be migrated corresponds to the file to be migrated;
and sending migration data to the second terminal, wherein a data structure of the migration data comprises a destination address field and a user data field, the user data field is used for bearing the file to be migrated, and the destination address field is used for bearing a target path corresponding to the file to be migrated.
2. The method of claim 1,
the receiving a target path sent by a second terminal includes: receiving M target paths sent by a second terminal, wherein the M target paths are the final storage positions of N files to be migrated in the second terminal, M is more than or equal to 2, and N is more than or equal to 2;
generating a file path mapping relation according to the target path and the information of the file to be migrated, wherein the file path mapping relation comprises: generating a file path mapping relation according to the M target paths and the N pieces of information of the files to be migrated, wherein the file path mapping relation comprises the corresponding relation between the M target paths and the N pieces of information of the files to be migrated;
the sending migration data to the second terminal includes: and sending migration data corresponding to each file to be migrated to the second terminal.
3. The method according to claim 1 or 2, wherein before the receiving the target path sent by the second terminal, further comprising:
and sending description information of the file to be migrated to the second terminal, wherein the description information of the file to be migrated comprises size information, type information and/or source path information of the file to be migrated.
4. The method according to claim 3, wherein the target path is allocated according to size information, type information and/or source path information of the file to be migrated.
5. The method of claim 1 or 2, further comprising:
packaging two or more files to be migrated, wherein the two or more files to be migrated are smaller than or equal to a preset size threshold value, and generating file packages corresponding to the two or more files to be migrated;
the sending migration data to the second terminal includes: and sending migration data corresponding to the file packet to the second terminal, wherein a user data field of the migration data is used for bearing the file packet, and a destination address field of the migration data is used for bearing a temporary path corresponding to the file packet.
6. The method according to claim 1 or 2, wherein the file to be migrated includes application data corresponding to an application program file, and the target path includes a target path corresponding to the application data;
before the receiving the target path sent by the second terminal, the method further includes:
and sending migration data corresponding to the application program file to the second terminal, wherein a user data field of the migration data is used for bearing the application program file, and a destination address field of the migration data is used for bearing a target path or a temporary path corresponding to the application program file.
7. A data migration method, applied to a second terminal, includes:
sending a target path to a first terminal, wherein the target path is a final storage position of a file to be migrated in a second terminal;
receiving migration data sent by the first terminal, wherein a data structure of the migration data comprises a destination address field and a user data field, the user data field is used for bearing the file to be migrated, and the destination address field is used for bearing a target path corresponding to the file to be migrated;
and storing the file to be migrated in a target path corresponding to the file to be migrated.
8. The method of claim 7,
the sending the target path to the first terminal includes: sending M target paths to a first terminal, wherein the M target paths are final storage paths of N files to be migrated in a second terminal, M is more than or equal to 2, and N is more than or equal to 2;
the receiving migration data sent by the first terminal includes: receiving migration data corresponding to each file to be migrated, which is sent by the first terminal;
the storing the file to be migrated in the target path corresponding to the file to be migrated includes: and storing each file to be migrated in a target path corresponding to each file to be migrated.
9. The method according to claim 7 or 8, wherein before said sending the target path to the first terminal, further comprising:
receiving description information of a file to be migrated, which is sent by the first terminal, wherein the description information of the file to be migrated comprises size information, type information and/or source path information of the file to be migrated;
and determining a target path corresponding to the file to be migrated according to the description information of the file to be migrated.
10. The method according to claim 9, wherein the determining a target path corresponding to the file to be migrated according to the file to be migrated description information includes:
when the description information of the file to be migrated comprises size information of the file to be migrated, allocating a target path for the file to be migrated according to the size information, wherein a storage space corresponding to the target path is larger than or equal to the size of the file to be migrated;
when the description information of the file to be migrated comprises the type information of the file to be migrated, allocating a target path matched with the type information for the file to be migrated;
and when the description information of the file to be migrated comprises a source path of the file to be migrated, allocating a target path which is the same as the source path to the file to be migrated.
11. The method of claim 7 or 8, further comprising:
receiving migration data which is sent by the first terminal and corresponds to a file packet, wherein a user data field of the migration data is used for bearing the file packet, and a destination address field of the migration data is used for bearing a temporary path corresponding to the file packet;
storing the file package in a temporary path corresponding to the file package;
the file package comprises two or more files to be migrated, wherein the two or more files to be migrated are smaller than or equal to a preset size threshold.
12. The method according to claim 7 or 8, wherein the file to be migrated includes application data corresponding to an application program file, and the target path includes a target path corresponding to the application data;
before the sending the target path to the first terminal, the method further includes:
receiving migration data which is sent by the second terminal and corresponds to the application program file, wherein a user data field of the migration data is used for bearing the application program file, and a destination address field of the migration data is used for bearing a target path or a temporary path corresponding to the application program file;
installing the application program file;
and determining a target path corresponding to the application data according to the installation directory of the application program file.
13. A first terminal, comprising:
one or more processors;
a memory;
and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions which, when executed by the first terminal, cause the first terminal to perform the method of any of claims 1-6.
14. A second terminal, comprising:
one or more processors;
a memory;
and one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs comprising instructions which, when executed by the second terminal, cause the second terminal to perform the method of any of claims 7-12.
15. A computer-readable storage medium, comprising a stored program, wherein the program, when executed, controls an apparatus in which the computer-readable storage medium resides to perform the method of any one of claims 1-6.
16. A computer-readable storage medium, comprising a stored program, wherein the program, when executed, controls an apparatus in which the computer-readable storage medium resides to perform the method of any one of claims 7-12.
CN202111048320.0A 2021-09-08 2021-09-08 Data migration method, terminal, storage medium, and program product Active CN115080505B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111048320.0A CN115080505B (en) 2021-09-08 2021-09-08 Data migration method, terminal, storage medium, and program product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111048320.0A CN115080505B (en) 2021-09-08 2021-09-08 Data migration method, terminal, storage medium, and program product

Publications (2)

Publication Number Publication Date
CN115080505A true CN115080505A (en) 2022-09-20
CN115080505B CN115080505B (en) 2023-07-14

Family

ID=83245597

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111048320.0A Active CN115080505B (en) 2021-09-08 2021-09-08 Data migration method, terminal, storage medium, and program product

Country Status (1)

Country Link
CN (1) CN115080505B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116009960A (en) * 2023-02-14 2023-04-25 花瓣云科技有限公司 Target micro-service migration method, system and electronic equipment

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080077605A1 (en) * 2006-09-25 2008-03-27 Microsoft Corporation Automatic discovery of application settings' storage locations
US20080162604A1 (en) * 2005-03-01 2008-07-03 Serge Soulet System and Method For Migrating a Platform, User Data, and Applications From at Least One Server to at Least One Computer
US20090210871A1 (en) * 2008-02-20 2009-08-20 Zak Dechovich System and method for software application migration
US20110167039A1 (en) * 2010-01-05 2011-07-07 Microsoft Corporation Distributed throttling for mailbox data replication
US20140222761A1 (en) * 2011-09-30 2014-08-07 Beijing Qihoo Technology Company Limited Terminal Backup and Recovery Method
CN105491113A (en) * 2015-11-25 2016-04-13 小米科技有限责任公司 Migrating method, device and terminal
CN106201789A (en) * 2016-07-27 2016-12-07 北京金山安全软件有限公司 Data backup method and device and terminal
CN106445663A (en) * 2016-09-14 2017-02-22 广东欧珀移动通信有限公司 Application data migration method and device
CN106527979A (en) * 2016-10-19 2017-03-22 广东欧珀移动通信有限公司 Data migration method and device
CN106547486A (en) * 2016-10-20 2017-03-29 广东欧珀移动通信有限公司 A kind of data migration method and device
CN107018189A (en) * 2017-03-31 2017-08-04 青岛海信移动通信技术股份有限公司 Migrate application data and receive the method and device of application data
US20180232174A1 (en) * 2017-02-15 2018-08-16 Beijing Baidu Netcom Science And Technology Co., Ltd. Data Migration Between Cloud Storage Systems

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080162604A1 (en) * 2005-03-01 2008-07-03 Serge Soulet System and Method For Migrating a Platform, User Data, and Applications From at Least One Server to at Least One Computer
US20080077605A1 (en) * 2006-09-25 2008-03-27 Microsoft Corporation Automatic discovery of application settings' storage locations
US20090210871A1 (en) * 2008-02-20 2009-08-20 Zak Dechovich System and method for software application migration
US20110167039A1 (en) * 2010-01-05 2011-07-07 Microsoft Corporation Distributed throttling for mailbox data replication
US20140222761A1 (en) * 2011-09-30 2014-08-07 Beijing Qihoo Technology Company Limited Terminal Backup and Recovery Method
CN105491113A (en) * 2015-11-25 2016-04-13 小米科技有限责任公司 Migrating method, device and terminal
CN106201789A (en) * 2016-07-27 2016-12-07 北京金山安全软件有限公司 Data backup method and device and terminal
CN106445663A (en) * 2016-09-14 2017-02-22 广东欧珀移动通信有限公司 Application data migration method and device
CN106527979A (en) * 2016-10-19 2017-03-22 广东欧珀移动通信有限公司 Data migration method and device
CN106547486A (en) * 2016-10-20 2017-03-29 广东欧珀移动通信有限公司 A kind of data migration method and device
US20180232174A1 (en) * 2017-02-15 2018-08-16 Beijing Baidu Netcom Science And Technology Co., Ltd. Data Migration Between Cloud Storage Systems
CN107018189A (en) * 2017-03-31 2017-08-04 青岛海信移动通信技术股份有限公司 Migrate application data and receive the method and device of application data

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116009960A (en) * 2023-02-14 2023-04-25 花瓣云科技有限公司 Target micro-service migration method, system and electronic equipment
CN116009960B (en) * 2023-02-14 2024-01-23 花瓣云科技有限公司 Target micro-service migration method, system and electronic equipment

Also Published As

Publication number Publication date
CN115080505B (en) 2023-07-14

Similar Documents

Publication Publication Date Title
CN111095723B (en) Wireless charging method and electronic equipment
CN112684969B (en) Always displaying method and mobile device
CN113691842A (en) Cross-device content projection method and electronic device
CN113254409A (en) File sharing method, system and related equipment
CN110636554B (en) Data transmission method and device
CN113490291B (en) Data downloading method and device and terminal equipment
CN114915721A (en) Method for establishing connection and electronic equipment
CN111615820B (en) Method and equipment for performing domain name resolution by sending key value to GRS server
CN111865646A (en) Terminal upgrading method and related device
CN112969089B (en) HTTP request transmission method and equipment
CN113596919B (en) Data downloading method and device and terminal equipment
CN114880251A (en) Access method and access device of storage unit and terminal equipment
CN115080505B (en) Data migration method, terminal, storage medium, and program product
CN114548141A (en) Method and device for generating waveform file, electronic equipment and readable storage medium
WO2022135195A1 (en) Method and apparatus for displaying virtual reality interface, device, and readable storage medium
CN113901485B (en) Application program loading method, electronic device and storage medium
CN114338642B (en) File transmission method and electronic equipment
CN115393676A (en) Gesture control optimization method and device, terminal and storage medium
CN113923351A (en) Method, apparatus, storage medium, and program product for exiting multi-channel video shooting
CN114445522A (en) Brush effect graph generation method, image editing method, device and storage medium
CN114329595B (en) Application program detection method, device, storage medium and program product
CN116048236B (en) Communication method and related device
CN116346982B (en) Method for processing audio, electronic device and readable storage medium
WO2023109569A1 (en) File storage method, file access method, electronic device, and storage medium
CN114661190A (en) Terminal window display method, terminal and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant