CN101453418B - Updating method for synchronization between customer terminal and server - Google Patents
Updating method for synchronization between customer terminal and server Download PDFInfo
- Publication number
- CN101453418B CN101453418B CN2007101990013A CN200710199001A CN101453418B CN 101453418 B CN101453418 B CN 101453418B CN 2007101990013 A CN2007101990013 A CN 2007101990013A CN 200710199001 A CN200710199001 A CN 200710199001A CN 101453418 B CN101453418 B CN 101453418B
- Authority
- CN
- China
- Prior art keywords
- server
- client
- file
- static
- static file
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for updating a client and a server synchronously, which comprises the following steps: generating a static file from a dynamic file by the server and storing the static file in a static catalog; making an initial backup for the static catalog of the server by the client; regenerating the static file from the modified dynamic file when the server performs periodical check on a source catalog storing the dynamic file, storing the static file in the static catalog, and modifying the version number of the static file simultaneously; sending a static file list stored in the client to the server when the client is updated; comparing the received static file list with the static file list stored in the server by the server, and putting the static file lists with different versions to a temporary catalog; sending all the files in the temporary catalog to the client by the server; and updating the client according to the received files. Therefore, by adopting the technical proposal of the invention, the downloading stream quantity in the updating of the client can be reduced so that the downloading stream quantity is minimized.
Description
Technical field
The present invention relates to the wireless application field, comprise the wireless network application technology of server and client, refer to the update method of a kind of client and server sync especially.
Background technology
Along with the arrival of network times and client device use extensive gradually, the application of radio network technique also progressively is penetrated in daily life, the working and learning.Usually, wireless network comprises the server and client side.In great majority were used, for service is provided better, the informational needs of client and the information on the server were consistent.That is to say that the file of storing on the client must be up-to-date.
In order to keep the consistency of client and data in server, renewal to client, at present, adopting with the bag mostly is the update method of unit, be about to all files that need upgrade and break into bag, be dealt on each client by wireless network then, client will be finished local update after will wrapping decompress(ion) again.
Because server is accomplished fluently bag the back distribution in advance, so it is all identical to send to the bag content of each client, thinks the client of one or two file in the update package for those, it is just renewable also to need to download whole AKU, make data quantity transmitted big, thereby caused unnecessary downloading flow.
Summary of the invention
The problem to be solved in the present invention provides the update method of minimized client of a kind of downloading flow and server sync.
In order to address the above problem, the technical scheme of the update method of client of the present invention and server sync comprises:
Living document is generated static file to server and the static file tabulation is left under the static catalog, described living document refers to do the file of renewal, the file of described static file confession under directions client downloads, the static file tabulation refers to deposit the title of static file and the tabulation of version number, and described static catalog refers to deposit the catalogue of static file and static file tabulation;
The described static catalog of a server of client initial back-up;
When server regularly detects the source directory of depositing described living document, the living document of revising is regenerated static file and leave under the static catalog, revise the version number of static file correspondence described in the static file tabulation simultaneously;
When client was upgraded, the described static file tabulation that it oneself is preserved earlier sent to server;
The described static file tabulation that server will receive is compared with the static file tabulation of its preservation, and static file that version is different and the tabulation of the static file of server end are put under the temp directory;
Server sends to client with the All Files under the described temp directory;
Client is upgraded according to the file of being received;
Server is confirmed to empty described temp directory after client is received the file of its transmission.
In addition, the update method of client of the present invention and server sync also comprises step:
Server detects behind the living document of modification to send to client and upgrades prompting.
In addition, the update method of client of the present invention and server sync also comprises step:
Client regularly sends update request to server.
Compared with prior art, the beneficial effect of the update method of client of the present invention and server sync is:
Because server is compared the static catalog of the client of desire renewal and the static catalog of its preservation, the static file of having revised is left under the temp directory, that is to say, what deposit under temp directory is the file that client that desire is upgraded need be upgraded, the file that does not have to revise can not leave under this catalogue, then, server sends to client with the All Files under the temp directory again and upgrades for client, therefore the file of client downloads all is the file of having revised, unmodified file need not to download, reduce the downloading flow that client is upgraded, made downloading flow minimize.
Description of drawings
Fig. 1 is the flow chart of the update method of client of the present invention and server sync;
Fig. 2 is the data in server flow diagram.
Embodiment
As shown in Figure 1, the update method of client of the present invention and server sync comprises:
1) server generates the tabulation of static file and static file with living document and leaves under the static catalog, described living document refers to do the file of renewal, the file of described static file confession under directions client downloads, the static file tabulation refers to deposit static file title and version number, and described static catalog refers to deposit the catalogue of static file and static file tabulation;
2) the described static catalog of a server of client initial back-up;
3) when server regularly detects the source directory of depositing described living document, the living document of revising is regenerated static file and leave under the static catalog, revise its version number simultaneously;
When 4) client was upgraded, the described static file tabulation that it oneself is preserved earlier sent to server;
5) the server described static file tabulation that will receive is compared with the static file tabulation of its preservation, and the static files that version is different are put under the temp directory;
6) server sends to client with the All Files under the described temp directory;
7) client is upgraded according to the file of being received.
From the above, step 1) and 2) be initial phase, at this stage server living document is generated static file, the title and the version number of static file are generated the static file tabulation, static file and static file tabulation are all left under the static catalog, back up the described static catalog of a server in client.That is to say, deposit the static file and the static file tabulation of a server in client.
Server regularly detects the former catalogue of depositing described living document, there is living document to be modified if find, just the living document that will revise regenerates static file, and then the static file that this regenerates left under the static catalog, revise its version number simultaneously, just the version number in the pairing static file tabulation of this static file is made amendment.When client is upgraded, server is issued in the static file tabulation that client is at first preserved it, server is compared its static file of receiving tabulation and the static file tabulation of himself, static file and static file tabulation that version number has changed are left in the temp directory, after the server comparison is finished, client for the desire renewal, what deposit in the server temp directory all is the file that client that desire is upgraded need be upgraded, server sends to client with the All Files in the temp directory then, client is upgraded oneself according to these files, to finish the synchronous of client and server.
For when client upgrade, can adopt dual mode generally speaking, a kind of is send to upgrade prompting to client after server detects the living document of modification, and client sends update request to server after receiving the renewal prompting of server again; A kind of is that client regularly sends update request to server.
As shown in Figure 1, the update method of client of the present invention and server sync comprises that also the step 8) server confirms to empty temp directory after client is received the file of its transmission.
For example: the source directory of depositing living document on server is:
<Root>
|-statement .txt
|-＜news 〉
| | .doc is opened in No. five line time-delays of-Beijing Metro
| | the relevant report .doc of-Beijing day with no cars
|-＜public affair report 〉
|-＜photo-document 〉
Wherein, three files are arranged under the Root catalogue: news, public affair report, photo-document, and a file state .txt.
Two files are arranged under the news catalogs: .doc, the relevant report .doc of Beijing's day with no cars are opened in No. five line time-delays of Beijing Metro.
When therefore, server is initial above-mentioned living document is generated static file:
Statement .txt .doc, the relevant report .doc of Beijing's day with no cars are opened in No. five line time-delays of Beijing Metro
Server will copy above-mentioned static file to static catalog, and sets up the static file tabulation.
The static file of being set up is listed as follows:
/ Root/ states .txt, 2
No. five line time-delays of/Root/ news/Beijing Metro are opened .doc, 1
The relevant report .doc of/Root/ news/Beijing's day with no cars, 5
In the static file tabulation, the order of expression file is like claiming that the back is a version number before ", ".
If added a file in the source directory this moment, " new file .txt " by name is placed on＜Root〉under the catalogue, file state .txt upgrades, and its version number changes 4 into by 2.Server with on detection resources catalogue file after time period once, how detection resources catalogue has once more found under the catalogue file.
Server can copy static catalog to this file (" new file .txt "), and adds the new file .txt of lastrow :/Root/, 1 at last at static list.
Then the static file tabulation can become:
/ Root/ states .txt, 4
No. five line time-delays of/Root/ news/Beijing Metro are opened .doc, 1
The relevant report .doc of/Root/ news/Beijing's day with no cars, 5
The new file .txt of/Root/, 1
If a client proposes synchronous request now, the static file tabulation of uploading to server is such:
/ Root/ states .txt, 2
No. five line time-delays of/Root/ news/Beijing Metro are opened .doc, 1
The relevant report .doc of/Root/ news/Beijing's day with no cars, 5
At this moment, the version of file compared during server can be tabulated content in the static file tabulation of client upload and the static file of oneself.The document copying that needs are synchronous is in temp directory.
Detect static file on the client as, server to pass in the tabulation/FileVersion of Root/ statement .txt is 2, and on the server/and the version of Root/ statement .txt is 4.Server just with the document copying under the static catalog to temp directory.
Server detects on the client does not have the new file .txt of file/Root/ in the static file tabulation, and 1, just copy this document to temp directory.
Server detects in the tabulation of static file on the client/and the version of the relevant report .doc of Root/ news/Beijing's day with no cars is identical, just do not copy files in the temp directory, or the like.
Server was with temp directory after contrast was finished, and packing sends to client, and temp directory is deleted.
As shown in Figure 2, it is data flow at server end, at server end dynamic file data is converted to the static file data, the static file tabulation that server end is uploaded its static file of oneself preserving tabulation and client (perhaps user) compares, different files is left in the temp directory, also can be described as the temporary file data, server is set up a temp directory for each client, and server will be passed to the user after the temporary file packing data more then.
In sum, because server is compared the static catalog of the client of desire renewal and the static catalog of its preservation, the static file of having revised is left under the temp directory, that is to say, what deposit under temp directory is the file that client that desire is upgraded need be upgraded, the file that does not have to revise can not leave under this catalogue, then, server sends to client with the All Files under the temp directory again and upgrades for client, therefore the file of client downloads all is the file of having revised, unmodified file need not to download, and has reduced the downloading flow that client is upgraded, and makes downloading flow minimize.
Claims (3)
1. the update method of client and server sync is characterized in that, comprises step:
Living document is generated static file to server and the static file tabulation is left under the static catalog, described living document refers to do the file of renewal, the file of described static file confession under directions client downloads, the static file tabulation refers to deposit the title of static file and the tabulation of version number, and described static catalog refers to deposit the catalogue of static file and static file tabulation;
The described static catalog of a server of client initial back-up;
When server regularly detects the source directory of depositing described living document, the living document of revising is regenerated static file and leave under the static catalog, revise the version number of static file correspondence described in the static file tabulation simultaneously;
When client was upgraded, the described static file tabulation that it oneself is preserved earlier sent to server;
The described static file tabulation that server will receive is compared with the static file tabulation of its preservation, and static file that version is different and the tabulation of the static file of server end are put under the temp directory;
Server sends to client with the All Files under the described temp directory;
Client is upgraded according to the file of being received;
Server is confirmed to empty described temp directory after client is received the file of its transmission.
2. the update method of client as claimed in claim 1 and server sync is characterized in that, also comprises step:
Server detects behind the living document of modification to send to client and upgrades prompting.
3. the update method of client as claimed in claim 1 and server sync is characterized in that, also comprises step:
Client regularly sends update request to server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101990013A CN101453418B (en) | 2007-12-05 | 2007-12-05 | Updating method for synchronization between customer terminal and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101990013A CN101453418B (en) | 2007-12-05 | 2007-12-05 | Updating method for synchronization between customer terminal and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101453418A CN101453418A (en) | 2009-06-10 |
| CN101453418B true CN101453418B (en) | 2011-01-12 |
Family
ID=40735447
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101990013A Expired - Fee Related CN101453418B (en) | 2007-12-05 | 2007-12-05 | Updating method for synchronization between customer terminal and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101453418B (en) |
Families Citing this family (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102130929A (en) * | 2010-01-20 | 2011-07-20 | 金蝶软件（中国）有限公司 | Method and device for updating client testing server and testing server |
| CN101854395A (en) * | 2010-06-02 | 2010-10-06 | 四川华廷威思信息技术有限公司 | Automatic attachment modifying method based on Web program |
| CN102456027A (en) * | 2010-10-21 | 2012-05-16 | 北京市金蝶政务软件有限公司 | Method, terminals and system for copying files in distributed system |
| CN102480494B (en) * | 2010-11-23 | 2014-04-02 | 金蝶软件（中国）有限公司 | File updating method, device and system |
| CN102073523B (en) * | 2011-01-19 | 2016-07-06 | 中兴通讯股份有限公司 | Realize the method and device of software version synchronization |
| CN102223378B (en) * | 2011-06-28 | 2014-01-29 | 北京新媒传信科技有限公司 | File synchronization method and system |
| CN102289480B (en) * | 2011-08-02 | 2013-05-01 | 深圳市茁壮网络股份有限公司 | Method and system for updating data |
| CN102385614B (en) * | 2011-09-29 | 2014-07-02 | 奇智软件（北京）有限公司 | Terminal file updating management method and system |
| CN102360375B (en) * | 2011-09-29 | 2017-05-31 | 北京奇虎科技有限公司 | A kind of network file update management method and system |
| CN103995894B (en) * | 2011-09-29 | 2017-09-29 | 北京奇虎科技有限公司 | A kind of terminal file updating management method and system |
| CN102404338B (en) * | 2011-12-13 | 2014-08-20 | 华为技术有限公司 | File synchronization method and device |
| CN102591693B (en) * | 2012-01-12 | 2016-05-04 | 北京中广睛彩导航科技有限公司 | A kind of method and device that carries out file update based on CMMB |
| CN102693302B (en) * | 2012-05-21 | 2015-04-22 | 浙江省公众信息产业有限公司 | Quick file comparison method, system and client side |
| CN102811260B (en) * | 2012-08-10 | 2015-04-15 | 清华大学 | File cloud synchronizing system and method |
| CN103841167A (en) * | 2012-11-27 | 2014-06-04 | 中国移动通信集团公司 | User data synchronizing method and device |
| CN103326929B (en) * | 2013-06-24 | 2017-02-08 | 小米科技有限责任公司 | Method and device for transmitting messages |
| CN103595707A (en) * | 2013-10-17 | 2014-02-19 | 广东电网公司茂名供电局 | Automatic file network synchronization method based on SVN |
| CN105205010A (en) * | 2014-06-03 | 2015-12-30 | 上海联影医疗科技有限公司 | Basic data caching method and device |
| CN105549996B (en) * | 2015-12-10 | 2020-03-17 | 网易（杭州）网络有限公司 | Application program updating method of mobile terminal and mobile terminal |
| CN105786574B (en) * | 2016-03-17 | 2019-01-22 | 武汉华星光电技术有限公司 | CIM system client method for updating edition and more new system based on VDI group |
| CN108449415A (en) * | 2018-03-27 | 2018-08-24 | 深圳中兴网信科技有限公司 | Method of data synchronization, data synchronization unit, computer equipment and storage medium |
| CN109246245A (en) * | 2018-10-31 | 2019-01-18 | 武汉新迪数字工程系统有限公司 | Realize method, server, system and the storage medium of file synchronization |
| CN110430287A (en) * | 2019-08-30 | 2019-11-08 | 湖北楚天高速智能产业研究院有限公司深圳分公司 | A kind of mobile terminal data synchronous method and system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1493982A (en) * | 2002-10-31 | 2004-05-05 | 鼎新电脑股份有限公司 | Method of on line rapid automatic renew |
| WO2005045671A1 (en) * | 2003-10-27 | 2005-05-19 | American Power Conversion Corporation | System and method for updating a software program |
| CN1635021A (en) * | 2004-12-08 | 2005-07-06 | 中国科学院长春应用化学研究所 | Process for increasing polyolefin nano composite material through catalytic charcoal forming |
| CN1786903A (en) * | 2004-12-11 | 2006-06-14 | 鸿富锦精密工业（深圳）有限公司 | System and method for synchronously renewing file of remote computer |
| CN1801087A (en) * | 2004-12-31 | 2006-07-12 | 英业达股份有限公司 | Synchronous updating system and method for data and application |
| EP1410202B1 (en) * | 2001-03-16 | 2006-07-26 | Novell, Inc. | Client-server model for synchronization of files |
| CN1863050A (en) * | 2005-09-15 | 2006-11-15 | 上海华为技术有限公司 | Method of document synchronization between server and system thereof |
| CN1914601A (en) * | 2004-01-27 | 2007-02-14 | 皇家飞利浦电子股份有限公司 | Audio/video content synchronization through playlists |
-
2007
- 2007-12-05 CN CN2007101990013A patent/CN101453418B/en not_active Expired - Fee Related
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1410202B1 (en) * | 2001-03-16 | 2006-07-26 | Novell, Inc. | Client-server model for synchronization of files |
| CN1493982A (en) * | 2002-10-31 | 2004-05-05 | 鼎新电脑股份有限公司 | Method of on line rapid automatic renew |
| WO2005045671A1 (en) * | 2003-10-27 | 2005-05-19 | American Power Conversion Corporation | System and method for updating a software program |
| CN1914601A (en) * | 2004-01-27 | 2007-02-14 | 皇家飞利浦电子股份有限公司 | Audio/video content synchronization through playlists |
| CN1635021A (en) * | 2004-12-08 | 2005-07-06 | 中国科学院长春应用化学研究所 | Process for increasing polyolefin nano composite material through catalytic charcoal forming |
| CN1786903A (en) * | 2004-12-11 | 2006-06-14 | 鸿富锦精密工业（深圳）有限公司 | System and method for synchronously renewing file of remote computer |
| CN1801087A (en) * | 2004-12-31 | 2006-07-12 | 英业达股份有限公司 | Synchronous updating system and method for data and application |
| CN1863050A (en) * | 2005-09-15 | 2006-11-15 | 上海华为技术有限公司 | Method of document synchronization between server and system thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101453418A (en) | 2009-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101453418B (en) | Updating method for synchronization between customer terminal and server | |
| US10911518B2 (en) | Network folder synchronization | |
| CN103942058B (en) | A kind of EMBEDDED AVIONICS method for upgrading software and system | |
| CN106156359B (en) | A kind of data synchronization updating method under cloud computing platform | |
| CN102129378B (en) | A kind of software menu updating method and device | |
| CN101160903B (en) | Method, system, client terminal and server for implementing data synchronization | |
| US20070168721A1 (en) | Method, network entity, system, electronic device and computer program product for backup and restore provisioning | |
| CN102480520B (en) | Media data synchronism method based on differential metadata description structure | |
| WO2001097071A3 (en) | File system for distributing content in a data network and related method | |
| EP2157758A1 (en) | Data soft deletion, recovery and synchronization method, terminal and system thereof | |
| CN103297459A (en) | Synchronizing system of application configuration information, access server, clients and synchronizing method of application configuration information | |
| CN101567858A (en) | Method and system for synchronizing data | |
| CN109814902A (en) | A kind of configuration file update method, device, electronic equipment and storage medium | |
| CN102833350A (en) | Processing method and processing device of WebApp updating | |
| CN104881604B (en) | The operation method and device of version file | |
| CN103098487A (en) | Broadcast content transmitting device, and broadcast content receiving device | |
| CN105635277A (en) | Upgrade packet providing method and device and client side upgrade method and device | |
| CN103605798A (en) | Method for directly operating file stored at cloud end | |
| CN103793482A (en) | Data synchronization method and system | |
| CN101420324B (en) | Network management system and version renovating method for proxy software | |
| CN102238197A (en) | Mobile reading multi-screen synchronization method | |
| CN101977217A (en) | Widget updating method and system as well as Widget client and Widget server | |
| CN103841180A (en) | Network data synchronization method and device based on operating instruction, terminal device and server | |
| CN103037005A (en) | File synchronization method and device of on-line storage service | |
| CN101656739A (en) | Method, system and equipment for updating assembly |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200512 Address after: 310052 room 508, floor 5, building 4, No. 699, Wangshang Road, Changhe street, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Alibaba (China) Co.,Ltd. Address before: 102200, No. 18, Changsheng Road, Changping District science and Technology Park, Beijing, B1 Patentee before: AUTONAVI SOFTWARE Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110112 Termination date: 20201205 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |