CN106201606A - software distribution method and system - Google Patents
software distribution method and system Download PDFInfo
- Publication number
- CN106201606A CN106201606A CN201610519114.6A CN201610519114A CN106201606A CN 106201606 A CN106201606 A CN 106201606A CN 201610519114 A CN201610519114 A CN 201610519114A CN 106201606 A CN106201606 A CN 106201606A
- Authority
- CN
- China
- Prior art keywords
- version
- request information
- background
- software
- version identifier
- 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 OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides software distribution method and system, the background request information with version identifier and request content is built by system entry, background module determines process function by version identifier, and use corresponding function process the background request information, i.e. different editions of processing to be bound with processing function by version identifier.Multiple process function can be included in a service of same background module simultaneously, it is achieved that only arrange a service, i.e. have only to run a system process on line, thus avoid arranging and overlap back-end system more, it is achieved Operation and Maintenance simple software upgrading mode.
Description
Technical field
The present invention relates to computer software fields, particularly relate to a kind of software distribution method and system.
Background technology
When software upgrading, on the basis of the stable release of existing software, generally progressively issue transition version, until complete
Entirely it is upgraded to new stable release, thus stably realizes software upgrading.
Meanwhile, in order to tackle the problem in software upgrading, efficiently control the problem that software upgrading brought involves model
Enclose, prevent core customer to run off, when software upgrading, more New Policy based on user can be used, i.e. user is classified, right
Ask to use different software versions to process in different classes of user, a part of user asked to use transition version,
And another part user request is still used stable release.So, before affecting important service or user, this redaction is drawn
The problem entered just can be found, and reduces the issuable coverage of software upgrading the most well.
In software distribution method based on user of the prior art, generally use dissemination method based on route.Specifically
For, the method increased a routing module before back-end system, and the request of all access back-end systems first passes around this road
By module.The method needs to start multiple back-end system for tackling different software versions simultaneously, a software version correspondence
One back-end system.After being resolved user's request by routing module, ask corresponding software version according to user, access corresponding version
This back-end system.During release upgrade software, the user needing upgrading in routing table is pointed to new software version from old software version
This, the routing iinformation after then routing module dynamic load updates.
But, above-mentioned prior art needs additionally to arrange routing module, and the development and maintenance adding routing module become
This.Prior art needs to start multiple back-end system simultaneously, operation complexity, troublesome maintenance.
Summary of the invention
It is an object of the invention to provide dissemination method and the software system of a kind of software, carry out software more based on user
Time new, Operation and Maintenance is simple, the most error-prone.
According to an aspect of the present invention, it is provided that a kind of software distribution method, including step: receive user request information；
Based on user request information, determine the feature of the requesting party being associated with user request information；Feature based, determines to requesting party
The version identifier of the software issued；Build the background request information with version identifier and request content；Based on background request
The version identifier of information, determines corresponding process function, different editions mark binding different disposal function；Using please with backstage
Seek the process function process background request information that the version identifier of information is corresponding.
According to another aspect of the present invention, it is provided that a kind of software system, including system entry, system entry is based on reception
User request information, determine the feature of the requesting party being associated with user request information, and feature based, determine to requesting party
The version identifier of the software issued, system entry builds the background request information with version identifier and request content；At least
One background module, each background module includes multiple process function, and each background module performs at least one service, often
One or the one group combination comprising multiple process function in multiple process functions in one service call background module, extremely
A few background module receives system entry and sends the background request information come version identifier based on background request information, really
Fixed corresponding process function, use processes function and processes background request information, wherein different editions mark binding different disposal
Function.
The present invention builds the background request information with version identifier and request content, background module by system entry
Determine process function by version identifier, and use corresponding function process the background request information, i.e. different editions of processing to pass through
Version identifier is bound with processing function.Owing to there is multiple process function, by the corresponding different disposal function of different editions mark,
Therefore basic version can be existed by the form processing function with transition version simultaneously, processes function by version identifier by backstage
Module is mated and uses, thus without using routing module, it is to avoid the cost of routing module is safeguarded in extra exploitation.Due to same
Individual background module can include multiple process function simultaneously, when processing every time, and multiple in this background module of service call
Process one or the one group combination comprising multiple process function in function, therefore can only arrange a service, i.e. on line
Have only to run a system process, and without arranging multiple service or overlapping back-end system more.
Accompanying drawing explanation
Below in conjunction with the drawings and specific embodiments, technical scheme is described in detail, so that the present invention
Characteristic and advantage become apparent from.
Fig. 1 is the flow chart of an example of the software distribution method of the present invention；
Fig. 2 is the data flow schematic diagram of an example of software system and the user comprising the present invention；
Fig. 3 is the data structure schematic diagram of an example of the background request information of the present invention.
Detailed description of the invention
Hereinafter embodiments of the invention will be provided detailed description.Although the present invention will be in conjunction with some detailed description of the invention
It is illustrated and illustrates, but it should be noted that the present invention is not merely confined to these embodiments.On the contrary, to the present invention
The amendment carried out or equivalent, all should contain in the middle of scope of the presently claimed invention.
Some exemplary embodiments are described as process or the method described as flow chart.Although flow chart is by every behaviour
It is described into the process of order, but many of which operation can be implemented concurrently, concomitantly or simultaneously.Additionally, it is each
The order of item operation can be rearranged.The most described process can be terminated, it is also possible to have not
Including additional step in the accompanying drawings.Described process can correspond to method, function, code, subroutine, subprogram etc..
Fig. 1 is the flow chart of an example of the software distribution method of the present invention.Fig. 2 is the software system comprising the present invention
And the data flow schematic diagram of an example of user.
Shown in Fig. 1 and Fig. 2, usually used as the user 201 of requesting party on its subscriber equipment equipped with client, visitor
Family end can run on particular clients program, such as, install APP (application, application program) on the mobile apparatus,
Client can also run on browser.User 201 sends user request information 301 by client to software system 202, uses
Family solicited message 301 includes request content, such as, settle accounts the commodity chosen, and request content is represented by code means.Need
It is noted that user request information 301 comes from specific user in the present embodiment, user request information in other embodiments
301 may also be the example that the example from system self-operating, such as monitoring system the most normally work.
According to software approach S100 as shown in Figure 1, software system 202 mainly implements the steps of:
Step S101: receive user request information.
Step S102: determine requesting party's feature.
Step S103: determine the version identifier of the software issued to described requesting party.
Step S104: build the background request information with described version identifier and request content.
Step S105: determine the process function corresponding with the version identifier of background request information.
Step S106: use processes function and processes described background request information.
Step S107: build response message and return requesting party.
Specifically, first such as step S101, the system entry 203 of software system 202 receives user request information 301.
Such as step S102, system entry 203, based on user request information 301, determines and is associated with user request information 301
The feature of requesting party 201.Here feature can include user name, IP address, subscriber equipment communication physical address, use
Family client release number, user's history use habit, user facility operation system etc..Software system 202 can by read with
Cookie information that user request information is associated, subscriber equipment communication physical address, resolve user request information 301, inquiry
Database mode obtains features described above.
Then such as step S103, system entry 203 is based on feature determined by step S102, according to software publishing policy,
The version identifier (message type ID) of the software issued to this requesting party corresponding to matching characteristic.Software publishing policy
It is one or more rule specified the most in advance, such as when confirming this user for new user according to user name, then
Issue up-to-date transition version to it, when determining that the user is client steady in a long-term, then issue stable basic version to it.?
In other embodiments, when user request information 301 comes from example, such as, can be graded feature by the importance degree of this example,
Determine the user request information 301 using transition version or basic version to process this example.Software publishing policy can also be
The combination of multiple rules, multiple rules such as can arrange according to priority, when feature meets multiple rule, according to excellent
First level rule formerly determines the version issued to it, and multiple rules can also be combined by increasingly complex logic.No
Made a distinction by different editions mark with the software of version, thus according to software publishing policy, matching characteristic, thus obtain to
The version identifier of the software that this requesting party issues.
The most in this example, system entry 203 reads subscriber equipment communication physical address and obtains subscriber equipment communication thing
The feature of reason address, is determined that the user is by inquiry data base and uses user first, according to software publishing policy, to this user
Issue up-to-date transition version.
Then, such as step S104, system entry 203, based on user request information 301, builds background request information 302, after
Platform solicited message 302 includes version identifier and request content.Fig. 3 shows the data structure of background request information 302.Such as figure
Shown in 3, background request information 302 includes information header 401 and informosome 402, preserves version identifier, information in information header 401
Body 402 preserves request content.Specifically, informosome 402 includes request content in user request information 301, such as: knot
The commodity chosen.For the same requested content from different user, informosome 402 is identical.Information header 401 includes version
Identification field (message type ID), message type ID correspondence current version identifications, and include current version identifications
The basic version mark of the basic version being based on.Type ID is identical for identical version message, the message of different editions
Type ID is different.Owing to message type ID includes the basic version mark of basic version, therefore, pass through message
Type ID is possible not only to uniquely determine current software version, additionally it is possible to by extracting the basic version in message type ID
Mark, thus obtain the basic version that current version is based on.
In the present embodiment, message type ID coincidence formula:
Message type ID=X+V*graybase (1)
Wherein, message type ID is version identifier, version identifier based on X, and V is version number, on the basis of graybase
Side-play amount, message type ID, V and graybase be numerical value ,+representing additive operation, * represents multiplying.X can
Value is the integer between 0-100000, and V can be to start progressive whole number from 1.When V takes 0, message type ID represents
Basic version.
It should be noted that basic version mark numerical value corresponding to X is less than corresponding to datum offset amount graybase
Numerical value, consequently facilitating extract basic version mark X from message type ID.Generally datum offset amount graybase is one
Bigger numerical value, thus ensure that the version identifier of the transition version after having added datum offset amount will not be with basic version mark punching
Prominent.
Such as, taking X is 100, and taking graybase is 1000, it is assumed that current version is the 1st edition transition on basic version
Version, then taking version V is 1, according to formula (1), message type ID=100+1*1000=1100.
When needing the basic version mark X extracting message type ID, it is only necessary to according to formula:
X=message type ID mod graybase (2)
Wherein mod represents remainder number, i.e. message type ID is divided by remainder number after graybase.Due to basic version
Mark numerical value corresponding to X less than the numerical value corresponding to datum offset amount graybase, therefore mod computing can easily from
Message type ID extracts basic version mark X.
Such as, message type ID is 1100, and graybase is 1000, according to formula (2), X=1100 mod
1000=100.
Easily learn, when version V value is 0, then message type ID correspondence basic version.
When new transition version occurs, it is only necessary to take new version V and can build new message type ID.
Other computing formula can also be used in other embodiments to set message type ID, it is only necessary to meet
Message type ID correspondence current version identifications, and include the basic version of basic version that current version identifications is based on
Identify, such as by marker character spaced apart base version identifier and version number, such as by using alphanumeric etc..This
The structure rule of the message type ID in embodiment, i.e. formula (1), it is ensured that all of version identifier does not conflict, and
Can quickly show that basic version identifies.
According to above-mentioned method step, in the present embodiment, as it is shown in figure 1, system entry 203 builds obtains background request
Information 302.1, determines according to step before and issues up-to-date transition version to the requesting party that this user request information is corresponding, because of
This backstage solicited message 302.1 includes the version identifier 1100 of up-to-date transition version, is to represent clearing choosing including request content
In the code of commodity.
Then, background request information 302 is processed by background module 204, specifically, such as step S105, on backstage
After module 204 receives background request information 302, background request information 302 is resolved, read information header 401
Message type id field obtains version identifier, searches and determine the process function 205 of correspondence according to version identifier.Each
Individual background module 204 includes multiple process function 205, and each background module 204 performs at least one service, each service
Call one or the one group combination comprising multiple process function in the multiple process functions 205 in this background module 204.No
Bind with processing function 205 with version identifier correspondence different disposal function 205, i.e. version identifier.Here different editions mark
Corresponding different disposal function 205, can be the process function 205 of corresponding different of different editions mark, it is also possible to be different versions
The combination comprising multiple process function of the corresponding different groups of this mark.
The process function 205 process function corresponding to basic version identifies corresponding to the version identifier of transition version
205 full doses replicate and revise on this basis and obtain.It is envisioned that in other embodiments can also be by additive method
Obtain the process function 205 corresponding to the version identifier of transition version, such as, general subfunction is set, at the version of transition version
Processing corresponding to mark is only arranged in function 205 and the difference part of the process function 205 corresponding to basic version mark.
As it is shown in figure 1, in the present embodiment, background module A204.1 performs service: calculates and chooses commodity to carry out preferential rule
The amount of money after then.Background module A204.1 includes processing function A1 205.1 and processing function A2 205.2, version identifier
1100 is transition version, and alignment processing function A2 205.2, version identifier 100 is stable release, alignment processing function A1
205.1, process function A2 205.2 are replicated by process function A1 205.1 full dose and are revised and obtain.Background module A204.1 reads
The information header 401 of background request information 302.1 thus to obtain version identifier be 1100, determine according to version identifier 1100 and used
Process function A2 205.2.
Such as step S106, after background module 204 determines used process function 205, use processes function 205 and processes
Background request information 302.Such as, after background module A 204.1 determines that use processes function A2 205.2, use processes function A2
205.2 process background request information 302.1.
In some cases, after background module 204 platform solicited message 302 after treatment, according to background request information 302
Result, build response message 303 return requesting party 201；In other cases, a background module 204 is according to right
The result of background request information 302, rebuilds the background request information 302 including that identical version identifies, and will again
The background request information 302 built sends to other background modules 204, and therefore step S104-S106 may repeatedly perform.
It should be noted that and communicated by background request information 302 between background module 204, processing with user's request
During information 301, the background request information 302 of different background modules 204 includes that identical version identifies, by identical version mark
Knowledge can ensure the uniformity that each background module 204 processes easily.
As in figure 2 it is shown, in the present embodiment, after background module A204.1 processes background request information 302.1, according to process
Result needs to rebuild background request information 302.2, and background request information 302.2 is sent to background module B204.2.
Background request information 302.2 includes the version identifier identical with background request information 302.1, i.e. after background module B204.2 reads
Platform solicited message 302.2 obtains version identifier and is similarly 1100.It is tired to choosing commodity to calculate that background module B204.2 performs service
Add the amount of money.Background module B204.2 includes processing function B1 205.3 and processing function B2 205.4, version identifier 1100
For transition version, alignment processing function B2 205.4, version identifier 100 is stable release, alignment processing function B1 205.3, place
Reason function B2 205.4 is replicated by process function B1 205.3 full dose and is revised and obtains.Background module B204.2 obtains version identifier
After being 1100, determine used process function B2 205.4 according to version identifier 1100, and then use processes function B2
205.4 process background request information 302.2.
It should be noted that in some cases, background module 204 needs only to use stable release, i.e. needs to disable
Cross version.In this case, background request information 302 is resolved, and after obtaining version identifier, carry according to version identifier
Take basic version mark, according to basic version identifier lookup and determine correspondence process function.
Such as, if needing to disable transition version for background module 204.2, then version is obtained as background module B204.2
After being designated 1100, extract basic version according to formula (2) and be designated 100, according to the place corresponding to basic version identity validation
Reason function is for processing function B1 205.3, and then use processes function B1 205.3 and processes background request information 302.2.
Can be seen that from the above description, any one background module 204 can be chosen whether by controlling version identifier
Carry out the upgrading of stable release.Start multiple back-end system, a software version correspondence conventionally, as use simultaneously
The method of one back-end system, therefore, it is difficult to realize selecting part of module to carry out the function upgraded, and by the method for the present invention,
Achieve simply and easily and the part of module in whole software system or partial service upgraded, and part of module or
Partial service does not carries out the function upgraded.
After background request information 302 is disposed, such as step S107, background module 204 builds corresponding information 303, and
Response message 303 is beamed back requesting party 201.It should be noted that in other embodiments, it is also possible to there is no step S107, i.e.
Background module 204 is done directly this process to user request information 301 after processing background request information 302.
Be can be seen that, due to the multiple software versions in the present invention by the above description for the software distribution method of the present invention
Corresponding multiple process functions 205 are to be concurrently present in the same service of same background module 204, therefore can be only
Arrange a service, i.e. have only on line run a system process, and without arranging multiple service or overlapping back-end system more.
And prior art starts due to needs simultaneously and overlaps back-end system more, if back-end system performs timed task, then need simultaneously
It is directed to often overlap back-end system and performs many subtasks, additionally when finding that basic version is wrong, then be required for often overlapping rear end
System is modified, troublesome maintenance.And owing to can only arrange a service in the present invention, therefore can when performing timed task
To be only performed once task, when repairing version error, can once revise corresponding multiple version, thus avoid above existing
Problem in technology.
Build with the background request information 302 of version identifier owing to the present invention uses, background module 204 by identify with
The version identifier processing function binding loads different editions, is therefore no longer necessary to arrange the routing module of prior art, saves
The exploitation maintenance cost of extra routing module.It addition, owing to arranging routing module before background module in prior art, use
Family solicited message carries out transfer by routing module, if therefore user request information needs to be completed by the multistage, then may
The background module that previous stage occurs uses basic version, and before the latter half generation, version is updated so that the latter half
Background module use transition version, thus cause the disunity that system processes.And due to the fact that there is no routing module, but
Communicated by the background request information 302 with identical edition code, therefore ensured uniformity.
After transition version is stable, the user request information 301 of all requesting parties 201 all has stepped through edition code
And when being processed by transition version, the process function 205 that original and this transition version version identifier is bound and base edition
This version identifier binding, and delete the process function 205 corresponding to version identifier of former basic version simultaneously, thus realize soft
What part updated completes.Such update mode can realize the smooth online switching of new and old basic version, it is not necessary to restart original enter
Journey.
Present invention also offers a kind of software system 202, this software system 202 includes system entry 203 and at least
Individual background module 204, system entry 203 is for being rewritten as background request information 302 also by the user request information 301 received
Being sent to background module 204, at least one background module 204 receives background request information 302 and processes.Software system
The concrete operation method of 202 and data flow are described in the software distribution method above, and here is omitted.
Below it is only the concrete exemplary applications of the present invention, protection scope of the present invention is not constituted any limitation.Except above-mentioned
Outside embodiment, the present invention can also have other embodiment.The technical scheme that all employing equivalents or equivalent transformation are formed, all
Fall within scope of the present invention.
Claims (22)
1. a software distribution method, it is characterised in that include step:
Receive user request information；
Based on described user request information, determine the feature of the requesting party being associated with described user request information；
Based on described feature, determine the version identifier of the software issued to described requesting party；
Build the background request information with described version identifier and request content；
Version identifier based on described background request information, determines corresponding process function, different editions mark binding difference
Process function；
The process function corresponding with the version identifier of described background request information is used to process described background request information.
2. software distribution method as claimed in claim 1, it is characterised in that described based on described user request information, determines
The step of the feature of the requesting party being associated with described user request information includes:
According to software publishing policy, mate the version identifier of the software issued to described requesting party corresponding to described feature.
3. software distribution method as claimed in claim 1, it is characterised in that described background request information include information header and
Informosome, described information header preserves described version identifier, and described informosome preserves described request content.
4. the software distribution method as described in claim 1 or 3, it is characterised in that described version identifier mark Current software
Version, described version identifier includes the basic version mark of the basic version that current version is based on.
5. software distribution method as claimed in claim 4, it is characterised in that described version identifier meets formula message
Type ID=X+V*graybase,
Wherein, message type ID is version identifier, version identifier based on X, and V is version number, offsets on the basis of graybase
Amount,
Described basic version identifies X, and version V and datum offset amount graybase are integer,
Basic version mark numerical value corresponding to X is less than the numerical value corresponding to datum offset amount graybase.
6. software distribution method as claimed in claim 5, it is characterised in that when version V value is 0, described version identifier
Corresponding basic version.
7. software distribution method as claimed in claim 1, it is characterised in that described version based on described background request information
Mark, determines that the corresponding step processing function includes:
Described background request information is resolved, and obtains described version identifier, search according to described version identifier and determine
Corresponding process function.
8. software distribution method as claimed in claim 1, it is characterised in that described software includes current version and current version
Originally the basic version being based on, replicates the process function corresponding to basic version mark and revises, thus obtaining current version mark
Process function corresponding to knowledge.
9. software distribution method as claimed in claim 4, it is characterised in that described version based on described background request information
Mark, determines that the corresponding step processing function includes:
Described background request information is resolved, and obtains described version identifier, according to described version identifier, extract described version
This mark described basic version mark, according to described basic version identifier lookup and determine correspondence process function.
10. software distribution method as claimed in claim 1, it is characterised in that further comprise the steps of:
According to the result to described background request information, build response message and return requesting party.
11. software distribution methods as claimed in claim 1, it is characterised in that at least include the version identifier institute of stable release
Corresponding processes function and the process function corresponding to version identifier of transition version,
By the process function corresponding to the version identifier of transition version and stable release mark binding, delete the version of stable release
Process function corresponding to mark, thus complete software version update.
12. 1 kinds of software delivery systems, it is characterised in that including:
System entry, described system entry, based on the user request information received, determines and is associated with described user request information
The feature of requesting party, and based on described feature, determine that the version identifier of the software issued to described requesting party, described system enter
Mouth builds the background request information with described version identifier and request content；
At least one background module, each background module includes multiple process function, and each background module performs at least one
Individual service, one or one group in multiple process functions in background module described in each service call comprises multiple process
The combination of function, at least one background module described receive described system entry send come described background request information and based on
The version identifier of described background request information, determines corresponding process function, uses described process function to process described backstage
Solicited message, wherein different editions mark binding different disposal function.
13. software delivery systems as claimed in claim 12, it is characterised in that including:
Communicated by background request information between at least one background module described, processing with a user request information
Period, the background request information of different background modules includes that identical version identifies.
14. software delivery systems as claimed in claim 12, it is characterised in that
Described background request information includes that information header and informosome, described background request information include information header and information
Body, described information header preserves described version identifier, and described informosome preserves described request content.
15. software delivery systems as claimed in claim 12, it is characterised in that
The version of described version identifier mark Current software, described version identifier includes the basic version that current version is based on
Basic version identifies.
16. software delivery systems as claimed in claim 15, it is characterised in that
Described version identifier meets formula message type ID=X+V*graybase,
Wherein, message type ID is version identifier, version identifier based on X, and V is version number, offsets on the basis of graybase
Amount,
Described basic version identifies X, and version V and datum offset amount graybase are integer,
Basic version mark numerical value corresponding to X is less than the numerical value corresponding to datum offset amount graybase.
17. software delivery systems as claimed in claim 16, it is characterised in that when version V value is 0, described version mark
Know corresponding basic version.
18. software delivery systems as claimed in claim 12, it is characterised in that
At least one background module described receives described background request information, resolves described background request information, and obtains
Obtain described version identifier, search and determine the process function of correspondence according to described version identifier.
19. software delivery systems as claimed in claim 12, it is characterised in that
Described software includes that the basic version that current version and current version are based on replicates corresponding to basic version mark
Process function and revise, thus obtaining the process function corresponding to current version identifications.
20. software delivery systems as claimed in claim 15, it is characterised in that
At least one background module described receives described background request information, resolves described background request information, and obtains
Obtain described version identifier, extract the described basic version mark of described version identifier according to described version identifier, according to described base
Plinth version identifier is searched and determines the process function of correspondence.
21. software delivery systems as claimed in claim 12, it is characterised in that
At least one background module described, according to the result to described background request information, builds response message and returns request
Side.
22. software delivery systems as claimed in claim 12, it is characterised in that
At least one background module described, according to the result to described background request information, rebuilds and includes identical version
The background request information of mark, and the background request information rebuild is sent to other background modules.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610519114.6A CN106201606A (en) | 2016-07-04 | 2016-07-04 | software distribution method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610519114.6A CN106201606A (en) | 2016-07-04 | 2016-07-04 | software distribution method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106201606A true CN106201606A (en) | 2016-12-07 |
Family
ID=57465911
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610519114.6A Pending CN106201606A (en) | 2016-07-04 | 2016-07-04 | software distribution method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106201606A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109491700A (en) * | 2018-09-26 | 2019-03-19 | 平安科技（深圳）有限公司 | Multiple version application issued method, apparatus and relevant device |
| CN109634636A (en) * | 2018-12-17 | 2019-04-16 | 百度在线网络技术（北京）有限公司 | Application processing method, device, equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060168578A1 (en) * | 2005-01-21 | 2006-07-27 | U-Turn Media Corporation | Methods and systems for managing a mobile client in a client-server system connected via a public network |
| US7886287B1 (en) * | 2003-08-27 | 2011-02-08 | Avaya Inc. | Method and apparatus for hot updating of running processes |
| CN104143067A (en) * | 2014-08-05 | 2014-11-12 | 广东欧珀移动通信有限公司 | Implementation method of a terminal device and software sharing mechanism |
| CN104793932A (en) * | 2015-03-24 | 2015-07-22 | 百度在线网络技术（北京）有限公司 | Method and device used for software release |
| CN105389172A (en) * | 2015-12-07 | 2016-03-09 | 深圳市金锐显数码科技有限公司 | Application upgrading method and apparatus |
-
2016
- 2016-07-04 CN CN201610519114.6A patent/CN106201606A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7886287B1 (en) * | 2003-08-27 | 2011-02-08 | Avaya Inc. | Method and apparatus for hot updating of running processes |
| US20060168578A1 (en) * | 2005-01-21 | 2006-07-27 | U-Turn Media Corporation | Methods and systems for managing a mobile client in a client-server system connected via a public network |
| CN104143067A (en) * | 2014-08-05 | 2014-11-12 | 广东欧珀移动通信有限公司 | Implementation method of a terminal device and software sharing mechanism |
| CN104793932A (en) * | 2015-03-24 | 2015-07-22 | 百度在线网络技术（北京）有限公司 | Method and device used for software release |
| CN105389172A (en) * | 2015-12-07 | 2016-03-09 | 深圳市金锐显数码科技有限公司 | Application upgrading method and apparatus |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109491700A (en) * | 2018-09-26 | 2019-03-19 | 平安科技（深圳）有限公司 | Multiple version application issued method, apparatus and relevant device |
| CN109634636A (en) * | 2018-12-17 | 2019-04-16 | 百度在线网络技术（北京）有限公司 | Application processing method, device, equipment and medium |
| CN109634636B (en) * | 2018-12-17 | 2022-05-17 | 百度在线网络技术（北京）有限公司 | Application processing method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107506219A (en) | A kind of general version upgrade method based on android system | |
| CN104134109A (en) | Engineering configuration method and engineering configuration system integrating version management | |
| CN1886976B (en) | Method and apparatus for performing actions on a wireless device using action lists and versioning | |
| CN109408067A (en) | A kind of data managing method and server based on monomer applications | |
| CN102279749A (en) | Method and equipment for merging codes | |
| CN111669428A (en) | Vehicle remote upgrading method and system and cloud server | |
| CN105005543A (en) | Interface generation apparatus and method | |
| CN108520019A (en) | Data managing method, device, equipment and computer readable storage medium | |
| US10776313B2 (en) | Converting source objects to target objects | |
| CN113535206B (en) | Multi-version code upgrading method and system | |
| CN107122362A (en) | Cloud database resource extends the method and system with service extension | |
| CN102855305A (en) | Data upgrading method and device | |
| CN106201606A (en) | software distribution method and system | |
| CN106130751B (en) | A kind of upgrade status data administrator, system and method | |
| CN109842482B (en) | Information synchronization method, system and terminal equipment | |
| CN114663177B (en) | State change control method, device, electronic device and storage medium | |
| CN112835571B (en) | Automatic RESTful API code generation method based on Laravel framework | |
| CN114490647A (en) | Parameter value acquisition method, controller, terminal device and readable storage medium | |
| US7460552B2 (en) | Method for managing a group in a star network and apparatus using the method | |
| CN115729946B (en) | Method, device, equipment and storage medium for processing distributed transaction | |
| CN115390939B (en) | Service processing method and system | |
| CN104156586A (en) | Information integration exchange method suitable for PDM system | |
| CN112506580A (en) | Data fusion method and device, storage medium and electronic device | |
| CN110851169B (en) | A method and system, medium and electronic device for updating patch information | |
| CN110378664B (en) | Method and device for establishing contract on line, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Inventor after: Wu Binwei Inventor after: Ding Shun Inventor before: Wu Binwei |
|
| CB03 | Change of inventor or designer information | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 200433 Room 201, 10 B, 619 Longchang Road, Yangpu District, Shanghai. Applicant after: Excellent Polytron Technologies Inc Address before: 200433 room 1207-10, 6 Wade Road, Yangpu District, Shanghai. Applicant before: SHANGHAI UCLOUD INFORMATION TECHNOLOGY CO., LTD. |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20161207 |