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

Description

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

  When content such as audio and video is provided using a communication network, particularly an IP (Internet Protocol) network, if congestion occurs due to a usage request exceeding the capacity of the communication path, the communication quality is reduced due to packet loss and the like. It will deteriorate. Resource management in the network layer has been studied for the purpose of preventing such degradation of communication quality. One type of resource management involves using a resource management device (resource management server) that is independent of the routers that make up the communication network, to determine the resource capacity between nodes (links) that make up the communication network, and their usage. There is a method of paying out appropriate resources in response to a resource securing request from a user terminal or the like while managing. A conventional example will be described below.

  Before starting operation of a communication network, first, routing information in the communication network is collected. This routing information includes the resource capacity and connection information of each link in the communication network. Next, a communication path through which the packet passes is calculated based on the connection information of each link, and a path information table is created based on the calculation result. Also, a link information table is created from the resource capacity of each link. This link information table manages the total resource capacity of each link and the remaining amount of available resources.

  After starting the operation of the communication network, when the resource management server accepts a communication service use request (resource securing request), it is necessary for the communication from the route information table based on the requested communication IP address. Identify the link. Then, referring to the link information table, it is checked whether or not the capacity required for the communication is available for each identified link.

  As a result, when sufficient capacity is available for all the specified links, it is determined that the resources can be secured. Then, a permission response is made to the resource securing request, and a process of subtracting the capacity allocated to the communication from the resource remaining amount of the identified link in the link information table is performed. On the other hand, when the available capacity is insufficient for any of the links, it is determined that the resource cannot be secured, and a rejection response is made to the resource securing request (for example, Patent Document 1 and Non-Patent Document 1). See).

Communication quality is ensured by using a communication service in response to a permission response for a resource securing request.
After that, when the use of the communication service ends, the resources secured up to that point are released immediately.

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)

  For a large-scale communication network such as the Internet, the resources that must be managed become enormous and requests for securing resources to be handled by the resource management server increase. It becomes difficult to manage resources. In order to cope with such a problem, it is conceivable to divide the communication network into a plurality of management ranges, and provide resource management servers in these management ranges, respectively, to perform resource management distributed processing. Specifically, for example, it is conceivable to provide a resource management server for each autonomous system (AS) operated by an operator such as an Internet service provider (ISP).

  In such a communication network, when the originating terminal and the terminating terminal that communicate with each other belong to different autonomous systems, a series of resources that span multiple autonomous systems are managed in cooperation between multiple resource management servers. It will be. At this time, each resource management server uses the routing information in the autonomous system managed by itself and the address information of the border router that is the gateway to the neighboring autonomous system to establish a communication path extending to the neighboring autonomous system. It is necessary to calculate.

  The address information of the border router used for this calculation must be that of the border router actually used in each communication. However, when there are a plurality of border routers that can be gateways to adjacent autonomous systems, it is not easy to know which border router is actually used for each communication. For this reason, there is a problem that it is difficult to set appropriate border router address information in the resource management server.

  Further, the setting of the address information of the border router has to be performed manually by the maintenance person of the resource management server, which is complicated. In particular, when a failure occurs in an autonomous system and the communication route must be changed, it is not possible to reset the address information of the border router in a short time, and resource management is performed by updating the route table. There was a problem that it took a long time to resume.

  The present invention has been made to solve such a problem, and its purpose is to enable information on border routers serving as gateways to neighboring autonomous systems to be set in resource management devices appropriately and in a short time. There is to do.

In order to achieve such an object, a resource management device according to the present invention is a resource management device that manages resources of an autonomous system adjacent to another autonomous system via a plurality of border routers, The BGP route information to other autonomous systems acquired by the border routers belonging to the autonomous system by exchanging information with other border routers by BGP is periodically collected by BGP from the border routers belonging to the managed autonomous system. A route information collection unit that performs communication and calculates a communication route that spans between the managed autonomous system and another autonomous system based on the collected BGP route information each time BGP route information is collected by the route information collection unit a route calculating means, stores the information of the calculated communication path, autonomic managed Characterized in that it comprises a communication path information memory means for storing information of the border router that outlet or inlet of the communication path from the stem to other autonomous systems as one of the communication path information.
Here, the communication path information storage means can store information on the communication path in the managed autonomous system as one of the communication path information.

  In addition, the resource management device described above refers to the communication path information when receiving a request for securing a resource necessary for communication between the managed autonomous system and another autonomous system, and exits to the other autonomous system. Alternatively, it may further comprise resource securing means for selecting a communication path in the managed autonomous system connected to the entrance and performing a resource securing process for this communication path.

  Further, the communication path calculation means can calculate a plurality of communication paths having the same combination of communication origination terminal and destination terminal. Then, the resource management device described above refers to failure information collection means for collecting information related to communication path failure from the nodes constituting the managed autonomous system, and refers to the communication path information. A resource transshipment unit that transships the reserved resources to another communication path that is the same as the communication path and the originating terminal and the destination terminal may be further provided.

  Further, the communication path calculation means determines the priority order among the plurality of communication paths, the communication path information storage means stores the priority order as one of the communication path information, and the resource securing means has the highest priority order. Resource reservation processing is performed for a high communication path, and the resource transshipment unit is configured to transship resources reserved for a communication path in which a failure has occurred to a communication path with the highest priority next to this communication path. Also good.

  In addition, the resource management device described above creates a message with the identifier of the resource management device and the identifier of the autonomous system to be managed, and transmits the message to another resource management device, and another resource management device Message receiving means for receiving a message to which an identifier of an autonomous system to be managed by another resource management device is added, identifier extracting means for extracting two identifiers from the received message, and two extracted Management object storage means for associating identifiers and storing management objects of other resource management apparatuses may be further provided.

  A resource management system according to the present invention includes a plurality of the resource management devices described above.

The resource management method according to the present invention is a resource management method for managing resources of an autonomous system adjacent to another autonomous system via a plurality of border routers, wherein the border router belonging to the autonomous system to be managed is other Collecting BGP route information to other autonomous systems obtained by exchanging information with the border router of BGP from other border routers belonging to the managed autonomous system by BGP, and BGP route information Each time it is collected, a step of calculating a communication path that spans between the managed autonomous system and another autonomous system based on the collected BGP path information, and storing the calculated communication path information, and from the managed autonomous system Border router that is the exit or entrance of the communication path to other autonomous systems And storing the above information as one of the communication path information.
Here, the step of storing the communication path information can store the information of the communication path in the managed autonomous system as one of the communication path information.

  Further, the resource management method described above refers to the communication path information when receiving a request for securing resources necessary for communication between the managed autonomous system and another autonomous system, and exits to the other autonomous system. Alternatively, the method may further include a step of selecting a communication path in the managed autonomous system connected to the entrance and performing a resource securing process on the communication path.

  Further, the step of calculating the communication path can calculate a plurality of communication paths having the same combination of the communication source terminal and the destination terminal. The resource management method described above includes a step of collecting information on a communication path failure from the nodes constituting the managed autonomous system, and the communication path information is referred to and secured for the communication path in which the failure has occurred. The communication resource may be further included in the communication path and the source terminal and the destination terminal are transferred to another same communication path.

  The step of calculating the communication path determines the priority order among the plurality of communication paths, and the step of storing the communication path information stores the priority order as one of the communication path information, and performs the resource securing process. The performing step performs the process of securing resources for the communication path with the highest priority, and the step of transshipping resources prioritizes the resources reserved for the communication path in which the failure occurs next to this communication path. You may make it transship to the communication path | route with a high order | rank.

  The resource management method described above includes a step of creating a message to which an identifier of an autonomous system to be managed and an identifier of a resource management device that manages the autonomous system are added, and transmitting the message to another resource management device. A step of receiving a message to which an identifier of a system and an identifier of another resource management device that manages the autonomous system are added; a step of extracting two identifiers from the received message; and a correspondence between the two extracted identifiers And a step of storing management targets of other resource management devices.

In the present invention, based on route information to other autonomous systems that the border router has, a communication route between the managed autonomous system and other autonomous systems is calculated, and the managed autonomous system to the other autonomous system is calculated. Information on the border router that is the gateway of the communication path is stored. As a result, even when there are a plurality of border routers that can serve as gateways to other autonomous systems, an appropriate gateway can be easily set in the resource management device.
In addition, since the information of the border router serving as an entrance / exit can be automatically set, the complexity of manual setting can be eliminated and setting (or resetting) can be performed in a short time. Therefore, even when a failure occurs in the autonomous system and the communication path must be changed, it is possible to update the entrance / exit in a short time and perform resource management without delay.

In addition, when multiple communication paths with the same combination of communication origination terminal and destination terminal are calculated and a failure occurs in the communication path used for communication, the resources reserved for the communication path are determined. Transship to another communication path. Thereby, even if a failure occurs in the communication path, resource management can be continuously performed.
Furthermore, by determining a priority order among a plurality of communication paths and selecting a communication path to transfer resources based on the priority order, the resource can be used when using the best available communication path. Management can be continued.

  A message including the identifier of each device and the identifier of the autonomous system to be managed is transmitted / received between a plurality of resource management devices, and the two identifiers added to the received message are stored in association with each resource management device. . As a result, it is possible to automatically generate and store information representing management targets of other resource management apparatuses.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
1. First embodiment 1-1. Communication Network to which Resource Management System is Applied FIG. 1 is a block diagram showing a configuration of a communication network to which a resource management system according to the first embodiment of the present invention is applied.
This communication network is a communication network based on IP (Internet Protocol), and includes a plurality of networks AS1, AS2, AS3, AS4, and AS5 having the same route information. Each of the networks AS1 to AS5 is referred to as an “autonomous system”. Specifically, this is a network operated by an Internet provider.

Each of the autonomous systems AS1 to AS5 includes a plurality of routers. When many routers are provided, for example, the autonomous system AS5 is divided into a plurality of subsystems SubAS51, SubAS52, SubAS53, and SubAS54. Each of these subsystems SubAS51 to SubAS54 is also an autonomous system.
A router located at the boundary between adjacent autonomous systems AS and SubAS is referred to as “border router BR”.

  The autonomous systems AS and SubAS exchange route information in each other's system with the neighboring autonomous systems AS and SubAS by BGP (Border Gateway Protocol). This route information also includes route information of autonomous systems AS and SubAS that are only indirectly connected. Such route information exchanged by BGP is referred to as “BGP route information”. By exchanging BGP route information, it is possible to know where to send the packet to which border router BR of the adjacent autonomous system AS or SubAS. There are two types of BGP. EBGP is used between the border routers BR between the autonomous systems AS and SubAS, and IBGP is used between the border routers BR within the autonomous systems AS and SubAS.

1-2. Outline of Resource Management System FIG. 2 is a block diagram showing an outline of the resource management system according to the present embodiment.
The resource management system includes a plurality of resource management servers RMS1, RMS2, and RMS3 that manage the resources of the plurality of autonomous systems AS1, AS2, and AS3. The resources of the autonomous systems AS1 to AS3 are the link between the access line between the terminal T and the router R and the link between the routers R that constitutes the communication path between the two terminals (source terminal and destination terminal) that communicate with each other. That means.

  Upon receiving a request from a terminal (for example, terminal T11), the application server 6 requests a resource management server (for example, resource management server RMS1) that manages resources of the autonomous system (for example, autonomous system AS1) to which the terminal belongs. A server that sends messages. The request message includes a resource securing request message for requesting securing of a resource required for communication, a resource change request message for requesting to change a secured resource, and a resource release request message for requesting release of a secured resource. is there.

  The resource management servers RMS1 to RMS3 are connected to be communicable with each other. When communication is performed between two terminals (for example, terminals T11 and T31) belonging to different autonomous systems, request messages are exchanged between a plurality of resource management servers (for example, resource management servers RMS1 to RMS3). To secure resources necessary for communication in the autonomous systems (for example, autonomous systems AS1 to AS3) managed by each.

1-3. Configuration of Resource Management Server Resource management servers RMS1 to RMS3 are computers each having a communication function, and each include a table creation unit, a table storage unit, a transmission / reception unit, a resource control unit, and a maintenance terminal. These basic functions are common to each of the resource management servers RMS1 to RMS3.
These functions are based on computer hardware resources such as an arithmetic unit (MPU) and a storage device (including an internal memory such as a ROM and a RAM and an external storage device such as an HDD) and a computer installed in this computer. -Realized by collaboration with programs (software).

FIG. 3 is a block diagram showing the configuration of the resource management server RMSi (i = 1, 2, 3).
The table creation unit 1 collects BGP route information from border routers belonging to the autonomous system ASi managed by the resource management server RMSi, calculates a communication route across a plurality of autonomous systems AS, and creates a table relating to the calculated communication route. To do.
The table storage unit 2 holds various tables necessary for resource management, including the table created by the table creation unit 1.
The transmission / reception unit 3 includes a communication interface, and the application server 6 and other resource management servers (hereinafter simply referred to as “adjacent servers”) RMSi−1 and RMSi + 1 adjacent to the resource management server RMSi and the managed autonomous system AS. Send and receive request messages.
The resource control unit 4 secures and releases resources in the autonomous system ASi managed by the resource management server RMSi in accordance with the received request message, and requests messages to be transmitted to the adjacent server RMSi + 1 as necessary Create
The maintenance terminal 5 is a terminal used for maintenance management of the resource management server RMSi by a maintenance person.

Hereinafter, functions of each unit of the resource management server RMSi will be described in more detail.
1-3-1. Table storage unit 2
As shown in FIG. 3, the table storage unit 2 includes an address list 21, a route information table 22, a link information table 23, a BGP route management information table 24, a BGP link information table 25, an IP prefix information table 26, and a border router priority order. An information table 27 is held.

  Here, the address list 21 is a list of IP addresses of terminals belonging to the autonomous system ASi managed by the resource management server RMSi. For example, it consists of the IP address of the terminal (for example, the IP address of the terminal 11) and the IP address of the edge router that accommodates this terminal (for example, the IP address of the edge router ER11).

  The route information table 22 is a table relating to a communication route in the autonomous system ASi managed by the resource management server RMSi, as shown in FIG. For example, as shown in FIG. 4B, “ID representing route information”, “IP address of starting node”, “IP address of destination node”, “list of link ID”, “priority” It consists of.

The “originating node IP address” is the system IP address of the node that is the starting point of the communication path in the autonomous system ASi. When the calling terminal belongs to the autonomous system ASi, it becomes the IP address of the edge node that accommodates the calling terminal. Further, when the calling terminal belongs to another autonomous system, the IP address of the border router serving as an entrance from the autonomous system ASi-1 in the direction of the calling terminal in the autonomous system ASi.
The “IP address of the end node” is the system IP address of the node that is the end point of the communication path in the autonomous system ASi. When the called terminal belongs to the autonomous system ASi, it becomes the IP address of the edge node that accommodates the called terminal. Further, when the called terminal belongs to another autonomous system, the IP address of the border router serving as an exit to the autonomous system ASi + 1 in the called terminal direction in the autonomous system ASi.

The “link ID list” is a list of IDs of individual links that constitute a communication path in the autonomous system ASi, that is, individual links that connect between a start node and an end node.
“Priority order” indicates a preferred order as a communication path under various conditions when there are a plurality of communication paths having the same combination of the calling terminal and the called terminal. First, the communication path with the highest priority is used, and when a failure occurs in this communication path, the communication path with the second highest priority is replaced.

  The link information table 23 is a table related to information on links belonging to the autonomous system ASi managed by the resource management server RMSi. For example, as shown in FIG. 5, from “ID representing link information”, “link ID” unique to the link, “total resource capacity” of the link, and “resource remaining amount” available for the link Become.

  The BGP route management information table 24 is a table relating to a route between the autonomous system ASi managed by the resource management server RMSi and the adjacent autonomous system ASi + 1, as shown in FIG. For example, as shown in FIG. 6B, “ID indicating BGP route management information”, “origin AS number”, “destination AS number”, “IP address of origin border router (BR)”, It consists of “destination border router (BR) IP address”, “link ID list”, and “priority”.

The “starting AS number” is the number of the autonomous system ASi. When the autonomous system ASi is a subsystem, the number of the subsystem SubAS is entered.
The “destination AS number” is the number of the autonomous system ASi + 1 adjacent to the autonomous system ASi. When the adjacent autonomous system ASi + 1 is a subsystem, the number of the subsystem SubAS is entered.

The “originating border router IP address” is the system IP address of the border router belonging to the autonomous system ASi on the path between the autonomous systems ASi and ASi + 1. It corresponds to the exit to the adjacent autonomous system ASi + 1 in the autonomous system ASi. When the communication route in the autonomous system ASi reaches the adjacent autonomous system ASi + 1, the same address as the “IP address of the end node” in the route information table 22 is entered.
The “destination border router IP address” is the system IP address of the border router belonging to the adjacent autonomous system ASi + 1 on the path between the autonomous systems ASi and ASi + 1. It corresponds to the entrance from the autonomous system ASi in the adjacent autonomous system ASi + 1.

The “link ID list” is a list of IDs of links constituting a route between autonomous systems.
The “priority order” indicates a preferable order as a route under various conditions when there are a plurality of routes between the autonomous systems ASi and ASi + 1.

  The BGP link information table 25 is a table related to a link on a route between autonomous systems. For example, as shown in FIG. 7, “ID representing BGP link information”, “link ID” unique to the link, “total resource capacity” of the link, and “resource remaining amount” available for the link, Consists of.

The IP prefix information table 26 is a table indicating which autonomous system to reach a predetermined IP prefix (predetermined upper bits in the IP address) among the autonomous systems adjacent to the autonomous system ASi. It is. For example, as shown in FIG. 8A, it consists of a “destination AS number” and an “IP prefix”. The “destination AS number” is the number of the autonomous system to go to. When the autonomous system is a subsystem, the number of the subsystem SubAS is entered.
Specifically, as shown in FIG. 8C, in order to reach the IP prefixes # 100, # 101, # 200, and # 30 starting from the subsystem SubAS # 1, as shown in FIG. And autonomous system AS # 2, autonomous system AS # 2, autonomous system AS # 2, and subsystem SubAS # 2, respectively.

  The border router priority information table 27 is a table indicating which border router should be selected in order to go to the autonomous system ASi + 1 when there are a plurality of border routers connected to the same adjacent autonomous system Asi + 1. For example, as shown in FIG. 9, “ID indicating border router (BR) priority information”, “destination AS number”, “originating IP prefix”, “destination IP prefix”, “destination border router” (BR) IP address ”and“ priority ”.

The “destination AS number” is the number of the adjacent autonomous system ASi + 1. When the adjacent autonomous system ASi + 1 is a subsystem, the number of the subsystem SubAS is entered.
The “destination border router IP address” is the system IP address of the border router that connects with the autonomous system ASi + 1 associated with the “destination AS number” among the border routers belonging to the autonomous system ASi. The same address as the “originating border router IP address” in the BGP route management information table 24 is entered.
The “priority order” is a priority order in which the border router related to the “destination border router IP address” is selected when going to the autonomous system ASi + 1 related to the “destination AS number”.

  In the network configuration shown in FIG. 10A, the combination of the source IP prefix and the destination IP prefix follows the rules shown in FIG.

1-3-2. Table creation part 1
As illustrated in FIG. 3, the table creation unit 1 includes an intra-AS link information collection unit 11, an intra-AS table creation unit 12, a BGP route information collection unit 13, and a BGP table creation unit 14.

  Here, the intra-AS link information collection unit 11 periodically collects the resource capacity and connection information of the links in the autonomous system ASi from the routers belonging to the autonomous system ASi managed by the resource management server RMSi. For example, a general-purpose protocol such as SNMP (Simple Network Management Protocol) or MIB (Management Information Base) can be used.

The intra-AS table creation unit 12 calculates the communication path in the autonomous system ASi managed by the resource management server RMSi using the connection information of each link collected by the intra-AS link information collection unit 11. If possible, a plurality of communication paths having the same combination of the start node and the end node are calculated, and the priority order is determined between these communication paths.
The AS internal table creation unit 12 also creates the route information table 22 shown in FIG. 4B based on the communication path information obtained in this way, and stores it in the table storage unit 2. Further, the link information table 23 shown in FIG. 5 is created using the resource capacity of each link collected by the intra-AS link information collection unit 11 and stored in the table storage unit 2.
The intra-AS table creation unit 12 can calculate the communication path and update the tables 22 and 23 each time information is collected by the intra-AS link information collection unit 11.

The BGP route information collection unit 13 periodically collects BGP route information of the adjacent autonomous systems ASi-1, ASi + 1 from the border router belonging to the autonomous system ASi managed by the resource management server RMSi. For example, it collects as follows.
In response to a request message from the BGP route information collection unit 13, the border router has a function of returning BGP route information of the autonomous systems ASi-1, ASi + 1 held by the border router. Then, the BGP route information collection unit 13 can collect the BGP route information by transmitting a request message to the border router.
Alternatively, the border router uses the function of exchanging BGP route information with other border routers, and the BGP route information collection unit 13 impersonates as a pseudo border router, that is, one of the border routers belonging to the autonomous system Asi. It is also possible to collect route information.

  The BGP table creation unit 14 uses the BGP route information collected by the BGP route information collection unit 13 to calculate communication routes spanning a plurality of autonomous systems AS including the autonomous system ASi managed by the resource management server RMSi. If possible, a plurality of communication paths having the same combination of the calling terminal and the called terminal are calculated, and a priority order is determined between these communication paths. The communication path calculation method and the priority order determination method are based on BGP, and the same result as the calculation performed by the border router belonging to the autonomous system ASi must be obtained. The detailed algorithm will be described later.

The BGP table creation unit 14 also uses the BGP route management information table 24 shown in FIG. 6B and the IP prefix information table shown in FIG. 8A based on the communication route information obtained in this way. 26, the border router priority order information table 27 shown in FIG. 9 is created and stored in the table storage unit 2. Further, the BGP link information table 25 shown in FIG. 7 is created using the BGP route information collected by the BGP route information collection unit 13 and stored in the table storage unit 2.
The BGP table creation unit 14 can calculate a communication route and update the tables 24 to 27 each time information is collected by the BGP route information collection unit 13.

  The BGP route information collection unit 13 may collect only information on communication routes spanning a plurality of autonomous systems AS calculated by the border router from the border routers belonging to the autonomous system ASi. In this case, the BGP table creation unit 14 does not have to calculate the communication path.

1-3-3. Resource control unit 4
As shown in FIG. 3, the resource control unit 4 includes a message analysis unit 41, a destination terminal presence / absence determination unit 42, a resource management unit 43, and a message creation unit 44.
Here, the message analysis unit 41 analyzes various messages received by the transmission / reception unit 3. For example, the message analysis unit 41 identifies the IP address of the called terminal included in the resource securing request message.
The called terminal presence / absence determining unit 42 refers to the address list 21 of the table storage unit 2 and determines whether the called terminal corresponding to the IP address included in the received resource securing request message is managed by the resource management server RMSi. It is determined whether it belongs to the system ASi.

The resource management unit 43 refers to the tables 22 to 27 of the table storage unit 2 and specifies a communication path from information included in the received resource reservation request message, and secures resources necessary for communication.
As a result of the determination by the arrival terminal presence / absence determination unit 42, the message creation unit 44 sends a resource securing request message to be transmitted to the adjacent server RMSi + 1 in the arrival terminal direction when it is determined that the arrival terminal does not belong to the autonomous system ASi. create.

1-4. Next, resource securing processing when performing communication via a plurality of autonomous systems AS will be described.
FIG. 11 is a flowchart showing an outline of the flow of the resource securing process performed by the resource management server RMSi.

  When communication via a plurality of autonomous systems AS is started, a resource securing request message for requesting securing of resources necessary for the communication is sent from the adjacent server RMSi-1. This resource securing request message includes “IP address of originating terminal”, “IP address of terminating terminal”, “amount of resources to be secured”, and “IP address of ingress border router”. The “ingress border router IP address” is the system IP address of the border router that serves as an entrance from the autonomous system ASi-1 managed by the adjacent server RMSi-1 to the resource management server RMSi.

In the resource management server RMSi, when the transmission / reception unit 3 receives the resource reservation request message (step S1, YES), the message analysis unit 41 extracts information included in the resource reservation request message described above.
The called terminal presence / absence determining unit 42 checks whether the IP address of the called terminal is in the address list 21. As a result, if it is in the address list 21, it is determined that the called terminal is in the autonomous system ASi (step S2, YES). If it is not in the address list 21, the called terminal is in the autonomous system ASi. It is determined that it is not present (step S2, NO).

  If the called terminal is in the autonomous system ASi (step S2, YES), the resource management unit 43 specifies a communication path in the autonomous system ASi. Specifically, first, the address list 21 is referred to, and the IP address of the edge router that accommodates the called terminal is searched from the IP address of the called terminal. Then, referring to the route information table 22, the “IP address of the ingress border router” extracted from the resource securing request message is “IP address of the origin node”, and the IP address of the edge router that accommodates the destination terminal is “the destination node's IP address”. A communication route with “IP address” is searched. At this time, when there are a plurality of communication paths having the same combination of “IP address of starting node” and “IP address of end node”, the communication path with the highest priority is selected. Thereby, the communication path in the autonomous system ASi is specified (step S3).

  Subsequently, the resource management unit 43 reads the ID of the link constituting the communication path, and in the link information table 23, the “resource remaining amount” of the link corresponding to the read ID is extracted from the resource securing request message. Subtract the amount of resources you want to secure. Thereby, resources necessary for communication are secured in the autonomous system ASi (step S4).

On the other hand, as a result of the determination by the arrival terminal presence / absence determination unit 42, if the arrival terminal is not in the autonomous system ASi (step S2, NO), the communication path is specified as follows.
Here, the originating IP prefix corresponding to the upper bits of the IP address of the calling terminal and the called IP prefix corresponding to the upper bits of the IP address of the destination terminal are used. First, referring to the IP prefix information table 26, the “destination AS number” corresponding to the destination IP prefix is searched. This “destination AS number” indicates the number of the adjacent autonomous system ASi + 1 that should go to reach the destination IP prefix, and it can be seen that the communication path in the autonomous system ASi is connected to the adjacent autonomous system ASi + 1.

  Next, referring to the border router priority information table 27, the “destination border router IP address” corresponding to the obtained “destination AS number”, source IP prefix and destination IP prefix is the one with the highest priority. Search for. As a result, the border router having the highest priority among the border routers connected to the adjacent autonomous system ASi + 1 is known. Let this border router be the destination border router. This destination border router becomes an exit to the adjacent autonomous system ASi + 1 in the autonomous system ASi.

  Next, with reference to the route information table 22, the “ingress border router IP address” extracted from the resource securing request message is retrieved from the “originating node IP address” and the border router priority information table 27. A communication path having “IP address” as “IP address of destination node” is searched. At this time, when there are a plurality of communication paths having the same combination of “IP address of starting node” and “IP address of end node”, the communication path with the highest priority is selected. Thereby, a communication path in the autonomous system ASi is specified.

  Next, referring to the BGP route management information table 24, the autonomous system ASi number is “originating AS number”, the “destination AS number” retrieved from the IP prefix information table 26 is “destination AS number”, and border router priority information. A communication route is searched with the “IP address of the destination border router” retrieved from the table 27 as the “IP address of the origin border router”. At this time, if there are a plurality of communication paths, the communication path with the highest priority is selected. Thereby, the communication path from the autonomous system ASi to the adjacent autonomous system ASi + 1 is specified. The destination border router related to the “IP address of the destination border router” of this communication path becomes an entrance from the autonomous system ASi in the adjacent autonomous system ASi + 1 (step S5).

  Subsequently, the resource management unit 43 reads the ID of the link constituting the communication path in the autonomous system ASi from the path information table 22, and the “resource remaining amount” of the link corresponding to the read ID in the link information table 23. Then, the “resource amount to be secured” extracted from the resource securing request message is subtracted. Further, the ID of the link constituting the communication path between the autonomous system ASi and the adjacent autonomous system ASi + 1 is read from the BGP path management information table 24, and the “resource” of the link corresponding to the read ID is read from the BGP link information table 25. The “resource amount to be secured” extracted from the resource securing request message is subtracted from the “remaining amount”. Thereby, resources necessary for communication are secured in the autonomous system ASi and between the adjacent autonomous system ASi + 1 (step S6).

The message creation unit 44 creates a resource securing request message to be transmitted to the adjacent server RMSi + 1 that manages the adjacent autonomous system ASi + 1 to which the communication path is connected. In this resource securing request message, in addition to “IP address of originating terminal”, “IP address of terminating terminal”, “amount of resources to be secured”, “IP address of destination border router” obtained from BGP route management information table 24 "Is added as" IP address of ingress border router ".
The transmission / reception unit 3 transmits the resource securing request message created by the message creation unit 44 to the adjacent server RMSi + 1 (step S7).

  For example, when communication is performed between the terminal T11 belonging to the autonomous system AS1 and the terminal T31 belonging to the autonomous system AS3, the resource management server RMS1 that manages the autonomous system AS1 performs the processes of steps S1, S2, S5 to S7. The resource management server RMS2 that manages the autonomous system AS2 performs the processing of steps S1, S2, S5 to S7, and the resource management server RMS3 that manages the autonomous system AS3 performs the processing of steps S1 to S4. A series of resources spanning the autonomous systems AS1 to AS3 can be secured.

  Thereafter, when the communication is terminated, the secured resources are released in the same manner as when the resources are secured.

1-5. Communication Route Calculation Method Next, a communication route calculation method in BGP will be described as a communication route calculation method that spans a plurality of autonomous systems AS.
For calculation of the communication path in BGP, for example, the path attribute of RFC1771 shown in FIG. 12 can be used. Here, in particular, “Origin”, “AS_Path”, “Next_Hop”, “Multi_Exit_Discriminator (MED)”, and “Local_Preference” are used.

“Origin” is an attribute that distinguishes where the notified route information is, and each value of “IGP (Interior Gateway Protocol)”, “EGP (Exterior Gateway Protocol)”, and “INCOMPLETE” is set. Have. The meaning of each value is as shown in FIG.
“AS_Path” is an attribute that sequentially indicates the number of the autonomous system AS on the route.
“Next_Hop” is an attribute indicating the number of the next border router on the route from the origin to the destination. This “Next_Hop” is overwritten with the number of the border router when entering the EBGP link (when exiting from one autonomous system AS) in the route from the destination to the origin, and the route information source side from the border router Be representative of This represents the origin of the route information, and becomes the next destination (Next_Hop) when the border router that has received this route information performs communication according to this route information. In principle, it is not overwritten in the link of IBGP.
“MED” is an attribute that directly indicates the priority of the link when there are a plurality of parallel paths (links) between the autonomous systems AS, and a different value is set and exchanged for each adjacent border router.
“Local_Preference” is an attribute indicating a priority set for each autonomous system AS when there are a plurality of routes passing through different autonomous systems AS. For routes with different destinations, different priorities can be set for the same autonomous system AS.

The priority order of communication paths is determined according to the above-described path attribute conditions and the following logic.
Step A: A route that cannot reach the destination from the origin is deleted by “Next_Hop”.
Step B: Increase the priority of a route with a large “Local_Preference”.
Step C: When “Local_Preference” is the same, if there is a route generated in the own router, the priority of the route is increased.
Step D: When there is no route generated by itself, the priority of the route having the short “AS_Path” is increased.
Step E: When “AS_Path” is the same, the priority of the route with a small “Origin” is increased.
Step F: When “Origin” is the same, the priority of a route with a small “MED” is increased.
Step G: When both the IBGP peer and the EBGP peer have advertised, prioritize the EBGP peer over the IBGP peer.
Step H: In the case of IBGP, the priority of the route of a peer close by IGP is increased. In the case of EBGP, the priority of the route that has been advertised is increased.
Step J: Increase the priority of the route of a peer with a small border router ID.
Step I: Increase the priority of the route of the peer having a large IP address.

  Information on the communication path whose priority is determined in this way is stored in the BGP path management information table 24, and the communication path with the highest priority is used for the resource securing process.

1-6. Specific Example Next, a method for creating a table used for specifying a communication path will be described using a specific example.

1-6-1. Communication Network Model FIG. 14 is a diagram showing a simplified model of a communication network.
The communication network shown here has autonomous systems AS # 100 and AS # 200. The AS # 100 further includes subsystems SubAS # 101 and SubAS # 102.

  SubAS # 101 is an edge router ER with network ID (nw_id) # 1001 (hereinafter abbreviated as “ER # 1001”) and a border router BR with network ID # 1002 (hereinafter abbreviated as “BR # 1002”). ). SubAS # 101 is connected to SubAS # 102 via BR # 1002. As shown in FIG. 15, the system IP of ER # 1001 is set to “192.168.0.1”. Further, it is assumed that the system IP of BR # 1002 is “192.168.0.2” and IF_IP # 1 is “fd81: 3c00: 2000: 1000 :: 1”.

  SubAS # 102 is a border router BR having a network ID # 1003 (hereinafter abbreviated as “BR # 1003”) and a border router BR having a network ID # 1004 (hereinafter abbreviated as “BR # 1004”). Have SubAS # 102 is connected to SubAS # 101 and AS # 200 via BR # 1003 and BR # 1004, respectively. As shown in FIG. 15, it is assumed that the system IP of BR # 1003 is “192.168.0.3” and IF_IP # 2 is “fd81: 3c00: 2000: 1000 :: 2”. Further, it is assumed that the system IP of BR # 1004 is “192.168.0.4”, and IF_IP # 3 is “fd81: 3c00: 4000: 1000 :: 1”.

  The AS # 200 has a border router BR (hereinafter abbreviated as “BR # 2004”) whose network ID is # 2004. AS # 200 is connected to SubAS # 102 via BR # 2004. As shown in FIG. 15, it is assumed that the system IP of BR # 2004 is “172.23.129.4” and IF_IP # 4 is “fd81: 3c00: 4000: 1000 :: 2”.

Also, IP prefix # 1 “fd81: 3c00: 2000: 0000 :: / 64” belongs to ER # 1001, and IP prefix # 3 “fd81: 3c04: 0000: 0000 :: / 64 ".
SubAS # 101 is managed by resource management server RMS # 101. SubAS # 102 is managed by resource management server RMS # 102. SubAS # 200 is managed by resource management server RMS # 200.

1-6-2. BGP Route Information FIG. 16 is a diagram showing a list of BGP route information collected by the RMSs # 101, # 102, and # 200.
The RMS # 102 can collect the BGP route information of (1) to (3) in FIG. 16 from the BR # 1004 of the SubAS # 102. “Da_prefix” represents a destination IP prefix. As shown in FIG. 17A, FIG. 16A shows route information from BR # 1004 to “fd81: 3c04: 0000: 0000 :: / 64” (IP prefix # 3). FIG. 16B shows route information from BR # 1004 toward “fd81: 3c00: 3000: 0000 :: / 64” (IP prefix # 2 belonging to SubAS # 102). FIG. 16 (3) shows route information from BR # 1004 toward “fd81: 3c00: 2000: 0000 :: / 64” (IP prefix # 1).

  The RMS # 102 can also collect the BGP route information of (4) to (6) in FIG. 16 from the BR # 1003 of the SubAS # 102. As shown in FIG. 17 (b), FIG. 16 (4) shows route information from BR # 1003 toward "fd81: 3c04: 0000: 0000 :: / 64" (IP prefix # 3). FIG. 16 (5) shows route information from BR # 1003 toward "fd81: 3c00: 3000: 0000 :: / 64" (IP prefix # 2). FIG. 16 (6) shows route information from BR # 1003 toward “fd81: 3c00: 2000: 0000 :: / 64” (IP prefix # 1).

  The RMS # 101 can collect the BGP route information of (7) to (9) in FIG. 16 from the BR # 1002 of the SubAS # 101. As shown in FIG. 17 (c), FIG. 16 (7) shows route information from BR # 1002 toward "fd81: 3c04: 0000: 0000 :: / 64" (IP prefix # 3). FIG. 16 (5) shows route information from BR # 1002 toward “fd81: 3c00: 3000: 0000 :: / 64” (IP prefix # 2). FIG. 16 (6) shows route information from BR # 1002 toward “fd81: 3c00: 2000: 0000 :: / 64” (IP prefix # 1).

1-6-3. IP Prefix Information Table FIG. 18 is a diagram illustrating a method for creating an IP prefix information table.
For example, the RMS # 102 can receive BGP route information (1), (2) or (5), (6) shown in FIG. 18A (BGP route information (1), (2) or ( By extracting “as_pass” and “da_prefix” of 5) and (6), the IP prefix information table shown in FIG. 18B can be created. The same applies to RMS # 101.

1-6-4. Border Router Priority Information Table FIG. 19 is a diagram for explaining a method of creating a border router priority information table from BGP route information collected by the RMS # 101.
The RMS # 101 can collect the BGP route information (7) to (9) shown in FIG. 19A (same as the BGP route information (7) to (9) shown in FIG. 16) from the BR # 1002. it can.

  As shown in FIG. 20, the source IP prefix “fd81: 3c00: 2000: 0000 :: / 64” (IP prefix # 1) to the destination IP prefix “fd81: 3c04: 0000: 0000 :: / 64” (IP prefix # Consider the route to 3). As shown in FIG. 19, in the BGP path information (7) with “da_prefix” being “fd81: 3c04: 0000: 0000 :: / 64”, “200” of “as_path” is set to “destination SubAS” and BR # 1002 By setting the IP address “192.168.0.2” as the “IP address of the destination border router”, the border router priority information table can be created.

  Similarly, the route from the originating IP prefix “fd81: 3c00: 2000: 0000 :: / 64” (IP prefix # 1) to the destination IP prefix “fd81: 3c00: 3000: 0000 :: / 64” (IP prefix # 2) think of. In the BGP path information (8) where “da_prefix” is “fd81: 3c00: 3000: 0000 :: / 64”, “102” of “as_path” is “destination SubAS” and the IP address “192.168.0.2” of BR # 1002 Is set as the “IP address of the destination border router”, the border router priority order information table can be created.

FIG. 21 is a diagram for explaining a method of creating a border router priority order information table from BGP route information collected by RMS # 102.
The RMS # 102 can collect the BGP route information (1) to (6) shown in FIG. 16 from the BR # 1003 and the BR # 1004.

Regarding the BGP route information (1) to (6), the following routes are considered for the source IP prefix and the destination IP prefix, respectively.
(1) fd81: 3c00: 3000: 0000 :: / 64 → fd81: 3c04: 0000: 0000 :: / 64
(2) fd81: 3c04: 0000: 0000 :: / 64 → fd81: 3c00: 3000: 0000 :: / 64
(3) fd81: 3c04: 0000: 0000 :: / 64 → fd81: 3c00: 2000: 0000 :: / 64
(4) fd81: 3c00: 2000: 0000 :: / 64 → fd81: 3c04: 0000: 0000 :: / 64
(5) fd81: 3c00: 2000: 0000 :: / 64 → fd81: 3c00: 3000: 0000 :: / 64
(6) fd81: 3c00: 3000: 0000 :: / 64 → fd81: 3c00: 2000: 0000 :: / 64

  The route (4) is equal to the route (5) → route (1), and the route (3) is equal to the route (2) → route (6). Therefore, the route (4) can be specified by combining the routes (5) and (1), and the route (3) can be specified by combining the routes (2) and (6). Therefore, a border router priority information table shown in FIG. 21 may be created from the BGP route information (1) to (6).

1-7. Effects of the present embodiment In the present embodiment, a communication path extending between the autonomous system ASi managed by the resource management server RMSi and the adjacent autonomous systems ASi-1, ASi + 1 is calculated based on the BGP path information possessed by the border router. Then, the IP address of the border router serving as the gateway of the communication path from the autonomous system ASi to the adjacent autonomous systems ASi-1 and ASi + 1 is held. Thus, even when there are a plurality of border routers that can be gateways of communication paths to the adjacent autonomous systems ASi-1, ASi + 1, an appropriate gateway can be easily set in the resource management server RMSi.

  In addition, since the IP address of the border router serving as an entrance / exit can be automatically set, the complexity of manual setting can be eliminated and setting (or resetting) in a short time is possible. Therefore, for example, even when a failure occurs in the autonomous system ASi and the communication path must be changed, the entrance / exit can be updated in a short time, and resource management can be performed without delay.

2. Second Embodiment Next, a second embodiment of the present invention will be described. In the present embodiment, even when a failure occurs in a communication path, resource management can be continuously performed.
FIG. 22 is a block diagram showing the configuration of the resource management server RMSi (i = 1, 2, 3) according to the second embodiment of the present invention. In this figure, the same reference numerals as those in FIG. 3 are used for the same elements as those shown in FIG.

  The table storage unit 102 holds an address list 21, a route information table 122, a link information table 123, a BGP route management information table 124, a BGP link information table 125, an IP prefix information table 26, and a border router priority order information table 27.

  The route information table 122 and the BGP route management information table 124 have the items of “in-use resource amount” and “failure flag” as shown in FIGS. 23 and 25, respectively, and the route information in the first embodiment, respectively. Different from the table 22 and the BGP route management information table 24. The “in-use resource amount” is a resource amount already secured in the communication path. The “failure flag” is set when a failure occurs in any of the links included in the communication path. For example, the value of this item is normally “0”, and when a failure occurs, the value changes from “0” to “1”.

  The link information table 123 and the BGP link information table 125 have an item of “failure flag” as shown in FIGS. 24 and 26, respectively, and the link information table 23 and the BGP link information table 25 in the first embodiment, respectively. And different. The “failure flag” is set when a failure occurs in the link.

The table creation unit 101 includes an intra-AS link information collection unit 111, an intra-AS table creation unit 112, a BGP route information collection unit 113, and a BGP table creation unit 114.
Here, the intra-AS link information collection unit 111, in addition to the function of the intra-AS link information collection unit 11 in the first embodiment, from the router belonging to the autonomous system ASi managed by the resource management server RMSi, It has a function of collecting failure information of links, nodes, interface boards, and L2SWs in ASi. For example, general-purpose protocols such as SNMP, SNMP trap, and MIB can be used. Each router may be set to transmit failure information to the resource management server RMSi when a link or the like fails. The intra-AS link information collection unit 111 may periodically collect and recollect failure information in consideration of failure to receive failure information.

  The AS internal table creation unit 112 has the following functions in addition to the functions of the AS internal table creation unit 12 in the first embodiment. That is, the failed link is identified based on the failure information received by the intra-AS link information collection unit 111, and a failure flag is set in the failed link column in the link information table 123. Further, a communication path including a broken link is searched in the path information table 122, and a failure flag is set in the field of the communication path. A communication path including a broken link is called a “failure path”. When the failed link is recovered, the failure flag is reset in the route information table 122 and the link information table 123.

  In addition to the function of the BGP route information collection unit 13 in the first embodiment, the BGP route information collection unit 113 is adjacent to the autonomous system ASi from a border router belonging to the autonomous system ASi managed by the resource management server RMSi. It has a function of collecting failure information such as a link with the autonomous system ASi + 1. The failure information collection method may be the same as that of the intra-AS link information collection unit 111.

  The BGP table creation unit 114 has the following functions in addition to the functions of the BGP table creation unit 14 in the first embodiment. That is, the failed link is identified based on the failure information received by the BGP route information collection unit 113, and a failure flag is set in the failed link column in the BGP route management information table 124. Further, the communication path including the broken link is searched in the BGP link information table 125, and a failure flag is set in the field of the communication path. A communication path including a broken link is called a “failure path”. When the failed link is recovered, the failure flag is reset in the BGP route management information table 124 and the BGP link information table 125.

The resource control unit 104 includes a message analysis unit 41, a destination terminal presence / absence determination unit 42, a resource management unit 143, and a message creation unit 44.
The resource management unit 143 has the following function in addition to the function of the resource management unit 43 in the first embodiment.
First, the route information table 122 and the BGP route management information table 124 are monitored, and when a failure flag is set in any of the communication route columns, it is determined whether or not the failure route is currently used. For example, if the failure path has the highest priority compared to other communication paths for which no failure flag is set, it can be determined that the failure path is in use.

If the failure path is currently used, the use of the communication path is stopped thereafter, and the communication path having the second highest priority is used instead of the communication path. The communication path used instead is called “alternative path”.
At this time, referring to the “in-use resource amount” in the route information table 122 or the BGP route management information table 124, it is determined whether or not the resource is secured in the failed route. , Transshipment of reserved resources to alternative routes. Reloading resources is performed as follows.

  First, the ID of the link constituting the failure path is read, and in the link information table 123 or link information table 125, the “resource remaining in use” of the failure path is added from the “resource remaining amount” of the link corresponding to the read ID. To do. Further, the ID of the link constituting the alternative route is read, and the “resource remaining amount” of the failure route is subtracted from the “resource remaining amount” of the link corresponding to the read ID in the link information table 123 or the link information table 125. To do. Further, the value of “in-use resource amount” of the failure path is set to “0”, and the value is written in “in-use resource amount” of the alternative route. Thereby, the transshipment of resources is completed.

  When the failed link is recovered and the failure flag is reset, the resources secured in the alternative path are loaded back to the original communication path including the recovered link. The resource unloading may be performed in the same manner as the resource reloading described above.

As described above, when a failure occurs in a link, it is possible to continue resource management by transshipment of resources reserved for the communication path including the link to another communication path. Become.
In addition, when a resource is reloaded (including unloading), a message indicating processing content may be transmitted to the maintenance terminal and a log may be created. As a result, even when the remaining resources of the links that constitute the route of the transshipment destination are insufficient and the resource transshipment cannot be performed appropriately, the verification becomes easy. In addition, it is possible to urge the maintenance person not to charge for the reloading of resources.

3. Third Embodiment Next, a third embodiment of the present invention will be described. In the present embodiment, information that associates an autonomous system adjacent to an autonomous system managed by a resource management server with a resource management server that manages the adjacent autonomous system can be automatically generated.
FIG. 27 is a block diagram showing the configuration of the resource management server RMSi (i = 1, 2, 3) according to the third embodiment of the present invention. In this figure, the same reference numerals as those in FIG. 3 are used for the same elements as those shown in FIG.

The resource control unit 204 includes a message analysis unit 241, a destination terminal presence / absence determination unit 42, a resource management unit 243, and a message creation unit 244.
In addition to the function of the message creation unit 44 in the first embodiment, the message creation unit 244 assigns the number of the autonomous system ASi (which may be a subsystem SubASi) managed by the resource management server RMSi to other resources It has a function of creating an AS number notification message to be notified to the management server. The AS number notification message includes an identifier indicating that this message is an AS number notification message, an autonomous system ASi number (identifier) managed by the resource management server RMSi, and an identifier (specifically, the resource management server RMSi). , ID and IP address). The AS number notification message is transmitted from the transmission / reception unit 3 to another resource management server.

In addition to the function of the message analysis unit 41 in the first embodiment, the message analysis unit 241 includes an autonomous system number added to the message when the analyzed message is an AS number notification message, a resource management server Is extracted and output to the resource management unit 243 (identifier extraction function).
In addition to the function of the resource management unit 43 in the first embodiment, the resource management unit 243 creates a management target table 228 that associates the autonomous system number extracted from the message with the identifier of the resource management server, It has a function of storing in the table storage unit 202.

  An example of the management target table 228 is shown in FIG. The autonomous system number is written in “AS number”, the resource management server ID is written in “server ID”, and the IP address of the resource management server is written in “server IP address”. The autonomous system represented by “AS number” is an autonomous system managed by a resource management server specified by “server ID” or “server IP address”. Therefore, by adding the above-described function to the resource control unit 204, it is possible to automatically generate information that associates an adjacent autonomous system with a resource management server that manages the autonomous system.

  The management target table 228 is used when, for example, a resource securing request message is transmitted to the adjacent server RMSi + 1. That is, after the resource management unit 243 searches for the “destination AS number” of the adjacent autonomous system ASi + 1 on the called side from the IP prefix information table 26, the resource management unit 243 refers to the management target table 228 and searches for the “server ID corresponding to the searched destination AS number. "And" IP address of server ". The resource management server RMSi + 1 specified by the searched “server ID” or the like is a server that manages the adjacent autonomous system ASi + 1 on the called side. Therefore, by transmitting a resource securing request message to the resource management server RMSi + 1, resource management in the adjacent autonomous system ASi + 1 on the called side becomes possible.

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

It is a block diagram which shows the structure of the communication network to which the resource management system concerning the 1st Embodiment of this invention is applied. It is a block diagram which shows the outline | summary of the resource management system concerning the 1st Embodiment of this invention. It is a block diagram which shows the structure of the resource management server in the 1st Embodiment of this invention. It is a figure explaining a route information table. It is a figure which shows an example of the data structure of a link information table. It is a figure explaining a BGP path | route management information table. It is a figure which shows an example of the data structure of a BGP link information table. It is a figure explaining an IP prefix information table. It is a figure which shows an example of the data structure of a border router priority order information table. It is a figure which shows the rule of the combination of an outgoing IP prefix and an incoming IP prefix. It is a flowchart which shows the flow of the resource securing process by a resource management server. It is a figure which shows the list | wrist of a path attribute. It is a figure explaining "Origin". It is a figure which shows the model which simplified the communication network used for description of the table preparation method. It is a figure which shows the specific examples, such as an address. It is a figure which shows the list of BGP path | route information collected by the resource management server. It is a figure explaining the BGP path | route information shown in FIG. It is a figure explaining the preparation method of an IP prefix information table. It is a figure explaining the method to produce a border router priority information table from the BGP path | route information collected by RMS # 101. It is a figure which shows the path | route in RMS # 101. It is a figure explaining the method to produce a border router priority information table from the BGP path | route information collected by RMS # 102. It is a block diagram which shows the structure of the resource management server concerning the 2nd Embodiment of this invention. It is a figure which shows the other example of the data structure of a path | route information table. It is a figure which shows the other example of the data structure of a link information table. It is a figure which shows the other example of the data structure of a BGP path | route management information table. It is a figure which shows the other example of the data structure of a BGP link information table. It is a block diagram which shows the structure of the resource management server concerning the 3rd Embodiment of this invention. It is a figure which shows an example of the data structure of a management object table.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1,101 ... Table creation part, 11, 111 ... AS link information collection part, 12, 112 ... AS table creation part, 13, 113 ... BGP route information collection part, 114, 114 ... BGP table creation part, 2, 102, 202 ... Table storage unit, 21 ... Address list, 22, 122 ... Route information table, 23, 123 ... Link information table, 24, 124 ... BGP route management information table, 25, 125 ... BGP link information table, 26 ... IP prefix information table, 27 ... border router priority order information table, 228 ... management target table, 3 ... transmission / reception unit, 4, 104, 204 ... resource control unit, 41, 241 ... message analysis unit, 42 ... destination terminal presence / absence determination unit 43, 143, 243 ... resource management unit, 44, 244 ... message creation unit, 5 ... Mamoru terminal, 6 ... application server, AS ... autonomous system, BR ... border router, ER ... edge router, RMS ... resource management server, SubAS ... subsystem, T ... terminal.

Claims (13)

A resource management device that manages resources of an autonomous system adjacent to another autonomous system via a plurality of border routers,
The BGP route information to the other autonomous system acquired by the border router belonging to the managed autonomous system by exchanging information with other border routers by BGP is obtained from the border router belonging to the managed autonomous system. Route information collecting means for collecting periodically by BGP ,
A communication path calculating unit that calculates a communication path spanning the managed autonomous system and the other autonomous system based on the collected BGP path information each time the BGP path information is collected by the path information collecting unit; ,
Communication that stores information on the calculated communication route and stores information on a border router that is an exit or entrance of a communication route from the managed autonomous system to the other autonomous system as one of the communication route information A resource management device comprising: path information storage means. The resource management device according to claim 1,
The communication path information storage means stores information on a communication path in the managed autonomous system as one of the communication path information. The resource management device according to claim 2,
When receiving a request for securing a resource necessary for communication across the managed autonomous system and the other autonomous system, the communication path information is referred to and connected to the exit or entrance to the other autonomous system. A resource management apparatus further comprising resource securing means for selecting a communication path in the autonomous system to be managed and performing a resource securing process for the communication path. The resource management device according to claim 3,
The communication path calculation means calculates a plurality of communication paths with the same combination of communication origination terminal and destination terminal,
further,
A failure information collecting means for collecting information on a failure of the communication path from a node constituting the managed autonomous system;
Resource re-transmission means for referring to the communication path information and for reserving resources reserved for the communication path in which the failure has occurred to another communication path that is the same as the communication path and the originating terminal and the terminating terminal. A resource management device. The resource management apparatus according to claim 4, wherein
The communication path calculation means determines a priority order among a plurality of communication paths,
The communication path information storage means stores the priority as one of the communication path information,
The resource securing means performs the resource securing process for the communication path with the highest priority,
The resource transshipment unit transships resources reserved for the communication path in which a failure has occurred to a communication path having a higher priority next to the communication path. In the resource management device according to any one of claims 1 to 5,
Creating a message with the identifier of the resource management device and the identifier of the managed autonomous system, and sending the message to other resource management devices;
Message receiving means for receiving a message to which an identifier of another resource management device and an identifier of an autonomous system to be managed by the other resource management device are added;
Identifier extracting means for extracting two identifiers from the received message;
A resource management device further comprising: a management target storage unit that associates the extracted two identifiers with each other and stores a management target of the other resource management device. A resource management system for managing resources of a communication network composed of a plurality of autonomous systems adjacent via a plurality of border routers using a plurality of resource management devices,
The resource management apparatus according to any one of claims 1 to 6, wherein the resource management apparatus is the resource management apparatus according to any one of claims 1 to 6. A resource management method for managing resources of an autonomous system adjacent to another autonomous system via a plurality of border routers,
The BGP route information to the other autonomous system acquired by the border router belonging to the managed autonomous system by exchanging information with other border routers by BGP is obtained from the border router belonging to the managed autonomous system. Collecting regularly by BGP ;
A step of calculating a communication path spanning the managed autonomous system and the other autonomous system based on the collected BGP path information each time the BGP path information is collected ;
Storing the calculated communication path information, and storing border router information serving as an exit or entrance of the communication path from the managed autonomous system to the other autonomous system as one of the communication path information; A resource management method comprising: The resource management method according to claim 8, wherein
The step of storing the communication path information stores the information of the communication path in the managed autonomous system as one of the communication path information. The resource management method according to claim 9, wherein
When receiving a request for securing a resource necessary for communication across the managed autonomous system and the other autonomous system, the communication path information is referred to and connected to the exit or entrance to the other autonomous system. A resource management method further comprising a step of selecting a communication path in the autonomous system to be managed and performing a resource securing process on the communication path. The resource management method according to claim 10,
The step of calculating the communication path calculates a plurality of communication paths in which the combination of the communication source terminal and the destination terminal is the same,
further,
Collecting information on communication path failure from nodes constituting the managed autonomous system;
A step of referring to the communication path information, and re-loading resources reserved for the communication path in which the failure has occurred to another communication path that is the same as the communication path and the calling terminal and the called terminal. Resource management method. The resource management method according to claim 11,
The step of calculating the communication path determines priority among a plurality of communication paths,
The step of storing the communication path information stores the priority order as one of the communication path information,
The step of performing the resource securing process performs the resource securing process for the communication path having the highest priority,
The step of transloading the resource comprises translocating a resource reserved for the communication path in which a failure has occurred to a communication path having a higher priority next to the communication path. In the resource management method of any one of Claims 8-12,
Creating a message with the identifier of the autonomous system to be managed and the identifier of the resource management device that manages this autonomous system, and sending it to another resource management device;
Receiving a message to which an identifier of the other autonomous system and an identifier of another resource management device that manages the autonomous system are added; and
Extracting two identifiers from the received message;
The resource management method further comprising: associating the extracted two identifiers with each other and storing a management target of the other resource management device.

Images