JP4268143B2 - Resource management apparatus and method, and system - Google Patents

Description

  The present invention relates to a resource management apparatus and method for managing resources in a communication network, and a system.

When content such as audio and video is provided using a communication network, especially an IP (Internet Protocol) network, if congestion occurs due to a usage request that exceeds the capacity of the communication path, the communication quality is accompanied by packet loss. Will deteriorate. Conventionally, resource management in a network layer by a resource management device has been studied for the purpose of preventing such deterioration of communication quality.
Resource management by the resource management device manages the transmission capacity between nodes (links) constituting the communication network and the usage status thereof by a resource management server (resource management device) independent of the router constituting the communication network. An appropriate resource is paid out in response to a resource securing request from a user terminal or the like.

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

After starting the operation of the communication network, when the resource management server accepts a communication service use request (resource securing request), a link necessary for the communication from the route table based on the IP address of the requested communication Is identified. Then, referring to the resource management table, it is checked whether or not the capacity required for the communication is available for each of these links. As a result, when a sufficient capacity is available, a permission response is made to the communication service use request and a resource including the link is secured. Specifically, the capacity allocated to the communication is added to the resource capacity being used in the resource management table and stored. On the other hand, when resources cannot be secured, a rejection response is made to the use request (see, for example, Patent Document 1 and Non-Patent Document 1).
Also, when the use of the resource is completed, the resource that has been reserved for communication is released immediately.

The applicant has not yet found prior art documents related to the present invention by the time of filing other than the prior art documents specified by the prior art document information described in this specification.
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)

When the communication network becomes large, the resources that must be managed become enormous, and the resource securing requests that the resource management server should deal with increase. Therefore, one resource management server manages the resources of the entire communication network. It becomes difficult. In order to cope with such a problem, it is conceivable to divide the communication network into a plurality of management ranges for each region, for example, and to provide resource management servers in these management ranges.
When connecting a plurality of communication networks operated by different operators, a resource management server may be provided for each communication network. In this case, it can be considered that a large communication network is divided for each business operator, and a resource management device that manages each business operator's communication network is provided.

  In such a communication network, when a transmitting terminal and a receiving terminal that communicate with each other belong to different management ranges, a series of resources that span a plurality of management ranges are managed in cooperation between a plurality of resource management servers. It will be.

  However, since the management scope of each resource management server is limited, even if the maintenance person of the resource management server can browse information on resources within the management scope on the resource management server, Information cannot be viewed. For this reason, even if a failure occurs somewhere in a series of resources that span multiple management ranges, if the failure does not occur within the management range of the resource management server, the maintainer In this case, it is not possible to browse information regarding failures, and it is not possible to specify specific failure locations.

In addition, even if the maintenance person can browse information on resources in other management scopes on the resource management server, a series of resource connections between his management scope and other management scopes is I do n’t know. For this reason, a table representing the connection relationship of resources is prepared separately, and the maintainer needs to consider a series of resource connections while referring to this table.
As described above, as a result of limiting the management range of the resource management server, there is a problem that the maintenance operability of the resource management server is deteriorated.

  The present invention has been made to solve such problems, and an object thereof is to improve the maintenance operability of a resource management server provided for each of a plurality of management ranges obtained by dividing a communication network.

In order to achieve such an object, the resource management apparatus according to the present invention is provided for each of a plurality of management ranges obtained by dividing a communication network composed of a plurality of routers and terminals linked to each other, Other resource management devices that manage resources within a range, and that manage resource information related to resources managed by the resource management device and other management ranges adjacent to the management range of the resource management device Resource information storage means for storing together with the identifier of the management device, and a browse request message for requesting the other resource management device identified by the identifier to browse the resource information relating to the resource managed by the other resource management device A browsing request means for creating and transmitting the file, and the other resource Characterized in that it comprises a display means for displaying the resource information in the management device. Here, the resource information storage means stores identification information for identifying a communication path between two terminals performing communication as one of the resource information, and the browsing request means stores the identification information in the browsing request message. It may be added. Correspondingly, the resource information reading means may read the resource information related to the resource of the communication path specified by the identification information added to the browsing request message.

  The resource management device includes: a browse request message receiving unit that receives a browse request message from another resource management device that manages another management range adjacent to the management range of the resource management device; and the received browse request Resource information reading means for reading out the resource information from the resource information storage means in response to a message, and display enabling means for displaying the read resource information on the other resource management device, Also good.

  The resource management device described above further includes login request means for creating and transmitting a login request message to which authentication information used for identity verification is added to the other resource management device specified by the identifier. There may be. Also, by verifying authentication information storage means for storing authentication information used for identity verification, authentication information added to the received login request message and the authentication information stored in the authentication information storage means The log information requesting means further comprises authentication means for confirming that the sender of the login request message is an authorized user, and the resource information reading means is that the sender of the login request message is an authorized user by the authenticating means. The resource information may be read when it is confirmed.

In addition, the resource management method according to the present invention divides a communication network composed of a plurality of routers and terminals linked to each other into a plurality of management ranges, and the resource management device provided for each of these management ranges A resource management method for managing resources of a communication network, wherein, in one resource management device, an identifier of another resource management device that manages another management range adjacent to the management range of the one resource management device is a first. A storage request stored in the storage means, and a browse request message for requesting the other resource management device specified by the identifier to browse resource information related to the resource managed by the other resource management device. A browsing request step to transmit, and the resource in the other resource management device Characterized in that it comprises a display step of displaying the information. Here, the first storage means further stores identification information for identifying a communication path between two terminals performing communication, and the browsing request step adds the identification information to the browsing request message. Also good. Correspondingly, the resource information reading step may read the resource information related to the resource of the communication path specified by the identification information added to the browsing request message.

  The resource management method includes a storage step of storing resource information related to resources managed by the other resource management device in a second storage unit in the other resource management device; A browsing request message receiving step for receiving the browsing request message, a resource information reading step for reading the resource information from the second storage unit in response to the received browsing request message, and the read resource information You may make it further provide the display enabling step displayed on said one resource management apparatus.

  In the resource management method described above, in the one resource management apparatus, a login request message to which authentication information used for identity verification is added is transmitted to the other resource management apparatus specified by the identifier. A login request step may be further provided. Further, in the other resource management device, the authentication information added to the received login request message and the authentication information stored in the authentication information storage means are collated, whereby the sender of the login request message is authorized. An authentication step for confirming that the user is the user is further included, and the resource information reading step reads the resource information when the sender of the login request message is confirmed to be the authorized user by the authentication step. You may do it.

