CN1756191B - Method for starting net element management system - Google Patents
Method for starting net element management system Download PDFInfo
- Publication number
- CN1756191B CN1756191B CN 200410084838 CN200410084838A CN1756191B CN 1756191 B CN1756191 B CN 1756191B CN 200410084838 CN200410084838 CN 200410084838 CN 200410084838 A CN200410084838 A CN 200410084838A CN 1756191 B CN1756191 B CN 1756191B
- Authority
- CN
- China
- Prior art keywords
- network element
- ems
- version
- information
- interface document
- 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 Transfer Between Computers (AREA)
Abstract
The invention discloses a initiate method of network unit management system, comprising: the EMS connects the network unit and logs in successfully; the EMS transmits the instruction for inquiring the version number of network unit to the network unit; said network unit feeds back the version number to the EMS and judges that if the EMS can operate on said network unit according to the version number, if it can, directly executing the initialized start; if not, said EMS downloads and stores the matching relationship information between the network unit and the version of EMS from said network unit, and judges if the EMS can operate said network unit according to downloaded information; if can, the EMS downloads and stores the interface document data, records the operation on the network of this type and executes the initialized start; if not, alarming the user. The invention can confirm the versatility of EMS, make application more convenient and improve the working efficiency.
Description
Technical field
The present invention relates to the application technology of Element management system, particularly the startup method of Element management system.
Background technology
Network element (Network Element) is the common name of various device in the telecommunications network, all is network element such as RNC, NodeB, SGSN, MSC etc. in the WCDMA of 3G network.Element management system (EMS) is the general name of the terminal (or other kinds Terminal Type) of safeguarding these network elements and the software systems of moving on it.
EMS to operation, control and the maintenance of network element referring to Fig. 1.Fig. 1 is the interconnection structure schematic diagram of EMS and network element, and it comprises Element management system (EMS) 101, mobile switching centre (MSC) 111, mobile switching centre's gateway (GMSC) 112, Serving GPRS Support Node (SGSN) 113, GPRS Support Node gateway (GGSN) 114, radio network controller (RNC) 115, base station (NodeB) 116.As shown in Figure 1, EMS not only can be at the local maintenance network element, such as: EMS direct connecting ne, EMS and the network element LAN inside that coexists; Also can be applied in remote maintenance environment, such as: EMS is connected by WAN with network element.The attendant of telecommunication apparatus sends man-machine language (MML) instruction by EMS to network element, and network element receives the instruction back by the command request operation, and operation result information also feeds back to operating personnel by EMS.
At present, in the world almost each telecom equipment manufacturers all provide EMS to come the network element device of oneself is safeguarded.EMS generally comprises contents such as equipment control, alarm management, performance management and safety management.Because EMS and network element relation are very close, relate to a lot of internal interfaces, so EMS together released when generally issuing the network element product by telecom equipment manufacturers.
In the prior art, EMS to the operation of network element, safeguard flow process as shown in Figure 2, the concrete operations step of this flow process is as follows:
Step 201:EMS connects network element and logins successfully.
Step 202: judge that can EMS operate this network element, if can, then execution in step 203; If can not, then nullify.
Step 203:EMS carries out initialization and starts.
More than in the operation, the concrete execution of the described login process of step 201 is as follows:
1) user starts the EMS program.
2) EMS ejects dialog boxes for login to the user, and the prompting user imports the information such as IP address, username and password of login network element.
3) EMS sends the TCP connection request according to the network element IP address of user's input to this network element.
4) network element is replied this TCP connection request.
5) EMS receives replying that this network element beams back, and so far the TCP between EMS and this network element connects and sets up.
6) EMS is issued to this network element according to the username and password composition log on command of user's input.
7) network element is received its user identity of verification after the log on command.
8) after the verification succeeds, network element returns login success message and gives EMS.
9) after EMS receives message, learn and login successfully.
At present, judge in the step 202 that can EMS exist dual mode by operating network element:
One: adopt artificial affirmation mode, only confirmed the network management personnel that EMS can operate under the situation of this network element and just started subsequent operation, otherwise withdrawed from operation;
Its two: EMS obtains network element version number from this network element, only just starts subsequent operation under this network element belongs to the situation of network element version of EMS coupling, otherwise withdraws from operation;
When operation was carried out to step 203, system's operation relative program was realized the coupling of EMS and network element, and this program waits for that the user imports other instructions then, and initialization starts to be finished.
From the aforesaid operations flow process as can be seen, at present, there is following problem in the EMS that equipment manufacturers provide:
A) EMS that provides of part manufacturer is specially at the equipment of a certain type.Such as: special EMS or special EMS at NodeB at RNC.Different types of network element device needs different types of EMS control, can not be general mutually between these EMS.
B) EMS that provides of part manufacturer is specially at a certain concrete version of a certain type equipment.Such as: the supporting EMS of the V100R002 version of RNC, supporting another EMS of the V100R003 version of RNC.During the RNC network element updating, its supporting EMS also must upgrading, otherwise EMS is uncontrollable and safeguard this network element.
C) EMS that provides of part manufacturer is specially at a certain concrete languages of a certain concrete version of a certain type equipment.Such as: the supporting EMS of the V100R002 Chinese version of RNC, supporting another EMS of the V100R002 English edition of RNC, supporting another EMS of V100R002 Spanish version of RNC.
This shows that under the existing situation, the EMS that network element is operated and controlled that equipment manufacturers provide is special-purpose.During network element updating, the EMS that this network element is operated is supporting upgrading simultaneously also, otherwise can not finish maintenance task.Network element is carried out under the situation of Long-distance Control at EMS, this not general meeting brings very big inconvenience.During the whole network equipment upgrading, owing to relate to problems such as a plurality of network elements, a plurality of version and a plurality of languages, the corresponding one by one inconvenience that brings of this strictness is just more outstanding.
Summary of the invention
In view of this, main purpose of the present invention is to provide the startup method of a kind of EMS, makes things convenient for the user to realize operation, control and maintenance to the network element of dissimilar, different editions or different language with same EMS platform.
For achieving the above object, technical scheme of the present invention specifically is achieved in that
The startup method of a kind of Element management system EMS, this method may further comprise the steps:
A.EMS connects network element and logins successfully;
B. judge that can EMS operate this network element, if can, direct execution in step d then, if can not, execution in step c then;
C.EMS uploads net element information and preservation from this network element, described net element information comprises the information of network element and EMS version match relation, information according to network element and EMS version match relation, judge whether local EMS version belongs to this network element fit version, when the EMS of this locality version belongs to this network element fit version, EMS uploads the interface document data from network element;
D.EMS carries out initialization and starts.
Wherein, can the described judgement of step b EMS carry out method of operating to this network element and be: preserve one and can safeguard the network element version list in that EMS is local; Whether EMS inquires about this network element version and number can safeguard in the network element version list at this.
Can above-mentioned judgement EMS as follows to the process that this network element is operated:
B1.EMS sends number instruction of inquiry network element version to network element;
B2. this network element returns version number to EMS;
B3. search this network element version and number whether can safeguard in the network element version list at this, if could operate, otherwise can not operate.
Preferably, the method for described preservation net element information is: deposit net element information in EMS this locality for this network element creaties directory.
Preferably, further comprise:
According to network element and EMS version match relation information, judge that local EMS version does not belong to this network element fit version, then alert users.
Described uploading write down network element and the information of EMS version match relation and the operation of network element interface file type and interface document version number, and the present invention realizes by upload ini file from this network element.
The operation of described alert users further comprises: whether the prompting user continues to use in the time of alarm, if not, then nullifies operation this time; If then upload and this network element matching E MS program characteristic code and preservation from network element.
Described net element information further comprises: network element interface file type and interface document version number;
The method that described EMS uploads the interface document data from network element is:
C21. judge the local network element version of the same type that whether exist with this network element, if exist, execution in step c22, if there is no execution in step c25 then;
C22. copy network element interface file data of the same type to this network element catalogue;
C23. compare the interface document type and the interface document version number of two network element versions, search the interface document data that need renewal;
C24. upload the interface document data of need upgrading and cover file of the same name this network element catalogue from this network element, then execution in step c26;
C25.EMS uploads the required whole interface document data of this network element;
C26.EMS can safeguard the network element version list with number adding of this network element version.
Preferably, the network element interface file data of the same type of the copy described in the step c2 is that one of selection and this network element version number immediate version copy.
As seen from the above technical solutions, the startup method of this EMS of the present invention, by uploading required net element information realization network element and the Interface Matching between the EMS, greatly reduce the workload of EMS and network element coupling, and be difficult for makeing mistakes, the efficient height, thus overlapping development reduced effectively, reduce use cost.
Description of drawings
Fig. 1 is the interconnection structure schematic diagram of EMS and network element;
Fig. 2 is that EMS starts flow chart in the prior art;
Fig. 3 starts flow chart for EMS among the present invention;
Fig. 4 is the flow chart of a preferred embodiment of the present invention.
Embodiment
The core concept of EMS startup method of the present invention as shown in Figure 3, the startup flow process of Element management system may further comprise the steps:
Step 301:EMS connects network element and logins successfully.
Step 302: judge that can EMS operate this network element, if can not operate, then execution in step 303, if can operate, and then direct execution in step 304.
Step 303:EMS uploads net element information and preservation from this network element.
Step 304:EMS carries out initialization and starts.
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in more detail.
Among the embodiment, suppose that the current EMS version number that network element is carried out operation and maintenance is: LMTV100R002B02D002, operated NE type is SGSN, version number is: SGSN9810V800R002B02D007.
As shown in Figure 4, the startup flow process of this EMS may further comprise the steps:
Step 401:EMS connection is operated network element and logins successfully.Login process is identical with step 201 among Fig. 2, repeats no more herein.
Step 402～404:EMS assigns number instruction of inquiry network element version to this network element, and this network element returns network element version SGSN9810V800R002B02D007 to EMS.After obtaining version number, EMS checks that this locality can safeguard the network element version list, if this version number in tabulation, direct execution in step 413 then, if do not exist, then execution in step 405.The described network element version list of safeguarding writes down the operable NE type of this EMS and network element version number.The network element the safeguarded version list of supposing this EMS as shown in Table 1, judged result is that this network element version is not number in can safeguarding the network element version list.
| Numbering | Network element version number |
| 1 | SGSN9810V800R002B01D005 |
| 2 | SGSN9810V800R002B01D006 |
| 3 | SGSN9810V800R002B02D003 |
| 4 | BSC6800V100R002B03D006 |
| 5 | BSC6800V100R002B04D006 |
| 6 | BSC6800V100R002B04D007 |
| 7 | BTS3802CV100R003B02D001 |
| 8 | BTS3802CV100R003B02D002 |
| 9 | BTS3802CV100R003B02D004 |
| 10 | BTS3812V100R003B02D002 |
| 11 | BTS3812V100R003B02D003 |
| Numbering | Network element version number |
| 12 | BTS3812V100R003B02D004 |
| 13 | BTS3812V100R003B02D005 |
| 14 | UMG8900V100R002B01D003 |
| 15 | UMG8900V100R002B01D005 |
| 16 | UMG8900V100R002B02D003 |
| 17 | UMG8900V100R002B03D001 |
| 18 | CSOFTX3000V100R001B01D001 |
| 19 | CSOFTX3000V100R001B01D002 |
| 20 | CSOFTX3000V100R001B02D001 |
| 21 | CSOFTX3000V100R002B03D001 |
Table one
Step 405:EMS number runs after fame with network element version and is called this network element and creates a directory, and from information and network element interface file type and interface document version number that this network element is uploaded record network element and EMS version match relation, above-mentioned information is saved under this catalogue.In network element, above-mentioned information is recorded as an ini file.The ini file of this network element comprises table two and table three two parts content, and wherein table two is matching relationship tabulations of network element version number and EMS version number, and table three is interface document type and tabulations of interface document version number of EMS and network element.
| Numbering | Network element version number | EMS version number |
| 1 | SGSN9810V800R002B01D003 | LMTV100R002B01D007 LMTV100R002B01D008 LMTV100R002B01D010 |
| 2 | SGSN9810V800R002B01D004 | LMTV100R002B01D009 LMTV100R002B01D010 LMTV100R002B01D011 LMTV100R002B01D012 LMTV100R002B01D013 |
| Numbering | Network element version number | EMS version number |
| LMTV100R002B01D014 LMTV100R002B01D015 | ||
| 3 | SGSN9810V800R002B01D005 | LMTV100R002B01D015 LMTV100R002B01D016 LMTV100R002B01D017 |
| 4 | SGSN9810V800R002B01D006 | LMTV100R002B01D015 LMTV100R002B01D016 LMTV100R002B01D017 LMTV100R002B01D018 |
| 5 | SGSN9810V800R002B01D007 | LMTV100R002B01D015 LMTV100R002B01D016 LMTV100R002B01D017 LMTV100R002B01D018 LMTV100R002B01D019 |
| 6 | SGSN9810V800R002B01D008 | LMTV100R002B01D017 LMTV100R002B01D018 LMTV100R002B01D019 |
| 7 | SGSN9810V800R002B01D009 | LMTV100R002B01D020 LMTV100R002B01D021 |
| 8 | SGSN9810V800R002B02D002 | LMTV100R002B01D020 LMTV100R002B01D021 |
| 9 | SGSN9810V800R002B02D003 | LMTV100R002B01D020 LMTV100R002B01D021 |
| 10 | SGSN9810V800R002B02D004 | LMTV100R002B01D020 LMTV100R002B01D021 LMTV100R002B02D001 |
| 11 | SGSN9810V800R002B02D005 | LMTV100R002B01D020 LMTV100R002B01D021 LMTV100R002B02D001 |
| Numbering | Network element version number | EMS version number |
| 12 | SGSN9810V800R002B02D006 | LMTV100R002B02D002 |
| 13 | SGSN9810V800R002B02D007 | LMTV100R002B02D002 LMTV100R002B02D003 |
Table two
| Numbering | The interface document type | Interface document version number |
| 1 | bam_retcode.ini | 0004 |
| 2 | Cc128toc.idx | 0017 |
| 3 | Macro.ini | 0017 |
| 4 | UMSCUI.INI | 0010 |
| 5 | SGSN_maintenance.xml | 0005 |
| 6 | SGSN_BSSAP_INTER.dll | 0006 |
| 7 | SGSN_CDB_INTER.dll | 0001 |
| 8 | SGSN_DNS_INTER.dll | 0012 |
| 9 | SGSN_GSS_INTER.dll | 0013 |
Table three
Step 406: judge by the matching relationship of network element version in the ini file number and EMS version number whether local EMS version belongs to this network element fit version, if not, then execution in step 407, if then execution in step 410.For the network element in the present embodiment, by table two as can be seen: with this network element version SGSN9810V800R002B02D007 matching E MS version number be: LMTV100R002B02D002 and LMTV100R002B02D003, so current EMS version and this network element version coupling, promptly EMS can carry out operation and maintenance to this network element.
Step 407～409: alert users, whether inquiry simultaneously continues to use, if do not continue to use, then nullifies and withdraw from operation this time, if continue to use, then uploads characteristic code with the program of its matching E MS from this network element, and execution in step 410 then.Described characteristic code is meant the program patch that is encapsulated as executable file, moves this patch and can carry out the function that this version EMS is different from other EMS.
Step 410: judgement can safeguard whether there be the network element version of the same type with this network element in the network element version list, and if there is no execution in step 411 then is if exist then execution in step 412.By table one as can be seen, can safeguard the network element version identical of existence in the network element version list number with this NE type, be respectively: SGSN9810V800R002B01D005, SGSN9810V800R002B01D006 and SGSN9810V800R002B02D003, so execution in step 412.
Step 411:EMS uploads the required whole interface document data of this network element and is kept in the catalogue of step 405 establishment, and execution in step 413 then.
Step 412: select to compare with the immediate SGSN version of this network element version SGSN9810V800R002B02D003, total interface file data in the SGSN9810V800R002B02D003 catalogue is copied in the catalogue of step 405 establishment, the ini file of this network element and network element SGSN9810V800R002B02D003 relatively simultaneously, finding out needs the interface document that upgrades.Table four is interface document type and tabulations of interface document version number of network element SGSN9810V800R002B02D003.The table of comparisons three and table four, the interface document that need upload comprises: bam_retcode.ini version number 0004, UMSCUI.INI version number 0010, SGSN_BSSAP_INTER.dll version number 0006 and SGSN_GSS_INTER.dll version number 0013.EMS uploads the interface document that needs renewal from this network element, and covers the file of the same name in this network element catalogue.
| Numbering | The interface document type | Interface document version number |
| 1 | bam_retcode.ini | 0003 |
| 2 | Cc128toc.idx | 0017 |
| 3 | Macro.ini | 0017 |
| 4 | UMSCUI.INI | 0009 |
| 5 | SGSN_maintenance.xml | 0005 |
| 6 | SGSN_BSSAP_INTER.dll | 0005 |
| 7 | SGSN_CDB_INTER.dll | 0001 |
| 8 | SGSN_DNS_INTER.dll | 0012 |
| 9 | SGSN_GSS_INTER.dll | 0012 |
Table four
Step 413: interface document is uploaded and is finished, and EMS can safeguard the network element version list with number adding of this network element version.Table five is the network element the safeguarded version list after upgrading.
| Numbering | Network element version number |
| 1 | SGSN9810V800R002B01D005 |
| Numbering | Network element version number |
| 2 | SGSN9810V800R002B01D006 |
| 3 | SGSN9810V800R002B02D003 |
| 4 | SGSN9810V800R002B02D007 |
| 5 | BSC6800V100R002B03D006 |
| 6 | BSC6800V100R002B04D006 |
| 7 | BSC6800V100R002B04D007 |
| 8 | BTS3802CV100R003B02D001 |
| 9 | BTS3802CV100R003B02D002 |
| 10 | BTS3802CV100R003B02D004 |
| 11 | BTS3812V100R003B02D002 |
| 12 | BTS3812V100R003B02D003 |
| 13 | BTS3812V100R003B02D004 |
| 14 | BTS3812V100R003B02D005 |
| 15 | UMG8900V100R002B01D003 |
| 16 | UMG8900V100R002B01D005 |
| 17 | UMG8900V100R002B02D003 |
| 18 | UMG8900V100R002B03D001 |
| 19 | CSOFTX3000V100R001B01D001 |
| 20 | CSOFTX3000V100R001B01D002 |
| 21 | CSOFTX3000V100R001B02D001 |
| Numbering | Network element version number |
| 22 | CSOFTX3000V100R002B03D001 |
Table five
Step 414:EMS carries out initialization and starts.Start-up course is identical with step 203 among Fig. 2, repeats no more herein.
By the above embodiments as seen, the general EMS startup method that the present invention adopts is under EMS and the unmatched situation of network element version, need not to change EMS, only need from network element upload need the interface document data upgraded or with this network element matching E MS program characteristic code, the needs of EMS and network element matching operation in the time of can satisfying the initialization startup, simplified the operating process of EMS on the one hand, improve the versatility of EMS, be user-friendly to, greatly reduce the workload of EMS and network element coupling on the other hand, raise the efficiency.
Claims (9)
1. the startup method of an Element management system EMS is characterized in that, this method may further comprise the steps:
A.EMS connects network element and logins successfully;
B. judge that can EMS operate this network element, if can, direct execution in step d then, if can not, execution in step c then;
C.EMS uploads net element information and preservation from this network element, described net element information comprises the information of network element and EMS version match relation, information according to network element and EMS version match relation, judge whether local EMS version belongs to this network element fit version, when the EMS of this locality version belongs to this network element fit version, EMS uploads the interface document data from network element;
D.EMS carries out initialization and starts.
2. method according to claim 1 is characterized in that, can safeguard the network element version list one of the local preservation of EMS; Can the described EMS of judgement of step b carry out method of operating to this network element: whether EMS inquires about this network element version and number can safeguard in the network element version list at this.
3. method according to claim 2 is characterized in that, judges that can EMS as follows to the process that this network element is operated:
B1.EMS sends number instruction of inquiry network element version to network element;
B2. this network element returns version number to EMS;
B3. search this network element version and number whether can safeguard in the network element version list at this, if could operate, otherwise can not operate.
4. method according to claim 1 is characterized in that, further comprises:
According to network element and EMS version match relation information, judge that local EMS version does not belong to this network element fit version, then alert users.
5. method according to claim 4 is characterized in that, the operation of described alert users further comprises: whether the prompting user continues to use in the time of alarm, if not, then nullifies operation this time; If then upload and this network element matching E MS program characteristic code and preservation from network element.
6. method according to claim 1 is characterized in that, described net element information further comprises: network element interface file type and interface document version number;
The method that described EMS uploads the interface document data from network element is:
C21. judge the local network element version of the same type that whether exist with this network element, if exist, execution in step c22, if there is no execution in step c25 then;
C22. copy network element interface file data of the same type to this network element catalogue;
C23. compare the interface document type and the interface document version number of two network element versions, search the interface document data that need renewal;
C24. upload the interface document data of need upgrading and cover file of the same name this network element catalogue from this network element, then execution in step c26;
C25.EMS uploads the required whole interface document data of this network element;
C26.EMS can safeguard the network element version list with number adding of this network element version.
7. method according to claim 6 is characterized in that, selects one to copy with this network element version number immediate version when copying network element interface file data of the same type.
8. method according to claim 6 is characterized in that, describedly uploads the information of record network element and EMS version match relation and the operation of network element interface file type and interface document version number realizes by upload ini file from this network element.
9. according to each described method of claim 1 to 8, it is characterized in that the method for described preservation net element information is: deposit net element information for this network element creaties directory in EMS this locality.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410084838 CN1756191B (en) | 2004-09-30 | 2004-09-30 | Method for starting net element management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410084838 CN1756191B (en) | 2004-09-30 | 2004-09-30 | Method for starting net element management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1756191A CN1756191A (en) | 2006-04-05 |
| CN1756191B true CN1756191B (en) | 2010-04-28 |
Family
ID=36689157
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200410084838 Expired - Fee Related CN1756191B (en) | 2004-09-30 | 2004-09-30 | Method for starting net element management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1756191B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100454847C (en) * | 2006-12-12 | 2009-01-21 | 华为技术有限公司 | Method and apparatus for starting terminal management system |
| CN101212346B (en) * | 2006-12-31 | 2010-12-01 | 中兴通讯股份有限公司 | Software version management method and device for network element management system |
| CN100466556C (en) * | 2007-03-30 | 2009-03-04 | 华为技术有限公司 | Network device management method and system |
| CN101296111B (en) * | 2007-04-29 | 2012-06-27 | 华为技术有限公司 | Method and system for automatically implementing link between management equipment and managed equipment |
| CN101370221B (en) * | 2007-08-15 | 2014-11-05 | 中兴通讯股份有限公司 | Software version management method for network element management system based on file mode |
| CN101753346B (en) * | 2008-12-03 | 2011-11-09 | 中国移动通信集团公司 | Method and system for leading in comprehensive webmaster data |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6047279A (en) * | 1997-11-17 | 2000-04-04 | Objective Systems Integrators, Inc. | System and method for automatic network management support using artificial intelligence |
| JP2001203743A (en) * | 2000-01-24 | 2001-07-27 | Nippon Telegr & Teleph Corp <Ntt> | Method for managing communication network |
| JP2001344161A (en) * | 2000-06-01 | 2001-12-14 | Matsushita Electric Ind Co Ltd | Network apparatus management system |
| WO2004010631A2 (en) * | 2002-07-19 | 2004-01-29 | Masergy Communications | Automated configuration of packet routed network |
-
2004
- 2004-09-30 CN CN 200410084838 patent/CN1756191B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6047279A (en) * | 1997-11-17 | 2000-04-04 | Objective Systems Integrators, Inc. | System and method for automatic network management support using artificial intelligence |
| JP2001203743A (en) * | 2000-01-24 | 2001-07-27 | Nippon Telegr & Teleph Corp <Ntt> | Method for managing communication network |
| JP2001344161A (en) * | 2000-06-01 | 2001-12-14 | Matsushita Electric Ind Co Ltd | Network apparatus management system |
| WO2004010631A2 (en) * | 2002-07-19 | 2004-01-29 | Masergy Communications | Automated configuration of packet routed network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1756191A (en) | 2006-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102164363B (en) | Base station version updating realization method and base station | |
| RU2549126C2 (en) | Method and system for installing and updating software of application terminal in home network | |
| CN101577901B (en) | Wireless access platform and equipment upgrading management system and method thereof | |
| CN110086652B (en) | Management system and method for service network element in 5G core network | |
| CN101163043B (en) | Network management function configuring method and system | |
| CN101227428B (en) | Application server and remote control method thereof | |
| CN103593207A (en) | High-speed automatic cluster system deployment method using virtual disk | |
| CN100399268C (en) | Computer system not relying on operation system renewing software data and method | |
| US20120117557A1 (en) | Method and system for upgrading wireless data card | |
| JP2001043086A (en) | System and method for constituting personal system | |
| CN106254127A (en) | Automatic deployment method of RabbitMQ cluster service based on virtualization platform | |
| CN101694637A (en) | Method and system for restoring database | |
| CN101883002A (en) | Method and system for installing plug-in device | |
| CN101188516A (en) | A highly reliable and self-adapted remote update method for network device software system | |
| CN104657161A (en) | Method and device for updating firmware of mobile terminal | |
| CN1756191B (en) | Method for starting net element management system | |
| CN103777981A (en) | Multi-operation-system remote loading implementation method suitable for X86 framework | |
| CN103024782A (en) | Base station software version management method and system | |
| CN101221507B (en) | Device, system and method for automatically installing network television incremental value service | |
| CN103746998A (en) | Method for realizing support of wireless network mounting by NFS (network file system) | |
| CN104793998A (en) | Terminal system resource management method and device | |
| CN104318091A (en) | Moonlet ground testing method based on virtualization computer system | |
| CN102567050B (en) | The method and apparatus of B/S system remote deploying projects | |
| CN101453473A (en) | Remote service system based on different operation systems and equipment thereof | |
| CN103096137A (en) | Smart television application program remote boot method and system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100428 Termination date: 20200930 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |