WO2012155642A1

WO2012155642A1 - Method and device for scheduling batch operation using restricted resources

Info

Publication number: WO2012155642A1
Application number: PCT/CN2012/072555
Authority: WO
Inventors: 孟英
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-07-21
Filing date: 2012-03-19
Publication date: 2012-11-22
Also published as: CN102891806B; CN102891806A

Abstract

Disclosed are a method and device for scheduling a batch operation using restricted resources. The method comprises: upon receiving a command message comprising a network element identifier and sent by a network management client, a request receiver sending the command message to a command message distributor; the command message distributor allocating the command message to a corresponding logic reader; the logic reader determining whether the command message is a restricted resource message, and if the command message is a restricted resource message, the logic reader applying for a resource token from a resource token pool for the command message, and after the application succeeds, sending the command message to a command message scheduler; and the command message scheduler sending the command message to a corresponding network element device through a command message sender. In the present invention, various command messages in a network management system are classified according to the principle of whether restricted resources are used, and different scheduling policies are used for different command messages, thereby implementing dynamic management of the restricted resources in the system.

Description

Scheduling method and device for batch operation using restricted resources

The present invention relates to a scheduling technique for large-scale messages in the field of network communications, and in particular, to a scheduling method and apparatus for batch operations using restricted resources. Background technique

In an existing network management system, multiple network elements of the same type can be operated in batches. For a large network management system, it is also possible to manage thousands of network element devices. For some operations, the message is simple and can operate on hundreds of network element devices at the same time. It is very convenient to use this network management system. However, for some special operation functions, some additional resources may be needed. When the resources are limited, it is impossible to simultaneously operate the same number of network element devices in batches. For example, the version download function of the existing network management system is performed by the network element device downloading the version file through the FTP (File Transfer Protocol) service in the network management system. Here, the maximum number of connections supported by the FTP server and the network bandwidth used for downloading are limited. It is impossible to simultaneously support hundreds of network element devices to simultaneously download versions. At the same time, because this operation is time consuming, its execution has a certain impact on other simple operations.

At present, the general scheduling policy only considers the processing capability of the network element device, and does not consider the available resources of the network management system. Bulk-operated messages are usually in one schedule, and operation requests are all sent. However, for a limited resource such as the number of network connections, network bandwidth, and central processing unit (CPU) utilization, it is impossible to use it without restriction. When such messages requiring these restricted resources are scheduled as such, , the request operation exceeding the resource capability range is executed, resulting in a decrease in the operation success rate.

In addition, the current general scheduling strategy assumes that the execution time of all operation requests is substantially the same, without considering that messages requiring restricted resources may be occupied for a long time due to resource constraints. Between. No specific analysis of the reason for the failure of the operation is caused by the problem of the network element device or due to the limited resources of the network management system.

In the case of such a batch operation requiring limited resources and time-consuming messages, it is currently common practice to limit the interface so that the operator can select only a small number of network element batch operations at a time. However, if this is the case, in an actual deployment or upgrade scenario, thousands of devices need to download the version, and each time an operator is required to be on duty, which requires hundreds of operations to complete, which is undoubtedly inefficient. Summary of the invention

It is an object of the present invention to provide a scheduling method and apparatus for batch operations using restricted resources, which solves the scheduling problem when ordinary messages and restricted resource messages coexist.

According to an aspect of the present invention, a scheduling method for a batch operation using a restricted resource is provided, the method comprising:

After receiving the command message including the network element identifier sent by the network management client, the request receiver sends the command message to the command message distributor;

The command message dispatcher assigns the command message to the corresponding logical reader;

The logic reader determines whether the command message is a restricted resource message. If the command message is a restricted resource message, the command message applies for a resource token to the resource token pool and sends the command message to the command message scheduler after the application is successful; as well as

The command message scheduler sends a command message to the corresponding network element device through the command message sender.

Preferably, the restricted resource message is a message that uses limited resources in the network.

Preferably, the command message distributor allocates the command message to the corresponding logical reader, and the method includes: the command message distributor obtains a logical reader corresponding to the command message according to the network element identifier;

If the message in the logical reader has a restricted resource message, the command message allocation fails, the result of the fast failure is created and stored in the operation result storage pool; and if the message in the logical reader If there is no restricted resource message, the command message is assigned to the logical reader.

Preferably, the logic reader applies for the resource token to the resource token pool for the command message, including: the task timer presets the timing time;

The logical reader applies for a resource token in the resource token pool for the command message at regular intervals. The logical reader records the number of failed application resource tokens. If the number of failures exceeds a fixed number of times, the application fails. Otherwise, the application succeeds.

Preferably, the logic reader requests a resource token for the command message from the resource token pool. If the application fails, the command message is not processed, and the result of the operation timeout is created and stored in the operation result storage pool.

Preferably, after the command message distributor allocates the command message to the corresponding logical reader, the method further includes: the logic reader determining whether the command message is a restricted resource message, and if the command message is not a restricted resource message, And the logic reader sends the command message to the command message scheduler; and the command message scheduler sends the command message to the corresponding network element device by using the command message sender.

Preferably, the method further includes: the operation result processor listening to the message sent to the network element device, and if the message sent to the network element device is a restricted resource message, informing the resource token pool to release the resource token occupied by the message.

According to another aspect of the present invention, there is provided a scheduling apparatus for a batch operation using a restricted resource, the apparatus comprising: a request receiver, a command message distributor, a logic reader, a resource token pool, a command message schedule , and command message sender; where

The request receiver is configured to receive a command message including the network element identifier sent by the network management client, and send the command message to the command message distributor;

a command message dispatcher, configured to receive a command message and assign the command message to a corresponding logical reader;

a logical reader, configured to determine whether the command message is a restricted resource message, and apply for a resource token to the resource token pool when the command message is a restricted resource message; a resource token pool, configured to allocate a resource token for the command message when the command message is a restricted resource message, and send the command message to the command message scheduler after the application is successful;

The command message scheduler is configured to send a command message to the control command message sender; the command message sender is configured to send the command message to the corresponding network element device.

Preferably, the device further comprises:

The operation result processor is configured to monitor the message sent to the network element device, and if the message sent to the network element device is a restricted resource message, notify the resource token pool to release the resource token occupied by the message.

Compared with the prior art, the present invention has the following advantages: The present invention classifies various command messages in the network management system according to the principle of whether to use restricted resources, and adopts different scheduling strategies for different command messages. The dynamic management of the limited resources in the system solves the practical problem that the number of limited resource messages in a single batch operation needs to be manually controlled, the success rate of the batch operation of the restricted resource message operation is low, and the normal message is generally timed out, and The result type of operation failure is refined, and it is easy to use for operator positioning problems. DRAWINGS

1 is a schematic flowchart of a scheduling method for a batch operation using a restricted resource according to the present invention; FIG. 1 is a schematic structural diagram of a scheduling apparatus for a batch operation using a restricted resource according to the present invention;

FIG. 3 is a flowchart of processing a command message scheduler according to an embodiment of the present invention;

4 is a process flowchart of an operation result processor according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of the operation of distributing a command message according to an embodiment of the present invention. detailed description

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings, The preferred embodiments illustrated are for illustrative purposes only and are not intended to limit the invention. As shown in FIG. 1 , the flow of the scheduling method for batch operations using restricted resources provided by the present invention may include the following steps:

Step S101: After receiving the command message including the network element identifier sent by the network management client, the request receiver sends the command message to the command message distributor.

Step S102, the command message distributor allocates the command message to the corresponding logical reader. The command message distributor obtains a logical reader corresponding to the command message according to the network element identifier in the command message, and if the current command message in the logical reader and the message in the command message queue have a restricted resource message, the command The message allocation fails, the command message distributor does not assign the command message to the logical reader, and the command message scheduler controls the logical reader to create a fast failed result and stores it through the operation result processor to the operation result storage pool; if the logical reader The current command message in the command message and the command message queue message do not have a restricted resource message, and the command message is assigned to the logical reader.

The restricted resource message is a message that uses limited resources in the network.

Step S103: The logic reader determines whether the command message is a restricted resource message. If the command message is a restricted resource message, the logic reader applies a resource token to the resource token pool for the command message and sends the command message after the application is successful. To the command message scheduler, if the command message is not a restricted resource message, the logic reader sends a command message to the command message scheduler via the command message distributor.

The logic reader processes the resource token for the resource token pool for the command message as follows: The task timer presets the timing time, and the logic reader applies for the resource token in the resource token pool for the command message every regular time. The logical reader records the number of failed application resource tokens. If the number of failures exceeds a preset fixed number of times, the application fails. Otherwise, the application is successful. If the application is successful, the logic reader sends the command message to the command message scheduler through the command message distributor. If the application fails, the command message is not processed, and the result of the operation timeout is created and stored to the operation. Result storage pool.

Step S104: The command message scheduler sends the command message to the corresponding network element device by using the command message sender.

In addition, the operation result processor monitors the message sent to the network element device. If the message sent to the network element device is a restricted resource message, the operation result processor notifies the resource token pool to release the resource token occupied by the message. The number of tokens in the resource token pool is fixed. If the logical reader requests a resource token from the resource token pool, the number of restricted resource messages in the command message currently being processed has reached the resource. If the number of tokens in the token pool is exceeded, the application fails. Otherwise, the application is successful.

The operation result processor sends all the operation results to the operation result storage pool, and the request receiver reads the operation result from the operation result storage pool according to the operation result request message sent by the network management client and sends the operation result to the network management client.

As shown in FIG. 1, the scheduling apparatus for batch operation using restricted resources provided by the present invention includes a network management client 101, a network management server 111, and a network element device 112.

The network management client 101 is configured to assemble a command message including the network element identifier and the operation identifier to the network management server 111. On the other hand, the network management client 101 periodically requests the operation result from the network management server 111, and displays the operation result. On the graphical interface. The network management server 111 is configured to process messages from the network management client 101 and the network element device 112. The network element device 112 receives the command message from the network management server 111, and is connected to the network management system, and is operated and managed by the network management system.

The network management server 111 includes:

The request receiver 102 is configured to receive a command message including the network element identifier sent by the network management client 101, and receive an operation result request message sent by the network management client 101, and return the operation result to the network management client 101.

The command message distributor 103 maintains a command message queue of the logical reader 104 in the network management system, and is configured to distribute the batch command message received by the request receiver 102 to different logical readers. 104 in the command message queue.

The logical reader 104 is configured to identify a virtual network element device in the management network management system, and the operation of the virtual network element device is stored in an internal command message queue.

The resource token pool 105 is set to control and manage the use of limited resources within the network management system. For example, determining whether the command message is a restricted resource message, and requesting the resource token from the resource token pool when the command message is a restricted resource message.

Command message scheduler 106, set to schedule command message, and start command message sender

107.

The command message sender 107 is arranged to send a command message to the network element device 112.

The operation result processor 108 is arranged to perform corresponding processing and to send the operation result to the operation result storage pool 109 when different types of operation results are generated. At the same time, the message sent to the network element device is monitored, and if the message sent to the network element device is a restricted resource message, the resource token pool is notified.

105 releases the resource token occupied by the message.

The operation result storage pool 109 is set to store the result of the operation of the command message.

The task timer 110 is configured to start timing when the logical reader 104 requests a resource token from the resource token pool 105. If the timeout period is reached, a response timeout result is generated, and the operation result is put into the operation result processor 108. Storage pool 109.

Referring to FIG. 2, the scheduling method for the batch operation using the restricted resource of the present invention includes the following steps:

Step S201: After receiving the command message list sent by the network management client 101, the request receiver 102 sends the command message list to the command message distributor 103.

Step S202: After receiving the command message list sent by the request receiver 102, the command message distributor 103 parses the network element identifier included in the command message one by one, and sends the command message to the corresponding logical reader 104 according to the network element identifier.

Step S203, the logic reader 104 receives the command sent by the command message distributor 103. After the message is placed, the command message is placed in the command message queue, and the task timer 110 is started to start timing.

Step S204, after the task timer 110 is started, the timing starts, and after the timeout period is reached, the generated operation result is given to the operation result processor 108 for logical processing.

Step S205, the command message scheduler 106 starts working when the system is started, and periodically retrieves whether there is a command message to be sent in the command message distributor 103.

Step S206, the command message distributor 103 loops through the current command message of the logical reader 104.

Step S207, the logic reader 104 determines whether the current command message is a restricted resource message, if yes, step S208 is performed, otherwise step S209 is performed.

Step S208, the logic reader 104 applies for resources to the resource token pool 105 and obtains a resource token.

Step S209, the logic reader 104 returns the current command message to the command message distributor.

103.

In step S210, the command message distributor 103 returns the command messages returned by all the logical readers 104 to the command message scheduler 106.

Step S211, the command message scheduler 106 schedules the command message in the logical reader 104, and starts the command message sender 107 to send the message.

Step S212, the command message sender 107 receives the command message sent by the command message scheduler 106, and sends a command message to the network element device 112 through the network.

In step S213, the operation result processor 108 determines whether the resource token is occupied when the newly generated operation result is received. If the resource token is occupied, step S214 is performed; otherwise, step S215 is performed.

Step S214, the resource token pool 105 releases the resource token occupied by the operation result for subsequent use by other applicants.

Step S215, the operation result processor 108 puts the operation result into the operation result storage pool 109. in.

Step S216, the request receiver 102 periodically retrieves the operation result from the operation storage pool 109, and returns it to the network management client 101 for display.

As shown in FIG. 3, the processing flow of the command message scheduler provided by the embodiment of the present invention specifically includes the following steps:

Step S301: After the request receiver receives the command message sent by the network management client, the process begins. Step S302, the command message distributor obtains the logical reader identifier according to the command message, determines whether the current command message of the logical reader and the message in the command message queue already have a restricted resource message, and if yes, executes step S315, otherwise, the step is performed. S303.

Step S303, the command message distributor adds the command message to the command message queue of the corresponding logical reader.

Step S304, the command message distributor starts the task timer and starts timing.

Step S305, the command message scheduler cyclically schedules the current command message in the logic reader by using the command message distributor.

Step S306, the command message scheduler determines whether the currently scheduled message is a restricted resource message, if yes, step S307 is performed, otherwise step S309 is performed.

Step S307, the command message scheduler applies for a resource token from the resource token pool.

Step S308: The resource token pool determines whether the application is successful according to the number of the remaining limited resources in the current system. If yes, step S309 is performed; otherwise, step S312 is performed.

Step S309, the logic reader's application resource token failure counter is cleared.

Step S310, the command message scheduler starts a command message sender, and sends a command message. Step S311, the command message scheduler creates a successful transmission result, and the process ends.

Step S312: If the application for the resource token fails, the logical resource reader's request resource token failure counter is incremented by one.

Step S313, the command message scheduler determines that the logical reader fails to apply for the resource token. Whether the number exceeds the limit, if yes, step S314 is performed, otherwise step S305 is returned, waiting for the next round to be scheduled again.

Step S314, the command message scheduler creates a result of the operation timeout, and the process ends.

Step S315, the command message scheduler creates a fast failed result, and the process ends.

As shown in FIG. 4, the processing flow of the operation result processor provided by the embodiment of the present invention includes the following steps:

Step S401: After the operation result processor receives different types of operation results generated by different timings of the system, the process starts.

Step S402, the operation result processor determines whether the operation result is a timeout result due to a timer arrival time point, and if yes, executes step S403, otherwise performs step S407.

Step S403, the operation result processor calls the logical reader corresponding to the operation result, and determines whether the timeout result generated by the timer corresponds to the current command message of the logical reader, and if yes, executes step S404, otherwise performs step S407. .

Step S404, the operation result processor determines whether the operation request corresponding to the operation result is a restricted resource message, if yes, step S405 is performed, otherwise step S407 is performed.

Step S405: The operation result processor determines whether the number of times the application resource token failure counter of the logic reader exceeds the limit by calling the logical reader corresponding to the operation result. If the limit is not exceeded, step S406 is performed; otherwise, step S407 is performed.

Step S406, the operation result processor starts a new timer by calling the logical reader corresponding to the operation result, and if a new timer task arrives at the time point, starts a new round of the loop processing operation result, and loops to step S401.

Step S407: Put the operation result into the operation result storage pool, and prepare to return to the network management client to be set to display.

Step S408, the operation result processor determines whether the current operation result occupies the resource token by calling the resource token pool, and if yes, executing step S409, otherwise the process ends. Step S409, the resource token pool releases the resource token occupied by the current operation result, so as to be used by other restricted resource messages.

As shown in FIG. 5, the working process of the distribution command message provided by the embodiment of the present invention is as follows: Command message distributor 103: All messages enter the portal of the network management system, and are assigned to the logical reader of the specific processing according to the network element identifier of the message. 104.

Logic Reader 104: Simulates a real network element device, corresponding to a physical network element. Responsible for managing and maintaining operational messages that are being sent and will be sent on this network element. It consists of a two-part structure, one is "current command message" and the other is "command message queue". The command message queue retrieves the message of the team head one by one, and is placed in the structure of the current command message to identify the command message currently being processed by the logic reader. After the operation result corresponding to the current command message is generated, the current command message is deleted, and the queue header message of the command message queue is taken out.

Resource Token Pool 105: Manages the number of resources within the network management system, providing the ability to apply for tokens and release tokens.

The command message sender 107: the command message dispatcher 103 retrieves the command message of the executable operation from the logical reader 104, and transmits it to the network element device by calling the command message transmitter 107.

Moreover, the state in which the logic reader of the present invention is in the system operation includes the following possible states, wherein the current command message in the logic reader 104-b, the current command message in the logic reader 104-c, and the logic reading Command message 3 in device 104-d is a restricted resource message:

Logic Reader 104-a: There are no restricted resource messages in the current command message and command message queue of the logic reader. When the command message distributor 103 schedules a message, the current command message is directly sent by calling the command message sender 107. In addition, if the command message 5 is newly generated at this time, since there is no restricted resource message in the current command message of the logical reader 104-a and the command message queue, and the command message queue is not full, it can be successfully inserted into the command message queue. Waiting to send.

Logic Reader 104-b: The current command message for the logical reader is a restricted resource message. Life When the message distributor 103 schedules the message, it first applies the token to the resource token pool. If the application is successful, the current command message is sent by calling the command message sender 107. In addition, if the command message 5 is newly generated at this time, since the current command message of the logical reader 104-b is a restricted resource message, the result of the fast failure operation is returned, prompting the operator that the network element is performing a time-consuming operation. , please try again later, the command message 5 is no longer inserted into the command message queue.

Logic Reader 104-c: The current command message for the logical reader is a restricted resource message. When the message dispatcher 103 schedules the message, it first requests the token in the resource token pool. If the application fails, the command message sender 107 is not called for transmission, but waits for the next request to re-apply the token. In addition, if the command message 5 is newly generated at this time, since the current command message of the logical reader 104-c is a restricted resource message, the result of the fast failure operation is returned, prompting the operator that the network element is performing time-consuming operations. , please try again later, the command message 5 is no longer inserted into the command message queue.

Logic Reader 104-d: The current command message for the logical reader is not a restricted resource message, but there is a restricted resource message in the command message queue. When the command message distributor 103 schedules a message, the current command message is directly sent by calling the command message sender. In addition, if the command message 5 is newly generated at this time, due to the existence of the restricted resource message in the command message queue of the logical reader 104-d, the result of the fast failure operation is returned, prompting the operator that "the network element is executing time-consuming. Action, please try again later, the command message 5 is no longer inserted into the command message queue.

In summary, the present invention has the following technical effects: The present invention improves the batch message scheduling policy of multiple similar network elements, and divides the operation request into ordinary messages by using the physical resources and time resources required for operation. And restricted resource messages, and provide adjustments to the corresponding scheduling policy. The concept of "restricted resources" proposed in the present invention and "resource token", "multi-segment timer", etc., solve the need for a single batch operation of limited resource messages in practical applications. The actual problem of artificial control, batch operation limited resource message operation success rate and common timeout of common message is affected, and the result type of operation failure is refined, which is very easy to use for operator positioning problem.

Claims

Claim

A scheduling method for a batch operation using a restricted resource, the method comprising: after receiving a command message including a network element identifier sent by a network management client, the requesting receiver sends the command message to a command message distribution Device

The command message distributor allocates the command message to a corresponding logical reader; the logic reader determines whether the command message is a restricted resource message, and if the command message is a restricted resource message, The command message requests a resource token from the resource token pool and sends the command message to the command message scheduler after the application is successful;

The command message scheduler sends the command message to the corresponding network element device by using a command message sender.

2. The method of claim 1, the restricted resource message being a message that uses limited resources in the network.

3. The method of claim 2, the command message distributor assigning the command message to a corresponding logical reader, comprising:

The command message distributor obtains a logical reader corresponding to the command message according to the network element identifier;

If the message in the logical reader has a restricted resource message, the command message allocation fails, and the fast failed result is created and stored in the operation result storage pool;

If the message in the logical reader does not have a restricted resource message, the command message is assigned to the logical reader.

4. The method according to claim 3, the logic reader applying for the resource token to the resource token pool for the command message, including:

The task timer presets the timing time;

The logic reader requests a resource token in the resource token pool for the command message every time the timing message is; and The logical reader records the number of failed application resource tokens. If the number of failures exceeds a fixed number of times, the application fails. Otherwise, the application is successful.

5. The method according to claim 4, the method further comprising: the logic reader applying a resource token to the resource token pool for the command message, and if the application fails, not processing the command message, creating The result of the operation timeout is stored in the operation result storage pool.

The method of claim 5, after the command message distributor assigns the command message to the corresponding logical reader, the method further includes:

The logic reader determines whether the command message is a restricted resource message, and if the command message is not a restricted resource message, the logic reader sends the command message to a command message scheduler;

7. The method of claim 6, further comprising:

The operation result processor listens to the message sent to the network element device, and if the message sent to the network element device is a restricted resource message, instructs the resource token pool to release the resource token occupied by the message.

8. A scheduling apparatus for batch operations using restricted resources, the apparatus comprising: a request receiver, a command message distributor, a logic reader, a resource token pool, a command message scheduler, and a command message sender; among them,

a command message dispatcher configured to receive the command message and assign the command message to a corresponding logical reader;

a logic reader, configured to determine whether the command message is a restricted resource message, and request a resource token from the resource token pool when the command message is a restricted resource message;

a resource token pool, set to be the command when the command message is a restricted resource message Allocating a resource token and sending the command message to the command message scheduler after the application is successful; the command message scheduler is configured to send the command message by the control command message sender;

The command message sender is configured to send the command message to the corresponding network element device.

9. The apparatus of claim 8, the restricted resource message being a message that uses limited resources in the network.

10. The device of claim 9, the device further comprising: