CN106886433A - The update method and device of client software - Google Patents
The update method and device of client software Download PDFInfo
- Publication number
- CN106886433A CN106886433A CN201510947067.0A CN201510947067A CN106886433A CN 106886433 A CN106886433 A CN 106886433A CN 201510947067 A CN201510947067 A CN 201510947067A CN 106886433 A CN106886433 A CN 106886433A
- Authority
- CN
- China
- Prior art keywords
- file
- version
- current version
- client
- factor
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44536—Selecting among different versions
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides the update method and device of a kind of client software.Methods described includes：Multiple original documents in local current version catalogue are converted into a second current version file；Receive the delta file that service end sends；It is the second target version file by the delta file and the second current version Piece file mergence；The second target version file is decomposed into multiple new edition files；The multiple original document is replaced with the multiple new edition file, to form target version catalogue.The delta file of client current version and target version can be sent to client by the application service end, multiple original documents in local current version catalogue can be converted to a second current version file by client, then multiple new edition files are decomposed into again after merging delta file and the second current version file, so as to realize the incremental update to off-line files, the flow consumption in renewal process is greatlyd save.
Description
Technical field
The application is related to field of terminal technology, more particularly to a kind of client software update method and device.
Background technology
With the fast development of Internet technology, increasing smart machine has come into the life of people.
People can install various client softwares (Application, APP) in smart machine,
For meeting different demands.
Various applications can generally be included in client software, each application would generally include some and can protect
In the presence of local offline resources, such as：CSS (Cascading Style Sheets, CSS) texts
Part, JS (JavaScript) file etc..When client software is updated, generally require again from clothes
These offline resources are downloaded at business end, cause flow to consume more.
The content of the invention
In view of this, the application provides the update method and device of a kind of client software.
Specifically, the application is achieved by the following technical solution：
A kind of update method of client software, applies in service end, and methods described includes：
Obtain the version information of client Current software；
By the corresponding multiple original documents of the version information that service end is preserved be converted to one it is first current
Version file；
The corresponding multiple new edition files of latest edition are converted into a first object version file；
The delta file of the first current version file is generated according to the first object version file；
The delta file is sent to client, so that client is updated.
Optionally, methods described also includes：
For the first current version file generated first verifies the factor；
For delta file generation second verifies the factor；
The described first verification factor and the second verification factor are sent to client, so that client is entered
Row verification, and verification by when be updated.
Optionally, it is described to be converted to the corresponding multiple original documents of the version information that service end is preserved
One the first current version file, including：
Based on FLAT agreements and default ordering rule, the version information pair that service end is preserved
The multiple original documents answered are converted to a first current version file；
It is described that the corresponding multiple new edition files of latest edition are converted into a first object version file,
Including:
Based on FLAT agreements and the ordering rule, by the corresponding multiple new edition files of latest edition
Be converted to a first object version file.
A kind of update method of client software, applies in client, and methods described includes：
Multiple original documents in local current version catalogue are converted into a second current version file；
Receive the delta file that service end sends；
It is the second target version file by the delta file and the second current version Piece file mergence；
The second target version file is decomposed into multiple new edition files；
The multiple original document is replaced with the multiple new edition file, to form target version catalogue.
Optionally, described is the second target by the delta file and the second current version Piece file mergence
Before version file, also include：
Receive the first verification factor and the second verification factor that service end sends；
For the second current version file generated the 3rd verifies the factor；
For delta file generation the 4th verifies the factor；
When the described 3rd verification factor and the 4th verification factor verify the factor and institute with described first respectively
State the second verification factor it is identical when, be the by the delta file and the second current version Piece file mergence
Two target version files.
Optionally, the multiple original documents by local current version catalogue are converted to one second and work as
Preceding version file, including：
It is based on FLAT agreements and default ordering rule, the multiple in local current version catalogue is former
Beginning file is converted to a second current version file.
Optionally, when the multiple original document is converted into a second current version file, ignore
The particular community of the original document.
A kind of updating device of client software, applies in service end, and described device includes：
Version acquiring unit, obtains the version information of client Current software；
First converting unit, the corresponding multiple original document conversions of the version information that service end is preserved
It is a first current version file；
The corresponding multiple new edition files of latest edition are converted to a first object by the second converting unit
Version file；
Increment generation unit, the first current version file is generated according to the first object version file
Delta file；
Increment transmitting element, client is sent to by the delta file, so that client is updated.
Optionally, described device also includes：
First generation unit, is the verification of the first current version file generated first factor；
Second generation unit, is that the delta file generation second verifies the factor；
Factor transmitting element, client is sent to by the described first verification factor and the second verification factor,
So that client is verified, and verification by when be updated.
Optionally, first converting unit, is specifically based on FLAT agreements and default ordering rule,
The corresponding multiple original documents of the version information that service end is preserved are converted into first current version
File；
Second converting unit, is specifically based on FLAT agreements and the ordering rule, by latest edition
This corresponding multiple new edition file is converted to a first object version file.
A kind of updating device of client software, applies in service end, and described device includes：
Multiple original documents in local current version catalogue are converted to one second by the 3rd converting unit
Current version file；
Incremental receipt unit, receives the delta file that service end sends；
Increment combining unit, is the second mesh by the delta file and the second current version Piece file mergence
Mark version file；
File resolving cell, multiple new edition files are decomposed into by the second target version file；
File replacement unit, the multiple original document is replaced with the multiple new edition file, to be formed
Target version catalogue.
Optionally, described device also includes：
Factor receiving unit, described is the by the delta file and the second current version Piece file mergence
Before two target version files, the first verification factor and the second verification factor that service end sends are received；
3rd generation unit, is the verification of the second current version file generated the 3rd factor；
4th generation unit, is that the delta file generation the 4th verifies the factor；
The increment combining unit, specifically in the described 3rd verification factor and the 4th verification factor difference
During with the described first verification factor and identical the second verification factor, by the delta file and described the
Two current version Piece file mergences are the second target version file.
Optionally, the 3rd converting unit, is specifically based on FLAT agreements and default ordering rule,
Multiple original documents in local current version catalogue are converted into a second current version file.
Optionally, the 3rd converting unit, is specifically being converted to one by the multiple original document
During two current version files, ignore the particular community of the original document.
By above description as can be seen that the application service end can be by client current version and target version
Delta file be sent to client, client can be by the multiple original text in local current version catalogue
Part is converted to a second current version file, and then delta file is carried out with the second current version file
Multiple new edition files are decomposed into after merging again, so as to realize the incremental update to off-line files, are saved significantly
The flow consumption in renewal process is saved.
Brief description of the drawings
Fig. 1 is a kind of flow of the update method of the client software shown in the exemplary embodiment of the application one
Schematic diagram.
Fig. 2 is the stream of the update method of another client software shown in the exemplary embodiment of the application one
Journey schematic diagram.
Fig. 3 is a kind of updating device for client software shown in the exemplary embodiment of the application one
One structural representation.
Fig. 4 is a kind of structure of the updating device of the client software shown in the exemplary embodiment of the application one
Schematic diagram.
Fig. 5 is updating device of the another kind shown in the exemplary embodiment of the application one for client software
A structural representation.
Fig. 6 is the knot of the updating device of another client software shown in the exemplary embodiment of the application one
Structure schematic diagram.
Specific embodiment
Here exemplary embodiment will be illustrated in detail, its example is illustrated in the accompanying drawings.Following
When description is related to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawings represent same or analogous
Key element.Implementation method described in following exemplary embodiment does not represent the institute consistent with the application
There is implementation method.Conversely, they are only with described in detail in such as appended claims, the application
The example of the consistent apparatus and method of a little aspects.
It is the purpose only merely for description specific embodiment in term used in this application, and is not intended to be limiting
The application." one kind ", " institute of the singulative used in the application and appended claims
State " and " being somebody's turn to do " be also intended to include most forms, unless context clearly shows that other implications.Should also
Work as understanding, term "and/or" used herein refers to and associated lists item comprising one or more
Purpose any or all may combine.
It will be appreciated that though may describe various using term first, second, third, etc. in the application
Information, but these information should not necessarily be limited by these terms.These terms only be used for by same type of information that
This is distinguished.For example, in the case where the application scope is not departed from, the first information can also be referred to as
Two information, similarly, the second information can also be referred to as the first information.Depending on linguistic context, as in this institute
Use word " if " can be construed to " and ... when " or " when ... when " or " response
In it is determined that ".
In correlation technique, the renewal of the off-line files such as CSS files, JS files of client local cache is frequently
Rate is relatively low, when client terminal software updating, it will usually download above-mentioned off-line files from service end again, from
And consume a large amount of non-essential flows of user.
Regarding to the issue above, the application provides a kind of update scheme of client software, can be in client
During software upgrading, incremental update is realized for off-line files, so as to save customer flow.
Fig. 1 is a kind of flow of the update method of the client software shown in the exemplary embodiment of the application one
Schematic diagram.
Refer to Fig. 1, the update method of the client software can be applied in service end, include with
Lower step：
Step 101, obtains the version information of client Current software.
In the present embodiment, service end when redaction is issued, can obtain the version of client Current software
This information, such as：Service end can obtain the version information of local preservation, and service end can also be sent out
Version querying is sent to ask to client to obtain the version information.
In another embodiment, client can also actively send renewal request to service end, and described
The version information of carrying client Current software in request is updated, service end can be from the renewal request
Obtain the version information.
The corresponding multiple original documents of the version information that service end is preserved are converted to one by step 102
Individual first current version file.
Based on abovementioned steps 101, service end, can after the version information for getting client Current software
First to obtain the corresponding multiple original documents of the version information of service end preservation, such as：Service end can
To obtain the corresponding multiple original documents of the version information from nonvolatile memory.The original text
Part can include：CSS files, JS files etc..
In this step, the corresponding multiple original documents of the version information can be converted to one by service end
Individual file, for ease of description, in the present embodiment, the version information that service end is preserved is corresponding
File after multiple original document conversions is referred to as the first current version file.
Specifically, service end can be based on FLAT agreements and default ordering rule, will be the multiple
Original document is converted to the first current version file.Wherein, the FLAT agreements are a kind of customized
File protocol, for realizing multiple files a to conversion for file.The file obtained after conversion by
A series of item compositions, each item is for each in the multiple files before description conversion, item
Form be usually：The content of the title+byte number+file of file.In the present embodiment, after conversion
Each item of the first current version file can be：Title+the byte number of original document+this is original
The content of file.The ordering rule is the sequencing of each item, and the ordering rule can be by opening
Hair personnel be configured, such as：Before the ordering rule can be for order, the document time of file name
Order, order of file size afterwards etc., the application is not particularly limited to this.
The corresponding multiple new edition files of latest edition are converted to a first object version by step 103
File.
In the present embodiment, service end can also obtain the corresponding multiple new edition files of latest edition, so
The multiple new edition file is converted into a file afterwards, for ease of distinguishing, by the multiple redaction
The file obtained after file conversion turns into first object version file.Service end can be based on FLAT agreements
And the multiple new edition file is converted to a first object version file by default ordering rule,
The description of abovementioned steps 102 is specifically may be referred to, this is no longer going to repeat them.
Step 104, the increasing of the first current version file is generated according to the first object version file
Amount file.
Based on abovementioned steps 102 and 103, service end can be generated according to the first object version file
The residual quantity file of the first current version file, in the present embodiment, can claim the residual quantity file
It is delta file.
Step 105, client is sent to by the delta file, so that client is updated.
Based on abovementioned steps 104, service end, can be by the increment after the delta file is generated
File is sent to client, and client can carry out increment more after the delta file is received
Newly.
Fig. 2 is the stream of the update method of another client software shown in the exemplary embodiment of the application one
Journey schematic diagram.
Refer to Fig. 2, the update method of the client software can be applied in client, include with
Lower step：
Step 201, by the multiple original documents in local current version catalogue be converted to one it is second current
Version file.
In the present embodiment, the off-line files such as the CSS files of client local cache, JS files generally with
The mode of catalogue (being referred to as file) is preserved, and multiple texts have been generally included in a catalogue
Part.
In this step, client can obtain the current version in the current version target of local preservation
Multiple original documents, may then based on FLAT agreements and with service end identical ordering rule, will
Multiple original documents in the local current version catalogue are converted to a file, in the present embodiment,
Made a distinction for ease of the processing procedure with aforementioned service end, obtained after being changed via client
File is referred to as the second current version file.
Optionally, in another embodiment of the application, client is converted to by the multiple original document
During one the second current version file, the particular community of the original document can be ignored, it is follow-up to ensure
File increment renewal process runs smooth.The particular community is generally configured by developer, than
Such as：File generated time, file permission etc. do not influence the attribute that file is used.
Step 202, receives the delta file that service end sends.
In the present embodiment, client receives the delta file that service end sends when being updated, than
Such as：Client can receive service end according to the increasing for updating request return after renewal request is sent
Amount file, client can also receive the delta file of service end active push, and the application does not make spy to this
Different limitation.The delta file is generated by service end according to the version information of client Current software, specifically
The description process in the embodiment shown in earlier figures 1 is may be referred to, this is no longer going to repeat them.
Step 203, is the second target version by the delta file and the second current version Piece file mergence
Presents.
Based on abovementioned steps 201 and step 202, client can be according to the file provided in correlation technique
Merging method, the delta file and the second current version file is merged, to obtain second
Target version file.
It should be noted that in this application, being not intended to limit the execution of abovementioned steps 201 and step 202
Sequentially, in actual applications, client can also be after delta file be received, and performing step 201 will
Multiple original documents in local current version catalogue are converted into a second current version file, you can
To first carry out step 202, step 201 is then performed again.
Step 204, multiple new edition files are decomposed into by the second target version file.
Based on abovementioned steps 203, client, can after merging obtains the second target version file
Decomposed with by the second target version file, to obtain multiple new edition files.Due to described second
Target version file is the file by being obtained after FLAT protocol conversions, and client can be according to FLAT
The construction of file is decomposed to the second target version file, such as：By second target version
Each item in file is decomposed into a new edition file, so as to obtain multiple new edition files.
Step 205, replaces the multiple original document, to form target with the multiple new edition file
The release directory.
Based on abovementioned steps 204, client can replace local current version with the multiple new edition file
Multiple original documents in this catalogue, and then local current version catalogue is updated to target version catalogue,
Realize the renewal of increment.
By above description as can be seen that the application service end can be by client current version and target version
Delta file be sent to client, client can be by the multiple original text in local current version catalogue
Part is converted to a second current version file, and then delta file is carried out with the second current version file
Multiple new edition files are decomposed into after merging again, so as to realize the incremental update to off-line files, are saved significantly
The flow consumption in renewal process is saved.
Optionally, in another embodiment of the application, to ensure being smoothed out for incremental update, the application
It is also provided with checkschema during incremental update.Specifically, service end can send delta file to
First is sent while client and verifies the factor and the second verification factor to client, client is according to institute
Stating the first verification factor and the second verification factor carries out carrying out incremental update after verification passes through.
Wherein, the first verification factor is the first current version file generated by service end, such as：Clothes
Business end can be described using MD5 (Message Digest Algorithm, summary info algorithm) algorithm
The first verification factor described in first current version file generated, certainly, service end can also be using other calculations
Method generation the first verification factor, such as：(Cyclic Redundancy Check, follow CRC algorithm
Ring redundancy check) etc..The second verification factor is that delta file is generated by service end, and service end can be with
Use and verify factor identical algorithm for delta file generation second verifies the factor, clothes with generation first
Business end can also use and verify the algorithm of the factor for the delta file generates the second school different from generation first
The factor is tested, the application is not particularly limited to this.
In the present embodiment, client is receiving the first verification factor and the second verification factor
Afterwards, verified.Specifically, client uses the first verification factor described with service end generation identical
Algorithm for the second current version file generated the 3rd verify the factor, then judge it is described 3rd verification the factor
It is whether identical with the described first verification factor, if identical, illustrate that the client that service end is preserved is current
In the current version catalogue that the corresponding multiple original documents of version information of software are locally preserved with client
Multiple original documents are identical, if it is not the same, the then version of the client Current software that explanation service end is preserved
It is multiple original in the current version catalogue that the corresponding multiple original documents of this information are locally preserved with client
File is differed, it may be possible to which the client software current version that service end gets is wrong, stops increment more
New process.Client can also be used and verify factor identical algorithm to receive with service end generation second
Delta file generation the 4th verify the factor, then judge the 4th verification factor whether with described second
The verification factor is identical, if identical, illustrates that network transmission does not have packet loss, the increment that client is received
File is exactly the delta file of service end generation, if it is not the same, the increment that then explanation client is received
File is not the delta file of service end generation, stops the process of incremental update.
In the present embodiment, when client confirms the 3rd verification factor with the described first verification factor phase
Together, and it is described 4th verification the factor with described second verification the factor it is identical when, by the delta file and institute
The second current version Piece file mergence is stated for the second target version file, to carry out the process of incremental update, this
This is no longer going to repeat them for application.
Embodiment with the update method of foregoing client software is corresponding, present invention also provides client
The embodiment of the updating device of software.
The embodiment of the updating device of the application client software can be applied in terminal and service end respectively.
Device embodiment can be realized by software, it is also possible to be realized by way of hardware or software and hardware combining.
It is by terminal where it and service end as the device on a logical meaning as a example by implemented in software
Processor corresponding computer program instructions in nonvolatile memory read to run in internal memory formed
's.From for hardware view, as shown in figure 3, applying the client software in service end for the application
Updating device where service end a kind of hardware structure diagram, except the processor shown in Fig. 3, internal memory,
Outside network interface and nonvolatile memory, service end in embodiment where device generally according to
The actual functional capability of the service end, can also include other hardware, and this is repeated no more.
Fig. 4 is a kind of structure of the updating device of the client software shown in the exemplary embodiment of the application one
Schematic diagram.
Fig. 4 is refer to, the updating device 300 of the client software can be applied in the clothes shown in Fig. 3
In business end, include：Version acquiring unit 301, the first converting unit 302, the second converting unit 303,
Increment generation unit 304, increment transmitting element 305, the first generation unit 306, the second generation unit 307
And factor transmitting element 308.
Wherein, the version acquiring unit 301, obtains the version information of client Current software；
First converting unit 302, the corresponding multiple of the version information that service end is preserved is original
File is converted to a first current version file；
The corresponding multiple new edition files of latest edition are converted to one by second converting unit 303
First object version file；
The increment generation unit 304, it is current according to first object version file generation described first
The delta file of version file；
The increment transmitting element 305, client is sent to by the delta file, so that client is entered
Row updates.
First generation unit 306, is the verification of the first current version file generated first factor；
Second generation unit 307, is that the delta file generation second verifies the factor；
The factor transmitting element 308, the described first verification factor and the second verification factor are sent
To client, so that client is verified, and verification by when be updated.
Optionally, first converting unit 302, is specifically based on FLAT agreements and default sequence
The corresponding multiple original documents of the version information that service end is preserved are converted to one first and worked as by rule
Preceding version file；
Second converting unit 303, is specifically based on FLAT agreements and the ordering rule, will most
The corresponding multiple new edition files of redaction are converted to a first object version file.
Fig. 5 is updating device of the another kind shown in the exemplary embodiment of the application one for client software
A structural representation.
As shown in figure 5, the updating device place terminal of the client software for the application application in the terminal
A kind of hardware structure diagram, except the processor shown in Fig. 3, internal memory, network interface and non-volatile
Outside property memory, the terminal in embodiment where device may be used also generally according to the actual functional capability of the terminal
Including other hardware, to be repeated no more to this.
Fig. 6 is a kind of structure of the updating device of the client software shown in the exemplary embodiment of the application one
Schematic diagram.
Fig. 6 is refer to, the updating device 500 of the client software can be applied at the end shown in Fig. 5
In end, include：3rd converting unit 501, Incremental receipt unit 502, increment combining unit 503,
File resolving cell 504, file replacement unit 505, factor receiving unit 506, the 3rd generation unit 507,
4th generation unit 508.
Wherein, the 3rd converting unit 501, by the multiple original documents in local current version catalogue
Be converted to a second current version file；
The Incremental receipt unit 502, receives the delta file that service end sends；
The increment combining unit 503, by the delta file and the second current version Piece file mergence
It is the second target version file；
The file resolving cell 504, multiple new editions are decomposed into herein by the second target version file
Part；
The file replacement unit 505, the multiple original document is replaced with the multiple new edition file,
To form target version catalogue.
The factor receiving unit 506, it is described by the delta file and the second current version file
Before merging into the second target version file, the first verification factor and the second verification that service end sends are received
The factor；
3rd generation unit 507, is the verification of the second current version file generated the 3rd factor；
4th generation unit 508, is that the delta file generation the 4th verifies the factor；
The increment combining unit 503, specifically in the described 3rd verification factor and the 4th verification factor
When respectively with the described first verification factor and identical the second verification factor, by the delta file and institute
The second current version Piece file mergence is stated for the second target version file.
Optionally, the 3rd converting unit 501, is specifically based on FLAT agreements and default sequence
Multiple original documents in local current version catalogue are converted to a second current version file by rule.
Optionally, the 3rd converting unit 501, is specifically being converted to one by the multiple original document
During individual second current version file, ignore the particular community of the original document.
The function of unit and the implementation process of effect specifically refer to correspondence in the above method in said apparatus
The implementation process of step, will not be repeated here.
For device embodiment, because it corresponds essentially to embodiment of the method, so related part ginseng
See the part explanation of embodiment of the method.Device embodiment described above be only it is schematical,
It is wherein described as separating component illustrate unit can be or may not be it is physically separate, make
For the part that unit shows can be or may not be physical location, you can with positioned at a place,
Or can also be distributed on multiple NEs.Can select according to the actual needs part therein or
Person whole modules realize the purpose of application scheme.Those of ordinary skill in the art are not paying creativeness
In the case of work, you can to understand and implement.
The preferred embodiment of the application is the foregoing is only, is not used to limit the application, it is all at this
Within the spirit and principle of application, any modification, equivalent substitution and improvements done etc. should be included in
Within the scope of the application protection.
Claims (14)
1. a kind of update method of client software, applies in service end, it is characterised in that methods described
Including：
Obtain the version information of client Current software；
By the corresponding multiple original documents of the version information that service end is preserved be converted to one it is first current
Version file；
The corresponding multiple new edition files of latest edition are converted into a first object version file；
The delta file of the first current version file is generated according to the first object version file；
The delta file is sent to client, so that client is updated.
2. method according to claim 1, it is characterised in that methods described also includes：
For the first current version file generated first verifies the factor；
For delta file generation second verifies the factor；
The described first verification factor and the second verification factor are sent to client, so that client is entered
Row verification, and verification by when be updated.
3. method according to claim 1, it is characterised in that it is described service end is preserved described in
The corresponding multiple original documents of version information are converted to a first current version file, including：
Based on FLAT agreements and default ordering rule, the version information pair that service end is preserved
The multiple original documents answered are converted to a first current version file；
It is described that the corresponding multiple new edition files of latest edition are converted into a first object version file,
Including:
Based on FLAT agreements and the ordering rule, by the corresponding multiple new edition files of latest edition
Be converted to a first object version file.
4. a kind of update method of client software, applies in client, it is characterised in that methods described
Including：
Multiple original documents in local current version catalogue are converted into a second current version file；
Receive the delta file that service end sends；
It is the second target version file by the delta file and the second current version Piece file mergence；
The second target version file is decomposed into multiple new edition files；
The multiple original document is replaced with the multiple new edition file, to form target version catalogue.
5. method according to claim 4, it is characterised in that described by the delta file and institute
The second current version Piece file mergence is stated before the second target version file, also to include：
Receive the first verification factor and the second verification factor that service end sends；
For the second current version file generated the 3rd verifies the factor；
For delta file generation the 4th verifies the factor；
When the described 3rd verification factor and the 4th verification factor verify the factor and institute with described first respectively
State the second verification factor it is identical when, be the by the delta file and the second current version Piece file mergence
Two target version files.
6. method according to claim 4, it is characterised in that described by local current version catalogue
In multiple original documents be converted to a second current version file, including：
It is based on FLAT agreements and default ordering rule, the multiple in local current version catalogue is former
Beginning file is converted to a second current version file.
7. method according to claim 6, it is characterised in that
When the multiple original document is converted into a second current version file, ignore described original
The particular community of file.
8. a kind of updating device of client software, applies in service end, it is characterised in that described device
Including：
Version acquiring unit, obtains the version information of client Current software；
First converting unit, the corresponding multiple original document conversions of the version information that service end is preserved
It is a first current version file；
The corresponding multiple new edition files of latest edition are converted to a first object by the second converting unit
Version file；
Increment generation unit, the first current version file is generated according to the first object version file
Delta file；
Increment transmitting element, client is sent to by the delta file, so that client is updated.
9. device according to claim 8, it is characterised in that described device also includes：
First generation unit, is the verification of the first current version file generated first factor；
Second generation unit, is that the delta file generation second verifies the factor；
Factor transmitting element, client is sent to by the described first verification factor and the second verification factor,
So that client is verified, and verification by when be updated.
10. device according to claim 8, it is characterised in that
First converting unit, is specifically based on FLAT agreements and default ordering rule, will service
The corresponding multiple original documents of the version information for preserving are held to be converted to a first current version file；
Second converting unit, is specifically based on FLAT agreements and the ordering rule, by latest edition
This corresponding multiple new edition file is converted to a first object version file.
A kind of 11. updating devices of client software, apply in service end, it is characterised in that the dress
Put including：
Multiple original documents in local current version catalogue are converted to one second by the 3rd converting unit
Current version file；
Incremental receipt unit, receives the delta file that service end sends；
Increment combining unit, is the second mesh by the delta file and the second current version Piece file mergence
Mark version file；
File resolving cell, multiple new edition files are decomposed into by the second target version file；
File replacement unit, the multiple original document is replaced with the multiple new edition file, to be formed
Target version catalogue.
12. devices according to claim 11, it is characterised in that described device also includes：
Factor receiving unit, described is the by the delta file and the second current version Piece file mergence
Before two target version files, the first verification factor and the second verification factor that service end sends are received；
3rd generation unit, is the verification of the second current version file generated the 3rd factor；
4th generation unit, is that the delta file generation the 4th verifies the factor；
The increment combining unit, specifically in the described 3rd verification factor and the 4th verification factor difference
During with the described first verification factor and identical the second verification factor, by the delta file and described the
Two current version Piece file mergences are the second target version file.
13. devices according to claim 11, it is characterised in that
3rd converting unit, is specifically based on FLAT agreements and default ordering rule, will be local
Multiple original documents in current version catalogue are converted to a second current version file.
14. methods according to claim 13, it is characterised in that
3rd converting unit, is specifically being converted to a second current version by the multiple original document
During presents, ignore the particular community of the original document.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510947067.0A CN106886433A (en) | 2015-12-16 | 2015-12-16 | The update method and device of client software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510947067.0A CN106886433A (en) | 2015-12-16 | 2015-12-16 | The update method and device of client software |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106886433A true CN106886433A (en) | 2017-06-23 |
Family
ID=59176736
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510947067.0A Pending CN106886433A (en) | 2015-12-16 | 2015-12-16 | The update method and device of client software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106886433A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109656613A (en) * | 2018-12-12 | 2019-04-19 | 深圳市丰巢科技有限公司 | A kind of application and development method and apparatus based on increment |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102480494A (en) * | 2010-11-23 | 2012-05-30 | 金蝶软件（中国）有限公司 | File updating method, device and system |
| US20130055231A1 (en) * | 2011-08-31 | 2013-02-28 | Avaya Inc. | System and method for incremental software installation |
| CN103051723A (en) * | 2012-12-27 | 2013-04-17 | 广州市动景计算机科技有限公司 | Increment updating method as well as server and terminal |
| CN103095838A (en) * | 2013-01-16 | 2013-05-08 | 福州博远无线网络科技有限公司 | Method for upgrading Android smartphone software through downloading incremental upgrade package |
| CN103259672A (en) * | 2012-02-17 | 2013-08-21 | 阿里巴巴集团控股有限公司 | Software upgrading method and software upgrading system |
| CN103428188A (en) * | 2012-05-25 | 2013-12-04 | 北京小米科技有限责任公司 | Method and apparatus for file updating, and associated equipment |
| CN103699410A (en) * | 2013-12-20 | 2014-04-02 | 北京奇虎科技有限公司 | Method and device for updating application programs |
| CN103713928A (en) * | 2013-12-31 | 2014-04-09 | 优视科技有限公司 | Incremental file generating method, and application program installing file updating method and device |
| CN104252364A (en) * | 2013-06-25 | 2014-12-31 | 腾讯科技（深圳）有限公司 | Increment updating method, equipment and system |
| CN104539696A (en) * | 2014-12-26 | 2015-04-22 | 北京像素软件科技股份有限公司 | Client end incremental updating method and system |
-
2015
- 2015-12-16 CN CN201510947067.0A patent/CN106886433A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102480494A (en) * | 2010-11-23 | 2012-05-30 | 金蝶软件（中国）有限公司 | File updating method, device and system |
| US20130055231A1 (en) * | 2011-08-31 | 2013-02-28 | Avaya Inc. | System and method for incremental software installation |
| CN103259672A (en) * | 2012-02-17 | 2013-08-21 | 阿里巴巴集团控股有限公司 | Software upgrading method and software upgrading system |
| CN103428188A (en) * | 2012-05-25 | 2013-12-04 | 北京小米科技有限责任公司 | Method and apparatus for file updating, and associated equipment |
| CN103051723A (en) * | 2012-12-27 | 2013-04-17 | 广州市动景计算机科技有限公司 | Increment updating method as well as server and terminal |
| CN103095838A (en) * | 2013-01-16 | 2013-05-08 | 福州博远无线网络科技有限公司 | Method for upgrading Android smartphone software through downloading incremental upgrade package |
| CN104252364A (en) * | 2013-06-25 | 2014-12-31 | 腾讯科技（深圳）有限公司 | Increment updating method, equipment and system |
| CN103699410A (en) * | 2013-12-20 | 2014-04-02 | 北京奇虎科技有限公司 | Method and device for updating application programs |
| CN103713928A (en) * | 2013-12-31 | 2014-04-09 | 优视科技有限公司 | Incremental file generating method, and application program installing file updating method and device |
| CN104539696A (en) * | 2014-12-26 | 2015-04-22 | 北京像素软件科技股份有限公司 | Client end incremental updating method and system |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109656613A (en) * | 2018-12-12 | 2019-04-19 | 深圳市丰巢科技有限公司 | A kind of application and development method and apparatus based on increment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2915620C (en) | Method and apparatus for code virtualization and remote process call generation | |
| CN104714827B (en) | Update of plug-in method and device | |
| CN107203395A (en) | Resource graded method, device and computer-readable recording medium and electronic equipment | |
| US9063815B2 (en) | Provisioning a virtual machine from one or more VM images | |
| CN108804188A (en) | Changing an interface skin method and device | |
| CN108509209A (en) | A kind of generation method, device, computer equipment and the storage medium of resource packet | |
| EP3011442A1 (en) | Method and apparatus for customized software development kit (sdk) generation | |
| US11108871B2 (en) | Dynamic generation of network routing configuration with service requirements | |
| US10893091B2 (en) | Management of asynchronous content post and media file transmissions | |
| CN108052340A (en) | A kind of application upgrade method, apparatus | |
| CN110688598A (en) | Service parameter acquisition method and device, computer equipment and storage medium | |
| CN109462650A (en) | Data file downloading method, device, computer equipment and storage medium | |
| CN106569860A (en) | Application management method and terminal | |
| WO2019109519A1 (en) | Service rule management method, apparatus and device, and computer-readable storage medium | |
| CN108268346A (en) | Data back up method, device, equipment and storage medium | |
| AU2014412020B2 (en) | Techniques to transform network resource requests to zero rated network requests | |
| CN106886433A (en) | The update method and device of client software | |
| US20130080253A1 (en) | Error-specific advertisement display in electronic device | |
| JP2023031223A (en) | Apparatus and method for supporting source code generation of software and program therefor | |
| CN104539697B (en) | A kind of client, server and the method for making Android mobile application | |
| CN107704278A (en) | Application upgrade method and apparatus | |
| CN103761247B (en) | A kind of processing method and processing device of error file | |
| WO2015142596A1 (en) | Asset collection service through capture of content | |
| CN109698973A (en) | A kind of progress update method, device, electronic equipment and medium | |
| CN110309106A (en) | Method, apparatus, electronic equipment and the computer storage medium that file updates |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170623 |
|
| RJ01 | Rejection of invention patent application after publication |