CN111008028A - Software upgrading method, device and storage medium - Google Patents
Software upgrading method, device and storage medium Download PDFInfo
- Publication number
- CN111008028A CN111008028A CN201911152687.XA CN201911152687A CN111008028A CN 111008028 A CN111008028 A CN 111008028A CN 201911152687 A CN201911152687 A CN 201911152687A CN 111008028 A CN111008028 A CN 111008028A
- Authority
- CN
- China
- Prior art keywords
- software
- data
- version
- upgraded
- new
- 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.)
- Granted
Links
Images
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
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 relates to a software upgrading method, which comprises the following steps: respectively and correspondingly recording module information of software, an entity object required by software operation, characteristic attributes of the entity object and a software interface by using a module information table, a model field table and an action table; respectively recording the associated identifications of the module information table, the model field table and the action table by using the installation registry; comparing the difference between the new version and the target version to be upgraded based on the installation registry of the new version and the installation registry of the target version to be upgraded; and upgrading the target version to be upgraded based on the data of the new version which is more than the target version to be upgraded in the difference comparison result and the data of the new version and the target version to be upgraded which exist but have difference. The invention has the beneficial effects that: the problem of low upgrading speed is solved; using delta calculations solves the problem of smooth upgrades and thus greatly reduces the amount of data required for an upgrade and narrows the scope of impact.
Description
Technical Field
The invention belongs to the technical field of software upgrading, and particularly relates to a software upgrading method, software upgrading equipment and a storage medium.
Background
At present, the upgrading modes of software products are mainly divided into two types:
the first type is a way of upgrading with a new version of the complete installation package. And packaging the historical version non-updating part, the historical version updating part and the new version part into a new version installation package, and then completely covering the content of the existing version installation package with the new version installation package for upgrading.
Because the upgrade mode uses the installation package containing all functions to carry out the whole upgrade, the differential upgrade aiming at the functions used by the software user can not be finished. If a user needs to upgrade and add some special function points, the part of special function points also need to be packaged into an integral installation package for upgrading. The upgrading not only needs a large amount of data to be processed and the upgrading speed is reduced, but also users who do not need the part of function points are upgraded to add the function points.
The second type is an upgrade mode in which components (or modules) having different version numbers are updated by comparing version number increments of software components (or modules). This approach can satisfy isolation update at the component (or module) level, but cannot solve the problem of independent installation of dependent function points between components (or modules). Due to the dependency among the components (or modules), most of the components (or modules) in the upgrade software installation package are likely to need to be upgraded to complete the update, so that the effect of updating at the component (or module) level is reduced.
By combining the two main upgrading methods, the existing software upgrading method affects the existing functions of the whole assembly or the whole software during upgrading, and the upgrading needs large data volume to be processed and is slow in upgrading speed.
Disclosure of Invention
In order to solve the problems of large data volume required to be processed for upgrading and low upgrading speed in the prior art, the invention provides a software upgrading method, equipment and a storage medium, which have the characteristics of high upgrading speed, reduction of data volume required for upgrading, reduction of influence range and the like.
A software upgrading method according to the specific embodiment of the invention comprises the following steps:
respectively and correspondingly recording module information of software, an entity object required by software operation, characteristic attributes of the entity object and a software interface by using a module information table, a model field table and an action table;
respectively recording the module information table, the model field table and the association identification of the action table by using an installation registry;
performing delta comparison on the new version and the target version to be upgraded based on the installation registry of the new version and the installation registry of the target version to be upgraded;
and upgrading the target version to be upgraded based on the data of the new version which is more than the target version to be upgraded in the differential comparison result and the data of the new version and the target version to be upgraded which have differences.
Further, upgrading the version of the target version to be upgraded based on the data of the new version that is more than the target version to be upgraded and the data of the new version and the target version to be upgraded that are different but exist:
recording data of the new version which is more than the target version to be upgraded by using a newly added queue;
recording data of the new version and the target version to be upgraded which are different but exist by using an updating queue;
constructing a new data table based on the model and the model field in the newly added queue;
constructing a new software interface based on the actions in the newly added queue;
updating the new data table based on the model in the update queue;
updating data table fields in the new data table based on model fields in the update queue;
replacing the software interface in the update queue with the new software interface.
Further, the software upgrading method further comprises the following steps:
recording data of the target version to be upgraded which is more than the new version by using a waste queue, and marking the data as waste data;
restricting a user from using modules, models, model fields, and actions contained in the obsolete data.
Further, after replacing the software interface in the update queue with the new software interface, the method further includes:
and recovering system resources occupied by the modules, the models, the model fields and the actions contained in the waste data.
Further, when the difference comparison is performed on the new version and the target version to be upgraded, a data part which is different from the new version and the target version to be upgraded is omitted.
Further, the process of recording data in which the new version and the target version to be upgraded exist but are different by using the update queue includes:
and determining the data with difference by judging whether the last updating time of the data with the same technical name in the installation registry of the new version and the target version to be upgraded is the same or not.
Further, the module information table includes:
the module table, the module classification table and the module dependency table are used for describing the modules contained in the software and the dependency relationship among the modules.
Further, the entity objects required by the software to run comprise:
modules, module classes, module dependencies, models, model fields, actions, and business models.
A software upgrading device according to an embodiment of the present invention includes: a processor, and a memory coupled to the processor;
the memory is for storing a computer program for at least performing the software upgrade method as described above;
the processor is used for calling and executing the computer program in the memory.
A storage medium according to an embodiment of the present invention stores a computer program which, when executed by a processor, implements a software upgrade method as described above.
The invention has the beneficial effects that: by adopting an upgrading mode with smaller granularity, the installation registry is used for carrying out corresponding association based on modules, models, model fields and actions contained in data of a new version and the existing version, the corresponding data is read through the installation registry, row-column-level difference comparison can be carried out, and a part needing upgrading is judged; using delta calculations solves the problem of smooth upgrades and thus greatly reduces the amount of data required for an upgrade and narrows the scope of impact.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of a method of software upgrade provided in accordance with an exemplary embodiment;
FIG. 2 is a diagram of a definition of a module table provided in accordance with an exemplary embodiment;
FIG. 3 is a diagram of a definition of a module classification table provided in accordance with an exemplary embodiment;
FIG. 4 is a definition diagram of a module dependency table provided in accordance with an illustrative embodiment;
FIG. 5 is a diagram of a specific application of a module table provided in accordance with an exemplary embodiment;
FIG. 6 is a diagram of a specific application of a module classification table provided in accordance with an exemplary embodiment;
FIG. 7 is a diagram of a specific application of a module dependency table provided in accordance with an illustrative embodiment;
FIG. 8 is a definition diagram of a model table provided in accordance with an exemplary embodiment;
FIG. 9 is a diagram of a specific application of a model table provided in accordance with an exemplary embodiment;
FIG. 10 is a diagram of a definition of a model field table provided in accordance with an illustrative embodiment;
FIG. 11 is a table of user model fields provided in accordance with an exemplary embodiment;
FIG. 12 is a definition diagram of an action table provided in accordance with an exemplary embodiment;
FIG. 13 is a diagram of a specific application of an action table provided in accordance with an exemplary embodiment;
FIG. 14 is a definition diagram of an installation registry provided in accordance with an exemplary embodiment;
FIG. 15 is an installation registry diagram for an existing version provided in accordance with an exemplary embodiment;
FIG. 16 is a diagram of an installation registry for a new version provided in accordance with an exemplary embodiment;
FIG. 17 is a table of original users provided in accordance with an exemplary embodiment;
FIG. 18 is a new user table provided in accordance with an exemplary embodiment;
FIG. 19 is a user log table provided in accordance with an exemplary embodiment;
FIG. 20 is a diagram of the relationship between portions of software provided in accordance with an exemplary embodiment;
FIG. 21 is a delta description diagram in an upgrade process provided in accordance with an exemplary embodiment;
FIG. 22 is a relational diagram providing software update based on delta comparisons according to an exemplary embodiment;
FIG. 23 is a block diagram of a manner in which delta escalation between different users is provided according to an example embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without any inventive step, are within the scope of the present invention.
Referring to fig. 1, an embodiment of the present invention provides a software upgrading method, including the following steps:
101. respectively and correspondingly recording module information of software, an entity object required by software operation, characteristic attributes of the entity object and a software interface by using a module information table, a model field table and an action table;
102. respectively recording the associated identifications of the module information table, the model field table and the action table by using the installation registry;
103. comparing the difference between the new version and the target version to be upgraded based on the installation registry of the new version and the installation registry of the target version to be upgraded;
104. and upgrading the target version to be upgraded based on the data of the new version which is more than the target version to be upgraded in the difference comparison result and the data of the new version and the target version to be upgraded which exist but have difference.
Specifically, for a new version and an existing version (target version to be upgraded) of software, the software upgrade for the existing version includes:
201. and describing the modules contained in the new version software and the dependency relationship among the modules by using the module table, the module classification table and the module dependency table contained in the module information table. The definitions of the module table, the module classification table and the module dependency table are shown in fig. 2 to 4. The display name display _ name of the module table is a name displayed by a user interface, and the technical name is a unique module index used by software operation. For example, with reference to fig. 5-7, certain software includes three modules: the system comprises a user module, a member module and a point module. And describing the dependency relationship between the modules of the software and the module by using the module table, the module classification table and the module dependency table to express the relationship between the modules and the components.
202. And describing entity objects required by the operation of the new version software by using the model table, wherein the entity objects comprise modules, module classifications, module dependencies, models, model fields, actions and business models. The model table is shown in fig. 8, where the technology name in the model table is a unique index of the model used for software operation, and the model instance table name cname is the name of the data table created in the database by each model. For example, referring to FIG. 9, the user module contains two models: and the user model and the role model respectively describe and record the functions of the user model and the role model.
203. And describing the characteristic attributes of the entity objects required by the operation of the new version software by using the model field table. Refer to the definition diagram of the model field table shown in FIG. 10. The technical name in the model field table is the unique index of the model field used by software operation, the model ID is the ID of the model to which the current field belongs, and the field name cname of the model instance table is the table field name of the model instance data table established in the database. For example, a user model contains five model fields: name, login account, password, mailbox, and mobile phone number. Describing the user model field using the model field table is shown in fig. 11, where the name includes a user identifier and a user name, and the user identifier and the user name are in a one-to-one correspondence relationship.
204. And describing a software interface required by the operation of the new version software by using the action table. As shown with reference to fig. 12. The model ID model _ ID in the action table records the incidence relation between the action and the model, and the entry name list arg _ names, the entry type list arg _ types, the exit type list return _ types and the action logic codes jointly describe the interface definition corresponding to the action. For example, the user model has one user login action. The description of the user login action using the action table is shown in fig. 13, in which the action logic code of the user login action is recorded in the code column.
205. All metadata (modules, models, model fields, actions) information for a software installation is registered using an installation registry. Referring to fig. 14, the technology name of the installation registry is a unique index, the model technology name model _ name is an association relationship between the installation registry data and the model, the association ID relationship _ ID is a data record ID in the model corresponding data table, and the data last modification time update _ date is the occurrence time of the latest update of the data record in the model corresponding data table. Taking the update of the user module in the above steps as an example, the data in the installation registry is shown in fig. 15 as the installation registry of the original version, and fig. 16 is shown as the installation registry of the new version.
When installing, the module information, the entity object and the characteristic attribute needed by the software operation and the interface are respectively recorded in the module table, the model field table and the action table, and the data ID of the module table, the model field table and the action table which are installed at this time is recorded by using the installation registry and is stored in the associated ID relationship _ ID field of the installation registry.
When upgrading, a user can read the module, the model field and the action table record by installing the registry. Because the registry is installed, the service data except the module, the model field and the action table can not be influenced during upgrading, and the normal operation of other modules is not influenced.
206. Comparing the read recorded data of the existing module, the model field and the action table with the module, the model field and the action data of the new version in row-column level differential quantity based on the installation registry of the original version and the installation registry of the new version respectively, taking the example of upgrading the user module, comparing the installation registry information of the new version shown in figure 16 with the installation registry of the original version shown in figure 15, wherein the new version adds a 'user log' model for the user model, adds a 'gender' field, adds a 'logout' action, modifies the length of a 'password' field to be 256 characters, and deletes a 'mailbox' field.
In delta comparison, the newly added queue is used to record the missing data parts of the existing version over the new version. As shown in fig. 16, the 9 th, 10 th, 11 th, 12 th, 13 th and 14 th pieces of data in the installation registry of the new version are missing data portions of the original version of the upgrade.
And when the difference quantity is compared, whether the last updating time of the data with the same technical name in the new version installation registry and the original version installation registry is different or not is judged to find out the data part with the difference. The update queue is used to record the portions of data where both the existing and new versions exist, but there is a difference. As shown in fig. 15 and 16, the 5 th piece of data in the installation registry of the original version is a data portion with a difference in the upgrade.
207. And constructing a new data table by using the corresponding model and model field in the newly added queue. As shown in fig. 17 and 18, the user table will be augmented with a "gender" field; as shown in fig. 19, the software adds a user log table to record the corresponding update.
208. And constructing a new software interface by the corresponding action in the newly added queue.
209. The existing data table is updated by updating the corresponding model in the queue.
210. The existing data table fields are updated by updating the corresponding model fields in the queue.
211. And replacing the software interface constructed by the corresponding action in the update queue.
The problem of user differentiation upgrading is solved through using the installation registry, and compared with the prior art that a smaller granularity upgrading mode is used, the part needing upgrading is determined through the difference of the rank levels of the data, so that the data volume required by upgrading is greatly reduced, the influence range is reduced, and the upgrading speed is improved.
To further optimize the technical solution in another embodiment of the present invention, during the delta comparison, the obsolete queue is used to record the data portions of the existing version that are more than the new version. As shown in fig. 15 and 16, the 6 th piece of data in the installation registry of the original version is the extra data part of the upgrade;
ignoring data portions where both the existing version and the new version exist but are not different;
and marking the corresponding module, model field and action table record in the abandon queue as abandoned.
The user is restricted from using modules, models, model fields, actions that are marked as obsolete.
The speed of upgrading is further increased by using the obsolete queues and omitting data portions where existing versions and new versions both exist but are not different.
And the system resources occupied by abandoned modules, models, model fields and actions are recovered after the software interface of the software is updated. The system resources occupied by the modules include a CPU, a database connection pool and a memory. The system resources occupied by the model and the model field comprise database storage, connection and memory. The system resources occupied by the actions include a CPU and a memory. Under the condition that the user call is limited, CPU and memory resources occupied by the software are automatically recycled by an operating system operated by the software, and the database connection pool and the connection resources are recycled by using a recycling method of the database connection component, so that the data volume and occupied space required by upgrading are further reduced.
In some embodiments of the present invention, for the problem of differential upgrading of different users, in a specific application, only difference comparison is performed between a target version to be upgraded (original version) and a new version of software of a user, and specifically, the method includes the following steps:
301. describing the modules and module dependency relationship contained in the user software by using a module table, a module classification table and a module dependency table, which is shown in fig. 20;
302. using a model to describe entity objects required by the user software to run;
303. describing the characteristic attribute of the entity object required by the operation of the user software by using a model field;
304. describing a software interface required by the user software to run by using an action;
305. all metadata (modules, models, model fields, actions) information for a software installation is registered using an installation registry, and different users use different installation registries for recording.
306. When installing, the module information, the entity object and characteristic attribute needed by software operation and the interface are respectively recorded in the module table, the model field table and the action table. And records the data record IDs of the module table, the model field table, and the action table installed this time using the installation registry, as shown in fig. 21. The installation registry is shown in fig. 15.
307. The module, model field and action table records are read by the user's own installation registry. As shown in fig. 23, since there is a user-independent installation registry, the service data other than the module, the model field, and the action table is not affected during upgrading, and the users do not affect each other.
308. Using the module to describe the module contained by the new version software for the user software;
309. describing entity objects required by the new version software for running the user software by using a model;
310. describing the characteristic attribute of the entity object required by the new version software for the operation of the user software by using the model field;
311. describing a software interface required by the new version software for running the user software by using the action;
312. comparing the read recorded data of the existing module, the model field and the action table with the difference of the module, the model field and the action data of the new version;
313. when the difference is compared, a waste queue is used for recording the data part of the existing version which is more than the new version;
314. when the difference is compared, a newly-added queue is used for recording the missing data part of the existing version compared with the new version;
315. when the difference quantity is compared, the updating queue is used for recording the data parts of which the existing version and the new version exist but have differences;
316. when comparing the difference, ignoring the data part which exists in the existing version and the new version but has no difference;
317. marking the corresponding modules, models, model fields and action table records in the abandon queue as abandoned;
318. restricting the user from using modules, models, model fields, actions that are marked as obsolete;
319. constructing a new data table by using the corresponding model and model field in the newly added queue;
320. constructing a new software interface by using the corresponding action in the newly added queue, as shown in fig. 22;
321. updating the existing data table by updating the corresponding model in the queue;
322. updating the existing data table fields by updating the corresponding model fields in the queue;
323. replacing the software interface constructed by the corresponding action in the update queue;
324. and after the software interface is updated, the software executes and recycles the system resources occupied by the abandoned modules, models, model fields and actions.
An embodiment of the present invention further provides a software upgrading apparatus, including: a processor, and a memory coupled to the processor;
the memory is used for storing a computer program, and the computer program is at least used for executing the software upgrading method described in the embodiment;
the processor is used to call and execute the computer program in the memory.
An embodiment of the present invention further provides a storage medium, where a computer program is stored, and when the computer program is executed by a processor, the software upgrading method described in the above embodiment is implemented.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean a "non-exclusive or".
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (10)
1. A method of upgrading software, comprising:
respectively and correspondingly recording module information of software, an entity object required by software operation, characteristic attributes of the entity object and a software interface by using a module information table, a model field table and an action table;
respectively recording the module information table, the model field table and the association identification of the action table by using an installation registry;
performing delta comparison on the new version and the target version to be upgraded based on the installation registry of the new version and the installation registry of the target version to be upgraded;
and upgrading the target version to be upgraded based on the data of the new version which is more than the target version to be upgraded in the differential comparison result and the data of the new version and the target version to be upgraded which have differences.
2. The software upgrading method according to claim 1, wherein upgrading based on the data of the new version that is more than the target version to be upgraded and the data of the new version and the target version to be upgraded that are both different includes:
recording data of the new version which is more than the target version to be upgraded by using a newly added queue;
recording data of the new version and the target version to be upgraded which are different but exist by using an updating queue;
constructing a new data table based on the model and the model field in the newly added queue;
constructing a new software interface based on the actions in the newly added queue;
updating the new data table based on the model in the update queue;
updating data table fields in the new data table based on model fields in the update queue;
replacing the software interface in the update queue with the new software interface.
3. The software upgrading method according to claim 2, further comprising:
recording data of the target version to be upgraded which is more than the new version by using a waste queue, and marking the data as waste data;
restricting a user from using modules, models, model fields, and actions contained in the obsolete data.
4. The software upgrading method according to claim 3, further comprising, after replacing the software interface in the update queue with the new software interface:
and recovering system resources occupied by the modules, the models, the model fields and the actions contained in the waste data.
5. The software upgrading method according to claim 1, wherein when performing delta comparison between the new version and the target version to be upgraded, a data portion of the new version and the target version to be upgraded, which are both different but not different, is omitted.
6. The software upgrading method according to claim 2, wherein the process of using the update queue to record the data that the new version and the target version to be upgraded exist but have differences comprises:
and determining the data with difference by judging whether the last updating time of the data with the same technical name in the installation registry of the new version and the target version to be upgraded is the same or not.
7. The software upgrading method according to any one of claims 1 to 6, wherein the module information table comprises:
the module table, the module classification table and the module dependency table are used for describing the modules contained in the software and the dependency relationship among the modules.
8. The software upgrading method of claim 7, wherein the entity objects required by the software to run comprise:
modules, module classes, module dependencies, models, model fields, actions, and business models.
9. A software upgrading apparatus, comprising: a processor, and a memory coupled to the processor;
the memory is used for storing a computer program for performing at least the software upgrade method of any one of claims 1 to 8;
the processor is used for calling and executing the computer program in the memory.
10. A storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the software upgrade method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911152687.XA CN111008028B (en) | 2019-11-22 | 2019-11-22 | Software upgrading method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911152687.XA CN111008028B (en) | 2019-11-22 | 2019-11-22 | Software upgrading method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111008028A true CN111008028A (en) | 2020-04-14 |
| CN111008028B CN111008028B (en) | 2022-07-01 |
Family
ID=70113651
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911152687.XA Active CN111008028B (en) | 2019-11-22 | 2019-11-22 | Software upgrading method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111008028B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111736869A (en) * | 2020-06-19 | 2020-10-02 | 浙江大搜车软件技术有限公司 | Version updating method of server-side interface and calling method of server-side interface |
| CN112287658A (en) * | 2020-11-03 | 2021-01-29 | 深圳壹账通智能科技有限公司 | Business data processing method and device, electronic equipment and medium |
| CN112597261A (en) * | 2020-12-29 | 2021-04-02 | 武汉中海庭数据技术有限公司 | High-precision map incremental data checking method and system, server and medium |
| CN115408031A (en) * | 2022-09-29 | 2022-11-29 | 北京亚控科技发展有限公司 | Application updating method and related equipment |
| CN117032765A (en) * | 2023-10-10 | 2023-11-10 | 浙江大华技术股份有限公司 | Model upgrading method, model upgrading device and computer storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050108701A1 (en) * | 2003-11-14 | 2005-05-19 | Eun-Jung Kwon | Method for processing updated application data in headend or terminal of digital data broadcasting system |
| US20060041881A1 (en) * | 2004-08-19 | 2006-02-23 | Adkasthala Bheema P | Universal upgrade architecture |
| JP2006227871A (en) * | 2005-02-17 | 2006-08-31 | Fujitsu Ten Ltd | Updating system, information processor, information distribution device, and updating method |
| US20090044195A1 (en) * | 2007-05-03 | 2009-02-12 | Kivati Software, Llc | method for performing tasks based on differences in machine state |
| CN102855305A (en) * | 2012-08-20 | 2013-01-02 | 大唐移动通信设备有限公司 | Data upgrading method and device |
| CN103002024A (en) * | 2012-11-21 | 2013-03-27 | 用友软件股份有限公司 | Application program upgrade system and application program upgrade method |
| CN103995854A (en) * | 2014-05-13 | 2014-08-20 | 大唐移动通信设备有限公司 | Equipment cross-version upgrading method and device |
| WO2014171112A1 (en) * | 2013-04-16 | 2014-10-23 | 株式会社デンソー | Map difference data distribution device, map difference data distribution method, and vehicle navigation device |
| CN104391728A (en) * | 2014-12-12 | 2015-03-04 | 北京奇虎科技有限公司 | Software upgrading delta pack acquiring method, corresponding upgrading method and device |
| US20160255090A1 (en) * | 2015-02-26 | 2016-09-01 | Kevin JOHNSTON, JR. | Method and system for securely updating a website |
| CN108108181A (en) * | 2017-12-14 | 2018-06-01 | 深圳市雷鸟信息科技有限公司 | The function renewal method, apparatus and computer readable storage medium of application program |
| CN108874406A (en) * | 2018-06-28 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of upgrade package production method and device |
| CN110347662A (en) * | 2019-07-12 | 2019-10-18 | 之江实验室 | A kind of multicenter medical data construction standard system based on generic data model |
-
2019
- 2019-11-22 CN CN201911152687.XA patent/CN111008028B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050108701A1 (en) * | 2003-11-14 | 2005-05-19 | Eun-Jung Kwon | Method for processing updated application data in headend or terminal of digital data broadcasting system |
| US20060041881A1 (en) * | 2004-08-19 | 2006-02-23 | Adkasthala Bheema P | Universal upgrade architecture |
| JP2006227871A (en) * | 2005-02-17 | 2006-08-31 | Fujitsu Ten Ltd | Updating system, information processor, information distribution device, and updating method |
| US20090044195A1 (en) * | 2007-05-03 | 2009-02-12 | Kivati Software, Llc | method for performing tasks based on differences in machine state |
| CN102855305A (en) * | 2012-08-20 | 2013-01-02 | 大唐移动通信设备有限公司 | Data upgrading method and device |
| CN103002024A (en) * | 2012-11-21 | 2013-03-27 | 用友软件股份有限公司 | Application program upgrade system and application program upgrade method |
| WO2014171112A1 (en) * | 2013-04-16 | 2014-10-23 | 株式会社デンソー | Map difference data distribution device, map difference data distribution method, and vehicle navigation device |
| CN103995854A (en) * | 2014-05-13 | 2014-08-20 | 大唐移动通信设备有限公司 | Equipment cross-version upgrading method and device |
| CN104391728A (en) * | 2014-12-12 | 2015-03-04 | 北京奇虎科技有限公司 | Software upgrading delta pack acquiring method, corresponding upgrading method and device |
| US20160255090A1 (en) * | 2015-02-26 | 2016-09-01 | Kevin JOHNSTON, JR. | Method and system for securely updating a website |
| CN108108181A (en) * | 2017-12-14 | 2018-06-01 | 深圳市雷鸟信息科技有限公司 | The function renewal method, apparatus and computer readable storage medium of application program |
| CN108874406A (en) * | 2018-06-28 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of upgrade package production method and device |
| CN110347662A (en) * | 2019-07-12 | 2019-10-18 | 之江实验室 | A kind of multicenter medical data construction standard system based on generic data model |
Non-Patent Citations (1)
| Title |
|---|
| 马苗立等: "基于字节级优化更新的云存储增量式网络编码方法研究", 《信息网络安全》 * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111736869A (en) * | 2020-06-19 | 2020-10-02 | 浙江大搜车软件技术有限公司 | Version updating method of server-side interface and calling method of server-side interface |
| CN112287658A (en) * | 2020-11-03 | 2021-01-29 | 深圳壹账通智能科技有限公司 | Business data processing method and device, electronic equipment and medium |
| CN112597261A (en) * | 2020-12-29 | 2021-04-02 | 武汉中海庭数据技术有限公司 | High-precision map incremental data checking method and system, server and medium |
| CN115408031A (en) * | 2022-09-29 | 2022-11-29 | 北京亚控科技发展有限公司 | Application updating method and related equipment |
| CN115408031B (en) * | 2022-09-29 | 2023-09-05 | 北京亚控科技发展有限公司 | Application updating method and related equipment |
| CN117032765A (en) * | 2023-10-10 | 2023-11-10 | 浙江大华技术股份有限公司 | Model upgrading method, model upgrading device and computer storage medium |
| CN117032765B (en) * | 2023-10-10 | 2024-01-16 | 浙江大华技术股份有限公司 | Model upgrading method, model upgrading device and computer storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111008028B (en) | 2022-07-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111008028B (en) | Software upgrading method, device and storage medium | |
| US9836336B2 (en) | Central registry for binding features using dynamic pointers | |
| US8589876B1 (en) | Detection of central-registry events influencing dynamic pointers and app feature dependencies | |
| US11106444B2 (en) | Cognitive expected program code installation result assessment | |
| CN100429619C (en) | Branding framework | |
| EP3499363A1 (en) | Data collection method, apparatus and system | |
| US11256712B2 (en) | Rapid design, development, and reuse of blockchain environment and smart contracts | |
| US8656126B2 (en) | Managing snapshots of virtual server | |
| US9697037B2 (en) | Tagging virtual machine instances based on commands | |
| US20070239471A1 (en) | Systems and methods for specifying security for business objects using a domain specific language | |
| US20170351506A1 (en) | Automating feature graduation | |
| US11347619B2 (en) | Log record analysis based on log record templates | |
| US9170809B1 (en) | Identifying transactions likely to be impacted by a configuration change | |
| US10757190B2 (en) | Method, device and computer program product for scheduling multi-cloud system | |
| CN109582382B (en) | Loading method and device of configuration information, storage medium and terminal equipment | |
| US20060206346A1 (en) | Activity forms for automated business processes | |
| CN110705637A (en) | User classification method and device based on application installation list information and electronic equipment | |
| US11030409B2 (en) | Identifying attributes associated with an entity using natural language processing | |
| CN111737964B (en) | Form dynamic processing method, equipment and medium | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN112181407B (en) | Service realization processing method, device, system, electronic equipment and storage medium | |
| CN114281688A (en) | Codeless or low-code automatic case management method and device | |
| CN114745305B (en) | Dynamic interaction method and system based on user behavior recognition | |
| CN113762871B (en) | Production data control method, device, equipment and storage medium | |
| CN117093638B (en) | Micro-service data initialization method, system, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |