CN103118048A - Data synchronization method, server and terminal - Google Patents
Data synchronization method, server and terminal Download PDFInfo
- Publication number
- CN103118048A CN103118048A CN 201110365835 CN201110365835A CN103118048A CN 103118048 A CN103118048 A CN 103118048A CN 201110365835 CN201110365835 CN 201110365835 CN 201110365835 A CN201110365835 A CN 201110365835A CN 103118048 A CN103118048 A CN 103118048A
- Authority
- CN
- China
- Prior art keywords
- synchrodata
- terminal
- data
- server
- data format
- 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.)
- Pending
Links
Images
Abstract
The invention discloses a data synchronization method, a server and a terminal and belongs to the field of the data synchronization. The method comprises the steps that the server receives the synchronization data uploaded by a first terminal, the server receives a synchronization request of a second terminal for the synchronization data, and the server converts the synchronization data to a data format supported by the second terminal according to the synchronization request and sends the converted data to the second terminal. The method is characterized by receiving the uploading order of uploading the designated data, regarding the designated data as the synchronization data and uploading the synchronization data to the server. The server comprises a receiving module, a converting module and a sending module. The terminal comprises a receiving module and an uploading module. The data synchronization method, the server and the terminal not only achieve the data synchronization between the terminals of different platform types and expand the range of the terminal which can be synchronized, but also improve the flexibility of synchronization.
Description
Technical field
The present invention relates to the data field of synchronization, particularly synchronous method, server and the terminal of a kind of data.
Background technology
Along with the development of terminal, produced the cell phone platform of a plurality of types, such as Symbian (V3), Symbian (V5), Android, MTK (MediaTek), iPhone, KJAVA, blackberry, blueberry, WM (Windows Mobile) etc.Terminal to the method for synchronous of data such as contact person etc. on the terminal seldom, the overwhelming majority still relies on the synchronizing softwares of mobile phone itself, with the content backup of lane terminal in computer, again by another terminal and be to carry out the synchronous of contact person at single platform.
After prior art was analyzed, the inventor found that prior art has following shortcoming at least:
The method for synchronous of prior art only be to the contact person synchronously, synchronizing content is single, and it only limits to the terminal of same platform synchronously, range of application is narrow, very flexible, the data that limited between the different platform are synchronous.
Summary of the invention
The embodiment of the invention provides the synchronous method of a kind of data, server and terminal.Described technical scheme is as follows:
The method that a kind of data are synchronous comprises:
Server receives the synchrodata of being uploaded by first terminal;
Described server receives the second terminal to the synchronization request of described synchrodata;
Described server is converted to the data format that described the second terminal is supported according to described synchronization request with described synchrodata, and the data after the described conversion are sent to described the second terminal.
Described synchronization request comprises the data format that described the second terminal is supported,
Correspondingly, described server is converted to the data format that described the second terminal is supported according to described synchronization request with described synchrodata, and the data after the described conversion are sent to described the second terminal, specifically comprises:
Judge that whether described synchrodata is the data format that described the second terminal is supported, if so, sends to described the second terminal with described synchrodata; If not, described synchrodata is converted to the data format that described the second terminal is supported, and the synchrodata after the described conversion is sent to described the second terminal.
Described synchronization request comprises the Platform Type of described the second terminal,
Correspondingly, described server is converted to the data format that described the second terminal is supported according to described synchronization request with described synchrodata, and the data after the described conversion are sent to described the second terminal, specifically comprises:
Judge that whether the Platform Type of described the second terminal can support described synchrodata, if so, sends to described the second terminal with described synchrodata; If not, described synchrodata is converted to the data format that the Platform Type of described the second terminal can be supported, and the synchrodata after the described conversion is sent to described the second terminal.
Judge that whether the Platform Type of described the second terminal can support described synchrodata, specifically comprises:
Described server is according to the Platform Type of described the second terminal, inquire about the first data format, the data format that the Platform Type that described the first data format is described the second terminal can be supported, and contrast the data format of described the first data format and described synchrodata, when described the first data format consistent with the data format of described synchrodata, then the Platform Type of described the second terminal can be supported described synchrodata, inconsistent when the data format of described the first data format and described synchrodata, then the Platform Type of described the second terminal can not be supported described synchrodata.
Server receives the synchrodata of being uploaded by first terminal, comprises afterwards:
When server receives modify instruction to described synchrodata, according to described modify instruction described synchrodata correspondingly to be processed, described modify instruction is used for described synchrodata is added, revised or deletes.
The method that a kind of data are synchronous comprises:
The upper teletype command of specific data is uploaded in reception;
Described specific data is uploaded onto the server as synchrodata.
The corresponding relation of local data and server data is preserved in this locality, correspondingly, described specific data is uploaded onto the server as synchrodata, specifically comprises:
Inquire about described corresponding relation, judge that whether described specific data repeats with described server data, if not, then described specific data or the described specific data increment with respect to described server data is uploaded onto the server.
When the synchrodata that receives from server, the local corresponding relation of preserving of inquiry, judge whether this synchrodata and local data from server repeats, if, then do not carry out Data Update, if not, then described local data is upgraded with respect to the increment of local data with described synchrodata from server or described synchrodata from server.
Described specific data is uploaded onto the server as synchrodata, specifically comprises:
Described specific data is converted to the synchrodata of presetting form, and the synchrodata of described default form is uploaded onto the server.
A kind of server comprises:
Receiver module is used for receiving the synchrodata of being uploaded by first terminal;
Described receiver module also is used for receiving the second terminal to the synchronization request of described synchrodata;
Modular converter is used for the synchronization request according to described receiver module reception, and described synchrodata is converted to the data format that described the second terminal is supported;
Sending module is used for the data after the described modular converter conversion are sent to described the second terminal.
Described synchronization request comprises the data format that described the second terminal is supported,
Correspondingly, described server comprises:
The first judge module is used for judging whether described synchrodata is the data format that described the second terminal is supported;
Described sending module is used for when described the first judge module judges that described synchrodata is the data format of described the second terminal support described synchrodata being sent to described the second terminal;
Described modular converter, be used for when described the first judge module judges that described synchrodata is not the data format of described the second terminal support, described synchrodata is converted to the data format that described the second terminal is supported, and triggers the synchrodata of described sending module after with described conversion and send to described the second terminal.
Described synchronization request comprises the Platform Type of described the second terminal,
Correspondingly, described server comprises:
The second judge module is used for judging whether the Platform Type of described the second terminal can support described synchrodata;
Described sending module is used for when described the second judge module judges that the Platform Type of described the second terminal can be supported described synchrodata described synchrodata being sent to described the second terminal;
Described modular converter, be used for when described the second judge module judges that the Platform Type of described the second terminal can not be supported described synchrodata, described synchrodata is converted to the data format that the Platform Type of described the second terminal can be supported, and triggers the synchrodata of described sending module after with described conversion and send to described the second terminal.
Described the second judge module specifically is used for the Platform Type according to described the second terminal, inquire about the first data format, the data format that the Platform Type that described the first data format is described the second terminal can be supported, and contrast the data format of described the first data format and described synchrodata, when described the first data format consistent with the data format of described synchrodata, then the Platform Type of described the second terminal can be supported described synchrodata, inconsistent when the data format of described the first data format and described synchrodata, then the Platform Type of described the second terminal can not be supported described synchrodata.
Described server also comprises:
Modified module is used for according to described modify instruction described synchrodata correspondingly being processed when the modify instruction that receives described synchrodata, and described modify instruction is for described synchrodata is added, revised or deletes.
A kind of terminal comprises:
Receiver module is used for receiving the upper teletype command of uploading specific data;
Upper transmission module is used for described specific data is uploaded onto the server as synchrodata.
The corresponding relation of local data and server data is preserved in this locality, correspondingly, described upper transmission module specifically is used for inquiring about described corresponding relation, judge whether described specific data repeats with described server data, if not, then described specific data or the described specific data increment with respect to described server data is uploaded onto the server.
Described terminal also comprises:
Receiver module is used for receiving the synchrodata from server;
Update module, be used for the synchrodata according to described receiver module reception, the local corresponding relation of preserving of inquiry, judge whether this synchrodata and local data from server repeats, if, then do not carry out Data Update, if not, then described local data is upgraded with respect to the increment of local data with described synchrodata from server or described synchrodata from server.
Described terminal also comprises: modular converter is used for described specific data is converted to the synchrodata of default form, and triggers described upper transmission module the synchrodata of described default form is uploaded onto the server.
The beneficial effect of the technical scheme that the embodiment of the invention provides is:
To need synchronous synchrodata to upload onto the server by first terminal, and with server as the transfer platform, when server receives synchronization request from the second terminal, according to this synchronization request, synchrodata on the server is carried out Data Format Transform, data after the conversion are sent to the second terminal, so that this data format can be identified by the second terminal, realized that not only the data between the terminal of different platform type are synchronous, expanded and to have carried out the scope of synchronous terminal, and strengthened synchronous flexibility.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, the below will do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art, apparently, accompanying drawing in the following describes only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the flow chart of a kind of method of data synchronization of providing of the embodiment of the invention;
Fig. 2 is the flow chart of the synchronous method of a kind of data of providing of the embodiment of the invention;
Fig. 3 is the flow chart of the synchronous method of a kind of data of providing of the embodiment of the invention;
Fig. 4 is the structural representation of a kind of server of providing of the embodiment of the invention;
Fig. 5 is the structural representation of a kind of server of providing of the embodiment of the invention;
Fig. 6 is the structural representation of the another kind of server that provides of the embodiment of the invention;
Fig. 7 is the structural representation of another server of providing of the embodiment of the invention;
Fig. 8 is the structural representation of a kind of terminal of providing of the embodiment of the invention;
Fig. 9 is the structural representation of the another kind of terminal that provides of the embodiment of the invention;
Figure 10 is the structural representation of another terminal of providing of the embodiment of the invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, embodiment of the present invention is described further in detail below in conjunction with accompanying drawing.
Before introducing the synchronous method of data provided by the invention, at first rudimentary knowledge of the present invention is carried out concise and to the point introduction:
Multi-platform: refer to a plurality of cell phone platforms existing and that occur in the future, existing such as symbian (V3), symbian (V5), android, MTK, iPhone, KJAVA, blackberry, blueberry, WM (Windows Mobile) etc.
Terminal: refer to input, outlet terminal, such as the input/output terminal of computer PC, panel computer, mobile phone terminal etc. are arranged.
Synchronously: two data sources are arranged, and their data all are the same at first.If change (perhaps change has all occured the data of two data sources) has occured through operations such as interpolation, modification, deletions in the data of a data source, be consistent for the data that make two data sources so, namely allow the change of a data source data be reflected on another, just must carry out the operation that data that allow two data sources are consistent, this operation is just cried synchronous.After simultaneous operation finished, the data on two equipment were just in full accord, are in synchronous regime.Comprise synchronously one-way synchronization and bi-directional synchronization.
Fig. 1 is the flow chart of a kind of method of data synchronization of providing of the embodiment of the invention.Executive agent among this embodiment is server, and this server can be application server, and referring to Fig. 1, this embodiment specifically comprises:
101, server receives the synchrodata of being uploaded by first terminal;
Wherein, first terminal can be the terminal with communication capacity; Synchrodata can be the data of the terminals such as contact person, log, QQ chat record, user's head portrait, device end software installation information, label preservation, wherein, the contact person can comprise name of contact person and contact method, and log can comprise: message registration and note record etc.
In the present embodiment, this synchrodata can upload onto the server by modes such as Wifi, GPS, and server receives the synchrodata that first terminal is uploaded, and preserves this synchrodata.Those skilled in the art can know that server must be preserved when receiving synchrodata, therefore the step of preserving is repeated no more.
Need to prove that this synchrodata is carried first terminal user's user ID or the user ID of this synchrodata is accessed in the permission that sets in advance, restriction to the access of this synchrodata and synchronously.
102, described server receives the second terminal to the synchronization request of described synchrodata;
In the present embodiment, when the second terminal needs and first terminal carries out can carrying out transfer by server when synchronous, uploaded onto the server by first terminal, send synchronization request to synchrodata by the second terminal to server again.Particularly, this synchronization request is carried the second terminal use's user ID.Whether the user ID that server is judged this second terminal use and first terminal user's user ID be identical or judge whether the second terminal use's user ID is the user ID that allows this synchrodata of access, when this second terminal use's user ID is accessed the user ID of this synchrodata with first terminal user's user ID user ID identical or the second terminal use for permission, respond this synchronization request.Those skilled in the art can know that this user ID can be username and password, for example, and phone number and password for inquiry, QQ number and QQ password etc.
103, described server is converted to the data format that described the second terminal is supported according to described synchronization request with described synchrodata, and the data after the described conversion are sent to described the second terminal.
In the present embodiment, because the Platform Type of first terminal and the second terminal might be different, platform such as first terminal is the android platform, the platform of the second terminal is the Nokia platform, the data format of its support is different, therefore, synchrodata need to be converted to the data format that the second terminal is supported, the data after will changing again send to the second terminal.This synchronization request comprises the data format of the second terminal support or the Platform Type of the second terminal.Particularly, this step 103 comprises: judge whether described synchrodata is the data format that described the second terminal is supported, if not, described synchrodata is converted to the data format that described the second terminal is supported, and the synchrodata after the described conversion is sent to described the second terminal.Or, judge whether the Platform Type of described the second terminal can support described synchrodata, if so, described synchrodata is sent to described the second terminal; If not, whether the Platform Type that described synchrodata is converted to described the second terminal can be supported, and the synchrodata after the described conversion is sent to described the second terminal.
Further, after this step 103, comprising:
When server receives modify instruction to described synchrodata, according to described modify instruction described synchrodata correspondingly to be processed, described modify instruction is used for described synchrodata is added, revised or deletes.
To need synchronous synchrodata to upload onto the server by first terminal, and with server as the transfer platform, when server receives synchronization request from the second terminal, according to this synchronization request, synchrodata on the server is carried out Data Format Transform, data after the conversion are sent to the second terminal, so that this data format can be identified by the second terminal, realized that not only the data between the terminal of different platform type are synchronous, expanded and to have carried out the scope of synchronous terminal, and strengthened synchronous flexibility.
Fig. 2 is the flow chart of the synchronous method of a kind of data of providing of the embodiment of the invention.The interaction agent of this embodiment is terminal, and referring to Fig. 2, this embodiment specifically comprises:
201, receive the upper teletype command of uploading specific data;
In the present embodiment, the upper teletype command that receives of first terminal can be following any one situation:
(1) upper teletype command is sent for specific data by the user.For example, the data that first terminal is deposited terminal provide one " uploading " button as the entrance that calls upper teletype command, when the user will upload contacts list, and can be by clicking teletype command in " uploading " triggering.
(2) upper teletype command is triggered the operation of specific data by the user, and this operation comprises: add, revise or deletion.For example, the user makes amendment to the telephone number of the contact person A in the contacts list, if this retouching operation is predetermined registration operation, then trigger the upper teletype command of uploading specific data, wherein, predetermined registration operation refers to the operation that can trigger teletype command that terminal is default, is established at the beginning of during in exploitation in the terminal setting or by the technical staff by the user.Need to prove that this specific data can be the single operation object, for example, carried out the contact person A that revises, can also be the data group at operand place, for example, and the contacts list at contact person place.
202, described specific data is uploaded onto the server as synchrodata.
Further, the corresponding relation of local data and server data is preserved in this locality, correspondingly, described specific data is uploaded onto the server as synchrodata, specifically comprises:
Inquire about described corresponding relation, judge that whether described specific data repeats with described server data, if not, then described specific data or the described specific data increment with respect to described server data is uploaded onto the server as synchrodata.
When the synchrodata that receives from server, the local corresponding relation of preserving of inquiry, judge whether this synchrodata and local data from server repeats, if, then do not carry out Data Update, if not, then described local data is upgraded with respect to the increment of local data with described synchrodata from server or described synchrodata from server.
Wherein, described specific data is uploaded onto the server as synchrodata, specifically comprises:
Described specific data is converted to the synchrodata of presetting form, and the synchrodata of described default form is uploaded onto the server.
Fig. 3 is the flow chart of the synchronous method of a kind of data of providing of the embodiment of the invention.The interaction agent of this embodiment is first terminal, the second terminal and server, and referring to Fig. 3, this embodiment specifically comprises:
301, first terminal receives the upper teletype command of uploading specific data;
This step 301 and step 201 in like manner do not repeat them here.
302, first terminal is converted to specific data the synchrodata of default form;
In the present embodiment, the data format that the specific data of first terminal storage is supported for this first terminal, when receiving upper teletype command, this specific data is converted to the synchrodata of default form, so that server can be supported the synchrodata of this default form, those skilled in the art can know that this default form is by arranging between server and the terminal.
In another embodiment, after having carried out step 301, first terminal can not carry out format conversion to specific data yet, and specific data is uploaded onto the server as synchrodata.
Further, first terminal is preserved the corresponding relation of first terminal data and server data, when the upper teletype command that receives specific data, first terminal is inquired about this corresponding relation, judge that whether described specific data repeats with described server data, if so, then finishes; If not, then described specific data or the described specific data increment with respect to described server data is uploaded onto the server as synchrodata.Wherein, first terminal is inquired about this corresponding relation, specifically comprises: inquire about whether comprise specific data in this corresponding relation, if so, then server data and specific data repeat, and if not, then server data and specific data do not repeat.
303, first terminal uploads onto the server synchrodata;
When first terminal is preserved the corresponding relation of first terminal data and server data, when knowing that by judgement specific data and server data do not repeat (inconsistent), then described specific data or the described specific data increment with respect to described server data is uploaded onto the server as synchrodata.This uploads specific data or increment is preset in terminal by the user, uploads according to predetermined manner.
Those skilled in the art can know that this method of uploading has multiple, does not repeat them here.
304, server receives the synchrodata of being uploaded by first terminal;
In the present embodiment, when the modify instruction that receives described synchrodata, according to described modify instruction described synchrodata is correspondingly processed, described modify instruction is used for described synchrodata is added, revised or deletes.For example, the note in the note record is deleted etc.After the synchrodata that the server reception is uploaded by first terminal, can check by other modes such as WEB, WAP, notes at each terminal (such as mobile phone, PC computer, panel computer, other equipment), and the editor such as additions and deletions modification, the data behind editor are retained in the server; When server receives the synchronization request of terminal, the data behind the editor can be returned terminal synchronously as synchrodata, further strengthen the management to synchrodata.
305, server receives the second terminal to the synchronization request of this synchrodata, and this synchronization request comprises the Platform Type of the second terminal;
This synchronization request comprises the data format that the Platform Type that comprises the second terminal or the second terminal are supported.
In embodiments of the present invention, upload synchrodata with first terminal, the second terminal request describes for example synchronously, in another embodiment, first terminal is uploaded synchrodata, and first terminal sends synchronization request to server, and the embodiment of the invention is not specifically limited.First terminal and the second terminal are to have uploads and asks synchronous terminal.
Whether the Platform Type of 306, judging described the second terminal can support described synchrodata;
If so, execution in step 307;
If not, execution in step 308;
In the present embodiment, the Platform Type of the terminal that uploading data and request are synchronous can be inconsistent, therefore need to when receiving synchronization request, judge whether the Platform Type of the terminal that sends this synchronization request can support this synchrodata.
Particularly, described server is according to the Platform Type of described the second terminal, inquire about the first data format, the data format that the Platform Type that described the first data format is described the second terminal can be supported, and contrast the data format of described the first data format and described synchrodata; When described the first data format consistent with the data format of described synchrodata, then the Platform Type of described the second terminal can be supported described synchrodata, inconsistent when the data format of described the first data format and described synchrodata, then the Platform Type of described the second terminal can not be supported described synchrodata.
In another embodiment, this synchronization request comprises the data format that the second terminal is supported, then described server is according to described synchronization request, judge whether described synchrodata is the data format that described the second terminal is supported, if so, execution in step 307, if not, execution in step 308.
307, described synchrodata is sent to described the second terminal.
Be sent as prior art described in the present invention, do not repeat them here.
308, described synchrodata is converted to the data format that the Platform Type of described the second terminal can be supported, and the synchrodata after the described conversion is sent to described the second terminal.
309, the second terminal receiving isochronous data, and according to synchrodata local data is upgraded.
Further, the second terminal is preserved the corresponding relation of the second terminal data and server data, when the second terminal receiving isochronous data, the local corresponding relation of preserving of inquiry, judge whether this synchrodata and local save data repeat, if so, then do not carry out Data Update, if not, then with synchrodata or the synchrodata increment with respect to local data local data is upgraded.Repeated situation appears in the data after this step can be avoided synchronously, also can simplify the operation of terminal.
The method that present embodiment provides, to need synchronous synchrodata to upload onto the server by first terminal, and with server as the transfer platform, when server receives synchronization request from the second terminal, according to this synchronization request, synchrodata on the server is carried out Data Format Transform, data after the conversion are sent to the second terminal, so that this data format can be identified by the second terminal, realized that not only the data between the terminal of different platform type are synchronous, expanded and to have carried out the scope of synchronous terminal, and strengthened synchronous flexibility.
Fig. 4 is the structural representation of a kind of server of providing of the embodiment of the invention.Referring to Fig. 4, this server comprises:
Receiver module 401 is used for receiving the synchrodata of being uploaded by first terminal;
Described receiver module 401 also is used for receiving the second terminal to the synchronization request of described synchrodata;
Modular converter 402 is used for the synchronization request according to described receiver module 401 receptions, and described synchrodata is converted to the data format that described the second terminal is supported;
Sending module 403 is used for the data after described modular converter 402 conversions are sent to described the second terminal.
Described synchronization request comprises the data format that described the second terminal is supported,
Correspondingly, referring to Fig. 5, described server comprises:
The first judge module 404 is used for judging whether described synchrodata is the data format that described the second terminal is supported;
Described sending module 403 is used for when described the first judge module 404 judges that described synchrodata is the data format of described the second terminal support described synchrodata being sent to described the second terminal;
Described modular converter 402, be used for when described the first judge module 404 judges that described synchrodata is not the data format of described the second terminal support, described synchrodata is converted to the data format that described the second terminal is supported, and triggers the synchrodata of described sending module 403 after with described conversion and send to described the second terminal.
Described synchronization request comprises the Platform Type of described the second terminal,
Correspondingly, referring to Fig. 6, described server comprises:
The second judge module 405 is used for judging whether the Platform Type of described the second terminal can support described synchrodata;
Described sending module 403 is used for when described the second judge module 405 judges that the Platform Type of described the second terminal can be supported described synchrodata described synchrodata being sent to described the second terminal;
Described modular converter 402, be used for when described the second judge module 405 judges that the Platform Type of described the second terminal can not be supported described synchrodata, described synchrodata is converted to the data format that the Platform Type of described the second terminal can be supported, and triggers the synchrodata of described sending module 403 after with described conversion and send to described the second terminal.
Described the second judge module 405 concrete Platform Types that are used for according to described the second terminal, inquire about the first data format, the data format that the Platform Type that described the first data format is described the second terminal can be supported, and contrast the data format of described the first data format and described synchrodata, when described the first data format consistent with the data format of described synchrodata, then the Platform Type of described the second terminal can be supported described synchrodata, inconsistent when the data format of described the first data format and described synchrodata, then the Platform Type of described the second terminal can not be supported described synchrodata.
Referring to Fig. 7, described server also comprises:
Modified module 406 is used for according to described modify instruction described synchrodata correspondingly being processed when the modify instruction that receives described synchrodata, and described modify instruction is for described synchrodata is added, revised or deletes.
The server that present embodiment provides belongs to same design with embodiment of the method, and its specific implementation process sees embodiment of the method for details, repeats no more here.
Fig. 8 is the structural representation of a kind of terminal of providing of the embodiment of the invention.Referring to Fig. 8, this terminal comprises:
Receiver module 801 is used for receiving the upper teletype command of uploading specific data;
Upper transmission module 802 is used for described specific data is uploaded onto the server as synchrodata.
The corresponding relation of local data and server data is preserved in this locality, correspondingly, described upper transmission module 802 specifically is used for inquiring about described corresponding relation, judge whether described specific data repeats with described server data, if not, then described specific data or the described specific data increment with respect to described server data is uploaded onto the server.
Referring to Fig. 9, described terminal also comprises:
Described receiver module 801 is used for receiving the synchrodata from server;
Update module 803, be used for the synchrodata according to described receiver module reception, the local corresponding relation of preserving of inquiry, judge whether this synchrodata and local data from server repeats, if, then do not carry out Data Update, if not, then described local data is upgraded with respect to the increment of local data with described synchrodata from server or described synchrodata from server.
Referring to Figure 10, described terminal also comprises:
Modular converter 804 is used for described specific data is converted to the synchrodata of default form, and triggers described upper transmission module 802 synchrodata of described default form is uploaded onto the server.
The terminal that present embodiment provides belongs to same design with embodiment of the method, and its specific implementation process sees embodiment of the method for details, repeats no more here.
The all or part of step that one of ordinary skill in the art will appreciate that realization above-described embodiment can be finished by hardware, also can come the relevant hardware of instruction to finish by program, described program can be stored in a kind of computer-readable recording medium, the above-mentioned storage medium of mentioning can be read-only memory, disk or CD etc.
The above only is preferred embodiment of the present invention, and is in order to limit the present invention, within the spirit and principles in the present invention not all, any modification of doing, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (18)
1. the method that data are synchronous is characterized in that, comprising:
Server receives the synchrodata of being uploaded by first terminal;
Described server receives the second terminal to the synchronization request of described synchrodata;
Described server is converted to the data format that described the second terminal is supported according to described synchronization request with described synchrodata, and the data after the described conversion are sent to described the second terminal.
2. method according to claim 1 is characterized in that, described synchronization request comprises the data format that described the second terminal is supported,
Correspondingly, described server is converted to the data format that described the second terminal is supported according to described synchronization request with described synchrodata, and the data after the described conversion are sent to described the second terminal, specifically comprises:
Judge that whether described synchrodata is the data format that described the second terminal is supported, if so, sends to described the second terminal with described synchrodata; If not, described synchrodata is converted to the data format that described the second terminal is supported, and the synchrodata after the described conversion is sent to described the second terminal.
3. method according to claim 1 is characterized in that, described synchronization request comprises the Platform Type of described the second terminal,
Correspondingly, described server is converted to the data format that described the second terminal is supported according to described synchronization request with described synchrodata, and the data after the described conversion are sent to described the second terminal, specifically comprises:
Judge that whether the Platform Type of described the second terminal can support described synchrodata, if so, sends to described the second terminal with described synchrodata; If not, described synchrodata is converted to the data format that the Platform Type of described the second terminal can be supported, and the synchrodata after the described conversion is sent to described the second terminal.
4. method according to claim 3 is characterized in that, judges whether the Platform Type of described the second terminal can support described synchrodata, specifically comprises:
Described server is according to the Platform Type of described the second terminal, inquire about the first data format, the data format that the Platform Type that described the first data format is described the second terminal can be supported, and contrast the data format of described the first data format and described synchrodata, when described the first data format consistent with the data format of described synchrodata, then the Platform Type of described the second terminal can be supported described synchrodata, inconsistent when the data format of described the first data format and described synchrodata, then the Platform Type of described the second terminal can not be supported described synchrodata.
5. each described method is characterized in that according to claim 1-4, and server receives the synchrodata of being uploaded by first terminal, comprises afterwards:
When server receives modify instruction to described synchrodata, according to described modify instruction described synchrodata correspondingly to be processed, described modify instruction is used for described synchrodata is added, revised or deletes.
6. the method that data are synchronous is characterized in that, comprising:
The upper teletype command of specific data is uploaded in reception;
Described specific data is uploaded onto the server as synchrodata.
7. method according to claim 6 is characterized in that, the corresponding relation of local data and server data is preserved in this locality, correspondingly, described specific data is uploaded onto the server as synchrodata, specifically comprises:
Inquire about described corresponding relation, judge that whether described specific data repeats with described server data, if not, then described specific data or the described specific data increment with respect to described server data is uploaded onto the server.
8. method according to claim 7, it is characterized in that, when the synchrodata that receives from server, the local corresponding relation of preserving of inquiry, judge that whether this synchrodata and local data from server repeats, and if so, does not then carry out Data Update, if not, then described local data is upgraded with respect to the increment of local data with described synchrodata from server or described synchrodata from server.
9. each described method is characterized in that according to claim 6-8, and described specific data is uploaded onto the server as synchrodata, specifically comprises:
Described specific data is converted to the synchrodata of presetting form, and the synchrodata of described default form is uploaded onto the server.
10. a server is characterized in that, comprising:
Receiver module is used for receiving the synchrodata of being uploaded by first terminal;
Described receiver module also is used for receiving the second terminal to the synchronization request of described synchrodata;
Modular converter is used for the synchronization request according to described receiver module reception, and described synchrodata is converted to the data format that described the second terminal is supported;
Sending module is used for the data after the described modular converter conversion are sent to described the second terminal.
11. server according to claim 10 is characterized in that, described synchronization request comprises the data format that described the second terminal is supported,
Correspondingly, described server comprises:
The first judge module is used for judging whether described synchrodata is the data format that described the second terminal is supported;
Described sending module is used for when described the first judge module judges that described synchrodata is the data format of described the second terminal support described synchrodata being sent to described the second terminal;
Described modular converter, be used for when described the first judge module judges that described synchrodata is not the data format of described the second terminal support, described synchrodata is converted to the data format that described the second terminal is supported, and triggers the synchrodata of described sending module after with described conversion and send to described the second terminal.
12. server according to claim 10 is characterized in that, described synchronization request comprises the Platform Type of described the second terminal,
Correspondingly, described server comprises:
The second judge module is used for judging whether the Platform Type of described the second terminal can support described synchrodata;
Described sending module is used for when described the second judge module judges that the Platform Type of described the second terminal can be supported described synchrodata described synchrodata being sent to described the second terminal;
Described modular converter, be used for when described the second judge module judges that the Platform Type of described the second terminal can not be supported described synchrodata, described synchrodata is converted to the data format that the Platform Type of described the second terminal can be supported, and triggers the synchrodata of described sending module after with described conversion and send to described the second terminal.
13. server according to claim 12, it is characterized in that, described the second judge module specifically is used for the Platform Type according to described the second terminal, inquire about the first data format, the data format that the Platform Type that described the first data format is described the second terminal can be supported, and contrast the data format of described the first data format and described synchrodata, when described the first data format consistent with the data format of described synchrodata, then the Platform Type of described the second terminal can be supported described synchrodata, inconsistent when the data format of described the first data format and described synchrodata, then the Platform Type of described the second terminal can not be supported described synchrodata.
14. each described server is characterized in that according to claim 10-13, described server also comprises:
Modified module is used for according to described modify instruction described synchrodata correspondingly being processed when the modify instruction that receives described synchrodata, and described modify instruction is for described synchrodata is added, revised or deletes.
15. a terminal is characterized in that, comprising:
Receiver module is used for receiving the upper teletype command of uploading specific data;
Upper transmission module is used for described specific data is uploaded onto the server as synchrodata.
16. terminal according to claim 15, it is characterized in that, the corresponding relation of local data and server data is preserved in this locality, correspondingly, described upper transmission module specifically is used for inquiring about described corresponding relation, judge that whether described specific data repeats with described server data, if not, then described specific data or the described specific data increment with respect to described server data is uploaded onto the server.
17. terminal according to claim 16 is characterized in that, described terminal also comprises:
Receiver module is used for receiving the synchrodata from server;
Update module, be used for the synchrodata according to described receiver module reception, the local corresponding relation of preserving of inquiry, judge whether this synchrodata and local data from server repeats, if, then do not carry out Data Update, if not, then described local data is upgraded with respect to the increment of local data with described synchrodata from server or described synchrodata from server.
18. each described terminal according to claim 15-17, it is characterized in that, described terminal also comprises: modular converter is used for described specific data is converted to the synchrodata of default form, and triggers described upper transmission module the synchrodata of described default form is uploaded onto the server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110365835 CN103118048A (en) | 2011-11-17 | 2011-11-17 | Data synchronization method, server and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110365835 CN103118048A (en) | 2011-11-17 | 2011-11-17 | Data synchronization method, server and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103118048A true CN103118048A (en) | 2013-05-22 |
Family
ID=48416322
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201110365835 Pending CN103118048A (en) | 2011-11-17 | 2011-11-17 | Data synchronization method, server and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103118048A (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103281798A (en) * | 2013-05-30 | 2013-09-04 | 腾讯科技（深圳）有限公司 | Method, device and system for achieving modification synchronization |
| CN103533036A (en) * | 2013-09-29 | 2014-01-22 | 方正国际软件有限公司 | Asynchronous queue return data response system and method |
| CN103685497A (en) * | 2013-12-06 | 2014-03-26 | 中国科学院深圳先进技术研究院 | On-line storing and sharing method and system |
| CN103927288A (en) * | 2014-04-30 | 2014-07-16 | 惠州Tcl移动通信有限公司 | Method and system for transferring and sharing information among mobile devices |
| CN104092740A (en) * | 2014-06-25 | 2014-10-08 | 腾讯科技（深圳）有限公司 | Application data synchronizing method and device |
| CN104184776A (en) * | 2013-05-27 | 2014-12-03 | 腾讯科技（深圳）有限公司 | Method and apparatus for realizing commonly used expression synchronization of instant messaging tools |
| CN105429846A (en) * | 2014-09-18 | 2016-03-23 | 中兴通讯股份有限公司 | Instant chat tool chat record synchronization methods and terminal equipment |
| CN105530272A (en) * | 2014-09-29 | 2016-04-27 | 阿里巴巴集团控股有限公司 | Method and device for application data synchronization |
| CN106412052A (en) * | 2016-09-27 | 2017-02-15 | 四川变体科技有限公司 | Service synchronization method and device |
| CN106453586A (en) * | 2016-10-31 | 2017-02-22 | 宇龙计算机通信科技(深圳)有限公司 | Message synchronizing method, device and system |
| CN106576061A (en) * | 2014-06-02 | 2017-04-19 | 爱唯思有限公司 | Systems and methods for secure communication over a network using a linking address |
| CN107846450A (en) * | 2017-09-29 | 2018-03-27 | 珂伯特机器人（天津）有限公司 | A kind of synchronous method of chat data |
| CN108595274A (en) * | 2017-12-28 | 2018-09-28 | 广州京墨医疗科技有限公司 | Program Synchronization control method, device, system, computer equipment and storage medium |
| CN110413957A (en) * | 2018-04-28 | 2019-11-05 | 中移(苏州)软件技术有限公司 | The method and processor of data exchange, server, data interchange platform |
| CN110765744A (en) * | 2019-10-22 | 2020-02-07 | 苏州思必驰信息科技有限公司 | Multi-person collaborative document editing method and system |
| CN111352749A (en) * | 2020-03-02 | 2020-06-30 | 珠海随变科技有限公司 | Data synchronization method, device, equipment and storage medium |
| CN116506450A (en) * | 2023-06-27 | 2023-07-28 | 武汉吧哒科技股份有限公司 | File synchronization method and device, electronic equipment and storage medium |
-
2011
- 2011-11-17 CN CN 201110365835 patent/CN103118048A/en active Pending
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104184776A (en) * | 2013-05-27 | 2014-12-03 | 腾讯科技（深圳）有限公司 | Method and apparatus for realizing commonly used expression synchronization of instant messaging tools |
| CN103281798A (en) * | 2013-05-30 | 2013-09-04 | 腾讯科技（深圳）有限公司 | Method, device and system for achieving modification synchronization |
| CN103533036A (en) * | 2013-09-29 | 2014-01-22 | 方正国际软件有限公司 | Asynchronous queue return data response system and method |
| CN103685497A (en) * | 2013-12-06 | 2014-03-26 | 中国科学院深圳先进技术研究院 | On-line storing and sharing method and system |
| CN103685497B (en) * | 2013-12-06 | 2017-10-31 | 中国科学院深圳先进技术研究院 | A kind of on-line storage sharing method and system |
| CN103927288B (en) * | 2014-04-30 | 2018-12-07 | 惠州Tcl移动通信有限公司 | Information transfer and shared method and system between a kind of mobile device |
| CN103927288A (en) * | 2014-04-30 | 2014-07-16 | 惠州Tcl移动通信有限公司 | Method and system for transferring and sharing information among mobile devices |
| CN106576061A (en) * | 2014-06-02 | 2017-04-19 | 爱唯思有限公司 | Systems and methods for secure communication over a network using a linking address |
| CN104092740B (en) * | 2014-06-25 | 2016-05-04 | 腾讯科技（深圳）有限公司 | Application data synchronous method and device |
| CN104092740A (en) * | 2014-06-25 | 2014-10-08 | 腾讯科技（深圳）有限公司 | Application data synchronizing method and device |
| CN105429846B (en) * | 2014-09-18 | 2020-03-31 | 中兴通讯股份有限公司 | Instant chat tool chat record synchronization method and terminal equipment |
| CN105429846A (en) * | 2014-09-18 | 2016-03-23 | 中兴通讯股份有限公司 | Instant chat tool chat record synchronization methods and terminal equipment |
| CN105530272A (en) * | 2014-09-29 | 2016-04-27 | 阿里巴巴集团控股有限公司 | Method and device for application data synchronization |
| CN106412052A (en) * | 2016-09-27 | 2017-02-15 | 四川变体科技有限公司 | Service synchronization method and device |
| CN106412052B (en) * | 2016-09-27 | 2019-08-30 | 四川变体科技有限公司 | Service synchronization method and device |
| CN106453586A (en) * | 2016-10-31 | 2017-02-22 | 宇龙计算机通信科技(深圳)有限公司 | Message synchronizing method, device and system |
| CN107846450A (en) * | 2017-09-29 | 2018-03-27 | 珂伯特机器人（天津）有限公司 | A kind of synchronous method of chat data |
| CN108595274A (en) * | 2017-12-28 | 2018-09-28 | 广州京墨医疗科技有限公司 | Program Synchronization control method, device, system, computer equipment and storage medium |
| CN110413957A (en) * | 2018-04-28 | 2019-11-05 | 中移(苏州)软件技术有限公司 | The method and processor of data exchange, server, data interchange platform |
| CN110765744A (en) * | 2019-10-22 | 2020-02-07 | 苏州思必驰信息科技有限公司 | Multi-person collaborative document editing method and system |
| CN110765744B (en) * | 2019-10-22 | 2024-01-30 | 思必驰科技股份有限公司 | Multi-user collaborative document editing method and system |
| CN111352749A (en) * | 2020-03-02 | 2020-06-30 | 珠海随变科技有限公司 | Data synchronization method, device, equipment and storage medium |
| CN116506450A (en) * | 2023-06-27 | 2023-07-28 | 武汉吧哒科技股份有限公司 | File synchronization method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103118048A (en) | Data synchronization method, server and terminal | |
| CN1625878B (en) | Method and equipment for processing synchronous related information | |
| CN102819461B (en) | Desktop synchronous method, device, equipment and system | |
| US20130139143A1 (en) | Method and device arrangement for managing the use profile of a terminal device | |
| CN106385664A (en) | IOT (Internet of Things) intelligent equipment communication method and system based on virtual SIM card | |
| CN105139877A (en) | Method for connecting multimedia play devices, main device, control terminal and system | |
| CN101204112A (en) | System, terminal, network entity, method and computer program for system selection in a multi-mode communication system | |
| CN103220822A (en) | Data transmission method, data transmission device and mobile terminal | |
| CN103297459A (en) | Synchronizing system of application configuration information, access server, clients and synchronizing method of application configuration information | |
| CN102420891A (en) | Mobile terminal and test method, equipment and system thereof | |
| CN101835137A (en) | Method for transmitting and receiving file based on mobile terminals and mobile terminal | |
| CN110635957B (en) | Method and device for network distribution of Internet of things equipment and mobile terminal | |
| CN102118831A (en) | Wireless access method and device | |
| CN103227836A (en) | Off-line downloading method and off-line downloading server | |
| CN105827740A (en) | Method, equipment and system for contact person information backup | |
| EP1796354B1 (en) | Method and mobile terminal for log management during Bluetooth communication | |
| CN103986824A (en) | Data display method and system of electronic equipment | |
| CN100531431C (en) | Device for realizing maintenance of far end radio frequency terminal by local maintenance terminal | |
| CN103327133B (en) | A kind of geographical location information update method and device | |
| CN113992652A (en) | Cross-terminal file synchronization method and device | |
| CN101969501A (en) | Mobile terminal, and data synchronization system and method thereof | |
| CN106454541A (en) | Calling method, calling device and calling system | |
| CN103514003A (en) | Program installation method and device | |
| KR100818962B1 (en) | Method for managing remote mobile device | |
| CN100455059C (en) | Short message gateway bridging system, method and short message gateway bridge module |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20130522 |