JP4386370B2 - Resource management device - Google Patents

Description

  The present invention relates to a resource management apparatus that performs resource management and log file management of a communication network.

  When providing content such as audio and video using communication networks, especially IP (Internet Protocol) networks, if congestion occurs due to usage requests that exceed the capacity of the communication path, communication quality deteriorates due to packet loss, etc. Resulting in. Conventionally, resource management in a network layer by a resource management device (resource management server) has been studied for the purpose of preventing such deterioration of communication quality.

  Resource management by the resource management device manages the transmission capacity and usage status between nodes (links, etc.) constituting the communication network by a server (resource management device) independent of the router that constitutes the communication network, as well as the user. An appropriate resource is paid out in response to a resource securing request from a terminal or the like.

  As an example of such resource management, the following method is disclosed. First, before starting the operation of the communication network, the route through which the packet passes is calculated based on the link information (connection information) in the communication network and the routing information including the resource capacity of each link, and this is stored in the “route table”. And the resource capacity of each link is stored in the “resource management table”. The total resource capacity in the communication network and the resource capacity in use or the remaining resource capacity that can be used can be managed by the resource management table thus obtained.

  After the communication network starts operation, when the resource management server accepts a communication service use request (resource securing request), it becomes necessary for the communication from the route table based on the arrival / departure IP address of the requested communication. By specifying the link and referring to the resource management table, it is checked whether or not the transmission capacity (resource) necessary for the communication is available for each of these links.

  When sufficient resources are available, a permission response is made to the communication service use request, and the resource amount allocated to the communication is added to the resource capacity being used in the resource management table and stored. On the other hand, when necessary resources cannot be secured, the use request is not permitted (see Patent Document 1 and Non-Patent Document 1). In this method, resources reserved for communication are released immediately when the use of the resources is completed.

  In a resource management apparatus that controls such a network, it is important to monitor the state of the network. On the network, for example, an edge router outputs information such as parameters given at the time of processing, details of executed processing, processing results, and the like according to operations. The output information includes communication results and edge router failure information.

JP 2003-258855 A Yaguchi et al., "A Proposal and Specific Example of Resource Management Method Using Management Server in Large IP Network", IEICE General Conference, B-6-31 (2002)

  In the above-described conventional technology, the vacancy of the existing resource is managed, and the payout of the resource in response to the resource securing request and the return due to the release are only managed. For this reason, in a state where resource securing requests occur frequently due to an increase in resource request sources and resource request frequency, resources are always in shortage, and resource securing failures frequently occur. If such a state is left unattended, a user using the network may not be able to receive a desired service such as content provision.

  The present invention has been made to solve the above-described problems, so that the maintenance manager can easily recognize the state of resource management, and the state of lack of resources can be solved more quickly. The purpose is to do.

  A resource management apparatus according to the present invention is a resource management apparatus that manages resources of a communication network composed of a plurality of routers and terminals linked to each other, and includes a request that includes at least the amount of resources to be secured in requested communication Resource management means for accepting messages and securing necessary resources, log management means for collecting resource reservation failure messages accepted by the resource management device and adding them to a log file stored in the log storage unit, and log storage The log file stored in the log file is monitored, and error messages indicating failure to secure resources recorded in the log file are aggregated for each path that failed to secure resources, and stored as a secondary log file. Means for storing in the storage unit, and secondary log file stored in the log storage unit Log display means for displaying and outputting at least, and the resource allocation failure message includes information on the path that failed to secure the resource together with the resource allocation failure, and the secondary log file is arranged higher in the path having a larger number of aggregations. The display is output in the state.

  In the resource management apparatus, the log management means collects a resource securing failure message received from a communication network within a range where the resource management apparatus itself manages and adds the message to the log file stored in the log storage unit. The monitoring unit monitors the update of the log file stored in the log storage unit, and the log display unit is stored in the log storage unit when the log file is updated as a result of monitoring by the monitoring unit. Displays and outputs the next log file message.

  Note that the communication network has a plurality of divided management ranges, a plurality of resource management devices are provided for each of the plurality of management ranges, and the resource management means includes resources within the management range of the resource management device in which the communication network is accommodated. May be secured. Further, the resource management device includes identification information for identifying its own management range and itself, and the log display means stores a log file stored in a log storage unit of the corresponding resource management device based on the identification information The message may be displayed and output.

  Further, in the resource management device, the request message includes an identifier of a destination terminal in the requested communication, and the resource management unit is configured to allow the terminal to determine the resource management device based on the identifier included in the received request message. When it is determined whether or not the terminal is not within the management range of the resource management apparatus as a result of this determination, the other resource management apparatus that manages resources in another management range A request message may be transmitted to the terminal to secure necessary resources within the management range of the resource management apparatus.

  As described above, according to the present invention, error messages indicating failure to secure resources recorded in the log file are aggregated for each path that failed to secure resources, and stored as a secondary log file. The secondary log file is displayed and output in a state where the secondary log file has a higher number of tabulations arranged at the top, so that the maintenance manager can easily recognize the resource management status. As a result, it is possible to obtain an excellent effect that the resource shortage state can be resolved more quickly. In this manner, if the resource shortage state can be easily recognized, for example, the maintenance manager can be given an opportunity to increase or decrease the resources for each route.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a configuration diagram illustrating a configuration example of a resource management system using a resource management device according to an embodiment of the present invention. The resource management system shown in FIG. 1 includes resource management servers 101a to 101c that manage resources for each of the management range networks 201a to 201c constituting the communication network 200. Each resource management server (resource management apparatus) 101a to 101c manages resources of the management range networks 201a to 201c to be managed. The communication network 200 to be managed is a communication network based on a so-called Internet protocol (IP). Although FIG. 1 illustrates three sets of resource management servers and management range networks, the present invention is not limited to this, and the same applies when there are four or more sets of resource management servers and management range networks.

  For example, the management range network 201a includes, for example, a plurality of routers 202a, 202b, 202c and terminals (T) 203a, 203b, 203c, 203d, 203e, 203f that are connected (linked) to each other. The terminals 203b and 203c are concentrated on a switching hub (SW) 204a connected to the router 202a, and the terminals 203d, 203e and 203f are concentrated on a switching hub 204b connected to the router 202a. The terminals 203e and 203f are concentrated on the switching hub 204b via a gateway device (GW) 205. For example, the terminal 203e and the terminal 203f are arranged in the same house and are connected to a gateway device 205 provided in the house.

  The terminal 203a is connected to the router 202a via an access line 231, the terminal 203b is connected to the switching hub 204a via an access line 232, and the terminal 203c is connected to the switching hub 204a via an access line 233. The terminal 203d is connected to the switching hub 204b via an access line 234, and the gateway device 205 is connected to the switching hub 204b via an access line 235. The switching hub 204a is connected to the router 202a by an access line converging 241 and the switching hub 204b is connected to the router 202a by an access line converging 242. The router 202 a is connected to the router 202 b via the inter-router connection 221, and the router 202 b is connected to the router 202 c via the inter-router connection 222.

  The resources to be managed in the management range network 201a configured in this way are, for example, the access lines 231 to 235, the access line convergence 241 and 242 and the inter-router connections 221 and 222. Note that the configuration of each node such as the terminal, switching hub, gateway device, and router described above and the configuration of each link are examples, and the same applies to the other management range networks 201b and 201c. They are connected to each other by various forms of links.

  As described above, in the resource management system shown in FIG. 1, the communication network 200 is divided into a plurality of management range networks 201a to 201c, and resource management servers 101a to 101c are provided for these management ranges. . Moreover, each resource management server 101a-101c is connected so that communication is mutually possible.

  The application server (AS) 301 receives a communication request from any of the terminals 203a to 203f, and sends a request message to the resource management server 101a that manages the resources of the management range network 201a to which the requesting terminals 203a to 203f belong. Send. This request message includes at least the identifiers of the terminals 203a to 203f in the requested communication and the amount of resources to be secured. In the system shown in FIG. 1, the IP addresses of the terminals 203a to 203f are used as the identifiers. Used.

  Each resource management server 101 is a computer having a communication function, and includes a transmission / reception unit 102, a control unit (resource management means) 103, and a main storage unit 104. Each resource management server 101 includes a log management unit 105, a log storage unit 106, a monitoring unit 107, and a log display unit 108. These functions are installed in this computer and computer hardware resources such as a central processing unit (CPU) and storage devices (including internal memories such as ROM and RAM, as well as external storage devices such as fixed disk devices). This can be realized by cooperation with a computer program (software).

  In the communication network 200 configured as described above, the application server 301 can provide services such as content provision. For example, when one of the application servers 301 receives a request for content transmission from one of the terminals 203a to 203f, the application server 301 transmits the requested content to, for example, the requesting terminal 203b. In the management range network 201a, this content distribution is performed via, for example, the router 202c, the inter-router connection 222, the router 202b, the inter-router connection 221, the router 202a, the access line converging 241, the switching hub 204a, and the access line 232. Done. In such content distribution, the resource management server 101a manages the inter-router connection 222, the inter-router connection 221, the access line convergence 241 and the access line 232 which are necessary resources.

  In the above case, the application server 301 that has received the content transmission request sends a resource request message for sending the content to the resource management server 101a that manages the management range network 201a to which the requesting terminal 203b belongs. Send. This request message includes at least the identifier of the requesting terminal 203b in the requested communication and the resource amount to be secured. As the identifier of the terminal 203b, for example, the IP address of the terminal 203b can be used.

  In the resource management server 101a, the transmission / reception unit 102 includes a communication interface, and transmits and receives various messages. The transmission / reception unit 102 receives a request message transmitted from the application server 301 or other resource management servers 101b and 101c. The transmission / reception unit 102 transmits the request message to the other adjacent resource management servers 101b and 101c. The transmission / reception unit 102 transmits / receives a response message between the resource management servers 101a to 101c.

  The control unit 103 performs processing according to the request message received by the resource management server 101a (transmission / reception unit 102). The control unit 103 analyzes each received message and identifies, for example, the IP address of the request source terminal 203b included in the received message. Further, the control unit 103 determines with reference to the database that the terminal 203b corresponding to the identified IP address is within the confidence management range.

  In addition, the control unit 103 refers to the route information and resource management table prepared in the main storage unit 104 and secures necessary resources. The state of the resource secured by the control unit 103 is managed by a resource management table in the main storage unit 104. In this stage of securing resources, if the resource allocation fails, the control unit 103 generates a resource allocation failure message. For example, the control unit 103 generates an error message including yyyymmddhhss (date and time), “error content: reservation failure”, “resource ID (identifier)”, “resource management server ID”, and the like. The error message may include information on a target link for which resource allocation has failed. The generated message is sent out on the communication network 200.

  In addition, the control unit 103 transmits a resource securing request message to another resource management server having an adjacent management range as necessary. The other resource management server that has received this message also reserves resources within its management range, and transmits a resource reservation request message to the other resource management server as necessary. For example, based on the identifier included in the received request message, when the requesting (content distribution destination) terminal 203b determines that it is out of the management range, and when the requested resource exceeds the management range itself If it is included, the control unit 103 generates a request message for securing resources to the resource management server 101b that manages the adjacent management range network 201b.

  In addition, when the control unit 103 receives a notification from the application server 301 that communication such as content transmission has been completed, the control unit 103 secures or releases the source, and this time the resource is transmitted to the adjacent server that has transmitted the resource securing request message. Send a release request message. Here, the other resource management server that received this message also releases the resource within its own management range, and sends a resource release request message to the other resource management server that sent the resource reservation request message first. .

  Next, the log management unit 105 collects the event occurrence message received by the resource management server 101a (transmission / reception unit 102) and the event occurrence message in the resource management server 101a, and stores the newly generated message in the log storage unit 106. Add to and update the stored log file. The monitoring unit 107 monitors the log file stored in the log storage unit 106, totals messages (error messages) indicating resource allocation failure for each route and service type, and displays the total resource allocation failure. The indicated message is stored in the log storage unit 106 as a secondary log file.

  The log display unit 108 refers to the log file and the secondary log file stored in the log storage unit 106 and displays a message in each log file in a state that is visible to the administrator. For example, the resource allocation failure messages in the log file are aggregated for each path, extracted to the secondary log file, and displayed by the log display unit 108. Accordingly, referring to the secondary log file makes it possible for the administrator to visually recognize a route (resource) in which failure to secure resources occurs frequently. As described above, according to the resource management device shown in FIG. 1, the situation where the resource allocation has failed can be easily recognized by the administrator, and the administrator can easily grasp the resource shortage state in the network. become. As a result, the administrator can easily determine the resource expansion opportunity.

  Hereinafter, an operation example of the resource management apparatus illustrated in FIG. 1 will be described with reference to the flowcharts of FIGS. 2A and 2B. First, in step S201, when the log management unit 105 detects the occurrence of a new message, in step S202, the log management unit 105 adds and updates the detected message to the log file stored in the log storage unit 106. Next, after a log file is added and updated for a predetermined time (step S203), the monitoring unit 107 that monitors the log storage unit 106 collects a resource allocation failure message (step S204). The securing failure messages are sorted by route (resource) (step S205), the collected securing failure messages are sorted by route (resource) (step S206), and sorted in descending order of the number of counting (step S207).

  For example, in step S204, the monitoring unit 107 collects a resource reservation failure message and generates a resource reservation failure file in which “date, time, connection ID, terminal ID” is described as shown below. The “connection ID” corresponds to the access lines 231 to 235, the access line convergence 241 and 242 and the inter-router connections 221 and 222 shown in FIG. 1, and the terminal IDs are the terminals 203a, 203b, 203c, 203d, and 203e. , 203f.

Date, time, connection ID, terminal ID
yyyymmdd, hhmmss, access line 231, terminal a
yyyymmdd, hhmmss, link 221, terminal a
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line focusing 242, terminal f
yyyymmdd, hhmmss, link 221, terminal a
yyyymmdd, hhmmss, access line 231, terminal a
yyyymmdd, hhmmss, link 221, terminal d
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line 232, terminal b
yyyymmdd, hhmmss, access line 233, terminal c
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line focusing 241, terminal c
yyyymmdd, hhmmss, access line 234, terminal d
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, link 221, terminal a
yyyymmdd, hhmmss, access line 235, terminal e
yyyymmdd, hhmmss, link 221, terminal b
yyyymmdd, hhmmss, link 221, terminal a
yyyymmdd, hhmmss, access line focusing 242, terminal d
yyyymmdd, hhmmss, access line 234, terminal d
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line 235, terminal f
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line 231, terminal a
yyyymmdd, hhmmss, access line 231, terminal a
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line focusing 242, terminal e
yyyymmdd, hhmmss, link 221, terminal b
yyyymmdd, hhmmss, link 222, terminal c

  Further, in step S205, the monitoring unit 107 rearranges the contents of the above-mentioned securing failure file for each route as shown below, for example.

Date, time, connection ID, terminal ID
yyyymmdd, hhmmss, access line 231, terminal a
yyyymmdd, hhmmss, access line 231, terminal a
yyyymmdd, hhmmss, access line 231, terminal a
yyyymmdd, hhmmss, access line 231, terminal a
yyyymmdd, hhmmss, access line 232, terminal b
yyyymmdd, hhmmss, access line 233, terminal c
yyyymmdd, hhmmss, access line 234, terminal d
yyyymmdd, hhmmss, access line 234, terminal d
yyyymmdd, hhmmss, access line 235, terminal e
yyyymmdd, hhmmss, access line 235, terminal f
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line converging 241, terminal b
yyyymmdd, hhmmss, access line converging 241, terminal c
yyyymmdd, hhmmss, access line focusing 242, terminal e
yyyymmdd, hhmmss, access line focusing 242 and terminal f
yyyymmdd, hhmmss, access line convergence 242 and terminal d
yyyymmdd, hhmmss, link 221, terminal d
yyyymmdd, hhmmss, link 221, terminal a
yyyymmdd, hhmmss, link 221, terminal b
yyyymmdd, hhmmss, link 221, terminal a
yyyymmdd, hhmmss, link 221, terminal b
yyyymmdd, hhmmss, link 221, terminal a
yyyymmdd, hhmmss, link 221, terminal a
yyyymmdd, hhmmss, link 222, terminal c

  In step S206, the monitoring unit 107 adds up the contents of the allocation failure files rearranged for each of the routes as shown below, for example.

Connection ID, total access line 231, 04
Access line 232,01
Access line 233, 01
Access line 234,02
Access line 235, 02
Access line focusing 241,08
Access line focusing 242,03
Link 221, 07
Link 222, 01

  In step S207, the monitoring unit 107 rearranges the contents of the allocation failure files aggregated for each of the above routes in the descending order of the aggregation count as shown below, for example.

Connection ID, aggregated access line convergence 241, 08
Links 221 and 07
Access line 231, 04
Access line converging 242,03
Access line 234, 02
Access line 235, 02
Access line 232, 01
Access line 233, 01
Link 222, 01

  Finally, the monitoring unit 107 adds the result of the aggregation and rearrangement as described above to the secondary log file (step S208). Therefore, the resource allocation failure message in the log file generated within the predetermined time is stored as a secondary log file aggregated for each path.

  In the state where the log file and the secondary log file are stored in the log storage unit 106 as described above, the log display unit 108 first stores the secondary log file stored in the log storage unit 106 in step S221. When the increase is detected, the secondary log file is referred to (step S222). The log storage unit 106 detects an increase in the secondary log file at a preset time interval. Next, the log display unit 108 displays the secondary log file in a state that is visible to the maintenance manager (step S223).

  For example, the log display unit 108 includes a monitor not shown in FIG. 1, and the secondary log file described above is displayed on this monitor. For example, as described above, the resource reservation failure status is displayed on the monitor in a state of being aggregated for each route and rearranged in descending order of the number of aggregations. As described above, when the resource reservation failure state is displayed on the monitor, the maintenance manager can easily identify (recognize) the state of the path where the resource reservation failure frequently occurs. In this way, if the maintenance manager recognizes the status of resource reservation failure for each path, the maintenance manager can easily grasp the path where the resource shortage has occurred. As described above, according to the resource management apparatus shown in FIG. 1, it is possible to give the maintenance manager an opportunity to increase or decrease for each resource for each route.

  The log management unit 105 collects event occurrence (resource allocation failure) messages received from the management range network 201 that manages resources by the resource management server 101 and stores them in the log storage unit 106. You may make it add to. In addition, the monitoring unit 107 monitors the update time of the log file stored in the log storage unit 106, and the log display unit 108 determines the update time of the log file as a result of monitoring by the monitoring unit 107. The display may be output with

  By the way, the resource management server 101 includes identification information for identifying itself, identification information for identifying its own management range, and the like. For example, the resource management server 101 is given a set of station name and identifier as identification information together with the IP address. These are provided as a reference table. When the station name “Tokyo” is selected by the log display unit 108, the reference table is referred to, and the log display unit 108 corresponds to the IP address “192.168.0.5” paired with “Tokyo”. The log file stored in the log storage unit 106 of the resource management server 101 can be referred to.

It is a block diagram which shows the structural example of the resource management system using the resource management apparatus in embodiment of this invention. 3 is a flowchart for explaining an operation example of the resource management apparatus shown in FIG. 1.

Explanation of symbols

  101a, 101b, 101c ... resource management server, 102 ... transmission / reception unit, 103 ... control unit, 104 ... main storage unit, 105 ... log management unit, 106 ... log storage unit, 107 ... monitoring unit, 108 ... log display unit, 200 Communication network, 201a, 201b, 201c ... Management range network, 202a, 202b, 202c ... Router, 203a-203f ... Terminal (T), 204a, 204a ... Switching hub (SW), 205 ... Gateway device (GW), 301 ... Application server (AS), 221 and 222 ... Connection between routers, 231 to 235 ... Access line, 241, 242 ... Access line convergence.

Claims (6)

A resource management device for managing resources of a communication network composed of a plurality of routers and terminals linked to each other,
A resource management means for accepting a request message including at least a resource amount to be secured in requested communication and securing necessary resources;
Log management means for collecting a resource securing failure message received by the resource management device and adding it to a log file stored in a log storage unit;
The log file stored in the log storage unit is monitored, and error messages indicating failure to secure resources recorded in the log file are aggregated for each path that failed to secure resources, and the secondary log file. Monitoring means for storing in the log storage unit as
Log display means for displaying and outputting the secondary log file stored in the log storage unit,
The resource reservation failure message includes information on a route that failed to secure the resource together with the resource reservation failure,
The resource management apparatus according to claim 2, wherein the secondary log file is displayed and output in a state in which the path having a larger total number is arranged at a higher position. The resource management device according to claim 1, wherein
The log management means collects a resource securing failure message received from the communication network within a range in which the resource is managed and adds the message to a log file stored in a log storage unit apparatus. The resource management device according to claim 1 or 2,
The monitoring means monitors the update of the log file stored in the log storage unit,
The log display unit displays and outputs a secondary log file stored in the log storage unit when the log file is updated as a result of monitoring by the monitoring unit. In the resource management device according to any one of claims 1 to 3,
The communication network includes a plurality of divided management ranges, and a plurality of the resource management devices are provided for each of the plurality of management ranges.
The resource management device, wherein the resource management unit secures a resource within a management range of a resource management device in which the resource management unit is housed. The resource management device according to claim 4, wherein
The resource management device includes its own management range and identification information for identifying itself,
The said log display means displays and outputs the message of the said log file memorize | stored in the said log memory | storage part of a corresponding resource management apparatus based on the said identification information. The resource management apparatus characterized by the above-mentioned. In the resource management device according to any one of claims 1 to 5,
The request message includes an identifier of a destination terminal in the requested communication,
The resource management means determines, based on the identifier included in the received request message, whether or not the terminal is within the management range of the resource management apparatus. As a result of the determination, the terminal When it is determined that it is not within the management range of the management device, the request message is transmitted to another resource management device that manages resources in the other management range, and resources required within the management range of the resource management device A resource management device characterized by securing

Images