JP2002051076A - Management server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a management server that enhances efficiency of resource reservation, extends opportunity of the resource reservation to users, and simplify the resource reservation. SOLUTION: The management server managing band assignment is provided with a resource management database that stores resource information, a 1st resource management section that references the resource management database to discriminate whether or not a band requested to be secured can be ensured, a list registration section that registers the band secured request to a wait list when it is discriminated that the band cannot be secured, a 1st setting management section that makes a secured setting request of the band instructed by the band secured request, a 1st database management section that updates the resource management database on the basis of the secured setting request and a release of a band between repeaters, and a 2nd resource management section that references the resource management database on the basis of the band release between the repeaters and discriminates whether or not the band between the repeaters and passing through a path with respect to the band secured request registered in the wait list can be secured.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a management server, and more particularly to a management server that implements centralized management and automatic setting of network devices or resources based on a policy.
The present invention relates to a technique for securing a bandwidth by a server (hereinafter, a management server) in a BN (Policy Based Networking) network.

[0002]

2. Description of the Related Art An IP network is composed of a plurality of routers for relaying IP packets, and IP packets transmitted from a plurality of communication terminals such as personal computers are relayed by routers to communicate with other communication devices. Delivered to Generally, an IP packet can be delivered to a partner communication terminal without previously securing a band of a communication path connecting the partner communication devices. However, if a band cannot be secured due to an increase in traffic, the IP packet is discarded. Therefore,
In order to prevent the IP packet from being discarded, a technique of previously securing a band to be used between routers serving as a route passing between a communication source and a communication destination is used. For example, a user who wants to receive a video service provided by a video server can provide a video service by using a communication terminal to secure a band between the communication terminal and the video server in advance in accordance with a video transmission rate. Can receive. As one means of bandwidth reservation, RSVP
(resource reservation Protocol).

FIG. 21 is a diagram showing bandwidth reservation by RSVP. When receiving a video service or the like from the server 6 such as a video server, the communication terminal 2 # Ai (i = 1 to n) requests a resource reservation (Resv message) to the RSVP router 4 # 1 located on the route. I do. Re
The sv message flows from the communication terminal 2 # Ai, which is the data receiver (request sender), to the data sender. The message (Pass message) of the answer (possibility of resource reservation) of the router 4 # i in response thereto is returned to the data receiver by a completely reverse route. Here, if one of the resources of the router on the route cannot be secured, the request is rejected. If your request is denied,
When resource reservation is necessary, the user repeatedly makes resource requests until resources can be secured.

[0004] The same applies to a case where a management server (policy server) allocates a band to a user in a PBN network. The bandwidth allocated to the resource reservation is statically determined in advance, and the server performs the admission control of the bandwidth reservation from the user for each flow (resource reservation request) so as not to exceed the range. If it does, the request is denied.

[0005]

In the bandwidth reservation according to the above-mentioned method, if there is a resource, it is possible to secure the resource quickly and surely. However, in other cases, the request is rejected. If a resource becomes available, it is possible to make a reservation again, but the user cannot recognize the timing. Therefore, when a resource reservation is necessary, the request must be repeated until the request is accepted. This has the following problems.

[0006] Reservations can only be made when resources are available.

[0007] The user cannot grasp the status of securing resources.

[0008] Since a trigger for an invalid bandwidth request is generated, useless processing for securing traffic and bandwidth increases.

[0009] If the service level is the same, it is unfair because the service is provided on a first-come, first-served basis.

[0010] Since the process of securing the bandwidth is performed in units of flows (request units), the frequency of the process is increased, and extra traffic and processing are generated.

SUMMARY OF THE INVENTION The present invention has been made in view of the above, and has as its object to provide a management server capable of improving the efficiency of resource reservation, expanding the resource reservation opportunities for users, and simplifying resource reservation. And

[0012]

FIG. 1 is a diagram illustrating the principle of the present invention. As shown in FIG. 1, the management server includes a receiving unit 10,
It includes a resource management database 11, a first determination unit 12, a list registration unit 13, a second determination unit 14, a resource management unit 15, a waiting list 16, and a setting management unit 17. The receiving unit 10
Receives a bandwidth reservation request transmitted from a communication terminal or the like. The resource management database 11 stores resource information on the bandwidth that can be allocated to each relay device. The first determination unit 12 inquires the resource management unit 15 of the resource use status based on the bandwidth securing request. The resource management unit 15 responds to the inquiry about the resource use status from the first determination unit 12.
The resource management database 11 is searched, and a value of a bandwidth that can be secured by the relay device on the route related to the bandwidth securing request is returned.

[0013] Then, the first determination unit 12 determines whether or not a band related to the request can be secured based on the response.
When the first determining unit 12 determines that the bandwidth related to the bandwidth securing request cannot be secured, the list registering unit 13 registers the bandwidth securing request in the waiting list 16. Setting management unit 17
Performs the setting for securing the bandwidth indicated by the bandwidth securing request to the relay device related to the bandwidth securing request. The resource management unit 15
The resource management database 11 is updated based on the secure setting by the setting management unit 17 and the release of the bandwidth of the relay device. The resource management unit 13 determines that the bandwidth of the relay device is released by the second determination unit 14.
Notify. The second determination unit 14 inquires of the resource management unit 13 about the resource usage status, and determines whether or not the bandwidth of the relay device on the route related to the bandwidth securing request registered in the waiting list 16 can be secured. . From the result of the determination by the second determination unit 14, it is possible to reserve the band preferentially to the band reservation request waiting for the band reservation, thereby imparting fairness in the band reservation and securing the band again when rejected. No request is required, and traffic can be reduced.

[0014]

DESCRIPTION OF THE PREFERRED EMBODIMENTS First Embodiment FIG. 2 is a block diagram of PBN network according to a first embodiment of the present invention. For example, the communication terminal 20 # Ai (i = 1
To n) receive services such as video from the server 26, the management server automatically sets the routers 22 # 1, # 2, # 3, and # 4 on the routes 20 to 26 by using the Policy control protocol or the like. 20-26
Secure the band between.

As shown in FIG. 2, the PBN network includes a plurality of communication terminals 20 # Ai (i = 1 to n), a plurality of routers 22 # i (i = 1 to 6), a management server 24 and a server 26. Be composed. The communication terminal 20 # Ai is a terminal such as a personal computer, and communicates with the server 26 and the like according to a predetermined protocol such as TCP / IP.
When it is necessary to secure a band for receiving a distribution service of video or the like, and when the band is secured, a message to that effect is sent from the management server 24 to the communication terminal Ai (i = 1 to 1).
n). If the bandwidth is not secured, and the user wishes to wait for a reservation, the request is placed on the reservation list. Then, a message to that effect is notified from the management server 24. After that, when the band becomes available and the band can be secured, the communication terminal 20 # Ai is automatically secured by the management server 24 to the communication terminal 20 # Ai, and the band securing notification is sent. A notification is made as to whether or not bandwidth allocation is possible and bandwidth allocation is required.

In the former case, since the bandwidth is automatically secured, there is no need to make another bandwidth request. In addition, since the bandwidth request may be made again at the time of the notification, both the former and the latter can prevent the frequent useless requests when the bandwidth cannot be secured. As a result, unnecessary control traffic can be reduced. When the band reservation can be secured, either the former only, the latter only, or the user selecting by specifying the former or the latter when making a bandwidth request Is also possible.

The router 22 # i (i = 1 to 6) performs device setting for realizing the bandwidth reservation in accordance with an instruction from the management server 24, and notifies the management server 24 of the fact that the bandwidth has been secured. . If bandwidth could not be secured,
A message to that effect is transmitted to the management server 24. After the bandwidth is secured, if the received IP packet corresponds to the secured bandwidth, the IP packet is transferred in the bandwidth secured to the corresponding router. If the received IP packet does not correspond to the secured band, the packet is transferred in the best effort mode or the IP packet is discarded. Thus, the router 22
#I is a relay device that secures a band and routes an IP packet, and is not limited to a router as long as the relay device has a similar function in other than the IP network.

The management server 24 has the following functions.

Upon receiving the bandwidth reservation request message from the communication terminal 20 # Ai, the communication route is calculated from the communication destination address and the source address of the request (the address of the communication terminal 20 # Ai) indicated by the bandwidth reservation request message. . An address identifies a device,
For example, in an IP network, it usually means an IP address.

It is determined whether the required bandwidth can be secured on the calculated communication path.

When the required bandwidth can be secured, an instruction to set a device for realizing the bandwidth is issued to the router on the communication path. If the band is secured, the band information relating to the secured band is registered in the database, and a message to that effect is sent to the requesting communication terminal 20 # Ai.

If the required bandwidth cannot be secured, the bandwidth setting request is registered in the waiting list and a message to that effect is sent to the requesting communication terminal 20 # Ai.

When a bandwidth release request is received from the communication terminal 20 # Ai or when the bandwidth securing time has elapsed, a device release request is made to the corresponding router.

With the release of the bandwidth, a bandwidth setting request having a high priority and an old time registered in the waiting list is
It is determined whether the band can be secured.

If there is a band setting request for which a band can be secured, the same processing as described above is performed, and the request is deleted from the list. At this time, as described above, the user may be notified that the band can be secured without securing the band.

FIG. 3 is a functional block diagram of the management server 24 in FIG. As shown in FIG. 3, the management server 24
Has a user I / F unit 30, an event detection unit 32, an admission control unit 34, a topology database 36, a resource management unit 38, a resource management database 40, a list management unit 42, a waiting list 44, and a user profile 46. The user I / F unit 30 includes the communication terminal 2
From 0 # Ai, reception of a bandwidth securing request message and a bandwidth securing stop request message, transmission of a bandwidth securing result message to the communication terminal 20 # Ai, and the like are performed. Event detector 3
2 detects an event such as a bandwidth securing request / bandwidth securing stop request from a message input from the user I / F unit 30 and a bandwidth securing / bandwidth release notification from the resource management unit 38.
Notify the admission control unit 34.

The admission control section 34 has the following functions.

When a Bandwidth Securing Request is Detected by the Event Detection Unit 32 i) The route relating to the bandwidth allocating request is calculated with reference to the topology database 36. Router 2 located on the route
An inquiry is made to the resource management unit 38 as to whether there is a required bandwidth between 2 # i. As the route, a plurality of routes may be selectable. For example, the route is selected from the shortest route.

Ii) All routers 22 # located on the route
If the band can be secured for i, the setting management unit 48 is instructed to set the band for all the routers 22 # i. When receiving the notification of the band setting OK from the setting management unit 48, it notifies the user I / F unit 30 of the completion of the band setting. When the setting management unit 48 receives a notification that the band setting is NG, it notifies the user I / F unit 30 of the rejection of the band setting.

Iii) A certain router 22 # i located on the route
If the bandwidth cannot be secured for the request, the list management unit 42 is instructed to register the bandwidth securing request in the waiting list 44. Notify the user of band setting rejection.

When Resource Release Notification is Detected by the Event Detector 32 For all the bandwidth setting requests registered in the waiting list 44, the processing of i) and the processing of ii) are performed in order of priority and registration time ( However, the processing of the notification of the band rejection is performed). When the bandwidth is secured for the bandwidth setting request registered in the wait list 44, the bandwidth management server 42 instructs the wait list management unit 42 to delete the bandwidth setting request from the wait list 44.

The topology database 36 stores the router 2
2 # i (i = 1 to 5) and communication terminal 20 # Ai (i = 1
And n is a database for calculating a route related to a bandwidth setting request. In the topology database 36, for each router 22 # i, information on all neighboring routers and the accommodated communication terminal 20 # Ai, for example, addresses of each router, addresses of all routers adjacent to the router, and all accommodated routers Of the communication terminal 20 # Ai.

The resource management section 38 has the following functions.

When notified by the admission control unit 34 In the case of an inquiry, the resource management database 40 is searched, and the router 22 # i located on the route is responded to the admission control unit 34 with the band securing status. . The admission control unit 34 is notified of whether or not the band can be secured.

When notified by the setting management unit 48 i) When notified of the band release, the resource management database 40 is rewritten for the router 22 #i involved in the band release.

Ii) When the bandwidth reservation is notified, the resource management database 40 is rewritten for the router 22 # i involved in the bandwidth reservation.

FIG. 4 shows the resource management database 4 in FIG.
FIG. The resource management database 40 is a database for determining whether a required bandwidth of a router located on a route can be secured. For example, as shown in FIG. 4, for each router 22 # i,
The address of i (relay source address), the total bandwidth between the relay source and the relay destination, and the used bandwidth are registered.

The list management section 42 has the following functions.

When an instruction to register a waiting list is received from the admission control unit 34, the waiting list 4
The bandwidth request is registered at the position corresponding to the priority in the fourth.

When an instruction to search the waiting list 44 is received from the admission control unit 34, for a high priority and the same priority, the bandwidth request first registered in the waiting list 44 is searched sequentially, and Notify the mission control unit 34.

When a request to delete a bandwidth request from the waiting list 44 is received from the admission control unit 34, the bandwidth request is deleted from the waiting list 44.

FIG. 5 is a configuration diagram of the waiting list 44.
As shown in FIG. 5, the waiting list 44 is a list for registering a bandwidth request for which a bandwidth could not be secured in a waiting queue for each priority, and a table for storing a pointer to a leading bandwidth securing request for each priority. And a chain of bandwidth reservation requests for each priority. The chain of the bandwidth securing request is realized by, for example, a pointer to the record of the next bandwidth securing request in the record of each bandwidth securing request. next
Is, for example, a pointer from the earliest time registered in the waiting list 44 to the next latest time. The bandwidth securing request record is a record related to a bandwidth securing request from the communication terminal 20 # Ai. For example, it is composed of a request source address, a requested band, a communication destination address, a band securing time, and the like.
The request source address is the address of the communication terminal that has issued the bandwidth reservation request, the requested band is the band to be reserved, the communication destination address is the address of the data transmission source, and the band reservation time is the time for which the band is to be reserved. Value).

FIG. 6 is a configuration diagram of the user profile 46. The user profile 46 is a profile for determining a priority for each band securing request. For example, as shown in FIG. 6, an address (user address) of each communication terminal 20 # Ai and its priority are set. You.
The priority is set, for example, at the time of contract when a user subscribes to the PBN network.

The server 26 is a server that performs services such as video distribution. The management server 24 is a communication terminal 20
#Ai (i = 1 to n) and router 22 # i (i = 1 to
5) may be logically connected, may be connected by an IP network, or may be individually connected via a dedicated line.

FIG. 7 is an operation explanatory diagram of FIG. FIG. 8 is a flowchart of the admission control unit 34 in FIG. FIG. 9 is a flowchart of the resource management unit 38 in FIG. FIG. 10 is a flowchart of the setting management unit 48 in FIG.

The operation of FIG. 7 will be described below with reference to these figures.

(1) Resource securing (bandwidth securing) FIG. 11 is a diagram showing a resource securing request processing sequence.
It is assumed that the user has made a resource securing (bandwidth securing) request to the management server 24 in order to receive the service. For example, the communication terminal 20 # A1 requests the management server 24 to set the request source address to the address of the communication terminal 20 # A1, the communication destination address to the address of the server 26, the requested bandwidth, and the set time (if there is no restriction, this is true). Is transmitted.

The management server 24 receives the bandwidth setting request. As shown in (1) in FIG. 11, the user I / F unit 30 notifies the event detection unit 72 that the band securing request has been received.
Notify. The event detection unit 72 notifies the admission control unit 34 that a band securing request has been issued, as indicated by (2) in FIG.

At step S2 in FIG. 8, the admission control unit 34 determines which of the request and the resource use status notification from the user, based on the message content. If the request is from the user, the process proceeds to step S4. If it is a resource use status notification, the process proceeds to step S20. Here, since it is a request from the user, step S4
Proceed to. In step S4, the request is analyzed.
In step S5, it is determined whether the request is a resource reservation request or a resource release request. If it is a resource securing request, the process proceeds to step S6. If it is a resource release request, step S12
Proceed to. Here, since it is a resource securing request, step S6
Proceed to. In step S6, after calculating the route related to the resource securing request, as shown in (3) of FIG. 11, the resource management unit 38 is inquired about the resource status of the bandwidth of the calculated route.

The resource management unit 38 determines in step S4 in FIG.
At 0, it is determined whether the message is from the admission control unit 34 or the setting management unit 48. If it is from the admission control unit 34, the process proceeds to step S42. If it is from the setting management unit 48, the process proceeds to step S54. Here, since it is from the admission control unit 34, the process proceeds to step S42. In step S42, the message is analyzed. In step S44, it is determined whether the request is an inquiry or an addition request. For inquiries,
Proceed to step S46. If it is an addition request, step S5
Go to 0. Here, since it is an inquiry, step S4
Proceed to 6.

In step S46, the resource management database 40 is searched for between routers located on the route. Here, the bandwidth usage status of the routers 22 # 4, # 3, # 2, and # 1 is searched. In step S48, as shown in (4) in FIG. 11, the admission control unit 34 is notified of the band securing status.

In step S8 in FIG. 8, the admission control unit 34 determines from the notification from the resource management unit 38 whether or not all the bands on the route can be reserved (there are resources). If the band can be secured, the process proceeds to step S10. If the bandwidth cannot be secured, step S
Proceed to 14. Here, since the band has been secured, the process proceeds to step S10. In step S10, it is determined that the admission is OK. In step S12, as shown in (5) of FIG. 11, the setting management unit 48 is requested to perform a bandwidth securing process on each relay source router located on the route.

The setting management unit 48 determines in step S in FIG.
At 70, the message is parsed. That is, it is determined which of the band setting and the band release. Step S7
In 1, it is determined whether or not n ≦ 0 (n is the number of devices to be set). If n ≦ 0, the process ends. n>
If 0, the process proceeds to step S72. In step S72, in accordance with the message, a connection is established with a router (setting device) instructing band setting / band release. In step S74, it is determined whether a connection has been established. If the connection has been established, the process proceeds to step S76. If the connection is not established, the process ends. Here, assuming that the connection has been established,
Proceed to step S76. In step S76, according to the message, a bandwidth setting request / bandwidth release setting is performed for the router on the route as shown in (6) in FIG.
The router makes a bandwidth setting request / bandwidth release setting, and
Respond as shown in (7) of 1. Here, a band is set.

In step S78, it is determined whether or not the device setting has been successfully executed. If the device setting execution has succeeded, the process proceeds to step S80. If the device setting has failed, the process ends. In step S80, as shown in (8) and (10) in FIG.
8 is notified of the band related to the device setting, and step S
Return to 72. In step S82, n is decremented, and the process returns to step S72. Steps S71 to S82 are performed for all routers located on the route. Here, the routers 22 # 1, 22 # 2, 22 # 3
A resource securing setting is made for 22 # 4.

At step S16 in FIG. 8, the admission control unit 34 notifies the user I / F unit 30 of the execution result as shown in (9) in FIG. The user I / F unit 30 reports the execution result (bandwidth reservation) to the communication terminal 2
Notify 0 # A1. The resource management unit 38 determines which of the setting management unit 48 and the admission control unit 34 it is in step S40 in FIG.
Here, since it is from the setting management unit 48, the process proceeds to step S54. In step S54, it is determined whether the operation is resource securing or resource releasing. If the resource is secured, the process proceeds to step S58. If the resource is released, the process proceeds to step S62. Here, since resources are secured, the process proceeds to step S58.

In step S58, the resource management database 40 sets the reserved band to the used band for the router for which the resource has been reserved. In step S60, as shown in (11) of FIG.
Notify that the band has been secured. Event detector 32
As shown in (12) of FIG. 11, upon receiving the resource securing notification, notifies the admission control unit 34.
In step S2 in FIG. 8, the admission control unit 34 determines which of the request and the resource use status notification is from the user. Here, since the resource use status is notified, the process proceeds to step S20. In step S20, since resources are secured, the process ends. As described above, the band is secured.

(2) Band Reservation Service FIG. 12 is a diagram showing a service reservation processing sequence.
Here, the communication terminal 20 # A5 sends a request source address to the communication terminal 20 # A5 address (IP address), a communication destination address to the server 26 address (IP address), a requested bandwidth, and a set time to the management server 24. Is transmitted. (1) to (3) in FIG.
The processes up to are the same as the processes (1) to (3) in FIG.

The resource management unit 38 determines in step S4 in FIG.
In step 6, the resource management database 40 is searched for a router located on the route to check the band securing status. Here, it is assumed that there is no available bandwidth for the requested bandwidth, and that resources cannot be secured. In step S48, as shown in (4) in FIG. 12, the search result is notified to the admission control unit 34 (bandwidth shortage).

At step S8 in FIG. 8, the admission control unit 34 determines from the notification from the resource management unit 38 whether or not all the bands on the route can be reserved (there are resources). Here, since the band could not be secured, the process proceeds to step S14. In step S14, the waiting list 44 is sent to the list
Ask to register. The list management unit 42 adds the bandwidth request at the end of the chain for each priority of the user request. In step S16, a bandwidth refusal message is transmitted to the user through the user I / F unit 30, as shown in (6) of FIG.

(3) Resource securing stop processing FIG. 13 is a diagram showing a resource securing stop processing sequence.
The user who received the service is the communication terminal 20 # A1
It is assumed that a bandwidth release request has been made to the management server 24 from # 20 to # A4. The user I / F unit 30 is configured as shown in FIG.
As shown in (1), an event that the line IF section has received the band release request message is notified to the event detection section 72. The event detection unit 72 notifies the admission control unit 34 that a band release request has been made, as shown in (2) in FIG. In step S2 in FIG. 8, the admission control unit 34 determines which of the request and the resource use status notification from the user based on the message content.

If it is a request from the user, step S4
Proceed to. If it is a resource use status notification, the process proceeds to step S20. Here, since it is a request from the user, step S
Proceed to 4. In step S4, the request is analyzed. In step S5, it is determined whether the request is a band securing request or a band releasing request. Here, since it is a band release request, the process proceeds to step S12. In step S12, as shown in (5) in FIG. 11, a bandwidth release request for each relay source router located on the path related to the bandwidth release request is output to the setting management unit 48.

The setting management unit 48 executes step S in FIG.
In steps 70 to S78, a setting release request is made as shown in (4) in FIG. Upon receiving the setting release request, the router releases the setting and notifies the setting management unit 48 of the setting result as shown in (5) of FIG. The setting management unit 48 receives the setting result notification from the router, and in step S80 in FIG. 10, as shown in (6) and (8) in FIG. Notify the band related to device setting release,
It returns to step S72. Step S72 to step S8
0 is performed for all routers located on the path related to setting release. Here, the routers 22 # 1, 22 # 2, 2
Resource release setting is performed for 2 # 3 and 22 # 4.

The admission control unit 34 notifies the user I / F unit 30 of the execution result at step S16 in FIG. 8, as shown in (7) in FIG. The user I / F unit 30 reports the execution result (bandwidth release) to the communication terminal 2
Notify 0 # A1. The resource management unit 38 determines which of the setting management unit 48 and the admission control unit 34 it is in step S40 in FIG.
If the resource is secured, the process proceeds to step S58. If the resource is released, the process proceeds to step S62. Here, since the resources are released, the process proceeds to step S62.

In step S62, the used bandwidth is updated for the router whose resources have been released from the resource management database 40. In step S64,
As shown in (9), the event detection unit 32 is notified that the band has been released. The event detection unit 32 detects (1
As shown in (0), when the resource release notification is received, it notifies the admission control unit 34.

(4) Waiting service start processing FIG. 14 is a diagram showing a waiting service start processing sequence. As described above, upon receiving the service, the user makes a bandwidth release request to the management server 24. This allows
As shown in FIG. 13, the management server 24 releases the reserved bandwidth. As will be described later, when a bandwidth securing time is designated at the time of the bandwidth securing request, the bandwidth is released after the elapse of the time.

When the event detection unit 32 receives the resource release notification from the resource management unit 38 as shown in (1) of FIG. 14, the admission control unit 32 as shown in (2) of FIG. Notify 34. In step S2 in FIG. 8, the admission control unit 34 determines which of the request and the resource use status notification is from the user. In this case, since the resource use status is notified, step S20 is performed.
Proceed to. In step S20, it is determined whether the release is resource release or resource reservation. Here, since resources are released, the process proceeds to step S22. In step S22,
As shown at (3) in FIG. 14, the list management unit 42 is inquired of a waiting state as to whether or not there is a band setting request waiting in the waiting list 44. If there is a band setting request wait, the process proceeds to step S24. If there is no next band setting request, the process is terminated. In step S24, the list management unit 4
2, a list search is executed. The list management unit 42
By referring to the priority table, the one having the highest priority and the first request for securing the bandwidth is searched. In FIG.
As shown in (4), the found bandwidth setting request is notified to the admission control unit 34.

At step S26 in FIG. 11, the admission control unit 34 makes an inquiry about the resource securing status related to the bandwidth setting request notified from the list management unit 42 as shown in (5) in FIG. . The resource management unit 38 searches for the status of securing the resource related to the inquiry through the processing of steps S40 to S46 in FIG. Then, as shown in (6) in FIG. 14, the result is notified to the admission control unit 34 in step S48.

At step S 28 in FIG. 8, the admission control unit 34 notifies the resource management unit 38 of the resource reservation status. The result is determined by the admission control unit 34, and if resources can be secured, the process proceeds to step S30. If resources are not available,
finish. Here, it is assumed that resources can be secured. In step S30, it is determined that the admission is OK. In step S32, as shown in (7) of FIG. 11, for each relay source router located on the route,
A message requesting the band setting is output to the setting management unit 48. The setting management unit 48 sets the bandwidth for the router located on the route as shown in (8) of FIG. The router notifies the setting management unit 48 of the setting result, as indicated by (9) in FIG.

The setting management section 48 notifies the admission control section 34 of the result of the setting, as indicated by (10) in FIG. The admission control unit 34, in step S34, as shown in (11) of FIG.
The user I / F unit 30 is notified that the band has been secured. Upon receiving the result notification, the user I / F unit 30 notifies the user whose band has been secured. As a result, even if the user cannot secure the bandwidth at the time of the bandwidth securing request, the bandwidth is automatically secured when a free area is available. In addition, since the bandwidth is secured in the order of the priority and the request time during the bandwidth securing waiting, fairness can be maintained. Here, although the bandwidth is automatically secured when the bandwidth can be secured, the bandwidth may be secured after confirming with the user whether or not the bandwidth is secured when the bandwidth can be secured.

In step S36, the admission control unit 34, as shown in (12) of FIG.
The list management unit 42 is instructed to delete the bandwidth setting request record for which the bandwidth has been set from the waiting list 44. The list management unit 42 deletes the bandwidth setting request record from the waiting list 44. The setting management unit 48 notifies the resource management unit 38 of the setting result related to resource reservation, as shown in (13) in FIG. The resource management unit 38 updates the resource management database 40 related to the route for which the bandwidth has been secured. Resource Management Department 3
Reference numeral 8 denotes an event detector 3 as shown in (14) of FIG.
2. Notify the resource reservation. The event detection unit 32 is configured as shown in FIG.
As shown in (15) of FIG. 4, the resource admission control unit 34 is notified of resource reservation.

(5) The band release is also performed when the set time specified by the user in the band setting request has elapsed. In this case, the setting time is managed by the setting management unit 48 managing the setting time or instructing the setting time to the router at the time of a device setting request, and managing the setting time on the router side. After the elapse of the set time, the resources are released, and the same processing as the processing of (5) to (10) in FIG. 13 is performed.

As described above, according to the first embodiment, a user who is rejected for a bandwidth reservation request is automatically allocated a resource when a resource becomes available, or when a resource becomes available. Can be received, it is possible to prevent frequent requests by rejection. As a result, the load on the server that performs resource allocation can be reduced, and the increase in traffic due to request messages can be suppressed. Further, since resources are secured in the order of priority and bandwidth request time, fairness can be maintained.

Second Embodiment FIG. 15 is a block diagram of a PBN network according to a second embodiment of the present invention. Components that are substantially the same as the components in FIG. 2 are given the same reference numerals. . As shown in FIG. 15, the PBN network has a domain 62 # i (i =
1, 2) and the management server 60 # i (i =
1, 2). The domain 62 # 1 is a user domain including a plurality of routers such as the communication terminals 20 # A to 20 # G and the router 64 # 1. Domain 62 # 2
Is a domain including the router 64 # 2 and the server 26, for example, an ISP (Internet Service Provider) domain. The domains 62 # 1 and 62 # 2 are connected by routers 64 # 1 and 64 # 2.

For example, the user domain 62 # 1 has the IS
P has contracted a bandwidth of 20 Mbps, with 6 Mbps being allocated for securing bandwidth and the remaining 14 Mbps being allocated for best effort. The band for securing the band is a band guaranteed by the ISP to the user domain 62 # 1. The communication quality of the best effort band changes depending on the state of the network. The band for best effort was
This is because the cost can be reduced by using some bands for best effort.

The management server 60 # 1 has the following functions.

When a user requests a resource reservation,
It is determined whether or not the route relating to the resource securing request is closed to the domain 62 # 1.

I) When closed to the domain 62 # 1, the same processing as the management server 24 of the first embodiment is performed.

Ii) When passing through the adjacent domain 62 # 2: If there is a vacancy in the bandwidth for securing the bandwidth, the route in the domain 62 # 1 related to the resource securing request is the same router as in the first embodiment. Make a device setting request. Here, the bandwidth allocation of the edge router 64 # 2 of the domain 62 # 2 and the band allocation of the passing router (relay) in the domain 62 # 2 is set in advance by the management server 60 # 2 or at any time based on the contract. Shall be.

If there is no available band for securing the band, register it in the waiting list. When the sum of the bandwidths waiting for securing the bandwidth becomes equal to or more than a certain value, a resource addition request is made to the management server 60 # 2 of the adjacent domain 62 # 2. The resource addition request is, for example, a band securing request for the effort band. When the resource is secured by the management server 60 # 2, the device setting for the router on the route in the domain 62 # 1 for the resource securing request registered in the waiting list related to the resource addition request is performed.

When a resource release request is made by the user, it is determined whether or not the route related to the resource release request is closed to the domain 62 # 1.

I) If the domain is closed to the domain 62 # 1, the same processing as that of the management server 24 of the first embodiment is performed.

Ii) When passing through the adjacent domain 62 # 2: For the route in the domain 62 # 1 related to the resource release request, a device setting release request is made to the corresponding router as in the first embodiment. Regarding the band between the adjacent domains 62 # 2, the band release request is not made to the management server 60 # 2, but the band for securing the band or the additional reserved band is set as the free band for the resource release request band. Perform bandwidth management. However, when all the additional reserved bands are released, a request to release the additional band is made to the management server 60 # 2.

When the bandwidth can be secured for the bandwidth setting request registered in the waiting list by the resource release request, the bandwidth is secured. Bandwidth is secured in the same manner as in i) or ii).

The management server 60 # 2 has the domain 62 # 1
When a device setting request for bandwidth allocation based on a contract with the router 64 # 2 between the router 64 # 2 and the domain 62 # 2 and a resource addition request / resource addition release request from the management server 60 # 1 are received, the router 64 # 2 A device setting request / release request for the bandwidth for the added resources is made.

FIG. 16 shows the management server 60 # 1 in FIG.
3, wherein substantially the same components as those in FIG. 3 are denoted by the same reference numerals. The admission control unit 70 has the following functions.

When a resource securing request is received from the event detecting unit 32, the topology database 72 is searched and
It is determined whether or not the route related to the resource securing request passes through the adjacent domain 62 # 2.

I) When the route related to the resource securing request is closed within the own domain 62 # 1, the same processing as that of the admission control unit 34 of the first embodiment is performed.

Ii) When the route related to the resource securing request passes through the adjacent domain 62 # 2, the following processing is performed. An inquiry is made to the resource management unit 74 as to whether resources can be secured from the allocated bandwidth between the routers 64 # 1 and 64 # 2. If the resources can be secured, a device setting request relating to the path of the resource securing request in the own domain 62 # 1 is instructed to the setting management unit 48 as in the first embodiment, and the allocated bandwidth is allocated to the resource management unit 74. Instruct only to update during use.

If resources cannot be secured, a resource securing request is registered in the waiting list 80. When the sum of the required bandwidths of the resource securing requests waiting for the allocation of resources between the routers 64 # 1 and 64 # 2 registered in the waiting list 80 exceeds a certain value, a resource addition request is issued to the other domain I / F unit 78. To instruct. Upon receiving a notification from the other domain I / F unit 78 that the resource addition request has succeeded, the device management request relating to the route related to the resource securing request registered in the waiting list 80 is sent to the setting management unit as in the first embodiment. Instruct 48.

When the resource release request is received from the event detection unit 32, the topology database 72 is searched and
It is determined whether or not the route related to the resource securing request passes through the adjacent domain 62 # 2.

I) If the path related to the resource release request is closed in the own domain 62 # 1, the same processing as in the admission control unit 34 of the first embodiment is performed.

Ii) When the route related to the resource release request passes through the adjacent domain 62 # 2, the following processing is performed. With respect to the path related to the resource release request in the own domain 62 # 1, the same processing as i) is performed. Regarding the additional allocated bandwidth, when the usage rate during a certain period falls below a certain value or when the usage rate is not used at all, the management server 60 # 1 requests the management server 60 # 2 to release the additional bandwidth. . In response, the management servers 60 # 1 and # 2 change the settings of each edge router.

The waiting list 80 includes a resource securing request waiting for a resource request in the own domain 62 # 1 and the adjacent domain 62 #.
7 is a list for registering resource reservation requests waiting for a resource request between two resources. The resource management unit 74 is a resource management unit 3 according to the first embodiment.
In addition to the function of FIG. 8, the resource management database 7 uses the allocation band between the adjacent domains 62 # 2 and the usage status of the additional band.
6 and manage it.

The resource management database 76 is a database for managing resources in the own domain 62 # 1 and managing the use of the allocated band and the added band between the adjacent domains 62 # 2 as in the first embodiment. It is. The other domain I / F unit 78 controls an interface for communication with the management server 60 # 2 of the adjacent domain 62 # 2, and according to an instruction from the resource management unit 74, the adjacent domain 6 # 2.
A resource addition request is made to the 2 # 2 management server 60 # 2, and a resource addition response from the management server 60 # 2 is notified to the resource management unit 74.

FIG. 17 is a flow chart of the admission control section 70 in FIG. FIG. 18 shows FIG.
26 is a flowchart of the resource management unit 74 related to resource management with another domain 62 # 2 in the inside. FIG. 19 is a flowchart of the other domain I / F unit 78 in FIG. Less than,
The operation of FIG. 15 will be described with reference to these drawings.

(1) Reserving Resources in Own Domain 62 # 1 Reserving resources in own domain 62 # 1 is the same as (1) in the first embodiment, and a description thereof will be omitted.

(2) Securing Resources Between Other Domains 62 # 2 For example, the communication terminal 20 # A may create a 3D virtual mall provided on the server 26 of the ISP domain 62 # 2.
, And to watch videos as its content,
The management server 60 # 1 issues a request for securing a resource of 2 Mbps bandwidth.
Suppose you went to Upon receiving the request content notification from the user I / F unit 30, the admission control unit 70 analyzes the request content in step S92 in FIG. In step S92, referring to the topology database 72, it is determined whether or not the route related to the resource securing request is within the own domain 62 # 1. here,
Since the path relating to the resource request passes through the own domain 62 # 2, the process proceeds to step S94. In step S94, an inquiry is made to the resource management unit 76 as to whether the resources of the route related to the resource securing request can be secured.

[0098] The resource management unit 74 determines in step S4 in FIG.
The resource management database 76 is searched in the same manner as in the processing of steps S0 to S46. For the own domain 62 # 1 and the other domain 62 # 2, the resource use status is notified to the admission control unit 70 in the same manner as in step S48 in FIG. Here, it is assumed that the bandwidth can be secured in the own domain 62 # 1 and the other domain 62 # 2.

Upon receiving the notification from the resource management unit 76, the admission control unit 70
At 96, it is determined whether there is a resource in the own domain 62 # 1. If there is no resource in the own domain 62 # 1, it is registered in the waiting list 80 and notified to the user I / F unit 30 as in step S14 in FIG. If there is a resource in the own domain 62 # 2, the process proceeds to step S98.
Here, since there are resources in the own domain 62 # 1, the process proceeds to step S98. In step S98, it is determined whether there is a resource with another domain 62 # 2. If there are resources, the process proceeds to step S108. Here, since there is a resource in the own domain 62 # 1, the process proceeds to step S108.

In step S108, it is determined that the admission is OK. In step S110, the resource management unit 76 is notified of the reservation of the band for securing the band with the other domain 62 # 2, and the setting management unit 48 is notified of the router 64 # 1 related to the route in the own domain 62 # 1 related to the band setting request. Instruct a device setting request. The resource management unit 76
In the middle step S134, upon receiving a notification of securing a bandwidth for securing resources from the admission control unit 70,
Update the resource management database 76. Setting management unit 48
Performs the same processing as steps S70 to S80 in FIG. 10 to set the device. With the above processing, a bandwidth of 2 Mbps is secured for the communication terminal 20 # A within the own domain 62 # 1 and between the other domains 62 # 2, and the user A receives a service such as a moving image from the server 26. Can be.

Similarly, communication terminals 20 # B to 20 # C
Also receives a resource securing request from users B and C,
It is assumed that a bandwidth of 2 Mbps has been secured in the own domain 62 # 1 and between the other domains 62 # 2. As a result, the three users A to C can immediately receive a high-quality service, but 6 Mbps between the other domains 62 # 2.
Are all communication terminals 20 # A to 20 # C
Will be assigned to

(3) Resource addition between other domains 62 # 2 FIG. 20 is a sequence chart of resource addition. As shown in (1) in FIG. 20, the user I / F unit 30 notifies the event detection unit 32 when receiving a 2 Mbps band resource reservation request from the communication terminal 20 # D. As shown in (2) in FIG. 20, the event detection unit 32 sends the resource request contents (bandwidth reservation) to the admission control unit 70.
Notify. The admission control unit 70 determines whether or not the resource securing request is in the own domain 62 # 1 through the processing of steps S90 to S92 in FIG. Here, since it is a resource securing request related to the other domain 62 # 2, the process proceeds to step S94. In step S94, a resource inquiry is made to the resource management unit 74 as shown in (3) of FIG.

The resource management section 74 searches the resource management database 76 and finds the domain 62 relating to the resource securing request.
A response is made as shown in (4) in FIG. 20 about the usage status of the bandwidth for securing the bandwidth between # 1 and the other domain 62 # i.
Here, a response is sent to the effect that there is no vacancy in the bandwidth securing band with the other domain 62 # 2, and the bandwidth cannot be secured due to lack of bandwidth. The admission control unit 70 receives the response of the resource management unit 74 in step S98,
Determine whether admission is possible. Here, since there is no link resource, the process proceeds to step S100. Step S1
At 00, it is determined that admission is not possible.
In step S102, it is determined whether or not there is a free space in the waiting list 80, that is, whether or not the sum of the bandwidths of the resource securing requests waiting for the link resource with the other domain 62 # 2 has exceeded a certain value or more. If there is a vacancy, it is determined that it has not exceeded, and the process proceeds to step S104. Here, since there is a free space, the process proceeds to step S104. In step S104, as shown in (5) in FIG. In step S104, the user I / F unit 30 is notified. A similar process is performed for the communication terminal 2 # ij20 #
This is repeated from E to #F.

Similarly, the user of communication terminal 20 # G issues a band securing request to management server 60 # 1 user I / F unit 3.
0 is the communication terminal 20 # E as shown in (1) in FIG.
Receives a request for securing resources of 2 Mbps bandwidth from
Notify the event detection unit 32. As described above, FIG.
The processing shown in (2) to (4) in 0 is performed. Upon receiving the notification of the band shortage from the resource management unit 74, the admission control unit 70 determines whether or not there is a free space in the waiting list 80 in step S102 in FIG. Here, since the band of the waiting list 80 has exceeded a certain range, the process proceeds to step S112. In step S112, the resource management unit 74 is requested to add a link resource to the other domain 62 # 2.

The resource management unit 74 determines in step S in FIG.
At 130, it is determined that the request is from the admission control unit 70, and the process proceeds to step S132.
In step S132, a resource addition request is made to the other domain I / F unit 78 as shown in (6) of FIG. The other domain I / F unit 78 receives the request from the resource management unit 74 in step S140. Step S142
Communicates with the other domain management server 60 # 2.

In step S 144,
As shown in (7), a resource addition request is made. Upon receiving the resource addition request, the other domain management server 60 # 2 receives an additional bandwidth between the routers 64 # 2 and 64 # 1, for example, 10 Mbp.
It is determined whether or not the band of s can be secured. If the additional bandwidth can be ensured, a device setting request for the additional bandwidth is made to the router 64 # 2, and the other domain I / F unit operates as shown in FIG.
As shown in (8), the other domain I / F unit 7 of the request source
8 is responded to the resource addition.

The other domain I / F unit 78 is provided in FIG.
As shown in (9), the admission control unit 70
To the resource addition response. The admission control unit 70 determines whether or not the addition request has succeeded in step S114. If the addition is not successful, step S1
Proceed to 22. If the addition is successful, the process proceeds to step S116. In step S122, a band securing request that cannot be secured is not registered in the waiting list 80. Step S12
In 2, the user I / F unit 30 is notified that the resource cannot be secured. In step S116, as shown in (10) of FIG. 20, a setting request is made to the setting management unit 48 for the route related to the bandwidth securing request to which the resource has been added.

The setting management section 48 performs device setting and notifies the admission control section 70 of the setting result as shown in (11) of FIG. Step S11
In step 8, as shown at (13) in FIG. 20, the bandwidth reservation request related to the addition request is deleted from the waiting list 80. In step S120, as shown in (12) in FIG. 20, the user I / F unit 30 is notified that the resources have been secured.

