CN106603289B - LMT configuration file smooth upgrading method - Google Patents
LMT configuration file smooth upgrading method Download PDFInfo
- Publication number
- CN106603289B CN106603289B CN201611161293.7A CN201611161293A CN106603289B CN 106603289 B CN106603289 B CN 106603289B CN 201611161293 A CN201611161293 A CN 201611161293A CN 106603289 B CN106603289 B CN 106603289B
- Authority
- CN
- China
- Prior art keywords
- configuration
- configuration file
- data
- file
- dat
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a smooth upgrading method of an LMT configuration file, which comprises the steps of upgrading the version of a base station, and storing an original configuration file into a flash memory of the base station; setting a smooth upgrading identifier of an LMT configuration file, and restarting a base station; judging whether a configuration file smooth upgrading identifier is set, if so, performing script file smooth upgrading, analyzing configuration data files of a new version and an old version, and sequentially configuring and storing data to be transplanted into a new data configuration file according to an analysis result; migrating an original configuration file in a flash memory to a backup folder; and starting other processes after the base station is upgraded. By adopting the method, the base station upgrading restart can automatically and smoothly upgrade the data configuration file and the script file, conveniently and quickly realize the upgrading of the LMT configuration file, reduce the operation complexity of the upgrading of the base station configuration file and simultaneously reduce the possibility of human errors caused by the operation errors of service personnel.
Description
Technical Field
The invention relates to the technical field of network management tools in the field of wireless communication, in particular to a smooth upgrading method for an LMT (local maintenance terminal) configuration file, which realizes data configuration of a local maintenance terminal.
Background
In the field of wireless communication, LMT (Local Maintenance Terminal) is a stand-alone network management tool for operating and maintaining a single base station, and LMT software mainly includes the following functions: data configuration, alarm processing, diagnostic testing, real-time performance measurement and the like, for example, a data configuration module completes the configuration process of data required by the normal work of a base station; the alarm processing module completes the real-time receiving and inquiring functions of the base station alarm. The LMT is generally installed on a local computer, and is suitable for developers to carry out local station opening configuration, fast position and solve problems.
The LMT data parameter configuration mainly performs parameter configuration on each function of the base station, such as base station service IP address configuration, base station IP configuration, base station information configuration, local cell configuration, and the like. The data parameter configuration comprises online configuration and offline configuration, the online configuration displays the configuration of the base station side, and the LMT modifies the data and then directly sends the modified data to the site; after the LMT offline configuration is finished, the configuration files can be automatically stored under a local LMT root directory, the base station is opened in a mode that after the configuration files are modified on a local computer, the corresponding configuration files need to be copied to the base station in the offline parameter configuration, and at the moment, the configuration files on the base station side and the local computer are the same.
Referring to fig. 1, LMT configuration files may be mainly divided into two types, one type is a script file database. One is a configuration data file eNodeBCfg.dat, and specific data information of the configuration file is saved according to the format of a script file. The specific configuration information can be analyzed through the script file.
The LMT configuration file may be flexibly modified according to development requirements, such as adding a new configuration, deleting an original configuration, or adding or deleting parameters of an existing configuration, and it is necessary to modify database. After the configuration file is modified, the configuration file of the local LMT and the configuration file corresponding to the base station side need to be modified correspondingly based on the configuration file of the new version, that is, the configuration file is smoothly upgraded. And updating the configuration file version, fusing the local existing configuration data information and the configuration file of the new version, and storing the data in the LMT configuration file of the old version while retaining the format and the configuration data information of the configuration file of the new version. The above functions can be realized by a specific upgrading tool, but the smooth upgrading tool has the following disadvantages:
1) developers need to be skilled in correctly using the smooth upgrade tool, and if the operation is wrong, the final smooth upgrade may fail.
2) Local debugging may be performed on a plurality of computers, and different configurations are correspondingly stored, so that developers are required to perform manual smooth upgrade for many times, and the development workload is increased.
Disclosure of Invention
Aiming at the defects and shortcomings of manual smooth upgrading of the LMT configuration file, the invention aims to provide a method for realizing smooth upgrading of the local maintenance terminal configuration file, which can effectively reduce the operation complexity of the existing system. Developers do not need to carry out any operation, the base station version can automatically compare the configuration files of the old version and the new version after being upgraded and started, and if the configuration files are different, the configuration files are automatically and smoothly upgraded.
In order to achieve the above object, the present invention provides a method for smoothly upgrading an LMT configuration file, including the following steps,
s101, upgrading the base station version, including storing the latest version of configuration files database.ini and eNodeBCfg.dat in a base station memory, and storing the configuration files database.ini and eNodeBCfg.dat used for debugging the local LMT in a flash memory of the base station; wherein, database.ini is a script file, and eNodeBCfg.dat is a configuration data file;
s102, setting an LMT configuration file smooth upgrading identifier, wherein the LMT configuration file smooth upgrading identifier comprises the step of renaming data base.ini and eNodeBCfg.dat under a flash memory to src _ data base.ini and src _ eNodeBCfg.dat;
s103, restarting the base station;
s104, judging whether a smooth upgrade identifier of the configuration file is set or not, wherein the realization mode is that whether src _ database.ini and src _ eNodeB Cfg.dat exist in a flash memory or not is judged, if yes, the smooth upgrade identifier is set, and the step S105 is entered; if not, go to step S108;
s105, smoothly upgrading the script file, including storing the script file database.ini stored in the memory into a flash memory as the smoothly upgraded script file;
s106, configuring smooth upgrade of the data file, wherein src _ eNodeBCfg.dat is used as old version configuration of smooth upgrade of the configuration file, and database.ini and eNodeBCfg.dat stored in the memory are used as new version configuration; establishing a new data configuration file new _ eNodeBCfg.dat, and storing the smoothly upgraded data configuration file information; analyzing new and old versions of configuration data files src _ eNodeBCfg.dat and eNodeBCfg.dat, and sequentially storing the data configuration to be transplanted into the new data configuration file new _ eNodeBCfg.dat according to the analysis result;
s107, migrating src _ database.ini and src _ eNodeB Cfg.dat in the flash memory to a backup folder;
and S108, starting other processes after the base station is upgraded.
In S106, moreover, the smooth upgrade of the configuration data file is implemented as follows,
firstly, the data configuration files in the flash memory and the memory are analyzed, and the method is realized as follows,
analyzing a data configuration file src _ eNodeBCfg.dat in the flash according to a script file src _ database.ini format, and storing all table ids analyzed from the data configuration information into an aggregate table id group; the table id is an identifier of a configuration table;
analyzing a data configuration file eNodeBCfg.dat in the memory according to the format of the script file database.ini;
then, comparing the table id analyzed in the flash memory with the table id analyzed in the memory, including judging whether the same table id exists in the table id group when one table id is analyzed from the memory,
if the same table id does not exist in the table id group, writing configuration information related to the table id corresponding to the data configuration file stored in the memory into new _ eNodeBCfg.dat;
if the same table id exists in the table id group, judging whether the length of the memory occupied by the corresponding configuration tables of the table id in the memory and the flash is the same or not, if so, writing the configuration information related to the corresponding table id in the flash memory into new _ eNodeBCfg.dat; otherwise, writing configuration information related to table id corresponding to the data configuration file stored in the memory into new _ eNodeBCfg.dat;
and finally, after all table ids analyzed by the configuration data file in the memory are processed, modifying the file name of the newly generated data configuration file new _ eNodeBCfg.dat into eNodeBCfg.dat, and storing the data configuration file new _ eNodeBCfg.dat into a base station flash memory and the memory.
By adopting the method, the base station upgrading restart can automatically and smoothly upgrade the data configuration file and the script file, conveniently and quickly realize the upgrading of the LMT configuration file, reduce the operation complexity of the upgrading of the base station configuration file, simultaneously reduce the possibility of human errors caused by the operation errors of service personnel, save the cost, improve the efficiency, have important significance in large-scale wireless communication operation and realize great market value.
Drawings
Fig. 1 is a schematic diagram of a data configuration file in the prior art.
Fig. 2 is a schematic diagram illustrating a data configuration file upgrading principle in an embodiment of the present invention.
Fig. 3 is a schematic diagram of a smooth upgrade process of a configuration file according to an embodiment of the present invention.
Fig. 4 is a specific flowchart of data configuration file upgrade in the embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the accompanying drawings and detailed description, in order to facilitate the understanding and implementation of the invention by those skilled in the art.
As shown in fig. 2, the present invention provides a method for smoothly upgrading an LMT configuration file, which includes upgrading a script file and a data configuration file.
a. When the base station version is upgraded, setting an LMT configuration file version upgrading identification bit;
b. according to the identification bit, after the version of the base station is upgraded successfully, the configuration file is automatically and smoothly upgraded when the base station is started;
c. after the configuration file is smoothly upgraded, storing the newly generated configuration file into a base station flash and a base station memory;
in the step b, the method further comprises the following steps: if the identification position is set, smooth upgrading of the LMT configuration file is automatically processed; otherwise, the base station skips the smooth upgrading process and directly carries out the subsequent starting process;
step b further comprises: respectively upgrading the script file and the data configuration file;
the data configuration file is upgraded, and corresponding data configuration information needs to be analyzed according to flash and script information in an internal memory; and comparing the analyzed data configuration information results, and correspondingly performing data configuration information migration to generate new data configuration information.
As shown in fig. 3, the process of the embodiment of the present invention includes the following steps:
s101, upgrading the base station version: namely, the configuration file of the latest version is stored in a base station memory, and comprises new database.ini and eNodeBCfg.dat;
the smooth upgrade of the LMT configuration file should include the upgrade of two files, a script file database. In addition, specifically, in the present invention, before the base station version is upgraded, in order to retain the local existing configuration data information, the configuration files database.ini and enodebcfg.dat used in the local LMT debugging need to be saved in the base station flash directory, that is, in the flash memory.
S102, setting a smooth upgrading identifier of an LMT configuration file;
specifically, in the invention, when the base station version is upgraded, database.ini and eNodeBCfg.dat in the current flash memory of the base station are renamed to src _ database.ini and src _ eNodeBCfg.dat and are used as trigger marks for smoothly upgrading the configuration file.
Ini and src _ enodebcfg.dat are added to the white list. The white list refers to that after the base station is restarted, the files in the list still exist and cannot be cleared, modified or lost.
S103, restarting the base station;
furthermore, only the first restart after the base station version is upgraded can trigger the smooth upgrade of the configuration file; except for the subsequent restart of the base station of the first restart, the smooth upgrade of the LMT configuration file cannot be triggered.
S104, judging whether the smooth upgrading identifier of the configuration file is set;
specifically, in the present invention, the setting of the smooth upgrade flag is determined by determining whether two files, src _ database.ini and src _ enodebcfg.dat, exist in the flash memory, and if yes, the setting of the smooth upgrade flag is indicated, and it is necessary to first perform smooth upgrade of the configuration file and then start the configuration file, and then step S105 is performed; if not, the configuration file is not required to be smoothly upgraded, and the subsequent starting process is directly entered, that is, the step S108 is entered.
And if the configuration file is required to be smoothly upgraded, continuing the subsequent smooth upgrade process of the configuration file.
The configuration file includes two parts: and smoothly upgrading the script file and the data configuration file.
Firstly, executing smooth upgrade of the script file, namely step S105; then, smooth upgrade of the data configuration file is executed, namely step S106;
and S105, smoothly upgrading the script file.
Specifically, the script file database.ini stored in the memory is stored in the flash memory as the smoothly upgraded script file, that is, the smoothly upgraded script file is the same as the script file stored in the memory.
And S106, smoothly upgrading the configuration data file.
Specifically, src _ enodebcfg.dat is used as an old version configuration for smooth upgrade of the configuration file, and the latest configuration file obtained from the version library after the version upgrade, that is, database.ini and enodebcfg.dat stored in the memory are used as a new version configuration. And newly establishing a new data configuration file new _ eNodeBCfg.dat for storing the smoothly upgraded data configuration file information. And analyzing the new and old versions of the configuration data files src _ eNodeBCfg.dat and eNodeBCfg.dat, and sequentially configuring and storing the data to be transplanted into the new data configuration file new _ eNodeBCfg.dat according to the analysis result. The specific upgrade flow of the embodiment is shown in fig. 4.
The principle of smooth upgrade is as follows:
LMT profiles are stored in the form of tables, and different configurations have a unique Identifier (ID), i.e., table ID, to distinguish each configuration table.
For the table ids existing in the new version and the old version at the same time, if the number of the parameters corresponding to the table ids in the new version and the old version is the same, the data information corresponding to the table ids in the configuration file of the old version is migrated into the newly generated configuration file, and the data information reserved by local debugging can be migrated into the upgraded configuration data file in this way.
For the unique table id in the new version configuration file, migrating the data information corresponding to the table id in the new version configuration file to the newly generated configuration file;
and for the unique table id in the old version configuration file, no data migration is performed.
S107, migrating src _ database.ini and src _ enodebcfg.dat in the flash memory to a backup folder, and backing up the backup folder in a directory during specific implementation, where the directory is characterized in that the file in the restart directory of the base station is not lost.
And S108, starting other processes after the base station is upgraded, such as application of configuration files, clock synchronization, loading of DSP/FPGA and the like.
Fig. 4 is a specific process of smoothly upgrading a configuration data file in step S106 of a method for smoothly upgrading an LMT configuration file according to an embodiment of the present invention, where the specific process includes:
s201, analyzing data configuration files in a flash memory and a memory;
the method further comprises the following steps: and analyzing the data configuration file src _ eNodeBCfg.dat in the flash according to the script file src _ database.ini format, and storing all the table ids analyzed from the data configuration information into an aggregate table id group.
The method further comprises the following steps: and analyzing a data configuration file eNodeBCfg.dat in the memory according to the format of the script file database.ini.
S202, comparing the table id analyzed in the flash memory with the table id analyzed in the memory, and performing corresponding processing;
the method further comprises the following steps: and each time one table id is analyzed from the memory, judging whether the same table id exists in the table id group.
If the table id group does not have the same table id, the script file in the memory is used
The database.ini format writes the configuration information related to the table id in the data configuration file enodebcfg.dat in the memory into new _ enodebcfg.dat, i.e., enters S205.
If the same table id exists in the table id group, it indicates that there are corresponding tables in both the local and the configuration files in the library, and data information migration is required, that is, the process proceeds to S203.
S203, if data information migration is needed, it is further needed to determine whether the memory lengths occupied by the two tables are the same, and the table id analyzed in step S202 is respectively in the corresponding configuration tables in the memory and the flash.
If the memory length occupied by the two tables is the same, executing step S204; otherwise, executing step S205;
when the content length is the same, the content can be migrated; otherwise, the memory will have errors. The reason that whether the contents are the same or not does not need to be compared is to reduce the operation complexity, if the contents are the same, the contents are not changed after the migration, but the contents are different, namely the data are modified through local debugging, so that the contents modified according to the local debugging condition in the old version can be directly migrated to a new file.
S204, writing the configuration information related to the corresponding table id in the flash memory into new _ eNodeBCfg.dat, and finishing the corresponding table id processing.
S205, writing configuration information related to table id corresponding to the data configuration file stored in the memory into new _ enodebcfg.dat, and ending the corresponding table id processing.
S206, after all the analyzed table ids of the data configuration files in the memory are processed according to the process, the file name of the newly generated data configuration file new _ eNodeBCfg.dat is modified into eNodeBCfg.dat, and the newly generated data configuration file new _ eNodeBCfg.dat is stored in a base station flash memory and the memory.
In specific implementation, the automatic process operation can be realized by adopting a computer software technology.
It can be seen from the foregoing embodiments that the LMT configuration file smooth upgrade method of the present invention can automatically implement smooth upgrade of a configuration file, and different debug terminals can automatically save local configuration data into a latest configuration file by a uniform method, thereby implementing upgrade of the configuration file. The new configuration file generated after the upgrade not only retains the data information of the old version of the local debugging, but also integrates the modification of the new version of the configuration file. By adopting the method, the LMT configuration file is more simply upgraded and used, so that the possibility of causing human accidents due to configuration errors caused by operation errors of user personnel is reduced to a great extent, and the actual application requirements are better met.
Claims (2)
1. A smooth upgrading method for LMT configuration files is characterized in that: the method is used for realizing the data configuration of the local maintenance terminal, comprises the upgrading and restarting of the base station and automatically upgrades the script file and the data configuration file, and comprises the following steps,
s101, upgrading the base station version, including storing the latest version of configuration files database.ini and eNodeBCfg.dat in a base station memory, and storing the configuration files database.ini and eNodeBCfg.dat used for debugging the local LMT in a flash memory of the base station; wherein, database.ini is a script file, and eNodeBCfg.dat is a configuration data file;
s102, setting an LMT configuration file smooth upgrading identifier, wherein the LMT configuration file smooth upgrading identifier comprises the step of renaming data base.ini and eNodeBCfg.dat under a flash memory to src _ data base.ini and src _ eNodeBCfg.dat;
s103, restarting the base station;
s104, judging whether a smooth upgrade identifier of the configuration file is set or not, wherein the realization mode is that whether src _ database.ini and src _ eNodeB Cfg.dat exist in a flash memory or not is judged, if yes, the smooth upgrade identifier is set, and the step S105 is entered; if not, go to step S108;
s105, smoothly upgrading the script file, including storing the script file database.ini stored in the memory into a flash memory as the smoothly upgraded script file;
s106, configuring smooth upgrade of the data file, wherein src _ eNodeBCfg.dat is used as old version configuration of smooth upgrade of the configuration file, and database.ini and eNodeBCfg.dat stored in the memory are used as new version configuration; establishing a new data configuration file new _ eNodeBCfg.dat, and storing the smoothly upgraded data configuration file information; parsing new and old two versions of configuration data files src _ eNodeBCfg.dat and eNodeBCfg.dat, and sequentially storing the data configuration to be transplanted into the new data configuration file new _ eNodeBCfg.dat according to the parsing result, wherein the parsing is realized as follows,
the LMT configuration file is stored in a form of a table and is provided with a unique identifier table id;
for table ids existing in the new version and the old version at the same time, if the number of parameters corresponding to the table ids in the new version and the old version is the same, data information corresponding to the table ids in the configuration file of the old version is migrated to a newly generated configuration file, so that data information reserved by local debugging is migrated to an upgraded configuration data file;
for the unique table id in the new version configuration file, migrating the data information corresponding to the table id in the new version configuration file to the newly generated configuration file;
for the unique table id in the old version configuration file, no data migration is carried out;
s107, migrating src _ database.ini and src _ eNodeB Cfg.dat in the flash memory to a backup folder;
and S108, starting other processes after the base station is upgraded.
2. The LMT configuration file smooth upgrading method of claim 1, characterized in that: in S106, the smooth upgrade of the configuration data file is implemented as follows,
firstly, the data configuration files in the flash memory and the memory are analyzed, and the method is realized as follows,
analyzing a data configuration file src _ eNodeBCfg.dat in the flash according to a script file src _ database.ini format, and storing all table ids analyzed from the data configuration information into an aggregate table id group; the table id is an identifier of a configuration table;
analyzing a data configuration file eNodeBCfg.dat in the memory according to the format of the script file database.ini;
then, comparing the table id analyzed in the flash memory with the table id analyzed in the memory, including judging whether the same table id exists in the table id group when one table id is analyzed from the memory,
if the same table id does not exist in the table id group, writing configuration information related to the table id corresponding to the data configuration file stored in the memory into new _ eNodeBCfg.dat;
if the same table id exists in the table id group, judging whether the length of the memory occupied by the corresponding configuration tables of the table id in the memory and the flash is the same or not, if so, writing the configuration information related to the corresponding table id in the flash memory into new _ eNodeBCfg.dat; otherwise, writing configuration information related to table id corresponding to the data configuration file stored in the memory into new _ eNodeBCfg.dat;
and finally, after all table ids analyzed by the configuration data file in the memory are processed, modifying the file name of the newly generated data configuration file new _ eNodeBCfg.dat into eNodeBCfg.dat, and storing the data configuration file new _ eNodeBCfg.dat into a base station flash memory and the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611161293.7A CN106603289B (en) | 2016-12-15 | 2016-12-15 | LMT configuration file smooth upgrading method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611161293.7A CN106603289B (en) | 2016-12-15 | 2016-12-15 | LMT configuration file smooth upgrading method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106603289A CN106603289A (en) | 2017-04-26 |
| CN106603289B true CN106603289B (en) | 2020-12-25 |
Family
ID=58802735
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611161293.7A Active CN106603289B (en) | 2016-12-15 | 2016-12-15 | LMT configuration file smooth upgrading method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106603289B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109271210A (en) * | 2017-07-17 | 2019-01-25 | 中兴通讯股份有限公司 | A kind of check method and device of configuration file |
| CN108874436A (en) * | 2018-06-13 | 2018-11-23 | 珠海市君天电子科技有限公司 | A kind of method for upgrading software, device, terminal device and medium |
| CN113238782B (en) * | 2021-06-02 | 2023-04-07 | 西安热工研究院有限公司 | Method and system for upgrading domestic Ruitang real-time database file |
| CN114816571B (en) * | 2022-04-15 | 2023-06-16 | 西安广和通无线通信有限公司 | Method, device, equipment and storage medium for plug-in flash memory |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102264086A (en) * | 2007-12-17 | 2011-11-30 | 华为技术有限公司 | Method, devices and system for debugging base station |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7149508B2 (en) * | 2003-02-05 | 2006-12-12 | Samsung Electronics Co., Ltd. | System and method for delta-based over-the-air software upgrades for a wireless mobile station |
| CN100369519C (en) * | 2006-04-27 | 2008-02-13 | 北京北方烽火科技有限公司 | Operation maintenance system and method for base-station system |
| CN101136690B (en) * | 2006-11-23 | 2012-01-11 | 中兴通讯股份有限公司 | System and method for synchronizing operation maintenance center and base station configuration data |
| CN101286881B (en) * | 2008-05-16 | 2011-01-19 | 中兴通讯股份有限公司 | Device for implementing multi-version compatibility of software configuration data of base station and application thereof |
| CN103024782B (en) * | 2011-09-20 | 2017-10-10 | 中兴通讯股份有限公司 | A kind of method and system of base station software version management |
-
2016
- 2016-12-15 CN CN201611161293.7A patent/CN106603289B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102264086A (en) * | 2007-12-17 | 2011-11-30 | 华为技术有限公司 | Method, devices and system for debugging base station |
Non-Patent Citations (1)
| Title |
|---|
| 马银银." CDMA无线通讯基站***平滑升级的设计与实现".《中国优秀硕士学位论文全文数据库——信息科技辑》.2012,I136-877. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106603289A (en) | 2017-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106603289B (en) | LMT configuration file smooth upgrading method | |
| CN110209568B (en) | Coverage rate test method and device and storage equipment | |
| US9575830B2 (en) | Run-time error repairing method, device and system | |
| US20160378456A1 (en) | Method for offline updating virtual machine images | |
| US9372784B2 (en) | Test system configuration method and system | |
| CN107844343B (en) | Upgrading system and method for complex server application system | |
| CN103530150A (en) | Remote updating method for Linux operating system | |
| CN105045617B (en) | A kind of application recovery method and system of android system | |
| CN103914564A (en) | Method and system for updating and warehousing urban pipelines on basis of ArcGIS (geographic information system) | |
| CN103309712A (en) | Mobile phone software upgrade method and system | |
| CN110063042A (en) | A kind of response method and its terminal of database failure | |
| CN111737227A (en) | Data modification method and system | |
| CN104750601A (en) | Test method and test device | |
| CN104536398A (en) | Frequency converter monitoring method and system | |
| CN106484452B (en) | unified configuration management method and device for software platform | |
| CN104820676A (en) | Method and device for judging magnitude of version number | |
| CN110688305B (en) | Test environment synchronization method, device, medium and electronic equipment | |
| CN112052037A (en) | Application software development method, device, equipment and medium | |
| EP2575037A1 (en) | Generation apparatus, generation method and computer readable information recording medium | |
| WO2020143324A1 (en) | Service program releasing method and apparatus, and computer device and storage medium | |
| CN105117329A (en) | Application automatic online system and method | |
| CN108664255B (en) | Software upgrading method and device | |
| CN113434180A (en) | Data processing method and device for application, server and storage medium | |
| CN101267645B (en) | Automatic test method and system for service flow software development of W base station | |
| WO2016131294A1 (en) | Version upgrade processing method and device |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201026 Address after: 430205 No.1 tanhu 2nd Road, Canglong Island, Jiangxia Economic Development Zone, Wuhan City, Hubei Province Applicant after: Wuhan Hongxin Technology Development Co.,Ltd. Address before: 430073 Hubei province Wuhan Dongxin East Lake high tech Development Zone, Road No. 5 Applicant before: Wuhan Hongxin Telecommunication Technologies Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |