CN107977223B - Configuration compatibility checking method and device - Google Patents
Configuration compatibility checking method and device Download PDFInfo
- Publication number
- CN107977223B CN107977223B CN201711160928.6A CN201711160928A CN107977223B CN 107977223 B CN107977223 B CN 107977223B CN 201711160928 A CN201711160928 A CN 201711160928A CN 107977223 B CN107977223 B CN 107977223B
- Authority
- CN
- China
- Prior art keywords
- compatibility
- change
- configuration
- version number
- configuration information
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
Abstract
The application provides a configuration compatibility checking method, which is characterized by comprising the following steps: acquiring a configuration file before upgrading, a first version number and a second version number before upgrading and a second version number after upgrading, wherein the configuration file comprises at least one item of configuration information; acquiring a pre-established compatibility change table, wherein the compatibility change table comprises all configuration information items with compatibility change and the version number of each configuration information item with compatibility change; according to the compatibility change table, determining a configuration information item with compatibility change in the configuration file after the first version number is upgraded to the second version number; and outputting the determined configuration information item with the compatibility change. By applying the scheme, the checking efficiency of the configuration compatibility checking and the accuracy of the checking result can be effectively improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for checking configuration compatibility.
Background
When the software is started or after the version is upgraded, the configuration information in the configuration file is read and analyzed, so that various configurations of the user can be recovered. For some devices in a computer network, such as special devices like switches and routers, configuration files of software therein include configuration commands in specific formats, and in the process of updating and upgrading software versions, formats of the commands in the configuration files may be changed, so that compatibility problems of configuration between different versions of the software occur, that is, the new version cannot identify the command format in the old version, and further cannot automatically perform corresponding configuration through the configuration files. For example, in a certain version of software, the command configuring the IPv4 address for the interface is "IPv 4 address a.b.c.d/M", while in another new version, the command is changed to "ip address a.b.c.d/M", and after the new version is upgraded, the software cannot identify the "IPv 4 address a.b.c.d/M" command in the configuration file, and will not configure the IPv4 address for the interface. Therefore, when the software version is upgraded, configuration compatibility between the new version and the old version needs to be checked in addition to recovering each configuration by reading and analyzing the configuration information in the configuration file.
In the prior art, version data such as a version specification and the like are generally checked manually, and a command of changing a format between versions before and after upgrading is checked, so that configuration which cannot be automatically read and executed through software is confirmed, and the upgraded version is reconfigured. However, the manual one-by-one inspection process is complicated, time-consuming and labor-consuming, and the condition of missing inspection cannot be eliminated.
Disclosure of Invention
In view of the above, the present application provides a method and an apparatus for checking configuration compatibility, and the technical solution is as follows:
a configuration compatibility checking method, the method comprising:
acquiring a configuration file before upgrading, a first version number and a second version number before upgrading and a second version number after upgrading, wherein the configuration file comprises at least one item of configuration information;
acquiring a pre-established compatibility change table, wherein the compatibility change table comprises all configuration information items with compatibility change and the version number of each configuration information item with compatibility change;
according to the compatibility change table, determining a configuration information item with compatibility change in the configuration file after the first version number is upgraded to the second version number;
and outputting the determined configuration information item with the compatibility change.
A configuration compatibility checking apparatus, comprising:
the input module is used for obtaining a configuration file before upgrading, a first version number and a second version number before upgrading and a second version number after upgrading, wherein the configuration file comprises at least one item of configuration information;
the input module is further configured to obtain a pre-established compatibility change table, where the compatibility change table includes all configuration information items that are subjected to compatibility change and a version number of each configuration information item that is subjected to compatibility change;
the checking module is used for determining a configuration information item with compatibility change in the configuration file after the first version number is upgraded to the second version number according to the compatibility change table;
an output module for outputting the determined configuration information item with the compatibility change.
According to the technical scheme, the compatibility change table is established in advance, the compatibility change conditions of the configurations in the versions are summarized in the table, and whether the existing configurations of the old version of the software are subjected to compatibility change or not is checked between the two versions before and after upgrading in the table, so that the configuration which cannot be automatically read and executed through the software in the new version is automatically confirmed, manual comprehensive checking is not needed, and the efficiency and the accuracy of configuration compatibility checking are improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application. Moreover, not all of the above-described effects need to be achieved by any of the embodiments in this application.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required in the description of the embodiments will be briefly introduced below, and it is apparent that the drawings in the following description are only some embodiments described in the present invention, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic flow chart of a configuration compatibility checking method of the present application;
FIG. 2 is a schematic illustration of a configuration file of the present application;
FIG. 3 is a schematic structural diagram of the configuration compatibility checking apparatus of the present application;
FIG. 4 is a schematic structural diagram of an inspection module of the present application;
FIG. 5 is a schematic diagram of one configuration of an inspection submodule of the present application;
fig. 6 is another structural schematic diagram of the inspection submodule of the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be described in detail below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.
First, a configuration compatibility checking method according to an embodiment of the present application is described, and referring to fig. 1, the method may include the following steps:
s101, obtaining a configuration file before upgrading, a first version number and a second version number before upgrading, wherein the configuration file comprises at least one item of configuration information;
when the version of the software is upgraded, the configuration information in the configuration file can be read and analyzed to recover the existing configurations of the software before the upgrade, but the format of the configuration command may be changed during the iterative update of the version, so that the upgraded software cannot identify the configuration command before the upgrade, and therefore, it is necessary to check whether the configuration file before the upgrade has a configuration that cannot be identified by the upgraded software, that is, whether the configuration before and after the upgrade has a compatibility problem.
The configuration file of the software generally includes a version number and configuration information of each configuration, for example, as shown in fig. 2, a version 2.1 of the software includes functions A, C and D, each function includes at least one piece of configuration information, where the configuration information item is a division of the configuration file for facilitating configuration compatibility check in the embodiment of the present application, and a specific division manner may be multiple, for example, each configuration command and command parameter may be one configuration information, a set of multiple configuration commands and command parameters, such as multiple configuration commands and command parameters with mutually associated formats or parameters, may be one configuration information, and even all configurations of each function may be one configuration information, which is not limited in the embodiment of the present application in theory, and a person skilled in the art may in practical applications, setting is carried out according to the requirement.
In order to perform configuration compatibility check before and after upgrading, a configuration file before upgrading and a version number before and after upgrading need to be obtained. The version number can be obtained by reading the configuration file before and after upgrading, or can be obtained by other modes such as user specification.
S102, obtaining a pre-established compatibility change table, wherein the compatibility change table comprises all configuration information items with compatibility change and the version number of each configuration information item with compatibility change;
before configuration compatibility check, a compatibility change table of software configuration may be pre-established, where the table may include all configuration information of software that has undergone compatibility change and all corresponding version numbers of the software that has undergone compatibility change, and specifically may adopt multiple forms, where table 1 and table 2 respectively give two available form forms, and those skilled in the art may select other forms as needed in practical application.
As shown in table 1 below, the change information is configured in a group with each row in the table, the first column is the item number of the configuration information, and the other columns are the version number where the compatibility change occurs. Each row of the table, i.e. each group of configuration change information, corresponds to one item of configuration information one to one, and includes all version numbers of the configuration information item with compatibility change, and the version numbers can be recorded according to the sequence of version update. The configuration information that has not been changed in compatibility may not be recorded in the table, or only the configuration information item number may be recorded.
TABLE 1
As shown in table 2 below, each row in the table is used as a set of version change information, the first column is the version number after each version update, and the other columns are the item numbers of the configuration information items with compatibility changes. Each row of the table, namely each group of version change information, corresponds to one version update one by one, and comprises configuration information item numbers with compatibility change after updating. The version number for which compatibility change occurs in no configuration information item may not be recorded in the table, or only the version number may be recorded.
TABLE 2
In order to ensure the accuracy of the configuration compatibility check, the content of the compatibility change table needs to be updated after each version update. If there is an incompatible change in the configuration information item in the updated version, the corresponding item number needs to be added to the corresponding change information group. For the configuration information items that are newly added or removed after the version update, the corresponding update can also be performed in the table.
S103, according to the compatibility change table, determining a configuration information item with compatibility change in the configuration file after the first version number is upgraded to the second version number;
after the configuration file before the upgrade, the version number before and after the upgrade, and the compatibility change table are obtained, the configuration information item in which the compatibility change occurs in the configuration file may be checked and determined, and specifically, various implementation manners may be available. For example, the configuration information items specifically included in the configuration file may be determined, taking the configuration file shown in fig. 2 as an example, and include 12 configuration information items, such as a1, a2, A3, and the like, and at the same time, the range of version numbers to be checked may be determined, for example, if the version number before upgrading can be read from the configuration file is 2.1, and the version number after upgrading is 2.4, it can be known that the version number to be checked includes 2.2, 2.3, and 2.4, or a section (2.1,2.4 ]. determining the configuration information items included in the configuration file and the version number sections before and after upgrading, that each configuration information item included in the configuration file can be confirmed one by one in the pre-established compatibility change table, and whether compatibility change occurs in the version number sections, the following takes the form of two compatibility change tables of table 1 and table 2 as an example, the description will be specifically made.
Assuming that the compatibility change table is in the form of table 1, first, 12 items of configuration information, such as a1, a2, A3, etc., may be searched, whether there is a corresponding configuration change information set in the table is found, and it is determined that a1 and B2 have a corresponding configuration change information set in the table. Then, it can check whether the version numbers of a1 and B2 recorded in the table are in the version number section (2.1, 2.4), and check determines that the version number 2.4 of a1 is in the section, and the version number 2.1 of a1 and the version number 1.2 of B2 are not in the section, so it can be determined that the configuration information item with compatibility change in the configuration file is only a 1.
Assuming that the compatibility change table is in the form of table 2, first, the version change information group corresponding to the version number interval (2.1,2.4] can be searched, and it can be known from table 2 that the interval corresponds to three rows with updated version numbers of 2.2, 2.3, and 2.4. then, it can be checked whether 12 configuration information items, such as a1, a2, A3, etc., are included in the three rows, and it can be determined through checking that 12 configuration information items are not included in versions 2.2 and 2.3, and a configuration information item a1 is included in version 2.4, so that it can be determined that there is only a1 as the configuration information item in which the compatibility change occurs in the configuration file.
S104, outputting the determined configuration information item with the compatibility change.
After determining the configuration information item with compatibility change in the configuration file, a specific configuration information item or item number may be output. If it is determined that there is no configuration information item in which compatibility change occurs in the upgraded configuration file, an empty file may be output, or a prompt such as "no configuration compatibility problem" may be output.
In addition, although the software upgrading process must be performed on the installed device, the process of configuring the compatibility check may be performed locally on the device, may be performed by a remote connection server, may be performed by an external device, and the like, and the check may be performed at any time during and before upgrading without affecting the upgrading process, and a person skilled in the art may select the compatibility check according to the device, the external condition, and other specific settings of the software in the practical application, which is not limited in the present application.
Corresponding to the above method embodiment, the present application further provides a configuration compatibility checking device, as shown in fig. 3, the device may include:
an input module 110, configured to obtain a configuration file before upgrade, and a first version number and a second version number before and after upgrade, where the configuration file includes at least one item of configuration information;
the input module 110 is further configured to obtain a pre-established compatibility change table, where the compatibility change table includes all configuration information items that have undergone compatibility change and a version number of each configuration information item that has undergone compatibility change;
the checking module 120 is configured to determine, according to the compatibility change table, a configuration information item in the configuration file, where compatibility change occurs after the configuration file is upgraded from the first version number to the second version number;
an output module 130, configured to output the determined configuration information item with the compatibility change.
In one embodiment of the present application, referring to fig. 4, the checking module 130 may include:
an obtaining submodule 131, configured to obtain configuration information items in the configuration file;
forming a sub-module 132 for forming a version number interval not including the first version number and including the second version number;
the checking submodule 133 is configured to determine whether compatibility change occurs in the version number interval for each item of the obtained configuration information according to the compatibility change table.
In a specific embodiment of the present application, the compatibility change table may include:
at least one group of configuration change information, wherein each group of configuration change information comprises one item of configuration information with compatibility change and all version numbers with compatibility change of the included configuration information.
In one embodiment of the present application, referring to fig. 5, the checking sub-module 133 may include:
a first searching unit 133a, configured to search each obtained configuration information item, and a corresponding configuration change information group in the compatibility change table;
the first determining unit 133b is configured to determine that the compatibility of the corresponding configuration information item is changed if the searched configuration change information group includes the version number in the version number interval.
In a specific embodiment of the present application, the compatibility change table may include:
and at least one group of version change information, wherein each group of version change information corresponds to one version update and comprises an updated version number and a configuration information item with compatibility change.
In one embodiment of the present application, referring to fig. 6, the checking sub-module 133 may include:
a second searching unit 133c, configured to search at least one set of version change information corresponding to the version number interval according to the version number included in the version change information set;
the second determining unit 133d is configured to determine that compatibility change occurs to the included configuration information item if the obtained configuration information item is included in the at least one set of found version change information.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
Embodiments of the subject matter and the functional operations described in this specification can be implemented in: digital electronic circuitry, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a tangible, non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. In other instances, features described in connection with one embodiment may be implemented as discrete components or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Further, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (8)
1. A configuration compatibility checking method, the method comprising:
acquiring a configuration file before upgrading, a first version number and a second version number before upgrading and a second version number after upgrading, wherein the configuration file comprises at least one item of configuration information;
acquiring a pre-established compatibility change table, wherein the compatibility change table comprises all configuration information items with compatibility change and the version number of each configuration information item with compatibility change;
obtaining configuration information items in the configuration file;
forming a version number interval which does not include the first version number and includes the second version number;
according to the compatibility change table, determining whether each item of acquired configuration information is subjected to compatibility change in the version number interval;
and outputting the determined configuration information item with the compatibility change.
2. The method of claim 1, wherein the compatibility change table comprises:
at least one group of configuration change information, wherein each group of configuration change information comprises one item of configuration information with compatibility change and all version numbers with compatibility change of the included configuration information.
3. The method according to claim 2, wherein the determining whether the compatibility change occurs in the version number interval for each item of configuration information obtained according to the compatibility change table comprises:
searching each obtained configuration information item, and configuring a corresponding configuration change information group in the compatibility change table;
and if the searched configuration change information group comprises the version number in the version number interval, determining that the compatibility change of the corresponding configuration information item occurs.
4. The method of claim 1, wherein the compatibility change table comprises:
and at least one group of version change information, wherein each group of version change information corresponds to one version update and comprises an updated version number and a configuration information item with compatibility change.
5. The method according to claim 4, wherein the determining whether the compatibility change occurs in the version number interval for each item of configuration information obtained according to the compatibility change table comprises:
searching at least one group of version change information corresponding to the version number interval according to the version number included in the version change information group;
and if the obtained configuration information item is included in the at least one group of searched version change information, determining that the compatibility of the included configuration information item is changed.
6. A configuration compatibility checking apparatus, characterized in that the apparatus comprises:
the input module is used for obtaining a configuration file before upgrading, a first version number and a second version number before upgrading and a second version number after upgrading, wherein the configuration file comprises at least one item of configuration information;
the input module is further configured to obtain a pre-established compatibility change table, where the compatibility change table includes all configuration information items that are subjected to compatibility change and a version number of each configuration information item that is subjected to compatibility change;
the checking module is used for obtaining the configuration information items in the configuration file; forming a version number interval which does not include the first version number and includes the second version number; according to the compatibility change table, determining whether each item of acquired configuration information is subjected to compatibility change in the version number interval;
an output module for outputting the determined configuration information item with the compatibility change.
7. The apparatus of claim 6, wherein the compatibility change table comprises:
at least one group of configuration change information, wherein each group of configuration change information comprises one item of configuration information with compatibility change and all version numbers with compatibility change of the included configuration information.
8. The apparatus of claim 7, wherein the inspection module comprises:
a first searching unit, configured to search each obtained configuration information item, and a corresponding configuration change information group in the compatibility change table;
and the first determining unit is used for determining that the compatibility change occurs to the corresponding configuration information item if the searched configuration change information group comprises the version number in the version number interval.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711160928.6A CN107977223B (en) | 2017-11-20 | 2017-11-20 | Configuration compatibility checking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711160928.6A CN107977223B (en) | 2017-11-20 | 2017-11-20 | Configuration compatibility checking method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107977223A CN107977223A (en) | 2018-05-01 |
| CN107977223B true CN107977223B (en) | 2020-12-04 |
Family
ID=62010573
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711160928.6A Active CN107977223B (en) | 2017-11-20 | 2017-11-20 | Configuration compatibility checking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107977223B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110519649B (en) * | 2018-05-22 | 2022-04-19 | 青岛海尔多媒体有限公司 | Control method and device of split television and computer readable storage medium |
| CN109491701A (en) * | 2018-11-01 | 2019-03-19 | 郑州云海信息技术有限公司 | A kind of configuration information recovery method, system, equipment and computer storage medium |
| CN109658588A (en) * | 2019-01-25 | 2019-04-19 | 浪潮金融信息技术有限公司 | A method of realizing that intelligence configures can recognize banknote |
| CN110286926B (en) * | 2019-06-20 | 2021-05-11 | 西北工业大学 | Industrial machine updating method and device |
| CN112988222B (en) * | 2021-04-25 | 2022-04-08 | 郑州信大捷安信息技术股份有限公司 | Method and system for checking information system integration project interface version compatibility |
| CN113805961B (en) * | 2021-08-27 | 2023-09-15 | 中国航空无线电电子研究所 | Product software and hardware compatibility management method based on compatibility list file |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101286881A (en) * | 2008-05-16 | 2008-10-15 | 中兴通讯股份有限公司 | Device for implementing multi-version compatibility of software configuration data of base station and application thereof |
| CN102244652A (en) * | 2010-05-13 | 2011-11-16 | 阿里巴巴集团控股有限公司 | Method and system for generating session information and application server |
| CN102902707A (en) * | 2012-08-01 | 2013-01-30 | 杭州华三通信技术有限公司 | Method for realizing compatibility of binary data with different versions and data version converting system |
| CN104932973A (en) * | 2014-03-21 | 2015-09-23 | 腾讯科技（深圳）有限公司 | Version compatibility test method and apparatus |
| US9678728B1 (en) * | 2012-03-29 | 2017-06-13 | Emc International Company | Version compatibility |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE10008245A1 (en) * | 2000-02-23 | 2001-09-06 | Siemens Ag | Method for ensuring compatibility and method for data backup within a distributed computer system having several sub-computer systems |
| CA2601937C (en) * | 2005-04-18 | 2013-01-22 | Research In Motion Limited | Implementing data-compatibility-based version scheme |
| CN100551088C (en) * | 2006-02-23 | 2009-10-14 | 华为技术有限公司 | A kind of method that detects upgrade software and top-set hardware compatibility |
| CN100517229C (en) * | 2006-10-31 | 2009-07-22 | 中兴通讯股份有限公司 | Data version upgrading method |
| CN103186391B (en) * | 2011-12-29 | 2016-05-11 | 腾讯科技（深圳）有限公司 | Browser upgrade method and system and a kind of upgrade server |
-
2017
- 2017-11-20 CN CN201711160928.6A patent/CN107977223B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101286881A (en) * | 2008-05-16 | 2008-10-15 | 中兴通讯股份有限公司 | Device for implementing multi-version compatibility of software configuration data of base station and application thereof |
| CN102244652A (en) * | 2010-05-13 | 2011-11-16 | 阿里巴巴集团控股有限公司 | Method and system for generating session information and application server |
| US9678728B1 (en) * | 2012-03-29 | 2017-06-13 | Emc International Company | Version compatibility |
| CN102902707A (en) * | 2012-08-01 | 2013-01-30 | 杭州华三通信技术有限公司 | Method for realizing compatibility of binary data with different versions and data version converting system |
| CN104932973A (en) * | 2014-03-21 | 2015-09-23 | 腾讯科技（深圳）有限公司 | Version compatibility test method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107977223A (en) | 2018-05-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107977223B (en) | Configuration compatibility checking method and device | |
| WO2017071494A1 (en) | Application deployment method and apparatus | |
| US10423585B2 (en) | Method and device for making differential upgrade package, and method and device for system differential upgrading | |
| US9405630B2 (en) | Methods and apparatus to perform site recovery of a virtual data center | |
| CN105262831A (en) | Method, device, and synchronizing system for synchronizing data among memory systems | |
| CN105187475B (en) | The method and system that data synchronize | |
| US7765439B2 (en) | Traceability management apparatus, storage medium storing program, and tracing method | |
| CN113254033B (en) | Method and device for generating master disc file, electronic equipment and storage medium | |
| CN111443912A (en) | Page rendering method and device based on components, computer equipment and storage medium | |
| EP3015987A1 (en) | System update method, apparatus, and device | |
| US9990363B2 (en) | Methods and apparatus of using customizable templates in initializing process control devices | |
| CN106709066B (en) | Data synchronization method and device | |
| CN106909429A (en) | A kind of synchronous upgrade method and device | |
| CN112149035A (en) | Website static resource processing method and device | |
| CN104462342A (en) | Synchronous processing method and device for database snapshots | |
| CN106383755A (en) | Method, apparatus and system for recovering slave database from master-slave database system | |
| CN104298618B (en) | The command handling method and device of a kind of intelligent terminal | |
| CN104199689B (en) | The installation method and device of comprehensive front-end system | |
| JP5905313B2 (en) | Information processing apparatus, information processing method, information processing system, and program | |
| CN112527446A (en) | Time zone synchronization method, equipment and terminal equipment | |
| US10936563B2 (en) | System and method for merging a source data from a source application into a target data of a target application | |
| CN113867754A (en) | Firmware maintenance method, system, equipment and medium | |
| CN108710665B (en) | Data backflow method, device, system and equipment | |
| CN105302425B (en) | A kind of processing method and electronic equipment of application | |
| CN103379167A (en) | Multipoint synchronous storing file downloading exception handling system and method |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210621 Address after: 310051 05, room A, 11 floor, Chung Cai mansion, 68 Tong Xing Road, Binjiang District, Hangzhou, Zhejiang. Patentee after: Hangzhou Dip Information Technology Co.,Ltd. Address before: 6 / F, Zhongcai building, 68 Tonghe Road, Binjiang District, Hangzhou City, Zhejiang Province Patentee before: Hangzhou DPtech Technologies Co.,Ltd. |
|
| TR01 | Transfer of patent right |