CN101267341A - A distributed network management system, network management server and method - Google Patents
A distributed network management system, network management server and method Download PDFInfo
- Publication number
- CN101267341A CN101267341A CNA2008100662213A CN200810066221A CN101267341A CN 101267341 A CN101267341 A CN 101267341A CN A2008100662213 A CNA2008100662213 A CN A2008100662213A CN 200810066221 A CN200810066221 A CN 200810066221A CN 101267341 A CN101267341 A CN 101267341A
- Authority
- CN
- China
- Prior art keywords
- server
- information
- subsystem
- deployment
- current
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention embodiment discloses a distributed network management system, comprising: a deployment server and at least one network management server. The network management server is used for gaining deployment information corresponding to a native machine from the deployment server, and determining system identification information waiting for being deployed in the current network management server according to the deployment information, and gaining and saving a subsystem software corresponding to the subsystem identification information from the deployment server, and starting the subsystem software. The deployment server is used for storing all subsystem softwares and subsystem distributed deployment information of the subsystem provided with the distributed network management system. The invention embodiment also discloses the network management server and a distributed deployment method.
Description
Technical field
The present invention relates to the network management technology field, particularly a kind of distributed network management system, NM server, distributed deployment method.
Background technology
Continuous development along with computer and mechanics of communication, the network size that network management system need be managed is increasing, managerial ability to system is had higher requirement, at present in order to tackle the situation that network size constantly enlarges, network management system reaches the ability that improves management scale progressively by the mode switch of single host to the distributed multi-master machine by using the multiple host load sharing.Owing to become several or even tens main frames by a main frame, the deployment maintenance work such as installation, upgrading, patch installing that operate in the software systems on each main frame respectively all become very complicated;
At distribution type network management system, present deployment way is the mode that adopts manual maintenance, promptly uses the installation medium of network management system manually to carry out the operation of installation, upgrading, patch installing on every main frame by the system manager;
The present inventor finds that in the research process to prior art existing mode is poor for the maintainability of distribution type network management system.
Summary of the invention
The embodiment of the invention provides a kind of distributed deployment method, distributed network management system and NM server, to improve the maintainability of system.
For achieving the above object, the technical scheme of the embodiment of the invention specifically is achieved in that
A kind of distributed network management system comprises: deployment server and at least one NM server,
Described NM server, be used for obtaining the deployment information relevant with this machine from described deployment server, determine to wait to be deployed in the subsystem identification information of current NM server according to described deployment information, and, start described subsystem software from described deployment server acquisition and corresponding subsystem software of described subsystem identification information and preservation;
Described deployment server is used to store the subsystem software and the subsystem distribution deployment information of all subsystems of distribution type network management system.
And a kind of NM server is applied to distributed network management system, comprising:
Information transmission modular, be used to send the request message that obtains deployment information, and receive return with described request message corresponding response information, obtain the deployment information relevant by this response message, and obtain and described definite corresponding subsystem software of subsystem identification information to be disposed and preservation from deployment server with current NM server;
The management of process module is used for the subsystem software that described information transmission modular obtains is started;
Dispose administration module, be used to call described information transmission modular and obtain deployment information, determine the subsystem identification information that this machine is to be disposed according to the deployment information that described information transmission modular obtains, call described information transmission modular and obtain corresponding subsystem software, and after described information transmission modular obtains subsystem software, call described management of process module and start.
And a kind of NM server is applied in the distribution type network management system, and other NM servers are communicated by letter with this NM server in this distribution type network management system, and this NM server comprises:
The subsystem loader, be used for obtaining the deployment information relevant with current NM server to described transmission service module request, determine to wait to be deployed in the subsystem identification information of current NM server according to the deployment information of described acquisition, and, the subsystem software of described acquisition is preserved and startup to described transmission service module request acquisition and the corresponding subsystem software of described subsystem identification information;
The transmission service module, the request message that is used for obtaining according to being used to of receiving deployment information returns and described request message corresponding response information, described response message comprises the deployment information relevant with requesting party's NM server, and obtain request message with the corresponding subsystem software of requesting party's NM server subsystem identification information according to being used to of receiving, return corresponding subsystem software.
And a kind of distributed deployment method is applied at least one NM server in the distributed network management system, and wherein the subsystem mutual group on each NM server becomes distributed network management system, comprising:
Obtain the deployment information relevant with current NM server;
Determine the subsystem identification information that current NM server is to be disposed according to the deployment information of described acquisition;
The subsystem software corresponding with this subsystem identification information downloaded in request, receives and preserve the subsystem software of returning corresponding with this request;
Start described subsystem software.
As seen from the above technical solution, in the embodiment of the invention by adopting the mode that pulls down file from deployment server to realize automatic installation, deployment, the upgrading of subsystem software, thereby improve the maintainability of distribution type network management system, improve maintenance efficiency, reduced the maintenance cost of distribution type network management system.
Description of drawings
Fig. 1 is a kind of distribution type network management system structural representation of the embodiment of the invention;
Fig. 2 is the content exemplary plot of the subsystem distribution deployment information of the embodiment of the invention;
Fig. 3 is the running state moving schematic diagram of the NM server of the embodiment of the invention;
Fig. 4 is the distribution type network management system structural representation of the embodiment of the invention one;
Fig. 5 is the internal module schematic diagram of the NM server of the embodiment of the invention one;
Fig. 6 is the distribution type network management system structural representation of the embodiment of the invention two;
Fig. 7 is the internal module schematic diagram of the NM server of the embodiment of the invention two;
Fig. 8 is the distribution type network management system structural representation of the embodiment of the invention three;
Fig. 9 is the flow diagram of the distributed deployment method of the embodiment of the invention;
Figure 10 is the interaction diagrams of the distributed deployment method of the embodiment of the invention four;
Figure 11 is the interaction diagrams of the upgrade method of the embodiment of the invention five;
Figure 12 obtains the interaction diagrams of deployment information for the embodiment of the invention six from deployment server;
Figure 13 obtains the interaction diagrams of deployment information for the embodiment of the invention seven from deployment server;
Figure 14 obtains the interaction diagrams of deployment information for the embodiment of the invention eight from deployment server;
Figure 15 is the interaction diagrams of the employing http protocol of the embodiment of the invention nine from the deployment server file in download;
Figure 16 is the interaction diagrams of the non-http protocol of the employing of the embodiment of the invention ten from the deployment server file in download;
Embodiment
For making purpose of the present invention, technical scheme clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in further detail.
In embodiments of the present invention, distributed network management system (abbreviation distribution type network management system) comprises deployment server and at least one NM server (having another name called the webmaster main frame), wherein each NM server can be finished deployment first, the installation of subsystem software to be disposed automatically, and the renewal/upgrading that has been deployed in the subsystem software of this machine.
Fig. 1 is the structural representation of the distribution type network management system in the embodiment of the invention.As shown in Figure 1, the distribution type network management system of the embodiment of the invention comprises deployment server 200 and NM server 101-10N, wherein,
Deployment server 200 is used to store all subsystem software of this distribution type network management system, and the distribution deployment information of each subsystem in this network management system; The subsystem distribution deployment information here is the distribution deployment information of each subsystem in the network management system, the distribution situation of each subsystem at each NM server described, under a kind of implementation, the content example is as shown in Figure 2: this subsystem distribution deployment information comprises subsystem identification information, NM server identification information (having another name called equipment identification information), subsystem version information three's mapping relations (here subsystem identification information and subsystem version information can be referred to as subsystem information), be every and be recorded as the subsystem identification information of every NM server correspondence and the version information of this subsystem, for example: that subsystem correspondence to be disposed is subsystem A on the NM server 1, and the version information of this subsystem A is 3.2; Should be understood that: the NM server identification information here can be IP address, MAC Address or the host name etc. of the NM server of correspondence; Wherein, the storage mode of subsystem distribution deployment information can have several, a kind of be that deployment information with all NM servers is stored in the file is full dose deployment information file, a kind of is that deployment information with each NM server is stored in respectively in the file, i.e. the deployment information of a NM server of each deployment information file description; Another kind can also be that the subsystem deployment information that distributes is stored in the database;
Subsystem on the NM server 101-10N is incomplete same, and promptly the subsystem on all NM servers has constituted the background system of whole distribution type network management system jointly.
Fig. 3 is the running state moving schematic diagram of NM server, introduces the operation principle that NM server is disposed installation, upgrading and patch installing automatically below in conjunction with Fig. 3; Because the operation principle of every NM server is identical, is that example describes with a NM server here:
During initial state, the local cache of current NM server is empty, and system still can not move.
Current NM server (when system initialization time) when starting for the first time carries out the installation first of this loom systems soft ware, the subsystem software that is about to wait to be deployed on this machine downloads to local cache from deployment server, afterwards each subsystem is started, then current NM server has just entered run mode, just can handle the webmaster business.
Subsystem software on deployment server has been carried out upgrading or patch has been installed, and then system has entered attitude to be updated, and there is the inconsistent situation of version in subsystem software and the software on the deployment server in the local cache of current NM server at this moment.Current NM server carries out the renewal of increment, download and the renewal local cache from deployment server at the subsystem software that needs upgrade, start promptly upgrade subsystem software in the current NM server local cache of each subsystem then, system has returned to run mode again.
Fig. 4 is the structural representation of the distribution type network management system of the embodiment of the invention one, wherein, deployment server 400, be used to store all subsystem software of this distribution type network management system, and the distribution deployment information of each subsystem in this network management system, and return corresponding subsystem software, deployment information according to the request message of NM server;
Wherein, deployment server 400 comprises: memory module, be used to store all subsystem software of this distribution type network management system, and the distribution deployment information of each subsystem in this network management system; The subsystem software here, subsystem distribution deployment information can be that the form with file is saved in the hard disk of deployment server 400, also can be distribute deployment information, subsystem software of subsystem is saved in the database of deployment server 400;
Transmission service module 4010 is used to receive the request message from NM server, and obtains response message that should request message from memory module and return according to this request message; The response message here comprises: deployment information, subsystem software;
NM server 300-30N, be used for obtaining the deployment information relevant with this machine from deployment server 400, determine to wait to be deployed in the subsystem identification information of current NM server according to described deployment information, and, start described subsystem software from deployment server 400 acquisitions and corresponding subsystem software of described subsystem identification information and preservation; Under a kind of implementation, promptly be used for when system initialization, send first request message that is used to obtain deployment information to deployment server 400, and receive first response message corresponding return with first request message, obtain the deployment information relevant by described first response message with this machine, determine to wait to be deployed in the subsystem identification information of current NM server according to this deployment information, for example: subsystem A, and send second request message that is used to download with the corresponding subsystem software of described subsystem identification information to deployment server 400, receive and preserve the subsystem software of returning, start described subsystem software, thereby finished the installation automatically first of the subsystem software of current NM server; Be that NM server 300-30N is moved to run mode from initial state;
NM server 300-30N, also be used for when determining that subsystem software that current NM server has been disposed the subsystem related with current NM server on the deployment server is inconsistent, send the 3rd request message of the subsystem file after being used for down loading updating to deployment server 400, and the subsystem software returned preserved and restart, thereby finished the auto-update of the subsystem software of current NM server, promptly NM server 300-30N is moved to run mode from attitude to be updated;
Fig. 5 is the internal module schematic diagram of the NM server of the embodiment of the invention one, considers that the internal module of every NM server is identical, and following is that example is introduced with the NM server among Fig. 4 300, and as shown in Figure 5, wherein NM server 300 comprises:
Dispose administration module 3010, be used for when system initialization, recalls information transport module 3012 obtains deployment information, determine the subsystem identification information that this machine is to be disposed according to the deployment information that information transmission modular 3012 obtains, recalls information transport module 3012 obtains subsystem software, and after information transmission modular 3012 obtained subsystem software, calling process administration module 3014 started; In other words, disposing administration module 3010 is master control centers, is responsible for the finishing of deployment, escalation process of the subsystem software of current NM server;
Information transmission modular 3012, be used to send the request message that obtains deployment information, and receive deployment server 400 that return with described request message corresponding response information, obtain the deployment information relevant by this response message, and obtain and described definite corresponding subsystem software of subsystem identification information to be disposed and preservation from deployment server 400 with current NM server; The response message here can be the response message that includes the relevant deployment information of current NM server, also can be full dose deployment information file, also can be the deployment information file of current NM server correspondence.
Management of process module 3014 is used for the subsystem software that information transmission modular 3012 obtains is started.
NM server 300 further comprises: memory module 3016, the subsystem software that is used to store current NM server; Optionally, the deployment information file that obtains before memory module 3016 can also be stored can be a catalogue of hard disk;
When adopting the deployment information of all NM servers is left concentratedly in a file, be that deployment information file under a kind of implementation is that full dose deployment information file (is called for short the full dose file, be stored in deployment server, deployment server returns corresponding file according to access path) time, information transmission modular 3012 is a first information transport module, be used to send the 4th request message that carries full dose deployment information file access routing information, and receive the full dose file corresponding that returns with described the 4th request message, from described full dose file, search and obtain the relevant deployment information of current NM server; And, be used to send the 5th request message that carries current NM server subsystem identification information corresponding file access path information to be disposed, and receive subsystem software corresponding and the preservation of returning with described the 5th request message.Should be understandable that: the made an appointment form in file access path of different files of NM server and deployment server, for example: can divide storing directory by subsystem, as for subsystem A, can be so subsystem A * .*, be exactly the path of the All Files of subsystem A;
When adopting the deployment information of the deployment information of all NM servers being left concentratedly in a file maybe all NM servers to be stored in the database of deployment server (in this manner, be responsible for finding the relevant deployment information of current NM server and return by deployment server), information transmission modular 3012 is second information transmission modular, be used to send the 6th request message of the equipment identification information that carries current NM server, and receive the 6th response message that includes current NM server related deployment information that returns, from this response message, extract and obtain the relevant deployment information of current NM server; And, be used to send the 7th request message that carries current NM server subsystem identification information corresponding file access path information to be disposed, and receive subsystem software corresponding and the preservation of returning with described the 7th request message.
When adopting deployment information to leave in the unique file with each NM server, when promptly being stored as a plurality of file by each NM server (in this manner, deployment server returns corresponding file according to access path), information transmission modular 3012 is the 3rd information transmission modular, be used to send the 8th request message of the deployment information corresponding file access path information that carries current NM server, and receive the deployment information file corresponding that returns with described the 8th request message, from described deployment information file, extract and obtain the relevant deployment information of current NM server; And, be used to send the 9th request message that carries current NM server subsystem identification information corresponding file access path information to be disposed, and receive subsystem software corresponding and the preservation of returning with described the 9th request message.
Disposing administration module 3010 is further used for, regularly recalls information transport module 3012 obtains up-to-date deployment information, compare this machine and disposed the related subsystem of current NM server in the deployment information of subsystem and the acquisition of described information transmission modular, disposed the related subsystem of current NM server in the deployment information of subsystem and described information transmission modular acquisition when inconsistent determining this machine, the subsystem software relevant after recalls information transport module 3012 obtains to upgrade with current NM server, and calling process administration module 3014 restarts the subsystem after the renewal;
Information transmission modular 3012, be further used for sending the request message that obtains deployment information, and receive the response message that deployment server 400 returns, obtain the deployment information relevant by described response message, and obtain subsystem software after the renewal relevant with current NM server from deployment server with current device;
Described management of process module is further used for stopping the subsystem to have disposed on the current NM server, and starts the subsystem software after the renewal that described information transmission modular obtains.
Fig. 6 is the distribution type network management system structural representation of the embodiment of the invention two.Wherein, NM server 600 (role who takes on NM server and deployment server simultaneously), existing function as deployment server also has the function as NM server; As shown in Figure 6, other NM servers 501-50N communicates by letter with this NM server 600 in this distribution type network management system, subsystem on NM server 600 and the NM server 501-50N is incomplete same, and promptly the subsystem on all NM servers has constituted the background system of whole distribution type network management system jointly.
Fig. 7 is the internal module schematic diagram of NM server 600 in the distribution type network management system of the embodiment of the invention two, (the internal module structure of NM server 501-50N as shown in Figure 5, so no longer describe), as shown in Figure 7, NM server 600 comprises subsystem loader 6020 and transmission service module 6010, wherein:
Subsystem loader 6020, be used for when current NM server initialization, obtain the deployment information relevant to 6010 requests of transmission service module with current NM server, determine to wait to be deployed in the subsystem identification information (subsystem tabulation) of current NM server according to the deployment information of described acquisition, and, the subsystem software of described acquisition is preserved and startup to described transmission service module request acquisition and the corresponding subsystem software of described subsystem identification information;
Transmission service module 6010, the request message that is used for obtaining according to being used to of receiving deployment information returns and described request message corresponding response information, described response message comprises the deployment information relevant with requesting party's NM server, and obtain request message with the corresponding subsystem software of requesting party's NM server subsystem identification information according to being used to of receiving, return corresponding subsystem software.
NM server 600 further comprises: store all subsystem software in this distribution type network management system, and the memory module of subsystem distribution deployment information;
Under a kind of implementation, transmission service module 6010 is the second transmission service module, be used to receive the request message of the equipment identification information that carries requesting party's NM server, from this memory module, find the deployment information relevant and return the response message that comprises deployment information according to the equipment identification information in the request message with the requesting party, and the request message that receives the subsystem file access path information that carries requesting party's subsystem identification information correspondence, obtain corresponding subsystem software and return corresponding subsystem software from this memory module according to the subsystem file access path information in the request message.
Under a kind of implementation, transmission service module 6010 is the first transmission service module, be used to receive the request message that carries deployment information file access routing information, from this memory module, obtain the deployment information file under this path and return according to the deployment information file access routing information in the request message, and the request message that receives the subsystem file access path information that carries requesting party's subsystem identification information correspondence, from this memory module, obtain the subsystem software under this path and return corresponding subsystem software according to the subsystem file access path information in the request message.The deployment information file access routing information here comprises: the access path of the deployment information file of full dose deployment information file access path, current NM server correspondence.
Subsystem loader 6020 comprises:
Dispose management submodule 6021, be used for when initialization, recalls information transmission submodule 6022 obtains the deployment information relevant with current device, determine the subsystem identification information that this machine is to be disposed according to the deployment information that message transmission submodule 6022 obtains, recalls information transmission submodule 6022 obtains subsystem software, and after message transmission submodule 6022 obtained subsystem software, calling process management submodule 6023 started;
When the response message returned of transmission service module 6010 during for requesting party's deployment information file (deployment information that promptly only comprises the requesting party), message transmission submodule 6022 extracts from the deployment information file that returns and obtains the deployment information relevant with current NM server;
When the response message returned of transmission service module 6010 was full dose deployment information file (deployment information that promptly comprises all NM servers), message transmission submodule 6022 was searched from the deployment information file that returns and is obtained the deployment information relevant with current NM server;
The response message of returning when transmission service module 6010 is when comprising the response message of requesting party's related deployment information, and message transmission submodule 6022 extracts from the response message of returning and obtains the deployment information relevant with current NM server;
And subsystem loader 6020 also comprises: management of process submodule 6023 is used for the subsystem software that message transmission submodule 6022 obtains is started.
Further, subsystem loader 6020 comprises: buffer memory 6024 is used to preserve the subsystem software that message transmission submodule 6022 obtains.
Fig. 8 is the structural representation of the distribution type network management system of the embodiment of the invention three, has described the scene of a concrete distribution type network management system, and wherein, the subsystem on the NM server 701 is topology service, security service; Subsystem on the NM server 702 is a failed services; Subsystem on the NM server 703 is performance management, Circuit management; Subsystem on the NM server 704 is a service dispense.These subsystems have constituted the background system of whole distribution type network management system jointly.Different NM servers is handled different webmaster business.
The embodiment of the invention also provides a kind of distributed deployment method, at least one the NM server that this method is applied in the distributed network management system installed subsystem software automatically, wherein the subsystem mutual group on all NM servers becomes distributed network management system, Fig. 9 is the flow diagram of the distributed deployment method of the embodiment of the invention, being corresponding NM server moves to the process of run mode from initial state, comprising:
Step 8010, the deployment information that acquisition is relevant with current device; Should be understood that the trigger condition that obtains deployment information here can be when system initialization;
Specifically can be: send the request message be used to obtain deployment information, and receive return with described request message corresponding response information, obtain the deployment information relevant by this response message with current device;
Step 8011, determine the subsystem identification information that current device is to be disposed according to the deployment information that obtains, for example: subsystem A, B, C, D.
Wherein, deployment information comprise subsystem identification information, equipment identification information, with corresponding subsystem version information three's related information, here subsystem identification information and subsystem version information can be referred to as subsystem information;
Under a kind of implementation, specifically can be: according to described related information, determine the subsystem identification information corresponding with the current device identification information, the identification information that described subsystem identification information is current device subsystem to be disposed (should be understood that:, subsystem identification information can be called the subsystem tabulation) when subsystem to be disposed when being a plurality of.
The subsystem software corresponding with this subsystem identification information downloaded in step 8012, request, and the subsystem software corresponding with request that will return preserved;
Step 8013, the described subsystem software that starts.
Promptly download to finish each subsystem is started, current NM server enters run mode, and when every NM server has all entered run mode, whole network management system has just entered run mode.
Distributed deployment method for a better understanding of the present invention, the interaction flow below in conjunction with Figure 10 specifically introduces the distributed deployment method of an embodiment of the present invention as shown in figure 10, comprising:
Step 9010, NM server and deployment server are mutual, obtain the deployment information relevant with current NM server; Here have multiple implementation, the back will be introduced in detail;
Whether step 9011, deployment server determine whether allowing the download of deployment information and subsystem software in subsystem distribution deployment information according to requesting party's equipment identification information; This is optional step, further improves fail safe; The equipment identification information here, for example: IP address, host name, MAC Address etc.;
Step 9012, NM server are kept at this locality with the deployment information that returns; Mainly be in the process of convenient upgrading subsystem software, whether relatively more local deployment configuration information is consistent with the deployment configuration information of obtaining, and promptly whether the subsystem disposed of the subsystem of the current NM server association in the deployment information that relatively obtains of NM server and current NM server is consistent;
Step 9013, NM server are determined this machine subsystem identification information to be disposed (subsystem tabulation) according to the relevant deployment information of current NM server;
Step 9014, NM server send the request message that carries the subsystem file access path information corresponding with this subsystem identification information;
Step 9015, deployment server obtain corresponding subsystem software under this path according to the file access routing information in the request message of receiving;
Step 9016, deployment server return the acquisition subsystem software;
There are local cache in step 9017, NM server with the subsystem software of returning;
Step 9018, NM server start the subsystem software in the local cache.
Introduce the different execution modes of step 9010 respectively below in conjunction with Figure 12-14:
As shown in figure 12 for the embodiment of the invention one obtain the interaction diagrams of deployment information from deployment server, wherein deposited full dose deployment information file in the deployment server, comprising:
Step 1310, NM server send a request message, and to download full dose deployment information file, wherein comprise the equipment identification information (optionally) and the full dose deployment information file access routing information of this NM server in this request message;
When carrying equipment identification information in the request message in the step 1310, deployment server is according to carrying out security inspection from the equipment identification information in the request message of NM server, and promptly whether deployment server (for example: download subsystem software) determines whether allowing deployment information file and other file according to request end IP in subsystem distribution deployment information.
Step 1311, deployment server obtain full dose deployment information file corresponding under this path according to the file access routing information in the request message of receiving;
Step 1312, deployment server return this full dose deployment information file;
Step 1313, NM server are searched according to the equipment identification information of this NM server and to be obtained the relevant deployment information of current NM server from the full dose deployment information file that obtains;
As shown in figure 13 for the embodiment of the invention two obtain the interaction diagrams of deployment information from deployment server, wherein deposit the deployment information of all NM servers of storage in full dose deployment information file or the database in the deployment server, comprising:
Step 1410, NM server send a request message, and to download the relevant deployment information of this machine, comprise the equipment identification information of this NM server in this request message;
Step 1411, deployment server are searched according to the equipment identification information that comprises in this request message and are obtained the deployment information relevant with this NM server;
Step 1412, deployment server return the response message that includes the relevant deployment information of this NM server;
Step 1413, NM server obtain the relevant deployment information of this machine from this response message.
Obtain the interaction diagrams of deployment information for the embodiment of the invention three from deployment server as shown in figure 14, wherein store a plurality of deployment information files in the deployment server, the NM server that different deployment information files is corresponding different respectively, the deployment information that is about to each NM server leaves in the unique file, comprising:
Step 1510, NM server send a request message, to download the relevant deployment information file of this machine, wherein comprise the equipment identification information (optionally) and the deployment information file access routing information of NM server in this request message, the deployment information file access routing information here is the access path information of the deployment information file of current NM server correspondence;
When carrying equipment identification information in the request message in the step 1510, deployment server is according to carrying out security inspection from the equipment identification information in the request message of NM server, and promptly whether deployment server (for example: download subsystem software) determines whether allowing deployment information file and other file according to request end IP in subsystem distribution deployment information.
Step 1511, deployment server obtain deployment information file corresponding under this path according to the file access routing information in the request message of receiving;
Step 1512, deployment server return this deployment information file;
Step 1513, NM server directly obtain all relevant deployment informations of this machine from this deployment information file.
When network management system need be upgraded or during patch installing, the keeper can upgrade partial document on deployment server, and the subsystem version information in the modification deployment information file, perhaps, the subsystem of adjusting as required on each NM server of network management system distributes, this step can be manually to finish or finished by upgrading tool, this moment, network management system entered attitude to be upgraded, inconsistent on software in the local cache on the NM server and the non-uniformity of software versions on the deployment server or software in the local cache and the deployment server to software that should NM server distributed, the deployment configuration information of each NM server by regularly obtaining up-to-date deployment configuration information and this machine of inspection whether with obtain consistent, whether need to carry out synchronously with decision.This has just related to run mode---〉attitude to be updated---〉process of run mode, below in conjunction with Figure 11 upgrade method is described, and as shown in figure 11, the upgrade method of the embodiment of the invention comprises:
Step 1010, NM server and deployment server are mutual, regularly obtain up-to-date deployment configuration information;
Here, obtaining up-to-date deployment configuration information can be to download from deployment server to dispose message file;
Step 1011, NM server check whether the deployment configuration information of this machine is consistent with the deployment configuration information of obtaining, when inconsistent, and execution in step 1012; When unanimity, this process finishes, and waits for that next timer triggers;
When in the process that this machine software is installed first, the deployment information that NM server is relevant with this machine of current acquisition is preserved with file, and in escalation process, adopt the mode of previous embodiment three to go to obtain to dispose message file (with reference to Figure 14), whether the deployment configuration information of this machine of inspection here consistent with the deployment configuration information of obtaining can be check deployment information file that this organizational security deposits whether with the deployment information file unanimity of obtaining.
Step 1012, stop disposing on this machine all subsystems of (installation);
Step 1013, request download section are deployed on this machine and determine inconsistent subsystem software;
Step 1014, deployment server return the subsystem software of renewal;
Step 1015, NM server are kept at local cache with the subsystem software of upgrading, and start all subsystem software in the local cache; This NM server enters run mode once more.
Further be presented in the escalation process NM server below from the process of deployment server file in download, should be understood that: under one embodiment of the present invention, can adopt deployment configuration information and/or subsystem software are kept in the deployment server with file, so obtain file after deployment configuration information after the renewal and/or subsystem software just can be understood as down loading updating;
Be the interaction diagrams of the employing http protocol of the embodiment of the invention as shown in figure 15, be applicable to escalation process, comprising from the deployment server file in download:
Step 1110, NM server send the HTTP request, with file in download, wherein comprise the file identification information and the corresponding file access routing information of this document of file in this NM server local cache in this HTTP request;
The file here can be the deployment information file, also can be the file (being subsystem file) at subsystem software place, and above-mentioned modification time can also adopt check codes such as MD5; The file identification information here, for example check codes such as the last modification time of file, MD5.
Step 1111, deployment server receive this HTTP request, whether the file identification information of judging the corresponding document that carries in this request is consistent with the file identification information of the corresponding document of this machine storage, when file identification information is consistent, directly return success, need not transmit corresponding file content, process ends; Otherwise, obtain corresponding file according to the file access routing information that comprises in this request, and execution in step 1112;
Under a kind of implementation, judge whether the last modification time of the corresponding document that carries in this request is consistent with the modification time of the corresponding document of this machine storage, when modification time is consistent, directly return success, need not transmit corresponding file content; Otherwise, obtain corresponding file according to the file access routing information that comprises in this request, and carry out next step;
For example: in request, carry the last modification time of subsystem file A, judge promptly whether the last modification time of subsystem file A is consistent with the modification time of the subsystem file A of this machine of deployment server storage.
Step 1112, deployment server return corresponding file;
Step 1113, NM server are kept at the file of receiving in the local cache.
Therefore above-mentioned process can make the file of NM server local cache and the file on the deployment server synchronous efficiently, and can not download duplicate file.File upgrades to be finished, and starts the subsystem of this machine of NM server once more, and NM server enters run mode once more.
In order better to understand in escalation process NM server from the process of deployment server file in download, be example to adopt non-http protocol file in download more below, agreements such as FTP, SFTP, NFS for example, for convenience of description, in the present embodiment be that example is described with the File Transfer Protocol, as shown in figure 16, be the employing File Transfer Protocol of the embodiment of the invention interaction diagrams, comprise from the deployment server file in download:
Step 1210, NM server send the FTP inquiry request message, to obtain the file details on the deployment server;
Step 1211, deployment server return the FTP response message, wherein comprise file identification information in this response message, for example: the last modification time of file;
Whether the file identification information of file is consistent with the file identification information of returning in step 1213, the NM server comparison local cache, when file identification information is consistent, returns and downloads successfully, process ends; Otherwise, execution in step 1214;
Under a kind of implementation, whether the last modification time of file is consistent with the last modification time of the file that returns in the NM server comparison local cache, when modification time is consistent, returns and downloads successfully, process ends; Otherwise, carry out next step;
Step 1214, NM server send the request message of FTP file in download, wherein, and the access path information of the inconsistent file of include file identification information in this request message;
Under a kind of implementation, comprise the access path information of the inconsistent file of last modification time in this request message;
Step 1215, deployment server are obtained corresponding document under this path according to the file access routing information in this request message;
Step 1216, deployment server return corresponding file;
Step 1217, NM server are kept at the file that returns in the local cache.
Should be understood that: adopt the process of other non-http protocol file in download identical with said process.
By the embodiment of the invention as can be known, by adopting the mode that pulls down file from deployment server to realize automatic installation, deployment, the upgrading of subsystem software, thereby improve the maintainability of distribution type network management system, improved maintenance efficiency, reduce the maintenance cost of distribution type network management system, administrator just specifies is wanted single-point upgrading, patch installing, and each NM server that distributes is finished the process of installation, deployment, upgrading, patch installing automatically;
And, by adopting the embodiment of the invention, avoided existing based on the authority of in the distributed deployment scheme of push-model every NM server being developed Long-distance Control to main control computer, the problem of the poor stability that is caused, and running status, the network connection having avoided having now based on requirement each NM server in deployment in the distributed deployment scheme of push-model must be normal, the problem of the poor reliability of being brought, thus the fail safe and the reliability of distribution type network management system improved.
One of ordinary skill in the art will appreciate that and realize installing in the foregoing description method and/or the process of upgrading can be finished by the relevant hardware of program command, described program can be stored in the read/write memory medium of network management system or call center, and this program is carried out the corresponding step in the said method when carrying out.Described storage medium can be as ROM/RAM, magnetic disc, CD etc.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.All any modifications of being done within the spirit and principles in the present invention, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (15)
1. a distributed network management system is characterized in that, comprising: deployment server and at least one NM server,
Described NM server, be used for obtaining the deployment information relevant with this machine from described deployment server, determine to wait to be deployed in the subsystem identification information of current NM server according to described deployment information, and, start described subsystem software from described deployment server acquisition and corresponding subsystem software of described subsystem identification information and preservation;
Described deployment server is used to store the subsystem software and the subsystem distribution deployment information of all subsystems of distribution type network management system.
2. according to power 1 described system, it is characterized in that, described NM server, also be used for when determining that subsystem software that current NM server has been disposed the subsystem software related with current NM server on the deployment server is inconsistent, subsystem software after described deployment server acquisition renewal is also preserved, and restarts described subsystem software.
3. a NM server is applied to distributed network management system, it is characterized in that, comprising:
Information transmission modular, be used to send the request message that obtains deployment information, and receive return with described request message corresponding response information, obtain the deployment information relevant by this response message, and obtain and described definite corresponding subsystem software of subsystem identification information to be disposed and preservation from deployment server with current NM server;
The management of process module is used for the subsystem software that described information transmission modular obtains is started;
Dispose administration module, be used to call described information transmission modular and obtain deployment information, determine the subsystem identification information that this machine is to be disposed according to the deployment information that described information transmission modular obtains, call described information transmission modular and obtain corresponding subsystem software, and after described information transmission modular obtains subsystem software, call described management of process module and start.
4. according to power 3 described NM servers, it is characterized in that, described deployment administration module is further used for, regularly calling described information transmission modular obtains deployment information, disposed the related subsystem of current NM server in the deployment information of subsystem and described information transmission modular acquisition when inconsistent determining this machine, call the subsystem software relevant after described information transmission modular obtains to upgrade, and call described management of process module and restart subsystem with current NM server;
Described information transmission modular is further used for obtaining the deployment information relevant with this machine from deployment server, and from the deployment server acquisition relevant with current NM server and renewal after subsystem software;
Described management of process module is further used for stopping the subsystem to have disposed on the current NM server, and starts the subsystem software after described information transmission modular obtains to upgrade.
5. according to power 3 described NM servers, it is characterized in that, described information transmission modular is a first information transport module, be used to send the 4th request message that carries full dose deployment information file access routing information, and receive the full dose file corresponding that returns with described the 4th request message, from described full dose file, search and obtain the relevant deployment information of current NM server; And, be used to send the 5th request message that carries current NM server subsystem identification information corresponding file access path information to be disposed, and receive subsystem software corresponding and the preservation of returning with described the 5th request message.
6. according to power 3 described NM servers, it is characterized in that, described information transmission modular is second information transmission modular, be used to send the 6th request message of the equipment identification information that carries current NM server, and receive the 6th response message that includes current NM server related deployment information that returns, from this response message, extract and obtain the relevant deployment information of current NM server; And, be used to send the 7th request message that carries current NM server subsystem identification information corresponding file access path information to be disposed, and receive subsystem software corresponding and the preservation of returning with described the 7th request message.
7. according to power 3 described NM servers, it is characterized in that, described information transmission modular is the 3rd information transmission modular, be used to send the 8th request message of the deployment information corresponding file access path information that carries current NM server, and receive the deployment information file corresponding that returns with described the 8th request message, from described deployment information file, obtain the relevant deployment information of current NM server; And, be used to send the 9th request message that carries current NM server subsystem identification information corresponding file access path information to be disposed, and receive subsystem software corresponding and the preservation of returning with described the 9th request message.
8. a NM server is characterized in that, is applied in the distribution type network management system, and other NM servers are communicated by letter with this NM server in this distribution type network management system, and this NM server comprises:
The subsystem loader, be used for obtaining the deployment information relevant with current NM server to described transmission service module request, determine to wait to be deployed in the subsystem identification information of current NM server according to the deployment information of described acquisition, and, the subsystem software of described acquisition is preserved and startup to described transmission service module request acquisition and the corresponding subsystem software of described subsystem identification information;
The transmission service module, the request message that is used for obtaining according to being used to of receiving deployment information returns and described request message corresponding response information, described response message comprises the deployment information relevant with requesting party's NM server, and obtain request message with the corresponding subsystem software of requesting party's NM server subsystem identification information according to being used to of receiving, return corresponding subsystem software.
9. according to power 8 described NM servers, it is characterized in that described NM server further comprises: store all subsystem software in this distribution type network management system, and the memory module of subsystem distribution deployment information;
Described transmission service module is the first transmission service module, be used to receive the request message that carries deployment information file access routing information, from this memory module, obtain corresponding deployment information file and return according to the deployment information file access routing information in this request message, and the request message that receives the subsystem file access path information carry requesting party's subsystem identification information correspondence, from this memory module, obtains the subsystem software of correspondence and return according to the subsystem file access path information in this request message.
10. according to power 8 described NM servers, it is characterized in that described NM server further comprises: store all subsystem software in this distribution type network management system, and the memory module of subsystem distribution deployment information;
Described transmission service module is the second transmission service module, be used to receive the request message that carries requesting party's equipment identification information, search from described memory module according to the equipment identification information in this request message and to obtain the deployment information relevant and to return the response message that comprises this deployment information with the requesting party, and the request message that receives the subsystem file access path information carry requesting party's subsystem identification information correspondence, obtain corresponding subsystem software and return from described memory module according to the subsystem file access path information in this request message.
11., it is characterized in that described subsystem loader comprises according to power 8 described NM servers:
The message transmission submodule, be used to ask described transmission service module to return and obtain the request corresponding response information of deployment information, obtain the deployment information relevant by this response message, and obtain with the described definite corresponding subsystem software of subsystem identification information to be disposed and preserve the subsystem software of described acquisition to transmission service module request with current NM server;
The management of process submodule is used for the subsystem software that described message transmission submodule obtains is started;
Dispose the management submodule, be used to call described message transmission submodule and obtain the deployment information relevant with current device, determine the subsystem identification information that this machine is to be disposed according to the deployment information that described message transmission submodule obtains, call described message transmission submodule and obtain subsystem software, and after described message transmission submodule obtains subsystem software, call described management of process submodule and start.
12. a distributed deployment method is characterized in that, is applied at least one NM server in the distributed network management system, wherein the subsystem mutual group on each NM server becomes distributed network management system, comprising:
Obtain the deployment information relevant with current NM server;
Determine the subsystem identification information that current NM server is to be disposed according to the deployment information of described acquisition;
The subsystem software corresponding with this subsystem identification information downloaded in request, receives and preserve the subsystem software of returning corresponding with this request;
Start described subsystem software.
13. according to power 12 described methods, it is characterized in that, described deployment information comprise subsystem identification information, equipment identification information, with the related information of corresponding subsystem version information,
Described deployment information according to described acquisition determines that the step of the subsystem identification information that current NM server is to be disposed comprises:
According to described related information, determine the subsystem identification information corresponding with the current device identification information, described subsystem identification information is current NM server subsystem identification information to be disposed.
14., it is characterized in that the step of the deployment information that described acquisition is relevant with current NM server comprises according to power 12 described methods:
Transmission carries the request message of full dose deployment information file access routing information, the full dose deployment information file corresponding that reception is returned with this request message, and search from this full dose deployment information file according to the equipment identification information of current NM server and to obtain the relevant deployment information of current NM server;
Perhaps, transmission carries the request message of the equipment identification information of current NM server, the response message that includes the deployment information relevant that reception is returned with current NM server, and from this response message, obtain the relevant deployment information of current NM server;
Perhaps, transmission carries the request message of the deployment information file access routing information of current NM server correspondence, the deployment information file corresponding with this request message that reception is returned obtains the relevant deployment information of current NM server from this deployment information file.
15., it is characterized in that described method further comprises according to power 12 described methods:
Regularly obtain up-to-date deployment information;
When determining that the subsystem of the current NM server association in the deployment information of described acquisition and the subsystem that current NM server has been disposed are inconsistent, stop the subsystem of having disposed on the current NM server;
The request download section is deployed on current NM server and determines inconsistent subsystem software, the subsystem software after the renewal corresponding with this request that reception and preservation are returned;
Start the subsystem software of described preservation.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008100662213A CN101267341A (en) | 2008-03-28 | 2008-03-28 | A distributed network management system, network management server and method |
| PCT/CN2009/070755 WO2009117921A1 (en) | 2008-03-28 | 2009-03-12 | Distributed network management system, network management server and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2008100662213A CN101267341A (en) | 2008-03-28 | 2008-03-28 | A distributed network management system, network management server and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101267341A true CN101267341A (en) | 2008-09-17 |
Family
ID=39989490
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2008100662213A Pending CN101267341A (en) | 2008-03-28 | 2008-03-28 | A distributed network management system, network management server and method |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101267341A (en) |
| WO (1) | WO2009117921A1 (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009117921A1 (en) * | 2008-03-28 | 2009-10-01 | 华为技术有限公司 | Distributed network management system, network management server and method |
| CN102769627A (en) * | 2012-07-26 | 2012-11-07 | 北京神州绿盟信息安全科技股份有限公司 | Configuration file synchronizing method and device |
| CN103067445A (en) * | 2012-12-06 | 2013-04-24 | 华为技术有限公司 | Method and device of software upgrading of distributed system |
| CN105306237A (en) * | 2014-06-26 | 2016-02-03 | 中兴通讯股份有限公司 | Distributed management method and device for network management |
| WO2016045392A1 (en) * | 2014-09-26 | 2016-03-31 | 华为技术有限公司 | Service deployment method, service management method and apparatus |
| CN106484443A (en) * | 2015-08-26 | 2017-03-08 | 中车大连电力牵引研发中心有限公司 | Train operation program renewing device and ground-based server |
| CN109426514A (en) * | 2017-08-24 | 2019-03-05 | 北京金山云网络技术有限公司 | Automatization of service dispositions method, device, electronic equipment and storage medium |
| CN110190997A (en) * | 2019-05-31 | 2019-08-30 | 深圳前海微众银行股份有限公司 | Configuration information obtaining method, device, equipment and computer readable storage medium |
| CN110806927A (en) * | 2019-10-15 | 2020-02-18 | 中国航空无线电电子研究所 | Software operation control method under distributed system |
| CN111274255A (en) * | 2020-01-20 | 2020-06-12 | 拉扎斯网络科技（上海）有限公司 | Service data monitoring method and system, monitoring architecture, equipment and storage medium |
| CN112099803A (en) * | 2020-07-30 | 2020-12-18 | 山东浪潮通软信息科技有限公司 | Incremental deployment method and system of ERP system |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103297477B (en) * | 2012-03-02 | 2016-03-02 | 腾讯科技（深圳）有限公司 | A kind of data acquisition reporting system and data processing method and proxy server |
| CN108616576B (en) * | 2018-04-08 | 2022-05-27 | 网宿科技股份有限公司 | Method and device for scheduling application server |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100754198B1 (en) * | 2005-12-12 | 2007-09-03 | 삼성전자주식회사 | Method for automatic software update and system thereof |
| CN1988469A (en) * | 2005-12-22 | 2007-06-27 | 华为技术有限公司 | Automatic managing software method and system |
| CN101141303A (en) * | 2007-09-24 | 2008-03-12 | 华为技术有限公司 | Client terminal updating method, server, client terminal of network management system |
| CN101267341A (en) * | 2008-03-28 | 2008-09-17 | 华为技术有限公司 | A distributed network management system, network management server and method |
-
2008
- 2008-03-28 CN CNA2008100662213A patent/CN101267341A/en active Pending
-
2009
- 2009-03-12 WO PCT/CN2009/070755 patent/WO2009117921A1/en active Application Filing
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009117921A1 (en) * | 2008-03-28 | 2009-10-01 | 华为技术有限公司 | Distributed network management system, network management server and method |
| CN102769627A (en) * | 2012-07-26 | 2012-11-07 | 北京神州绿盟信息安全科技股份有限公司 | Configuration file synchronizing method and device |
| CN102769627B (en) * | 2012-07-26 | 2015-06-17 | 北京神州绿盟信息安全科技股份有限公司 | Configuration file synchronizing method and device |
| CN103067445A (en) * | 2012-12-06 | 2013-04-24 | 华为技术有限公司 | Method and device of software upgrading of distributed system |
| CN103067445B (en) * | 2012-12-06 | 2015-07-08 | 华为技术有限公司 | Method and device of software upgrading of distributed system |
| CN105306237A (en) * | 2014-06-26 | 2016-02-03 | 中兴通讯股份有限公司 | Distributed management method and device for network management |
| WO2016045392A1 (en) * | 2014-09-26 | 2016-03-31 | 华为技术有限公司 | Service deployment method, service management method and apparatus |
| CN106484443A (en) * | 2015-08-26 | 2017-03-08 | 中车大连电力牵引研发中心有限公司 | Train operation program renewing device and ground-based server |
| CN106484443B (en) * | 2015-08-26 | 2020-04-24 | 中车大连电力牵引研发中心有限公司 | Train operation program updating device and ground server |
| CN109426514A (en) * | 2017-08-24 | 2019-03-05 | 北京金山云网络技术有限公司 | Automatization of service dispositions method, device, electronic equipment and storage medium |
| CN110190997A (en) * | 2019-05-31 | 2019-08-30 | 深圳前海微众银行股份有限公司 | Configuration information obtaining method, device, equipment and computer readable storage medium |
| CN110806927A (en) * | 2019-10-15 | 2020-02-18 | 中国航空无线电电子研究所 | Software operation control method under distributed system |
| CN111274255A (en) * | 2020-01-20 | 2020-06-12 | 拉扎斯网络科技（上海）有限公司 | Service data monitoring method and system, monitoring architecture, equipment and storage medium |
| CN112099803A (en) * | 2020-07-30 | 2020-12-18 | 山东浪潮通软信息科技有限公司 | Incremental deployment method and system of ERP system |
| CN112099803B (en) * | 2020-07-30 | 2024-04-12 | 浪潮通用软件有限公司 | Incremental deployment method and system of ERP system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2009117921A1 (en) | 2009-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101267341A (en) | A distributed network management system, network management server and method | |
| CN100361066C (en) | Method and arrangement for use of shared resources in a network | |
| JP3088269B2 (en) | Computer network system and operating system version management method | |
| RU2417416C2 (en) | Solution deployment in server farm | |
| EP1635257A2 (en) | System method and medium for configuring client computers to operate disconnected from a server computer while using a master instance of the operating system | |
| CN101751415B (en) | Metadata service system, metadata synchronized method and writing server updating method | |
| US20040260765A1 (en) | System and method for distribution of software licenses in a networked computing environment | |
| US20090225360A1 (en) | Information processing apparatus, servers,data processing method, and computer-readable storage medium | |
| KR102038527B1 (en) | Distributed cluster management system and method for thereof | |
| CN101739263A (en) | Method and device for realizing operating system update in multi-computer cluster system | |
| CN102479099A (en) | Virtual machine management system and use method thereof | |
| CN107688611B (en) | Saltstack-based Redis key value management system and method | |
| CN111190547B (en) | Distributed container mirror image storage and distribution system and method | |
| CN107357681A (en) | Zookeeper backup management systems and method based on salt | |
| CN111158752A (en) | SAAS multi-version control system and use method thereof | |
| CN111464603B (en) | Server capacity expansion method and system | |
| CN115150410A (en) | Multi-cluster access method and system | |
| CN104793981A (en) | Online snapshot managing method and device for virtual machine cluster | |
| CN112565475B (en) | Ip address allocation method for adding new node in container cluster service layer | |
| CN103164410B (en) | The method of the storage of a kind of file and operation, storage device and system | |
| CN110650033B (en) | Distributed application configuration management method and distributed computing system | |
| CN108650320B (en) | Method for synchronizing configuration files of isomorphic cascading equipment in cluster environment | |
| CN111124428A (en) | Application automatic publishing method based on middleware creating and related device | |
| CN114675893B (en) | Drive management method and device and computer equipment | |
| CN114327533B (en) | Method, device and equipment for upgrading uninterrupted service and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20080917 |