CN103916373A - Data updating method, server, client side and system - Google Patents
Data updating method, server, client side and system Download PDFInfo
- Publication number
- CN103916373A CN103916373A CN201310005204.XA CN201310005204A CN103916373A CN 103916373 A CN103916373 A CN 103916373A CN 201310005204 A CN201310005204 A CN 201310005204A CN 103916373 A CN103916373 A CN 103916373A
- Authority
- CN
- China
- Prior art keywords
- data
- flag bit
- update request
- client
- server
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a data updating method, a server, a client side and a system and relates to the technical field of network communication. By the adoption of the data updating method, the server, the client side and the system, the problem that flow is waste when the content of a web page is refreshed can be solved. The data updating method comprises the steps that the server receives a data updating request sent by the client side, wherein the data updating request is used for requesting updating of first data and contains an updating identification of the first data; whether the updating identification of the first data is identical with an updating identification of second data is judged, wherein the second data are updating data corresponding to the first data; an updating identification bit is sent to the client side according to a judgment result, wherein the updating identification bit is used for indicating whether the second data are identical with the first data. The data updating method, the server, the client side and the system are mainly used for web page refreshing.
Description
Technical field
The present invention relates to network communications technology field, relate in particular to a kind of method, server, client and system of Data Update.
Background technology
At present, the client such as mobile phone, panel computer can be upgraded the data content having obtained.For example, client is obtained and display web page content by browser, and when receiving while refreshing instruction, client sends Data Update request to network side server, obtains the web page contents after renewal, then the web page contents after upgrading is shown.
In the process of Data Update, client receives at every turn and refreshes the web page contents that all needs to obtain to network side server renewal after instruction, in the time that network side server does not produce more new data, the renewal web page contents that client arrives is identical with the web page contents of current demonstration.Client repeats to receive identical web page contents can waste surfing flow, causes unnecessary flow expense.
Summary of the invention
The embodiment of the present invention provides a kind of method, server, client and system of Data Update, the problem of wasting flow can solve refreshed web page content time.
First aspect, the embodiment of the present invention provides a kind of method of Data Update, comprising:
Server receives the Data Update request that client sends, and described Data Update request is used for asking to upgrade the first data, carries the more new logo of described the first data in described Data Update request;
Whether the more new logo that judges described the first data is identical with the more new logo of the second data that find, and wherein said the second data are the more new data of corresponding described the first data;
Send and upgrade flag bit to described client according to judged result, whether described renewal flag bit is used for characterizing described the second data identical with described the first data.
Second aspect, the embodiment of the present invention also provides a kind of method of Data Update, comprising:
Client generated data update request, described Data Update request is used for asking to upgrade the first data, carries the more new logo of described the first data in described Data Update request;
Described Data Update request is sent to server, so that described server judges that according to described Data Update request whether described the first data are identical with the second data, wherein said the second data are the more new data of described the first data;
Receive the renewal flag bit that described server sends, and show the more new data of described the first data according to described renewal flag bit, whether described renewal flag bit is used for characterizing described the first data identical with described the second data.
The third aspect, the embodiment of the present invention also provides a kind of server, comprising:
Receiving element, the Data Update request sending for receiving client, described Data Update request is used for asking to upgrade the first data, carries the more new logo of described the first data in described Data Update request;
Judging unit, whether identical with the more new logo of the second data that find for judging the more new logo of described the first data that described receiving element receives, wherein said the second data are the more new data of described the first data of correspondence;
Transmitting element, for sending and upgrade flag bit to described client according to the judged result of described judging unit, whether described renewal flag bit is used for characterizing described the second data identical with described the first data.
Fourth aspect, the embodiment of the present invention also provides a kind of client, comprising:
Processing unit, for generated data update request, described Data Update request is used for asking to upgrade the first data, carries the more new logo of described the first data in described Data Update request;
Transmitting element, send to server for the described Data Update request that described processing unit is generated, so that described server judges that according to described Data Update request whether described the first data are identical with the second data, wherein said the second data are the more new data of described the first data;
Receiving element, the renewal flag bit sending for receiving described server;
Display unit, for show the more new data of described the first data according to the described renewal flag bit of described receiving element reception, whether described renewal flag bit is used for characterizing described the first data identical with described the second data.
The 5th aspect, the embodiment of the present invention provides a kind of system of Data Update, comprising: server and client side, wherein,
Described client, for generated data update request, described Data Update request is used for asking to upgrade the first data, in described Data Update request, carry the more new logo of described the first data, described Data Update request is sent to described server, and wherein said the second data are the more new data of described the first data;
Described server, the described Data Update request sending for receiving described client, whether the more new logo that judges described the first data is identical with the more new logo of the second data that find, send and upgrade flag bit to described client according to judged result, whether described renewal flag bit is used for characterizing described the second data identical with described the first data;
Described client, for receiving the described renewal flag bit of described server transmission, and shows the more new data of described the first data according to described renewal flag bit, whether described renewal flag bit is used for characterizing described the first data identical with described the second data.
Method, server, client and the system of the Data Update that the embodiment of the present invention provides, can be in client-requested during to the first Data Update of current demonstration, the more new logo of the first data is carried in Data Update request and sends to server, and whether the more new logo of server comparison the first data is identical with the more new logo of the second data that find.Server sends for characterizing the renewal flag bit whether described the second data are identical with described the first data to client, so that client is according to the more new data of indicated number first data of renewal flag bit.When not new data more of the first data, the first data are with the second data when identical, and server only returns to sign the first data renewal flag bit identical with the second data to client.Only take one or several bit owing to upgrading flag bit, so with in prior art when the first data are not more when new data, server will second data identical with the first data send to client to compare, can be in the process of new data more, avoid server to repeat to send identical data to client, save the flow of client refreshes webpage.
Brief description of the drawings
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the method flow diagram of Data Update in the embodiment of the present invention;
Fig. 2 is the method flow diagram of another Data Update in the embodiment of the present invention;
Fig. 3 is the structural representation of server in the embodiment of the present invention;
Fig. 4 is the structural representation of client in the embodiment of the present invention;
Fig. 5 is the system schematic of Data Update in the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiment.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
For solving in the time there is no new more new data, server sends to the problem of the waste client traffic that client causes using legacy data as new data more, and the embodiment of the present invention provides a kind of method of Data Update, and the method is applied to server side.As shown in Figure 1, described method comprises:
101, server receives the Data Update request that client sends.
Described Data Update request is used for asking to upgrade the first data, and these the first data are the page data of the current demonstration of client, is also the object of Data Update.In described Data Update request, carry the more new logo of the first data.Described more new logo is for carrying out unique identification to the more new state of the first data, this more new logo generated by server, and together send to client with the first data.When each Data Update, server can be all the more new logo of one of data allocations after upgrading, this more new logo can but to be not limited only to be at least one in following mark: the Hash HASH keyword of the update time of data, the MD5 value of data, data, the renewal numbering of data or the current version number of data.The embodiment of the present invention follow-up update time using data describes as new logo more.
102, server judges that whether the more new logo of the first data is identical with the more new logo of the second data that find.
Described the second data are the more new data of corresponding the first data.Server is the latest update data to corresponding the first data according to the URL(uniform resource locator) in Data Update request (Universal Resource Locator is called for short URL) address search, and these latest update data are described the second data.Server is finding after the second data, obtains the time of the second data last update, as the more new logo of the second data, the more new logo of the more new logo of the second data and the first data is compared, and judges that whether both are identical.
103, server sends and upgrades flag bit to client according to judged result.
Whether described renewal flag bit is used for characterizing the second data identical with the first data.When the more new logo of the second data and the first data more new logo is identical time, represent that the renewal version of the second data is identical with the renewal version of the first data, the second data are identical with the first data, in the time that the more new logo of the second data is not identical with the more new logo of the first data, represent that the second data are not identical with the first data.
Described renewal flag bit can be several binary bytes, and for example upgrading flag bit is a binary byte, and this binary system byte is that 1 sign the second data are identical with the first data, and this binary system byte is that 0 sign the second data are not identical with the first data.Or this binary system byte is that 0 sign the second data are identical with the first data, this binary system byte is that 1 sign the second data are not identical with the first data.
Whether renewal flag bit instruction client the second data that server sends a binary system byte to client are identical with the first data.If both are identical, client shows the first data of buffer memory (i.e. the more new data of the first data or the first data), if both are not identical, and the second data that client display server send.
When the judged result of step 102 is the more new logo of the first data when not identical with the more new logo of the second data, server sends the more new logo of the second data and the second data to client.
Concrete, if judged result for both are not identical, the more new data of server using the second data as the first data sends to client, so that client is carried out buffer memory and demonstration to the second data.And server also sends to client by the more new logo of the second data (being the last update time), so that the more new logo of the second data is sent to server by client (request is upgraded the second data) in the time of upper once Data Update request.
In embodiments of the present invention, server is more new logo of one of the data allocations that finds, in the time of client-requested Data Update, obtain the more new logo of data to be updated in Data Update request (the first data), then after judging data to be updated (the first data) and upgrading, whether data (the second data) are identical, then server sends one for the whether identical renewal flag bit of data after characterizing data to be updated and upgrading to client, in the time that data to be updated are identical with data after renewal, server does not repeat to send identical data content to client.And in the prior art, server is getting after the Data Update request that client sends, search upgrade after data, all just upgrade rear data and send to client no matter whether data identical with data to be updated after upgrading.The method of the Data Update that the embodiment of the present invention provides compared with prior art, can be in the time that data to be updated be identical with data after renewal, and server does not repeat to send identical data content to client, upgrades flag bit but only send one.Only occupy one or several byte owing to upgrading flag bit, so for repeating to send same data content, can save a large amount of flow expenses for client.
For solving in the time there is no new more new data, the problem of the waste client traffic that the more new data that client is identical with legacy data causes, the embodiment of the present invention also provides a kind of method of Data Update, and the method is applied to client-side.As shown in Figure 2, described method comprises:
201, client generated data update request.
Described Data Update request is used for asking to upgrade the first data, and these the first data are the page data of the current demonstration of client, is also the object of Data Update.In described Data Update request, carry the more new logo of the first data.Described more new logo is for carrying out unique identification to the more new state of the first data, this more new logo generated by server, and together send to client with the first data.When each Data Update, server can be all the more new logo of one of data allocations after upgrading, the first Data Update mark that client is added in the time of generated data update request is while once obtaining more new data (the first data), and server sends to the more new logo of client.Described more new logo can but to be not limited only to be at least one in following mark: the Hash HASH keyword of the update time of data, the MD5 value of data, data, the renewal numbering of data or the current version number of data.The embodiment of the present invention follow-up update time using data describes as new logo more.
202, Data Update request is sent to server by client.
Data Update request is sent to server by client, so that server judges that according to the more new logo of the first data in Data Update request whether the first data are identical with the second data, wherein the second data are the more new data of the first data of arriving of whois lookup.
Server is the second data to corresponding the first data according to the URL address search in Data Update request, then obtain the time of the second data last update, as the more new logo of the second data, the more new logo of the more new logo of the second data and the first data is compared, judge that whether both are identical.Server sends for characterizing the renewal flag bit whether the first data are identical with the second data to client according to judged result, this renewal flag bit can be several binary bytes, for example upgrading flag bit is a binary byte, this binary system byte is that 1 sign the second data are identical with the first data, and this binary system byte is that 0 sign the second data are not identical with the first data.Or this binary system byte is that 0 sign the second data are identical with the first data, this binary system byte is that 1 sign the second data are not identical with the first data.
203, the renewal flag bit that client server sends, and show the more new data of the first data according to upgrading flag bit.
Characterize the first data with the second data when identical when upgrading flag bit, client shows the first data of buffer memory as upgrading data afterwards; Characterize the first data when not identical with the second data when upgrading flag bit, the second data that client server sends and the more new logo of the second data, then the second data are carried out to buffer memory and demonstration, and preserve the more new logo of the second data, in the time again asking more new data (request is upgraded the second data), client sends to server according to the more new logo generated data update request of the second data that receive.
In embodiments of the present invention, server is more new logo of one of the data allocations that finds, in the time of client-requested Data Update, whether the more new logo of data to be updated (the first data) is sent to server by client, identical so that server judges data to be updated and upgrades rear data (the second data).Then client server send for characterizing data to be updated and upgrading the renewal flag bit that afterwards whether data identical, characterize both when identical if upgrade flag bit, the data to be updated of buffer memory are shown to user by client, characterize both when not identical if upgrade flag bit, the more new logo of data after data and renewal after the renewal that client server sends, and carry out buffer memory and demonstration to upgrading rear data, simultaneously after storage update the more new logo of data to use when request is upgraded next time.And in the prior art, no matter whether data identical with data to be updated after the renewal that whois lookup arrives, client all can receive server send renewal after data.The method of the Data Update that the embodiment of the present invention provides compared with prior art, can be in the time that data to be updated be identical with data after renewal, and client does not repeat the identical data content that reception server sends, and upgrades flag bit but only receive one.Only occupy one or several byte owing to upgrading flag bit, so for repeating to receive same data content, client can be saved a large amount of flow expenses.
In an application scenarios of the embodiment of the present invention, the data content of user end to server request site home page, server obtains this homepage data content and this homepage last update time 14:00, the homepage content obtaining is sent to client, and send to client using this homepage last update time as new logo more.User carries out homepage refresh operation having browsed after this homepage content, client generated data update request, and 14:05 more new logo 14:00 send to server.Server receives after Data Update request, according to the URL address search in Data Update request to this homepage, and the last update time that gets this homepage be 14:03.Server relatively update time 14:00 with update time 14:03 not identical, send and upgrade flag bit 1 to client, and by the homepage data content of 14:03 renewal and update time 14:03 send to client.Client is to upgrading after flag bit 1, and the homepage data content that 14:03 is upgraded carries out buffer memory and demonstration, and preserves more new logo 14:03.
User carries out homepage refresh operation for the second time having browsed after this homepage content, client generated data update request, and 14:10 more new logo 14:03 send to server.Server receives after Data Update request, according to the URL address search in Data Update request to this homepage, and the last update time that gets this homepage be still 14:03, do not upgrade to this homepage data content during 14:10 at 14:03.14:03 update time in server comparing data update request is identical with 14:03 update time of the homepage data content getting, and sends and upgrades flag bit 0 to client.Client, to upgrading after flag bit 0, shows the homepage data content that the 14:03 of buffer memory upgrades.
In the Another application scene of the embodiment of the present invention, the renewal of data is designated the current version number of data content.The data content of user end to server request site home page, server obtains the current version Ver1.0 of this homepage data content and this homepage, the homepage content obtaining is sent to client, and send to client using the current version Ver1.0 of this homepage as new logo more.User carries out homepage refresh operation having browsed after this homepage content, client generated data update request, and more new logo Ver1.0 sends to server.Server receives after Data Update request, and according to the URL address search in Data Update request, to this homepage, and the current version number that gets this homepage is Ver1.1.Server more more new logo Ver1.0 with more new logo Ver1.1 is not identical, to client send upgrade flag bit 1, and the homepage data content that is Ver1.1 by version number and more new logo Ver1.1 send to client.Client is to upgrading after flag bit 1, and the homepage data content that is Ver1.1 to version number carries out buffer memory and demonstration, and preserves more new logo Ver1.1.
User carries out homepage refresh operation for the second time having browsed after this homepage content, client generated data update request, and more new logo Ver1.1 sends to server.Server receives after Data Update request, and according to the URL address search in Data Update request, to this homepage, and the current version number that gets this homepage is still Ver1.1, and this homepage data content does not upgrade.More new logo Ver1.1 in server comparing data update request is identical with the more new logo Ver1.1 getting, and sends and upgrades flag bit 0 to client.Client, to upgrading after flag bit 0, shows the homepage data content that the version number of buffer memory is Ver1.1.
With reference to the realization of method shown in figure 1, the embodiment of the present invention also provides a kind of server, in order to realize the method shown in Fig. 1.As shown in Figure 3, described server comprises: receiving element 31, judging unit 32 and transmitting element 33, wherein,
Described receiving element 31, the Data Update request sending for receiving client, described Data Update request is used for asking to upgrade the first data, in described Data Update request, carry the more new logo of described the first data, described more new logo can but to be not limited only to be at least one in following mark: the Hash HASH keyword of the update time of data, the MD5 value of data, data, the renewal numbering of data or the current version number of data.
Described judging unit 32, whether identical with the more new logo of the second data that find for judging the more new logo of described the first data that described receiving element 31 receives, wherein said the second data are the more new data of corresponding described the first data;
Described transmitting element 33, for sending and upgrade flag bit to described client according to the judged result of described judging unit 32, whether described renewal flag bit is used for characterizing described the second data identical with described the first data.
Further, described transmitting element 33 also for:
When the described judged result of described judging unit 32 is the more new logo of described the first data when not identical with the more new logo of described the second data, send the more new logo of described the second data and described the second data to described client.
Further, the renewal flag bit that described transmitting element 33 sends can be several binary bytes, for example upgrading flag bit is a binary byte, this binary system byte is that 1 sign the second data are identical with the first data, and this binary system byte is that 0 sign the second data are not identical with the first data.Or this binary system byte is that 0 sign the second data are identical with the first data, this binary system byte is that 1 sign the second data are not identical with the first data.
The server that the embodiment of the present invention provides, can during to the first Data Update of current demonstration, receive the Data Update request of the more new logo that carries the first data in client-requested.Whether the more new logo of server comparison the first data is identical with the more new logo of the second data that find.Server sends for characterizing the renewal flag bit whether described the second data are identical with described the first data to client, so that client is according to the more new data of indicated number first data of renewal flag bit.When not new data more of the first data, the first data are with the second data when identical, and server only returns to sign the first data renewal flag bit identical with the second data to client.Only take one or several bit owing to upgrading flag bit, so with in prior art when the first data are not more when new data, server will second data identical with the first data send to client to compare, can be in the process of new data more, avoid server to repeat to send identical data to client, save the flow of refreshed web page.
With reference to the realization of method shown in figure 2, the embodiment of the present invention also provides a kind of client, in order to realize the method shown in Fig. 2.As shown in Figure 4, described client comprises: processing unit 41, transmitting element 42, receiving element 43, display unit 44 and memory cell 45, wherein,
Described processing unit 41, for generated data update request, described Data Update request is used for asking to upgrade the first data, in described Data Update request, carry the more new logo of described the first data, described more new logo can but to be not limited only to be at least one in following mark: the Hash HASH keyword of the update time of data, the MD5 value of data, data, the renewal numbering of data or the current version number of data.
Described transmitting element 42, send to server for the described Data Update request that described processing unit 41 is generated, so that described server judges that according to described Data Update request whether described the first data are identical with the second data, wherein said the second data are the more new data of described the first data;
Described receiving element 43, the renewal flag bit sending for receiving described server;
Described display unit 44, shows the more new data of described the first data for the described renewal flag bit receiving according to described receiving element 43, whether described renewal flag bit is used for characterizing described the first data identical with described the second data.
Further, described receiving element 43 also for: in the time that described the first data are not identical with described the second data, receive described the second data that described server sends and the more new logo of described the second data.
Further, described memory cell 45, described the second data that receive for the first data described in buffer memory and described receiving element 43;
Described display unit 44 for:
The described renewal flag bit receiving when described receiving element 43 characterizes described the first data and when identical, reads and show described first data of described memory cell 45 buffer memorys with described the second data;
The described renewal flag bit receiving when described receiving element 43 characterizes described the first data when not identical with described the second data, reads and show described second data of described memory cell 45 buffer memorys.
Further, described processing unit 41 also for:
The more new logo of described the second data that receive according to described receiving element 43 generates the Data Update request of Data Update next time.
Further, the renewal flag bit that described receiving element 43 receives can be several binary bytes, for example upgrading flag bit is a binary byte, this binary system byte is that 1 sign the second data are identical with the first data, and this binary system byte is that 0 sign the second data are not identical with the first data.Or this binary system byte is that 0 sign the second data are identical with the first data, this binary system byte is that 1 sign the second data are not identical with the first data.
The client that the embodiment of the present invention provides, can be in request during to the first Data Update of current demonstration, send the Data Update request of the more new logo that carries the first data to server, so that whether the more new logo of server comparison the first data is identical with the more new logo of the second data that find.Reception server send for characterizing the renewal flag bit whether described the second data identical with described the first data, then according to the more new data of indicated number the first data of renewal flag bit.When not new data more of the first data, the first data are with the second data when identical, client sign the first data renewal flag bit identical with the second data that only reception server sends.Only take one or several bit owing to upgrading flag bit, so with in prior art when the first data are not more when new data, client second data identical with the first data that still reception server sends are compared, can be in the process of new data more, avoid client to repeat to receive identical data, save the flow of client refreshes webpage.
In embodiments of the present invention, the client shown in Fig. 4 is the subscriber equipment (User Equipment is called for short UE) with network connecting function, such as portable computer etc., and the embodiment of the present invention does not limit the concrete form of client.
With reference to the realization of method shown in figure 1 and Fig. 2, the embodiment of the present invention also provides a kind of system of Data Update, in order to realize the method shown in Fig. 1 and Fig. 2.As shown in Figure 5, described system comprises server 51 and client 52, wherein,
Described client 52, for generated data update request, described Data Update request is used for asking to upgrade the first data, in described Data Update request, carry the more new logo of described the first data, described more new logo can but to be not limited only to be at least one in following mark: the Hash HASH keyword of the update time of data, the MD5 value of data, data, the renewal numbering of data or the current version number of data; Described Data Update request is sent to described server 51, and wherein said the second data are the more new data of described the first data;
Described server 51, for receiving the described Data Update request that described client 52 sends, whether the more new logo that judges described the first data is identical with the more new logo of the second data that find, send and upgrade flag bit to described client 52 according to judged result, whether described renewal flag bit is used for characterizing described the second data identical with described the first data;
Described client 52, the described renewal flag bit sending for receiving described server 51, and show the more new data of described the first data according to described renewal flag bit, whether described renewal flag bit is used for characterizing described the first data identical with described the second data.
Further, described renewal flag bit can be several binary bytes, for example upgrading flag bit is a binary byte, and this binary system byte is that 1 sign the second data are identical with the first data, and this binary system byte is that 0 sign the second data are not identical with the first data.Or this binary system byte is that 0 sign the second data are identical with the first data, this binary system byte is that 1 sign the second data are not identical with the first data.
The system of the Data Update that the embodiment of the present invention provides, can be in request during to the first Data Update of current demonstration, send the Data Update request of the more new logo that carries the first data to server, so that whether the more new logo of server comparison the first data is identical with the more new logo of the second data that find.Reception server send for characterizing the renewal flag bit whether described the second data identical with described the first data, then according to the more new data of indicated number the first data of renewal flag bit.When not new data more of the first data, the first data are with the second data when identical, client sign the first data renewal flag bit identical with the second data that only reception server sends.Only take one or several bit owing to upgrading flag bit, so with in prior art when the first data are not more when new data, client second data identical with the first data that still reception server sends are compared, can be in the process of new data more, avoid client to repeat to receive identical data, save the flow of client refreshes webpage.
Through the above description of the embodiments, those skilled in the art can be well understood to the mode that the present invention can add essential common hardware by software and realize, and can certainly pass through hardware, but in a lot of situation, the former is better execution mode.Based on such understanding, the part that technical scheme of the present invention contributes to prior art in essence in other words can embody with the form of software product, this computer software product is stored in the storage medium can read, as the floppy disk of computer, hard disk or CD etc., comprise that some instructions are in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) carry out the method described in each embodiment of the present invention.
The above; be only the specific embodiment of the present invention, but protection scope of the present invention is not limited to this, any be familiar with those skilled in the art the present invention disclose technical scope in; can expect easily changing or replacing, within all should being encompassed in protection scope of the present invention.Therefore, protection scope of the present invention should described be as the criterion with the protection range of claim.
Claims (17)
1. a method for Data Update, is characterized in that, comprising:
Server receives the Data Update request that client sends, and described Data Update request is used for asking to upgrade the first data, carries the more new logo of described the first data in described Data Update request;
Whether the more new logo that judges described the first data is identical with the more new logo of the second data that find, and wherein said the second data are the more new data of corresponding described the first data;
Send and upgrade flag bit to described client according to judged result, whether described renewal flag bit is used for characterizing described the second data identical with described the first data.
2. method according to claim 1, is characterized in that, described method further comprises:
When described judged result is the more new logo of described the first data when not identical with the more new logo of described the second data, send the more new logo of described the second data and described the second data to described client.
3. method according to claim 1 and 2, it is characterized in that, the renewal of described first, second data is designated at least one in following mark: the Hash HASH keyword of the update time of data, the MD5 value of data, data, the renewal numbering of data or the current version number of data.
4. method according to claim 3, it is characterized in that, described renewal flag bit is a binary system byte, described binary system byte is that described the second data of 1 sign are identical with described the first data, described binary system byte is that described the second data of 0 sign are not identical with described the first data, or described binary system byte is that described the second data of 0 sign are identical with described the first data, described binary system byte is that described the second data of 1 sign are not identical with described the first data.
5. a method for Data Update, is characterized in that, comprising:
Client generated data update request, described Data Update request is used for asking to upgrade the first data, carries the more new logo of described the first data in described Data Update request;
Described Data Update request is sent to server, so that described server judges that according to described Data Update request whether described the first data are identical with the second data, wherein said the second data are the more new data of described the first data;
Receive the renewal flag bit that described server sends, and show the more new data of described the first data according to described renewal flag bit, whether described renewal flag bit is used for characterizing described the first data identical with described the second data.
6. method according to claim 5, is characterized in that, described method further comprises:
In the time that described the first data are not identical with described the second data, receive described second data of described server transmission and the more new logo of described the second data.
7. method according to claim 6, is characterized in that, the described more new data that shows described the first data according to described renewal flag bit, comprising:
When described renewal flag bit characterizes described the first data with described the second data when identical, read and show described first data of buffer memory;
When described renewal flag bit characterizes described the first data when not identical with described the second data, buffer memory also shows described the second data that receive.
8. method according to claim 6, is characterized in that, described generated data update request, comprising:
Generate the Data Update request of Data Update next time according to the more new logo of described the second data.
9. according to the method described in any one in claim 5 to 8, it is characterized in that, the renewal of described first, second data is designated at least one in following mark: the Hash HASH keyword of the update time of data, the MD5 value of data, data, the renewal numbering of data or the current version number of data.
10. method according to claim 9, it is characterized in that, described renewal flag bit is a binary system byte, described binary system byte is that described the second data of 1 sign are identical with described the first data, described binary system byte is that described the second data of 0 sign are not identical with described the first data, or described binary system byte is that described the second data of 0 sign are identical with described the first data, described binary system byte is that described the second data of 1 sign are not identical with described the first data.
11. 1 kinds of servers, is characterized in that, comprising:
Receiving element, the Data Update request sending for receiving client, described Data Update request is used for asking to upgrade the first data, carries the more new logo of described the first data in described Data Update request;
Judging unit, whether identical with the more new logo of the second data that find for judging the more new logo of described the first data that described receiving element receives, wherein said the second data are the more new data of described the first data of correspondence;
Transmitting element, for sending and upgrade flag bit to described client according to the judged result of described judging unit, whether described renewal flag bit is used for characterizing described the second data identical with described the first data.
12. servers according to claim 11, is characterized in that, described transmitting element also for:
When the described judged result of described judging unit is the more new logo of described the first data when not identical with the more new logo of described the second data, send the more new logo of described the second data and described the second data to described client.
13. 1 kinds of clients, is characterized in that, comprising:
Processing unit, for generated data update request, described Data Update request is used for asking to upgrade the first data, carries the more new logo of described the first data in described Data Update request;
Transmitting element, send to server for the described Data Update request that described processing unit is generated, so that described server judges that according to described Data Update request whether described the first data are identical with the second data, wherein said the second data are the more new data of described the first data;
Receiving element, the renewal flag bit sending for receiving described server;
Display unit, for show the more new data of described the first data according to the described renewal flag bit of described receiving element reception, whether described renewal flag bit is used for characterizing described the first data identical with described the second data.
14. clients according to claim 13, is characterized in that, described receiving element also for:
In the time that described the first data are not identical with described the second data, receive described second data of described server transmission and the more new logo of described the second data.
15. clients according to claim 14, is characterized in that, described client further comprises:
Memory cell, for described second data of the first data described in buffer memory and the reception of described receiving element;
Described display unit is used for:
The described renewal flag bit receiving when described receiving element characterizes described the first data and when identical, reads and show described first data of described memory cell buffer memory with described the second data;
The described renewal flag bit receiving when described receiving element characterizes described the first data when not identical with described the second data, reads and show described second data of described memory cell buffer memory.
16. clients according to claim 14, is characterized in that, described processing unit also for:
The more new logo of described the second data that receive according to described receiving element generates the Data Update request of Data Update next time.
The system of 17. 1 kinds of Data Update, is characterized in that, comprising: server and client side, wherein,
Described client, for generated data update request, described Data Update request is used for asking to upgrade the first data, in described Data Update request, carry the more new logo of described the first data, described Data Update request is sent to described server, and wherein said the second data are the more new data of described the first data;
Described server, the described Data Update request sending for receiving described client, whether the more new logo that judges described the first data is identical with the more new logo of the second data that find, send and upgrade flag bit to described client according to judged result, whether described renewal flag bit is used for characterizing described the second data identical with described the first data;
Described client, for receiving the described renewal flag bit of described server transmission, and shows the more new data of described the first data according to described renewal flag bit, whether described renewal flag bit is used for characterizing described the first data identical with described the second data.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310005204.XA CN103916373A (en) | 2013-01-07 | 2013-01-07 | Data updating method, server, client side and system |
| PCT/CN2013/088271 WO2014106417A1 (en) | 2013-01-07 | 2013-12-02 | Method, server, client and system for updating data |
| US14/305,419 US20140298313A1 (en) | 2013-01-07 | 2014-06-16 | Method, server, client and system for updating data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310005204.XA CN103916373A (en) | 2013-01-07 | 2013-01-07 | Data updating method, server, client side and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103916373A true CN103916373A (en) | 2014-07-09 |
Family
ID=51041780
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310005204.XA Pending CN103916373A (en) | 2013-01-07 | 2013-01-07 | Data updating method, server, client side and system |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US20140298313A1 (en) |
| CN (1) | CN103916373A (en) |
| WO (1) | WO2014106417A1 (en) |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104702703A (en) * | 2015-03-30 | 2015-06-10 | 北京奇艺世纪科技有限公司 | Method and device for updating data |
| CN104811394A (en) * | 2015-04-21 | 2015-07-29 | 深圳市出众网络有限公司 | Method and system for saving traffic for accessing server |
| CN105550346A (en) * | 2015-12-25 | 2016-05-04 | 北京奇虎科技有限公司 | Information management method and device |
| CN105634801A (en) * | 2015-12-25 | 2016-06-01 | 北京奇虎科技有限公司 | Data updating method and device |
| CN105868251A (en) * | 2015-12-22 | 2016-08-17 | 乐视云计算有限公司 | Cache data updating method and device |
| CN105893607A (en) * | 2016-04-25 | 2016-08-24 | 青岛海信传媒网络技术有限公司 | Page data management method, device and data server |
| CN105939355A (en) * | 2016-06-13 | 2016-09-14 | 乐视控股（北京）有限公司 | Data access method and system, as well as client and server |
| CN106549983A (en) * | 2015-09-16 | 2017-03-29 | ***通信集团公司 | The access method and terminal of a kind of database, server |
| CN106878370A (en) * | 2016-09-19 | 2017-06-20 | 阿里巴巴集团控股有限公司 | The update method and equipment of a kind of local cache |
| CN106897444A (en) * | 2017-03-01 | 2017-06-27 | 郑州云海信息技术有限公司 | A kind of list data update method and device |
| CN107346347A (en) * | 2017-09-13 | 2017-11-14 | 广州酷狗计算机科技有限公司 | Web page form display methods and device |
| CN107621940A (en) * | 2017-09-18 | 2018-01-23 | 联想(北京)有限公司 | The update method and electronic equipment of a kind of initialization program |
| WO2018153271A1 (en) * | 2017-02-27 | 2018-08-30 | 腾讯科技（深圳）有限公司 | Data push method and apparatus, storage medium, and electronic device |
| CN109032747A (en) * | 2018-08-10 | 2018-12-18 | 江苏奇异点网络有限公司 | Data-updating method and device |
| CN109034732A (en) * | 2018-06-29 | 2018-12-18 | 深圳市商汤科技有限公司 | Attendance data treating method and apparatus, equipment, computer program and storage medium |
| WO2019109513A1 (en) * | 2017-12-08 | 2019-06-13 | 平安科技（深圳）有限公司 | Resource updating method and system, electronic device, and medium |
| CN110020288A (en) * | 2017-09-30 | 2019-07-16 | 北京国双科技有限公司 | A kind of page furbishing method and device |
| CN112389507A (en) * | 2019-08-14 | 2021-02-23 | 比亚迪股份有限公司 | Automatic train monitoring system and method, storage medium and data server |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9992258B2 (en) * | 2015-01-13 | 2018-06-05 | Whatsapp Inc. | Techniques for managing a remote web client from an application on a mobile device |
| CN106209568A (en) * | 2015-05-04 | 2016-12-07 | 阿里巴巴集团控股有限公司 | A kind of message treatment method and device |
| CN105938417B (en) * | 2015-08-06 | 2019-02-19 | 杭州迪普科技股份有限公司 | Update the method and device of configuration data |
| CN106990949B (en) * | 2016-12-31 | 2021-06-18 | 深圳大宇无限科技有限公司 | Application page display method and device |
| CN110392102A (en) * | 2019-07-16 | 2019-10-29 | 北京辰森世纪科技股份有限公司 | Processing method and client, the server-side of data |
| CN112632089B (en) * | 2019-09-24 | 2022-07-12 | 无锡江南计算技术研究所 | Parallel discrete updating method for heterogeneous many-core processor |
| CN112199617A (en) * | 2020-10-19 | 2021-01-08 | 广州华多网络科技有限公司 | Business data refreshing and pushing method and device, equipment and medium thereof |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030106051A1 (en) * | 2001-12-03 | 2003-06-05 | Morrison John A. | System and method for high availability firmware load |
| US20040139208A1 (en) * | 2002-12-03 | 2004-07-15 | Raja Tuli | Portable internet access device back page cache |
| CN1783804A (en) * | 2004-12-01 | 2006-06-07 | 华为技术有限公司 | Realtime updating method for net page data |
| CN101316256A (en) * | 2007-05-28 | 2008-12-03 | 微码（北京）移动技术有限公司 | Data updating method |
| US20090037453A1 (en) * | 2007-07-31 | 2009-02-05 | Sap Ag | Unified and extensible implementation of a change state id for update services based on a hash calculation |
| CN101626339A (en) * | 2008-07-07 | 2010-01-13 | 英华达(上海)电子有限公司 | Method and system for downloading network data |
| US20100295770A1 (en) * | 2006-08-23 | 2010-11-25 | Logicplant | Control method for controlling remote computer |
| CN102404241A (en) * | 2010-09-13 | 2012-04-04 | 腾讯科技（深圳）有限公司 | Display method and processing system of Feeds information and IM (Information Management) client side |
| CN102480397A (en) * | 2010-11-26 | 2012-05-30 | 金蝶软件（中国）有限公司 | Method and equipment for accessing internet pages |
| CN102571935A (en) * | 2011-12-23 | 2012-07-11 | 华为技术有限公司 | Data transmission method, client, server and system |
-
2013
- 2013-01-07 CN CN201310005204.XA patent/CN103916373A/en active Pending
- 2013-12-02 WO PCT/CN2013/088271 patent/WO2014106417A1/en active Application Filing
-
2014
- 2014-06-16 US US14/305,419 patent/US20140298313A1/en not_active Abandoned
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030106051A1 (en) * | 2001-12-03 | 2003-06-05 | Morrison John A. | System and method for high availability firmware load |
| US20040139208A1 (en) * | 2002-12-03 | 2004-07-15 | Raja Tuli | Portable internet access device back page cache |
| CN1783804A (en) * | 2004-12-01 | 2006-06-07 | 华为技术有限公司 | Realtime updating method for net page data |
| US20100295770A1 (en) * | 2006-08-23 | 2010-11-25 | Logicplant | Control method for controlling remote computer |
| CN101316256A (en) * | 2007-05-28 | 2008-12-03 | 微码（北京）移动技术有限公司 | Data updating method |
| US20090037453A1 (en) * | 2007-07-31 | 2009-02-05 | Sap Ag | Unified and extensible implementation of a change state id for update services based on a hash calculation |
| CN101626339A (en) * | 2008-07-07 | 2010-01-13 | 英华达(上海)电子有限公司 | Method and system for downloading network data |
| CN102404241A (en) * | 2010-09-13 | 2012-04-04 | 腾讯科技（深圳）有限公司 | Display method and processing system of Feeds information and IM (Information Management) client side |
| CN102480397A (en) * | 2010-11-26 | 2012-05-30 | 金蝶软件（中国）有限公司 | Method and equipment for accessing internet pages |
| CN102571935A (en) * | 2011-12-23 | 2012-07-11 | 华为技术有限公司 | Data transmission method, client, server and system |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104702703A (en) * | 2015-03-30 | 2015-06-10 | 北京奇艺世纪科技有限公司 | Method and device for updating data |
| CN104702703B (en) * | 2015-03-30 | 2019-03-15 | 北京奇艺世纪科技有限公司 | A kind of data-updating method and device |
| CN104811394A (en) * | 2015-04-21 | 2015-07-29 | 深圳市出众网络有限公司 | Method and system for saving traffic for accessing server |
| CN106549983A (en) * | 2015-09-16 | 2017-03-29 | ***通信集团公司 | The access method and terminal of a kind of database, server |
| CN105868251A (en) * | 2015-12-22 | 2016-08-17 | 乐视云计算有限公司 | Cache data updating method and device |
| WO2017107683A1 (en) * | 2015-12-25 | 2017-06-29 | 北京奇虎科技有限公司 | Data updating method and device |
| CN105550346A (en) * | 2015-12-25 | 2016-05-04 | 北京奇虎科技有限公司 | Information management method and device |
| CN105634801A (en) * | 2015-12-25 | 2016-06-01 | 北京奇虎科技有限公司 | Data updating method and device |
| CN105893607A (en) * | 2016-04-25 | 2016-08-24 | 青岛海信传媒网络技术有限公司 | Page data management method, device and data server |
| CN105939355A (en) * | 2016-06-13 | 2016-09-14 | 乐视控股（北京）有限公司 | Data access method and system, as well as client and server |
| CN106878370A (en) * | 2016-09-19 | 2017-06-20 | 阿里巴巴集团控股有限公司 | The update method and equipment of a kind of local cache |
| WO2018153271A1 (en) * | 2017-02-27 | 2018-08-30 | 腾讯科技（深圳）有限公司 | Data push method and apparatus, storage medium, and electronic device |
| US10949112B2 (en) | 2017-02-27 | 2021-03-16 | Tencent Technology (Shenzhen) Company Limited | Data push method and device, storage medium, and electronic device |
| CN106897444A (en) * | 2017-03-01 | 2017-06-27 | 郑州云海信息技术有限公司 | A kind of list data update method and device |
| CN107346347A (en) * | 2017-09-13 | 2017-11-14 | 广州酷狗计算机科技有限公司 | Web page form display methods and device |
| CN107346347B (en) * | 2017-09-13 | 2020-04-24 | 广州酷狗计算机科技有限公司 | Webpage table display method and device |
| CN107621940A (en) * | 2017-09-18 | 2018-01-23 | 联想(北京)有限公司 | The update method and electronic equipment of a kind of initialization program |
| CN110020288A (en) * | 2017-09-30 | 2019-07-16 | 北京国双科技有限公司 | A kind of page furbishing method and device |
| WO2019109513A1 (en) * | 2017-12-08 | 2019-06-13 | 平安科技（深圳）有限公司 | Resource updating method and system, electronic device, and medium |
| CN109034732A (en) * | 2018-06-29 | 2018-12-18 | 深圳市商汤科技有限公司 | Attendance data treating method and apparatus, equipment, computer program and storage medium |
| CN109032747A (en) * | 2018-08-10 | 2018-12-18 | 江苏奇异点网络有限公司 | Data-updating method and device |
| CN109032747B (en) * | 2018-08-10 | 2021-10-15 | 江苏奇异点网络有限公司 | Data updating method and device |
| CN112389507A (en) * | 2019-08-14 | 2021-02-23 | 比亚迪股份有限公司 | Automatic train monitoring system and method, storage medium and data server |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2014106417A1 (en) | 2014-07-10 |
| US20140298313A1 (en) | 2014-10-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103916373A (en) | Data updating method, server, client side and system | |
| US9143389B2 (en) | Methods, appratuses, and computer program products for determining a network interface to access a network resource | |
| CN105446750B (en) | The method and apparatus that WebApp starting runs, generates image file | |
| CN102572014A (en) | Message processing method and device and system thereof | |
| CN105391811A (en) | DNS (domain name resolution) method, access method for application server, and terminal | |
| CN103530160A (en) | Page loading method and device | |
| CN104995902A (en) | Methods and systems for seamless network communication between IPV4 and IPV6 devices | |
| CN102567339A (en) | Method, device and system for acquiring start page | |
| CN103109517A (en) | Double-stack terminal accessing service method, terminal and system | |
| CN104268229A (en) | Resource obtaining method and device based on multi-process browser | |
| CN101997853A (en) | Data downloading method and terminal | |
| CN112423281B (en) | Wireless module upgrading method, device, computer equipment and storage medium | |
| CN103312489A (en) | Method and device for synchronizing terminal and server | |
| CN103699635A (en) | Information processing method and device | |
| CN102752411A (en) | Redirection method and device | |
| CN104267921A (en) | Page display control method and server | |
| CN103634393A (en) | IVR (interactive voice response) and realization method thereof | |
| CN103634396A (en) | Method, gateway equipment and system for accessing intranet webpage service data | |
| CN102156697A (en) | Method and terminal equipment for realizing webpage application through widget | |
| CN103440281A (en) | Method, device and equipment for acquiring download file | |
| CN103368907A (en) | Event report request system, method thereof, client device and report request method thereof | |
| CN102523271B (en) | Terminal and communication method and system thereof | |
| CN103729440A (en) | Method and device for having access to website | |
| CN102469109A (en) | Display method of browser homepage in mobile terminal and apparatus thereof | |
| CN103793459B (en) | Webpage opening method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate 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: 20140709 |