WO2014206346A1

WO2014206346A1 - Method and device for synchronizing terminal and server

Info

Publication number: WO2014206346A1
Application number: PCT/CN2014/080993
Authority: WO
Inventors: 陈跃泉
Original assignee: 华为技术有限公司
Priority date: 2013-06-29
Filing date: 2014-06-27
Publication date: 2014-12-31
Also published as: CN103312489B; CN103312489A

Abstract

Disclosed are a synchronization method and device. The method comprises: a server receiving a request for moving a file from a first directory to a second directory, wherein the request carries an identification of the file and an identification of the second directory; the server searching for metadata of the file according to the identification of the file, changing an identification of a parent directory of the file into the identification of the second directory in the metadata of the file, and creating proxy metadata of the file in the first directory, wherein the proxy metadata is used for indicating that the file has been moved to the second directory; and the server sending the proxy metadata of the file to the terminal to conduct synchronization between the server and the terminal through a local file of the terminal. By applying the embodiments of the present invention, the bandwidth consumption is reduced and the synchronization efficiency is increased.

Description

The invention relates to a method and a device for synchronizing a terminal with a server. The application for the application of the method and device for synchronizing the terminal and the server is disclosed in the application No. 201310270933. Priority is hereby incorporated by reference in its entirety. Technical field

The present invention relates to the field of communications technologies, and in particular, to a method and apparatus for synchronizing a terminal with a server. Background technique

With the development of cloud technology, more and more users keep files in the cloud. At present, the cloud supports mobile phones, personal computers (PCs), web pages, and other clients to synchronize with the files in the cloud in real time, ensuring that the user's local data and the cloud data are consistent without user intervention, so that the user can Whenever and wherever you are, you are guaranteed to get the latest data and give the user a good experience.

In the prior art, there are two ways of typical cloud synchronization: full-size synchronization and incremental synchronization. Full-scale synchronization means that when the cloud is updated, the client needs to obtain the full amount of data from the server to the local client, and then compare the local client data with the data obtained from the cloud, obtain the inconsistent data, and finally synchronize the inconsistent data. Among them, obtaining full data from the cloud requires a large amount of user traffic.

Incremental synchronization means that when there is an update in the cloud, the client and the cloud only synchronize the updated data without obtaining all the data. Therefore, the user's traffic can be greatly reduced.

However, existing incremental synchronization is implemented by a combination of copy and delete operations when implementing a move operation. As shown in Figure 1, when the cloud moves the f file in the S directory to the D directory, the prior art first copies the file f to the D directory, generates a new file f, and then deletes the f file in the S directory. The cloud needs to regenerate a new file logical number (logicalFileld) for f. (It should be noted that the cloud uses the file logical number instead of the file name as the unique identifier of the file, because the file name can be renamed at will, resulting in failure to act as The unique identifier of the file). Due to the cloud The end regenerates a new file logical number for the file f, thus causing the sharing, disclosure, and link of the original associated file f to be invalid. Moreover, when the client synchronizes the directory S and the directory D from the cloud, the f file in the S directory of the terminal needs to be deleted, and the file f is downloaded from the cloud to the directory D of the terminal, resulting in waste of network traffic. Summary of the invention

The embodiment of the invention provides a method and a device for synchronizing a terminal with a server to solve the problem of waste of traffic and link failure when the client and the cloud synchronize the mobile operation.

In a first aspect, a terminal synchronizes with a server, including:

The server receives a request to move the file from the first directory to the second directory, the request carrying the identifier of the file and the identifier of the second directory;

The server searches for metadata of the file according to the identifier of the file, and changes a parent directory identifier of the file to an identifier of the second directory in the metadata of the file, and creates the file in the first directory. Proxy metadata of the file, the proxy metadata is used to indicate that the file has been moved to a second directory;

The server sends the proxy metadata of the file to the terminal to perform synchronization between the server and the terminal through the file local to the terminal.

In a first possible implementation manner of the first aspect, the proxy metadata includes an identifier of the file, an identifier of the second directory, and a mobile label indicating that the file has moved;

After the server sends the proxy metadata of the file to the terminal, the method further includes:

Determining, by the terminal, that the file has moved according to a movement flag in the proxy metadata;

Finding metadata of the file locally according to the identifier of the file;

Changing the parent directory identifier of the file to the identifier of the second directory in the metadata of the found file.

In a second possible implementation manner of the first aspect, the method further includes: The metadata of the piece is sent to the terminal;

The terminal updates the first directory in the terminal according to the proxy metadata of the file, and updates the second directory in the terminal according to the metadata of the file.

With reference to the second possible implementation of the first aspect, in a third possible implementation, the metadata of the file includes an identifier of the file and an identifier of the second directory;

Updating the second directory in the terminal according to the metadata of the file specifically includes: the terminal locally searching for metadata of the file according to the identifier of the file in the metadata of the file;

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation, the proxy metadata includes an identifier of the file, an identifier of the second directory, and is used to indicate that the file has occurred Moving move marker

Updating, by the terminal, the first directory specific item in the terminal according to the proxy metadata of the file includes:

Determining the metadata of the file locally according to the identifier of the file in the proxy metadata; determining whether the parent directory identifier of the file in the metadata of the file searching for 'J is an identifier of the second directory;

If the parent directory identifier of the file is not the identifier of the second directory, the file is set to be hidden in the metadata of the found file;

If the parent directory identifier of the file is an identifier of the second directory, the file is not processed.

In conjunction with the fourth possible implementation of the first aspect, in a fifth possible implementation, the terminal locally searches for the element of the file according to the identifier of the file in the metadata of the file. After the data, the method further includes: determining a state of the file, and if the file is in a hidden state, changing the file to a display state in metadata of the file. With reference to the first aspect, or any one of the first to fourth possible implementation manners of the first aspect, in a sixth possible implementation manner, after the server searches for metadata of the file according to the identifier of the file, The method further includes:

Determining, by the server, whether there is proxy metadata indicating that the file has been removed from the second directory under the second directory;

If there is proxy metadata for indicating that the file has been removed from the second directory under the second directory, the proxy metadata is deleted.

In a second aspect, a method for synchronizing a terminal with a server includes:

After the server moves the file from the first directory to the second directory by changing the parent directory identifier of the file in the metadata of the file, and creating the proxy metadata of the file in the first directory, the terminal Receiving proxy metadata of the file from the server, the proxy metadata is used to indicate that the file has been moved to a second directory;

The terminal searches the metadata of the file locally in the terminal according to the proxy metadata, and completes synchronization with the server by using the metadata of the file found locally.

In conjunction with the first possible implementation of the second aspect, the proxy metadata includes an identifier of the file, an identifier of the second directory, and a mobile tag indicating that the file has moved;

The terminal searches the metadata of the file locally in the terminal according to the proxy metadata, and completes synchronization with the server by using the metadata of the file found locally:

Finding metadata of the file locally according to the identifier of the file;

With reference to the second possible implementation manner of the second aspect, the performing the synchronization with the server by using the metadata of the file that is locally found specifically includes:: metadata of the file that is found locally Completing the first directory in the terminal and the first in the server Synchronization of a directory;

The method further includes:

Receiving, by the terminal, metadata of the file from the server;

The terminal completes synchronization of the second directory in the terminal with the second directory in the server according to the received metadata of the file.

With reference to the second possible implementation of the second aspect, in a third possible implementation, the metadata of the file received from the server includes an identifier of the file and a second directory Identification

The synchronizing the second directory in the terminal with the second directory in the server according to the metadata of the file includes:

The terminal locally searches for metadata of the file according to the identifier of the file in the received metadata of the file;

With reference to the third possible implementation manner of the second aspect, in a fourth possible implementation, the proxy metadata includes an identifier of the file, an identifier of the second directory, and is used to indicate that the file has occurred Moving move marker

The terminal searches the metadata of the file locally in the terminal according to the proxy metadata, and completes the first directory in the terminal and the first in the server by using the metadata of the file found locally. The synchronization of the directory specifically includes:

If the parent directory identifier of the file is an identifier of the second directory, the file is not deal with.

With reference to the fourth possible implementation of the second aspect, in a fifth possible implementation, the terminal finds the element of the file locally according to the identifier of the file in the metadata of the file. After the data, the method further includes: determining a state of the file, and if the file is in a hidden state, changing the file to a display state in metadata of the file.

A third aspect, a server that synchronizes with a terminal, the server includes: a receiving unit, configured to receive a request for moving a file from a first directory to a second directory, where the request carries an identifier and a location of the file The identifier of the second directory;

a processing unit, configured to search for metadata of the file according to the identifier of the file, change a parent directory identifier of the file to an identifier of the second directory in the metadata of the file, and in the Creating a proxy metadata of the file in a directory, the proxy metadata is used to indicate that the file has been moved to the second directory;

And a synchronization unit, configured to send proxy metadata of the file to the terminal, to perform synchronization between the server and the terminal by using the file local to the terminal.

In a first possible implementation manner of the third aspect, the synchronization unit is further configured to send metadata of the file to the terminal, and proxy metadata of the file is used to synchronize the first directory, where The metadata of the file is used to synchronize the second directory.

With reference to the third aspect, or the first possible implementation manner of the third aspect, in a second possible implementation manner, the processing unit, when changing a parent directory identifier of the file to an identifier of the second directory And further determining whether there is proxy metadata for indicating that the file has been removed from the second directory under the second directory; if the second directory exists to indicate that the file has been The proxy metadata removed by the second directory deletes the proxy metadata under the second directory.

A fourth aspect, a terminal for synchronizing with a server, comprising: a synchronization unit, configured to move the file from a first directory to a first manner by changing a parent directory identifier of the file in metadata of a file After the second directory, and the proxy metadata of the file is created in the first directory, the proxy metadata of the file is received from the server and provided to the processing unit, where the proxy metadata is used to indicate that the file has been Move to the second directory; The processing unit is configured to search for metadata of the file locally in the terminal according to the proxy metadata, and complete synchronization with the server by using metadata of the file found locally.

In a first possible implementation manner of the fourth aspect, the proxy metadata includes an identifier of the first file, an identifier of the second directory, and a mobile tag used to indicate that the file has moved; The movement has occurred; the metadata of the file is locally searched according to the identifier of the file; the parent directory identifier of the file is changed to the identifier of the second directory in the found metadata of the file.

In a second possible implementation manner of the fourth aspect, the synchronization unit is further configured to receive metadata of the file from the server;

The processing unit specifically includes:

a first operation module, configured to search for metadata of the file locally in the terminal according to the proxy metadata, and complete the local first directory and the first in the server by using the metadata of the file locally found Synchronization of a directory;

And a second operation module, configured to complete synchronization of the local second directory with the second directory in the server according to the received metadata of the file.

With reference to the second possible implementation of the fourth aspect, in a third possible implementation, the metadata of the file received from the server includes an identifier of the file and a second directory Identification

The second operation module is specifically configured to locally search for metadata of the file according to the identifier of the file in the metadata of the received file, where the metadata of the file is found The parent directory ID of the file is changed to the identity of the second directory.

With reference to the third possible implementation manner of the fourth aspect, in a fourth possible implementation, the proxy metadata includes an identifier of the file, an identifier of the second directory, and is used to indicate that the file has occurred Moving move marker

The first operation module is specifically configured to determine, according to the mobile tag in the proxy metadata The file has been moved; the metadata of the file is locally searched according to the identifier of the file in the proxy metadata; determining whether the parent directory identifier of the file in the metadata of the found file is the An identifier of the second directory; if the parent directory identifier of the file is not the identifier of the second directory, the file is set to be hidden in the metadata of the found file; if the parent directory of the file The identifier is an identifier of the second directory, and the file is not processed.

With reference to the third possible implementation manner of the fourth aspect, in a fourth possible implementation, the second operating module is further configured to determine a state of the file after the metadata of the file is found, If the file is in a hidden state, the file is changed to a display state in the metadata of the file.

In the embodiment of the present invention, the server moves the file from the source directory to the destination directory by changing the parent directory of the file, and creates proxy metadata for the file that has been moved to the target directory in the source directory, so that the terminal is in the synchronization source directory and In the target directory, it can be recognized that the mobile side operates on the server side, so that the local file is used to synchronize with the server without re-downloading the file from the server side, thereby saving network resources. Moreover, the present invention moves the file from the source directory to the destination directory by changing the parent directory of the file, so that the logical number of the file remains unchanged, so that the shared, public, and external links of the original associated file f can remain valid. DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. One of ordinary skill in the art can also obtain other drawings based on these drawings without undue creative effort.

1 is a flow chart of a synchronization method in the prior art;

2 is a flowchart of a method for synchronizing a terminal and a server according to an embodiment of the present invention; FIG. 3 is a flowchart of a method for synchronizing a terminal and a server according to another embodiment of the present invention; FIG. a schematic diagram of the movement of f; FIG. 6 is a schematic diagram of a network architecture according to an embodiment of the present invention;

7 is a schematic structural diagram of a server that synchronizes with a terminal according to an embodiment of the present invention; FIG. 8 is a schematic structural diagram of a server that synchronizes with a terminal according to another embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a terminal synchronized with a server according to another embodiment of the present invention; FIG.

FIG. 10 is a schematic structural diagram of a terminal synchronized with a server according to another embodiment of the present invention; FIG.

FIG. 11 is a schematic diagram showing the hardware structure of a server synchronized with a terminal according to an embodiment of the present invention;

FIG. 12 is a schematic diagram showing the hardware structure of a terminal synchronized with a server according to another embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 2 is a flowchart of a method for synchronizing a terminal and a server according to an embodiment of the present invention, where the method includes:

S200. The server receives a request for moving a file from a first directory to a second directory, where the request carries an identifier of the file and an identifier of the second directory. The server may be a cloud synchronization server, configured to provide a cloud synchronization service, and synchronize files on multiple terminals of the user. In a plurality of terminals synchronized by the user and the server, if the file in one of the terminals moves from the first directory to the second directory, the terminal initiates a request to move the file from the first directory to the second directory to the server, to Causes the server to perform a move operation based on the request and synchronize the user's other terminals through the server.

Optionally, the request in step S200 may also be sent by the user to the server through the web client, so that the server performs the mobile operation according to the request, and then synchronizes from the server to all or part of the user's terminal.

The request received by the server carries the identifier of the file to be moved and the identifier of the target directory of the file. In this embodiment, the source directory of the file to be moved is the first directory, and the target directory is the second directory, so the request received by the server needs to carry the identifier of the second directory. The identifier of the source directory of the file may or may not be carried.

S202. The server searches for metadata of the file according to the identifier of the file carried in the request, changes the parent directory identifier of the file to the identifier of the second directory in the metadata of the file, and creates the file in the first directory. The proxy metadata, where the proxy metadata is used to indicate that the file has been moved to the second directory.

After the server recognizes that the received request is a request to perform a move operation, the server performs the operation of step S202. The server may determine the received request as a request to perform a move operation according to the name of the request or the type of operation specified in the request. The request can use the mobile operation request in the prior art, and will not be described here.

It should be noted that the attributes of a file are usually defined by the metadata of the file. For example, the ownership of files and directories can be defined by the parent directory entry in the metadata of the file.

In the embodiment of the present invention, after receiving the request to move the file to the second directory, the server may The metadata of the file corresponding to the file identifier is searched according to the file identifier carried in the request, and the parent directory identifier of the file is changed to the identifier of the second directory in the metadata of the file. In addition, the server also needs to create proxy metadata for the file in the source directory of the file (ie, under the first directory) to indicate that the file has been moved to the second directory by the proxy metadata when the first directory is synchronized with the terminal. . The proxy metadata of the file may be composed of the metadata of the file plus the mobile tag, or the partial data in the metadata of the file plus the mobile tag. Wherein, the move marker is used to indicate that the file has moved. In general, the metadata of a file can include attributes such as the identifier of the file, the parent directory identifier of the file, and so on. In this embodiment, since the file has been moved to the target directory (ie, the second directory), the proxy metadata of the file may include the identifier of the file, the identifier of the second directory, and the mobile tag.

S204. The server sends the proxy metadata of the file to the terminal, so as to synchronize between the server and the terminal through the file local to the terminal.

It should be noted that the synchronization in the embodiment of the present invention may be full synchronization or partial synchronization, and the terminal and the server may synchronize the first directory and the second directory respectively. After determining the directory to be synchronized, the server detects the update data from the last synchronization in the directory to be synchronized, and transmits the detected update data to the terminal. For example, in this embodiment, when the server and the terminal synchronize the first directory, the server detects the update data of the first directory during the current synchronization and the last synchronization, and when determining that the update data includes the proxy metadata of the file, the first The proxy metadata of the file under the directory is sent to the terminal.

After receiving the proxy metadata returned by the server, the terminal may learn the received metadata as the proxy metadata of the file according to the mobile tag in the proxy metadata, and then update the local file according to the proxy metadata to complete the server. Synchronization between. It should be noted that the synchronization between the server and the terminal can be initiated by the terminal. The server can determine the directory to be synchronized according to the synchronization request sent by the terminal.

The embodiment of the present invention moves the file from the first directory to the second directory by changing the parent directory of the file, and creates proxy metadata for the file that has been moved to the second directory in the first directory, so that the terminal is synchronized first. When the directory is used, the agent metadata indicating that the file is moved may be sent to the terminal, and the terminal may identify, by the agent metadata, that a mobile operation occurs on the server side, thereby completing synchronization with the server through the file local to the terminal, without The server side re-downloads files, saving network resources. Moreover, the present invention moves the file from the source directory to the destination directory by changing the parent directory of the file, so that the logical number of the file remains unchanged, so that the shared, public, and external links of the original associated file f remain valid.

In an embodiment of the present invention, after receiving the proxy metadata sent by the server, the terminal may perform the following processing: the terminal determines, according to the mobile tag in the proxy metadata, that the file has moved; according to the file identifier carried in the proxy metadata. Find the metadata of the file locally; change the parent directory identifier of the file to the identifier of the second directory in the metadata of the file found.

In the above embodiment, the terminal directly changes the parent directory of the file to the second directory by locally finding the file corresponding to the proxy metadata, so that the file is locally moved between the directories without downloading from the server. Files, but still synchronized with the server.

The above embodiment describes the synchronization process of completing the file moving operation in the process of the terminal synchronizing the first directory with the server after the server moves the file from the first directory to the second directory.

In another embodiment of the present invention, the terminal may update the first directory in the terminal according to the proxy metadata of the file, or update the second directory during the synchronization process on the second directory. Specific On the basis of the embodiment shown in FIG. 2, the embodiment may further include: the server transmitting the metadata of the file to the terminal; the terminal updating the first directory in the terminal according to the proxy metadata of the file, and according to the The metadata of the file updates the second directory in the terminal.

When the terminal and the server synchronize the second directory, the server detects the update data of the second directory during the current synchronization and the last synchronization, and when determining that the update data includes the metadata of the file moved to the second directory, The metadata of the file is sent to the terminal.

The metadata of the file may include an identification of the file and an identification of the second directory. The updating, by the terminal, the second directory in the terminal according to the metadata of the file may include: the terminal locally searching for metadata of the file according to the identifier of the file carried in the metadata of the file sent by the server; and finding the metadata of the file in the file. Change the parent directory ID of the file to the ID of the second directory carried in the metadata of the received file.

The updating, by the terminal, the first directory in the terminal according to the proxy metadata of the file may include: the terminal locally searching for metadata of the file according to the file identifier carried in the proxy metadata; determining the parent of the file in the metadata of the found file. Whether the directory identifier is the identifier of the second directory carried in the proxy metadata; if the parent directory identifier of the file is not the identifier of the second directory, the file is set to be hidden in the metadata of the found file; if the file The parent directory identifier is the identifier of the second directory, and the file is not processed.

In a specific implementation, the terminal may first initiate synchronization of the first directory, and may also initiate synchronization of the second directory. When the terminal first synchronizes the first directory, if the terminal determines that the file in the first directory is moved to the second directory according to the proxy metadata returned by the server, the terminal may directly change the parent directory in the metadata of the file. The file is moved to the second directory, and the file in the first directory can also be set to be hidden without deleting the file. Among them, the file Set to hidden, in order to improve the user experience, so as not to change the second directory in the terminal when the terminal has not synchronized the second directory. Moreover, setting the file to be hidden can not only enable the terminal to find the file when synchronizing the second directory, but also without re-downloading the file from the server. Moreover, in the user's view, the first directory of the terminal and the file in the first directory of the server can also be consistent.

It should be noted that, if the terminal uses the method of changing the parent directory of the file when synchronizing the first directory, the operation does not conflict with the operation when the second directory is synchronized, but is executed twice in the metadata of the file. The same operation. Of course, in order to reduce duplication, when synchronizing the first directory or the second directory, it is possible to first determine whether the parent directory of the file has been changed to the second directory, and if it has been changed, there is no need to perform the changed operation.

If the terminal uses the method of setting the file to be hidden when the first directory is synchronized, the terminal may further include the following steps when synchronizing the second directory: after the terminal searches for metadata of the file to be synchronized, the terminal determines the status of the file. If the file is hidden, the file is further changed to the display state in the metadata of the file.

In the embodiment of the present invention, the file is moved from the source directory to the destination directory by changing the parent directory of the file, and the proxy metadata is created in the source directory for the file that has been moved to the target directory, so that the terminal is in the synchronization source directory and When the target directory is located, it can be recognized that the mobile operation occurs on the server side, so that the mobile terminal performs the local operation according to the mobile operation without saving the file from the server side, thereby saving network resources. Moreover, the present invention moves the file from the source directory to the destination directory by changing the parent directory of the file, so that the logical number of the file remains unchanged, so that the shared, public, and external links of the original associated file f can remain valid.

When the solution provided by the embodiment of the present invention is specifically implemented, the following may exist: The user first moves the file f from the S directory to the D directory, and then moves the file f from the D directory back to the S directory. In this case, according to the solution provided by the embodiment of the present invention, when the file f is moved from the D directory back to the S directory again, the proxy metadata of the file f already exists under the S directory, in which case the proxy element Data is no longer necessary. Therefore, in another embodiment of the present invention, when the server in step S102 changes the parent directory identifier of the file to the identifier of the second directory, the server may further include the following processing: determining whether the second directory exists for The proxy metadata indicating that the file has been removed from the second directory; if there is proxy metadata indicating that the file has been removed from the second directory under the second directory, the proxy metadata is deleted.

In addition, in order to save storage resources, in another embodiment of the present invention, the server may also periodically clear the proxy metadata. Specifically, the server may set a time limit for the proxy metadata, and the server deletes the expired proxy metadata in the server according to the preset time limit.

In another possible embodiment, after the data update occurs, the server may further send an update notification to the terminal that is synchronized with the server, that is, after step S202, the method may further include: sending the first directory and the terminal synchronized with the server. An update notification of the second directory, so that the terminal initiates a request to synchronize the first directory or the second directory according to the update notification.

The terminal synchronized with the server refers to the terminal that the user has registered with the server and established a connection with the server. The user here refers to the user to which the updated file belongs. It should be noted that if the server initiates a request to move the file from the first directory to the second directory by one of the user's terminals in step S200, the server may not initiate the request when sending the update notification. The terminal sends an update notification.

The embodiment of the present invention is further described from the terminal side. As shown in FIG. 3, FIG. 3 is a flowchart of a method for synchronizing according to another embodiment of the present invention, where the method includes: S300, moving the file from the first directory to the second directory by changing a parent directory identifier of the file in metadata of the file, and creating proxy metadata of the file in the first directory After that, the terminal receives the proxy metadata of the file created by the server in the first directory from the server, and the proxy metadata is used to indicate that the file has been moved to the second directory.

After the server moves the file from the first directory to the second directory, the server creates the proxy metadata for the file in the first directory. When the server synchronizes with the terminal for the first directory, the update data of the first directory since the last synchronization is detected. Because the proxy metadata for the file is added to the first directory between this synchronization and the last synchronization. When the server detects the update data, it detects the proxy metadata of the file and sends the proxy metadata of the file as update data to the terminal.

S302. The terminal searches for metadata of the file locally in the terminal according to the proxy metadata, and completes synchronization with the server by using metadata of the file found locally.

The proxy metadata may include an identifier of the file, an identifier of the second directory, and a mobile tag. The mobile tag is used to indicate that the file has moved, and the target directory after the terminal receives the update data, that is, the current parent directory of the file.

Specifically, the terminal searches the metadata of the file locally in the terminal according to the proxy metadata, and completes synchronization with the server by using the metadata of the file found locally. The method may include: determining, by the terminal, the file according to the mobile tag in the proxy metadata. The movement has occurred; the metadata of the file is found locally according to the identifier of the file, and the parent directory identifier of the file is changed to the identifier of the second directory in the metadata of the file found.

The above embodiment describes that after the server moves the file from the first directory to the second directory, In the process of synchronizing the first directory with the server, the synchronization process of the file moving operation is completed. In another embodiment of the present invention, after the terminal receives the proxy metadata of the file, the terminal may update the first directory in the terminal only according to the proxy metadata, and update the second directory during the synchronization process of the second directory. . Specifically, the step of completing the synchronization with the server by using the metadata of the file that is locally found in step 302 may include: completing the metadata in the terminal by using the metadata of the file that is locally found. The first directory is synchronized with the first directory in the server. On the basis of the embodiment shown in FIG. 3, the embodiment may further include: the terminal receiving metadata of the file from the server, and the terminal completing the second directory in the terminal and the second in the server according to the received metadata of the file. Synchronization of the directory.

The metadata of the file may include an identification of the file and an identification of the second directory. The terminal may complete the synchronization of the second directory in the terminal with the second directory in the server according to the received metadata of the file. The terminal may include: searching, by the terminal, the file according to the identifier of the file carried in the metadata of the received file. Metadata; in the metadata of the file found, the parent directory identifier of the file is changed to the identifier of the second directory carried in the metadata of the received file.

