JP2006165640A - Resource management method, resource management apparatus, and resource management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To make it possible to ensure a series of resources with respect to a resource assurance request over a plurality of management ranges. <P>SOLUTION: A resource management server (RMS 1) for receiving a request message discriminates whether or not a destination terminal on a requested communication exists within a management range of the resource management server on the basis of the received request message, and when the resource management server discriminates that the destination terminal does not exist within the management range (NW1) of the resource management server, the resource management server reserves resources required in the management range (NW1) of the resource management server and transmits the request message to another resource management server (RMS 2) for managing the other adjacent management range (NW2). <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a resource management method, a resource management apparatus, and a resource management system for managing resources in 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 has been studied for the purpose of preventing such deterioration of communication quality.

  Resource management by the resource management device is performed by a server (hereinafter referred to as “resource management server” or “resource management device”) that is independent of the router that constitutes the communication network, and the transmission capacity between nodes (links) that constitute the communication network. In addition to managing the usage status, appropriate resources are 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 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 storage device. At the same time, the resource capacity of each link is stored. The stored route is called “route table”, and the resource capacity of each link is called “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 the operation of the communication network is started, when the resource management server accepts a communication service use request (resource securing request), the resource management server is required for the communication from the route table based on the 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, if necessary resources cannot be secured, the use request is not permitted (see Patent Document 1 and Non-Patent Document 1).
In addition, when the use of the resource is finished, the resource that has been reserved for communication must be promptly released.

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 a communication network becomes large, the resources that must be managed become enormous, and the resource securing requests that the resource management device should deal with increase. Therefore, one resource management device manages the resources of the entire communication network. It becomes difficult.
In order to deal 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 devices in these management ranges. In addition, resource management apparatuses exist in communication networks operated by different operators. When connecting a plurality of these communication networks, it can be considered that a large communication network is divided for each business operator, and a resource management device is provided for each business operator's communication network.
In such a communication network, when the calling terminal and the called terminal that perform communication belong to different management ranges, resources are separately secured within the respective management ranges.

However, a resource securing request that spans a plurality of management ranges includes a source terminal or a destination terminal that is not within the management range of the resource management device, so that the conventional resource management device can respond to such a resource securing request. There was a problem that I could not.
Also, even if a resource securing request that spans multiple management ranges can be met, each resource management device can only secure resources within its own management range, so resources are secured within any one management range. If this is not possible, even if resources can be secured in all other resource management devices, the resources must be secured again after rollback. Furthermore, even if each resource management device can secure resources within the respective management ranges, more time is required to match those reserved resources between the management ranges.
Therefore, in response to a resource securing request that spans multiple management ranges, if each resource management device secures resources separately within each management range, a large amount of processing time is required until the necessary resources are secured. In reality, it is difficult to secure a series of resources.

  An object of the present invention is to enable a series of resources to be secured in response to a resource securing request that spans a plurality of management ranges.

In order to solve the above-described problems, the present invention secures a series of resources in cooperation with a plurality of resource management apparatuses in response to a request regarding resources that span a plurality of management ranges.
Specifically, in the first resource management method according to the present invention, a communication network composed of a plurality of routers and terminals linked to each other is divided into a plurality of management ranges, and provided for each of these management ranges. A resource management method for managing resources of the communication network by a plurality of resource management apparatuses, wherein a request message including at least an identifier of a called terminal in a requested communication and a resource amount to be secured is received in one resource management apparatus A first reception step, a determination step for determining whether or not the destination terminal corresponding to the identifier included in the received request message is within a management range of the resource management device, and a result of the determination step When it is determined that the destination terminal is not within the management range of the resource management device, the resource management While securing the necessary resources within the management range of location, and a first transmission step of transmitting the request message to another resource management apparatus for managing the resources of the adjacent other management range.

  In this resource management method, when the destination terminal corresponding to the identifier included in the received request message is not within the management range of the resource management apparatus, that is, a request message regarding a resource that spans a plurality of management ranges is received. A plurality of resources by securing the necessary resources within the management range of the resource management device and transmitting the request message to another resource management device that manages resources in other adjacent management ranges. A series of resources is secured via the management device.

  In the resource management method described above, the other resource management device that has received the request message does not necessarily need to send a response to the request to the source management device that is the transmission source of the request message. As a second resource management method, when it is determined in the determination step that the destination terminal is within the management range of the resource management device, the necessary resources are secured within the management range of the resource management device, and the Instead of sending the request message, a response message may be sent to the sender of the request message.

  In addition to the above steps, the third resource management method according to the present invention further includes a second reception step of receiving a response message from the other resource management device at the resource management device, and the response message. And a second transmission step of transmitting a response message to the transmission source of the request message for the resource management device.

In this resource management method, when a response message from another resource management device is received by the resource management device, the response message is transmitted to the transmission source of the request message for the resource management device.
Whether or not a series of resources could be secured in response to a resource securing request that spans multiple management ranges by transmitting a response message from another resource management device to the source of the previous request message. Can be confirmed.

  According to a fourth resource management method of the present invention, in the resource management method described above, the first transmission step uses the identifier of the resource management device that transmits the request message as the identifier of the transmission source of the request message. The response message is transmitted to another resource management device by adding to the request message, and the second transmission step sends the response message to the transmission source of the request message specified by the identifier of the transmission source included in the received request message. May be transmitted.

  In this resource management method, since the identifier of the resource management device that transmits the request message is added to the request message transmitted to the other resource management device, the other resource management device is based on this identifier. The resource management device that is to transmit the response message (which is the transmission source of the request message) is specified.

  The fifth resource management method according to the present invention further includes a first management step of assigning a first resource ID to a resource secured in the management range of the resource management device, and the first resource ID. And the identifier of the transmission source of the request message included in the request message received by the resource management device and the presence / absence of a response from another resource management device that is the transmission destination of the request message And a second management step.

In this resource management method, a first resource ID that identifies a resource secured by each resource management device is assigned. Therefore, the resources secured in each management range can be identified by this first resource ID.
Furthermore, the first resource ID, an identifier representing the transmission source of the request message included in the received request message, and the presence / absence of a response from another resource management device that is the transmission destination of the request message By storing them in association with each other, it is possible to manage the progress of securing a series of resources via a plurality of resource management devices in order in response to a resource securing request that spans a plurality of management ranges.

On the other hand, one form of the resource management method according to the present invention can further process a plurality of request messages in parallel by further including the following features.
That is, in the sixth resource management method according to the present invention, the request message further includes an identifier of a calling terminal in the requested communication, and is further included in the request message in response to reception of the request message. A third management step of storing the identifiers of the calling terminal and the called terminal, wherein the second sending step adds the stored identifiers of the calling terminal and the called terminal to the response message for transmission. It is a feature.

  In such a resource management method, each request message and response message includes the identifiers of the called terminal and the calling terminal in the requested resource. Therefore, the request message and the response message are distinguished by the identifiers of the called terminal and the calling terminal for each requested communication (that is, a series of resources to be secured).

  When processing a plurality of request messages in parallel, the seventh resource management method according to the present invention assigns a first resource ID to a resource secured in the management range of the resource management device. Management step, the first resource ID, the identifier of the other resource management device that is the transmission source of the request message, and the resource secured in the management range of the other resource management device, A fourth management step that associates and stores a second resource ID included in the request message, wherein the first transmission step adds the first resource ID to the request message and adds the first resource ID to the request message. The second transmission step transmits the second resource associated with the first resource ID. The source ID and transmits in addition to the response message.

In this resource management method, each resource management device manages the resource secured in its own management range by the first resource ID in the first management step, and in the request message in the first transmission step. The first resource ID is added and transmitted to the other resource management device.
Then, the other resource management device uses the first resource ID assigned to the resource secured in its own management range as the “related resource management device” and the request message received by the resource management device. The identifier of the transmitted (other) resource management device and the second resource ID included in the received request message, that is, the (other) resource management device that transmitted the request message is within its own management range. The resource ID assigned to the secured resource is stored in association with it.
Here, the second resource ID for the resource management apparatus is the first resource ID for the (other) resource management apparatus that transmitted the request message to the resource management apparatus.

When the resource management device transmits a response message to the (other) resource management device that is the source of the request message, the resource management device adds a second resource ID associated with the first resource ID to the response message. Then, this response message is transmitted to the resource management apparatus (which is the transmission source of the request message) that is specified based on the identifier that is also associated with the first resource ID (the second transmission step).
In the (other) resource management device that has received this response message, in association with the second resource ID included in the received response message, that is, the first resource ID for the (other) resource management device, The identifier of the resource management device to which the response message is to be transmitted and the resource ID secured in the resource management device (second resource ID for the (other) resource management device) are stored. Therefore, it is possible to further specify the resource management device to which the response message should be transmitted based on the resource ID included in the received response message and the stored related information. Thus, even if there are a plurality of resources being processed in each resource management device, it is possible to distinguish a specific resource from the transmission destination of the response message.

In the eighth resource management method according to the present invention, as the first management step, a first resource ID is assigned to a resource secured in a management range of a resource management device that first transmits a request message. As the first transmission step, the first resource ID is added to the request message and transmitted to the other resource management device. In the resource management device that has received the request message, the fourth management As a step, at least the first resource ID and an identifier of another resource management device that is the transmission source of the request message are stored in association with each other, and as the second transmission step, the second resource ID is substituted. The first resource ID is added to the response message and transmitted.
Further, in the resource management method according to the present invention, the first resource ID is transmitted together with the identifier of the resource management apparatus to which the first resource ID is assigned (that is, the request message is transmitted first). It may be.

  Further, in the resource management method according to the present invention, the request message is not limited to securing resources, but for example, for the purpose of changing the amount of resources required for communication or releasing already secured resources. It may be a thing. These are modifications of the resource management method for requesting resource reservation, and it can be considered that the resource amount after the change is secured for the change and the resource amount is 0 for the release.

  In addition, in order to release the reserved resources, the request message includes a code representing release instead of the amount of resources to be secured, and the first transmission step includes a step in which the request message includes the release code. Instead of securing resources, resources that have been secured in the resource management device may be released.

  Further, when managing a plurality of resources in parallel, the first transmission step further specifies a reserved resource to be released based on an identifier of the called terminal included in the request message. do it.

  In the resource management method described above, for example, the identifier of the called terminal is an Internet protocol (IP) address, and the determination step includes the IP address of the called terminal and the IP of the terminal existing within the management range of the resource management device. The address list may be compared to determine whether the destination terminal is within the management range of the resource management device.

  In addition, the identifier of the called terminal includes group information indicating a group to which the called terminal belongs, and the determination step includes group information included in the identifier of the called terminal and a terminal existing within the management range of the resource management device. By comparing with the group information, it may be determined whether or not the destination terminal is within the management range of the resource management apparatus.

Furthermore, the identifier of the destination terminal is an Internet Protocol (IP) address, and the determining step determines whether the destination terminal is the resource management device based on the upper bits of the IP address of the destination terminal included in the received request message. It may be determined whether it is within the management range.

  In addition, the resource management method according to the present invention includes a resource reservation state within the management range of the resource management apparatus for the request message, and whether or not a response message is received from another resource management apparatus that has transmitted the request message. And a display step of displaying at least one of resource securing results in other resource management devices included in the received response message.

  By having such steps, it is possible to confirm in one device whether or not there is a response from another resource management device and the content of the response, in addition to the status of resource reservation within the management range of the resource management device.

  On the other hand, a first resource management device 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, and manages resources of the communication network A resource management device, corresponding to the identifier included in the received request message, a first receiving unit that receives a request message that includes at least the identifier of the called terminal in the requested communication and the resource amount to be secured A determination unit that determines whether or not the destination terminal is within the management range of the resource management device, and as a result of determination by the determination unit, it is determined that the destination terminal is not within the management range of the resource management device A first transmitter that transmits the request message to another resource management device that manages resources in another adjacent management range; Those having a first management unit to ensure the necessary resources within the management range of the said resource management device.

  In this resource management device, necessary resources are secured within the management range of the resource management device, and the determination unit determines that the destination terminal corresponding to the identifier included in the received request message is the resource management device. When it is determined whether or not it is within the management range, and when it is not within the management range, that is, when a request message regarding a resource that spans a plurality of management ranges is received, the first transmission unit causes another adjacent management range The request message is transmitted to another resource management device that manages the resource.

  The second resource management device according to the present invention is further required within the management range of the resource management device when the determination unit determines that the destination terminal is within the management range of the resource management device. It has a response part which reserves resources and transmits a response message to the transmission source of the request message.

The third resource management device according to the present invention further includes a second reception unit that receives a response message from the other resource management device, and the resource management device when the response message is received. A second transmission unit that transmits a response message to a transmission source of the request message.
In such a resource management device, the response message received by the second reception unit is transmitted from the second transmission unit to the transmission source of the request message.

The fourth resource management device according to the present invention is the resource management device described above, wherein the first transmission unit uses the identifier of the resource management device that transmits the request message as the identifier of the transmission source of the request message. The second message is added to the request message and transmitted to another resource management device, and the second transmitter transmits the response message to the source of the request message specified by the identifier of the source included in the received request message. Is to be sent.
In such a resource management device, the identifier of the resource management device is added to the request message and transmitted. Further, based on the identifier included in the request message from the other resource management device, another resource management device that is the transmission source of this request message is specified, and is set as the transmission destination of the response message.

  Further, a fifth resource management device according to the present invention assigns a first resource ID to a resource secured within the management range of the resource management device in the resource management device described above, and this first resource ID And the identifier of the transmission source of the request message included in the request message received by the resource management device and the presence / absence of a response from another resource management device that is the transmission destination of the request message A second management unit;

  In a sixth resource management device according to the present invention, the request message includes an identifier of a calling terminal in the requested communication, and further, in response to receiving the request message, a calling terminal and a receiving terminal included in the request message. It has a 3rd management part which memorize | stores the identifier of a terminal, A said 2nd transmission part attaches | stores the identifier of the said calling terminal and destination terminal which were memorize | stored in the said response message, It is characterized by the above-mentioned.

  Similarly, the seventh resource management device according to the present invention further assigns a first resource ID to a resource secured in the management range of the resource management device, and the first resource ID and the request Associating an identifier of another resource management apparatus that is a message transmission source with a second resource ID that is allocated to a resource secured in the management range of the other resource management apparatus and included in the request message A first management unit that stores the request resource, the first transmission unit adds the first resource ID to the request message and transmits the request message to the other resource management device, and the second transmission unit. However, the second resource ID associated with the first resource ID is added to the response message and transmitted.

  When the eighth resource management device according to the present invention transmits a request message for the first time, the eighth resource management device assigns a first resource ID to a resource secured in the management range of the resource management device, and The first transmission unit adds the first resource ID assigned by the resource management apparatus that first transmitted the request message to the request message and transmits the request message to the other resource management apparatus, The first resource ID assigned to the resource secured by the management unit at least in the management range of the resource management device that first transmitted the request message, and another resource that is the transmission source of the request message And stores the identifier of the management device in association with each other, and the second transmitter replaces the second resource ID. The serial first resource ID and transmits in addition to the response message.

Further, in the resource management device according to the present invention, the request message is not limited to securing resources, but for example, for the purpose of changing the amount of resources required for communication or releasing already secured resources. What may be a thing is the same as that of the resource management method concerning this invention mentioned above.
As one form of the resource management device according to the present invention, for example, the request message includes a code representing release instead of the amount of resources to be secured, and the management unit is configured such that the request message includes the release code. The resources secured in the resource management apparatus may be released.
The first management unit may further specify a reserved resource to be released based on an identifier of a called terminal included in the request message.

  Furthermore, the resource management device according to the present invention provides a resource reservation state within the management range of the resource management device for the request message, and whether or not a response message is received from another resource management device that has transmitted the request message. And a display unit that displays at least one of resource securing results in other resource management devices included in the received response message.

  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 a plurality of resource management apparatuses provided for each of these management ranges. In the resource management system for managing resources of the communication network, the resource management device is any one of the resource management devices described above.

According to the present invention, a series of resources can be secured in cooperation with a plurality of resource management devices in response to a resource securing request that spans a plurality of management ranges.
Further, according to one aspect of the present invention (second and third “resource management methods” and second and third “resource management devices”), a response message from the other resource management device is sent to the resource management device. Was it possible to secure a series of resources in response to a resource securing request that spans multiple management ranges by receiving this at the device and sending a response message to the source of the request message for the resource management device? You can check whether or not.

  According to another aspect of the present invention (fourth “resource management method” and “apparatus”), the request message includes the identifier of the resource management apparatus that transmits the request message as the identifier of the transmission source of the request message. And transmitting to the other resource management device while transmitting the response message to the source of the request message specified by the identifier of the source included in the received request message, Each resource management device can identify a resource management device that is to transmit a response message (which is a transmission source of the request message) based on this identifier.

  According to another aspect of the present invention (fifth “resource management method” and “apparatus”), the first resource ID that identifies the resource secured by each resource management apparatus and the received request message Reserving resources across multiple management ranges by associating and storing the identifier representing the source of the request message included and the presence or absence of a response from another resource management device that is the destination of the request message In response to a request, it is possible to manage the progress of securing a series of resources via a plurality of resource management devices in order.

According to another aspect of the present invention (sixth “resource management method” and “apparatus”), the request message or the resource being secured can be specified by the identifier of the calling terminal in the requested communication. Therefore, it is possible to process a plurality of request messages in parallel.
According to another aspect of the present invention (seventh “resource management method” and “apparatus”), in each resource management apparatus, the resource secured by the resource management apparatus in its own management range, and the resource management Each resource management device processes a plurality of request messages in parallel by identifying the resource secured by the resource management device that has transmitted the request message to the device by the first resource ID and the second resource ID, respectively. It is also possible.

  In addition, according to one aspect of the present invention, it is possible to realize a series of resource change or release in cooperation with a plurality of resource management apparatuses even in response to a resource change or release request extending over a plurality of management ranges. Can do.

  Further, according to another aspect of the present invention, by specifying a reserved resource to be released based on an identifier of a called terminal included in the request message, release processing is individually or individually performed for a plurality of resources. Can be done in parallel.

According to an aspect of the present invention, the group information included in the identifier of the destination terminal is used to determine whether the destination terminal of the requested communication is within the management range of the resource management apparatus. Therefore, it is possible to improve the efficiency of the determination.
According to another aspect of the present invention, a determination is made by determining whether or not the destination terminal is within the management range of the resource management device based on the upper bits of the IP address of the destination terminal. Efficiency can be improved.

  Furthermore, according to another aspect of the present invention, the status of resource reservation within the management range of the resource management device for the request message, and reception of a response message from another resource management device that transmitted the request message By displaying at least one of the presence / absence and the result of resource reservation in another resource management device included in the received response message, the state of resource reservation related to the request message can be known.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
1. First embodiment 1-1. Overview of Resource Management System FIG. 1 is a diagram illustrating an overview of a resource management system according to a first embodiment of the present invention.
This resource management system is composed of a plurality of resource management devices (servers) RMS1, RMS2 for managing resources of a communication network.
The communication network to be managed here is a communication network based on a so-called Internet protocol (IP), and a plurality of routers R (R11 to R13, R21 to R23) and terminals T (T11 to T16, T21 to 21) linked to each other. T26). In addition to the routers and terminals, the communication network shown in FIG. 1 collects a plurality of terminals and connects them to a layer 2 switch SW (SW11, SW12, SW21, SW22) and a gateway device GW (GW11). , GW21).
In this communication network, a resource when a pair of terminals communicates is an access line and a router between the terminal and the router R that constitute a communication path between two terminals (the originating terminal and the terminating terminal) that communicate with each other. A link between R.

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

The application server AS (AS1, AS2) receives a communication request from a terminal (for example, the terminal 11), and manages a resource management server (for example, resource management) that manages resources in the management range (for example, the management range NW1) to which the terminal belongs. It is a server that sends a request message for requesting resource reservation to the server RMS1).
The request message includes at least the identifier of the called terminal in the requested communication and the resource amount to be secured. In this embodiment, the IP address of the called terminal is used as this identifier. .

  In FIG. 1, two resource management servers RMS1 and RMS2 and two management ranges (NW1 and NW2) are depicted. In addition to these, the third and fourth management ranges connected to the communication network are illustrated. May exist, the third and fourth resource management servers may be provided for the third and fourth management ranges, respectively, and these may be connected to the resource management servers RMS1 and RMS2.

1-2. Configuration of Resource Management Server (RMS) Each resource management server RMS1, RMS2 is a computer having a communication function, and has transmission / reception units 11, 21, control units 12, 22, and database units 13, 23, respectively. . Since these basic functions are common to each resource management server, the configuration and functions of the resource management server will be described below using the resource management server RMS1 as an example.
These functions are installed in the computer hardware resources such as a central processing unit (CPU) and a storage device (including internal memory such as ROM and RAM, as well as an external storage device such as HDD). It is realized by cooperation with a computer program (software).

FIG. 2 is a functional block diagram of the resource management server RMS1.
In the resource management server RMS1, the transmission / reception unit 11 includes a communication interface, and transmits and receives various messages.
The transmission / reception unit 11 functions as a first reception unit that receives a request message transmitted from the application server AS1 or another resource management server. In addition, as will be described later, the transmission / reception unit 11 transmits another request to the adjacent resource management server. It also functions as a first transmission unit that transmits to (for example, the resource management server RMS2).
As will be described later, when a response message is exchanged between the resource management servers RMS, the transmission / reception unit 11 serves as a second reception unit that receives the response message and a second transmission unit that transmits the response message. Also works.

The control unit 12 is a control unit that causes the resource management server RMS1 to perform processing according to the received request message. Specifically, as illustrated in FIG. 2, the message analysis unit 121, the determination unit 122, and the management unit 123. And a message creation unit 124.
Here, the message analysis unit 121 has a function of analyzing various messages received by the transmission / reception unit 11. For example, the IP address of the called terminal included in the received message is identified by the message analysis unit 121. . In addition, the message analysis unit 121 extracts an identifier, a resource ID, and the like of a message transmission source which will be described later.

  The determination unit 122 refers to the database unit 13 (more specifically, an address list 131 described later), and the destination terminal corresponding to the IP address included in the received request message is within the management range of the resource management server RMS1. It has a function of determining whether or not it exists.

  The management unit 123 stores various IDs extracted from various received messages, in addition to the function of securing necessary resources, together with the database unit 13 (more specifically, path information 132 and management table 133 described later). Has the function to manage.

When it is determined that the called terminal is not within the management range of the resource management server RMS1 as a result of the determination by the determination unit 122, the message creation unit 124 manages resources in other adjacent management ranges from the received request message. It has a function of creating a request message to be transmitted to another resource management device. Therefore, such a message creation unit 124 constitutes a first transmission unit together with the transmission / reception unit 11 described above.
As will be described later, when a response message is exchanged between the resource management servers RMS, when a response message is received from another resource management server, the response message is transmitted from the response message to the transmission source of the request message. While creating a response message, the determination unit 122 has a function of creating a response message to be transmitted to the transmission source of the request message when it is determined that the destination terminal is within the management range of the resource management device. Therefore, such a message creation unit 124 constitutes a second transmission unit and a response unit together with the transmission / reception unit 11 described above.

As illustrated in FIG. 2, the database unit 13 includes an address list 131, route information 132, and a management table 133.
Here, the address list 131 is a list of IP addresses of the terminals T11 to T14 and the gateway GW11 within the management range of the resource management server RMS1. In the present embodiment, the gateway GW 11 exists as a user network interface (border point with the user), and thus the IP address thereof is described as being included in the above list. However, generally, the IP address of the gateway GW 11 is Is not necessarily included.

  FIG. 3 is a diagram showing an example of the data structure of the address list 131 in the present embodiment. As shown here, the address list 131 includes a “terminal IP address” of each terminal, an “terminal accommodating edge node name” representing an edge node accommodating the terminal (for example, a router R11 accommodating the terminal T11), And the IP address of the terminal accommodating edge. Therefore, the determination unit 122 described above collates the IP address of the called terminal included in the received request message with the “terminal IP address” of the address list 131, so that the called terminal can recognize the resource management server RMS1. It can be determined whether it is within the management range.

The path information 132 is a list database of paths (communication paths) composed of resources within the management range of the resource management server RMS1.
FIG. 4 is a diagram illustrating an example of a data structure of the route information 132 in the present embodiment. In this example, the path information indicating the path between the calling-side edge node and the called-side edge node is “the calling-side edge node identifier (or IP address)” and “the called-side edge node identifier (or IP address)”. And “resource details” indicating the details of this route.

  As shown in FIG. 4, “route ID” is assigned to each route. This route ID is unique within the management range. Therefore, by referring to the route ID, a specific ID within the management range can be obtained without enumerating access lines and links between nodes constituting the route. A route (a set of resources) can be specified.

  Further, in the “resource details”, as individual resources constituting the route, individual nodes or links constituting the route between the originating edge node and the terminating edge node, for example, access lines (terminal and router or A list of a path between the layer 2 switch), an access concentrator line (a path between the layer 2 switch and the router), and a link (a path between the router and the router) is stored.

  Each of the resource management servers RMS1 and RMS2 includes a route calculation unit (not shown) that calculates a route based on the address list 131, calculates in advance all routes within the management range, and each resource management server RMS side And stored in the route information 132.

The management table 133 is a table for managing the received request message and the resource reservation state resulting therefrom.
In the present embodiment, the management table 133, together with the management unit 123 described above, manages the usage status of resources within the management range of the resource management apparatus (so-called “local resource management”), while transmitting and receiving messages. Manage resource allocation status across multiple management ranges.

  For the so-called “local resource management”, the management table 133 is not shown, but for example, for each link listed in the “route details” of the route information (see FIG. 4), the source node and destination node of the link By storing the total resource amount (communication capacity) and the resource amount in use, the use status of resources within the management range of the resource management device is managed.

On the other hand, regarding management of the status of securing resources across a plurality of management ranges, the management table 133 manages information included in the request message, the presence / absence of a response from the transmission destination of the request message, and the content thereof.
FIG. 5 is a diagram illustrating an example of the data structure of the management table 133 in the present embodiment, regarding the management of the resource securing status across a plurality of management ranges. As shown here, the management table 133 can be composed of items of “resource ID”, “transmission source ID”, “transmission source resource ID”, “transmission state”, and “timer”.

Here, the “resource ID” identifies a resource (a series of routes) secured within the management range of the resource management server RMS1 in response to the securing request. This resource ID is assigned by the management unit 123 of the resource management server RMS1 and is unique for each securing request.
The above-mentioned “resource ID” may be uniquely generated in each resource management server. For example, the request source such as the application server AS1 or the resource management server RMS1 that first received the request message is the first. The specified resource ID may also be used as its own resource ID in the other resource management server RMS2 that has received it. Further, the identifier of the called terminal (for example, IP address) may be used as the resource ID.

The “transmission source ID” is the ID (identifier) of the transmission source of the request message, that is, the server that transmitted the request message to the resource management server RMS1. This “source ID” is extracted from the request message.
The “transmission source resource ID” is a resource ID assigned to a resource secured in another resource management server that is a transmission source of the request message. This “source resource ID” is also extracted from the request message.
The “transmission state” indicates whether or not the resource management server RMS1 that transmitted the request message has received a response message from another resource management server (for example, RMS2) that is the transmission destination. For example, when a request message is transmitted, the value “1” is set in the “sending state”, and when a response message to the request message is received, the value “0” can be stored.
The “timer” can store a timer value that starts when a request message is transmitted and counts the time until a response message to the request message is received.

In the present embodiment, the database unit 13 described above is provided in the resource management server RMS1, but part or all of the database unit 13 is placed on a server different from the resource management server RMS1, You may make it connect with a communication line.
Further, when the database unit 13 is placed in the resource management server RMS1, the data to be stored therein, in particular, the address list 131 is not only the terminal information within the management range of the resource management server RMS1, but also the other resource management server RMS2. You may comprise so that the terminal information in the management range may be included.

1-3. Resource Management by Resource Management Server (1) Message Format of Request Message FIGS. 6A and 6B are diagrams illustrating an example of a message format of a request message received by the resource management server RMS.
The request message for requesting the resource reservation includes at least the following two pieces of information.
(A) “No. 4: Destination IP”: represents the identifier of the called terminal in the requested communication.
(B) “No. 5: Resource amount”: Represents the resource amount (BW) to be secured.
Further, in the present embodiment, as shown in FIG. 6, the request message includes the following.
(C) “No. 1: IP of resource request source server”: Indicates the identifier (IP address in the present embodiment) of the request source server (for example, application server AP1) that passed the request message to the resource management server. .
(D) “No. 8: Resource management server ID” (so-called “transmission source ID”): represents the identifier of the resource management server that transmitted the request message.
(E) “No. 7: Resource ID”: A resource ID assigned to a resource secured in the transmission source resource management server that has transmitted the request message, that is, a transmission source resource ID.
(F) “No. 3: Resource exit IP”: Indicates the exit IP of the management range managed by the source resource management server.

(2) Resource Reservation Operation Next, a resource reservation operation in the present embodiment will be described.
FIG. 7 is a flowchart showing a procedure for securing resources in each resource management server. Along with this flowchart, the operation of the resource management server RMS1 can be described as follows.
First, when the resource management server RMS1 receives the request message (S01: Yes), it specifies the IP address (Destination IP or DA) of the destination terminal contained therein, and refers to the address list of the database unit 13, It is determined whether the destination terminal exists within the management range NW1 of the resource management server RMS1 (S02). Further, the “transmission source ID” and “transmission source resource ID” extracted from the request message are stored in the management table 133.

(2-a) When the called terminal is within the management range When the called terminal is within the management range NW1 (S02: Yes), the management unit 123 refers to the route information 132 and the management table 133, and The route is identified, and a resource that satisfies the resource amount (BW) to be secured included in the request message is secured (S03).
At this time, if resources greater than the resource amount (BW) to be secured can be used in all links included in the route, after securing necessary resources (S03), the source of the request message is set as a response message. As a transmission destination (S04), and a response message of “reservation OK” is transmitted to the transmission source of the request message (S05). However, when securing resources (S03), if the amount of resources available in any link (= total resource amount—resource amount already in use) is less than the resource amount (BW) that is desired to be secured, A response message “reserved NG” is transmitted to the transmission source of the request message (S04, S05).

(2-b) When the called terminal is not within the management range On the other hand, when the called terminal is not within the management range NW1 (S02: No), a timer is started (S06), and resources required within the management range NW1 are allocated. In addition to securing (S07), the request message is transmitted to another resource management server RMS2 that manages another adjacent management range NW2 (S08).

Here, “Securing resources when the called terminal is not within the management range (S07)”, “Management of resource securing state”, and “Transmission of request message (S08)” will be described in detail.
(2-b-1) Reserving resources when the called terminal is not within the management range (S07) The above-mentioned "resources necessary within the management range NW1" means that the calling terminal is within the management range NW1 ( That is, when the request message is transmitted from any application server), the resource from the originating terminal to the resource exit IP of the management range NW1, that is, the resource to the router R13 serving as an exit to another adjacent management range NW2 It is. Such resources are searched from the route information 132 (see FIG. 4) by the management unit 123, and the use state of each link included in the route can be known by referring to the management table 133.

At this time, if a resource larger than the resource amount (BW) to be secured can be used in all links included in the route, the necessary resource is secured (S07: Yes). Resource ID "(first resource ID) is assigned. However, if the amount of resources that can be used in any link (= total resource amount—the amount of resources already in use) is less than the resource amount (BW) to be secured (S07: No), a request message is transmitted. The source is specified as the transmission destination of the response message (S12), a response message of “secure NG” is transmitted (S13), and a predetermined cancel process is executed to cancel the transmitted request message (S14).

(2-b-2) When a resource necessary for managing the resource securing state is secured, the “resource ID” assigned to the secured resource and the “No. 8: The transmission source ID of the request message included in the “resource management server ID” is stored in “resource ID” and “transmission source ID” of the management table 133 (see FIG. 5). Here, the transmission source ID is specifically the IP address of the server (for example, the application server AS1 or another resource management server not shown in FIG. 1) that is the transmission source of the request message.
Similarly, the transmission source resource ID (this is the resource ID assigned in the transmission source server of the request message) included in “No. 7: Resource ID” of the request message shown in FIG. Stored in the “source resource ID” (see FIG. 5).

As a result, the “resource ID” assigned in the resource management server RMS1, the “source ID” and the “source resource ID” extracted from the request message can be managed in association with each other.
Thus, by storing the resource ID of the resource secured in the resource management server as the transmission source resource ID in the subsequent resource management server, when securing a series of resources across a plurality of resource management servers, the so-called “ A resource ID chain is formed.

(2-b-3) Transmission of Request Message (S08) The resource management server RMS1 determines “No. 8: Resource management server ID” and “No. 7: Resource ID” (see FIG. 6) in the request message. After changing the identifier (for example, IP address) of the resource management server RMS1 as the transmission source and the resource ID of the resource secured in the resource management server RMS1, the request message is sent to the other resource management server RMS2. Send. When there are a plurality of adjacent resource management servers, the request message may be simultaneously transmitted to these resource management servers.
When this request message is transmitted to the other resource management server RMS2, the value “1” is set in the “transmission state” column of the management table 133 shown in FIG.

1-4. Response to Resource Securing Request In response to the request message as described above, the other resource management server RMS2 processes the request message according to the same procedure as that described above for the resource management server RMS1 (especially S01 and S02 shown in FIG. 7). To do. At this time, if the called terminal identified by the identifier included in the request message is within the management range NW2 (FIG. 7, S02: Yes), an attempt is made to secure resources (FIG. 7, S03), and the request is made. A response message is transmitted to the resource management server RMS1 that is the message transmission source (FIG. 7, S05), and the result of resource reservation (“reserved OK” if the resource can be secured, “secured NG” if not secured) is notified.
At this time, the resource management server RMS2 can specify the transmission destination of the response message by the transmission source ID included in “No. 8: Resource management server ID” (see FIG. 7) of the request message.

(1) Message Format of Response Message FIG. 8 is a diagram illustrating an example of the message format of the response message in the present embodiment. Here, FIG. 8A is a response message when resource reservation is successful (“reservation OK”), and FIG. 8B is a response message when resource reservation fails (“reservation NG”).
In the present embodiment, the response message (FIG. 8A) when the reservation is successful includes the following.
(A) “No. 1: IP of resource request source server”: IP address of the server that first issued the request message. In the present embodiment, for example, it is the IP address of the server (for example, application server AP1) that first transferred the resource securing request to the resource management server RMS1.
(B) “No. 2: Resource ID”: Resource ID assigned to the resource secured in the source resource management server RMS1 that transmitted the request message to the resource management server RMS2, that is, “source resource ID” .
(C) “No. 3: Resource management server ID”: The ID of the server that is the transmission source of the request message, that is, the server that is the transmission destination of the response message (so-called “transmission source ID”).

In the present embodiment, the response message (FIG. 8B) when securing fails is
In addition to “No. 1: IP of the resource request source server” (IP address of the server that issued the request message first), “No. 2: Response message” (reason of secured NG) and “No. 3: Congestion flag” Is included. Further, as in FIG. 8A, a “transmission source ID” and a “transmission source resource ID” may be added here.

(2) Identification of transmission destination of response message Next, the operation of the resource management server RMS1 that has received the response message as described above from the resource management server RMS2 will be described.
First, the resource management server RMS1 specifies the transmission destination of the response message as follows (FIG. 7, S10).
When the resource management server RMS1 receives the response message from the other resource management server RMS2 that is the transmission destination of the request message (S09: Yes), the message analysis unit 121 analyzes the response message, and “No. 2: The “source resource ID” included in the “resource ID” is specified. The “transmission source resource ID” extracted from this response message is a resource ID assigned to the resource secured within the management range by the resource management server RMS1 that has received this response message. Therefore, the management unit 123 of the resource management server RMS1 refers to the management table 133 by using this resource ID as a key, so that “transmission source ID” and “transmission source resource ID” associated with this “resource ID” are Can be acquired (FIG. 7, S10). The server specified by the “transmission source ID” acquired in this way is the transmission source of the response message at the same time as the transmission source of the request message received earlier for the resource management server RMS1.

The resource management server RMS1 specifies the transmission source server that transmitted the request message as described above as the transmission destination of the response message, and then “No. 2: Resource ID” and “No. 3: Resource management” of the response message. The “server ID” is rewritten to “source resource ID” and “source ID” read from the management table 133, respectively, and then transmitted (FIG. 7, S11).
In this way, by adding the “transmission source resource ID” stored in its own management table 133 to the response message, the other resource management server that has received the response message refers to the management table and the response message. It is possible to uniquely identify the resource ID related to. Therefore, even when the other resource management server transmits a plurality of request messages, the transmission destination of the response message can be uniquely determined.

  Further, the resource management server RMS1 records the fact that the “reserved OK” response has been received by changing the “transmission state” in the management table 133 from “1” to “0”, and a series of The process ends.

On the other hand, when the response message is not received within a predetermined time after starting the timer (FIG. 7, S09: No), the transmission source of the request message is specified as the transmission destination of the response message (S12). Is transmitted (S13), a predetermined cancel process (S14) is executed, and the process is terminated.
Note that if the response message is not received, the request message may be retransmitted a predetermined number of times before the process proceeds to the cancellation process.

With the above procedure, a series of resources can be secured in response to a resource securing request that spans a plurality of management ranges.
Further, by adding the transmission source ID to the request message and transmitting it, the resource management server that responds to the request message can efficiently identify the transmission destination of the response message based on the transmission source ID. Can be speeded up.
Further, in the present embodiment, the “transmission source resource ID” and the “resource ID” are managed as a pair in the management table 133 of the database unit 13, and the request message includes the transmission source ID within each management range. The resource ID assigned to the resource secured in (1) is transmitted and received, and the response message is transmitted and received with the resource ID (source resource ID) of the corresponding request message being added. This makes it possible to follow a so-called “resource ID chain” and distinguish individual request messages. Therefore, even when a plurality of request messages are received from the same transmission source resource management server, it is possible to secure resources and perform parallel processing of responses.

  In this embodiment, the “transmission source resource ID” added to the request message has been described as a resource ID uniquely assigned by the resource management server that manages the adjacent area, but the request message is transmitted first. The resource ID (first resource ID) assigned in the resource management server to be used may be carried between the resource management servers. That is, when the first resource ID is assigned to the resource secured in the management range of the resource management server that transmits the request message first, the first resource ID is added to the request message to another resource management device. In the other resource management server that has received this request message, the first resource is replaced with the resource ID (second resource ID) uniquely assigned to the resource secured within its management range. An ID may be added to a request message or a response message for transmission. In this case, for example, in the third and subsequent resource management servers, the resource ID assigned in the resource management server that first transmitted the request message is managed as the “first resource ID”. At this time, the resource ID assigned by itself as the “second resource ID” may be managed together with the “first resource ID”.

In addition, the identifier of the resource management server that transfers the request message may be added to the request message together with the first resource ID, but the first resource ID is assigned (that is, the request message is transmitted first). ) A request message or a response message may be transmitted with the identifier of the resource management server added.
By adding the resource ID assigned in the resource management server that first transmits the request message and the identifier of this resource management server to the request message, the response message from the other resource management server is transmitted first. Can be sent directly to the resource management server. As a result, for example, it is possible to perform unified management of requests such that the application server does not need to select a resource management server, and the processing efficiency can be further improved.

As described above, in the present invention, (a) the transmission source resource ID of the transmission source of the request message (the resource management server that manages the adjacent area) and the resource ID assigned by the resource management server are included in various messages. (B) Add the resource ID assigned by the resource management server that first transmits the request message; (c) The resource ID assigned by the resource management server that first transmits the request message and the resource management server are unique. It is possible to take various forms such as adding the resource ID assigned to the.
In addition, (a) the identifier of each resource management server that transmits the message, (b) the identifier of the resource management server that transmits the message first, and the like can be added to the various messages.

1-5. Change of Resource Amount The resource amount of a series of resources secured across a plurality of management ranges can be realized by transmitting and receiving a request message between resource management servers, as in the resource securing described above. The change in the resource amount is different from the resource reservation described above in that a series of routes in which resources have already been secured are specified. In the present embodiment, a series of routes that have already been specified are specified by resource IDs.
The resource amount can be changed ("change OK") if the resource amount (capacity) after the change can be paid out in all of the links constituting a series of routes. However, if the requested resource amount (capacity) cannot be paid out, the change cannot be made (“change NG”).

(1) Message Format of Resource Quantity Change Request Message FIG. 9 shows an example of a message format of a request message that requests a change in resource quantity. As shown here, the above-mentioned message for securing a resource is included in that it includes “No. 2: Resource amount” and “No. 3: Resource ID” (transmission source resource ID) indicating the resource amount after change to be secured. Common to the format (see FIG. 6). The request message also includes “No. 4: Resource management server ID” representing the transmission source ID.
By extracting “source resource ID” included in “No. 3: resource ID” from such a request message and referring to the management table 133 of the database unit 13, each resource management server can determine the resource amount. It is possible to specify a resource (a series of routes) to be changed.

(2) Procedure for Changing Resource Amount FIG. 10 is a flowchart showing a procedure for changing a resource amount.
First, when the resource management server RMS1 receives a request message for changing the resource amount (S30), it checks whether there is a reserved resource (a series of routes) specified by the request message (S31). . Specifically, referring to the management table 133, is the “transmission source resource ID” recorded in “No. 3: Resource ID” of the request message stored in its own management table 133 (see FIG. 5)? Confirm whether or not.

If the resource is not yet secured as a result of the confirmation (the source resource ID included in the request message is not recorded in the management table 133) (S31: No), the request is rejected (Reject) ( S37).
On the other hand, when the resource (series of routes) whose resource amount is to be changed has already been secured (S31: Yes), it is confirmed whether or not a series of routes has been secured in the adjacent resource management server RMS2. (S32). This confirmation can be performed, for example, by referring to the “transmission state” in the management table 133.

If a series of routes is not secured in the adjacent resource management server RMS2 (S32: No), it is considered that the receiving terminal exists in the management range of the resource management server RMS1, and therefore the resource amount of the resource in the management range (S36). Then, after specifying the transmission source of the request message (S45), a response message indicating the result of the change (“change OK” or “change NG”) is transmitted (S46).

On the other hand, when a series of routes are secured in the adjacent resource management server RMS2 (S32: Yes), after starting the timer (S33), the resource amount of the resource within the management range is changed. (S34). In parallel with the change of the resource amount, the request message is transmitted to the adjacent resource management server RMS2 (S35).
As a result of performing the resource amount change process (S34), if the required resource amount cannot be secured (S38: No), the response message transmission destination is specified (S40) and the response message of “change NG” is transmitted. (S41) A series of processing ends. At this time, a predetermined cancel process (S42) may be performed.

On the other hand, when the resource amount change process (S34) is performed and the necessary resource amount is secured (S38: Yes), a response message to the previously transferred request message (S35) is received within a predetermined time. Whether or not (S39). If there is a response indicating “change OK” within a predetermined time (S39: Yes), the destination of the response message is specified by referring to the management table 133 (S43), and the response “change OK” A message is transmitted (S44).
On the other hand, when there is no response within a predetermined time, that is, when a timeout occurs (S39: No) or when a response message of “change NG” is received, the other resource management server RMS2 can secure resources. It is assumed that there was no such process, and the processes of S40 to S41 described above are executed.

  Note that the message format of the response message and the identification of the transmission destination of the response message are basically the same as those in the case of the response message to the resource securing request described above. Therefore, the description is omitted.

1-6. Release of Resources Next, the release of a series of resources secured over a plurality of management ranges will be described.
The release of a series of resources can also be realized by transmitting and receiving a release request message between resource management servers, as in the resource reservation and change described above.

(1) Message Format of Resource Release Request Message FIG. 11 shows an example of a message format of a request message for requesting resource release. As shown here, by having “No. 2: Resource ID” and “No. 3: Resource Management Server ID”, even in a request message requesting release, “Source Resource ID” and “Source ID” Is included in common with the message format of the resource amount change request described above (see FIG. 9).
The resource management server RMS1 that has received such a request message can identify the resource to be released by referring to the management table 133 based on the “source resource ID” extracted from the request message.

(2) Resource Release Procedure FIG. 12 is a flowchart showing a resource release procedure.
First, upon receiving a resource release request message (S50), the resource management server RMS1 confirms whether there is a reserved resource (a series of routes) specified by the request message within its management range. (S51). Specifically, referring to the management table 133, is the “transmission source resource ID” recorded in “No. 2: Resource ID” of the request message stored in its own management table 133 (see FIG. 5)? Confirm whether or not.

If the resource is not yet secured as a result of the confirmation (the source resource ID included in the request message is not recorded in the management table 133) (S51: No), the request is rejected (Reject) ( S52).
On the other hand, if resources (a series of routes) to be released have already been secured within the self management range (S51: Yes), whether or not a series of routes have been secured in the adjacent resource management server. Is confirmed (S53). This confirmation can be performed, for example, by referring to the “transmission state” in the management table 133.

If a series of routes is not secured in the adjacent resource management server RMS2 (S53: No), it is considered that the receiving terminal exists within the management range of the resource management server RMS1, and thus it is confirmed whether or not the terminal can be released. (S54), the resources within the management range are released (S55), and the series of processing ends.
On the other hand, when a series of routes are secured in the adjacent resource management server RMS2 (S53: Yes), it is confirmed whether or not the resources secured within the self management range can be released (S54). ) Releases the resource within the management range (S55), and transmits the request message to the adjacent resource management server RMS2 (S56), and ends the series of processing.
If the resource cannot be released within its own management range (S54: No), a “NG log” is created (S57), and the series of processing ends.

  As described above, according to the resource management system according to the present embodiment, request messages are transmitted and received between a plurality of resource management servers for securing resources, changing resource amounts, and releasing resources over a plurality of management ranges. As a result, it is possible to realize securing, changing, and releasing of resources over a plurality of management ranges.

In addition, by sending and receiving response messages between multiple resource management devices, it is determined whether a series of resources could be secured in response to requests for securing resources and requests for changing resource amounts that span multiple ranges. Can be confirmed.
Further, a first resource ID that identifies a resource secured by each resource management device, an identifier that represents the transmission source of the request message included in the received request message, and a transmission destination of the request message In the middle of securing a series of resources via a plurality of resource management devices in order in response to a resource securing request that spans a plurality of management ranges by storing the presence or absence of a response from the resource management device Can be managed.

In addition, by identifying the resource being secured by the “resource ID”, a plurality of request messages can be processed in parallel.
Further, the “resource ID” (first resource ID) assigned in each resource management server is sent to the request message as “source resource ID” (second resource ID), and the request message is transmitted. In the received resource management server, the resource ID assigned by the resource management server (first resource ID), the ID of the server that transmitted the request message (source ID), and “source resource ID” (second In this way, each resource management server can identify a resource management device to which a response message should be transmitted (which is a transmission source of the request message). Therefore, each resource management apparatus can process a plurality of request messages in parallel.

  Further, according to another aspect of the present invention, by specifying a reserved resource to be released based on an identifier of a called terminal included in the request message, release processing is individually or individually performed for a plurality of resources. Can be done in parallel.

2. Second Embodiment Next, a second embodiment of the present invention will be described. In the second embodiment, the same components as those in the first embodiment described above are denoted by the same reference numerals, and the description thereof is omitted.
2-1. Overview of Resource Management System In the resource management system according to the second embodiment, in determining whether to send a request message to another resource management server based on the destination terminal ID included in the request message, This is common with the resource management system according to the first embodiment described above. However, in the second embodiment, the request message includes the calling terminal ID in addition to the called terminal ID, and in the management table 133 of the database unit 13 of the resource management servers RMS1 and RMS2, the “resource ID” is set. Instead, the difference between the ID of the destination terminal and the ID of the calling terminal is stored, which is different from the first embodiment described above. For example, the IP addresses of the called terminal and the calling terminal can be used as the IDs of these calling and called terminals, respectively.

2-2. Configuration of Resource Management Server (RMS) The basic structure of the resource management server in the second embodiment is the same as that of the resource management server according to the first embodiment shown in FIG. However, the data structure of the management table 133 is different from that of the first embodiment.
FIG. 13 is a diagram showing an example of the data structure of the management table 133 in the second embodiment. As shown here, “destination terminal ID” and “originating terminal ID” are stored in association with “transmission source ID”, “transmission state”, and the like.

2-3. Resource Management by Resource Management Server (1) Message Format of Request Message In the second embodiment, the request message includes “source terminal ID” and “destination terminal ID”. Unlike the first embodiment, “resource ID” and “source resource ID” are not essential.

(2) Resource reservation operation In resource reservation, whether the destination terminal ID included in the request message is in the address list 131 of the resource management server RMS1 that has received the request message, as in the first embodiment. Whether or not to transmit the request message to another adjacent resource management server RMS2 is determined.
Since the resource securing operation itself is the same as that in the first embodiment, the description thereof is omitted.

2-4. Response to Resource Securing Request (1) Message Format of Response Message In the second embodiment, the response message includes “source terminal ID” and “destination terminal ID” included in the request message. Unlike the first embodiment, the “transmission source resource ID” is not essential.

(2) Identification of transmission destination of response message In the second embodiment, as shown in FIG. 13, in each resource management server, “destination terminal ID” and “originating terminal ID” are associated with “source ID”. On the other hand, the destination terminal ID and the source terminal ID are added to the request message and response message for securing, changing, and releasing and transmitted.

It is considered that the above-mentioned combination of the called terminal ID and the calling terminal ID is uniquely determined for each request and is rarely duplicated. Accordingly, each resource management server refers to the management table 133 based on the pair of the called terminal ID and the calling terminal ID included in the received response message, thereby transmitting the response message transmission destination, that is, the request message. The origin can be specified.
Further, the resource targeted by the response message can be uniquely identified by referring to the pair of the called terminal ID and the calling terminal ID. Therefore, a plurality of messages can be processed in parallel.

  As described above, according to the second embodiment, parallel processing in each resource management server can be performed.

3. Third embodiment 3-1. Overview of Resource Management System In the first embodiment, the IP address of terminals T11 to T14 (and gateway GW11) within the management range of the resource management server RMS1 is added to the address list 131 of the database unit 13 of the resource management server RMS1. The request message is configured to include the IP address of the destination terminal in the requested communication, and the destination terminal collates the address list 131 with the IP address of the destination terminal so that the destination terminal can manage the management range. It was judged whether it was in.
On the other hand, the third embodiment of the present invention uses a group of terminals as an identifier instead of an IP address.
Here, the “group” is a set of one or a plurality of terminals. In the present embodiment, the group is preferably a set of terminals included in the management range of one resource management server or a subset thereof. Such a group can be defined for each router constituting the communication network, for example.
In addition, about this 3rd Embodiment, about the same structure as 1st Embodiment mentioned above, suppose that the description is abbreviate | omitted using the same code | symbol.

3-2. Configuration of Resource Management Server (RMS) FIG. 14 is a diagram illustrating an example of the configuration of the resource management server RMS1 according to the third embodiment. That is, as apparent from comparison with FIG. 2, in the third embodiment, the database unit 13 of the resource management server RMS 1 includes an identifier management table 134 instead of the address list 131.

FIG. 15 is a diagram showing an example of the configuration of the identifier management table 134 of the database unit 13 of the resource management server RMS1.
In this identifier management table 134, groups are registered as “identifiers”, and the IP addresses of terminals constituting each group are associated with each identifier (ie, group).
Further, in this embodiment, by configuring the groups so that the request message destinations are the same in advance, the ID of the other resource management server that is the request message destination for each group, It is possible to register the exit IP to the management range of the resource management server in the identifier management table 134.

3-3. By using the resource management group by the resource management server as an identifier included in the request message, the determination unit 122 of the resource management server RMS1 refers to this identifier management table 134 to transmit the request message. The resource management server can be automatically determined.
Further, by referring to the exit IP recorded for each group in the identifier management table 134, it is possible to easily specify a request destination for a resource outside the management range to be secured.
According to the third embodiment as described above, it is possible to improve the efficiency of the determination work and increase the processing speed as compared with the case of determining based on the IP address of each destination terminal. It becomes.
Even when the identifier management table 134 describes the identifier of the resource management server and the identifier of the management range or group instead of the exit IP, the transfer destination of the resource request can be easily specified.

4). Fourth Embodiment A fourth embodiment is a resource management system characterized in that it is determined whether or not it is within the management range based on the upper bits of the IP address of the terminal.
For example, when considering an IPv6 address, the IP address simply has a length of 128 bits. Therefore, as described in the first embodiment, when an IP address is used as various identifiers, the search target space becomes enormous in order to determine whether or not the IP address is within the management range because of its length. May take too much.
Therefore, in the fourth embodiment, a part of the IP address is used instead of the whole IP address as the identifier of the called terminal. This utilizes the fact that the communication network can be divided into subnets and managed by focusing on a part of the IP address.

For example, the communication network is divided for each router, and the same bit string as the subnet address is assigned to the upper bits of the IP address of the terminal accommodated in the same router as the upper bits of the IP address of each terminal.
In order to obtain the subnet address from the IP address, a subnet mask may be used.

FIG. 16 is a diagram illustrating an example of a configuration of the resource management server RMS1 according to the fourth embodiment. The database unit 13 is provided with a subnet list 135. In the subnet list 135, subnet addresses within the management range of the resource management server RMS1 are stored in advance.
Further, by providing the message analysis unit 121 with a subnet mask function, a subnet address can be obtained from the IP address.
The determination unit 122 searches the subnet list 135 of the database unit 13 using the subnet address obtained from the message analysis unit 121, thereby determining whether the destination terminal exists within the management range of the resource management server RMS1.

  As described above, by using the upper bits or the subnet address of the IP address, the search range can be reduced, and the efficiency of the determination work and the speeding up of the processing can be improved.

5. Fifth embodiment 5-1. Overview of Resource Management System In the resource management system according to the fifth embodiment of the present invention, the resource management server responds to the request message with the result of securing the resource within the management range of the resource management device, and the request A display unit configured to display whether or not a response message has been received from another resource management device that has transmitted the message, and a result of resource reservation in the other resource management device included in the received response message; Since other configurations and operations are the same as those of the first embodiment described above, the same components are denoted by the same reference numerals and description thereof is omitted.

5-2. Configuration of Resource Management Server (RMS) FIG. 17 is a diagram showing a configuration of the resource management server RMS1 in the fifth embodiment. As shown here, the resource management server RMS1 has a display unit 14.
The operations of “resource management” and “response to resource securing request” and the message formats by this resource management server are the same as those in the first embodiment, and the description thereof is omitted.

5-3. Information to be displayed In the fifth embodiment, the information displayed by the resource management server RMS1 is the following three items.
(A) The state of resource reservation within the management range of the resource management device RMS1.
(B) Whether a response message is received from another resource management server that has transmitted the request message.
(C) Result of resource reservation in another resource management device.
In the present embodiment, with respect to (a) above, there are three states of “own resource reservation processing”, “own resource reservation OK”, and “own resource reservation NG”. In addition, with regard to (b) and (c) above, there are three states: “Relay resource securing process in progress”, “Relay resource securing process result OK”, and “Relay resource securing process result NG”.

5-4. Display Operation Next, the display operation will be described with reference to FIG. 17 and the flowchart showing the data securing procedure shown in FIG. 7 and the data structure of the management table 133 shown in FIG.
With regard to the above (a) (resource reservation state within the management range of the resource management device RMS1), when receiving a resource reservation request message (S01: Yes), the management unit 123 displays “own resource reservation process” on the display unit 14. “Medium” is displayed. When the resource reservation process (S03 or S07) for the request message is completed, “own resource reservation OK” or “own resource reservation NG” is displayed according to the result.

On the other hand, the above (b) and (c) (whether or not a response message has been received from another resource management server that has transmitted the request message and its result) are displayed as follows.
When the resource management server transmits a request message to another adjacent resource management server (S08), a value “1” is set in the “sending state” of the management table 133, and a response message to this request message is received. (S09: Yes), the value “0” is set.
Accordingly, when the value “1” is set in the “transmission state”, the management unit 123 causes the display unit 14 to display “in process of securing relay resource”. Further, when the value “0” is set, according to the content of the response message, “relay resource securing process result OK” for “reserved OK”, “relay resource securing process result” for “reserved NG”. NG "can be displayed on the display unit 14.
In this embodiment, when a response is not obtained within a predetermined time (S09: No), “relay resource securing process result NG” is displayed.

  As described above, in the resource management system according to the present embodiment, in any resource management server, the status of resource allocation within the management range of the resource management server for the resource allocation request and the management of other resource management servers It is possible to know the state of resource reservation in the range.

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

It is a figure explaining the outline | summary of the resource management system concerning the 1st Embodiment of this invention. It is a functional block diagram of resource management server RMS1 in the 1st Embodiment of this invention. It is a figure which shows an example of the data structure of the address list in the 1st Embodiment of this invention. It is a figure which shows an example of the data structure of the route information in the 1st Embodiment of this invention. It is a figure which shows an example of the data structure of the management table in the 1st Embodiment of this invention. It is a figure which shows an example of the message format of the request message used in the 1st Embodiment of this invention. It is a figure which shows an example of the message format of the request message used in the 1st Embodiment of this invention. It is a flowchart showing the procedure of the resource reservation in the 1st Embodiment of this invention. It is a figure which shows an example of the message format of the response message (reservation OK) in the 1st Embodiment of this invention. It is a figure which shows an example of the message format of the response message (secure NG) in the 1st Embodiment of this invention. It is a figure which shows an example of the message format of the request message which requests | requires the change of the resource amount used in the 1st Embodiment of this invention. It is a flowchart showing the procedure of the change of the resource amount in the 1st Embodiment of this invention. It is a figure which shows an example of the message format of the request message which requests | requires release of the resource used in the 1st Embodiment of this invention. It is a flowchart showing the procedure of the release of the resource in the 1st Embodiment of this invention. It is a figure which shows an example of the data structure of the management table in the 2nd Embodiment of this invention. It is a figure which shows an example of a structure of the resource management server in the 3rd Embodiment of this invention. It is a figure which shows an example of a structure of the identifier management table in the 3rd Embodiment of this invention. It is a figure which shows an example of a structure of the resource management server in the 4th Embodiment of this invention. It is a figure which shows an example of a structure of the resource management server in the 5th Embodiment of this invention.

Explanation of symbols

11, 21 ... Transmission / reception unit, 12, 22 ... Control unit, 121 ... Message analysis unit, 122 ... Determination unit, 123 ... Resource management unit, 124 ... Message creation unit, 13, 23 ... Database unit, 131 ... Address list, 132 ... route information, 133 ... management table, 134 ... identifier management table, 135 ... subnet list, 14 ... display unit, AL11-AL25 ... access line, ALC11-ALC22 ... access line, AS1, AS2 ... application server, GW11, GW21 ... Gateway, NW1, NW2 ... Management range (communication network), R11 to R23 ... Router, RMS1, RMS2 ... Resource management server, SW1, SW2 ... Layer 2 switch, T11 to T26 ... Terminal.

Claims (29)

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 plurality of resource management devices provided for each of these management ranges Because
A first reception step of receiving, in one resource management device, a request message including at least an identifier of a called terminal in requested communication and a resource amount to be secured;
A determination step of determining whether or not the destination terminal corresponding to the identifier included in the received request message is within a management range of the resource management device;
As a result of this determination step, when it is determined that the destination terminal is not within the management range of the resource management device, a necessary resource is secured within the management range of the resource management device, and another adjacent management range And a first transmission step of transmitting the request message to another resource management device that manages the resource of the resource. The resource management method according to claim 1,
The first transmission step further includes:
When it is determined in the determination step that the destination terminal is within the management range of the resource management device, necessary resources are secured within the management range of the resource management device, and instead of transmitting the request message A resource management method, comprising: transmitting a response message to a transmission source of the request message. The resource management method according to claim 2, wherein
A second receiving step of receiving, in the resource management device, a response message from the other resource management device to the request message;
A resource management method comprising: a second transmission step of transmitting a response message to a transmission source of the request message for the resource management device when the response message is received. The resource management method according to claim 3, wherein
The first transmission step includes:
The identifier of the resource management device that transmits the request message is added to the request message as the identifier of the transmission source of the request message and transmitted to the other resource management device,
The second transmission step includes
A resource management method, comprising: transmitting the response message to a transmission source of the request message specified by a transmission source identifier included in the received request message. The resource management method according to claim 4, wherein
A first management step of assigning a first resource ID to a resource secured in the management range of the resource management device;
The first resource ID, the identifier of the transmission source of the request message included in the request message received by the resource management device, and the presence / absence of a response from another resource management device that is the transmission destination of the request message And a second management step for storing the information in association with each other. The resource management method according to any one of claims 3 to 5,
The request message further includes an identifier of the calling terminal in the requested communication,
And a third management step of storing an identifier of a calling terminal and a called terminal included in the request message in response to reception of the request message,
The second transmission step includes
A resource management method, wherein the stored identifiers of the calling terminal and called terminal are attached to the response message and transmitted. The resource management method according to any one of claims 3 to 5,
A first management step of assigning a first resource ID to a resource secured in the management range of the resource management device;
This first resource ID, an identifier of another resource management device that is the transmission source of the request message, and a resource secured in the management range of the other resource management device are included in the request message. A fourth management step for storing the associated second resource ID in association with each other,
The first transmission step includes:
Adding the first resource ID to the request message and sending it to the other resource management device;
The second transmission step includes
The resource management method, wherein the second resource ID associated with the first resource ID is added to the response message and transmitted. The resource management method according to claim 7, wherein
The first management step includes:
Assigning a first resource ID to a resource secured in a management range of a resource management device that transmits the request message first;
The fourth management step includes
Storing at least the first resource ID in association with an identifier of another resource management device that is a transmission source of the request message;
The first transmission step includes:
Adding the first resource ID assigned by the resource management apparatus that first transmitted the request message to the request message and transmitting the request message to the other resource management apparatus;
The second transmission step includes
The resource management method, wherein the first resource ID is added to the response message and transmitted instead of the second resource ID. The resource management method according to any one of claims 1 to 8,
The request message includes a code representing release instead of the amount of resources to be secured,
When the request message includes the release code, the resource management method includes a release step of releasing a resource already secured in the resource management device instead of securing the resource. The resource management method according to claim 9, wherein
The first transmission step further includes:
A secured resource to be released is specified based on an identifier of a called terminal included in the request message. The resource management method according to any one of claims 1 to 10,
The terminating terminal identifier is an Internet Protocol (IP) address,
The determination step includes
The IP address of the destination terminal is compared with a list of IP addresses of terminals existing within the management range of the resource management device to determine whether the destination terminal is within the management range of the resource management device A resource management method characterized by the above. The resource management method according to any one of claims 1 to 10,
The identifier of the called terminal includes group information indicating a group to which the called terminal belongs,
The determination step includes
By comparing the group information included in the identifier of the called terminal and the group information of the terminal existing within the management range of the resource management device, it is determined whether or not the called terminal is within the management range of the resource management device. A resource management method characterized by determining. The resource management method according to any one of claims 1 to 10,
The terminating terminal identifier is an Internet Protocol (IP) address,
The determination step includes
A resource management method comprising: determining whether or not the destination terminal is within a management range of the resource management apparatus based on an upper bit of the IP address of the destination terminal included in the received request message. The resource management method according to any one of claims 1 to 13,
Status of resource reservation within the management range of the resource management device for the request message, whether or not a response message has been received from another resource management device that sent the request message, and other information included in the received response message A resource management method comprising: a display step for displaying at least one of resource reservation results in the resource management apparatus. A resource management device that 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 that manages resources of the communication network,
A first receiving unit that receives a request message including at least an identifier of a called terminal in requested communication and a resource amount to be secured;
A determination unit that determines whether or not the destination terminal corresponding to the identifier included in the received request message is within a management range of the resource management device;
As a result of the determination by the determination unit, when it is determined that the destination terminal is not within the management range of the resource management device, the request message is sent to another resource management device that manages resources in another adjacent management range. A first transmitter for transmitting;
A resource management device comprising: a first management unit that secures necessary resources within a management range of the resource management device. The resource management device according to claim 15, wherein
A response unit that transmits a response message to the transmission source of the request message instead of transmitting the request message when the determination unit determines that the destination terminal is within the management range of the resource management device; A resource management device. The resource management device according to claim 16, wherein
A second receiving unit that receives a response message from the other resource management device to the request message;
A resource management apparatus comprising: a second transmission unit that transmits a response message to a transmission source of the request message for the resource management apparatus when the response message is received. The resource management device according to claim 17, wherein
The first transmitter is
The identifier of the resource management device that transmits the request message is added to the request message as the identifier of the transmission source of the request message and transmitted to the other resource management device,
The second transmitter is
A resource management device, wherein the response message is transmitted to a transmission source of the request message specified by a transmission source identifier included in the received request message. The resource management device according to claim 18, wherein
Furthermore, a first resource ID is assigned to a resource secured within the management range of the resource management apparatus, and the transmission source of the request message included in the request message received by the first resource ID and the resource management apparatus A resource management device comprising: a second management unit that stores the identifier and the presence / absence of a response from another resource management device that is the transmission destination of the request message in association with each other. The resource management device according to any one of claims 17 to 19,
The request message further includes an identifier of the calling terminal in the requested communication,
further,
A third management unit for storing an identifier of a calling terminal and a called terminal included in the request message in response to reception of the request message;
The second transmitter is
A resource management apparatus, wherein the stored identifiers of the calling terminal and called terminal are added to the response message and transmitted. The resource management device according to any one of claims 17 to 19,
Further, a first resource ID is assigned to a resource secured in the management range of the resource management device, the first resource ID, an identifier of another resource management device that is a transmission source of the request message, A fourth management unit that is allocated to a resource secured in the management range of the other resource management device and stores the second resource ID included in the request message in association with each other;
The first transmitter is
Adding the first resource ID to the request message and sending it to the other resource management device;
The second transmitter is
The resource management apparatus, wherein the second resource ID associated with the first resource ID is added to the response message and transmitted. The resource management device according to claim 21, wherein
The fourth management unit
Assigning a first resource ID to a resource secured in a management range of a resource management device that transmits the request message first;
Storing at least the first resource ID in association with an identifier of another resource management device that is a transmission source of the request message;
The first transmitter is
Adding the first resource ID assigned by the resource management apparatus that first transmitted the request message to the request message and transmitting the request message to the other resource management apparatus;
The second transmitter is
The resource management apparatus, wherein the first resource ID is added to the response message and transmitted instead of the second resource ID. The resource management device according to any one of claims 15 to 22,
The request message includes a code representing release instead of the amount of resources to be secured,
The management unit
When the request message includes the release code, the resource management apparatus releases the resource already secured in the resource management apparatus instead of securing the resource. The resource management device according to claim 23,
The management unit further includes:
A resource management apparatus characterized by identifying a reserved resource to be released based on an identifier of a called terminal included in the request message. The resource management apparatus according to any one of claims 15 to 24,
The terminating terminal identifier is an Internet Protocol (IP) address,
The determination unit
The IP address of the destination terminal is compared with a list of IP addresses of terminals existing within the management range of the resource management device to determine whether the destination terminal is within the management range of the resource management device A resource management device. The resource management apparatus according to any one of claims 15 to 24,
The identifier of the called terminal includes group information indicating a group to which the called terminal belongs,
The determination unit
By comparing the group information included in the identifier of the called terminal and the group information of the terminal existing within the management range of the resource management device, it is determined whether or not the called terminal is within the management range of the resource management device. A resource management device characterized by determining. The resource management apparatus according to any one of claims 15 to 24,
The terminating terminal identifier is an Internet Protocol (IP) address,
The determination unit
A resource management device that determines whether or not the destination terminal is within the management range of the resource management device, based on the upper bits of the IP address of the destination terminal included in the received request message. The resource management device according to any one of claims 15 to 27,
Status of resource reservation within the management range of the resource management device for the request message, whether or not a response message has been received from another resource management device that sent the request message, and other information included in the received response message A resource management device comprising: a display unit that displays at least one of resource reservation results in the resource management device. 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 the resources of the communication network by a plurality of resource management devices provided for each of these management ranges Because
29. A resource management system, wherein the resource management apparatus is the resource management apparatus according to any one of claims 15 to 28.

Images