The setting management section 48 notifies the resource management section 74 of a resource securing notification relating to the device setting, as shown at (14) in FIG. The resource management unit 74 updates the resource management database 76 and sends a resource reservation notification to the admission control unit 70 through the event detection unit 32 as shown in (15) and (16) in FIG. As a result, the additional bandwidth is allocated to the users D, E, F, and G, so that high-quality services can be received. The release of the additional band is performed when all users using the additional band release the band.

As described above, the three users A to C, who have previously reserved the bandwidth, can immediately receive high-quality services. The other users D to G reserve resources (request for securing a bandwidth) in advance, and the user can secure the bandwidth as soon as the bandwidth is available or when resources are added. This further increases the opportunities for securing resources for the user. Therefore, while the bandwidth is low, the virtual mall can be used with the content of only the still image or the text, and the content can be switched to the 3D or the moving image as soon as the bandwidth is secured. It is also expected that the profits of the providers will improve accordingly. In addition, by adding resources in a certain unit, the traffic can be reduced by reducing the setting frequency, the load on the server can be reduced, and when purchasing resources from other providers, the unit price can be reduced by purchasing additional bandwidth collectively. There is also a merit of cost reduction.

[0111]

As described above, according to the present invention, a user who is rejected for a bandwidth reservation request is automatically allocated a resource when a resource becomes available, or has a resource available. , It is possible to prevent frequent requests due to rejection. As a result, the load on the server that performs resource allocation can be reduced, and the increase in traffic due to request messages can be suppressed. Further, since resources are secured in the order of priority and bandwidth request time, fairness can be maintained.

Further, since the user can secure the band at the time when the resource can be secured, the opportunity for securing the resource for the user is further increased. Accordingly, it is expected that the profits of the provider will increase. Further, by adding resources in a certain unit, control traffic can be reduced by reducing the setting frequency and the load on the management server can be reduced.

[Brief description of the drawings]

FIG. 1 is a principle diagram of the present invention.

FIG. 2 is a configuration diagram of a PBN network according to a first embodiment of the present invention.

FIG. 3 is a configuration diagram of a management server in FIG. 2;

FIG. 4 is a configuration diagram of a resource management database in FIG. 3;

FIG. 5 is a configuration diagram of a waiting list in FIG. 3;

FIG. 6 is a configuration diagram of a user profile in FIG. 3;

FIG. 7 is an operation explanatory diagram of FIG. 2;

FIG. 8 is a flowchart of an admission control unit in FIG. 3;

FIG. 9 is a flowchart of a resource management unit in FIG. 3;

FIG. 10 is a flowchart of a setting management unit in FIG. 3;

FIG. 11 is a diagram showing a resource securing request processing sequence.

FIG. 12 is a diagram showing a service suspension processing sequence.

FIG. 13 is a diagram showing a resource securing stop processing sequence.

FIG. 14 is a diagram showing a waiting service start sequence.

FIG. 15 is a configuration diagram of a PBN network according to a second embodiment of the present invention.

16 is a configuration diagram of a domain management server in FIG.

FIG. 17 is a flowchart of an admission control unit in FIG. 16;

FIG. 18 is a flowchart of a resource management unit in FIG.

19 is a flowchart of the other domain I / F unit in FIG.

FIG. 20 is a sequence chart for adding resources.

FIG. 21 is a network configuration diagram showing resource securing by the conventional Resv method.

[Explanation of symbols]

 Reference Signs List 10 receiving unit 11 resource management database 12 first judgment unit 13 list registration unit 14 second judgment unit 15 resource management unit 16 waiting list 17 setting management unit

Claims (5)

[Claims] 1. A management server that manages bandwidth allocation, a receiving unit that receives a bandwidth securing request, a resource management database that stores resource information relating to a bandwidth that can be allocated between the relay devices, A first determining unit that makes an inquiry about the resource usage status and determines whether or not a bandwidth related to the inquiry about the resource usage status can be secured based on a response to the inquiry; and the first determination unit relates to the bandwidth securing request. If it is determined that the bandwidth cannot be secured, a list registration unit that registers the bandwidth securing request in a waiting list; and, based on the release of the bandwidth, an inquiry about the resource use status of the bandwidth securing request registered in the waiting list. And determining whether or not a bandwidth related to the inquiry about the resource usage status can be secured based on the response to the inquiry. A disconnection unit; a resource management unit that searches the resource management database based on the inquiry about the resource usage status, and responds to a query about a resource usage status of a relay device on a route related to the inquiry; A management server, comprising: a setting management unit that requests a relay device on a route related to the request to secure a bandwidth specified by the bandwidth securing request. 2. When the setting management unit determines that a bandwidth related to the bandwidth securing request registered in the waiting list can be secured, the setting managing unit transmits the bandwidth to a relay device on a route related to the bandwidth securing request. 2. The resource management unit updates a resource management database based on a result of the reservation setting request by the setting management unit, wherein the resource management unit makes a reservation setting request of a band indicated by the reservation request. The management server described. 3. When it is determined that the bandwidth related to the bandwidth securing request registered in the waiting list can be secured,
2. The management server according to claim 1, further comprising a notifying unit that notifies the bandwidth securing request source that the bandwidth can be secured. 4. The method according to claim 1, wherein the second determining unit determines, in response to a bandwidth securing request registered in the waiting list, whether or not a bandwidth related to the bandwidth securing request can be secured according to an arbitrary rule. The management server according to claim 1. 5. A management server that manages bandwidth allocation, a receiving unit that receives a bandwidth securing request, a resource management database that stores resource information relating to a bandwidth that can be allocated between the relay devices, A first determining unit that makes an inquiry about the resource use status and determines whether or not a bandwidth related to the inquiry about the resource use status can be secured based on a response to the inquiry; and A resource management unit that searches a management database and responds to the resource use status of the relay device on the route related to the inquiry; and a case where the first determination unit determines that the bandwidth related to the bandwidth reservation request cannot be secured. A list registration unit for registering the bandwidth reservation request in a waiting list; A second determining unit that determines whether to make an additional resource request based on an arbitrary rule; and a resource addition requesting unit that makes an additional resource request based on the determination result of the second determining unit. A management server, comprising: