CN100556211C - A kind of upgrade method of mobile communication network management system - Google Patents
A kind of upgrade method of mobile communication network management systemDownload PDFInfo
- Publication number
- CN100556211C CN100556211CCNB2004100277256ACN200410027725ACN100556211CCN 100556211 CCN100556211 CCN 100556211CCN B2004100277256 ACNB2004100277256 ACN B2004100277256ACN 200410027725 ACN200410027725 ACN 200410027725ACN 100556211 CCN100556211 CCN 100556211C
- Authority
- CN
- China
- Prior art keywords
- version
- upgrade
- network management
- management system
- database
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Translated fromChinese
Description
Translated fromChinese技术领域：Technical field:
本发明涉及移动通信网中网管系统，尤其涉及移动通信网中网管系统的数据库升级。The invention relates to a network management system in a mobile communication network, in particular to a database upgrade of the network management system in a mobile communication network.
背景技术：Background technique:
在移动通信网中，网管负责对网络设备进行维护工作，提供人机接口，对电信网络设备进行配置、检查、控制、诊断、操作权限检查，跟踪设备的运行状况，收集分析网络设备的运行数据。要保证前台电信网络设备(以下通称为前台)的正常运行及管理，必须在后台网管服务器(以下通称为后台)提供数据库管理系统，然后安全可靠地提供给设备使用以及支持对网络的管理。由此可见网管服务器的应用程序和数据库是不可以或缺的，并且必须是安全、可靠、及时、高效的。In the mobile communication network, the network administrator is responsible for maintaining the network equipment, providing man-machine interface, configuring, checking, controlling, diagnosing, and checking the operation authority of the telecommunications network equipment, tracking the operation status of the equipment, and collecting and analyzing the operation data of the network equipment. . In order to ensure the normal operation and management of the telecommunications network equipment in the foreground (hereinafter referred to as the foreground), a database management system must be provided on the background network management server (hereinafter referred to as the background), and then provide it safely and reliably for the equipment to use and support the management of the network. It can be seen that the application program and database of the network management server are indispensable, and must be safe, reliable, timely and efficient.
但是，业务的需求在不断地变化，网络管理功能也必须为了满足业务的新需求而发生改变，这就带来一个升级问题。按照原有的机制，升级时将前后台断开，然后升级后台网管服务器和客户端，升级完成后再升级前台各个MP和单板，重新同步升级后的数据库给前台，最后再将前台重启后，业务开始正常运行。However, business requirements are constantly changing, and network management functions must also be changed to meet new business requirements, which brings about an upgrade problem. According to the original mechanism, disconnect the front and backend during the upgrade, then upgrade the background network management server and client, after the upgrade is complete, upgrade each MP and single board in the foreground, re-synchronize the upgraded database to the foreground, and finally restart the foreground , the business starts to run normally.
这种机制的缺点不言而喻，就是它在升级过程中万一出现后台服务器升级失败，将会造成无法对前台网络设备的管理和维护，给运营商网络带来了现网运行的危险以及造成一定程度的损失。The disadvantage of this mechanism is self-evident, that is, if the upgrade of the background server fails during the upgrade process, it will cause the inability to manage and maintain the front-end network equipment, which brings the danger of the current network operation to the operator's network. cause a certain amount of loss.
发明内容：Invention content:
本发明要解决的问题，是提供一种方法保证后台网管在升级前后均能正常运行，即保证低版本网管服务器升级过程能够安全、可靠地进行，并且能够自动完成，如果出现失败，将自动安全地回滚到老版本而不影响当前现网运行。The problem to be solved by the present invention is to provide a method to ensure that the background network management can operate normally before and after the upgrade, that is, to ensure that the upgrade process of the low-version network management server can be carried out safely and reliably, and can be completed automatically. Roll back to the old version without affecting the current network operation.
本发明的技术方案如下：Technical scheme of the present invention is as follows:
1.1维护一个版本列表或配置文件，包含所有网管系统历史版本和当前最新版本；1.1 Maintain a version list or configuration file, including all historical and current versions of the network management system;
1.2为每一个历史版本定义一个升级脚本文件，该升级脚本只负责将当前历史版本升级到比当前版本高一级的版本；1.2 Define an upgrade script file for each historical version, the upgrade script is only responsible for upgrading the current historical version to a version higher than the current version;
1.3初始化系统，将所有历史版本与相应的升级脚本关联；1.3 Initialize the system and associate all historical versions with corresponding upgrade scripts;
1.4将当前数据库版本与待升级的版本比较，如果两者版本号一致，则连接数据库并对数据库进行备份，然后1.4 Compare the current database version with the version to be upgraded, if the two version numbers are consistent, connect to the database and back up the database, and then
1.5递归读取升级脚本语句，并逐级升级，直到升级到最新版本；1.5 Recursively read the upgrade script statement and upgrade step by step until it reaches the latest version;
1.6将最新版本修改到数据库中。1.6 Modify the latest version into the database.
步骤1.2中的升级脚本文件，包括系统名称、每一个历史版本号和它的下一个版本号。The upgrade script file in step 1.2 includes the system name, each historical version number and its next version number.
步骤1.4中的将当前数据库版本与待升级的版本比较是通过一个比较函数来完成的。The comparison of the current database version with the version to be upgraded in step 1.4 is accomplished through a comparison function.
步骤1.5中的递归读取升彖脚本语句将逐级升级，是通过升级入口函数，该函数是一个递归调用，它查找与当前低版本匹配的升级脚本，如果找到则调用此脚本进行升级，直到升级到最新版本。所述的逐级升级，是指每一个版本只升级到它的下一个版本。在逐级升级过程中，任何一级升级失败，则用备份数据库恢复。The recursive reading upgrade script statement in step 1.5 will be upgraded step by step through the upgrade entry function, which is a recursive call, which searches for an upgrade script that matches the current lower version, and if found, calls this script to upgrade until Upgrade to the latest version. The step-by-step upgrade means that each version is only upgraded to its next version. In the process of level-by-level upgrading, if any level of upgrading fails, the backup database will be used to restore.
在本发明中，还定义一个标记，表明是哪种系统(HLR后台/计费服务器/OMC网管服务器)待升级。In the present invention, a mark is also defined to indicate which system (HLR background/billing server/OMC network management server) is to be upgraded.
采用本发明所述方法，与现有技术相比，可以实现安全和自动化升级。安全是指使升级的后台软件能够避免升级过程中出现失败而无法自动恢复原先版本环境的现象，取得了产品稳定性、安全性方面的的效果。自动化是指用户只需要点击一个升级按钮，就把备份数据，恢复数据，升级数据等步骤自动完成；跨版本升级时也不需要人工参与，通过链式升级方法自动完成。By adopting the method of the invention, compared with the prior art, safety and automatic upgrading can be realized. Security refers to the fact that the upgraded background software can avoid failures during the upgrade process and cannot automatically restore the original version environment, and has achieved the best results in product stability and security. Automation means that users only need to click an upgrade button, and the steps of backing up data, restoring data, and upgrading data are automatically completed; cross-version upgrades do not require manual participation, and are automatically completed through the chain upgrade method.
由于本发明采用了链式升级的方法，它是一个逐步升级的过程，即在每次升级版本更新时，避免了需要重写所有历史版本的升级工作，只需要新增次新版本向最新版本升级的脚本(其他更老版本的网管系统可以由以前的升级脚本负责将它升级到次新版本，然后再由刚才新增的升级脚本再将次新版本的网管系统升级到最新版本)，这样就节省了开发时间，降低了开发的复杂度，提高了开发效率。Because the present invention adopts the method of chain type upgrade, it is a process of gradual upgrade, promptly when each upgrade version is updated, has avoided needing to rewrite the upgrade work of all historical versions, only needs to add a new version to the latest version Upgraded script (other older versions of the network management system can be responsible for upgrading it to the next new version by the previous upgrade script, and then upgrade the next newer version of the network management system to the latest version by the newly added upgrade script), so It saves development time, reduces development complexity, and improves development efficiency.
附图说明：Description of drawings:
图1是本发明的的流程图；Fig. 1 is a flow chart of the present invention;
图2是业务变动后，增加一个新版本的流程图；Figure 2 is a flow chart of adding a new version after the business change;
图3是开局现场，技术人员实施安全自动化升级操作的具体流程。Figure 3 shows the specific process for technicians to implement security automation upgrade operations at the deployment site.
具体实施方式：Detailed ways:
下面主要讨论数据库的升级，对于应用程序的升级提供文件备份，如果需要回滚，用备份的文件覆盖新安装的文件即可(同样由程序自动完成)。The following mainly discusses the upgrade of the database. For the upgrade of the application, file backup is provided. If rollback is required, just use the backup file to overwrite the newly installed file (also automatically completed by the program).
为了增加扩展性和兼容性，具体实现本发明的技术时，可以使用java语言以及JDBC(Java DataBase Connection，Java数据库连接)，做到跨平台(windows/unix)，跨数据库(sqlserver/mysql/oracle/db2等)，跨系统(HLR/计费/OMC等)，提供GUI图形界面，简单操作，方便实用。In order to increase scalability and compatibility, when implementing the technology of the present invention, java language and JDBC (Java DataBase Connection, Java Database Connection) can be used to achieve cross-platform (windows/unix) and cross-database (sqlserver/mysql/oracle) /db2, etc.), cross-system (HLR/billing/OMC, etc.), providing a GUI graphical interface, easy to operate, convenient and practical.
在发明内容中已对本发明的技术方案进行了详细描述，下面结合附图以具体实施进行说明。The technical solution of the present invention has been described in detail in the summary of the invention, and will be described below in conjunction with the accompanying drawings for specific implementation.
图1是本发明主要的流程。Fig. 1 is the main process flow of the present invention.
在本发明中，升级脚本文件命名规则如下：In the present invention, the upgrade script file naming rules are as follows:
将特定版本号和对应的升级系统相关联。其中sys是特定的系统名，可以是omc、hlr、billomm……；oldVersion是一个历史版本号，如：CNV2.00.1、CNV2.00.2……；newVersion是当前升级版本号，如CNV2.00.2、CNV2.00.3……。如果某个系统的历史版本要升级，可以根据系统名+版本号找到相应的升级脚本文件，然后通过JDBC调用具体的升级sql语句将数据库升级到下一个版本。这个文件命名的主要作用就是能够根据系统号+版本号快速查找到对应这个版本的升级脚本文件。Associate a specific version number with a corresponding upgrade system. Among them, sys is a specific system name, which can be omc, hlr, billomm...; oldVersion is a historical version number, such as: CNV2.00.1, CNV2.00.2...; newVersion is the current upgrade version number, such as CNV2.00.2, CNV2 .00.3……. If the historical version of a certain system needs to be upgraded, you can find the corresponding upgrade script file according to the system name + version number, and then call the specific upgrade sql statement through JDBC to upgrade the database to the next version. The main function of this file naming is to be able to quickly find the upgrade script file corresponding to this version according to the system number + version number.
当前维护一个版本列表或配置文件，包含所有网管系统历史版本和当前最新版本。在升级时，首先取得数据库配置文件信息，根据当前网管系统版本获取可升级版本列表。版本列表配置文件verupdate.ini如下：A version list or configuration file is currently maintained, including the historical version and the latest version of all network management systems. When upgrading, first obtain the database configuration file information, and obtain the upgradeable version list according to the current network management system version. The version list configuration file verupdate.ini is as follows:
它是一个版本列，内容就是前面所说的oldVersion和newVersion。在此模拟了实际开局情况下，运营商需要维护的版本列表，每一个版本都有可能在现实开局环境中存在。其中第n个版本是当前最新版本，不需要进行升级；其余n-1个版本都有对应的升级脚本，分别负责将自己对应的版本升级到下一个版本，直到升级到最新版本n。维护这个版本列表的主要目的主要就是为了保证任何一个低版本网管系统都能够顺利升级到最新版本。It is a version column, and its content is the oldVersion and newVersion mentioned above. This simulates the list of versions that operators need to maintain in the actual deployment situation, and each version may exist in the actual deployment environment. Among them, the nth version is the latest version and does not need to be upgraded; the remaining n-1 versions have corresponding upgrade scripts, which are responsible for upgrading their corresponding versions to the next version until they are upgraded to the latest version n. The main purpose of maintaining this version list is to ensure that any low-version network management system can be successfully upgraded to the latest version.
数据库存在一张带安全自动化升级版本信息的表r_dbver。表结构如下：There is a table r_dbver in the database with version information of security automation upgrade. The table structure is as follows:
其中dbver代表数据库的版本号，最初版本假定可以定为CNV2.00.1，以后如果版本发生变化，版本号将逐步上升。有了这个表以后，后台程序就可以根据版本号对升级版本进行判断和确认升级等工作。Among them, dbver represents the version number of the database. The initial version is assumed to be CNV2.00.1. If the version changes in the future, the version number will gradually increase. With this table, the background program can judge and confirm the upgrade based on the version number.
在升级过程中，通过一个版本比较函数将当前数据库版本号与待升级的网管系统版本比较，如果不等，升级失败；如果等于，为防止升级失败首先进行数据库连接，进行数据备份；成功备份后则调用该项的升级脚本，升级到下一个版本，如果备份失败则升级失败；如果执行该升级脚本返回失败，利用备份的数据进入自动恢复数据库流程，升级失败；如果升级成功，则将升级后的版本号为参数，进行递归调用，继续执行升级工作，直到将历史版本升级为最新的版本，最后将最新版本修改到数据库中，完成安全自动化升级流程。该升级流程是一个链式的升级的过程，即从低版本向高版本一步一步升级，绝对不会出现跳级升级的现象，这主要是为了降低以后新增版本的开发复杂度。During the upgrade process, a version comparison function is used to compare the current database version number with the version of the network management system to be upgraded. If they are not equal, the upgrade fails; Then call the upgrade script of this item to upgrade to the next version. If the backup fails, the upgrade will fail; if the upgrade script returns failure, the backup data will be used to enter the automatic database recovery process, and the upgrade will fail; if the upgrade is successful, the upgraded The version number is used as a parameter, and the recursive call is made to continue the upgrade work until the historical version is upgraded to the latest version, and finally the latest version is modified to the database to complete the security automation upgrade process. The upgrade process is a chained upgrade process, that is, upgrade step by step from a lower version to a higher version, and there will never be a phenomenon of skipping upgrades. This is mainly to reduce the development complexity of new versions in the future.
图2介绍了增加一个新版本的流程。当业务需求发生变化并且牵涉到数据库改动时，安全自动化升级必须随之更新，该图说明了安全自动化升级的详细更新步骤。从图中可以看出，该过程十分简单，只需新增版本列表项(和一个升级脚本命名一致即可)，因为如果有其他更低的版本需要升级到最新版本，安全自动化升级流程会先调用以前的升级脚本负责将这个低版本的网管系统升级到次新版本，最终再调用新增的升级脚本，将次新版本的网管系统升级到最新版本。这种简单的方法体现了安全自动化升级的优点，即在很大程度上提高了开发的效率。Figure 2 introduces the process of adding a new version. When business requirements change and database changes are involved, the security automation upgrade must be updated accordingly. This figure illustrates the detailed update steps of the security automation upgrade. As can be seen from the figure, the process is very simple, just add a new version list item (named the same as an upgrade script), because if there are other lower versions that need to be upgraded to the latest version, the security automation upgrade process will first Calling the previous upgrade script is responsible for upgrading the lower version of the network management system to the next new version, and finally calls the newly added upgrade script to upgrade the next version of the network management system to the latest version. This simple method embodies the advantages of security automation upgrade, that is, it improves the efficiency of development to a large extent.
图3介绍了在开局现场，技术人员实施安全自动化升级前后台时的具体操作流程。首先确定当前后台版本以及要升级到哪个新版本，利用升级工具进行后台网管的安全自动化升级；如果失败，则本次升级失败，如果后台升级成功，则可以进入前台的升级工作，否则，无法使用正常的网管系统对应的升级前台版本的工具来对老版本前台进行升级。前台可能有多个，这里需要逐个升级，每个前台升级完成后即可运行；如果所有前台升级完成，则前后台所有的升级工作就结束了，如果有前台升级后版本运行不正常，说明前台版本文件制作有问题，进行正确的前台版本加载即可。开局人员必须严格按照本图的步骤进行升级，否则升级后的系统运行可能存在很多的隐患，如前后台版本不一致，后台同步数据到前台失败等等。Figure 3 introduces the specific operation process when technicians implement the security automation upgrade front-end and back-end at the deployment site. First determine the current background version and which new version to upgrade to, and use the upgrade tool to carry out the security automatic upgrade of the background network management; if it fails, the upgrade will fail. The tool for upgrading the front-end version corresponding to the normal network management system is used to upgrade the front-end version of the old version. There may be multiple foregrounds, which need to be upgraded one by one, and each foreground can be run after the upgrade is completed; if all the foregrounds are upgraded, all the upgrade work for the front and back ends will be over. There is a problem with the production of the version file, just load the correct foreground version. Deployment personnel must strictly follow the steps in this figure to upgrade, otherwise there may be many hidden dangers in the operation of the upgraded system, such as inconsistent versions of the front and back, failure to synchronize data from the background to the foreground, and so on.
Claims (7)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100277256ACN100556211C (en) | 2004-06-22 | 2004-06-22 | A kind of upgrade method of mobile communication network management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100277256ACN100556211C (en) | 2004-06-22 | 2004-06-22 | A kind of upgrade method of mobile communication network management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1713154A CN1713154A (en) | 2005-12-28 |
| CN100556211Ctrue CN100556211C (en) | 2009-10-28 |
Family
ID=35718782
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100277256AExpired - Fee RelatedCN100556211C (en) | 2004-06-22 | 2004-06-22 | A kind of upgrade method of mobile communication network management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100556211C (en) |
Families Citing this family (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100426291C (en)* | 2005-11-26 | 2008-10-15 | 华为技术有限公司 | System and method to realize database upgrading in background management system |
| CN100407206C (en)* | 2006-02-20 | 2008-07-30 | 华为技术有限公司 | Method and system for converting between different versions of configuration data |
| CN101039494B (en)* | 2007-03-19 | 2010-12-08 | 中兴通讯股份有限公司 | Method and apparatus for batch upgrading multi-element configuration data |
| CN101345648B (en)* | 2007-07-12 | 2011-01-19 | 中兴通讯股份有限公司 | Solution method of data inconsistency |
| CN101188516B (en)* | 2007-12-21 | 2013-04-17 | 康佳集团股份有限公司 | A highly reliable and self-adapted remote update method for network device software system |
| CN101968741A (en)* | 2009-07-27 | 2011-02-09 | 阿里巴巴集团控股有限公司 | Method, server and system for data update |
| CN101650663A (en)* | 2009-08-27 | 2010-02-17 | 中兴通讯股份有限公司 | Database system and upgrading method thereof |
| CN102023903B (en)* | 2009-09-10 | 2012-12-19 | 联想(北京)有限公司 | Version management method and device for data backup |
| CN102681863A (en)* | 2011-03-15 | 2012-09-19 | 新奥特（北京）视频技术有限公司 | Method for automatically upgrading data based on command mode |
| CN102843252B (en)* | 2011-06-23 | 2018-06-19 | 南京中兴软件有限责任公司 | A kind of method and apparatus by network management upgrading network element |
| CN102495733A (en)* | 2011-12-08 | 2012-06-13 | 方正国际软件有限公司 | Methods for detecting compatibility of application program and relevant database script and performing upgrading maintenance on application program and relevant database script |
| CN102799522A (en)* | 2012-06-28 | 2012-11-28 | 浪潮(北京)电子信息产业有限公司 | Managing method and system for software version tracing test |
| CN104066077A (en)* | 2014-06-24 | 2014-09-24 | 青岛海信移动通信技术股份有限公司 | OTA downloading and upgrading method and device thereof |
| CN106815034A (en)* | 2015-11-27 | 2017-06-09 | 中兴通讯股份有限公司 | A kind of data updating method and device |
| CN106445618A (en)* | 2016-10-17 | 2017-02-22 | 成都知道创宇信息技术有限公司 | Automatic database updating method |
| CN106843984A (en)* | 2017-02-13 | 2017-06-13 | 东软集团股份有限公司 | The update method and device of application database |
| CN110034943B (en)* | 2018-01-12 | 2020-12-04 | 大唐移动通信设备有限公司 | Method and device for deleting Management Information Base (MIB) |
| CN111562931A (en)* | 2020-04-30 | 2020-08-21 | 斑马网络技术有限公司 | Method and system for upgrading vehicle firmware |
| CN112068881A (en)* | 2020-09-21 | 2020-12-11 | 北京天地和兴科技有限公司 | Database upgrading method based on data chain |
| CN112181946A (en)* | 2020-09-28 | 2021-01-05 | 云知声智能科技股份有限公司 | Method and device for automatically maintaining dynamic database script |
- 2004
- 2004-06-22CNCNB2004100277256Apatent/CN100556211C/ennot_activeExpired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN1713154A (en) | 2005-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100556211C (en) | A kind of upgrade method of mobile communication network management system | |
| US6970876B2 (en) | Method and arrangement for the management of database schemas | |
| CA2457440C (en) | System and method for the automatic installation and configuration of an operating system | |
| US9779126B2 (en) | Hybrid database upgrade migration | |
| US7085822B1 (en) | Managing pervasive devices | |
| CN111737227B (en) | Data modification method and system | |
| CA2281367C (en) | Method and apparatus for simplified administration of large numbers of similar information handling servers | |
| CN112434008A (en) | Distributed database upgrading method, device and medium | |
| CN107608681A (en) | Installation method of operating system, device and server | |
| CN106201773A (en) | The upgrading of instance system, cloud system and instance system or restoration methods | |
| CN108052336A (en) | Distributed software upgrading system and implementation method thereof | |
| CN110519088A (en) | Configure service disaster and system | |
| CN110209534A (en) | The system and method for automated back-up mysql database | |
| CN115658166A (en) | System, method and medium for centralized management and easy application configuration | |
| CN104516796A (en) | Command set based network element backup and recovery method and device | |
| CN116149713B (en) | Program upgrading method and device for all-level equipment under tree-type heterogeneous network | |
| CN119225925A (en) | Service management method, device, electronic device and storage medium | |
| US9207928B2 (en) | Computer-readable medium, apparatus, and methods of automatic capability installation | |
| CN106815004A (en) | A kind of method of compatibility difference Cocos2d-x versions | |
| CN111240700A (en) | A system and method for deploying server OS across network segments | |
| CN116028084A (en) | Cross-version hot upgrading method, system and terminal based on OpenStack cloud platform | |
| CN101383770B (en) | Communication apparatus upgrading method, communication system and access network appliance thereof | |
| US20030126159A1 (en) | Method and system for rollback of software system upgrade | |
| CN111597165B (en) | Database management method, terminal and storage medium | |
| CN116185462B (en) | A method, system, computer and readable storage medium for upgrading front-end applications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right | Owner name:HAIMEN TECHNOLOGY DEVELOPMENT CORP. Free format text:FORMER OWNER: ZTE CORPORATION Effective date:20130408 | |
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data | Free format text:CORRECT: ADDRESS; FROM: 518057 SHENZHEN, GUANGDONG PROVINCE TO: 226144 NANTONG, JIANGSU PROVINCE | |
| TR01 | Transfer of patent right | Effective date of registration:20130408 Address after:226144, 600 Beijing Road, Haimen, Jiangsu province (administrative center, room 0212) Patentee after:Haimen science and Technology Development General Corporation Address before:518057 Department of law, Zhongxing building, South Science and technology road, Nanshan District hi tech Industrial Park, Shenzhen Patentee before:ZTE Corporation | |
| CF01 | Termination of patent right due to non-payment of annual fee | Granted publication date:20091028 Termination date:20160622 | |
| CF01 | Termination of patent right due to non-payment of annual fee |