CN102014002B - Method and system for managing multiple kinds of network element equipment - Google Patents
Method and system for managing multiple kinds of network element equipment Download PDFInfo
- Publication number
- CN102014002B CN102014002B CN201010586002.5A CN201010586002A CN102014002B CN 102014002 B CN102014002 B CN 102014002B CN 201010586002 A CN201010586002 A CN 201010586002A CN 102014002 B CN102014002 B CN 102014002B
- Authority
- CN
- China
- Prior art keywords
- command request
- network element
- element device
- management service
- network management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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
-
- 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/045—Network management architectures or arrangements comprising client-server management architectures
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for managing multiple kinds of network element equipment. The method comprises the following steps that: a network management server numbers received command requests, stores the numbered command requests in command request queues corresponding to each piece of network element equipment to wait dispatching respectively; the network management server periodically dispatches the command requests in the command request queues and analyzes and transmits the command requests to the corresponding network element equipment; the network element equipment executes the operation of the command requests, returns an operation result and stores the operation result in the network management server; and the network management server returns an operation result to a network management client according to the demand of the network management client. The invention also discloses a system for managing the multiple kinds of network element equipment. Through the method and the system, the command requests aiming at the network element equipment are automatically dispatched by the network management server in a unified way; and the operation result can be purposely examined.
Description
Technical field
The present invention relates to the administrative skill of network element device, refer to a kind of management method and system of multiple network element device especially.
Background technology
In existing network management system, Operation and Maintenance can be carried out by the mode of order line or graphical interfaces to network element device.If by the mode of order line, the order line terminal that can directly be provided by network management system issues the manmachine command of arranging with network element device, realizes the Operation and Maintenance to network element device; If by the mode of graphical interfaces, operating personnel can safeguard the direct control of network element device according to the various functional realiey that graphical interfaces designs.The mode of graphical interfaces is less demanding for the professional knowledge of operating personnel, is conducive to operating personnel and carries out the various bookkeepings such as telecommunicatioin network management, user's service, post-sale support, thus achieve the every management function to a network element device.
But, also there is following shortcoming in aforesaid two kinds of modes: for the mode of order line, require that operating personnel skillfully must grasp manmachine command, and the order line terminal can only opened separately for a network element device is to perform manmachine command, if needs carry out the bookkeeping communicated for multiple network element device, need for each network element device repetitive operation; For the mode of graphical interfaces, operate after a network element device just needs to open multiple interface and could start to perform, and in reality, network management system manages hundreds of network elements usually, needs repetition many more manipulations.This shows, these two kinds of way to manages, for the management of multiple network element device, all need a large amount of manual operations, and for the ununified way to manage of result of operation, bring very large inconvenience to operating personnel.
Carry out bookkeeping for multiple network element device of the same type, comprise at existing patent documentation: number of patent application is the Chinese patent application " a kind of conflict management method to multiple similar network element and device " of 200710100313.4.Although propose the method for multiple similar network element being carried out to concurrent management in described patent documentation, wherein also have the following disadvantages:
One, the disposal ability of network element device is not considered.The action of network element device executable operations, normally order performs, and can avoid operating collision like this.When operating personnel's frequent operation or the operation of system automatic cycle, a large amount of task requests can be produced, if all send to network element device, message a large amount of on network element device certainly will be caused to pile up, be unfavorable for effective operation of network element device.Meanwhile, a large amount of message sends to network element device simultaneously, after network element device can be caused to return previous operating result, very fast again by Next operation amendment, and then constantly return operating result, easily make operating personnel produce and obscure, the state of current network equipment cannot be determined.
Two, the accumulation of a large amount of message of network management service is caused.The processing policy of message NM client being sent to network management service is not mentioned in described patent documentation.Network management service receives all task requests that NM client sends, if have accumulated a large amount of task requests to same network element device, the request needs wait continuing to receive NM client transmission for a long time could by network element device executable operations, and the bookkeeping of this undue delay has little significance for operating personnel.
Three, a large amount of command request can not get response for a long time.Refer in described patent documentation and send to NM client by network management service after bearing results, but due to first and second point problem mentioning before, cause and all may pile up a large amount of order on network management service and network element device, thus cause can not producing operating result for a long time, operating personnel can not get response for a long time on NM client.
Four, the influencing each other of different network elements equipment room.If NM client sends to the operational order of different network elements equipment to be stored together by network management service, obstruction may be created due to a large amount of command request mailing to some network element devices, and then the command request mailing to other network element devices cannot normally be sent, thus cause influencing each other of different network elements equipment room.
Summary of the invention
In view of this, main purpose of the present invention is the management method and the system that provide a kind of multiple network element device, when solving the multiple network element device of management, because network management service lacks scheduling to command request, network element device burden is strengthened, command request can not be effectively addressed, and operating personnel can not understand the problem of operating result targetedly.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention provides a kind of management method of multiple network element device, described method comprises:
Network management service is numbered the command request received, and the command request after numbering is saved in respectively in the command request queue of corresponding each network element device and waits for scheduling;
Command request in the queue of regular schedule command request, resolves and sends to corresponding network element device;
The operation of network element device fill order request, return operating result and be kept in network management service, network management service returns operating result according to the needs of NM client to it.
Wherein, described by numbering after command request be saved in command request queue, also comprise:
Receive the command request after numbering, if judge the command request do not processed, and the command request to be scheduled such as not, then the command request after numbering resolved and sent, otherwise judging whether the length of command request queue exceedes the length of regulation, if do not exceeded, then command request is saved in successively in command request queue, if exceeded, then ignore the command request after described numbering, and operating result is kept in network management service.
Wherein, in the process to be scheduled such as described, also comprise: start timer, work as timer expired, and etc. command request to be scheduled when not also being scheduled, delete described command request, and operating result be kept in network management service.
Wherein, command request in the queue of described regular schedule command request, resolves and sends to corresponding network element device, specifically according to the time cycle of presetting, regularly the command request being arranged in command request queue queue heads is recalled, resolve and send to corresponding network element device.
Wherein, described operating result comprises: the numbering of command request, corresponding network element device mark and object information.
Wherein, the described needs according to NM client return operating result to it, comprise: in the reading result request that network management service sends according to NM client, the numbering of the command request comprised, and/or network element device mark, and/or object information, retrieve and return operating result, or network management service is according to the tactful auto-returned operating result preset.
Present invention also offers a kind of management system of multiple network element device, described system comprises: NM client, network management service and network element device, wherein,
Described NM client, for command request is sent to network management service, display operating result;
Described network management service, for being numbered the command request received, command request after numbering is saved in the command request queue of corresponding each network element device respectively and waits for scheduling, command request in the queue of regular schedule command request, resolve and send to corresponding network element device, preserve operating result, the needs according to NM client return operating result to it;
Described network element device, for the operation of fill order request, returns operating result to network management service.
Wherein, described network management service, also for obtain number after command request after, if judge the command request do not processed, and the command request to be scheduled such as not, then the command request after numbering is resolved and sent, otherwise judge whether the length of command request queue exceedes the length of regulation, if do not exceeded, then command request is saved in successively in command request queue, if exceeded, then ignore the command request after described numbering, and operating result is kept in network management service.
Wherein, described network management service, also for, start timer when waiting for scheduling, work as timer expired, and etc. command request to be scheduled when not also being scheduled, delete described command request, and operating result be kept in network management service.
Wherein, command request in the queue of described network management service regular schedule command request, resolves and sends to corresponding network element device, specifically according to the time cycle of presetting, regularly the command request being arranged in command request queue queue heads is recalled, resolve and send to corresponding network element device.
The management method of multiple network element device provided by the present invention and system, be numbered the command request received by network management service, the command request after numbering is saved in respectively in the command request queue of corresponding each network element device and waits for scheduling; Command request in the queue of regular schedule command request, resolves and sends to corresponding network element device; The operation of network element device fill order request, return operating result and be kept in network management service, network management service returns operating result according to the needs of NM client to it.Make operating personnel only need shirtsleeve operation just to achieve concurrent management to multiple network element device, the command request unification for each network element device carries out automatic dispatching by network management service; And can check targetedly operating result.Wherein, method and system of the present invention breaches the thinking of single command request queue, for different network elements equipment opens up separately command request queue.When a network element device can be avoided like this to send command request obstruction, affect other network element device.
Further, the message queue quantity of each network element device is limited in method and system of the present invention, on the one hand a large amount of message can be avoided to pile up in network management service and network element device, on the other hand can alert as early as possible, avoid the wait that operating personnel are unnecessary.
Further, timing is carried out to sending command request each time in method and system of the present invention, make due to reasons such as network reason or network element device exceptions, the long-time situation about not responding caused is resolved, avoid waiting as long for of the waste of system resource and operating personnel, can also investigate as early as possible and be out of order, be conducive to operating personnel's management.
Accompanying drawing explanation
Fig. 1 is the basic structure schematic diagram of network element managing system;
Fig. 2 is the management method schematic flow sheet of a kind of multiple network element device of the present invention;
Fig. 3 is the management system structural representation of a kind of multiple network element device of the present invention;
Fig. 4 is the internal structure schematic diagram of network management service of the present invention.
Embodiment
For a better understanding of the present invention, first introduce the basic structure of existing network element managing system, Fig. 1 is the basic structure schematic diagram of network element managing system, as shown in Figure 1, described system comprises: NM client 11, network management service 12 and network element device 13, wherein
Described NM client 11, for command request is sent to network management service 12, display operating result;
Concrete, described NM client 11 is supplied to operating personnel patterned interface.By control and the input of operating personnel, according to the action need to network element device 13, generate command request, then command request is sent to network management service 12 by described NM client 11.Described NM client 11 receives the operating result of network management service 12, is shown to operating personnel.
Described network management service 12, for command request is sent to network element device 13, returns to networking client 11 by operating result;
Concrete, command request transmitted in parallel can be given multiple network element device 13 of the same type by described network management service 12.
Described network element device 13, for operating according to described command request, returns to network service end 12 by operating result.
Basic thought of the present invention is that network management service is numbered the command request received, and the command request after numbering is saved in respectively in the command request queue of corresponding each network element device and waits for scheduling; Command request in the queue of regular schedule command request, resolves and sends to corresponding network element device; The operation of network element device fill order request, return operating result and be kept in network management service, network management service returns operating result according to the needs of NM client to it.
Below in conjunction with the drawings and specific embodiments, the technical solution of the present invention is further elaborated.
Fig. 2 is the management method schematic flow sheet of a kind of multiple network element device of the present invention, and as shown in Figure 1, the management method of described network element device comprises the following steps:
Step 201, network management service is numbered the command request received, and the command request after numbering is saved in respectively in the command request queue of corresponding each network element device and waits for scheduling;
Concrete, described in the command request that receives sent by NM client, comprising: command request for the mark of one or more network element devices, and command messages parameter.When command request is for multiple network element device of the same type, command request builds in the mode of list, i.e. a corresponding multiple network element device mark of command messages parameter.Describedly the command request specifically received for each is numbered to command request distributes a task number, and task number is added in command request, obtain the command request after numbering.Further, while being added to by task number in command request, task number is returned to NM client.In order to when operating personnel need the operating result searched for certain command request, can be searched targetedly by task number.
The described command request queue being saved in corresponding each network element device, specifically according to the network element device mark in command request, is saved in command request in the command request queue of corresponding each network element device successively.Further, described by numbering after command request be saved in the process of command request queue, also comprise:
Step 201a, receives the command request after numbering, and whether judge currently has the command request processed, if not, performs step 201b, if had, performs step 201c;
Step 201b, judges command request to be scheduled such as whether having in command request queue, if had, then performs step 201c, if do not had, then resolves the command request after numbering and sends;
Step 201c, judge whether the length of command request queue exceedes the length of regulation, if do not exceeded, then command request is saved in successively in command request queue, if exceeded, then ignore the command request after described numbering, and will ignore operation be kept in network management service as operating result.
Concrete, described operating result comprises: the numbering of command request, corresponding network element device mark and object information, now object information is for ignoring operation.
Further, described step 201 etc. in process to be scheduled, also comprise: start timer, work as timer expired, and etc. command request to be scheduled when not also being scheduled, delete described command request, and deletion action be kept in network management service as operating result.
Concrete described operating result comprises: the numbering of command request, corresponding network element device mark and object information, now object information is deletion action.
Step 202, the command request in the queue of regular schedule command request, resolves and sends to corresponding network element device;
Concrete, command request in the queue of described regular schedule command request, resolves and sends to corresponding network element device, specifically according to the time cycle of presetting, regularly the command request being arranged in command request queue queue heads is recalled, resolve and send to corresponding network element device.Wherein, the time cycle of presetting can be set as the average time that command request is resolved and sent, or sets according to the disposal ability of system.Have if current and resolving and the command request sent, then do not dispatch.Describedly send to corresponding network element device specifically by the command request transmitter transmitted in parallel of each network element device of correspondence.
Step 203, the operation of network element device fill order request, return operating result and be kept in network management service, the needs according to NM client return operating result to it.
Concrete, described operating result comprises: the numbering of command request, corresponding network element device mark and object information, now object information is the result of network element device.The described needs according to NM client return operating result to it, comprise: in the reading result request that network management service sends according to NM client, the numbering of the command request comprised, and/or network element device mark, and/or object information, retrieve and return operating result, or network management service is according to the tactful auto-returned operating result preset.Wherein, described default strategy is arranged network management service as required by NM client, and the strategy of setting is: according to the numbering of the command request of coupling, and/or network element device mark, and/or object information carries out retrieving and returning operating result.The described two kinds of modes returning operating result are such as: when operating personnel only need the operating result about network element device 1, the reading result request of the mark comprising network element device 1 can be sent, the all operations result that network management service then retrieves network element device 1 returns to networking client, also the mark of network element device 1 can be set to the strategy returning operating result, network management service then according to strategy by all operations result auto-returned of network element device 1 to networking client; When operating personnel need about network element device 1 for be numbered 8 the operating result of command request time, can send the mark that comprises network element device 1 and command request be numbered 8 the request of reading result, the operating result that network management service then retrieves No. 8 command request of network element device 1 returns to networking client, also the mark of network element device 1 and command request can be numbered 8, be set to the strategy returning operating result, the operating result of network element device 1 No. 8 command request is then returned to networking client according to strategy by network management service.
Fig. 3 is the management system structural representation of a kind of multiple network element device of the present invention, and as shown in Figure 3, the management system of described network element device comprises: NM client 31, network management service 32 and multiple network element device 33, wherein,
Described NM client 31, for command request is sent to network management service 32, display operating result;
Concrete, the command request that described NM client 31 sends comprises: command request for the mark of one or more network element devices 33, and command messages parameter.When command request is for multiple network element device 33 of the same type, command request builds in the mode of list, i.e. a corresponding multiple network element device mark of command messages parameter.
Described network management service 32, for being numbered the command request received, command request after numbering is saved in the command request queue of corresponding each network element device respectively and waits for scheduling, command request in the queue of regular schedule command request, resolve and send to corresponding network element device 33, preserve operating result, the needs according to NM client 31 return operating result to it;
Concrete, described network management service 32 pairs of command request are numbered the command request specifically received for each and distribute a task number, and add in command request by task number, obtain the command request after numbering.Further, while being added to by task number in command request, task number is returned to NM client 31.In order to when operating personnel need the operating result searched for certain command request, can be searched targetedly by task number.The described command request queue being saved in corresponding each network element device, specifically according to the network element device mark in command request, is saved in command request in the command request queue of corresponding each network element device 33 successively.
Further, described network management service 32, also for the command request after numbering is saved in the process of command request queue, namely after obtaining the command request after numbering, if judge the command request do not processed, and the command request to be scheduled such as not, then the command request after numbering is resolved and sent, otherwise judge whether the length of command request queue exceedes the length of regulation, if do not exceeded, then command request is saved in successively in command request queue, if exceeded, then ignore the command request after described numbering, and will ignore operation be kept in network management service 32 as operating result.Wherein, described operating result comprises: the numbering of command request, corresponding network element device mark and object information, now object information is for ignoring operation.Further, in the processes to be scheduled such as described network management service 32, also for, start timer, work as timer expired, and etc. command request to be scheduled when not also being scheduled, delete described command request, and deletion action is kept in network management service 32 as operating result.Wherein, described operating result comprises: the numbering of command request, corresponding network element device mark and object information, now object information is deletion action.
Command request in the queue of described network management service 32 regular schedule command request, resolve and send to corresponding network element device, specifically according to the time cycle of presetting, regularly the command request being arranged in command request queue queue heads is recalled, resolve and send to corresponding network element device 33.Wherein, the time cycle of presetting can be set as the average time that command request is resolved and sent, or sets according to the disposal ability of system.Have if current and resolving and the command request sent, then do not dispatch.Describedly send to corresponding network element device 33 specifically by the command request transmitter transmitted in parallel of each network element device of correspondence.
The described needs according to NM client 31 return operating result to it, comprise: in the reading result request that network management service 32 sends according to NM client 31, the numbering of the command request comprised, and/or network element device mark, and/or object information, retrieve and return operating result, or network management service 32 is according to the tactful auto-returned operating result preset.Wherein, described default strategy is arranged network management service 32 as required by NM client 31, the strategy arranged is: according to the numbering of the command request of coupling, and/or network element device mark, and/or object information carries out retrieving and returning operating result.
Described network element device 33, for the operation of fill order request, returns operating result to network management service 32.
Concrete, described operating result comprises: the numbering of command request, corresponding network element device mark and object information, now object information is the result of network element device.
Fig. 4 is the internal structure schematic diagram of network management service of the present invention, as shown in Figure 4, also comprise in described network management service 32: command request distributor 321, logic reader 322, command request scheduler 323, command request transmitter 324 and operating result storage pool 325, wherein
Described command request distributor 321, for being numbered the command request received, being saved in the command request after numbering respectively in the logic reader 322 of corresponding each network element device 33 and waiting for scheduling;
Concrete, described command request distributor 321 pairs of command request are numbered the command request specifically received for each and distribute a task number, and add in command request by task number, obtain the command request after numbering.Further, while being added to by task number in command request, task number is returned to NM client 31.In order to when operating personnel need the operating result searched for certain command request, can be searched targetedly by task number.Describedly be saved in the logic reader 322 of corresponding each network element device 33, specifically according to the network element device mark in command request, command request be saved in successively in the logic reader 322 of corresponding each network element device 33.
Described logic reader 322, for preserving the command request queue of corresponding each network element device 33 and currently resolving and the command request sent;
Concrete, network management service 32 comprises one or more logic reader 322, for two logic readers 322 in the present embodiment, the corresponding network element device 33 of each logic reader 322, and described logic reader 322 comprises: command request Queue module 41 and the current command request module 42.Described command request Queue module 41 possesses the length of regulation, namely can only preserve the command request of some.Current parsing and the command request sent is saved in described the current command request module 42.
Further, described logic reader 322, also for receiving the command request after numbering, if judge there is no command request in described the current command request module 42, and the command request to be scheduled such as not in described command request Queue module 41, then the command request after numbering is saved in the current command request module 42 and carries out resolving and sending, otherwise judge whether the length of the medium command request queue to be scheduled of command request Queue module 41 exceedes the length of regulation, if do not exceeded, then command request is saved in successively in command request queue, if exceeded, then ignore the command request after described numbering, and will ignore operation be saved in operating result storage pool 325 as operating result.Wherein, described operating result comprises: the numbering of command request, corresponding network element device mark and object information, now object information is for ignoring operation.In the processes to be scheduled such as described logic reader 322, also comprise: start timer, work as timer expired, and etc. command request to be scheduled when not also being scheduled, delete described command request, and deletion action is saved in operating result storage pool 325 as operating result.Wherein, described operating result comprises: the numbering of command request, corresponding network element device mark and object information, now object information is deletion action.
Described command request scheduler 323, for the command request in regular schedule logic reader 322, resolves command request and sends to command request transmitter 324;
Concrete, command request in described command request scheduler 323 regular schedule logic reader 322, command request is resolved and sends to command request transmitter 324, specifically according to the time cycle of presetting, regularly the command request being arranged in command request Queue module 41 queue heads is recalled, be saved in the current command request module 42 and command request scheduler 323, and command request resolved and sends to command request transmitter 324.Wherein, the time cycle of presetting can be set as the average time that command request is resolved and sent, or sets according to the disposal ability of system.Resolving and the command request sent if existing in the current command request module 42, then do not dispatching.
Described command request transmitter 324, for sending to corresponding network element device 33 by the command request after parsing;
Concrete, described in send to corresponding network element device 33 specifically by command request transmitter 324 transmitted in parallel of each network element device of correspondence.
Described operating result storage pool 325, for preserving operating result, the needs according to NM client 31 return operating result to it.
Concrete, described operating result storage pool 325 returns operating result according to the needs of NM client 31 to it, comprise: in the reading result request that described operating result storage pool 325 sends according to NM client 31, the numbering of the command request comprised, and/or network element device mark, and/or object information, retrieve and return operating result, or described operating result storage pool 325 is according to the tactful auto-returned operating result preset.Wherein, described default strategy is arranged described operating result storage pool 325 as required by NM client 31, the strategy arranged is: according to the numbering of the command request of coupling, and/or network element device mark, and/or object information carries out retrieving and returning operating result.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention, and all any amendments done within the spirit and principles in the present invention, equivalent replacement and improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a management method for multiple network element device, is characterized in that, described method comprises:
Network management service is numbered the command request received, and the command request after numbering is saved in respectively in the command request queue of corresponding each network element device and waits for scheduling, described numbering is returned to NM client simultaneously;
Command request in the queue of regular schedule command request, resolves and sends to corresponding network element device;
The operation of network element device fill order request, return operating result and be kept in network management service, network management service returns operating result according to the needs of NM client to it.
2. method according to claim 1, is characterized in that, described by numbering after command request be saved in command request queue, also comprise:
Receive the command request after numbering, if judge the command request do not processed, and the command request to be scheduled such as not, then the command request after numbering resolved and sent, otherwise judging whether the length of command request queue exceedes the length of regulation, if do not exceeded, then command request is saved in successively in command request queue, if exceeded, then ignore the command request after described numbering, and operating result is kept in network management service.
3. in the processes to be scheduled such as method according to claim 1 and 2, is characterized in that, described, also comprise: start timer, work as timer expired, and etc. command request to be scheduled when not also being scheduled, delete described command request, and operating result is kept in network management service.
4. method according to claim 1 and 2, it is characterized in that, command request in the queue of described regular schedule command request, resolve and send to corresponding network element device, specifically according to the time cycle of presetting, regularly the command request being arranged in command request queue queue heads is recalled, resolve and send to corresponding network element device.
5. method according to claim 1 and 2, is characterized in that, described operating result comprises: the numbering of command request, corresponding network element device mark and object information.
6. method according to claim 5, it is characterized in that, the described needs according to NM client return operating result to it, comprise: in the reading result request that network management service sends according to NM client, the numbering of the command request comprised, and/or network element device mark, and/or object information, retrieve and return operating result, or network management service is according to the tactful auto-returned operating result preset.
7. a management system for multiple network element device, is characterized in that, described system comprises: NM client, network management service and network element device, wherein,
Described NM client, for command request is sent to network management service, display operating result;
Described network management service, for being numbered the command request received, command request after numbering is saved in the command request queue of corresponding each network element device respectively and waits for scheduling, described numbering is returned to NM client simultaneously, command request in the queue of regular schedule command request, resolve and send to corresponding network element device, preserve operating result, the needs according to NM client return operating result to it;
Described network element device, for the operation of fill order request, returns operating result to network management service.
8. system according to claim 7, it is characterized in that, described network management service, also for obtain number after command request after, if judge the command request do not processed, and the command request to be scheduled such as not, then the command request after numbering is resolved and sent, otherwise judge whether the length of command request queue exceedes the length of regulation, if do not exceeded, then command request is saved in command request queue successively, if exceeded, then ignore the command request after described numbering, and operating result is kept in network management service.
9. the system according to claim 7 or 8, it is characterized in that, described network management service, also for, start timer when waiting for scheduling, work as timer expired, and etc. command request to be scheduled when not also being scheduled, delete described command request, and operating result is kept in network management service.
10. the system according to claim 7 or 8, it is characterized in that, command request in the queue of described network management service regular schedule command request, resolve and send to corresponding network element device, specifically according to the time cycle of presetting, regularly the command request being arranged in command request queue queue heads is recalled, resolve and send to corresponding network element device.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010586002.5A CN102014002B (en) | 2010-12-13 | 2010-12-13 | Method and system for managing multiple kinds of network element equipment |
| PCT/CN2011/075707 WO2012079352A1 (en) | 2010-12-13 | 2011-06-14 | Method and system for managing multiple network element devices |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010586002.5A CN102014002B (en) | 2010-12-13 | 2010-12-13 | Method and system for managing multiple kinds of network element equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102014002A CN102014002A (en) | 2011-04-13 |
| CN102014002B true CN102014002B (en) | 2015-06-03 |
Family
ID=43844030
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010586002.5A Active CN102014002B (en) | 2010-12-13 | 2010-12-13 | Method and system for managing multiple kinds of network element equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102014002B (en) |
| WO (1) | WO2012079352A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102014002B (en) * | 2010-12-13 | 2015-06-03 | 中兴通讯股份有限公司 | Method and system for managing multiple kinds of network element equipment |
| WO2015180761A1 (en) * | 2014-05-27 | 2015-12-03 | Telecom Italia S.P.A. | System and method for network apparatus management |
| CN105049240B (en) * | 2015-06-26 | 2018-08-21 | 大唐移动通信设备有限公司 | A kind of message treatment method and server |
| CN106850245B (en) * | 2015-12-07 | 2020-12-29 | 中兴通讯股份有限公司 | Diagnostic test message processing method and device |
| CN111522511B (en) * | 2020-04-22 | 2022-04-22 | 杭州宏杉科技股份有限公司 | Command processing method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101060437A (en) * | 2007-06-07 | 2007-10-24 | 中兴通讯股份有限公司 | A parallel management method and device for several same types of network elements |
| CN101060559A (en) * | 2007-05-29 | 2007-10-24 | 中兴通讯股份有限公司 | A man-machine command queue management system and method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102014002B (en) * | 2010-12-13 | 2015-06-03 | 中兴通讯股份有限公司 | Method and system for managing multiple kinds of network element equipment |
-
2010
- 2010-12-13 CN CN201010586002.5A patent/CN102014002B/en active Active
-
2011
- 2011-06-14 WO PCT/CN2011/075707 patent/WO2012079352A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101060559A (en) * | 2007-05-29 | 2007-10-24 | 中兴通讯股份有限公司 | A man-machine command queue management system and method |
| CN101060437A (en) * | 2007-06-07 | 2007-10-24 | 中兴通讯股份有限公司 | A parallel management method and device for several same types of network elements |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102014002A (en) | 2011-04-13 |
| WO2012079352A1 (en) | 2012-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102014002B (en) | Method and system for managing multiple kinds of network element equipment | |
| CN101211277B (en) | Method of selecting one of execution schedules of guest OS and virtual machine monitor employing the method | |
| CN100477602C (en) | A method for realizing the multi-task polling in the network management monitoring system | |
| CN100547420C (en) | Reliable multicast communication | |
| CN101951411A (en) | Cloud scheduling system and method and multistage cloud scheduling system | |
| KR101416280B1 (en) | Event handling system and method | |
| CN100411365C (en) | Method for monitoring and maintaining multi-data link | |
| CN1817014A (en) | System for defining an alternate channel routing mechanism in a messaging middleware environment | |
| CN101741746B (en) | Method for realizing communication between two-way CAS gateway and user terminal based on IOCP | |
| CN114567519B (en) | Method and device for managing instruction messages of multiple intelligent devices in multithreading parallel | |
| CN110851248A (en) | Asynchronous task data processing method and device and computer readable storage medium | |
| CN101594621A (en) | The energy-saving control device of network system | |
| CN101374077A (en) | Method and system for forwarding network management alarm | |
| CN102236340A (en) | Multi-equipment management method and device | |
| WO2016193118A1 (en) | Load balancing server for forwarding prioritized traffic from and to one or more prioritized auto-configuration servers | |
| CN111722944B (en) | NIO-based AIRT-ROS communication method and system | |
| CN101321123A (en) | System and method for embedded type transmission of dynamic data | |
| CN104580209A (en) | Device and method for implementing multi-platform message processing | |
| CN102420783B (en) | Method and system for transmitting information to control terminal by server | |
| CN109818977A (en) | A kind of access server communication optimization method, access server and communication system | |
| CN107329842B (en) | Method and terminal for acquiring data based on Qt signal slot mechanism | |
| CN108462650B (en) | Output unit based on TTE switch | |
| CN101511098B (en) | Distributed net element task management system and method | |
| CN104348713A (en) | Instant messaging method based on comet of network platform under B/S (Browser/Server) architecture | |
| CN104240049A (en) | Comprehensive order handling platform |
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 | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20160914 Address after: 300308 Tianjin Airport Economic Zone, Binhai New Area seven East Road No. 2 Zhongxing Industrial Base Patentee after: ZTE INTELLIGENT IOT TECHNOLOGY Co.,Ltd. Address before: 518057 Nanshan District Guangdong high tech Industrial Park, South Road, science and technology, ZTE building, Ministry of Justice Patentee before: ZTE Corp. |
|
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: Room 401, building 12, east area, airport business park, No. 80, Huanhe North Road, free trade zone (Airport Economic Zone), Binhai New Area, Tianjin 300000 Patentee after: Gaoxing Zhilian Technology Co.,Ltd. Address before: 300308, Zhongxing Industrial base, 2 East seven, Airport Economic Zone, Tianjin Binhai New Area Patentee before: ZTE INTELLIGENT IOT TECHNOLOGY Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: Room 401, building 12, East Airport Business Park, 80 Huanhe North Road, Tianjin Binhai New Area pilot free trade zone (Airport Economic Zone) Patentee after: Zte Intelligent Iot Technology Co.,Ltd. Address before: Room 401, building 12, East Airport Business Park, 80 Huanhe North Road, Tianjin Binhai New Area pilot free trade zone (Airport Economic Zone) Patentee before: Gaoxing Zhilian Technology Co.,Ltd. |