The agent metadata of the file may include an identification of the file, an identification of the second directory, and a mobile tag indicating that the file has moved. The terminal searches for the metadata of the file in the terminal according to the proxy metadata of the file, and completes the synchronization between the first directory in the terminal and the first directory in the server by using the metadata of the file found locally. The terminal may specifically include: Finding the metadata of the file locally according to the file identifier carried in the proxy metadata; determining the found In the metadata of the file, the parent directory identifier of the file is the identifier of the second directory carried in the proxy metadata; if the parent directory identifier of the file is not the identifier of the second directory, the metadata of the found file will be The file is set to be hidden; if the parent directory identifier of the file is the identifier of the second directory, the file is not processed.

In a specific implementation, the terminal may initiate synchronization of the first directory first, and may also initiate synchronization of the second directory. When the terminal first synchronizes the first directory, if the terminal determines that the file in the first directory is moved to the second directory according to the proxy metadata returned by the server, the terminal may directly change the parent directory in the metadata of the file. The file is moved to the second directory, and the file in the first directory can also be set to be hidden without deleting the file. The file is set to be hidden to improve the user experience, so that the second directory in the terminal is changed when the terminal has not synchronized the second directory. Moreover, setting the file to be hidden can not only enable the terminal to find the file when it synchronizes the second directory, but does not have to re-download the file from the server. Moreover, in the user's view, the first directory of the terminal and the file in the first directory of the server are also consistent.

If the terminal synchronizes the second directory first, when the terminal synchronizes the first directory, the case where the parent directory identifier of the file has been changed to the identifier of the second directory occurs. Therefore, when the terminal determines that the parent directory identifier of the first file is the identifier of the second directory, the file is not processed.

If the terminal synchronizes the first directory first, there may be cases where the file is set to the hidden state. Therefore, when receiving the metadata of the file, the terminal may further determine whether the file is set to be hidden. If it is set to hide the state, the file is changed to the display state. If it is not set to the hidden state, no change is needed. The status of the file.

In the embodiment of the present invention, the server changes the file from the first directory by changing the parent directory of the file. The directory is moved to the second directory, and the proxy metadata is created in the first directory for the file that has been moved to the second directory, so that when the terminal synchronizes the first directory with the server, the server can send the proxy metadata indicating that the file is moved. To the terminal, the terminal can identify, by the proxy metadata, that a mobile operation occurs on the server side, thereby completing synchronization with the server through the local file of the terminal, without re-downloading the file from the server side, thereby saving network resources. Moreover, the present invention moves the file from the source directory to the destination directory by changing the parent directory of the file, so that the logical number of the file remains unchanged, so that the shared, public, and external links of the original associated file f can remain valid. The server sends a synchronization request as an example. Assume that terminal A and terminal B are two terminals that keep the user synchronized with the cloud server. The file to be moved is f, the source directory of file f is S, and the target directory is 0. As shown in FIG. 4, FIG. 4 is a flowchart of a synchronization method according to the embodiment, where the method specifically includes:

S400, terminal A moves the file f in the local source directory S to the target directory D.

In this embodiment, a file shift occurs in one of a plurality of terminals synchronized by the user and the server as an example. If the user uses the web client to operate the cloud server for file movement, step S400 may be omitted.

The attribution relationship between the file f and the directory can be described by the metadata of the file f. The data structure of the metadata of the file f is as shown in Table 1:

Table 1

The file identifier can be represented by the logical number of the file generated by the system. The data structure of the metadata shown in Table 1 is only an example, and may include other attributes or only tables in specific applications.

Part of the properties in 1.

S402. Terminal A sends a request to move the file f from the directory S to the directory D to the cloud server.

The request may include an account of the user, an identifier of the file f, an identifier of the target directory D, and an operation type. In this embodiment, the operation type is a mobile operation.

S404, the server creates the proxy metadata f, in the source directory S, and modifies the parent directory of the file f to the target directory D in the metadata of the file f.

The server obtains the data stored by the user in the cloud according to the account of the user carried in the received request. Find the metadata of file f in the user's data, and modify the parent directory of file f to the target directory D in the metadata of file f. As shown in Fig. 5, Fig. 5 is a schematic diagram of the movement of the file f. Before moving the directory A below the active directory S and the target directory D, the source directory S has a file f below. After the move, the source directory of the file f is stored under the source directory S, and the file f is located under the directory D.

The data structure of the metadata of the moved file f is as shown in Table 2:

Table 2

The data structure of the proxy metadata 文件 of file f is shown in Table 3: table 3

In the process of moving the file, it is possible that the proxy metadata f of the file f already exists in the directory D. Therefore, the server may also first check whether there is proxy metadata of the file f under the target directory D; if not, directly execute step S404; if there is proxy metadata of the file f under the target directory D, the server further deletes the target. The proxy metadata of the file f under the directory D, and step S404 is performed.

S406. The server pushes an update notification to the terminal B that the user synchronizes with the server.

The terminal may initiate a request to synchronize the first directory to the server, or may initiate a synchronization request according to an update notification sent by the server about the first directory. This embodiment is described by taking an example in which the server sends an update notification to the terminal.

When the user has multiple terminals synchronized with the server, the server can maintain the connection of the user's various online terminals. After the server detects that the user's data has been updated, it can send an update notification to each synchronization terminal that the user has connected to the server. When the update notification is initiated, it may no longer be sent to the terminal A initiating the mobile request.

The server may separately send an update notification of the source directory S and the target directory D, or may notify the update of the source directory S and the target directory D with an update notification.

S408. The terminal B initiates a synchronization request for synchronizing the directory S to the server.

The synchronization request carries the identifier of the directory S and the synchronization token ring syncToken, and the synchronization token ring syncToken is used to indicate the serial number of each synchronization.

S41 0, the server detects the update data in the directory S, and detects the update data as the file f. When proxy metadata, the proxy metadata is returned to the terminal.

After receiving the request of the synchronization directory S initiated by the terminal B, the server returns the metadata of the newly added or modified file in the directory S. Specifically, the server detects all the update data from the source directory S since the last syncToken according to the syncToken requested by the terminal B, and simultaneously generates a new syncToken to perform the synchronizationTo the next time the terminal synchronizes, and finally the server returns the update data. And the new s yncToken.

Assume that when the user initiates synchronization of directory S and directory D, the syncToken carried is

20121128000000, the server detects the update data of the source directory S since 20121128000000 as the proxy metadata of the file Γ , returns the update data under the source directory S, and sets the new syncToken to 20121128120000.

S412, terminal B sets the local file f to be hidden according to the proxy metadata returned by the server.

After receiving the update data returned by the server, terminal B determines that the file f has been removed from the directory S based on the movement flag in the data. Terminal B finds the metadata of file f locally, and sets file f to be hidden in the metadata of file f. Specifically, the data structure of the metadata of the file f set to be hidden is as shown in Table 4:

Table 4

After the file f is set to be hidden, the file f will not appear under the directory S, so that the directory S remains synchronized with the cloud. At the same time, it avoids deleting the file f, so that the subsequent directory is synchronized.

When D, the file f can be directly moved to the directory D. Of course, the terminal B can also change the parent directory of the file f to the directory D without setting the file f to be hidden, so that the file f can also be removed from the directory S. However, when the user only selectively synchronizes the directory S without synchronizing the directory D, this method causes the directory D to also change, affecting the user experience.

This embodiment is described by taking the file f as hidden as an example.

S414. The terminal B initiates a synchronization request for synchronizing the directory D to the server.

The synchronization request carries the identifier of the directory D and the synchronization token ring syncToken.

S41 6: The server detects the update data in the directory D, and when detecting the update data as the metadata of the file f, returns the metadata of the file f to the terminal.

For the process of detecting the update data by the server, refer to the description in step S41 0, which is not described here.

S41 8 , terminal B changes the parent directory of the local file f to the directory D according to the metadata of the server returning the file f.

After receiving the metadata of the file f, the terminal B finds that the parent directory of the file f is changed to the directory D, and then searches for the metadata of the local file f, and changes the parent directory of f to the directory D in the found metadata. In addition, the terminal B further judges the state of the file f. If the file f has been set to the hidden state, the terminal B further changes the state of the file f to the display state.

It should be noted that there is no sequence between the above steps S408-S41 2 and steps S414-S41 8 , and terminal B may synchronize the directory S first, or may synchronize the directory D first.

The foregoing method embodiment can be applied to the synchronization between the cloud server and the terminal. The network architecture for implementing the synchronization is as shown in FIG. 6, and may include: a client, a synchronization server, and a push server.

Wherein, the synchronization server and the push server are both located in the cloud, and the two can be combined in one object. In the device. The server in the embodiment of the present invention is a combination of the synchronization server and the push server in the cloud. However, in the embodiment of the present invention, the push server may be optional. In the embodiment that does not require the push server, the embodiment of the present invention is The so-called server refers to the synchronization server.

The client runs on the user terminal to synchronize between the terminal and the synchronization server. The client and the sync server can communicate via the HTTP protocol. In addition, the client can connect to the push server through registration to receive messages pushed by the push server. The client and push server can establish a connection via HTTP or XMPP.

The interaction process between devices in the above network architecture is as follows: The client in the terminal first establishes a connection with the push server. When the synchronization server detects a data update, the synchronization server sends an update notification to the push server. The push server pushes the update notification to the client in the terminal. The client initiates synchronization with the synchronization server based on the update notification.

The structure of each device in the above network structure will be described in detail below. As shown in FIG. 7, FIG. 7 is a schematic structural diagram of a server 700 that synchronizes with a terminal according to an embodiment of the present invention. The server 700 is a device that implements a function of a cloud. The server 700 can include:

The receiving unit 701 is configured to receive a request to move the file from the first directory to the second directory, and the identifier of the file and the identifier of the second directory in the request;

The processing unit 702 is configured to search for metadata of the file according to the identifier of the file received by the receiving unit 701, and change the parent directory identifier of the file to the identifier of the second directory in the metadata of the file, and at the first The proxy metadata of the file is created under the directory, and the proxy metadata is used to indicate that the file has been moved to the second directory;

The synchronization unit 703 is configured to send the proxy metadata of the file to the terminal to perform synchronization between the server and the terminal through the file local to the terminal. The request received by the receiving unit 701 carries the identifier of the file that needs to be moved and the identifier of the target directory of the file. In this embodiment, the source directory of the file to be moved is the first directory, and the target directory is the second directory, so the request received by the server needs to carry the identifier of the second directory. The identifier of the source directory of the file may or may not be carried.

After receiving the request to move the file, the processing unit 702 may determine the received request as a request to perform the move operation according to the name of the request or the type of operation specified in the request. When the processing unit 702 changes the parent directory identifier of the file to the identifier of the second directory, it is further used to determine whether there is proxy metadata for indicating that the file has been removed from the second directory in the second directory; The proxy metadata for indicating that the file has been removed from the second directory exists under the second directory, and the proxy metadata under the second directory is deleted.

The synchronization unit 703 detects the update data since the last synchronization in the directory to be synchronized, and transmits the detected update data to the terminal. For example, in this embodiment, when the first directory is to be synchronized with the terminal, the synchronization unit 703 detects the update data of the first directory during the current synchronization and the last synchronization, and when determining that the update data includes the proxy metadata, The proxy metadata in a directory is sent to the terminal. When the second directory is to be synchronized, the synchronization unit 703 detects the update data of the second directory during the current synchronization and the last synchronization, and when determining that the update data includes the metadata of the file moved to the second directory, The metadata of the file is sent to the terminal.

In the embodiment of the present invention, the file is moved from the source directory to the destination directory by changing the parent directory of the file, and the proxy metadata is created in the source directory for the file that has been moved to the target directory, so that the terminal is in the synchronization source directory and When the target directory is located, it can be recognized that the mobile operation occurs on the server side, so that the mobile terminal performs the local operation according to the mobile operation without saving the file from the server side, thereby saving network resources. Moreover, the present invention converts the file by changing the parent directory of the file. Moving from the source directory to the destination directory keeps the logical number of the file unchanged, so that the shared, public, and external links of the original associated file f remain valid.

In addition, in order to save storage resources, in another embodiment of the present invention, proxy metadata may also be periodically cleared. As shown in FIG. 8, FIG. 8 is a schematic structural diagram of a server 700 for synchronizing with a terminal according to another embodiment of the present invention. The server 700 further includes: a maintenance unit 704, based on the embodiment shown in FIG. Used to delete the expired agent metadata in the server according to the preset time limit.

In addition, the server may further include: a notification unit 705, configured to send, to the terminal synchronized with the server, an update notification of the first directory and the second directory, so that the terminal is configured according to the The update notification initiates a request to synchronize the first directory or the second directory.

The specific implementation of the functions of the units in the embodiment shown in FIG. 7 and FIG. 8 can be referred to the method embodiment, and details are not described herein again.

A terminal 900 synchronized with a server according to another embodiment of the present invention is shown in FIG. The terminal 900 can include:

The synchronization unit 901 is configured to move the file from the first directory to the second directory by changing the parent directory identifier of the file in the metadata of the file, and create proxy metadata of the file in the first directory. After receiving the proxy metadata of the file from the server, and providing it to the processing unit 902, where the proxy metadata is used to indicate that the file has been moved to the second directory; the processing unit 902 is configured to use the proxy metadata according to the proxy metadata The metadata of the file is locally looked up, and the synchronization with the server is completed by the metadata of the file found locally.

Wherein, the proxy metadata may include an identifier of the file, an identifier of the second directory, and a moving target Remember. The mobile tag is used to indicate that the file has moved, and the target directory when the terminal receives the update data movement, that is, the current parent directory of the file.

The processing unit 902 is specifically configured to determine, according to the mobile tag in the proxy metadata, that the file has moved; searching for metadata of the file locally according to the identifier of the file; and searching for the file in the metadata of the file The parent directory ID is changed to the ID of the second directory.

In another embodiment of the present invention, the synchronization unit 901 is further operable to receive metadata of the file from the server. In this embodiment, the specific structure of the processing unit 902 may be as shown in FIG. 10, and the processing unit 902 may specifically include:

The first operation module 9021 is configured to search for metadata of the file locally in the terminal according to the proxy metadata, and complete synchronization of the first directory in the local directory with the first directory in the server by using the metadata of the file locally found;

The second operation module 9022 is configured to complete synchronization of the local second directory with the second directory in the server according to the metadata of the received file.

The metadata of the file received by the synchronization unit 901 from the server may include an identifier of the file and an identifier of the second directory. The second operation module 9022 is specifically configured to locally search for metadata of the file according to the identifier of the file in the metadata of the received file; change the parent directory identifier of the file in the found metadata of the file. The identifier for the second directory.

The first operation module 9021 is specifically configured to determine, according to the mobile tag in the proxy metadata, that the file has moved; to find the metadata of the file locally according to the identifier of the file in the proxy metadata; and determine the found element of the file. Whether the parent directory identifier of the file in the data is the identifier of the second directory; if the parent directory identifier of the file is not the identifier of the second directory, the found The file is set to be hidden in the metadata of the file; if the parent directory identifier of the file is the identifier of the second directory, the file is not processed.

In addition, the second operation module 9022 is further configured to determine a state of the second file after the metadata of the file is found, and if the second file is in a hidden state, change the second file to the metadata of the second file to Display state.

The terminal 900 shown in FIG. 10 may initiate a request for synchronizing the first directory to the server, or may initiate a synchronization request according to the update notification sent by the server regarding the first directory. In the embodiment of receiving the update notification, the synchronization unit 901 in the terminal 900 shown in FIG. 10 is further configured to establish a connection with the server, and after the server moves the file from the first directory to the second directory, the receiving server sends the Update notification for a directory and a second directory.

The specific implementation of the functions of the units in the embodiment shown in FIG. 9 and FIG. 10 can be referred to the method embodiment, and details are not described herein again.

It should be noted that the server 700 in the embodiment shown in FIG. 7 and FIG. 8 can be implemented based on the hardware structure of the computer. As shown in FIG. 11, the hardware structure of the device 700 includes a memory 1101, a transceiver 1102, and processing. The device 1103 and the bus 1104.

The processor 1103, the memory 1101, and the transceiver 1102 are communicably connected by a bus 1104.

The memory 1101 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1101 can store instructions of the operating system and other applications as well as application data. The instructions stored in the memory 1101 are executed by the processor 1103.

The memory 1101 in the embodiment of the present invention can be used to store and implement the implementation shown in FIG. 7 and FIG. 8. The instructions for each functional unit in the example.

Transceiver 1102 is used to enable communication between device 700 and other devices.

In the embodiment of the present invention, the transceiver 1102 is configured to receive a message from a terminal and send a message to the terminal.

The processor 1103 can use a general-purpose central processing unit (CPU), a processor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs.

In the embodiment of the present invention, the processor 1103 is configured to execute the instructions in the memory 1101, and the steps in the method embodiment shown in FIG. 2 are specifically executed, and details are not described herein again.

Bus 1104 can include a path for communicating information between various components of synchronization device 700, such as processor 1103, memory 1101, and receiver 1102.

The terminal 900 in the foregoing embodiment shown in FIG. 9 and FIG. 10 can also be implemented based on the hardware structure of the computer. As shown in FIG. 12, the hardware structure of the terminal 900 includes a memory 1201, a transceiver 1202, a processor 1203, and a bus 1204. .

The processor 1203, the memory 1201, and the transceiver 1202 are communicatively coupled by a bus 1204.

The memory 1201 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1201 can store instructions of the operating system and other applications as well as application data. The instructions stored in the memory 1201 are executed by the processor 1203.

The memory 1201 in the embodiment of the present invention can be used to store instructions for implementing the functional units in the embodiments shown in FIG. 9 and FIG. The transceiver 1202 is configured to implement communication between the terminal 900 and other devices or communication networks (such as, but not limited to, Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc. . In the embodiment of the present invention, the transceiver 1202 is configured to receive a message from a server in the cloud and send a message to a server in the cloud.

The processor 1203 can use a general-purpose central processing unit (CPU), a processor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs.

In the embodiment of the present invention, the processor 1203 is configured to execute the instructions in the memory 1201, and the steps in the method embodiment shown in FIG. 3 may be specifically executed, and details are not described herein again.

Bus 1204 can include a path for communicating information between various components of terminal 900, such as processor 1203, memory 1201, and transceiver 1202. Through the description of the above embodiments, those skilled in the art can understand that all or part of the steps of the foregoing embodiment can be implemented by a program to instruct related hardware, and the program can be stored in a computer readable manner. In the storage medium, when the program is executed, the method includes the steps of the foregoing method embodiment, such as: ROM/RAM, magnetic disk, optical disk, and the like.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

Rights request

1. A method for synchronizing a terminal and a server, characterized in that the method includes: the server receives a request to move a file from a first directory to a second directory, and the request carries the identifier of the file and the The identification of the second directory;

The server searches for the metadata of the file according to the identifier of the file, changes the parent directory identifier of the file in the metadata of the file to the identifier of the second directory, and creates it under the first directory. The proxy metadata of the file, the proxy metadata is used to indicate that the file has been moved to the second directory;

2. The method according to claim 1, wherein the proxy metadata includes an identifier of the file, an identifier of the second directory, and a movement mark used to indicate that the file has been moved;

After the server sends the proxy metadata of the file to the terminal, the method further includes: the terminal determines that the file has moved based on the movement mark in the proxy metadata;

Search locally for the metadata of the file based on the identifier of the file;

In the found metadata of the file, the parent directory identifier of the file is changed to the identifier of the second directory.

3. The method according to claim 1, wherein the method further includes: sending metadata of the file to the terminal;

4. The method according to claim 3, wherein the metadata of the file includes the identifier of the file and the identifier of the second directory;

The updating of the second directory in the terminal according to the metadata of the file specifically includes: the terminal locally searches for the file according to the identifier of the file in the metadata of the file. File metadata;

5. The method according to claim 4, wherein the proxy metadata includes an identifier of the file, an identifier of the second directory, and a movement mark used to indicate that the file has been moved;

The terminal updating the first directory in the terminal according to the proxy metadata of the file specifically includes:

The terminal determines that the file has been moved based on the movement mark in the proxy metadata;

Search the metadata of the file locally according to the identifier of the file in the proxy metadata; Determine whether the parent directory identifier of the file in the found metadata of the file is the identifier of the second directory;

If the parent directory identifier of the file is not the identifier of the second directory, then the file is set to be hidden in the metadata of the found file;

If the parent directory identifier of the file is the identifier of the second directory, the file will not be processed.

6. The method according to claim 5, wherein after the terminal locally finds the metadata of the file based on the identifier of the file in the metadata of the file, the method further includes: : Determine the status of the file. If the file is in the hidden status, change the file to the displayed status in the metadata of the file.

7. The method according to any one of claims 1 to 6, characterized in that, after the server searches for the metadata of the file according to the identifier of the file, the method further includes: the server determines that the Whether there is proxy metadata in the second directory indicating that the file has been moved from the second directory;

If there is proxy metadata in the second directory that indicates that the file has been moved from the second directory, the proxy metadata is deleted.

8. A method for synchronizing a terminal and a server, which is characterized by including:

After the server moves the file from the first directory to the second directory by changing the parent directory identification of the file in the file's metadata, and creates proxy metadata of the file under the first directory, the terminal Receive proxy metadata of the file from the server, where the proxy metadata is used to indicate that the file has been moved to the second directory;

The terminal searches for the metadata of the file locally based on the proxy metadata, and completes synchronization with the server through the metadata of the file found locally.

9. The method according to claim 8, wherein the proxy metadata includes an identifier of the file, an identifier of the second directory, and a movement mark used to indicate that the file has been moved;

The terminal searches the metadata of the file locally based on the proxy metadata, and completes the synchronization with the server through the metadata of the file found locally, which specifically includes:

10. The method according to claim 8, characterized in that: completing the synchronization with the server through the metadata of the file found locally specifically includes: using the metadata of the file found locally. metadata to complete the synchronization of the first directory in the terminal and the first directory in the server;

The method also includes:

The terminal receives metadata of the file from the server;

The terminal completes synchronization of the second directory in the terminal and the second directory in the server according to the received metadata of the file.

11. The method according to claim 10, wherein the metadata of the file received from the server includes an identifier of the file and an identifier of the second directory; The metadata of the file completes the synchronization of the second directory in the terminal and the second directory in the server, which specifically includes:

The terminal locally searches for the metadata of the file based on the identification of the file in the received metadata of the file;

12. The method according to claim 11, wherein the proxy metadata includes an identifier of the file, an identifier of the second directory, and a movement mark used to indicate that the file has been moved;

The terminal searches the metadata of the file locally according to the proxy metadata, and completes the first directory in the terminal and the first directory in the server through the metadata of the file found locally. Directory synchronization specifically includes:

13. The method according to claim 12, wherein after the terminal locally finds the metadata of the file based on the identifier of the file in the metadata of the file, the method further includes: : Determine the status of the file. If the file is in the hidden status, change the file to the displayed status in the metadata of the file.

14. A server that synchronizes with a terminal, characterized in that the server includes: a receiving unit configured to receive a request to move a file from the first directory to the second directory, and the request carries the identifier of the file and the identification of the second directory;

A processing unit configured to search for the metadata of the file according to the identifier of the file, change the parent directory identifier of the file to the identifier of the second directory in the metadata of the file, and in the first Create proxy metadata for the file in a directory, where the proxy metadata is used to indicate that the file has been moved to the second directory;

A synchronization unit, configured to send the proxy metadata of the file to the terminal, so as to perform synchronization between the server and the terminal through the file local to the terminal.

15. The server according to claim 14, wherein the synchronization unit is also used to send the metadata of the file to the terminal; the proxy metadata of the file is used to synchronize the first directory, so The metadata of the described file is used to synchronize the second directory.

16. The server according to claim 14 or 15, characterized in that, when changing the parent directory identifier of the file to the identifier of the second directory, the processing unit is further configured to determine the second directory identifier. Whether there is proxy metadata in the directory indicating that the file has been removed from the second directory; if there is proxy metadata in the second directory indicating that the file has been removed from the second directory. data, delete the proxy metadata in the second directory.

17. A terminal that synchronizes with a server, characterized by including:

A synchronization unit, configured to move the file from the first directory to the second directory by changing the parent directory identification of the file in the file's metadata on the server, and create a proxy for the file under the first directory. After receiving the metadata, receive the proxy metadata of the file from the server and provide it to the processing unit, where the proxy metadata is used to indicate that the file has been moved to the second directory;

The processing unit is configured to search the metadata of the file locally on the terminal according to the proxy metadata, and complete synchronization with the server through the metadata of the file found locally.

18. The terminal according to claim 17, wherein the proxy metadata includes an identifier of the first file, an identifier of the second directory, and a movement mark used to indicate that the file has been moved;

The processing unit is specifically configured to determine that the file has been moved according to the movement mark in the proxy metadata; to locally search for the metadata of the file according to the identification of the file; and to search for the metadata of the found file. In the data, the parent directory identifier of the file is changed to the identifier of the second directory.

19. The terminal according to claim 17, wherein the synchronization unit is further configured to receive metadata of the file from the server;

The processing unit specifically includes:

The first operation module is configured to search the metadata of the file locally in the terminal according to the proxy metadata, and complete the local first directory and the third directory in the server through the metadata of the file found locally. Synchronization of a directory;

The second operation module is configured to complete the synchronization of the local second directory and the second directory in the server according to the received metadata of the file.

20. The terminal of claim 19, wherein the metadata of the file received from the server includes an identifier of the file and an identifier of the second directory; the second operation module Specifically configured to locally search for the metadata of the file according to the identifier of the file in the received metadata of the file; and change the parent directory identifier of the file in the found metadata of the file. is the identifier of the second directory.

21. The terminal according to claim 19, wherein the proxy metadata includes an identifier of the file, an identifier of the second directory, and a movement mark used to indicate that the file has been moved;

The first operation module is specifically configured to determine that the file has moved based on the movement mark in the proxy metadata; to locally search for the metadata of the file based on the identification of the file in the proxy metadata; to determine the search. Whether the parent directory identifier of the file in the metadata of the file is the identifier of the second directory; if the parent directory identifier of the file is not the second directory , the file is set to be hidden in the found metadata of the file; if the parent directory identifier of the file is the identifier of the second directory, the file is not processed.

22. The terminal according to claim 20, wherein the second operation module is further configured to determine the status of the file after finding the metadata of the file. If the file is in a hidden state, The file is then changed to a display state in the file's metadata.