CN111274224B - Data migration method and device - Google Patents
Data migration method and device Download PDFInfo
- Publication number
- CN111274224B CN111274224B CN202010018967.8A CN202010018967A CN111274224B CN 111274224 B CN111274224 B CN 111274224B CN 202010018967 A CN202010018967 A CN 202010018967A CN 111274224 B CN111274224 B CN 111274224B
- Authority
- CN
- China
- Prior art keywords
- data
- layer data
- terminal
- local database
- migration
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- Y—GENERAL 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
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE 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/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a data migration method and a device, wherein the method comprises the following steps: layering and storing data of the terminal, wherein the data of the terminal comprises basic layer data, middle layer data and application layer data; searching a local database according to the obtained identification of the terminal to obtain a data searching result; and migrating the data of the terminal according to the data retrieval result. The data of the terminal are stored in a layered mode, so that the edge node server can search the local database according to the identification of the terminal, further determine which layers of data are stored in the local database, and migrate the data which are not stored, and therefore when the terminal is in a mobile process, the edge node server can use less time to migrate only the data which are not stored, migration data quantity is reduced, migration speed of the terminal data is increased, and experience of a terminal user is improved.
Description
Technical Field
The invention relates to the technical field of mobile edge computing, in particular to a data migration method and device.
Background
The mobile edge calculation is a distributed deployment scheme for providing calculation, storage and network capability for users at the edge side of the network, solves the problem of insufficient computing capability of the terminal users, and simultaneously solves the problem of time delay caused by overlong network transmission time between a cloud service center and the terminal users. Emerging edge applications take full advantage of the features of mobile edge computing to serve end users in close proximity thereto, e.g., virtual Reality (VR) technology, augmented Reality (Augmented Reality, AR) technology, intelligent driving technology, etc.
Edge applications face the problem of reduced quality of service caused by the movement of the end user while providing corresponding services. Along with the movement of the terminal user, the data of the terminal can be obtained by using a tool corresponding to the virtualization platform to integrally package and synchronize the file on the edge application, but the data volume involved in the method is larger, the time required for obtaining the data is longer, and the experience of the terminal user on the edge application is reduced in the process of migrating the data of the terminal.
Disclosure of Invention
Therefore, the invention provides a data migration method and device, which are used for solving the problem that the experience of a terminal user on an edge application is reduced because the data of a terminal is large in quantity and the time required for migrating the data of the terminal is long in the prior art.
To achieve the above object, a first aspect of the present invention provides a data migration method, including: layering and storing data of the terminal, wherein the data of the terminal comprises basic layer data, middle layer data and application layer data; searching a local database according to the obtained identification of the terminal to obtain a data searching result; and migrating the data of the terminal according to the data retrieval result.
Wherein, the data retrieval result comprises: any one of the first search result, the second search result, or the third search result; the first search result is that the local database only stores any one of basic layer data, middle layer data and application layer data; the second search result is any two of the basic layer data, the middle layer data and the application layer data stored in the local database; and the third search result is that the local database stores the base layer data, the middle layer data and the application layer data.
The data migration step of the terminal according to the data retrieval result comprises the following steps: if the data retrieval result is the first retrieval result, any two of the base layer data, the middle layer data and the application layer data which are not stored in the local database are obtained, and the obtained data are synchronized to the local database; if the data retrieval result is the second retrieval result, any one of the base layer data, the middle layer data and the application layer data which are not stored in the local database is obtained, and the obtained data are synchronized to the local database; and if the data retrieval result is the third retrieval result, determining that the data migration to the terminal is completed.
The method comprises the steps of obtaining any one of base layer data, middle layer data and application layer data which are not stored in a local database, and comprises the following steps: and acquiring any one of the base layer data, the middle layer data and the application layer data which are not stored in the local database from the edge data sharing node server.
The step of hierarchically storing the data of the terminal comprises the following steps: according to the action of the data of the terminal, storing the base layer data in a first shared edge node server or a second shared edge node server; storing the middle layer data in a second shared edge node server or a first shared edge node server; the application layer data is stored in a local database.
The data migration step of the terminal according to the data retrieval result comprises the following steps: according to the data retrieval result, determining that only application layer data is stored in a local database; determining storage addresses of middle layer data and base layer data, wherein the storage addresses comprise the address of a second shared edge node server or the address of a first shared edge node server; middle layer data and base layer data are retrieved from the memory address.
The step of searching the local database according to the acquired identification of the terminal to obtain a data searching result comprises the following steps: responding to a migration request sent by a terminal, and obtaining the identification of the terminal; and searching the data stored in the database by taking the identification of the terminal as an index to obtain a data search result.
Wherein the base layer data comprises: system data except for the edge application in the data of the terminal, wherein the system data comprises at least one of operating system data, system application and configuration files; the intermediate layer data includes: static data of the edge application; the application layer data includes: dynamic data of the edge application.
In order to achieve the above object, a second aspect of the present invention provides a data migration apparatus, comprising: the layering storage module is used for layering and storing data of the terminal, wherein the data of the terminal comprises base layer data, middle layer data and application layer data; the retrieval module is used for retrieving the local database according to the acquired identification of the terminal to obtain a data retrieval result; and the migration module is used for migrating the data of the terminal according to the data retrieval result.
Wherein, migration module includes: a data retrieval result comprising: any one of the first search result, the second search result, or the third search result; the first migration submodule is used for acquiring any two of base layer data, middle layer data and application layer data which are not stored in the local database when the data retrieval result is determined to be the first retrieval result, and synchronizing the acquired data to the local database; the second migration submodule is used for acquiring any one of base layer data, middle layer data and application layer data which are not stored in the local database when the data retrieval result is determined to be the second retrieval result, and synchronizing the acquired data to the local database; and the third migration submodule is used for determining that the data migration to the terminal is completed when the data retrieval result is determined to be the third retrieval result.
The invention has the following advantages: the data of the terminal are stored in a layered mode, so that the edge node server can search the local database according to the identification of the terminal, further determine which layers of data are stored in the local database, and migrate the data which are not stored, and therefore when the terminal is in a mobile process, the edge node server can use less time to migrate only the data which are not stored, migration data quantity is reduced, migration speed of the terminal data is increased, and experience of a terminal user is improved.
Drawings
The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification, illustrate the invention and together with the description serve to explain, without limitation, the invention.
FIG. 1 is a flow chart of a data migration method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a data migration method according to another embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a data migration apparatus according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a data migration system according to an exemplary embodiment of the present invention.
In the drawings:
301: hierarchical storage module 302: retrieval module
303: migration module 401: terminal
402: the first edge node server 403: second edge node server
404: second shared edge node server 405: first shared edge node server
Detailed Description
The following describes specific embodiments of the present invention in detail with reference to the drawings. It should be understood that the detailed description and specific examples, while indicating and illustrating the invention, are not intended to limit the invention.
For better understanding of the technical solutions of the present invention, the following describes in detail the method and apparatus, electronic device, and computer readable medium provided by the present invention with reference to the accompanying drawings.
Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The terms first and second in the description and claims of the invention and in the above-described figures are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate to enable the embodiments described herein to be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
One embodiment of the invention relates to a data migration method. The method is used for reducing the migration data volume, accelerating the migration speed of the terminal data and improving the experience of the terminal user.
The implementation details of the method in this embodiment are specifically described below, and the following is only for facilitating understanding of the implementation details of this embodiment, and is not necessary for implementing this embodiment.
Fig. 1 is a flowchart of a data migration method in this embodiment, which can be applied to an edge node server. The method may include the following steps.
In step 101, data of the terminal is hierarchically stored, and the data of the terminal includes base layer data, middle layer data, and application layer data.
It should be noted that, according to the system application correlation and the data change state, the data of the terminal is stored in layers. The base layer data includes: system data except for the edge application in the data of the terminal, wherein the system data comprises at least one of operating system data, system application and configuration files; the middle layer data comprises static data of the edge application; the application layer data includes dynamic data of the edge application.
For example, an edge application is an application that a user installs on a terminal to facilitate the user's use of the relevant edge resources. All files and data except for the edge application, such as the operating system data, the system application and the system configuration file of the application program; and the static data (such as configuration information related to the application program) used by the user when using the application program is divided into middle layer data; dynamic data (e.g., real-time data of user interaction using the application program, memory data occupied by the application program in real time, current state of user, etc.) used by the user when using the application program is divided into application layer data.
The above base layer data, middle layer data and application layer data may be stored in a local database, or may be stored in other edge servers, which is not limited herein. The above storage locations for each layer of data are only exemplified, and other non-explained storage addresses are also within the protection scope of the present application, and are not described herein again.
In step 102, the local database is searched according to the obtained identification of the terminal, and a data search result is obtained.
In step 103, the data of the terminal is migrated according to the data retrieval result.
It should be noted that, migration is understood as acquiring each layer of data of the corresponding terminal from the corresponding storage address, and synchronizing the data to the local database of the node edge server. There are many ways to obtain data, such as copying, sharing, etc., and this is not limiting. The above manner of acquiring data is merely illustrative, and other undescribed manners of acquiring data are also within the scope of protection of the present application, and are not described herein.
In this embodiment, the edge node server searches the local database according to the identifier of the terminal by storing the data of the terminal in a layered manner, so as to determine which layers of data are stored in the local database, and then migrate the data without the stored layers, so that when the terminal is moving, the edge node server can use less time to migrate only the data without the stored layers, reduce the migration data amount, accelerate the migration speed of the terminal data, and improve the experience of the terminal user.
In some specific implementations, an identification of a terminal is obtained in response to a migration request sent by the terminal; and searching the data stored in the database by taking the identification of the terminal as an index to obtain a data search result.
It should be noted that, the data retrieval result includes: any one of the first search result, the second search result, or the third search result; the first search result is that the local database only stores any one of basic layer data, middle layer data and application layer data; the second search result is any two of the basic layer data, the middle layer data and the application layer data stored in the local database; and the third search result is that the local database stores the base layer data, the middle layer data and the application layer data.
The second search result may be that the local database stores base layer data and middle layer data; the local database can also store application layer data and middle layer data; the local database may also hold base layer data and application layer data.
According to the above description, through the received migration request sent by the terminal, the edge node server can acquire the identifier of the terminal, and search the data stored in the database by taking the identifier of the terminal as an index, so that the specific layers of data of the terminal can be determined to be stored in the local server, the edge node server can conveniently perform subsequent data migration, and the data migration speed is improved.
In some specific implementations, step 103 in the above embodiments may also consist of the following steps.
In step 1031, if the data search result is determined to be the first search result, any two of the base layer data, the middle layer data and the application layer data, which are not stored in the local database, are acquired, and the acquired data are synchronized to the local database.
For example, when only the application layer data is stored in the local database, only the base layer data and the middle layer data need to be acquired; when only middle layer data is stored in the local database, only basic layer data and application layer data are required to be acquired; when only the base layer data is stored in the local database, only the application layer data and the middle layer data are required to be acquired.
In step 1032, if the data search result is determined to be the second search result, any one of the base layer data, the middle layer data, and the application layer data, which are not stored in the local database, is acquired, and the acquired data is synchronized to the local database.
For example, when the second search result is that the local database stores the base layer data and the middle layer data, only the application layer data is required to be acquired; when the second search result is that the local database stores the application layer data and the middle layer data, only the basic layer data is needed to be obtained; when the second search result is that the local database stores the data of the base layer and the data of the application layer, only the data of the middle layer is needed to be obtained.
The method comprises the steps of obtaining any one of base layer data, middle layer data and application layer data which are not stored in a local database, and comprises the following steps: and acquiring any one of the base layer data, the middle layer data and the application layer data which are not stored in the local database from the edge data sharing node server.
The edge data sharing node server may be an upper node server of the edge node server, or may be a server with the same network level as the edge node server, which is not limited herein, so long as any one of the base layer data, the middle layer data, and the application layer data that are not stored in the edge node server can be maintained in the edge data sharing node server, so that the edge node server can obtain the missing related data from the edge data sharing node server, and complete the migration of the terminal data.
The above types of edge data sharing node servers are only examples, and other types of servers that are not described are also within the scope of the present application, and are not described herein.
In step 1033, if it is determined that the data search result is the third search result, it is determined that the data migration to the terminal has been completed.
When the data migration is completed, it means that the edge node server obtains all the data of the terminal, and can service the terminal.
According to the description, the data of the terminal are migrated in a layering manner according to different retrieval results, so that the data migration speed is increased, the migration time is shortened, and the user experience is improved.
In some specific implementations, step 101 in the above embodiment may also consist of the following steps.
In step 1011, the base layer data is stored in either the first shared edge node server or the second shared edge node server, depending on the role of the data of the terminal.
In step 1012, middle tier data is stored in the second shared edge node server or the first shared edge node server.
In step 1013, the application layer data is stored in a local database.
As can be seen from the above description, by storing the base layer data in the first shared edge node or the second shared edge node, the storage of the data related to the edge application in the terminal and the base layer data are physically separated; and storing the middle layer data in the second shared edge node or the first shared edge node, so that dynamic data and static data of edge application in the terminal can be physically separated, further, when data is migrated, the base layer data or middle layer data which is not stored in the local database can be rapidly obtained, migration time is shortened, and user experience is prompted.
In some specific implementations, according to the data retrieval result, determining that only application layer data is stored in the local database; determining storage addresses of middle layer data and base layer data, wherein the storage addresses comprise the address of a second shared edge node server or the address of a first shared edge node server; middle layer data and base layer data are retrieved from the memory address.
It should be noted that, the storage address may be one or multiple shared edge node servers, and the data stored at each storage address may include middle layer data and/or base layer data.
According to the analysis, the storage address comprises the address of the second shared edge node server or the address of the first shared edge node server, so that after layering processing is carried out on the data of the terminal, the physical storage addresses are distinguished, the data of the terminal can be stored in different physical spaces, when the data of the terminal are acquired, middle layer data and base layer data can be acquired at the same time, and the data of different layers can be acquired in a time-sharing and space-sharing mode on different storage addresses, so that the mode of acquiring the data of the terminal is more flexible, the migration time is less, the terminal user can be served more quickly and better, and the user experience is greatly improved.
Fig. 2 is a flow chart of a data migration method according to another embodiment of the present invention. The data migration of the terminal is completed by adopting the following steps that the data of the terminal is migrated from the second edge node server to the first edge node server.
In step 201, the user terminal sends a migration request to a first edge node server.
In step 202, the first edge node server looks up a database to determine if base layer data for the terminal is stored.
If it is determined that the base layer data of the terminal is stored in the database, step 205 is executed; otherwise, step 203 is performed.
In step 203, base layer data of the terminal is obtained from the second edge node server.
In step 204, the acquired base layer data of the terminal is synchronized to the first edge node server.
In step 205, the first edge node server searches a database to determine whether middle layer data of the terminal is stored.
If it is determined that the middle layer data of the terminal is stored in the database, executing step 208; otherwise, step 206 is performed.
In step 206, middle tier data for the terminal is obtained from the second edge node server.
In step 207, the acquired intermediate layer data of the terminal is synchronized to the first edge node server.
In step 208, the first edge node server looks up the database and determines whether application layer data for the terminal is stored.
If the application layer data of the terminal is stored in the database, determining that the migration process of the data of the terminal is completed, and ending the data migration; otherwise, step 209 is performed.
In step 209, application layer data of the terminal is obtained from the second edge node server.
In step 210, the acquired application layer data of the terminal is synchronized to the first edge node server.
So far, determining that the application layer data, the middle layer data and the base layer data of the terminal are stored in the database of the first edge node server, and ending the data migration.
In the mode, the data stored in the database of the first edge node server is searched and searched to judge whether the application layer data, the middle layer data and the base layer data of the terminal are stored or not, so that the data of the terminal can be migrated according to the hierarchy, the data amount of migration is reduced, the migration time is saved, and good customer experience is brought to customers.
The above steps of the methods are divided, for clarity of description, and may be combined into one step or split into multiple steps when implemented, so long as they include the same logic relationship, and they are all within the protection scope of this patent; it is within the scope of this patent to add insignificant modifications to the algorithm or flow or introduce insignificant designs, but not to alter the core design of its algorithm and flow.
Fig. 3 is a block diagram of a data migration apparatus in this embodiment, and the specific implementation of the apparatus may be referred to the related description of the above embodiment, and the repetition is omitted. It should be noted that the implementation of the apparatus in this embodiment is not limited to the above examples, and other non-illustrated examples are also within the scope of protection of the apparatus.
The device mainly comprises: the hierarchical storage module 301 is configured to store data of a terminal in a hierarchical manner, where the data of the terminal includes base layer data, middle layer data, and application layer data; the retrieval module 302 is configured to retrieve a local database according to the obtained identifier of the terminal, so as to obtain a data retrieval result; the migration module 303 is configured to migrate data of the terminal according to a data retrieval result.
In one embodiment, the migration module 303 includes: the data retrieval result comprises any one of a first retrieval result, a second retrieval result or a third retrieval result; the first migration submodule is used for acquiring any two of base layer data, middle layer data and application layer data which are not stored in the local database when the data retrieval result is determined to be the first retrieval result, and synchronizing the acquired data to the local database; the second migration submodule is used for acquiring any one of base layer data, middle layer data and application layer data which are not stored in the local database when the data retrieval result is determined to be the second retrieval result, and synchronizing the acquired data to the local database; and the third migration submodule is used for determining that the data migration to the terminal is completed when the data retrieval result is determined to be the third retrieval result.
In this embodiment, the data of the terminal is layered by the layered storage module, and according to the search result obtained by the search module, the migration module can determine which layers of data are stored in the local database, and migrate the data without stored layers.
It should be clear that the invention is not limited to the specific arrangements and processes described in the foregoing embodiments and shown in the drawings. For convenience and brevity of description, detailed descriptions of known methods are omitted herein, and specific working processes of the modules and apparatuses described above may refer to corresponding processes in the foregoing method embodiments, which are not repeated herein.
Fig. 4 shows a schematic diagram of the structure of a data migration system according to an exemplary embodiment of the present invention. In the data migration system, the terminal 401 is initially located in the coverage area of the second edge node server 403, and then moves into the coverage area of the first edge node server 402, so that the terminal 401 initiates a request for data migration to the first edge node server 402, so that the first edge node server 402 can provide services for the terminal 401.
It should be noted that, when the terminal 401 is within the coverage area of the second edge node server 403, the second edge node server 403 only stores the application layer data of the terminal 401 to the local database, and since the middle layer data is independent of the memory status of the user, and is only related to the application scenario, according to the geographical area deployment (such as streets, venues, etc.) of the application scenario, all the edge nodes in the level area share the same storage node, such as the second shared edge node server 404. Thus, the middle layer data of the terminal 401 is saved onto the second shared edge node server 404 to achieve a physical separation of the dynamic data and static data storage of the edge application.
Because the base layer data is independent of the execution of the application, deployed at a large geographic area level (e.g., province, city level), all edge nodes within the level region share the same storage node, i.e., either the first shared edge node server 405 or the second shared edge node server 404. The base layer data of the terminal 401 is saved to the first shared edge node server 405 to achieve physical separation of the edge application and the base layer data storage.
After the terminal 401 initiates a request for data migration to the first edge node server 402, the first edge node server 402 needs to confirm whether each layer of data of the terminal 401 is stored in the local database, that is, whether the base layer data, the middle layer data and the application layer data are stored; and determining which data to obtain specifically according to the search result of the local database, for example, when the search result is that the local database only stores the application layer data of the terminal 401, the second shared edge node server 404 needs to obtain the middle layer data of the terminal 401, the first shared edge node server 405 needs to obtain the base layer data of the terminal 401, and the middle layer data and the base layer data of the terminal 401 are synchronized into the local database, so that migration of each layer data of the terminal 401 to the first edge node server 402 is completed, and the first edge node server 402 can provide corresponding services for the terminal 401.
According to the embodiment of the present invention, the specific working process of the first edge node server 402 may refer to the processing process corresponding to the data migration method described in the foregoing method embodiment, which is not described herein again.
According to the description, the data of each layer of the terminal are stored in the shared edge node server in advance, so that the edge node server can carry out corresponding migration on the data of each layer according to the migration request reported by the terminal, and the migration data quantity and the migration time can be reduced because some data are already stored in the local database.
An electronic device according to an embodiment of the present invention includes: one or more processors; and a storage device having one or more programs stored thereon, which when executed by the one or more processors, cause the one or more processors to implement any one of the data migration methods described above.
The embodiment of the invention relates to a computer readable medium, on which a computer program is stored, which when executed by a processor implements any one of the above-mentioned data migration methods.
The processes described above with reference to flowcharts may be implemented as computer software programs according to embodiments of the present invention. For example, embodiments of the invention include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method shown in the flowchart. In such embodiments, the computer program may be downloaded and installed from a network, and/or installed from a removable storage medium.
Those of ordinary skill in the art will appreciate that all or some of the steps, systems, functional modules/units in the apparatus, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
It is to be understood that the above embodiments are merely illustrative of the application of the principles of the present invention, but not in limitation thereof. Various modifications and improvements may be made by those skilled in the art without departing from the spirit and substance of the invention, and are also considered to be within the scope of the invention.
Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted in a generic and descriptive sense only and not for purpose of limitation. In some instances, it will be apparent to one skilled in the art that features, characteristics, and/or elements described in connection with a particular embodiment may be used alone or in combination with other embodiments unless explicitly stated otherwise. It will therefore be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the scope of the present invention as set forth in the following claims.
Claims (7)
1. A method of data migration, the method comprising:
layering and storing data of a terminal, wherein the data of the terminal comprises basic layer data, middle layer data and application layer data;
searching a local database according to the acquired identification of the terminal to obtain a data searching result; the data retrieval result comprises: any one of the first search result, the second search result, or the third search result; the first search result is that the local database only stores any one of the base layer data, the middle layer data and the application layer data; the second search result is that the local database stores any two of the base layer data, the middle layer data and the application layer data; the third search result is that the local database stores the base layer data, the middle layer data and the application layer data;
and migrating the data of the terminal according to the data retrieval result, wherein the data migration comprises the following steps:
if the data retrieval result is the first retrieval result, any two of the base layer data, the middle layer data and the application layer data which are not stored in the local database are obtained, and the obtained data are synchronized to the local database; if the data retrieval result is the second retrieval result, any one of the base layer data, the middle layer data and the application layer data which are not stored in the local database is obtained, and the obtained data is synchronized to the local database; and if the data retrieval result is the third retrieval result, determining that the data migration to the terminal is completed.
2. The data migration method according to claim 1, wherein the step of acquiring any one of the base layer data, the middle layer data, and the application layer data, which are not stored in the local database, comprises:
and acquiring any one of the base layer data, the middle layer data and the application layer data which are not stored in the local database from an edge data sharing node server.
3. The data migration method according to claim 1, wherein the step of hierarchically storing the data of the terminal includes:
according to the action of the data of the terminal, the base layer data is stored in a first shared edge node server or a second shared edge node server;
storing the middle layer data in the second shared edge node server or the first shared edge node server;
and storing the application layer data in the local database.
4. The data migration method according to claim 3, wherein the step of migrating the data of the terminal according to the data retrieval result includes:
according to the data retrieval result, determining that only the application layer data is stored in the local database;
determining storage addresses of the middle layer data and the base layer data, wherein the storage addresses comprise the address of the second shared edge node server or the address of the first shared edge node server;
and acquiring the middle layer data and the base layer data from the storage address.
5. The data migration method according to any one of claims 1 to 4, wherein the step of retrieving a local database according to the obtained identification of the terminal to obtain a data retrieval result includes:
responding to a migration request sent by the terminal, and obtaining the identification of the terminal;
and searching the data stored in the database by taking the identification of the terminal as an index to obtain the data search result.
6. The data migration method of claim 5, wherein the base layer data comprises:
system data except for the edge application in the data of the terminal, wherein the system data comprises at least one of operating system data, system application and configuration files;
the intermediate layer data includes: static data of the edge application;
the application layer data comprises: dynamic data of the edge application.
7. A data migration apparatus, comprising:
the layering storage module is used for layering and storing data of the terminal, wherein the data of the terminal comprise base layer data, middle layer data and application layer data;
the retrieval module is used for retrieving the local database according to the acquired identification of the terminal to obtain a data retrieval result; the data retrieval result comprises: any one of the first search result, the second search result, or the third search result; the first search result is that the local database only stores any one of the base layer data, the middle layer data and the application layer data; the second search result is that the local database stores any two of the base layer data, the middle layer data and the application layer data; the third search result is that the local database stores the base layer data, the middle layer data and the application layer data;
the migration module is used for migrating the data of the terminal according to the data retrieval result; the migration module includes:
the first migration submodule is used for acquiring any two of the base layer data, the middle layer data and the application layer data which are not stored in the local database when the data retrieval result is determined to be the first retrieval result, and synchronizing the acquired data to the local database; the second migration submodule is used for acquiring any one of the base layer data, the middle layer data and the application layer data which are not stored in the local database when the data retrieval result is determined to be the second retrieval result, and synchronizing the acquired data to the local database; and the third migration submodule is used for determining that the data migration to the terminal is completed when the data retrieval result is determined to be the third retrieval result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010018967.8A CN111274224B (en) | 2020-01-08 | 2020-01-08 | Data migration method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010018967.8A CN111274224B (en) | 2020-01-08 | 2020-01-08 | Data migration method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111274224A CN111274224A (en) | 2020-06-12 |
| CN111274224B true CN111274224B (en) | 2023-04-28 |
Family
ID=70998861
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010018967.8A Active CN111274224B (en) | 2020-01-08 | 2020-01-08 | Data migration method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111274224B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105205154A (en) * | 2015-09-24 | 2015-12-30 | 浙江宇视科技有限公司 | Data migration method and device |
| CN105872053A (en) * | 2016-03-30 | 2016-08-17 | 中国联合网络通信集团有限公司 | Data migration method and system |
| CN106775470A (en) * | 2016-12-08 | 2017-05-31 | 武汉斗鱼网络科技有限公司 | A kind of method and system of data storage |
| CN106775464A (en) * | 2016-12-02 | 2017-05-31 | 郑州云海信息技术有限公司 | A kind of data hierarchy storage system and method |
| CN106790583A (en) * | 2016-12-28 | 2017-05-31 | 江苏盛世华安智能科技股份有限公司 | A kind of city management system for internet of things based on cloud platform |
| CN108388599A (en) * | 2018-02-01 | 2018-08-10 | 平安科技（深圳）有限公司 | Electronic device, Data Migration and call method and storage medium |
| CN110019140A (en) * | 2017-12-29 | 2019-07-16 | 华为技术有限公司 | Data migration method, device, equipment and computer readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9740574B2 (en) * | 2014-05-09 | 2017-08-22 | Commvault Systems, Inc. | Load balancing across multiple data paths |
-
2020
- 2020-01-08 CN CN202010018967.8A patent/CN111274224B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105205154A (en) * | 2015-09-24 | 2015-12-30 | 浙江宇视科技有限公司 | Data migration method and device |
| CN105872053A (en) * | 2016-03-30 | 2016-08-17 | 中国联合网络通信集团有限公司 | Data migration method and system |
| CN106775464A (en) * | 2016-12-02 | 2017-05-31 | 郑州云海信息技术有限公司 | A kind of data hierarchy storage system and method |
| CN106775470A (en) * | 2016-12-08 | 2017-05-31 | 武汉斗鱼网络科技有限公司 | A kind of method and system of data storage |
| CN106790583A (en) * | 2016-12-28 | 2017-05-31 | 江苏盛世华安智能科技股份有限公司 | A kind of city management system for internet of things based on cloud platform |
| CN110019140A (en) * | 2017-12-29 | 2019-07-16 | 华为技术有限公司 | Data migration method, device, equipment and computer readable storage medium |
| CN108388599A (en) * | 2018-02-01 | 2018-08-10 | 平安科技（深圳）有限公司 | Electronic device, Data Migration and call method and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 云计算中虚拟机磁盘迁移时机优化策略;陈睦等;《计算机工程与设计》(第02期);全文 * |
| 银行管理信息系统服务器国产化过程中的ETL应用迁移;张春瑞等;《计算机系统应用》(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111274224A (en) | 2020-06-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106487850B (en) | The methods, devices and systems of mirror image are obtained under a kind of cloud environment | |
| US9628438B2 (en) | Consistent ring namespaces facilitating data storage and organization in network infrastructures | |
| CN106201357A (en) | The construction method of a kind of storage pool and system | |
| CN111246397B (en) | Cluster system, service access method, device and server | |
| CN109714239B (en) | Management message issuing method, VNFM (virtual network management frequency) equipment and server | |
| CN107172214B (en) | Service node discovery method and device with load balancing function | |
| CN107015876B (en) | Service request processing method and device | |
| KR101654314B1 (en) | Distributed processing system in spatial data and method for operating the same | |
| CN113676511A (en) | Cloud storage method, system, equipment and storage medium | |
| US11093477B1 (en) | Multiple source database system consolidation | |
| CN111274224B (en) | Data migration method and device | |
| CN110347656B (en) | Method and device for managing requests in file storage system | |
| CN111600833B (en) | Network operating system and message forwarding method | |
| CN106649528A (en) | Picture writing and reading methods and devices | |
| CN107357691A (en) | The processing method and processing device of image file | |
| CN108090152B (en) | Data synchronization method and system | |
| CN113505111B (en) | Shared directory mounting method and distributed network additional storage system | |
| CN114466031B (en) | CDN system node configuration method, device, equipment and storage medium | |
| CN107547607B (en) | Cluster migration method and device | |
| CN111722783B (en) | Data storage method and device | |
| CN114356575A (en) | User request processing method and device | |
| CN114996236A (en) | Data processing method, device and equipment for converged storage system and storage medium | |
| CN114879907A (en) | Data distribution determination method, device, equipment and storage medium | |
| CN113656496A (en) | Data processing method and system | |
| CN107168645B (en) | Storage control method and system of distributed system |
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 |