The resource management system according to the present invention divides a communication network composed of a plurality of routers and terminals linked to each other into a plurality of management ranges, and the resource management apparatus provided for each of these management ranges A resource management system for managing resources of a communication network, wherein one resource management device stores an identifier of another resource management device that manages another management range adjacent to the management range of the one resource management device Browsing for creating and transmitting a browsing request message for requesting browsing of resource information related to resources managed by the other resource management device to the other resource management device identified by the first storage means and the identifier Display the resource information in the request means and the other resource management device Display means, wherein the other resource management device stores second resource information about resources managed by the other resource management device, and the browsing request from the one resource management device A browsing request message receiving means for receiving a message; a resource information reading means for reading the resource information from the second storage means in response to the received browsing request message; and the read resource information Display enabling means to be displayed on the resource management device , wherein the first storage means stores identification information for identifying a communication path between two terminals performing communication as one of the resource information, and the browsing request means is The identification information is added to the browsing request message .
The resource management device according to the present invention described above can be used as the one or other resource management device.

  In the present invention, in the resource management device, an identifier of another resource management device whose management range is adjacent is stored, and a browse request message for requesting the other resource management device specified by this identifier to browse the resource information And resource information is displayed as a response. Thereby, the maintenance person of the resource management apparatus can browse the resource information within the management range of other resource management apparatuses.

In the present invention, in the resource management device, identification information for identifying a communication path between two terminals that perform communication is stored, and the identification information is added to the browsing request message and transmitted. In another resource management device, the resource information specified by the identification information added to the browsing request message is read and displayed on the resource management device. Thereby, the maintenance person of the resource management apparatus can browse the resource information of the predetermined communication path within the management range of other resource management apparatuses.
At this time, in the resource management device, by adding the identification information designated by the maintenance person to the browsing request message, the maintenance person does not need to consider the connection of a series of resources.

  Further, according to the present invention, the other resource management apparatus can prevent the person who does not have management authority from browsing the resource information by performing identity verification before reading the resource information.

  In the present invention, the resource management device stores identifiers of other resource management devices adjacent to each other in the management range, requests resource processing from other resource management devices specified by the identifier, The resource management apparatus performs processing in response to a request from the resource management. Thereby, the maintenance person of the resource management apparatus can perform processing of resources within the management range of the other resource management apparatus from the resource management apparatus.

  As described above, according to the present invention, it is possible to improve the maintenance operability of the resource management device whose management range is limited.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
1. Overview of Resource Management System FIG. 1 is a block diagram showing an overview of a resource management system according to an embodiment of the present invention.
This resource management system includes a plurality of resource management servers RMS1, RMS2,..., RMSn (n is an integer equal to or greater than 2) for managing resources of a communication network.

  Here, the communication network to be managed is a communication network based on the Internet protocol (IP), and a plurality of routers R (R11, R12, R13, R14, R21, R22, R23, R24,. Rn1, Rn2, Rn3, Rn4) and terminals T (T11, T12,..., Tn1, Tn2). The resource of this communication network is an access line between the terminal T and the router R and a link between the routers R that constitutes a communication path between two terminals (source terminal and destination terminal) that perform communication. Say.

In this resource management system, the communication network is divided into a plurality of management ranges NW1, NW2,..., NWn, and resource management servers RMS1 to RMSn are provided for these management ranges NW1 to NWn, respectively. In FIG. 1, the resource management server RMS1 is a resource management device that manages resources in the management range NW1, the resource management server RMS2 is a resource management device that manages resources in the management range NW2, and the resource management server RMSn is a management range NWn. It is a resource management device that manages the resources. These resource management servers RMS1 to RMSn are connected to be communicable with each other.
In the configuration described above, each of the management ranges NW1 to NWn can be regarded as a communication network, and the resource management servers RMS1 to RMSn can be regarded as resource management devices that manage the resources of the communication networks NW1 to NWn, respectively.

  Upon receiving a communication request from a terminal (for example, terminal T11), the application server AS sends a resource management server (for example, resource management server RMS1) that manages resources in the management range (for example, management range NW1) to which this terminal belongs. A server that sends a request message. The request message includes a resource securing request message for requesting securing of a resource required for communication, a resource change request message for requesting to change a secured resource, and a resource release request message for requesting release of a secured resource. is there.

2. Configuration of Resource Management Server Resource management servers RMS1 to RMSn are computers each having a communication function, and each include a resource management server main body, a database unit, and an operation browsing unit. These basic functions are common to each of the resource management servers RMS1 to RMSn.
These functions are based on computer hardware resources such as an arithmetic unit (MPU) and a storage device (including an internal memory such as a ROM and a RAM and an external storage device such as an HDD) and a computer installed in this computer. -It is realized by cooperation with a program (software).

FIG. 2 is a functional block diagram of the resource management server RMSi (i = 1 to n).
The resource management server main body i1 is an application server AS and other resource management servers that manage other management ranges NWi-1 and NWi + 1 adjacent to the management range NWi of the resource management server RMSi (hereinafter abbreviated as “adjacent server”). The resource management within the management range NWi of the resource management server RMSi is performed while exchanging request messages with RMSi-1 and RMSi + 1.
Various pieces of information necessary for resource management by the resource management server body i1 are recorded in the database unit i2.
The operation browsing unit i3 displays information (resource information) related to resources managed by the resource management server body i1.

Hereinafter, functions of each unit of the resource management server RMSi will be described in more detail.
2-1. Database part i2
As illustrated in FIG. 2, the database unit i2 includes path information 201, a resource management table 202, and authentication information 203.
Here, the path information 201 is a list of communication paths configured from resources within the management range NWi of the resource management server RMSi. For example, the route information 201 includes an IP address “entrance node IP” of an edge node that is an entrance of a route within the management range NWi, an IP address “exit node IP” of an edge node that is an exit of the route, and the relationship between these nodes The resource capacity “resource capacity” for connecting the resources and details of these resources “resource details”.

  The “resource details” include individual resources that constitute a route between the ingress node and the egress node and between the originating terminal and the terminating terminal, that is, access lines (paths between the terminal and the router or switching hub), Lists the access concentration line (path between the switching hub and the router) and link (path between the router and the router), the IP of the calling terminal, the IP of the called terminal, and the user ID that uses the route Yes. However, the calling terminal IP and the called terminal IP are not necessarily shown. It suffices if the IP address of the entry node and the IP address of the exit node of the route can be specified within the management range NWi of the resource management device.

Each route is given a “resource ID”. This resource ID is a unique identifier within the management range NWi of the resource management server RMSi. Therefore, by referring to the resource ID, it is possible to specify a path (a set of resources) within the management range NWi without enumerating access lines and links between nodes constituting the path.
Instead of “entrance node IP” and “exit node IP”, “entrance node ID” and “exit node ID” that are IDs (identifiers) of edge nodes that are gateways in the management range NWi are used. Also good.

  The resource management table 202 is a table that stores resource information managed by the resource management server body i1. For example, the resource management table 202 includes “resource ID”, “originating terminal IP”, “destination terminal IP”, “ingress node IP”, “exit node IP”, “resource capacity”, “resource details”, “source” It consists of items of “server ID”, “transmission source resource ID”, “transmission destination server ID”, and “transmission destination resource ID”.

Here, the “resource ID” identifies a route managed by the resource management server body i1, and is the same as the resource ID used in the route information 201 described above.
The “entrance node IP”, “exit node IP”, “resource capacity”, and “resource details” are also edge nodes that are entrances of routes within the management range NWi, respectively, as used in the route information 201 described above. IP address of the edge node serving as the exit of the route, the used capacity and total capacity of the resources connecting these nodes, and details of these resources. Note that “entrance node ID” and “exit node ID” may be used instead of “entrance node IP” and “exit node IP”.

  The “transmission source server ID” and “transmission destination server ID” are identifiers such as adjacent servers adjacent to the resource management server RMSi on the communication path between the calling terminal and the called terminal. More specifically, the “transmission source server ID” is an identifier of the transmission source of the request message, that is, the adjacent server RMSi-1 (or application server AS) that has transmitted the request message to the resource management server RMSi. The “destination server ID” is the identifier of the transmission destination of the request message, that is, the adjacent server RMSi + 1 that transmitted the request message from the resource management server RMSi.

The “transmission source resource ID” is a resource ID assigned to a route managed by the adjacent server RMSi-1 when the transmission source of the request message is the adjacent server RMSi-1. The path identified by the “source resource ID” in the management range NWi-1 of the adjacent server RMSi-1 is connected to the path identified by the “resource ID” in the management range NWi of the resource management server RMSi. Yes.
The “transmission destination resource ID” is a resource ID assigned to a route managed by the adjacent server RMSi + 1 that is the transmission destination of the request message. The path identified by the “transmission destination resource ID” in the management range NWi + 1 of the adjacent server RMSi + 1 is connected to the path identified by the “resource ID” in the management range NWi of the resource management server RMSi.

  Thus, in the resource management table 202, “resource ID” and “transmission source resource ID” and “route ID” that identify routes in the other management ranges NWi−1 and NWi + 1 connected to the route identified by this “resource ID”. The “transmission destination resource ID” is stored in association with “transmission source server ID” and “transmission destination server ID” for identifying the adjacent servers RMSi−1 and RMSi + 1 that manage the other management ranges NWi−1 and NWi + 1.

  The authentication information 203 is the user ID and password of the maintenance person of any or all resource management servers including the resource management server RMSi, and the main body of the resource management server RMSi from the operation browsing unit of any resource management server Used for identity verification when logging into i1.

2-2. Operation browsing part i3
As illustrated in FIG. 2, the operation browsing unit i3 includes a GUI (Graphical User Interface) unit 301, a data storage unit 302, a login authentication unit 303, a control unit 304, and a transmission / reception unit 305.

  Here, the GUI unit 301 operates the resource management server RMSi by operating graphical elements such as icons and windows displayed on the screen with a pointing device such as a mouse. In particular, it has a designation function for designating a resource management server and a route managed there, and a display function for displaying resource information of a designated route sent from the designated resource management server on the screen. In this embodiment, the resource management server is designated by the server ID given to the server, and the route is designated by the resource ID given to the route.

The data storage unit 302 stores authentication information such as the user ID and password of the maintenance person of the resource management server RMSi. This authentication information is used for identity verification when logging in to the operation browsing unit i3. In addition, in the data storage unit 302, the server IDs of all the resource management servers RMS1 to RMSn including the resource management server RMSi are associated with the IP addresses of the server main bodies 11 to n1 (transmission / reception unit 101). Is remembered.
The login authentication unit 303 performs identity verification when logging in to the operation browsing unit i3. For example, the user ID and password input to the GUI unit 301 are compared with the user ID and password stored in the data storage unit 302, and the user logs in when the two match and are confirmed to be the authorized user. Otherwise, do not log in.

  The control unit 304 creates various messages in accordance with operations on the GUI unit 301. Specifically, a login request message for requesting login to the main body of any resource management server including the resource management server RMSi, and a browsing request for requesting browsing of resource information managed by the main body of the resource management server Create a message. Authentication information such as a user ID and password input to the GUI unit 301 is added to the login request message. The resource ID corresponding to the route specified in the GUI unit 301, the IP address of the transmission / reception unit 305 of the operation browsing unit i3 that created this message, and other information are added to the browsing request message.

  The transmission / reception unit 305 includes a communication interface, transmits / receives various messages to / from a main body of an arbitrary resource management server including the resource management server RMSi, and receives resource information returned from the transmission destination of the browsing request message. .

2-3. Resource management server body i1
As shown in FIG. 2, the resource management server body i <b> 1 includes a transmission / reception unit 101, a resource management unit 102, a login authentication unit 103, and a maintenance operation unit 104.
Here, the transmission / reception unit 101 includes a communication interface, transmits / receives various messages to / from the application server AS, adjacent servers RMSi-1, RMSi + 1, and the operation browsing unit i3, and also transmits the browsing request message. Return resource information to

  The resource management unit 102 refers to the path information 201 and the resource management table 202 of the database unit i2 in response to a request message from the application server AS or the neighboring server RMSi-1 on the calling terminal side, and manages the resource management server RMSi Within the range NWi, resources necessary for communication are secured, and the secured resources are changed and released. The resource is secured by adding the capacity allocated to the communication to the currently used capacity in the “resource capacity” of the resource management table 202. Similarly, the resource is released by subtracting the capacity allocated to the communication from the currently used capacity in the “resource capacity”.

In addition, when securing a resource or the like, if the destination terminal of the communication is not within its own management range NWi, a request message to be transmitted to the adjacent server RMSi + 1 on the destination terminal side is created. On the other hand, when the destination terminal of the communication is within its own management range NWi, a response message to be returned to the transmission source of the request message is created as necessary.
Furthermore, a response message to be returned to the transmission source of the request message is created also when a response message returned from the adjacent server RMSi + 1 on the called terminal side that is the transmission destination of the request message is received.

The login authentication unit 103 performs identity verification at the time of login from the operation browsing unit i3 to the resource management server body i1. Here, “login from the operation browsing unit i3” includes not only the resource management server RMSi but also login from the operation browsing unit i3 of another resource management server.
The identity verification in the login authentication unit 103 is performed as follows. First, authentication information such as a user ID and password added to the login request message received by the transmission / reception unit 101 is compared with the authentication information 203 stored in the database unit i2. As a result, when the two match and it is confirmed that the sender of the login request message is the authorized user, the login is performed. Otherwise, the login is not performed.

  The maintenance operation unit 104 receives various messages from the operation browsing unit i3 and performs processing necessary for maintenance and operation of the resource management server RMSi. Specifically, in response to the browsing request message, the resource management unit 102 is controlled, and the resource information of the route specified by the resource ID added to the browsing request message is read from the resource management table 202 of the database unit i2. And output to the transmitting / receiving unit 101. The maintenance operation unit 104 can perform the above-described process only when the login authentication unit 103 logs in.

2-4. Data management method of resource management table 202 In the resource management system according to the present embodiment, when two terminals (source terminal and destination terminal) that communicate with each other belong to different management ranges, the management range NW1 with the source terminal is set. By transmitting a request message from the managed resource management server RMS1 to the resource management server RMSn that manages a certain management range NWn of the called terminal and returning a response message to the request message through the reverse route, a plurality of management ranges NW1 to NW1 A series of resources extending over NWn is managed in cooperation with a plurality of resource management servers RMS1 to RMSn.
Further, using the exchange of the request message and the response message, various data of the resource management table 202 are set in each resource management server. Hereinafter, a data setting method will be described.

The resource securing request message includes “request source server IP”, “exit node IP”, “originating terminal IP”, “destination terminal IP”, “resource amount”, “source server ID”, and “source resource ID”. Etc. are added. Here, the “request source server IP” is the IP address of the server that first created the request message, that is, the application server AP. The “resource amount” is a resource amount to be secured by communication. Items other than these correspond to the items in the resource management table 202, respectively.
A case where such a resource securing request message is transmitted from the adjacent server RMSi-1 to the resource management server RMSi will be described.

  When the transmission / reception unit 101 of the main body i1 of the resource management server RMSi receives the resource reservation request message, the resource management unit 102 determines from the “source terminal IP” or “exit node IP” and “destination terminal IP” of the resource reservation request message. Then, the route information 201 in the database unit i2 is referred to search for a route in its own management range NWi, and resources are secured for this route as described above. Then, the “resource ID” of the route is recorded in the resource management table 202 of the database unit i2 together with the “entry node IP”, “exit node IP”, “resource capacity”, and “resource details”. At this time, the “source terminal IP”, “destination terminal IP”, “source server ID”, and “source resource ID” added to the resource securing request message are recorded in association with the “resource ID”. .

  Further, when the called terminal is not within its own management range NWi, a resource securing request message is created and transmitted from the transmitting / receiving unit 101 to the adjacent server RMSi + 1 on the called terminal side. In this resource reservation request message, the “request source server IP”, “source terminal IP”, “destination terminal IP”, and “resource amount” added to the resource reservation request message received by the transmission / reception unit 101 are added as they are. . Further, the server ID of the resource management server RMSi as the transmission source is added as a “transmission source server ID”. Further, the resource ID and the egress node IP in the own management range NWi are added as “source resource ID” and “egress node IP”, respectively.

  On the other hand, when the destination terminal is within its own management range NWi, a response message indicating that the resource has been successfully secured is created and returned to the source of the resource securing request message. The “request source server IP” and the “transmission source resource ID” added to the resource securing request message received by the transmission / reception unit 101 are added to the response message as they are. Further, the server ID and resource ID of the resource management server RMSi that is the transmission destination when viewed from the transmission source of the resource securing request message are added to the response message as “transmission destination server ID” and “transmission destination resource ID”, respectively.

Next, a case will be described in which a response message is returned from the adjacent server RMSi + 1 on the called terminal side that is the transmission destination of the resource securing request message to the resource management server RMSi.
The “transmission source resource ID” added to the response message is nothing but a resource ID for specifying a route in the own management range NWi in the resource management server RMSi that receives the response message. Accordingly, when the transmission / reception unit 101 of the resource management server body i1 receives the response message, the resource management unit 102 associates the resource ID with the “transmission destination server ID” and “transmission destination resource ID” added to the response message. Is recorded in the resource management table 202 of the database unit i2.

  Also, a response message is created, the “transmission source server ID” recorded in the resource management table 202 is read in association with the resource ID, and a response is sent to the adjacent server RMSn−1 specified by this “transmission source server ID”. Reply message. The “request source server IP” added to the response message received by the transmission / reception unit 101 is added to the response message as it is. Further, the server ID and resource ID of the resource management server RMSi are added to the response message as “transmission destination server ID” and “transmission destination resource ID”, respectively. Further, a “transmission source resource ID” recorded in the resource management table 202 is associated with the resource ID.

3. Operation of Resource Management System Next, the operation of the resource management system according to the present embodiment will be described.

3-1. Browsing Resource Information Managed by Own Resource Management Server The operation of the resource management server when browsing resource information managed by its own resource management server will be described with reference to FIG. Here, a case where the resource information managed by the main body 21 of the resource management server RMS2 is browsed by the operation browsing unit 23 of the resource management server RMS2 will be described as an example.

  When the maintenance person of the resource management server RMS2 activates the operation browsing unit 23 (step S11) and inputs the user ID and password of the maintenance person to the GUI unit 301 of the operation browsing unit 23 (step S12, YES), the operation browsing unit 23 Sends the entered user ID and password to the login authentication unit 303. Then, the login authentication unit 303 collates the input user ID and password with the user ID and password stored in the data storage unit 302. As a result, when it is confirmed that the two match and are the authorized user (step S13, OK), login (step S14), otherwise (step S13, NG), login rejection is displayed on the GUI unit 301. (Step S15). When logging in, the input user ID and password are stored in the login authentication unit 303 until logging out.

  When logged in, a menu is displayed on the screen of the GUI unit 301. At this time, a button for browsing the resource information managed by the resource management server RMS2 is also displayed. When the maintenance person clicks this button (step S16, YES), the operation browsing unit 23 creates a login request message in the control unit 304 in order to log in to the resource management server main body 21, and the resource management server main body from the transmission / reception unit 305. 21 (step S17). A user ID and a password input by the maintenance person stored in the login authentication unit 303 are added to the login request message.

  When the transmission / reception unit 101 receives the login request message from the operation browsing unit 23, the resource management server body 21 extracts the user ID and password added to the login request message and sends them to the login authentication unit 103. Then, the login authentication unit 103 collates the user ID and password added to the login request message with the authentication information 203 stored in the database unit 22. As a result, if both match and it is confirmed that the sender of the login request message is the authorized user (step S18, OK), the user logs in and between the resource management server body 21 and the operation browsing unit 23. A TCP connection is established (step S19).

On the other hand, when the two do not match as a result of the collation, the resource management server main body 21 creates a login rejection message and sends it back to the operation browsing unit 23 (step S20).
The operation browsing unit 23 that has received this login rejection message displays on the GUI unit 301 that the login is rejected to the resource management server main body 21 (step S21), and requests re-input of the user ID and password. When the maintenance person re-enters the user ID and password (step S22, YES), the operation browsing unit 23 creates a login request message to which the newly input user ID and password are added in the control unit 304, and transmits and receives Retransmission from 305 to the resource management server main body 21 (step S17).

  In step S19, when the login to the resource management server main body 21 is successful, the operation browsing unit 23 creates a browsing request message in the control unit 304 and acquires the transmission / reception unit 305 in order to acquire resource information from the resource management server main body 21. To the resource management server main body 21 (step S23).

  When the transmission / reception unit 101 receives the browsing request message from the operation browsing unit 23, the resource management server body 21 controls the resource management unit 102 by the maintenance operation unit 104 and reads the resource information from the resource management table 202 of the database unit 22. (Step S24), the read resource information is returned from the transmission / reception unit 101 to the operation browsing unit 23 (Step S25). At this time, all items of the resource information may be read and returned, or some items may be read and returned. In this embodiment, it is assumed that data of “resource ID”, “resource capacity”, “resource details”, “transmission source server ID”, and “transmission destination server ID” are read and returned.

The operation browsing unit 23 that has received the resource information sends the resource information to the GUI unit 301 and displays it on the screen (step S26).
In the GUI unit 301, resource information is displayed as shown in FIG. 4, for example. In this example, items “link (used capacity / total capacity)”, “source server”, and “destination server” are displayed on the screen.
Here, “link (capacity currently used / total capacity)” is a summary of the number of the link constituting the route in the management range NW2 of the resource management server RMS2, the total capacity of the link, and the capacity currently being used. Displayed.

In addition, in “transmission source server” and “transmission destination server”, adjacent servers connected to the route are displayed. When the name of the adjacent server is set, the name (“RMS1” in FIG. 4) is displayed. When the name is not set, the ID of the adjacent server (“281.0.556 in FIG. 4) is displayed. ”) Is displayed as it is. When the source terminal or the destination terminal exists in the management range NW2 of the resource management server RMS2, there is no transmission source server or transmission destination server, so each item is blank (in FIG. 4, “transmission source server” ”Column in the second column and“ destination server ”column in the fifth column)
FIG. 4 shows a state in which five sets of communications are currently being performed using resources managed by the resource management server RMS2. These communications pass through different paths, as can be seen from the column “Link (capacity in use / total capacity)”.

3-2. Browsing Resource Information Managed by Adjacent Server Next, the operation of the resource management server when browsing the resource information managed by the adjacent server will be described with reference to FIG. Here, a case where the resource information managed by the main body 31 of the adjacent server RMS3 is browsed by the operation browsing unit 23 of the resource management server RMS2 will be described as an example.

  It is assumed that resource information managed by the resource management server RMS2 is displayed on the GUI unit 301 as shown in FIG. For example, when the resource information of the route in the management range NW3 of the adjacent server RMS3 connected to the first-step route in the “link (used capacity / total capacity)” column is to be browsed, Click on the first path in the “Medium capacity / Total capacity)” column to select this path. When the display button 311 is clicked in this state, pull-down menus (not shown) of “transmission source server” and “transmission destination server” are displayed, and among these, “transmission destination server” is clicked. Alternatively, double-click the first row in the “destination server” field displayed on the screen. As a result, one of the plurality of routes in the management range NW2 of the resource management server RMS2 and the adjacent server RMS3 that is a transmission destination server connected to this route are designated (step S31).

  When the route and the adjacent server RMS3 are specified in this way, the operation browsing unit 23 sends the resource ID corresponding to the specified route and the ID (transmission destination ID) of the adjacent server RMS3 from the GUI unit 301 to the control unit 304. . First, in order to log in to the main body 31 of the designated adjacent server RMS3, the control unit 304 creates a login request message, and transmits it from the transmission / reception unit 305 to the main body 31 of the adjacent server RMS3 (step S32). A user ID and a password input by the maintenance person stored in the login authentication unit 303 are added to the login request message. Further, the IP address of the main body 31 of the adjacent server RMS3 can be obtained by searching the data storage unit 302 using the ID of the adjacent server RMS3 as a key.

  When the transmission / reception unit 101 receives the login request message from the operation browsing unit 23 of the resource management server RMS2, the main body 31 of the adjacent server RMS3 extracts the user ID and password added to the login request message, and the login authentication unit 103. Then, the login authentication unit 103 collates the user ID and password added to the login request message with the authentication information 203 stored in the database unit 32. As a result, if both match and it is confirmed that the sender of the login request message is the authorized user (step S33, OK), the user logs in and operates the main body 31 of the adjacent server RMS3 and the resource management server RMS2. A TCP connection is established with both the browsing unit 23 (step S34).

On the other hand, as a result of the collation, when the two do not match, the main body 31 of the adjacent server RMS3 creates a login rejection message and sends it back to the operation browsing unit 23 of the resource management server RMS2 (step S35).
Receiving this login rejection message, the operation browsing unit 23 of the resource management server RMS2 displays on the GUI unit 301 that the login is rejected to the main body 31 of the adjacent server RMS3 (step S36), and re-establishes the user ID and password. Ask for input. When the maintenance person re-enters the user ID and password (step S37, YES), the operation browsing unit 23 creates a login request message with the newly entered user ID and password in the control unit 304, and transmits and receives the transmission / reception unit. From 305, the message is retransmitted to the main body 31 of the adjacent server RMS3 (step S32).

  In step S34, when the login to the main body 31 of the adjacent server RMS3 is successful, the operation browsing unit 23 of the resource management server RMS2 requests a browsing request in the control unit 304 in order to acquire resource information from the main body 31 of the adjacent server RMS3. A message is created and transmitted from the transmission / reception unit 305 to the main body 31 of the adjacent server RMS3 (step S38). In this browsing request message, the resource ID corresponding to the route specified in step S31 is added as “source resource ID”. The resource ID is added as “source resource ID” because the resource ID in the resource management server RMS2 corresponds to the resource ID in the source of the resource securing request message, that is, the source resource ID when viewed from the adjacent server RMS3. Because it does. Similarly, when the adjacent server RMS1 that is the transmission source server is designated in step S31, the resource ID is added as a “transmission destination resource ID” to the browsing request message.

  When the main body 31 of the adjacent server RMS3 receives the browsing request message from the operation browsing unit 23 of the resource management server RMS2 in the transmission / reception unit 101, the maintenance operation unit 104 extracts the transmission source resource ID added to the browsing request message. To do. Then, the resource management unit 102 is controlled, and the resource information associated with the transmission source resource ID is read with reference to the resource management table 202 of the database unit 32 (step S39). This resource information is resource information of a route in the management range NW3 of the adjacent server RMS3 connected to the route specified in step S31. Therefore, the read resource information is returned from the transmission / reception unit 101 to the operation browsing unit 23 of the resource management server RMS2 (step S40).

The operation browsing unit 23 of the resource management server RMS2 that has received this resource information sends the resource information to the GUI unit 301 and displays it on the screen (step S41).
In the GUI unit 301, the resource information of the adjacent server RMS3 is displayed, for example, as shown in FIG. In FIG. 6, the name “RMS2” of the resource management server RMS2 is displayed in the “source server” column.

In this way, when it is desired to view the resource information of the adjacent server RMS4 while the resource information of the adjacent server RMS3 is displayed on the screen, the operations of steps S31 to S41 may be repeated.
By repeatedly performing such resource information browsing processing, even if a series of communication paths from the calling terminal to the called terminal spans the management range of a plurality of resource management servers, the resource information of the communication path is It can be browsed by the GUI unit 301 of the resource management server RMS2.

As a result, the maintenance person of the resource management server RMS2 can provide a specific failure when a failure occurs in a series of routes, even if the failure occurs within the management range of any resource management server. The location can be specified.
In addition, since the resource information of the designated route within the management range of the resource management server designated by the maintenance person is displayed on the GUI unit 301, the maintenance person needs to consider the connection of a series of routes across a plurality of management ranges. Disappears.

3-3. 6 shows an example in which only the resource information of the adjacent server RMS3 is displayed in the “link (capacity currently used / total capacity)” column. However, the resource information of the resource management server RMS2 in a series of routes is shown. And the resource information of the adjacent server RMS3 may be connected and displayed.

  In the present embodiment, an example is shown in which a route for browsing resource information is specified in step S31 of FIG. 5, but a route need not be specified. In this case, since the resource ID is not added to the browse request message created in step S38 of FIG. 5, the main body 31 of the adjacent server RMS3 that has received this browse request message reads all the resource information from the database unit 32. (Step S39 in FIG. 5), the response is returned to the operation browsing unit 23 of the resource management server RMS2 (Step S40 in FIG. 5). Thereby, all the resource information of the adjacent server RMS3 is displayed on the GUI unit 301 of the operation browsing unit 23 (step S41 in FIG. 5).

  In this case, the resource information of the resource management server RMS2 and the resource information of the adjacent server RMS3 may be displayed on the GUI unit 301 at the same time. The resource information in a series of routes may be displayed in a connected manner as described above.

3-4. Method for specifying a route within the management range of an adjacent server When browsing resource information of an adjacent server, an example in which “resource ID” in the resource management server is used as a method for specifying a route within the management range of the adjacent server will be described. However, the following method can also be adopted.

(1) Resource ID in the adjacent server ("transmission source resource ID" or "transmission destination resource ID" in the resource management server)
When the resource ID in the adjacent server, that is, the “transmission source resource ID” or the “transmission destination resource ID” in the resource management server is used, when the resource information of the resource management server is read from the resource management table 202, the “transmission source The “resource ID” and the “destination resource ID” are also read together (step S24 in FIG. 3) and sent to the GUI unit 301 (step S25 in FIG. 3). Then, in the browsing process of the resource information of the adjacent server, the “transmission source resource ID” or “destination resource ID” corresponding to the designated route is added to the browsing request message and sent to the main body of the adjacent server (FIG. 5). Step S38). The “transmission source resource ID” or “transmission destination resource ID” in the resource management server corresponds to the “resource ID” in the adjacent server. Therefore, the resource information associated with the resource ID is read from the resource management table 202 by the main body of the adjacent server and returned (steps S39 and S40 in FIG. 5), so that the GUI unit 301 of the resource management server performs the adjacent server. Resource information of a desired route within the management range can be displayed (step S41 in FIG. 5).

  If a resource ID is assigned to a series of routes from the calling terminal to the called terminal, this resource ID can also be used. In this case, it is necessary to record the resource ID assigned to the series of paths in the resource management table 202 of each resource management server.

(2) Called terminal IP (IP address of the called terminal that performs communication)
When the destination terminal IP is used, when the resource information of the resource management server is read from the resource management table 202, the “terminated terminal IP” is also read together (step S24 in FIG. 3) and sent to the GUI unit 301 (FIG. 3). Step S25). Then, in the browsing process of the resource information of the adjacent server, “Destination terminal IP” corresponding to the designated route is added to the browsing request message and sent to the main body of the adjacent server (step S38 in FIG. 5). The main body of the adjacent server reads out the resource information associated with the “destination terminal IP” from the resource management table 202 and sends it back (steps S39 and S40 in FIG. 5), so that the GUI unit 301 of the resource management server Resource information of a desired route within the management range of the adjacent server can be displayed (step S41 in FIG. 5).

  Similarly, the IP prefix (set of IP addresses) of the called terminal or the ID (identifier) of the called terminal can be used. In this case, it is necessary to record the IP prefix or ID of the called terminal in the resource management table 202 of each resource management server.

(3) Originating terminal IP (IP address of originating terminal that performs communication) and terminating terminal IP (IP address of terminating terminal that performs communication)
A specific method is the same as that when the destination terminal IP is used.
In addition, the IP prefix (or ID (identifier)) of the calling terminal and the IP prefix (or ID (identifier)) of the called terminal can be used. In these cases, it is necessary to record each information in the resource management table 202 of each resource management server.

(4) ID (identifier) of the resource management server
When the ID of the resource management server is used, the ID of the resource management server is added to the browsing request message and sent to the main body of the adjacent server (step S38 in FIG. 5). The ID of the resource management server corresponds to “transmission source ID” or “transmission destination ID” in the adjacent server. Therefore, when the resource information associated with the “transmission source ID” or “transmission destination ID” is read from the resource management table 202 by the main body of the adjacent server and returned (steps S39 and S40 in FIG. 5), the resource information The resource information of a desired route within the management range of the adjacent server can be displayed by the GUI unit 301 of the management server (step S41 in FIG. 5).

  Similarly, the IP address of the resource management server can be used. In this case, it is necessary to record the IP address of the resource management server in the resource management table 202 of each resource management server.

In addition, what identifies a route within the management range of the resource management server is defined as first identification information. Specifically, the resource ID in the resource management server corresponds to the first identification information.
Moreover, what identifies the path | route in the management range of an adjacent server is defined as 2nd identification information. Specifically, the resource ID in the adjacent server corresponds to the second identification information.
Resource ID given to a series of routes from the calling terminal to the called terminal, called terminal IP (or called terminal IP prefix, or called terminal ID), calling terminal IP (or calling terminal IP prefix, or calling terminal ID) And the destination terminal IP (or destination terminal IP prefix or destination terminal ID) are included in both the first and second identification information.

3-5. Release of resources secured by the resource management server As described above, the resource management server RMSi (i = 1 to n) secures necessary resources within its own management range NWi upon receiving a resource securing request message, Releases the resources already secured in response to the release request message.

  However, for example, when the resource management server RMS2 receives a resource securing request message and secures a resource, and communication with the adjacent server RMS1 that is the transmission source of the resource securing request message becomes impossible, it is between the sending and receiving terminals. The resource release request message that should be sent from the adjacent server RMS1 after the end of the communication cannot be received by the resource management server RMS2, and the resources reserved for the communication cannot be released even after the end of the communication. . In addition, when the resource management server RMS2 secures a resource and transmits a resource securing request message to the adjacent server RMS3, if the adjacent server RMS3 or further server fails and the resource cannot be secured, as a result, the calling terminal A series of resources from the terminal to the destination terminal cannot be secured.

In such a case, keeping resources that are not used for communication in the resource management server RMS2 hinders effective use of resources.
Therefore, a method for releasing resources in a pseudo manner by a maintenance person of the resource management server RMS2 will be described below.

3-5-1. Release of resources secured by own resource management server First, the operation of the resource management server RMS2 when releasing resources secured by the own resource management server RMS2 will be described with reference to FIG.
The resource information managed by the resource management server RMS2 is displayed on the screen of the GUI unit 301 as shown in FIG. 4, and between the operation browsing unit 23 of the resource management server RMS2 and the server main body 21. It is assumed that a TCP connection is established.

  For example, in the case where it is desired to release a resource related to the first-stage route in the “link (used capacity / total capacity)” column in FIG. 4, the maintenance person first selects “link (used capacity / total capacity)”. Click the first path in the column to select this path, and click the release button 312 in this state. As a result, a route for releasing the resource is designated from among a plurality of routes in the management range NW2 of the resource management server RMS2 (step S51).

  When the route is designated in this way, the operation browsing unit 23 sends a resource ID corresponding to the designated route from the GUI unit 301 to the control unit 304. Then, in order to release the resources related to the designated route, the control unit 304 creates a resource release request message (resource processing request message) and transmits it from the transmission / reception unit 305 to the resource management server main body 21 (step S52). A resource ID corresponding to the route specified in step S51 is added to this resource release request message.

  When the resource management server body 21 receives the resource release request message from the operation browsing unit 23 in the transmission / reception unit 101, the maintenance operation unit 104 extracts the resource ID added to the resource release request message. Then, the resource management unit 102 is controlled, the resource information associated with the resource ID is searched with reference to the resource management table 202 of the database unit 22, and the resource information is deleted from the resource management table 202. Thereby, resources related to the designated route are released (step S53).

3-5-2. Release of Resources Secured by Adjacent Servers Next, operations of the resource management servers RMS2 and RMS3 when releasing resources secured by the adjacent server RMS3 will be described with reference to FIG.
The resource information managed by the adjacent server RMS3 is displayed on the GUI unit 301 of the resource management server RMS2 as shown in FIG. 6, and the operation browsing unit 23 of the resource management server RMS2 and the adjacent server RMS3 are displayed. It is assumed that a TCP connection has been established with both the server main body 31.

  In order to release the resources related to the route in the “link (used capacity / total capacity)” column in FIG. 6, the maintenance person firstly selects the route in the “link (used capacity / total capacity)” column in FIG. 6. Click to select this route, and click the release button 312 in this state. As a result, a route from which resources are to be released is designated from among a plurality of routes within the management range NW3 of the adjacent server RMS3 (step S61).

  When the route is designated in this way, the operation browsing unit 23 sends a resource ID corresponding to the designated route from the GUI unit 301 to the control unit 304. Then, in order to release the resources related to the designated route, the control unit 304 creates a resource release request message and transmits it from the transmission / reception unit 305 to the main body 31 of the adjacent server RMS3 (step S62). A resource ID corresponding to the route specified in step S61 is added to the resource release request message.

  When the body 31 of the adjacent server RMS3 receives the resource release request message in the transmission / reception unit 101, the maintenance operation unit 104 extracts the resource ID added to the resource release request message. Then, the resource management unit 102 is controlled, the resource information associated with the resource ID is searched with reference to the resource management table 202 of the database unit 32 of the adjacent server RMS3, and the resource information is deleted from the resource management table 202 To do. Thereby, the resource concerning the route in the management range NW3 of the adjacent server RMS3 is released (step S63).

  Resources secured by other resource management servers can be released in the same manner. Therefore, even when a series of communication paths from the source terminal to the destination terminal extends over the management range of a plurality of resource management servers, the resources related to the communication paths are simulated from the GUI unit 301 of the resource management server RMS2. Can be released to.

Here, the case where the TCP connection is established between the operation browsing unit 23 and the resource management server main body 21, 31, etc. has been described, but if the TCP connection is not established, the operation browsing unit 23 It is necessary to log in to the resource management server main body 21, 31 or the like. Specifically, steps S17 to S22 in FIG. 3 are performed between steps S51 and S52 in FIG. 7, and steps S32 to S37 in FIG. 5 are performed between steps S61 and S62 in FIG. It will be.
In addition, the pseudo-release of the resources secured by the resource management server has been described, but it is also possible to perform pseudo-change of the secured resources and other processes.

3-6. Management authority of maintenance personnel Management authority granted to maintenance personnel, such as browsing resource information and releasing resources, can be individually set for each maintenance personnel. For example, “maintenance person A of resource management server RMS2 is allowed to view resource information of resource management server RMS2, but is not allowed to release resources”, “maintenance person B of resource management server RMS2 is “Although browsing of resource information of the management server RMS2 is permitted, but browsing of resource information of other resource management servers is not permitted”, “the resource information of the resource management server RMS4 is for maintenance personnel of the resource management servers 3, 4, 5” “Although browsing is permitted, but maintenance is not permitted for other resource management server maintainers” can be set.

Specifically, the management authority is set in the operation browsing unit i3 or the database unit i2 of the resource management server RMSi (i = 1 to n).
When setting to the operation browsing unit i3, the data storage unit 302 records management authority data representing the management authority granted to the maintenance person in association with the user ID of the maintenance person. This management authority data is sent to the GUI unit 301 via the login authentication unit 303 at the time of logging in to the operation browsing unit i3, so that the maintenance person cannot perform an action that is not permitted by the management authority data in the GUI unit 301. For example, a maintenance person is prevented from pressing a button for performing an unacceptable action among a plurality of buttons displayed on the screen.

  In the case of setting in the database unit i2, in the authentication information 203, management authority data representing management authority granted to the maintenance person is recorded in association with the user ID of the maintenance person. This management authority data is sent to the maintenance operation unit 104 via the login authentication unit 103 at the time of login to the resource management server main body i1, so that the maintenance person cannot perform an act not permitted by the management authority data in the maintenance operation unit 104. To do. For example, when a request message for performing an unauthorized action is sent from the maintenance person, a response is made to reject the request.

  The present invention can be used for a high-quality communication service using a wide area communication network.

It is a block diagram which shows the outline | summary of the resource management system concerning one embodiment of this invention. It is a functional block diagram of a resource management server. It is a flowchart which shows the flow of operation | movement of the resource management server at the time of browsing the resource information managed by the own resource management server. It is a figure which shows an example of the screen display of the resource information (resource information managed by the own resource management server) in a GUI part. It is a flowchart which shows the flow of operation | movement of the resource management server at the time of browsing the resource information managed by the adjacent server. It is a figure which shows an example of the screen display of the resource information (resource information managed by the adjacent server) in a GUI part. It is a flowchart which shows the flow of operation | movement of a resource management server at the time of releasing the resource ensured by the own resource management server. It is a flowchart which shows the flow of operation | movement of the resource management server at the time of releasing the resource ensured by the adjacent server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 ... Transmission / reception part, 102 ... Resource management part, 103 ... Login authentication part, 104 ... Maintenance operation part, 201 ... Path information, 202 ... Resource management table, 203 ... Authentication information, 301 ... GUI part, 302 ... Data storage part, 303 ... Login authentication unit, 304 ... Control unit, 305 ... Transmission / reception unit, 311 ... Display button, 312 ... Release button, i1 ... Resource management server body, i2 ... Database unit, i3 ... Operation browsing unit, AS ... Application server, NWi ... management range (communication network), Ri1 to Ri4 ... router, RMSi ... resource management server, T11, T12, Tn1, Tn2 ... terminal (above, i = 1 to n).

Claims (11)

A resource management device is provided for each of a plurality of management ranges obtained by dividing a communication network composed of a plurality of routers and terminals linked to each other, and manages resources in each management range,
Resource information storage means for storing resource information related to resources managed by the resource management device together with identifiers of other resource management devices that manage other management ranges adjacent to the management range of the resource management device;
Browsing request means for creating and sending a browsing request message for requesting browsing of resource information related to resources managed by the other resource management device to the other resource management device specified by the identifier;
Display means for displaying the resource information in the other resource management device ,
The resource information storage means stores identification information for identifying a communication path between two terminals that perform communication as one of the resource information,
The browsing request means adds the identification information to the browsing request message . The resource management device according to claim 1,
A browsing request message receiving means for receiving a browsing request message from another resource management device that manages another management range adjacent to the management range of the resource management device;
Resource information reading means for reading the resource information from the resource information storage means in response to the received browsing request message;
A resource management device, further comprising: a display enabling unit that displays the read resource information on the other resource management device. The resource management device according to claim 1 ,
The resource management device is characterized in that the resource information reading means reads resource information relating to a resource of a communication path specified by identification information added to the browsing request message. The resource management device according to claim 2,
A resource management apparatus, further comprising: a login request unit that creates and transmits a login request message to which authentication information used for identity verification is added to the other resource management apparatus specified by the identifier. The resource management apparatus according to claim 4 , wherein
Authentication information storage means for storing authentication information used for identity verification;
By confirming the authentication information added to the received login request message and the authentication information stored in the authentication information storage means, it is confirmed that the sender of the login request message is the authorized user. Further comprising an authentication means,
The resource information reading unit reads the resource information when the authenticating unit confirms that the sender of the login request message is an authorized user. A resource management method for dividing a communication network composed of a plurality of routers and terminals linked to each other into a plurality of management ranges, and managing resources of the communication network by a resource management device provided for each of these management ranges There,
A storage step of storing, in a first storage means, an identifier of another resource management device that manages another management range adjacent to the management range of the one resource management device;
A browsing request step for creating and transmitting a browsing request message for requesting browsing of resource information related to resources managed by the other resource management device to the other resource management device specified by the identifier;
A display step for displaying the resource information in the other resource management device ,
The first storage means further stores identification information for identifying a communication path between two terminals performing communication,
The browsing request step adds the identification information to the browsing request message . The resource management method according to claim 6 , wherein
In the other resource management device, a storage step of storing resource information related to resources managed by the other resource management device in a second storage unit;
A browsing request message receiving step of receiving the browsing request message from the one resource management device;
A resource information reading step of reading the resource information from the second storage means in response to the received browsing request message;
A display enabling step of displaying the read resource information on the one resource management apparatus. The resource management method according to claim 6 , wherein
The resource information reading step reads resource information relating to a resource of a communication path specified by identification information added to the browsing request message. The resource management method according to claim 7 , wherein
The one resource management device further includes a login request step of creating and transmitting a login request message to which authentication information used for identity verification is added to the other resource management device specified by the identifier. Resource management method. The resource management method according to claim 9 , wherein
In the other resource management device, by verifying the authentication information added to the received login request message and the authentication information stored in the authentication information storage means, the sender of the login request message is the authorized user. And further comprising an authentication step for confirming that
The resource information reading step reads the resource information when it is confirmed by the authentication step that the sender of the login request message is an authorized user. A resource management system that divides a communication network composed of a plurality of routers and terminals linked to each other into a plurality of management ranges, and manages resources of the communication network by a resource management device provided for each of these management ranges There,
One resource management device
First storage means for storing an identifier of another resource management device that manages another management range adjacent to the management range of the one resource management device;
Browsing request means for creating and sending a browsing request message for requesting browsing of resource information related to resources managed by the other resource management device to the other resource management device specified by the identifier;
Display means for displaying the resource information in the other resource management device,
The other resource management device is:
Second storage means for storing resource information related to resources managed by the other resource management device;
Browsing request message receiving means for receiving the browsing request message from the one resource management device;
Resource information reading means for reading out the resource information from the second storage means in response to the received browsing request message;
Display enabling means for displaying the read resource information on the one resource management device ,
The first storage means stores identification information for identifying a communication path between two terminals performing communication as one of the resource information,
The browsing request means adds the identification information to the browsing request message .

Images