JP2007214850A - Resource managing device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable a maintenance administrator to solve the state of shortage in resources rapidly while the state of resource management can be recognized easily. <P>SOLUTION: A monitoring section 107 for monitoring a log storage 106 counts the number of resource securance messages, and generates a secondary log file in which the number of normally received messages counted for each unit time (second time) obtained by equally dividing the time for each prescribed time (first time) is put in the order of a larger number for description, for storage at the log storage 106 in a resource managing device. When, first, a log display unit 108 detects an increase in the secondary log file stored in the log storage 106, the secondary log file is referred to. When an increase in the secondary log file is detected, the messages in the secondary log file are displayed so that the maintenance administrator can view them. <P>COPYRIGHT: (C)2007,JPO&INPIT

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.

  The resource management by the resource management device manages the transmission capacity between nodes (links) constituting the communication network and the use status thereof by a server (resource management device) independent of the router constituting the communication network, and also the user terminal Appropriate resources are paid out in response to a resource securing request from the.

  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 event occurrence messages accepted by the resource management apparatus and adding them to a log file stored in the log storage section; and log storage section The log file stored in the second time obtained by equally dividing the first time into the number of resource reservation messages indicating that the generated resource has been secured for each first time. Each resource count message is counted every first time, and is counted every second time within the first time. A monitoring means for generating and storing in the log storage section secondary log files described in order from the largest number of logs and a log display means for displaying and outputting the secondary log files stored in the log storage section It is a thing.

  The resource management device according to the present invention is a resource management device for managing resources of a communication network composed of a plurality of routers and terminals linked to each other, and at least a resource amount to be secured in requested communication is determined. A resource management unit that accepts a request message including a necessary resource, a log management unit that collects an event occurrence message received by the resource management device and adds it to a log file stored in the log storage unit, and a log The log file stored in the storage unit is monitored, and the number of resource release messages indicating that the generated resource is released is divided into the first time equally for each first time. The resource release mem- ory is counted every second time, and every second time within the first time. At least a monitoring unit that generates a secondary log file in which the number of sage is arranged and described and stores the secondary log file in the log storage unit; and a log display unit that displays and outputs the secondary log file stored in the log storage unit It is what I did.

  The resource management device according to the present invention is a resource management device for managing resources of a communication network composed of a plurality of routers and terminals linked to each other, and at least a resource amount to be secured in requested communication is determined. A resource management unit that accepts a request message including a necessary resource, a log management unit that collects an event occurrence message received by the resource management device and adds it to a log file stored in the log storage unit, and a log The log file stored in the storage unit is monitored, and the number of resource change messages indicating that the state of the generated resource is changed every first time is divided equally into the first time. Resources counted every second time, and counted every second time within the first time every first time At least monitoring means for generating a secondary log file in which the number of further messages is arranged and described in order and storing the secondary log file in the log storage unit, and log display means for displaying and outputting the secondary log file stored in the log storage unit It is intended to provide.

  In the resource management device, the log management means may collect the event occurrence message received from the communication network within the range in which the resource management device itself manages and add it to the log file stored in the log storage unit. Good. 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. The next log file may be displayed and output.

  In the above resource management device, 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 manages the resource management device in which it is housed. Resources are secured within the scope. 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 is displayed and output.

  In the resource management device, the request message includes an identifier of a transmission destination terminal in the requested communication, and the resource management means manages the resource management device based on the identifier included in the received request message. If the terminal is determined not to be within the management range of the resource management apparatus as a result of this determination, the resource management apparatus manages other resources within the management range. A request message may be transmitted to secure necessary resources within the management range of the resource management device.

  As described above, according to the present invention, the number of resource reservation messages, resource release messages, and resource change messages counted every second time within the first time is increased every first time. The secondary log file that is described in order is generated, so that the maintenance manager can easily recognize the resource management status, and the resource shortage status can be resolved more quickly. An effect is obtained. For example, it becomes easy to know that the number of resources secured has reached the limit of the processing capacity, and it is possible to give an opportunity to increase resources to the maintenance manager.

  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 a resource management server 101 that manages resources for each management range network 201 constituting the communication network 200. Each resource management server (resource management apparatus) 101 manages resources of the management range network 201 to be managed. The communication network 200 to be managed is a communication network based on a so-called Internet protocol (IP).

  The management range network 201 includes, for example, a plurality of routers 202 and terminals (T) 203 connected (linked) to each other. In addition, the management range network 201 includes a switching hub (SW) 204 and a gateway device (GW) 205 that collect a plurality of terminals 203 and connect them to any router 202. The resources in the management range network 201 configured in this way are the access line between the terminal 203 and one of the routers 202 and the router 202 for configuring a communication path between the two terminals 203 that perform communication. The link between.

  In the resource management system shown in FIG. 1, the communication network 200 is divided into a plurality of management range networks 201, and a resource management server 101 is provided for each of these management ranges. Each resource management server 101 is connected to be communicable with each other.

  Further, the application server (AS) 301 receives a communication request from one of the terminals 203 and transmits a request message to the resource management server 101 that manages the resources of the management range network 201 to which the terminal 203 belongs. This request message includes at least the identifier of the terminal 203 and the amount of resources to be secured in the requested communication. In the system shown in FIG. 1, the IP address of the terminal 203 is used as this identifier.

  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 any application server 301 receives a request for content transmission from any terminal T203, the application server 301 transmits the requested content to the terminal T203. In such content distribution, the resource management server 101 manages necessary resources.

  In the case described above, 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 101 that manages the management range network 201 to which the terminal T203 that is the request belongs. Send. This request message includes at least the identifier of the requesting terminal T203 in the requested communication and the resource amount to be secured. As the identifier of the terminal T203, for example, the IP address of the requesting terminal T203 can be used.

  In the resource management server 101, 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 another resource management server 101. The transmission / reception unit 102 transmits the request message to another adjacent resource management server 101. The transmission / reception unit 102 transmits / receives a response message between the resource management servers 101.

  The control unit 103 performs processing according to the request message received by the resource management server 101 (transmission / reception unit 102). The control unit 103 analyzes each received message and identifies, for example, the IP address of the requesting terminal T203 included in the received message. Further, the control unit 103 determines with reference to the database that the terminal T203 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. At this time, when the control unit 103 receives the above-described resource reservation request and resource change request, the control unit 103 first generates a message indicating that the request has been received. For example, the control unit 103 generates a message including yyyymmddhhss (date and time), “accepted content: resource securing request”, “resource ID”, “resource management server ID”, and the like. In addition, the message may include information on a link that is a target for securing the requested resource. The generated message is sent out on the communication network 200.

  More specifically, the control unit 103 that has received a request message (resource reservation request) first checks the congestion state, the state of parameters set in the received request, etc. Judgment is made. If it is determined that the request cannot be accepted, the control unit 103 responds that the request is not possible. As described above, when the request is not accepted, the control unit 103 outputs a message indicating that resource allocation has failed as a log.

  Next, the control unit 103 determines whether the transmission source of the received request is a terminal accommodated in the management range network managed by the control unit 103. When the transmission source of the request is accommodated in the management range network, the control unit 103 outputs, as a log, a resource reservation status message in which the identification information of the transmission source is described as an acceptance state. On the other hand, when the transmission source of the request is not in the management range network, the control unit 103 outputs, as a log, a resource reservation status message in which it is only accepted as an acceptance state. These messages indicate that the resource securing request has been normally accepted.

  Next, when the transmission source of the request is in the management range network, the control unit 103 starts a resource securing process. However, if the resource securing process does not end within a predetermined time after the resource securing process is started, the control unit 103 outputs a resource securing status message describing that the time is exceeded as a reception state as a log. This message indicates that resource allocation has failed.

  Here, each message described above includes a request content including information such as an IP address of an application server that provides the requested service and an identifier of the application server, in addition to the reception state. The request content includes, for example, a reception-side resource management server identifier, a reception-side resource identifier, a destination-side resource management server identifier, a reception-side router identifier, a router operating state, a service type, and a reception time.

  As described above, when a resource securing request is accepted, the control unit 103 starts a resource securing process for the accepted request. In this resource securing process, the control unit 103, for example, confirms the service status currently being implemented, confirms data used in the service that uses the requested resource, and conflicts in the service that uses the requested resource. Check the status. In addition, the control unit 103 generates a resource necessary for the received request, responds that the resource is secured in the requesting application server 301, and displays the generated resource at the end time specified by the received request. Set as the target to be used. In addition, the control unit 103 secures a necessary bandwidth as well as generating resources. When the resource and the necessary bandwidth are secured in this way, the control unit 103 outputs a message indicating that the resource is secured in the resource state (resource securing message) as a log.

  The control unit 103 secures resources to other resource management servers with adjacent management ranges as necessary, such as when the transmission source of the received request is not accommodated in the management range network managed by the control unit 103. Send the request message. 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, for example, when the content distribution destination terminal T203 determines that the content is out of the management range, and the requested resource includes a portion beyond the management range. In this case, the control unit 103 generates a request message for securing resources to the resource management server 101 that manages the adjacent management range network 201.

  The log management unit 105 collects event occurrence messages received by the resource management server 101 (transmission / reception unit 102) and event occurrence messages in the resource management server 101, and the newly generated messages are stored in the log storage unit 106. Add to and update existing log files. The monitoring unit 107 monitors the log file stored in the log storage unit 106 and confirms the resource state included in the message, thereby indicating that the requested resource has been secured ( The number of resource reservation messages is counted, and the number of resource reservation messages counted per unit time (second time) obtained by equally dividing this time every predetermined time (first time) is listed in descending order. The generated secondary log file is generated and stored in the log storage unit 106.

  For example, the monitoring unit 107 first extracts a message indicating that the resource is secured in the resource state from the log received within a predetermined time. Next, for example, for each service type, a frequency distribution of the number (frequency) of resource securing messages per unit time (class) within the predetermined time is created, and the top 10 frequency classes (time) are calculated in descending order of frequency. And take it out 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 log display unit 108 displays a secondary log file in which the result of counting the number of messages indicating that the resource is normally secured in the resource state is displayed. Therefore, by referring to the displayed secondary log file, the number of states in which the resources are secured becomes visible to the administrator. Thus, according to the resource management apparatus shown in FIG. 1, the number of states in which resources are secured can be easily recognized by the administrator.

  Hereinafter, an example of the operation of the monitoring unit 107 in the resource management apparatus shown in FIG. 1 will be described with reference to the flowcharts of FIGS. 2 (a) and 2 (b). First, the monitoring unit 107 confirms the passage of 0.1 second (second time) (step S201). In this 0.1 second, when the monitoring unit 107 detects the occurrence of a new message in the log file (step S202), the monitoring unit 107 checks the resource state included in the generated message, and the resource is normal. It is confirmed that it indicates that it has been secured (step S203). If the generated message indicates that the resource has been secured, the monitoring unit 107 counts for each service type included in the request content included in the message (step S204). It is not limited to 0.1 seconds, but may be every 1 second or every 0.5 seconds.

  After the above steps S202 to S204 are continued for 0.1 second (step S201), the monitoring unit 107 confirms that one hour (first time) has elapsed from the start (step S205). If one hour has not elapsed, the monitoring unit 107 counts the number of resource reservation success messages counted as the service type (step S206). In this way, after counting the number of resource allocation messages counted every 0.1 second and repeating this for 1 hour (step S205), the monitoring unit 107 sets the count result every 0.1 second to 0. 0. From the frequency distribution with the frequency per unit time of 1 second, the top 10 most frequent frequencies are extracted (step S207). Next, the monitoring unit 107 describes the extracted top ten ranks (unit time: second time) in this order for each service type (step S208), and generates this as a secondary log file (step S208). S209). In addition, you may make it total not only 1 hour but at intervals of 2 hours, and may be intervals of 30 minutes.

  For example, the generated secondary log file includes the following contents as text data.

Secondary log file example time zone, service type, counting result 23:00, content distribution, 0110
23:00, content distribution, 0080
23:00, content distribution, 0070
23:00, content distribution, 0065
23:00, content distribution, 0060
23:00, content distribution, 0055
23:00, content distribution, 0050
23:00, content distribution, 0048
23:00, videophone, 0310
23:00, videophone, 0150
23:00, videophone, 0085
23:00, videophone, 0065
23:00, videophone, 0060
23:00, videophone, 0055
23:00, videophone, 0050
23:00, videophone, 0048
・ ・ ・
・ ・ ・
・ ・ ・
23:00, total, 0310
23:00, total, 0250
23:00, total, 0185
23:00, total, 0165
23:00, total, 0120
23:00, total 0085
23:00, total 0050
23:00, total 0040

  In a state where the secondary log file is generated in the log storage unit 106 as described above, the log display unit 108 first increases the secondary log file stored in the log storage unit 106 (step S221). When a new generation 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 aggregation results in 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 displays the count result on the monitor. Therefore, when a new secondary log file is generated, it is displayed, and the status of the number of resources secured can be easily confirmed. As described above, in the operation example shown in the flowchart of FIG. 2, since a secondary log file is generated (added) every hour, resources are secured in the monitor (log display unit 108) every hour. The large number of time zones (0.1 seconds) that are displayed are displayed in descending order, and these are displayed for each service type.

  In this way, if the secondary log file is displayed on the monitor, the maintenance manager can easily identify (recognize) the number of states in which resources are secured. When the above-described secondary log file example is generated, there is a state in which the number of resource allocations is concentrated in a certain 0.1 second in the hour when the secondary log file is generated. Can be easily recognized. In addition, when the top 10 ranked resource allocations are all 200 (resource allocation count / 0.1 second), this state indicates the limit of the processing capability of the resource management server 101. It can be judged. When the required processing capacity is 3000 (number of resources secured / second), it can be easily determined that the above state is insufficient in processing capacity (resources). In this manner, the resource shortage state in the network can be easily grasped by the administrator, and the administrator can easily determine the resource expansion opportunity.

  In step S206, based on the information included in the message, a weight is assigned to each type of resource secured, and the given weight is reflected in the count result to obtain a frequency distribution. Also good. For example, according to the processing load of service provision in which reserved resources are used, the number of corresponding resource reservation messages may be multiplied (counted) by a coefficient to obtain a frequency distribution.

  Also, for example, a threshold value of 3000 (number of resources secured / second) is set, and a secondary log file is generated by adding “*” to the end of the line for a period (unit time) in which the count value exceeds this value You may do it. Further, an average value for one hour may be used as the formula position. In addition, when there is a counting result to which “*” is given in the secondary log file, an alarm message may be output when the secondary log file is displayed.

  Next, another embodiment of the present invention will be described. In the above description, the monitoring unit 107 checks the resource state included in the log file message and counts the number of messages indicating that the resource has been secured. Absent. The monitoring unit 107 may count the number of messages indicating that resources have been released by confirming the resource state included in the message.

  As described above, a resource request generates a resource required for the received request to secure the resource and necessary bandwidth, and the generated resource is a target to be used until the end time specified by the received request. When set, the control unit 103 monitors the state of the set resource until the specified end time. In this resource state monitoring, for example, upon receiving notification of network failure, insufficient bandwidth, forced release, etc., the control unit 103 releases the set resource and releases the reserved bandwidth. Further, the control unit 103 releases the resource when the designated end time is reached. When the resource is released in this way, the control unit 103 outputs a message (resource release message) indicated in the resource state that service provision has been completed as a log.

  Therefore, the monitoring unit 107 can count the number of messages (resource release messages) indicating that the reserved resources have been released by checking the resource state included in the message. For example, the monitoring unit 107 monitors a log file stored in the log storage unit 106, counts the number of resource securing messages, and divides this time into equal time units at a predetermined time (first time). A secondary log file in which the number of resource securing messages counted every (second time) is described in a descending order is generated and stored in the log storage unit 106.

  For example, the monitoring unit 107 first extracts a message indicating that the resource is released in the resource state from the log received within a predetermined time. Next, for example, for each service type, a frequency distribution of the number (frequency) of resource release messages per unit time (class) within the predetermined time is created, and the top 10 frequency classes (time) are calculated in descending order of frequency. And take it out 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 log display unit 108 displays a secondary log file in which the total number of messages whose resource status indicates that the resource has been released normally is shown. Accordingly, by referring to the displayed secondary log file, the number of states in which resources are released becomes visible to the administrator. As described above, according to the resource management apparatus shown in FIG. 1, it is possible to make the administrator easily recognize the number of states in which resources are released.

  Hereinafter, an example of the operation of the monitoring unit 107 when notifying the number of states in which resources are released will be described with reference to the flowcharts of FIGS. 3A and 3B. First, the monitoring unit 107 confirms the passage of 0.1 second (second time) (step S301). During this 0.1 second, when the monitoring unit 107 detects the occurrence of a new message in the log file (step S302), the monitoring unit 107 checks the resource state included in the generated message, and the resource is released. (Step S303). If the generated message indicates that the resource has been released, the monitoring unit 107 counts for each service type included in the request content included in the message (step S304).

  After the above steps S302 to S304 are continued for 0.1 second (step S301), the monitoring unit 107 confirms that one hour (first time) has elapsed from the start (step S305). If one hour has not elapsed, the monitoring unit 107 counts the number of resource release messages counted as the service type (step S306). In this way, after counting the number of resource release messages counted every 0.1 second and repeating this for one hour (step S305), the monitoring unit 107 sets the count result every 0.1 second to 0. 0. From the frequency distribution with the frequency per unit time of 1 second, the top 10 most frequent frequencies are extracted (step S307). Next, the monitoring unit 107 describes the extracted top ten ranks (unit time: second time) in this order for each service type (step S308), and generates this as a secondary log file (step S308). S309).

  In the state where the secondary log file is generated in the log storage unit 106 as described above, the log display unit 108 first increases the secondary log file stored in the log storage unit 106 (step S321). When a new generation is detected, the secondary log file is referred to (step S322). 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 aggregation results in the secondary log file in a state that is visible to the maintenance manager (step S323).

  For example, the log display unit 108 includes a monitor (not shown in FIG. 1), and displays the count result on the monitor. Therefore, when a new secondary log file is generated, this is displayed, and the status of the number of released resources can be easily confirmed. As described above, in the operation example shown in the flowchart of FIG. 3, since a secondary log file is generated (added) every hour, resources are released to the monitor (log display unit 108) every hour. The large number of time zones (0.1 seconds) that are displayed are displayed in descending order, and these are displayed for each service type.

  As described above, when the secondary log file is displayed on the monitor, the number of states in which resources are released can be easily identified (recognized) for the maintenance manager. When the above-described secondary log file example is generated, there is a state in which the number of resource releases is concentrated in a certain 0.1 second in one hour when the secondary log file is generated. Can be easily recognized.

  In step S306, weighting is given to each type of released resource based on the information included in the message, and the given weighting is reflected in the counting result to obtain a frequency distribution. Good. For example, according to the processing load of service provision in which the released resources are used, the number of corresponding resource release messages may be multiplied (counted) by a coefficient to obtain a frequency distribution.

  In addition, the log collecting the message includes a message indicating a change (change) in the resource state. Examples of messages indicating changes in resource status include a state in which resources are forcibly released, a state in which services such as content provision are interrupted due to a network failure, and a resource is released due to a network or application server 301 failure. State, bypass route due to network failure (new resource) set, bypass route released, bandwidth overflow due to network failure, bandwidth overflow due to network failure resolved Status, resource release due to timeout of control of the resource management server, resource forcible release by bandwidth cancellation notification, resource forcible release by disconnection notification between the application server 301 and the resource management server 101, and the like.

  When a message indicating a change in the resource state (resource change message) is detected, the number of generated resource change messages is set to the first time for each first time as in the case of the resource securing message described above. A secondary log that counts for each equally divided second time and describes the number of resource allocation messages counted for each second time within the first time in order of increasing number of times. A file may be generated and stored in the log storage unit, and the stored secondary log file may be displayed and output.

  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. It is a flowchart explaining the example of operation | movement of the monitoring part 107 when notifying the state of the number of the resources being released.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 101 ... Resource management server 102 ... Transmission / reception part 103 ... Control part 104 ... Main memory part 105 ... Log management part 106 ... Log storage part 107 ... Monitoring part 108 ... Log display part 200 ... Communication network, DESCRIPTION OF SYMBOLS 201 ... Management range network, 202 ... Router, 203 ... Terminal (T), 204 ... Switching hub (SW), 205 ... Gateway apparatus (GW), 301 ... Application server (AS).

Claims (8)

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 event occurrence messages received by the resource management device and adding them to a log file stored in a log storage unit;
The log file stored in the log storage unit is monitored, and for each first time, the number of resource securing messages indicating that the generated resources are secured is equally divided into the first time. A secondary log that counts for each second time and describes the number of resource reservation messages counted for each second time in the first time in order from the first time. Monitoring means for generating a file and storing it in the log storage unit;
A resource management apparatus comprising: log display means for displaying and outputting the secondary log file stored in the log storage unit. 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 event occurrence messages received by the resource management device and adding them to a log file stored in a log storage unit;
The log file stored in the log storage unit is monitored, and for each first time, the number of resource release messages indicating that the generated resource has been released is equally divided into the first time. The secondary log is counted every second time, and is arranged in descending order of the number of resource release messages counted for each second time within the first time for each first time. Monitoring means for generating a file and storing it in the log storage unit;
A resource management apparatus comprising: log display means for displaying and outputting the secondary log file stored in the log storage unit. 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 event occurrence messages received by the resource management device and adding them to a log file stored in a log storage unit;
The log file stored in the log storage unit is monitored, and for each first time, the number of resource change messages indicating that the state of the generated resource has been changed is set to the first time. Counting is performed for each equally divided second time, and the number of resource change messages counted for each second time within the first time is arranged in descending order 2 for each first time. Monitoring means for generating a next log file and storing it in the log storage unit;
A resource management apparatus comprising: log display means for displaying and outputting the secondary log file stored in the log storage unit. In the resource management device according to any one of claims 1 to 3,
The log management means collects an event occurrence message received from the communication network within a range in which the log management unit itself manages resources, and adds it to a log file stored in a log storage unit. . In the resource management device according to any one of claims 1 to 4,
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 5,
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 6, 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 7,
The request message includes an identifier of a destination terminal in the requested communication,
The resource management means determines whether or not the terminal is within the management range of the resource management device based on the identifier included in the received request message. As a result of the determination, the terminal When it is determined that it is not within the management range of the resource management device, the request message is transmitted to another resource management device that manages resources in another management range, and is necessary within the management range of the resource management device. A resource management device characterized by securing resources.