CN102013994A - Method, terminal and system for implementing network element version compatibility in network management - Google Patents
Method, terminal and system for implementing network element version compatibility in network management Download PDFInfo
- Publication number
- CN102013994A CN102013994A CN2010105284834A CN201010528483A CN102013994A CN 102013994 A CN102013994 A CN 102013994A CN 2010105284834 A CN2010105284834 A CN 2010105284834A CN 201010528483 A CN201010528483 A CN 201010528483A CN 102013994 A CN102013994 A CN 102013994A
- Authority
- CN
- China
- Prior art keywords
- network element
- version number
- class
- file
- version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to a method, a terminal and a system for implementing network element version compatibility in network management. The method comprises that: when a user selects a triggering network element, a client searches a version number of the network element from an internal memory; the version number is acquired from a server after the network element establishes link with an operation and maintenance center (OMC)and is saved in an internal memory network element information list; a configuration file corresponding to the version number is loaded according to the version number; and a corresponding network element interface and a service logic are started according to the configuration file, and the network element interface is displayed so as to implement version compatibility. By dynamically loading the corresponding configuration file according to the current version number of the network element and further loading different client interfaces and server service constraint rules, namely the service logics, different versions of network elements are managed compatibly and conveniently, so that the different versions of network elements can be displayed through different service logics and interfaces on network management. Therefore, the problem of compatible management of the different versions of network elements is radically solved.
Description
Technical field
The present invention relates to the telecommunication technology field, relate in particular to the method, terminal and the system that realize the network element version compatibility in a kind of webmaster.
Background technology
At present; continuous development along with the technologies of telecommunications network management; the network element scale of telecommunicatioin network management management constantly enlarges; same class NE quantity also can be a lot; various network element versions also can constantly be upgraded; it is redaction (this paper is defined as the N version) that webmaster can face a part of network element updating usually; and another part network element continues to use the situation of early version (this paper is defined as N-1, N-2 version); the compatible management expectancy of webmaster arises at the historic moment; be that webmaster must be managed redaction network element and early version network element simultaneously, different similar each network element of version all can normally be moved.
The solution of the compatible management of existing webmaster is to formulate some development specifications, only allows to increase newly such as specified data storehouse field, does not allow to revise and deletion; For the service logic class that restriction relation is arranged, can not change etc., make original code increase many redundant codes thus and logic is caused confusion, make mistakes easily when webmaster manages each version network element and be difficult to and safeguard.
Summary of the invention
Main purpose of the present invention is to provide method, terminal and the system that realizes the network element version compatibility in a kind of webmaster, is intended to improve the compatibility of different editions network element in the webmaster.
In order to achieve the above object, the present invention proposes to realize in a kind of webmaster the method for network element version compatibility, comprising:
When the user selected to trigger network element, client was searched the version number of described network element from internal memory; Described version number is obtained and is kept at the internal memory net element information table from service end behind described network element and OMC link setup by client;
Load the configuration file corresponding according to described version number with this version number;
Start corresponding network element interface class and service logic class according to described configuration file, show described network element interface realization edition compatibility.
Preferably, described step according to version number's loading configuration file corresponding with this version number comprises:
Client is searched the code file relevant with the service logic class with network element interface class of described version number correspondence;
Load described code file corresponding net element interface class and service logic class.
Preferably, described step according to version number's loading configuration file corresponding with this version number comprises:
Search the code file corresponding with described version number;
Search the common codes file;
Load described code file and common codes file corresponding net element interface class and service logic class.
Preferably, described step according to version number's loading configuration file corresponding with this version number comprises:
Search corresponding file bag with described version number;
Load described file bag corresponding net element interface class and service logic class.
Preferably, describedly start corresponding network element interface class and service logic class, show that described network element interface realizes that the step of edition compatibility comprises according to configuration file:
Client sends the trigger command of switching version to service end, and described trigger command carries described version number, loads corresponding service end service logic class by service end according to described version number and carries out the verification of data legitimacy;
After the service end verification was passed through, client received the check results of service end feedback, and by the user select to trigger will be corresponding with described version number the legitimacy data sync to described network element;
Start and show described network element interface with described version number corresponding net element interface class and service logic class.
The present invention also proposes to realize in a kind of webmaster the terminal of network element version compatibility, comprising:
Module is searched by version number, is used for when the user selects to trigger network element, searches the version number of described network element from internal memory; Described version number is obtained and is kept at the internal memory net element information table from service end behind described network element and OMC link setup by this terminal;
The configuration file load-on module is used for loading the configuration file corresponding with this version number according to described version number;
The edition compatibility module is used for starting corresponding network element interface class and service logic class according to described configuration file, shows described network element interface realization edition compatibility.
Preferably, described configuration file load-on module comprises:
The file acquiring unit is used to search the code file relevant with the service logic class with network element interface class of described version number correspondence;
Loading unit is used to load described code file corresponding net element interface class and service logic class.
Preferably, described file acquiring unit also is used to search the code file corresponding with described version number and searches the common codes file;
Described loading unit also is used to load described code file and common codes file corresponding net element interface class and service logic class.
Preferably, described file acquiring unit also is used to search the corresponding file bag with described version number;
Described loading unit also is used to load described file bag corresponding net element interface class and service logic class.
Preferably, described edition compatibility module comprises:
The trigger command transmitting element, the trigger command that is used for client transmission switching version is to service end, and described trigger command carries described version number, loads corresponding service end service logic class by service end according to described version number and carries out the verification of data legitimacy;
Data synchronisation unit is used for after the service end verification is passed through, and client receives the check results of service end feedback, and by the user select to trigger will be corresponding with described version number the legitimacy data sync to described network element;
Start display unit, be used for startup and show described network element interface with described version number corresponding net element interface class and service logic class.
The present invention also proposes to realize in a kind of webmaster the system of network element version compatibility, comprises client and service end, wherein:
Described client is used for when the user selects to trigger network element, searches the version number of described network element from internal memory; Described version number is obtained and is kept at the internal memory net element information table from service end behind described network element and OMC link setup by client; Load the configuration file corresponding according to described version number with this version number; And send according to described configuration file the trigger command that switches version to service end to start corresponding network element interface class and service logic class, show that described network element interface realizes edition compatibility;
Described service end is used for providing the version number of described network element to client behind described network element and OMC link setup; Receive the trigger command of the switching version of client transmission, load corresponding service end service logic class according to described trigger command and carry out the verification of data legitimacy, cooperate the customer side to start corresponding network element interface class and service logic class, show described network element interface realization edition compatibility.
Preferably, described customer side is each described terminal among the claim 6-10.
Realize method, terminal and the system of network element version compatibility in a kind of webmaster that the present invention proposes, by configuration file according to network element current version dynamic load correspondence, further loading the professional constraint rule of different client end interfaces and server end is service logic, realized compatible management different editions network element easily, make the different editions network element that different service logics and interface display can be arranged on webmaster, thereby fundamentally solve the compatible problem of management of different editions network element.
Description of drawings
Fig. 1 is method one an embodiment schematic flow sheet of realizing the network element version compatibility in the webmaster of the present invention;
Fig. 2 realizes in the webmaster of the present invention loading the configuration file a kind of execution mode schematic flow sheet corresponding with this version number according to version number among method one embodiment of network element version compatibility;
Fig. 3 realizes configuration file another kind execution mode schematic flow sheet corresponding with this version number according to version number's loading among method one embodiment of network element version compatibility in the webmaster of the present invention;
Fig. 4 realizes in the webmaster of the present invention loading configuration file another execution mode schematic flow sheet corresponding with this version number according to version number among method one embodiment of network element version compatibility;
Fig. 5 realizes in the webmaster of the present invention starting corresponding network element interface class and service logic class according to configuration file among method one embodiment of network element version compatibility, shows that the network element interface realizes the schematic flow sheet of edition compatibility;
Fig. 6 is terminal one an example structure schematic diagram of realizing the network element version compatibility in the webmaster of the present invention;
Fig. 7 realizes configuration file load-on module structural representation among terminal one embodiment of network element version compatibility in the webmaster of the present invention;
Fig. 8 realizes edition compatibility modular structure schematic diagram among terminal one embodiment of network element version compatibility in the webmaster of the present invention;
Fig. 9 is system's one example structure schematic diagram of realizing the network element version compatibility in the webmaster of the present invention.
In order to make technical scheme of the present invention clearer, clear, be described in further detail below in conjunction with accompanying drawing.
Embodiment
Solution for embodiment of the invention mainly is the configuration file according to network element current version dynamic load correspondence, further loading the professional constraint rule of different client end interfaces and server end is service logic, make the different editions network element that different service logics and interface display can be arranged on webmaster, realize the compatibility management of different editions network element.
As shown in Figure 1, one embodiment of the invention proposes to realize in a kind of webmaster the method for network element version compatibility, comprising:
Step S101, when the user selected to trigger network element, client was searched the version number of network element from internal memory;
The present embodiment method relates to OMC (the Operations ﹠amp in the technologies of telecommunications network management field; Maintenance Center, operation maintenance center), its application scenarios comprises that the OMC client with user interface is the present embodiment client, the OMC service end that is connected with the OMC client is present embodiment service end and each network element of being connected with the OMC service end, in order to realize that OMC supports to manage the network element of of the same type different editions simultaneously such as N, the network element of version such as N-1 or N-2, present embodiment is a service logic according to network element current version dynamic load different client end interface and the professional constraint rule of server end, realizes the compatibility management to the different editions network element.
Behind network element and OMC link setup, report this network element version information to give the OMC service end, the OMC service end sends to the OMC client with network element version information again, and the OMC client is preserved the version number information of obtaining in the internal memory net element information table; When the user when the OMC client triggers the operation relevant with network element, such as opening configuration management, click this network element on the topological tree, the version number that the OMC client is searched this network element according to internal memory net element information table realizes the compatible management of network element so that follow-up version number according to this network element loads corresponding configuration file.
Step S102 loads the configuration file corresponding with this version number according to version number;
According to the corresponding configuration file of this network element version dynamic load that finds, load with the service logic of determining the OMC client, present the configuration interface of this version network element.
In order to be implemented in the configuration file that the OMC client loads the respective version network element, at first, the OMC backstage need dispose the code file of the service logic (comprising the interface) of corresponding different editions network element for OMC client and OMC service end.
In the present embodiment, adopt three kinds of execution modes to carry out the configuration of code file and then have the mode of three kinds of corresponding loading configuration file, specific as follows:
First kind of execution mode, at the complete situation inequality of the code file of different editions network element, under this kind situation, the code file that need have version number for the configuration of different editions network element interface and service logic, filename can be class name or bag name, different version network elements has different filenames, when between different network elements, switching, when needing to load the code file of respective network elements, file associated name in the code file is unified to replace, carry out customized development then on this basis, the interface of different editions and service logic are distinguished, realize that OMC supports the interface of a plurality of version network elements and service logic to represent.
Second kind of execution mode, the few situation of file that interface that changes at the different editions network element and service logic relate to is under this kind situation, when carrying out the code file configuration, only need get final product the version number of respective network elements on the file band that changes, other shared file remains unchanged.When carrying out the code file loading in the OMC client, at first check the version number of network element, go to load relevant code file according to version number, if do not find relevant code file, then load shared file.
The third execution mode, at the code file bibliographic structure of the different editions network element situation all identical with filename, under this kind situation, the code file name of different editions network element need not be revised, after corresponding code file is developed, be packaged into the file bag and wrap such as breaking into Jar, and with going up version number to distinguish the interface and the service logic of different editions network element, use java class loader technology then, realize that the service logic of different editions is loaded by different Classloaders.Use different java class loaders in OMC client engine or OMC service end engine, the service logic class that loads in the corresponding version Jar bag can start different service logics.
Need to prove that three kinds of by way of example of the configuration of above-mentioned client code file and loading are applicable to client and service end simultaneously, just do not have user's service interface in service end.
Step S103 starts corresponding network element interface class and service logic class according to configuration file, shows network element interface realization edition compatibility.
After the OMC client loads the configuration file corresponding with this version number according to version number, determine interface and the service logic that needs load in the OMC client according to the requirement of this configuration file, afterwards, the OMC client sends and requires to switch the trigger command of version to service end, and in trigger command, increase version information (or category information), after the OMC service end is received trigger command, load different service end service logic classes by OMC service end engine according to version information, the method of correspondent service logic class can adopt three kinds of execution modes of the configuration and the loading of client code file among the step S102 in OMC service end configuration code file and the loading code file, by the OMC service end this version number's corresponding user data legitimacy is carried out verification afterwards, and check results will be fed back to the OMC client.
After the verification of user's data legitimacy was passed through, the OMC service end will be saved in the data of this version in the table of database correspondence.When the user selects to be synchronized to network element, correct edition data will be synchronized to corresponding network element.
Realized compatible management different editions network element thus easily, made the different editions network element can on webmaster, have different service logics and interface to represent.
As shown in Figure 2, as a kind of execution mode, step S102 comprises:
Step S1021, client is searched version number's correspondence and code file network element interface class and service logic associated class;
Step S1022, loading code file corresponding net element interface class and service logic class.
As shown in Figure 3, as another kind of execution mode, step S102 can also comprise:
Step S1023 searches the code file corresponding with version number;
Step S1024 searches the common codes file;
Step S1025, loading code file and common codes file corresponding net element interface class and service logic class.
As shown in Figure 4, as another execution mode, step S102 can also comprise:
Step S1026 searches the corresponding file bag with version number;
Step S1027, load document bag corresponding net element interface class and service logic class.
As shown in Figure 5, step S103 comprises:
Step S1031, client sends the trigger command of switching version to service end, and trigger command carries version number, loads corresponding service end service logic class by service end according to version number and carries out the verification of data legitimacy;
Step S1032, after the service end verification was passed through, client received the check results of service end feedback, and by the user select to trigger will be corresponding with version number the legitimacy data sync to network element;
Step S1033 starts and version number's corresponding net element interface class and service logic class demonstration network element interface.
As shown in Figure 6, one embodiment of the invention proposes to realize in a kind of webmaster the terminal of network element version compatibility, and comprising: module 601, configuration file load-on module 602 and edition compatibility module 603 are searched by version number, wherein:
Module 601 is searched by version number, is used for when the user selects to trigger network element, searches the version number of network element from internal memory; Version number is obtained and is kept at the internal memory net element information table from service end behind network element and OMC link setup by this terminal;
Present embodiment relates to OMC (the Operations ﹠amp in the technologies of telecommunications network management field; Maintenance Center, operation maintenance center), its application scenarios comprises that the OMC client with user interface is terminal in the present embodiment, the OMC service end that is connected with the OMC client and each network element of being connected with the OMC service end, in order to realize that OMC supports to manage the network element of the network element of of the same type different editions such as versions such as N, N-1 or N-2 simultaneously, present embodiment is a service logic according to network element current version dynamic load different client end interface and the professional constraint rule of server end, realizes the compatibility management to the different editions network element.
Behind network element and OMC link setup, report this network element version information to give the OMC service end, the OMC service end sends to the OMC client with network element version information again, and the OMC client is preserved the version number information of obtaining in the internal memory net element information table; When the user when the OMC client triggers the operation relevant with network element, such as opening configuration management, click this network element on the topological tree, the version number that the OMC client is searched this network element according to internal memory net element information table realizes the compatible management of network element so that follow-up version number according to this network element loads corresponding configuration file.
Configuration file load-on module 602 is used for loading the configuration file corresponding with this version number according to version number; According to the corresponding configuration file of this network element version dynamic load that finds, load with the service logic of determining the OMC client, present the configuration interface of this version network element.
In order to be implemented in the configuration file that the OMC client loads the respective version network element, at first, the OMC backstage need dispose the code file of the service logic (comprising the interface) of corresponding different editions network element for OMC client and OMC service end.
In the present embodiment, adopt three kinds of execution modes to carry out the configuration of code file and then have the mode of three kinds of corresponding loading configuration file, specific as follows:
First kind of execution mode, at the complete situation inequality of the code file of different editions network element, under this kind situation, the code file that need have version number for the configuration of different editions network element interface and service logic, filename can be class name or bag name, different version network elements has different filenames, when between different network elements, switching, when needing to load the code file of respective network elements, file associated name in the code file is unified to replace, carry out customized development then on this basis, the interface of different editions and service logic are distinguished, realize that OMC supports the interface of a plurality of version network elements and service logic to represent.
Second kind of execution mode, the few situation of file that interface that changes at the different editions network element and service logic relate to is under this kind situation, when carrying out the code file configuration, only need get final product the version number of respective network elements on the file band that changes, other shared file remains unchanged.When carrying out the code file loading in the OMC client, at first check the version number of network element, go to load relevant code file according to version number, if do not find relevant code file, then load shared file.
The third execution mode, at the code file bibliographic structure of the different editions network element situation all identical with filename, under this kind situation, the code file name of different editions network element need not be revised, after corresponding code file is developed, be packaged into the file bag and wrap such as breaking into Jar, and with going up version number to distinguish the interface and the service logic of different editions network element, use java class loader technology then, realize that the service logic of different editions is loaded by different Classloaders.Use different java class loaders in OMC client engine or OMC service end engine, the service logic class that loads in the corresponding version Jar bag can start different service logics.
Need to prove that three kinds of by way of example of the configuration of above-mentioned client code file and loading are applicable to client and service end simultaneously, just do not have user's service interface in service end.Edition compatibility module 603 is used for starting corresponding network element interface class and service logic class according to configuration file, shows network element interface realization edition compatibility.
After the OMC client loads the configuration file corresponding with this version number according to version number, determine interface and the service logic that needs load in the OMC client according to the requirement of this configuration file, afterwards, the OMC client sends and requires to switch the trigger command of version to service end, and in trigger command, increase version information (or category information), after the OMC service end is received trigger command, load different service end service logic classes by OMC service end engine according to version information, the method of correspondent service logic class can adopt three kinds of execution modes of the configuration and the loading of client code file in the said process in OMC service end configuration code file and the loading code file, afterwards, by the OMC service end this version number's corresponding user data legitimacy is carried out verification, and check results will be fed back to the OMC client.
After the verification of user's data legitimacy was passed through, the OMC service end will be saved in the data of this version in the table of database correspondence.When the user selects to be synchronized to network element, correct edition data will be synchronized to corresponding network element.
Realized compatible management different editions network element thus easily, made the different editions network element can on webmaster, have different service logics and interface to represent.
As shown in Figure 7, configuration file load-on module 602 comprises: file acquiring unit 6021 and loading unit 6022, wherein:
Further, file acquiring unit 6021 also is used to search the code file corresponding with version number and searches the common codes file;
Described loading unit 6022 also is used for loading code file and common codes file corresponding net element interface class and service logic class.
Further, file acquiring unit 6021 also is used to search the corresponding file bag with version number;
Described loading unit 6022 also is used for load document bag corresponding net element interface class and service logic class.
As shown in Figure 8, edition compatibility module 603 comprises: trigger command transmitting element 6031, data synchronisation unit 6032 and startup display unit 6033, wherein:
Trigger command transmitting element 6031, the trigger command that is used to send the switching version is to service end, and trigger command carries version number, loads corresponding service end service logic class by service end according to version number and carries out the verification of data legitimacy;
Data synchronisation unit 6032 is used for after the service end verification is passed through, and client receives the check results of service end feedback, and by the user select to trigger will be corresponding with version number the legitimacy data sync to network element;
Start display unit 6033, be used for starting and version number's corresponding net element interface class and service logic class demonstration network element interface.
As shown in Figure 9, one embodiment of the invention proposes to realize in a kind of webmaster the system of network element version compatibility, comprises client 901 and service end 902, wherein:
In the present embodiment, customer side 901 can be the terminal described in the foregoing description.
Realize method, terminal and the system of network element version compatibility in the embodiment of the invention webmaster, by configuration file according to network element current version dynamic load correspondence, further loading the professional constraint rule of different client end interfaces and server end is service logic, realized compatible management different editions network element easily, make the different editions network element that different service logics and interface display can be arranged on webmaster, thereby fundamentally solve the compatible problem of management of different editions network element.
The above only is the preferred embodiments of the present invention; be not so limit claim of the present invention; every equivalent structure or flow process conversion that utilizes specification of the present invention and accompanying drawing content to be done; or directly or indirectly be used in other relevant technical field, all in like manner be included in the scope of patent protection of the present invention.
Claims (12)
1. realize the method for network element version compatibility in the webmaster, it is characterized in that, comprising:
When the user selected to trigger network element, client was searched the version number of described network element from internal memory; Described version number is obtained and is kept at the internal memory net element information table from service end behind described network element and OMC link setup by client;
Load the configuration file corresponding according to described version number with this version number;
Start corresponding network element interface class and service logic class according to described configuration file, show described network element interface realization edition compatibility.
2. method according to claim 1 is characterized in that, described step according to version number's loading configuration file corresponding with this version number comprises:
Client is searched the code file relevant with the service logic class with network element interface class of described version number correspondence;
Load described code file corresponding net element interface class and service logic class.
3. method according to claim 1 is characterized in that, described step according to version number's loading configuration file corresponding with this version number comprises:
Search the code file corresponding with described version number;
Search the common codes file;
Load described code file and common codes file corresponding net element interface class and service logic class.
4. method according to claim 1 is characterized in that, described step according to version number's loading configuration file corresponding with this version number comprises:
Search corresponding file bag with described version number;
Load described file bag corresponding net element interface class and service logic class.
5. according to each described method among the claim 1-4, it is characterized in that, describedly start corresponding network element interface class and service logic class, show that described network element interface realizes that the step of edition compatibility comprises according to configuration file:
Client sends the trigger command of switching version to service end, and described trigger command carries described version number, loads corresponding service end service logic class by service end according to described version number and carries out the verification of data legitimacy;
After the service end verification was passed through, client received the check results of service end feedback, and by the user select to trigger will be corresponding with described version number the legitimacy data sync to described network element;
Start and show described network element interface with described version number corresponding net element interface class and service logic class.
6. realize the terminal of network element version compatibility in the webmaster, it is characterized in that, comprising:
Module is searched by version number, is used for when the user selects to trigger network element, searches the version number of described network element from internal memory; Described version number is obtained and is kept at the internal memory net element information table from service end behind described network element and OMC link setup by this terminal;
The configuration file load-on module is used for loading the configuration file corresponding with this version number according to described version number;
The edition compatibility module is used for starting corresponding network element interface class and service logic class according to described configuration file, shows described network element interface realization edition compatibility.
7. terminal according to claim 6 is characterized in that, described configuration file load-on module comprises:
The file acquiring unit is used to search the code file relevant with the service logic class with network element interface class of described version number correspondence;
Loading unit is used to load described code file corresponding net element interface class and service logic class.
8. terminal according to claim 7 is characterized in that,
Described file acquiring unit also is used to search the code file corresponding with described version number and searches the common codes file;
Described loading unit also is used to load described code file and common codes file corresponding net element interface class and service logic class.
9. terminal according to claim 7 is characterized in that,
Described file acquiring unit also is used to search the corresponding file bag with described version number;
Described loading unit also is used to load described file bag corresponding net element interface class and service logic class.
10. according to each described terminal among the claim 6-9, it is characterized in that described edition compatibility module comprises:
The trigger command transmitting element, the trigger command that is used to send the switching version is to service end, and described trigger command carries described version number, loads corresponding service end service logic class by service end according to described version number and carries out the verification of data legitimacy;
Data synchronisation unit is used for after the service end verification is passed through, and client receives the check results of service end feedback, and by the user select to trigger will be corresponding with described version number the legitimacy data sync to described network element;
Start display unit, be used for startup and show described network element interface with described version number corresponding net element interface class and service logic class.
11. realize the system of network element version compatibility in the webmaster, it is characterized in that, comprise client and service end, wherein:
Described client is used for when the user selects to trigger network element, searches the version number of described network element from internal memory; Described version number is obtained and is kept at the internal memory net element information table from service end behind described network element and OMC link setup by client; Load the configuration file corresponding according to described version number with this version number; And send according to described configuration file the trigger command that switches version to service end to start corresponding network element interface class and service logic class, show that described network element interface realizes edition compatibility;
Described service end is used for providing the version number of described network element to client behind described network element and OMC link setup; Receive the trigger command of the switching version of client transmission, load corresponding service end service logic class according to described trigger command and carry out the verification of data legitimacy, cooperate the customer side to start corresponding network element interface class and service logic class, show described network element interface realization edition compatibility.
12. system according to claim 11 is characterized in that, described customer side is each described terminal among the claim 6-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010528483.4A CN102013994B (en) | 2010-11-02 | 2010-11-02 | Method, terminal and system for implementing network element version compatibility in network management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010528483.4A CN102013994B (en) | 2010-11-02 | 2010-11-02 | Method, terminal and system for implementing network element version compatibility in network management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102013994A true CN102013994A (en) | 2011-04-13 |
| CN102013994B CN102013994B (en) | 2014-04-09 |
Family
ID=43844022
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010528483.4A Active CN102013994B (en) | 2010-11-02 | 2010-11-02 | Method, terminal and system for implementing network element version compatibility in network management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102013994B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104899017A (en) * | 2014-03-07 | 2015-09-09 | 施耐德电器工业公司 | Electronic system, circuit breaker and method for generating a deviation indicator |
| CN107168726A (en) * | 2017-03-30 | 2017-09-15 | 武汉斗鱼网络科技有限公司 | A kind of method and apparatus of dynamic configuration application program |
| CN107239283A (en) * | 2017-05-31 | 2017-10-10 | 郑州云海信息技术有限公司 | A kind of system management memory software adaptation method and device |
| CN107864414A (en) * | 2017-10-20 | 2018-03-30 | 深圳市新格林耐特通信技术有限公司 | The customized version-switching methods of ONU, device, storage medium and computer equipment |
| CN110221878A (en) * | 2019-06-17 | 2019-09-10 | 北京金山安全软件有限公司 | Game service updating method and device, electronic equipment and storage medium |
| CN111381796A (en) * | 2018-12-28 | 2020-07-07 | 北京字节跳动网络技术有限公司 | Processing method and device for realizing KTV function on client and user equipment |
| CN112948329A (en) * | 2019-12-11 | 2021-06-11 | 中盈优创资讯科技有限公司 | Method and device for comparing equipment configuration files |
| CN112965738A (en) * | 2021-02-02 | 2021-06-15 | 烽火通信科技股份有限公司 | Information model version difference comparison method and device |
| CN113656110A (en) * | 2021-09-02 | 2021-11-16 | 武汉众邦银行股份有限公司 | Page loading method and device for clear-free cache after front-end upgrading |
| CN113805911A (en) * | 2021-02-24 | 2021-12-17 | 北京沃东天骏信息技术有限公司 | Multi-version program management method, device and system of server side |
| CN116430800A (en) * | 2023-06-15 | 2023-07-14 | 中科航迈数控软件(深圳)有限公司 | Configuration method, device, equipment and storage medium based on numerical control system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101083684A (en) * | 2007-07-24 | 2007-12-05 | 华为技术有限公司 | Communication apparatus batch configuration managerial approach and apparatus |
| CN101212342A (en) * | 2006-12-27 | 2008-07-02 | 大唐移动通信设备有限公司 | Multi-version network element network management method |
| US20090319651A1 (en) * | 2008-06-23 | 2009-12-24 | International Business Machines Corporation | System and method for hosting one or more versions of a service using a service proxy |
-
2010
- 2010-11-02 CN CN201010528483.4A patent/CN102013994B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101212342A (en) * | 2006-12-27 | 2008-07-02 | 大唐移动通信设备有限公司 | Multi-version network element network management method |
| CN101083684A (en) * | 2007-07-24 | 2007-12-05 | 华为技术有限公司 | Communication apparatus batch configuration managerial approach and apparatus |
| US20090319651A1 (en) * | 2008-06-23 | 2009-12-24 | International Business Machines Corporation | System and method for hosting one or more versions of a service using a service proxy |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104899017A (en) * | 2014-03-07 | 2015-09-09 | 施耐德电器工业公司 | Electronic system, circuit breaker and method for generating a deviation indicator |
| CN107168726A (en) * | 2017-03-30 | 2017-09-15 | 武汉斗鱼网络科技有限公司 | A kind of method and apparatus of dynamic configuration application program |
| CN107239283A (en) * | 2017-05-31 | 2017-10-10 | 郑州云海信息技术有限公司 | A kind of system management memory software adaptation method and device |
| CN107864414A (en) * | 2017-10-20 | 2018-03-30 | 深圳市新格林耐特通信技术有限公司 | The customized version-switching methods of ONU, device, storage medium and computer equipment |
| CN111381796B (en) * | 2018-12-28 | 2021-09-17 | 北京字节跳动网络技术有限公司 | Processing method and device for realizing KTV function on client and user equipment |
| CN111381796A (en) * | 2018-12-28 | 2020-07-07 | 北京字节跳动网络技术有限公司 | Processing method and device for realizing KTV function on client and user equipment |
| CN110221878A (en) * | 2019-06-17 | 2019-09-10 | 北京金山安全软件有限公司 | Game service updating method and device, electronic equipment and storage medium |
| CN112948329A (en) * | 2019-12-11 | 2021-06-11 | 中盈优创资讯科技有限公司 | Method and device for comparing equipment configuration files |
| CN112948329B (en) * | 2019-12-11 | 2024-05-14 | 中盈优创资讯科技有限公司 | Device configuration file comparison method and device |
| CN112965738A (en) * | 2021-02-02 | 2021-06-15 | 烽火通信科技股份有限公司 | Information model version difference comparison method and device |
| CN113805911A (en) * | 2021-02-24 | 2021-12-17 | 北京沃东天骏信息技术有限公司 | Multi-version program management method, device and system of server side |
| CN113656110A (en) * | 2021-09-02 | 2021-11-16 | 武汉众邦银行股份有限公司 | Page loading method and device for clear-free cache after front-end upgrading |
| CN113656110B (en) * | 2021-09-02 | 2024-03-29 | 武汉众邦银行股份有限公司 | Page loading method and device for front-end updating free cache |
| CN116430800A (en) * | 2023-06-15 | 2023-07-14 | 中科航迈数控软件(深圳)有限公司 | Configuration method, device, equipment and storage medium based on numerical control system |
| CN116430800B (en) * | 2023-06-15 | 2023-09-01 | 中科航迈数控软件(深圳)有限公司 | Configuration method, device, equipment and storage medium based on numerical control system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102013994B (en) | 2014-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102013994B (en) | Method, terminal and system for implementing network element version compatibility in network management | |
| CN107147704B (en) | block chain-oriented universal service middleware system | |
| CN111176976B (en) | Test data generation method and device, storage medium and electronic device | |
| KR101164833B1 (en) | Virtual file system | |
| CN102855152B (en) | The method and system of resource file in upgrade applications | |
| CN109308284B (en) | Report menu generation method and device, computer equipment and storage medium | |
| JP5458995B2 (en) | System structure management apparatus, system structure management method, and program | |
| CN105404524A (en) | Class loading and isolating method and apparatus in Java application | |
| CN109144533A (en) | A kind of method, system and the computer installation of update and the load of application program | |
| CN102404149B (en) | Management system and method of service characteristics | |
| JP2009116733A (en) | Application retrieval system, application retrieval method, monitor terminal, retrieval server, and program | |
| CN110989891A (en) | Component deployment method in chart editor, chart editor and related equipment | |
| US20070168912A1 (en) | Program creating system, program creating program, and program creating module | |
| CN102455905A (en) | Method and system for establishing main panel interface, main panel and main panel interface system | |
| CN111045928A (en) | Interface data testing method, device, terminal and storage medium | |
| CN103530155A (en) | Method and device for installing application program | |
| CN111294397A (en) | npm packet management method, device, electronic equipment and storage medium | |
| CN113268272B (en) | Application delivery method, device and system based on private cloud | |
| CN112162731B (en) | Data expansion method, device, storage medium and electronic device | |
| CN114003210A (en) | SDK-based multi-application program adaptation method, device, equipment and medium | |
| CN113377682A (en) | Service testing method and device | |
| CN110007937B (en) | System updating method and system | |
| AU2009349406B2 (en) | Method for managing configuration information of outsourced part, and method and system for managing alarm | |
| CN110839101A (en) | Calling strategy method based on blacklist | |
| WO2011117954A1 (en) | Virtual machine management device, virtual machine management method, and program |
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 |