JP2012029259A - Communication system, communication method, and communication device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allocate bands of respective terminals by considering a remaining amount of an allocation possible band at every service under a plurality of policy server environments.SOLUTION: A present value of the band remaining amount which can be allocated to respective services is shared between the policy servers PCRF3. The policy server PCRF3 allocates a band for every service of each terminal MS5. Thus, congestion by excessive allocation of the band is dissolved and delay and packet disposal are reduced. A function for calculating user priority and priority of a request from a request generation time at every service for every band allocation request of the terminal MS5 is provided. Even if band allocation requests are simultaneously given from the plurality of terminals MS5, priority control can be performed on the request suitable for the service.

Description

  The present invention relates to a communication system and method, and a communication apparatus for allocating a band for each terminal and for each service.

  In recent years, research and standardization activities for the 3.9th generation mobile communication system have been promoted as a method for realizing higher speed and higher quality of mobile radio communication. In LTE (Long Term Evolution), which is one of the 3.9th generation mobile communication systems, non-patent document 1 describes a user and a service providing server as a parameter for setting a bandwidth for a best effort service that does not guarantee bandwidth. APN-AMBR (Access Point Name-Aggregate Maximum Bit Rate) is defined as a unit. Band control based on APN-AMBR is performed by a gateway in the downlink direction and by a terminal and a gateway in the uplink direction. In addition, as a parameter for setting a bandwidth for a service for which bandwidth guarantee is performed, Non-Patent Document 1 defines an MBR (Maximum Bit Rate) for each user and service. Band control based on MBR is performed by a gateway in the downlink direction and by a base station in the uplink direction. APN-AMBR and MBR use values determined by a policy or charging control function (PCRF), which is a gateway or policy server, based on a preset policy. There is no detailed standard for the determination method of APN-AMBR and MBR, and it is determined by a method suitable for the circumstances of each operator and each vendor.

  Policy servers and gateways generally use a RAM as a memory because of a request for response speed for writing and reading. However, in the case of an operator having several million users with a currently available RAM capacity, A distributed configuration using RAM is essential. There is no detailed standard for communication between policy servers and gateways in such a distributed configuration, and communication is performed in a manner suited to the circumstances of each operator and each vendor.

JP 2009-188961 A

3GPP TS23.401 V9.4.0, (2010-3), Technical Specification

  Bandwidth values of mobile communication systems such as APN-AMBR and MBR can be assigned and determined by the circumstances of each service or each node (gateway, service providing server, etc.) (line thickness, processing throughput limit), etc. When the allocated bandwidth exceeds the remaining bandwidth, packets counted as billing packets at the gateway are discarded at the service provider or base station, causing erroneous billing, or packets exceeding the capacity of each line or node are sent and received In some cases, the service quality may be degraded due to congestion. Therefore, the gateway or policy server must determine the APN-AMBR and MBR based on the remaining bandwidth that can be allocated for each service or each node in order to prevent service quality degradation due to erroneous charging or congestion. I must. However, in the standard provisions shown in Non-Patent Document 1, etc., the method of knowing the bandwidth value assigned by another policy server or another gateway is not considered, so in an environment where there are a plurality of policy servers or gateways, APN-AMBR and MBR cannot be determined based on the current value of the remaining bandwidth that can be dynamically changed.

  On the other hand, in the policy server, the upper policy server manages both the allocated bandwidth on the called side and the allocated bandwidth on the calling side, and notifies the lower policy server about the mutual bandwidth allocation. A method for allocating a band is disclosed in Patent Document 1 and the like. However, the method in which the upper policy server collectively manages the policy information of all the lower policy servers is difficult to satisfy the upper policy server performance that can withstand the load because the information is collected in one place. Challenges include the fact that the range of influence due to server failure extends to all services, and that it is difficult to continue services when adding or deleting services. Therefore, a configuration that avoids these problems is necessary.

  In addition, the conventional technology does not consider the case where the allocation of APN-AMBR and MBR occurs almost simultaneously in a plurality of policy servers or a plurality of gateways. Therefore, it is assumed that it is not possible to avoid the occurrence of inconvenience when a plurality of policy servers or a plurality of gateways allocate APN-AMBR and MBR at the same time exceeding the remaining bandwidth that can be allocated. There is a problem that is done.

  In view of the above points, the present invention decides according to the circumstances of each service or each node when a policy server or a gateway allocates a bandwidth to each terminal that requests allocation of a bandwidth to be used in a certain service in a wireless communication system. An object is to allocate a band to each terminal that requests allocation of a band to be used in the service based on the current value of the remaining band that can be allocated. In addition, the present invention exceeded the current value of the remaining bandwidth that can be allocated to a bandwidth allocation request that is used by a service for each terminal that occurred almost simultaneously on multiple policy servers or multiple gateways. One purpose is to avoid allocating bandwidth.

  The wireless communication system according to the present invention includes a user and a service for each terminal in communication between a base station (BS) and a terminal (MS), between a base station and a gateway (GW), and in communication between the gateway and a service providing server (SS). It has a bandwidth allocation function for setting a bandwidth for each provided server or user and service based on the current value of the remaining bandwidth that can be allocated to be shared among a plurality of policy servers (PCRFs) or between a plurality of gateways. Is one of the features. Further, the wireless communication system of the present invention includes a user unit and a service providing server unit or a user of each terminal in communication between a base station and a terminal, between a base station and a gateway, and between a gateway and a service providing server. A bandwidth is set for each service, and has a bandwidth allocation function for setting a bandwidth to be allocated to a terminal that requests allocation of a bandwidth to be used in the service based on the current value of the remaining bandwidth that can be allocated. One of the features. That is, the wireless communication system determines whether or not each terminal can accept a bandwidth allocation request by sharing the remaining amount of bandwidth that can be allocated for each service among a plurality of communication devices.

  In this wireless communication system, the policy server or the gateway is based on the priority of each request determined based on the set policy for a plurality of bandwidth allocation requests generated almost simultaneously in the bandwidth allocation described above. One of the characteristics is that it has a bandwidth allocation function for allocating a bandwidth in consideration of which request has priority among a plurality of bandwidth allocation requests.

  As information for determining the priority of each request described above, the priority (user priority) set for each terminal may be used. Further, the time at which each request occurs may be used as information for determining the priority of each request described above. In addition, as information for determining the priority of each request described above, a time at which each request is received by the gateway may be used. Furthermore, when calculating the priority of the request, the total priority of the request may be calculated based on both the priority for each user and the generation time of the request. In addition, as information for determining the priority of each request described above, a priority determined for each policy server or each gateway may be used. Further, as information for determining the priority of each request described above, a comprehensive priority of each request considering a plurality of the above-mentioned information simultaneously may be used. The priority of each comprehensive request described above may be calculated by the policy server or the gateway.

According to the first solution of the present invention,
A communication system,
A first communication device;
A second communication device connected to the first communication device;
With
The first communication device includes a first remaining bandwidth table that stores an allocatable bandwidth remaining amount corresponding to the service identifier, and one of the allocatable bandwidth remaining transmission destinations corresponding to the service identifier, or A first transmission destination table in which a plurality of communication devices are stored,
The MS includes the MS identifier of the first terminal requesting bandwidth allocation from the first terminal, the service identifier of the service for which the first terminal requests bandwidth, and the requested bandwidth for which the first terminal requests allocation. Receiving a first request message requesting bandwidth allocation for a service;
The first communication device refers to the first remaining bandwidth table, and based on the received first request message, an allocation request bandwidth for a service of the first terminal is assigned to the service. Determine if the available bandwidth is not exceeded,
If not, the first communication device sets a destination address of one or more other communication devices corresponding to the service based on the first destination table, and the first communication device Transmitting a second request message including an MS identifier, a service identifier, and a request bandwidth included in the request message to one or more other communication devices;
When the first communication device receives a permission message from all the other communication devices that have transmitted the second request message within a predetermined time, the first communication device Referring to the remaining amount table, subtracting the requested bandwidth from the remaining bandwidth that can be allocated for the service identifier of the requested service to calculate the changed allocated bandwidth remaining amount, and based on the remaining bandwidth, the first bandwidth remaining amount Update the table,
The first communication device transmits to the first terminal a permission message that permits assignment including an MS identifier, a service identifier, and a requested bandwidth, and all of the second request messages that have been transmitted. To the other communication device, a service identifier for changing the remaining bandwidth, and a bandwidth remaining amount change message including the changed allocated bandwidth remaining amount,
The second communication device includes a second remaining bandwidth table that stores the remaining bandwidth that can be allocated corresponding to the service identifier, and one of the remaining bandwidth remaining destinations that correspond to the service identifier, A second transmission destination table storing a plurality of communication devices,
When the second request message is received from the first communication device, for the service with the service identifier included in the received second request message, the first of the MS identifiers in the second request message. Determining whether there is a bandwidth allocation request from the second terminal other than
When there is a bandwidth allocation request of the second terminal for the service, the second communication device refers to the second remaining bandwidth table and corresponds to the service of the service identifier included in the second request message. Determining whether the sum of the allocation request bandwidth and the allocation request bandwidth requested from the second terminal for the service is less than or equal to the remaining bandwidth available for the service;
When the total exceeds the remaining bandwidth, the second communication device allocates a bandwidth based on the second request message from the first communication device based on the priority and / or request generation time of each terminal. And whether the bandwidth allocation request from the second terminal can be permitted,
When it is determined that the bandwidth allocation request received from the first communication device is rejected, the second communication device rejects the bandwidth allocation for the first terminal to the rejected first communication device. A message is returned, and the second communication device sets a destination address of one or more other communication devices corresponding to the service based on the second destination table, and permits The third identifier for requesting bandwidth allocation including the MS identifier for requesting the bandwidth of the other second terminal, the service identifier for requesting the bandwidth of the second terminal, and the allocation request bandwidth of the second terminal. Sending a request message to one or more other communication devices;
The communication system is provided.

According to the second solution of the present invention,
A communication method for sharing and managing a remaining bandwidth that can be allocated for each service between a plurality of communication devices including a first communication device and a second communication device,
Each of the first communication device and the second communication device is:
A remaining bandwidth table that stores the remaining bandwidth that can be allocated in response to the service identifier,
In correspondence with the service identifier, a transmission destination table in which one or a plurality of communication devices of the remaining bandwidth allocation destination is stored is stored,
The first communication device includes, from the first terminal, an MS identifier of the first terminal that requests bandwidth allocation, a service identifier of a service for which the first terminal requests bandwidth, and the first terminal Receiving a first request message requesting bandwidth allocation for a service including a requested bandwidth requesting allocation;
The first communication device refers to the remaining bandwidth table and, based on the received first request message, assigns a requested bandwidth for a service of the first terminal to an available bandwidth remaining in the service. Judge whether the amount exceeds,
If not exceeded, the first communication device sets a destination address of one or more other communication devices corresponding to the service based on the destination table, and in the first request message Transmitting a second request message including the included MS identifier, service identifier, and requested bandwidth to one or more other communication devices;
When the first communication device receives permission messages from all the other communication devices that have transmitted the second request message within a predetermined time, the first communication device , Subtract the requested bandwidth from the allocatable bandwidth remaining for the service identifier of the requested service to calculate the changed allocated bandwidth remaining, update the bandwidth remaining table with the bandwidth remaining,
The first communication device transmits to the first terminal a permission message that permits assignment including an MS identifier, a service identifier, and a requested bandwidth, and all of the second request messages that have been transmitted. To the other communication device, a service identifier for changing the remaining bandwidth, and a bandwidth remaining amount change message including the changed allocated bandwidth remaining amount,
When the second communication device receives the second request message from the first communication device, the second request message is sent to the service with the service identifier included in the received second request message. Determining whether there is a bandwidth allocation request from the second terminal other than the first terminal of the MS identifier in
When there is a bandwidth allocation request of the second terminal for the service, the second communication device refers to the bandwidth remaining amount table and allocates the requested bandwidth for the service of the service identifier included in the second request message. And the sum of the allocation request bandwidth requested from the second terminal for the service is less than or equal to the remaining bandwidth that can be allocated for the service,
When the total exceeds the remaining bandwidth, the second communication device allocates a bandwidth based on the second request message from the first communication device based on the priority and / or request generation time of each terminal. And whether the bandwidth allocation request from the second terminal can be permitted,
When it is determined that the bandwidth allocation request received from the first communication device is rejected, the second communication device rejects the bandwidth allocation for the first terminal to the rejected first communication device. A message is returned, and the second communication device sets a destination address of one or more other communication devices corresponding to the service based on the destination table and is permitted. An MS identifier for requesting the bandwidth of the other second terminal, a service identifier for requesting the bandwidth by the second terminal, and a third request message for requesting bandwidth allocation including the allocation request bandwidth of the second terminal. A communication method characterized by transmitting to one or a plurality of other communication devices is provided.

According to the third solution of the present invention,
A communication device,
A remaining bandwidth table that stores the remaining bandwidth that can be allocated for each service corresponding to the service identifier,
Corresponding to the service identifier, a storage unit that stores a destination table in which one or a plurality of communication devices of the remaining bandwidth available for each service is stored;
The MS includes the MS identifier of the first terminal requesting bandwidth allocation from the first terminal, the service identifier of the service for which the first terminal requests bandwidth, and the requested bandwidth for which the first terminal requests allocation. A request message receiving unit for receiving a first request message for requesting bandwidth allocation for a certain service;
With reference to the remaining bandwidth table, based on the received first request message, it is determined whether an allocation request bandwidth for a service of the first terminal exceeds an allocatable bandwidth remaining amount of the service. A bandwidth remaining excess determination unit;
If not exceeded, the destination address of one or more other communication devices corresponding to the service is set based on the destination table, and the MS identifier and service identifier included in the first request message A first request message transmission unit that transmits a second request message including a request band to one or more other communication devices;
When a permission message is received from all the other communication devices that have transmitted the second request message within a predetermined time, an allocatable bandwidth for the service identifier of the requested service is referred to the remaining bandwidth table An update unit that subtracts the requested bandwidth from the remaining amount to calculate the allocated bandwidth remaining after the change, and updates the bandwidth remaining amount table with the bandwidth remaining;
To the first terminal, a permission message for permitting allocation including an MS identifier, a service identifier, and a request bandwidth is transmitted to all the other communication devices that have transmitted the second request message. A service identifier for changing the remaining bandwidth, a remaining bandwidth change message sending unit for sending a remaining bandwidth change message including the assigned remaining bandwidth, and
When the second request message including the MS identifier, the service identifier, and the request bandwidth included in the first request message is received from another communication device, the service with the service identifier included in the received second request message is received. On the other hand, a bandwidth allocation request presence / absence determining unit that determines presence / absence of a bandwidth allocation request from the second terminal other than the first terminal of the MS identifier in the second request message;
When there is a bandwidth allocation request of the second terminal for the service, the bandwidth remaining table is referred to, an allocation request bandwidth for the service of the service identifier included in the second request message, and the service for the service A remaining bandwidth determination unit that determines whether the sum of the allocation request bandwidth requested from the second terminal is less than or equal to the remaining bandwidth that can be allocated to the service;
If the total exceeds the remaining bandwidth, bandwidth allocation by the second request message from the certain communication device and bandwidth allocation from the second terminal based on the priority and / or request generation time of each terminal A request permission unit for determining which of the requests can be permitted; and
When it is determined that the bandwidth allocation request received from the certain communication device is rejected, a bandwidth allocation rejection message for the first terminal is returned to the certain communication device that has been rejected, and the transmission destination table Based on the MS identifier for setting the destination address of one or more communication devices corresponding to the service and requesting the bandwidth of the other authorized second terminal, and the second terminal assigning the bandwidth A second request message transmission unit for transmitting a third request message for requesting bandwidth allocation including a requested service identifier and an allocation request bandwidth of the second terminal to the one or more communication devices. Is provided.

  According to the present invention, in a wireless communication system, when a policy server or a gateway allocates a band to each terminal that requests allocation of a band to be used for a certain service, an allocatable band determined according to circumstances of each service or each node. Based on the current value of the remaining amount, a bandwidth can be allocated to each terminal that requests allocation of a bandwidth to be used in the service. In addition, according to the present invention, in response to a request for allocation of a bandwidth used for a service by each terminal, which is generated almost simultaneously on a plurality of policy servers or a plurality of gateways, the current value of the remaining bandwidth that can be allocated is exceeded. Can be avoided.

An example of a policy server device and a gateway device having a bandwidth allocation function for setting a bandwidth to be allocated to a terminal that requests allocation of a bandwidth to be used in the service based on a current value of a remaining bandwidth that can be allocated. An example of a mobile radio communication system having a bandwidth allocation function for setting a bandwidth to be allocated to a terminal that requests allocation of a bandwidth to be used in the service (when the policy server and the gateway are separate nodes). An example of a mobile radio communication system (in the case where a policy server and a gateway are integrated nodes) having a bandwidth allocation function for setting a bandwidth to be allocated to a terminal that requests allocation of a bandwidth to be used in the service. An example of a block diagram of a policy server. An example of a block diagram of a gateway. An example of a table (a service-allocable bandwidth remaining amount table) held by a policy server or gateway having a bandwidth allocation function. An example of a table held by a policy server or gateway having a bandwidth allocation function (allocable bandwidth remaining amount transmission destination PCRF table for each service). An example of a table (PCRF-specific destination address table) held by a policy server or gateway having a bandwidth allocation function. An example of a table (UP table for each MS) held by a policy server or gateway having a bandwidth allocation function. An example of a table (parameter table for bandwidth allocation request total priority calculation for each service) held by a policy server or gateway having a bandwidth allocation function. An example of a table held by a policy server or gateway having a bandwidth allocation function (allocable bandwidth remaining amount transmission destination GW table by service). An example of a table (GW-specific destination address table) held by a policy server or gateway having a bandwidth allocation function. An example of a processing flowchart when a bandwidth allocation request message is received from a terminal in the bandwidth allocation function of the policy server. An example of the block diagram of the memory part of a policy server. An example of the block diagram of the process part of a policy server. An example of the block diagram of the memory part of a gateway. An example of the block diagram of the process part of a gateway. An example (1/2) of a processing flowchart when a bandwidth allocation request message is received from another policy server in the bandwidth allocation function of the policy server. An example (2/2) of a processing flowchart when a bandwidth allocation request message is received from another policy server in the bandwidth allocation function of the policy server. An example of a processing flowchart when a bandwidth remaining amount update message is received from another policy server in the bandwidth allocation function of the policy server.

1. Overview

FIG. 2 is an example of a mobile wireless communication system having a bandwidth allocation function based on the current value of the remaining bandwidth that can be allocated (when the policy server and the gateway are separate nodes).
One of the embodiments of the present invention is that in a mobile radio communication system, between base stations (hereinafter referred to as BS) 4 to MS 5 and between BS 4 and gateway devices (hereinafter referred to as MS: Mobile Station) 5 in a mobile radio communication system. In the present specification, it may be simply referred to as a gateway.Hereinafter, a policy server (hereinafter, referred to as SS: Service Server) 1 and a policy server (hereinafter, referred to as SS: Service Server) 1 that is referred to as GW: Gateway 2 PCRF (Policy and Charging Control Function) 3 collects each service between SS1 and GW2 or between BS4 and GW2, or to each MS 5 using the band of the service based on the remaining bandwidth that can be allocated in each node. The bandwidth to be allocated Provide a configurable system. At this time, as shown in FIG. 1, the PCRFs 3 are connected to each other so that messages can be transmitted and received.

FIG. 3 shows an example of a mobile wireless communication system having a bandwidth allocation function based on the current value of the remaining bandwidth that can be allocated (when the policy server and the gateway are integrated nodes).
As shown in FIG. 3, as a modification of the embodiment of the present invention, PCRF 3 and GW 2 may be the same node. In this case, in the mobile radio communication system, the GW2 that allocates the band between BS4 to MS5 and between BS4 to GW2 and between GW2 to SS1 of each MS5 is collected between SS1 to GW2 or between BS4 to GW2. Provided is a system capable of setting a band to be allocated to each MS 5 that uses the band of the service based on the remaining amount of band that can be allocated by each service or each node. At this time, the GWs 2 are connected to each other so that messages can be transmitted and received.

As another modification of the embodiment of the present invention, the BS 4 may pass through a plurality of GWs 2 while connected to the SS 1.
Note that the system of each embodiment is not limited to mobile communication, and may be a wireless communication system having a wireless section. In addition, the system according to each embodiment is not limited to wireless communication, and may be a communication system including only wired sections.

  In each embodiment, the bandwidth allocated by GW2 can be set in any unit of MS5 unit and SS1 unit or MS5 and service unit. When setting a band for each MS5 and SS1 unit, the band is controlled independently for each SS1 to which the MS5 is connected, and the SS1s that are also connected to the same MS5 are handled as mutually independent communication paths. In addition, when the band is set for each service unit in MS5, the band control is independently performed for each service for which MS5 requests band allocation, and the same MS5 is handled as an independent communication path depending on the service.

  Further, in each embodiment, the priority of the bandwidth allocation request of each MS 5 may be set in consideration of the priority of each user based on the policy (hereinafter, UP: User Priority). There is a method in which policy information including UP of each MS 5 and weighting of request priority based on UP, request generation time, etc. is set in advance in GW 2 or in advance in PCRF 3.

2. Embodiment of the present invention

The embodiment of the present invention relates to bandwidth allocation based on the current value of the remaining bandwidth that can be allocated in each service, and the BS4 of the MS 5 in the PCRF 3 that has received the bandwidth allocation request for the service of each MS 5. An example of band allocation between MS5, between BS4 and GW2, and between GW2 and SS1 is shown.

Further, as a modification of the present embodiment, when the PCRF 3 and the GW 2 are integrated nodes, the GW 2 that has received the bandwidth allocation request for the service of each MS 5 has the BS 5 to the BS 4 to the MS 5, the BS 4 to the GW 2, and the GW 2. An example of band allocation between ~ SS1 is shown.
Further, in the present embodiment, when the PCRF 3 or GW 2 allocates a band to each MS 5 that requests bandwidth allocation for a certain service, the total priority P of each request is set to the time at which the bandwidth allocation request is generated in a plurality of MSs 5. And a response to each request can be determined based on P. Further, in the present embodiment, when calculating the overall priority P of each request, the bandwidth allocation request reception time of GW 2 or the bandwidth allocation request of PCRF 3 is used instead of the time of occurrence of the bandwidth allocation request in MS 5. The reception time may be used.

2-1. System Configuration [Example of Architecture of Mobile Radio Communication System of this Embodiment]
An example of the architecture of the mobile radio communication system of the present embodiment is as described in the overview.

2-2. Device configuration 2-2-1. PCRF3
[Example of PCRF 3 of the present embodiment]
FIG. 4 shows an example of a functional block diagram of the PCRF 3 used in the present embodiment. FIG. 14 shows an example of a block diagram of the memory unit of the policy server. FIG. 15 shows an example of a block diagram of the processing unit of the policy server.
The PCRF 3 includes, for example, a GW interface unit 31, a PCRF interface unit 32, a memory unit 33, and a processing unit 34. As a modification, when the GW 2 is a PCRF3-integrated node, the PCRF 3 may be omitted.

  The GW interface unit 31 is an interface with the GW 2. The PCRF 3 transmits and receives IP packets to and from the GW 2 by the GW interface unit 31. In the present embodiment, the PCRF 3 uses the GW interface unit 31 to receive, from the GW 2, the identifier of the MS 5 that has requested bandwidth allocation, the allocation request bandwidth, and the like, and transmits the allocated bandwidth to the MS 5 to the GW 2. Further, UP of each MS, allocation request generation time, etc. may be received from GW2.

  The PCRF interface unit 32 is an interface with another PCRF 3. The PCRF interface unit 32 causes the PCRF 3 to transmit and receive IP packets with other PCRFs 3. In the present embodiment, the PCRF 3 transmits / receives the identifier of the MS 5 that has requested bandwidth allocation to / from another PCRF 3, the allocation request bandwidth, and the like by the PCRF interface unit 32. Moreover, you may transmit / receive the allocation request generation time etc. between PCRF3.

  The memory unit 33 stores and manages information such as the IP packet to be transmitted / received, the address of the GW 2 to be connected, the address of the PCRF 3 to be connected, the remaining bandwidth that can be allocated to each service, as necessary. In the present embodiment, for example, as illustrated in FIG. 14, the memory unit 33 includes a service-specific allocatable bandwidth remaining amount table 331, a service-specific allocatable bandwidth remaining amount transmission destination PCRF table 332, and a PCRF-specific transmission destination address table 333. A per-MS UP table 334 and a per-service bandwidth allocation request total priority calculation parameter table 335, each service's allocatable bandwidth remaining, each service's allocatable bandwidth remaining destination PCRF, each PCRF 3 Information such as the destination address, the UP of each MS 5, and the bandwidth allocation request total priority calculation parameter of each service can be managed. Details of each table will be described later.

  For example, as shown in FIG. 15, the processing unit 34 includes a memory management unit 341 that manages information held in the memory unit 33, a transmission / reception management unit 342 that performs IP packet transmission / reception processing such as construction and analysis of IP packets, and the like. Then, management of information held in the memory unit 33, IP packet transmission / reception processing such as construction and analysis of IP packets, and the like are performed. Further, for example, as shown in FIG. 15, the processing unit 34 allocates a band between the BS 4 and the MS 5, between the BS 4 and the GW 2, and between the GW 2 and the SS 1 for each MS 5, calculates the bandwidth allocation request total priority of each service, A bandwidth allocation processing unit 343 that determines whether or not to accept a request based on the calculated bandwidth allocation request total priority, and the allocation of bandwidth between BS4 and MS5, between BS4 and GW2, and between GW2 and SS1 for each MS5, Calculation of the bandwidth allocation request total priority of each service, determination of acceptability of a request based on the calculated bandwidth allocation request total priority, and the like are performed. Further, when the time when the PCRF 3 receives the bandwidth allocation request is used to determine the priority of the bandwidth allocation request, the processing unit 34 counts the time when the bandwidth allocation request reception time of the MS 5 acquired by the PCRF 3 from the GW 2 as shown in FIG. The time measuring unit 344 and the like that perform the time measurement, the PCRF 3 measures the time of receiving the band allocation request of the MS 5 acquired from the GW 2.

[An example of information held in the memory unit of the PCRF 3 of the present embodiment]
FIG. 6 shows an allocatable bandwidth remaining amount table for each service as an example of information held in the memory unit of the PCRF 3 according to the present embodiment.
The allocable bandwidth remaining amount table for each service stores, for example, the allocable bandwidth remaining amount corresponding to the service identifier.
The service identifier is an identifier of a service provided by SS1 connected to GW2. The remaining bandwidth that can be allocated is the remaining bandwidth that can be currently allocated to each MS 5.

  The initial values of these pieces of information can be set and stored in advance in the PCRF 3 by an operator, for example. Also, the information is updated by, for example, a value acquired from SS1 via GW2, a value additionally set by the operator in PCRF3, or a value acquired via BS4 and GW2 at the initial registration of MS5. Can be made. Further, the allocatable bandwidth remaining amount table for each PCRF 3 can be synchronized with each other.

FIG. 7 shows an allocatable bandwidth remaining amount transmission destination PCRF table for each service as an example of information held in the memory unit of the PCRF 3 according to the present embodiment.
The allocable bandwidth remaining amount transmission destination PCRF table for each service stores, for example, the allocable bandwidth remaining amount transmission destination PCRF corresponding to the service identifier.
The service identifier is an identifier of a service provided by SS1 connected to GW2. The allocatable bandwidth remaining amount transmission destination PCRF is destination information such as an identifier or an IP address of the PCRF 3 that needs to notify the change in the allocatable bandwidth remaining amount of the service.

  The initial values of these pieces of information can be set and stored in advance in the PCRF 3 by an operator, for example. Also, the information is updated by, for example, a value acquired from SS1 via GW2, a value additionally set by the operator in PCRF3, or a value acquired via BS4 and GW2 at the initial registration of MS5. Can be made.

FIG. 8 shows a PCRF-specific transmission destination address table as an example of information held in the memory unit of the PCRF 3 of the present embodiment. Also, these pieces of information can be updated with values obtained from SS1 via GW2.
In the PCRF-specific transmission destination address table, for example, a PCRF identifier and a transmission destination address are stored correspondingly.
The PCRF identifier is an identifier of each PCRF 3. The destination PCRF address is destination information such as the IP address of the PCRF. This table is not necessary when destination information such as an IP address is set in the allocatable bandwidth remaining amount transmission destination PCRF table of the allocatable bandwidth remaining amount transmission destination PCRF table for each service.

  The initial values of these pieces of information can be set and stored in advance in the PCRF 3 by an operator, for example. Also, the information is updated by, for example, a value acquired from SS1 via GW2, a value additionally set by the operator in PCRF3, or a value acquired via BS4 and GW2 at the initial registration of MS5. Can be made.

FIG. 9 shows an MS-specific UP table as an example of information held in the memory unit of the PCRF 3 according to the present embodiment.
The UP table for each MS stores, for example, the UP for each MS corresponding to the MS identifier.
The MS identifier is an identifier of MS5. UP is a value indicating the level of priority assigned to each user. For example, the smaller the value, the higher the priority.

  The initial values of these pieces of information can be set and stored in advance in the PCRF 3 by an operator, for example. Also, the information is updated by, for example, a value acquired from SS1 via GW2, a value additionally set by the operator in PCRF3, or a value acquired via BS4 and GW2 at the initial registration of MS5. Can be made.

FIG. 10 shows a service-specific bandwidth allocation request total priority calculation parameter table as an example of information held in the memory unit of the PCRF 3 according to the present embodiment.
The parameter table for bandwidth allocation request overall priority calculation for each service stores, for example, a request generation time difference weight a and an UP difference weight b used for bandwidth allocation request overall priority calculation corresponding to the service identifier. Is done.

  The service identifier is an identifier of a service provided by SS1 connected to GW2. The request generation time difference weight a is a value indicating a degree of emphasis on the request generation time difference when calculating the overall priority P of the bandwidth allocation request for the service. For example, the larger the value, the earlier the request generation time is. Indicates that there is a strong tendency to be more important. Further, when the request reception time of GW2 is used instead of the request generation time, the value indicates a degree of emphasis on the difference in request reception time of GW2. Further, when the request reception time of the PCRF 3 is used instead of the request generation time, the value indicates a degree of emphasis on the difference in the request reception time of the PCRF 3. The UP difference weight b is a value indicating the degree of emphasis on the UP difference when calculating the overall priority P of the bandwidth allocation request for the service. For example, the larger the value, the more important the request of the MS 5 with higher UP is. Indicates a strong tendency.

  The initial values of these pieces of information can be set and stored in advance in the PCRF 3 by an operator, for example. Also, the information is updated by, for example, a value acquired from SS1 via GW2, a value additionally set by the operator in PCRF3, or a value acquired via BS4 and GW2 at the initial registration of MS5. Can be made.

2-2-2. GW2
[Example of GW2 of this embodiment]
FIG. 5 shows an example of a functional block diagram of the GW 2 used in the present embodiment.
The GW 2 includes, for example, an SS interface unit 21, a BS interface unit 22, a PCRF interface unit 23, a GW interface unit 24, a memory unit 25, and a processing unit 26. Note that when the GW 2 is a separate node from the PCRF 3, the GW interface unit 24 may be omitted.
As a modification, when the GW 2 is a PCRF3 integrated node, the PCRF interface unit 23 may be omitted.

  The SS interface unit 21 is an interface with SS1. The SS interface unit 21 allows the GW 2 to transmit and receive IP packets with the SS 1. In the present embodiment, the GW 2 uses the SS interface unit 21 to set the initial value of the remaining bandwidth that can be allocated to each service from SS 1 and the request generation time difference weight a used for calculating the bandwidth allocation request total priority of each service. The UP difference weight b may be received.

  The BS interface unit 22 is an interface with the BS 4. The GW 2 transmits and receives IP packets to and from the BS 4 through the BS interface unit 22. In the present embodiment, the GW 2 may transmit the band assigned to each MS 5 to the BS 4 by the BS interface unit 22 or may receive the UP of each MS 5 and the band allocation request generation time from the BS 4.

  The PCRF interface unit 23 is an interface with the PCRF 3. With the PCRF interface unit 23, the GW 2 transmits and receives IP packets to and from the PCRF 3. In the present embodiment, the GW 2 may receive, for example, a band allocated to each MS 5 from the PCRF 3 by the PCRF interface unit 23, or may transmit the UP of each MS 5 and a band allocation request occurrence time to the PCRF 3.

  The GW interface unit 24 is an interface with another GW 2. With the GW interface unit 24, the GW 2 transmits and receives IP packets to and from other GWs 2. In the present embodiment, the GW 2 transmits / receives the identifier of the MS 5 that has requested bandwidth allocation to / from another GW 2, the allocation request bandwidth, and the like through the GW interface unit 24. Moreover, you may transmit / receive the allocation request generation time etc. between GW2.

  The memory unit 25 stores and manages information such as IP packets to be transmitted and received, addresses of SS1, GW2, PCRF3, and BS4 to be connected, bandwidth remaining capacity that can be allocated to each service, as necessary. The processing unit 26 performs management of information held in the memory unit 25, IP packet transmission / reception processing such as construction and analysis of IP packets, and the like.

FIG. 16 shows an example of a block diagram of the memory unit of the gateway. FIG. 17 shows an example of a block diagram of the processing unit of the gateway.
As a modification of the present embodiment, when the GW 2 is a PCRF3-integrated node, the memory unit 25, for example, as shown in FIG. GW table 252, GW-specific transmission destination address table 253, MS-specific UP table 254, and service-specific bandwidth allocation request total priority calculation parameter table 255, each service's allocable bandwidth remaining amount, each service Allocable bandwidth remaining amount transmission destination GW, transmission destination address of each GW2, UP of each MS5, bandwidth allocation request total priority calculation parameter for each service, and the like can be managed. Details of each table will be described later.

  For example, as shown in FIG. 17, the processing unit 26 includes a memory management unit 261 that manages information stored in the memory unit 25, a transmission / reception processing unit 262 that performs IP packet transmission / reception processing such as construction and analysis of IP packets, and the like. Then, management of information held in the memory unit 25, IP packet transmission / reception processing such as construction and analysis of IP packets, and the like are performed. Further, as shown in FIG. 17, for example, the processing unit 26 allocates a band between BS4 and MS5, between BS4 and GW2, and between GW2 and SS1 for each MS5, calculates a bandwidth allocation request total priority of each service, A bandwidth allocation processing unit 263 that determines whether or not to accept a request based on the calculated bandwidth allocation request total priority, and the like, and bandwidth allocation between BS4 and MS5, between BS4 and GW2, and between GW2 and SS1 for each MS5, Calculation of the bandwidth allocation request total priority of each service, determination of acceptability of a request based on the calculated bandwidth allocation request total priority, and the like are performed. When the time when the GW 2 receives the bandwidth allocation request is used for determining the priority of the bandwidth allocation request, the processing unit 26 receives the bandwidth allocation request of the MS 5 acquired by the GW 2 from the MS 5 via the BS 4 as shown in FIG. The time measuring unit 264 is configured to measure time, and the processing unit 26 also performs time measurement of the band allocation request reception time of the MS 5 acquired by the GW 2 from the MS 5 via the BS 4.

[An example of information held in the memory unit of the GW 2 of the present embodiment]
FIG. 6 (described above) shows an allocatable bandwidth remaining amount table for each service as an example of information held in the memory unit of GW2 when GW2 is a PCRF3-integrated node as a modification of the present embodiment.
The allocable bandwidth remaining amount table for each service stores, for example, the allocable bandwidth remaining amount corresponding to the service identifier.

The service identifier is an identifier of a service provided by SS1 connected to GW2. The remaining bandwidth that can be allocated is the remaining bandwidth that can be currently allocated to each MS 5.
The initial values of these pieces of information can be set and stored in advance in the GW 2 by the operator, for example. Also, these pieces of information can be updated by values acquired from SS1, for example, values additionally set by the operator in GW2, or values acquired via BS4 at the time of initial registration of MS5.

FIG. 11 shows, as an example of information held in the memory unit of GW 2, a allocable bandwidth remaining amount transmission destination GW table for each service when GW 2 is a PCRF 3 integrated node as a modification of the present embodiment.
The allocable bandwidth remaining amount transmission destination GW table for each service stores, for example, the allocable bandwidth remaining amount transmission destination GW corresponding to the service identifier.

The service identifier is an identifier of a service provided by SS1 connected to GW2. The allocatable bandwidth remaining amount transmission destination GW is destination information such as an identifier or an IP address of the GW 2 that needs to notify a change in the remaining allocatable bandwidth of the service.
The initial values of these pieces of information can be set and stored in advance in the GW 2 by the operator, for example. Also, these pieces of information can be updated by values acquired from SS1, for example, values additionally set by the operator in GW2, or values acquired via BS4 at the time of initial registration of MS5.

FIG. 12 shows a GW-specific destination address table as an example of information held in the memory unit of the GW 2 when the GW 2 is a PCRF3-integrated node as a modification of the present embodiment.
In the GW-specific transmission destination address table, for example, a GW identifier and a transmission destination address are stored in association with each other.

  The GW identifier is an identifier of each GW2. The transmission destination GW address is destination information such as the IP address of the GW. This table is not necessary when destination information such as an IP address is set in the allocatable bandwidth remaining amount transmission destination GW of the allocable bandwidth remaining amount transmission destination GW table for each service.

  The initial values of these pieces of information can be set and stored in advance in the GW 2 by the operator, for example. Further, these pieces of information can be updated, for example, by values acquired from SS1 or values additionally set by the operator in GW2.

FIG. 9 (described above) shows an MS-specific UP table as an example of information held in the memory unit of the GW 2 when the GW 2 is a PCRF3-integrated node as a modification of the present embodiment.
The UP table for each MS stores, for example, the UP for each MS corresponding to the MS identifier.
The MS identifier is an identifier of MS5. UP is a value indicating the level of priority assigned to each user. For example, the smaller the value, the higher the priority.

  The initial values of these pieces of information can be set and stored in advance in the GW 2 by the operator, for example. Also, these pieces of information can be updated by values acquired from SS1, for example, values additionally set by the operator in GW2, or values acquired via BS4 at the time of initial registration of MS5.

FIG. 10 (described above) shows a service-specific bandwidth allocation request total priority calculation parameter table as an example of information held in the memory unit of GW2 when GW2 is a PCRF3-integrated node as a modification of the present embodiment. .
The parameter table for bandwidth allocation request overall priority calculation for each service stores, for example, a request generation time difference weight a and an UP difference weight b used for bandwidth allocation request overall priority calculation corresponding to the service identifier. Is done.

  The service identifier is an identifier of a service provided by SS1 connected to GW2. The request generation time difference weight a is a value indicating a degree of emphasis on the request generation time difference when calculating the overall priority P of the bandwidth allocation request for the service. For example, the larger the value, the earlier the request generation time is. Indicates that there is a strong tendency to be more important. Further, when the request reception time of GW2 is used instead of the request generation time, the value indicates a degree of emphasis on the difference in request reception time of GW2. Further, when the request reception time of the PCRF 3 is used instead of the request generation time, the value indicates a degree of emphasis on the difference in the request reception time of the PCRF 3. The UP difference weight b is a value indicating the degree of emphasis on the UP difference when calculating the overall priority P of the bandwidth allocation request for the service. For example, the larger the value, the more important the request of the MS 5 with higher UP is. Indicates a strong tendency.

  The initial values of these pieces of information can be set and stored in advance in the GW 2 by the operator, for example. Also, these pieces of information can be updated by values acquired from SS1, for example, values additionally set by the operator in GW2, or values acquired via BS4 at the time of initial registration of MS5.

2-3. Bandwidth allocation [an example of bandwidth allocation by PCRF3 when GW2 of this embodiment is a separate node from PCRF3]
FIG. 13 shows processing when a bandwidth allocation request message is received from GW 2 as an example of processing of PCRF 3 in bandwidth allocation. Here, the process of PCRF # 2 in FIG. 1 is shown as an example.
In step S301, the processing unit 34 of the PCRF # 2 receives a message requesting bandwidth allocation for a service with MS from the GW # 1. The message includes a destination address (in this case, the address of PCRF # 2), an identifier of the MS requesting the bandwidth, an identifier of the service requesting the bandwidth by the MS, a bandwidth requested by the MS, and a flag indicating the assignment request message Such information is included. Further, the message can include a request occurrence time. For example, when the MS request generation time is used to determine the priority of the bandwidth allocation request, the MS request generation time acquired by the GW # 1 from the MS via the BS is also included. Further, when the request reception time of GW # 1 is used for determining the priority of the bandwidth allocation request, the time when GW # 1 acquires the request for the MS from the BS is also included. Here, for example, when the MS request generation time is used to determine the priority of the bandwidth allocation request, the MS identifier is MS # 1, the service identifier is Service # 1, the MS requests allocation bandwidth is 8 kbps, and the MS The request occurrence time is set to January 1, 2010 at 12:00:00.
In step S302, the processing unit 34 of the PCRF # 2 refers to the allocable bandwidth remaining amount table 331 by service, and the allocation request bandwidth for the service with the MS # 1 received in step S301 is the allocable bandwidth of the service. It is determined whether the remaining amount is exceeded.

If exceeded, in step S303Y, the processing unit 34 returns a request rejection message to GW # 1 and ends the process. The message includes information such as an identifier of an MS that rejects the request, an identifier of a service that rejects the request, and a flag indicating an assignment rejection message.
If not exceeded, the processing unit 34 of the PCRF # 2 determines, in step S303N, the PCRF 3 corresponding to the service based on the per-service allocatable bandwidth remaining amount transmission destination PCRF table 332 and / or the per-PCRF transmission destination address table 333. (Destination) A message requesting bandwidth allocation is sent to all of the destinations. Here, the processing unit 34 determines that it is not exceeded because the allocable bandwidth remaining amount (Remain) for Service # 1 is 15 kbps, and transmits a message to PCRF # 1 and PCRF # 3 corresponding to Service # 1, respectively. . In the message, the transmission source address (here, the address of PCRF # 2), the allocable bandwidth remaining amount transmission destination PCRF table 332 and / or the transmission destination address acquired from the PCRF transmission destination address table 333 are set. Information such as an identifier of an MS requesting a band, an identifier of a service for which the MS requests a band, a band for which the MS requests an allocation, and a flag indicating an allocation request message are included. Further, the message can include a request occurrence time. For example, when the MS request generation time is used to determine the priority of the bandwidth allocation request, the MS request generation time acquired by the GW # 1 from the MS via the BS is also included. Further, when the request reception time of GW # 1 is used for determining the priority of the bandwidth allocation request, the time when GW # 1 receives the request message of the MS from the BS is also included. When the request reception time of PCRF # 2 is used for determining the priority of the bandwidth allocation request, the time when PCRF # 2 receives the request message of the MS from GW # 1 is also included. Here, for example, when the MS request generation time is used to determine the priority of the bandwidth allocation request, the MS identifier is MS # 1, the service identifier is Service # 1, the MS requests allocation bandwidth is 8 kbps, and the MS The request occurrence time is set to January 1, 2010 at 12:00:00.

  In step S304, the processing unit 34 of the PCRF # 2 waits for the response message corresponding from all the PCRFs corresponding to the service that transmitted the message in step S303N to be returned. Here, the processing unit 34 of the PCRF # 2 waits for a response message to be returned from each of the PCRF # 1 and PCRF # 3. For example, the processing unit 34 of the PCRF # 2 may start a response waiting timer set in advance in the PCRF # 2 and wait for a reply for a certain time until the response waiting timer expires.

  Even if the response waiting timer expires, if no reply is received from any of the PCRFs that transmitted the message in step S303N, the processing unit 34 of PCRF # 2 returns the pre-set value to PCRF # 2 in step S305N. Operates according to normal processing. For example, the processing unit 34 of the PCRF # 2 may retransmit the message to a part of the PCRFs for which no reply is received. If no reply is received, the GW # 1 accepts or rejects the bandwidth allocation request. You may reply. Retransmission of messages for some PCRFs that do not receive a reply may be performed a preset number of times in PCRF # 2, or may be repeated until a reply is received. In addition, retransmission of a message for some PCRFs that do not receive a reply may be transmitted at a retransmission interval preset in PCRF # 2, or may be transmitted according to a transmission interval randomly generated by PCRF # 2. .

  If the processing unit 34 of the PCRF # 2 receives a corresponding response message from any of the PCRFs that transmitted the message in step S303N before the response waiting timer expires, the processing unit 34 receives from the PCRF in step S305Y. It is checked whether the response message is a message indicating assignment permission. For example, a flag indicating whether the bandwidth allocation is permitted or rejected may be included in the response message, and the value may be checked.

If the result of the check in step S305Y is a message indicating permission, the processing unit 34 has received a response message corresponding to the allocation request message from all PCRFs that transmitted the message in step S303N in step S306Y, or The determination is made based on a flag indicating an allocation request message.
If there is one or more PCRFs that have not received the response message among the PCRFs that have transmitted the message in step S303N in step S305Y, the processing unit 34 of PCRF # 2 returns to step S304 in step S307N and returns the response message. Wait for a reply.

  On the other hand, if the permission message has been received from all the PCRFs that transmitted the message in step S303N in step S306Y, the processing unit 34 of the PCRF # 2 in the memory unit allocable bandwidth remaining amount table 331 in the memory unit, The remaining bandwidth that can be allocated corresponding to the service for which bandwidth allocation is permitted is updated to a value obtained by subtracting the permitted bandwidth from the remaining bandwidth that can be allocated. Further, the processing unit 34 transmits an allocation permission message to GW # 1 in step S307Y, transmits a bandwidth remaining amount change message to all the PCRFs that transmitted the message in step S303N, and ends the processing. The allocation permission message to GW # 1 includes a transmission source address (here, the address of PCRF # 2), an identifier of the MS requesting the bandwidth, an identifier of the service requesting the bandwidth by the MS, and a bandwidth requested by the MS , Information such as a flag indicating an allocation permission message is included. The bandwidth remaining amount change message to another PCRF includes a transmission source address (here, the address of PCRF # 2), a transmission destination address, an identifier of a service for changing the remaining bandwidth, a remaining bandwidth after the change, and an allocation permission message. This includes information such as a flag indicating.

  On the other hand, when band allocation is rejected with one or more response messages from other PCRFs in step S305Y, the processing unit 34 of PCRF # 2 transmits a band allocation rejection message for the MS to GW # 1 in step S306N. . The band allocation rejection message for GW # 1 includes information such as the identifier of the MS requesting the band, the identifier of the service for which the MS requests the band, and a flag indicating the allocation rejection message.

FIGS. 18A and 18B show processing when a bandwidth allocation request message is received from PCRF 3 as an example of processing of PCRF 3 in bandwidth allocation. Here, the process of PCRF # 3 in FIG. 1 is shown as an example.
In this example, when a message requesting bandwidth allocation is transmitted from PCRF # 2 in step S303N of FIG. 13, the processing unit 34 of PCRF # 3 requests MS # 1 from PCRF # 2 in step S311. A message requesting bandwidth allocation for a service is received. In this message, the transmission source address (here, the address of PCRF # 2), the transmission destination address acquired by PCRF # 2 from the available bandwidth remaining amount transmission destination PCRF table 332 or the PCRF transmission destination address table 332 are set. And information such as an identifier of an MS requesting a bandwidth, an identifier of a service requesting a bandwidth by the MS, a bandwidth requested by the MS for allocation, and a flag indicating an allocation request message. Further, the message can include a request occurrence time. When the MS request generation time is used to determine the priority of the bandwidth allocation request, the MS request generation time acquired by the GW # 1 from the MS via the BS is also included. Further, when the request reception time of GW # 1 is used for determining the priority of the bandwidth allocation request, the time when GW # 1 receives the request message of the MS from the BS is also included. When the request reception time of PCRF # 2 is used for determining the priority of the bandwidth allocation request, the time when PCRF # 2 receives the request message of the MS from GW # 1 is also included. Here, for example, when the MS request generation time is used to determine the priority of the bandwidth allocation request, the MS identifier is MS # 1, the service identifier is Service # 1, the MS requests allocation bandwidth is 8 kbps, and the MS The request occurrence time is set to January 1, 2010 at 12:00:00.

In step S312, the processing unit 34 of the PCRF # 3 determines whether there is a bandwidth allocation request from another MS for a certain service requested by the MS # 1 based on the MS identifier and the service identifier included in the message received in the step S311. Determine.
If there is no bandwidth allocation request of another MS for the service with MS # 1 received in step S311, the processing unit 34 refers to the service-specific allocatable bandwidth remaining amount table 331 in step S313N and receives the MS received in step S311. It is determined whether the allocation request bandwidth for a service of # 1 exceeds the remaining bandwidth (Remain) of the allocatable bandwidth of the service.

If exceeded, the processing unit 34 returns a request rejection message to the PCRF # 2 in step S314Y and ends the process. The message includes a source address (here, the address of PCRF # 3), a destination address (here, the address of PCRF # 2), an identifier of the MS rejecting the request, an identifier of the service rejecting the request, and an allocation rejection message This includes information such as a flag indicating.
If not exceeded, in step S314N, the processing unit 34 transmits a message indicating permission to the PCRF # 2 that has transmitted the message requesting bandwidth allocation received in step S311 and ends the process. In the message, the source address (here, the address of PCRF # 3), the destination address acquired from the source address of the received message are set, the identifier of the MS requesting the bandwidth, the service requesting the bandwidth by the MS Information such as an identifier, a bandwidth requested by the MS for allocation, and a flag indicating an allocation permission message are included.

  On the other hand, if there is a message for requesting bandwidth allocation of another MS for the service for which bandwidth allocation is requested in step S311, the processing unit 34 of the PCRF # 3 refers to the allocable bandwidth remaining amount table 331 for each service in step S313Y. Then, the sum of the allocation request bandwidth for a certain service included in the message requesting the bandwidth allocation from MS # 1 and the total allocation request bandwidth for other MSs that are currently in the allocation permission determination for the request message for that service is Then, it is determined whether or not the remaining bandwidth of the band that can be allocated to the service is below.

  If the total requested bandwidth for the service is equal to or less than the remaining bandwidth that can be allocated for the service, in step S316Y, a message indicating permission is transmitted to the PCRF # 2 that has transmitted the bandwidth allocation message received in step S311. . In the message, the source address (here, the address of PCRF # 3), the destination address acquired from the source address of the received message are set, the identifier of the MS requesting the bandwidth, the service requesting the bandwidth by the MS Information such as an identifier, a bandwidth requested by the MS for allocation, and a flag indicating an allocation permission message are included.

  For example, the PCRF # 3 receives a message requesting band allocation of the MS # 1 from the PCRF # 2 in step S311 of FIG. 18, and the MS # 2 from the GW connected to the PCRF # 3 in step S301 of FIG. Assume that a message for requesting bandwidth allocation is received. At this time, when the process proceeds to step S316Y, with respect to the request from MS # 1, PCRF # 2 can update the remaining bandwidth by the band allocation permission message from PCRF # 3, while from MS # 2 Regarding the request, PCRF # 3 can update the remaining bandwidth according to the flowchart of FIG.

  On the other hand, when the total of the allocation request bandwidths for the service exceeds the remaining bandwidth of the bandwidth that can be allocated for the service, the processing unit 34 determines in step S316N whether the bandwidth allocation request message for PCRF # 2 can be permitted. Here, it is assumed that a message for requesting bandwidth allocation is received from MS # 1 and MS # 2 described above. At this time, when the request generation time of the MS 5 is used for determining the priority of the bandwidth allocation request for determination, the MS identifier is MS # 1 and the service identifier is Service as the contents of the PCRF # 2 allocation request received in step S 311. # 1, The bandwidth for which the MS requests allocation is 8 kbps, the MS request generation time is 12:00 on January 1, 2010, and the contents of the allocation request received from the GW # 2 by the PCRF # 3 are as follows: , MS # 2 is the service identifier, Service # 1 is the service identifier, 10 kbps is the bandwidth for which the MS requests allocation, and the MS request generation time is 1 January 2010 at 12:00:30. At this time, since the total required bandwidth is 18 kbps, the remaining bandwidth of the service allocatable bandwidth stored in the per-service allocatable bandwidth remaining amount table 331 exceeds 15 kbps.

For example, the PCRF # 3 determines the total priority difference P of the requests based on the following formula based on the difference X of the bandwidth allocation request occurrence time in the MS and the difference Y of the user priority UP. Then, it is determined whether the bandwidth allocation request message from PCRF # 2 can be permitted based on the sign. Instead of the band allocation request occurrence time in the MS, an appropriate time such as a GW band allocation request reception time or a PCRF band allocation request reception time may be used.
[Formula 1]
P = aX + bY

  For example, when P is positive, a bandwidth allocation request for a message from PCRF # 2 is rejected, and when P is negative, a bandwidth allocation request from PCRF # 2 is permitted. When P = 0, permission or rejection is determined according to a predetermined rule. For example, the priority set in advance in the MS, the priority set in advance in the PCRF or GW, or a request allowed at random may be determined. The request generation time difference weight a and the UP difference weight b used for the bandwidth allocation request overall priority calculation obtain values corresponding to the service identifiers from the service-specific bandwidth allocation request overall priority calculation parameter table. Here, a = 3 and b = 100 are used as a and b corresponding to the service identifier Service # 1. Further, here, the difference X between the request generation times is calculated in seconds. Request generation time of MS # 1 acquired from the request message January 1, 2010, 12:00:00, and request generation time of MS # 2 acquired from the response message, January 1, 2010, 12:00:30 The difference X is +30 seconds. On the other hand, the UP of each MS acquires a value corresponding to the identifier of the MS from the MS-specific UP table. Since UP = 3 corresponding to the MS identifier MS # 1 acquired from the request message and UP = 2 of the MS identifier MS # 2 acquired from the response message, the UP difference Y is -1. Substituting the above values into Equation 1, from P = 3 × 30−1 × 100 = −10 <0, a bandwidth allocation request for MS # 2, that is, a bandwidth allocation request received from GW # 2, is permitted, and MS # A bandwidth allocation request for 1, that is, a bandwidth allocation request received from PCRF # 2 is rejected.

  When there are a plurality of bandwidth allocation requests for a certain service, the processing unit 34 of the PCRF # 3 performs the above-described determination processing for all the allocation requests to be processed. In addition, the allocation request that is a target at this time may include all requests waiting for permission of other PCRFs at the time of determination processing, or may be limited to only a part of allocation requests. The criterion for limiting the allocation request may be only the allocation request received before a certain time before the determination process or before a certain preceding process.

In step S317, the processing unit 34 of the PCRF # 3 determines whether the request received in step S311 is permitted for all requests as a result of the determination process in step S316N for the allocation request received from the PCRF # 2 in step S311. Determine whether or not.
If the bandwidth allocation request received from the PCRF # 2 in step S311 is permitted in all determination processes, the processing unit 34 of the PCRF # 3 receives a permission message for the bandwidth allocation request received from the PCRF # 2 in step S318Y. To the source PCRF # 2. The message includes a source address (here, the address of PCRF # 3), a destination address (here, the address of PCRF # 2), an identifier of the MS that permits bandwidth allocation, an identifier of a service that permits bandwidth allocation, and an allocation. Includes information such as a band for permitting the allocation and a flag indicating an allocation permission message.

  If even one bandwidth allocation request received from PCRF # 2 in step S311 is rejected as a result of the determination process, the processing unit 34 of PCRF # 3 responds to the bandwidth allocation request received from PCRF # 2 in step S318N. A rejection message is returned to the sender PCRF # 2. The reject message includes a source address (here, the address of PCRF # 3), a destination address (here, the address of PCRF # 2), an identifier of the MS whose request is rejected, an identifier of the service whose request is rejected, and an assignment Information such as a flag indicating a rejection message is included.

  In step S319, the processing unit 34 of the PCRF # 3 transmits a band allocation request message for the other MS # 2 that is permitted as a result of the determination of the request received from the PCRF # 2. In this message, a transmission source address (here, the address of PCRF # 3), a destination address acquired from the per-service allocatable bandwidth remaining amount transmission destination PCRF table 332 and / or the per-PCRF transmission destination address table 333 is set, Information such as an identifier of the MS 5 requesting the band, an identifier of the service requesting the band by the MS 5, a band requesting the allocation by the MS 5, and a flag indicating the allocation request message are included. Further, the message can include a request occurrence time. For example, when the request generation time of the MS 5 is used for determining the priority of the bandwidth allocation request, the request generation time of the MS 5 acquired by the GW 2 from the MS 5 via the BS 4 is also included. Further, when the request reception time of the GW 2 is used for determining the priority of the bandwidth allocation request, the time when the GW 2 acquires the request of the MS 5 from the BS 4 is also included. The message may be merged with the rejection message transmitted in step S318Y and transmitted as one message sharing the header.

  The process after step S319 follows the process after step S304 'as shown in FIG. The processing after step S304 'is the same as the processing after step S304 in FIG. However, in each step of FIG. 13, the contents of “message sent in S303N” and “return to S304” are the same as “message sent in S319N” and “S304 ′” in each step of FIG. The content is changed to “Return”. Thereby, PCRF # 3 can update the remaining bandwidth with respect to the request from MS # 2.

  FIG. 19 shows a process when a remaining bandwidth update message is received from another PCRF 3 as an example of the process of the PCRF 3 in bandwidth allocation. Here, a process in which PCRF # 3 in FIG. 1 receives a remaining bandwidth update message from PCRF # 2 is shown as an example.

In step S321, the processing unit 34 of the PCRF # 3 receives a message for updating the remaining bandwidth of the service with the MS from the PCRF # 2. The message includes information such as the identifier of the service for updating the remaining bandwidth, the remaining bandwidth after the change, and a flag indicating the remaining bandwidth update message.
In step S322, the processing unit 34 of the PCRF # 3 updates the remaining amount of bandwidth that can be allocated for the service stored in itself, and ends the process. The processing unit 34 of the PCRF # 3 stores the allocable bandwidth remaining amount corresponding to the service specified by the bandwidth remaining amount update message received in step S321 in the allocable bandwidth remaining amount table 331 for each service in the memory unit 33. Update to the value specified in the remaining bandwidth update message received in step S321.

[Example of Band Allocation by GW 2 when GW 2 as a Modified Example of this Embodiment is a PCRF 3 Integrated Node]
When GW2 is a PCRF3-integrated node, the bandwidth allocation is performed by GW2 instead of PCRF3. 11 and 12 are used instead of FIG. 6 and FIG. 7, respectively. The source and destination nodes of each message are not GWs but BSs such as BSs are nodes that receive bandwidth allocation requests, and are not PCRFs but GWs. The only difference is that the bandwidth allocation process is performed in the same manner as the above-described flow.

3. Advantages of the present embodiment According to the above-described embodiment, since the current value of the bandwidth that can be allocated for each service is shared between the policy server or the gateway, the service can be provided even in an environment where there are a plurality of policy servers and gateways. It is prevented that bandwidth is allocated beyond the remaining bandwidth that can be allocated every time, and packets counted as charging packets at the gateway are discarded at the service provider or base station, causing erroneous charging, By transmitting / receiving packets exceeding the capacity of the node, service quality degradation such as delay due to congestion is not caused.

Further, the above-described embodiment can be realized without introducing higher-level policy server performance requiring high performance requirements for distributed control between policy servers or gateways. Furthermore, the scope of influence due to the failure or stop of the policy server or the gateway does not reach the whole, and the service does not have to be stopped when adding or deleting the service.
Also, even when bandwidth allocation requests are generated almost simultaneously in a plurality of policy servers or a plurality of gateways, priority calculation between requests can be performed for each service. This enables flexible priority control between requests with emphasis on parameters suitable for service operation policies.

The present invention can be used, for example, in a wireless communication system that allocates a band for each wireless terminal.
Further, the present invention can be applied to various communication devices other than PCRF and GW. In addition, the remaining bandwidth that can be allocated for each service managed by the policy server, for each user or each user and service band between terminals between the base station and the terminal, between the base station and the gateway, and between the gateway and the service providing server. The present invention relates to a communication system and method set by a policy server or a gateway based on information and a gateway or base station or the like performing bandwidth control, and a communication device such as a policy server device and a gateway device.

DESCRIPTION OF SYMBOLS 1 Service provision server 2 Gateway 21 SS interface part 22 BS interface part 23 PCRF interface part 24 GW interface part 25 Memory part 251 Allocable bandwidth remaining amount table 252 classified by service allocable remaining bandwidth transmission destination PCRF table 253 classified per service Destination address table 254 MS-specific UP table 255 Parameter table for service-specific bandwidth allocation request total priority calculation 26 processing unit 261 memory management unit 262 transmission / reception management unit 263 bandwidth allocation processing unit 264 timing unit 3 policy server steps S301 to S307 can be allocated Step S3 of the processing flow by the policy server that has received the bandwidth allocation request message from the terminal in the bandwidth setting based on the remaining amount of bandwidth 11 to Step S319 Steps S321 to S322 of the processing flow by the policy server that has received a bandwidth allocation request message from another policy server in bandwidth setting based on the remaining bandwidth that can be allocated Bands based on the remaining bandwidth that can be allocated Step 31 of the processing flow by the policy server that has received the remaining bandwidth update message from the other policy server in the setting GW interface unit 32 PCRF interface unit 33 Memory unit 331 Allocable bandwidth remaining table by service 332 Allocable bandwidth remaining by service Transmission destination PCRF table 333 Transmission destination address table by PCRF 334 UP table by MS 335 Band allocation request total priority calculation parameter table by service 34 Processing unit 341 Memo Management unit 342 reception management section 343 band allocation processing unit 344 time measuring unit 4 the base station 5 terminal

Claims (11)

A communication system,
A first communication device;
A second communication device connected to the first communication device;
With
The first communication device includes a first remaining bandwidth table that stores an allocatable bandwidth remaining amount corresponding to the service identifier, and one of the allocatable bandwidth remaining transmission destinations corresponding to the service identifier, or A first transmission destination table in which a plurality of communication devices are stored,
The MS includes the MS identifier of the first terminal requesting bandwidth allocation from the first terminal, the service identifier of the service for which the first terminal requests bandwidth, and the requested bandwidth for which the first terminal requests allocation. Receiving a first request message requesting bandwidth allocation for a service;
The first communication device refers to the first remaining bandwidth table, and based on the received first request message, an allocation request bandwidth for a service of the first terminal is assigned to the service. Determine if the available bandwidth is not exceeded,
If not, the first communication device sets a destination address of one or more other communication devices corresponding to the service based on the first destination table, and the first communication device Transmitting a second request message including an MS identifier, a service identifier, and a request bandwidth included in the request message to one or more other communication devices;
When the first communication device receives a permission message from all the other communication devices that have transmitted the second request message within a predetermined time, the first communication device Referring to the remaining amount table, subtracting the requested bandwidth from the remaining bandwidth that can be allocated for the service identifier of the requested service to calculate the changed allocated bandwidth remaining amount, and based on the remaining bandwidth, the first bandwidth remaining amount Update the table,
The first communication device transmits to the first terminal a permission message that permits assignment including an MS identifier, a service identifier, and a requested bandwidth, and all of the second request messages that have been transmitted. To the other communication device, a service identifier for changing the remaining bandwidth, and a bandwidth remaining amount change message including the changed allocated bandwidth remaining amount,
The second communication device includes a second remaining bandwidth table that stores the remaining bandwidth that can be allocated corresponding to the service identifier, and one of the remaining bandwidth remaining destinations that correspond to the service identifier, A second transmission destination table storing a plurality of communication devices,
When the second request message is received from the first communication device, for the service with the service identifier included in the received second request message, the first of the MS identifiers in the second request message. Determining whether there is a bandwidth allocation request from the second terminal other than
When there is a bandwidth allocation request of the second terminal for the service, the second communication device refers to the second remaining bandwidth table and corresponds to the service of the service identifier included in the second request message. Determining whether the sum of the allocation request bandwidth and the allocation request bandwidth requested from the second terminal for the service is less than or equal to the remaining bandwidth available for the service;
When the total exceeds the remaining bandwidth, the second communication device allocates a bandwidth based on the second request message from the first communication device based on the priority and / or request generation time of each terminal. And whether the bandwidth allocation request from the second terminal can be permitted,
When it is determined that the bandwidth allocation request received from the first communication device is rejected, the second communication device rejects the bandwidth allocation for the first terminal to the rejected first communication device. A message is returned, and the second communication device sets a destination address of one or more other communication devices corresponding to the service based on the second destination table, and permits The third identifier for requesting bandwidth allocation including the MS identifier for requesting the bandwidth of the other second terminal, the service identifier for requesting the bandwidth of the second terminal, and the allocation request bandwidth of the second terminal. Sending a request message to one or more other communication devices;
The communication system. The communication system according to claim 1,
If the second communication device further receives a permission message from all the other communication devices that have transmitted the third request message within a predetermined time, the second communication device Referring to the remaining bandwidth table, the allocated bandwidth remaining after the change is calculated by subtracting the requested bandwidth from the remaining bandwidth that can be allocated to the service identifier of the requested service, and the second bandwidth is calculated based on the remaining bandwidth. Update the remaining amount table
The second communication device transmits to the second terminal a permission message that permits assignment including an MS identifier, a service identifier, and a requested bandwidth, and all of the third request messages that have been transmitted. A communication system characterized by transmitting a remaining bandwidth change message including a service identifier for changing the remaining bandwidth and the allocated remaining bandwidth after the change to the other communication device. . The communication system according to claim 1,
The second communication device is configured such that a sum of an allocation request bandwidth for a service having a service identifier included in the second request message and an allocation request bandwidth requested to be allocated from the second terminal for the service is When the remaining bandwidth is not exceeded, the second communication device transmits a message indicating permission to the first communication device that has transmitted the second request message. The communication system according to claim 1,
The second communication device is:
If there is no bandwidth allocation request from the second terminal for the service for which bandwidth allocation is requested, the allocation request bandwidth for the service with the service identifier is determined by referring to the second remaining bandwidth table. Determine whether the remaining allocatable bandwidth is exceeded,
If not exceeded, a response message indicating permission is transmitted to the first communication device that is the transmission source of the second request message. On the other hand, if exceeding, a rejection message is transmitted. system. The communication system according to claim 1,
The second communication device is:
When it is determined that the bandwidth allocation request received from the first communication device is permitted, the second communication device sends the second request message to the first communication device to the first terminal. A communication system according to claim 1, wherein a bandwidth allocation permission message is returned. The communication system according to claim 1,
The second communication device is:
The third request message is merged with the rejection message of band allocation for the first terminal to the first communication device that has transmitted the second request message that has been rejected, and the header is shared. A communication system characterized by transmitting as one message. The communication system according to claim 1,
The first communication device is:
Furthermore, a first priority table that stores the priority for each MS corresponding to the MS identifier is provided,
The first, second, and third request messages further include a request occurrence time for requesting bandwidth allocation,
The first communication device obtains the bandwidth allocation request occurrence time for the first terminal and the second terminal, and the first terminal and the second obtained by referring to the first priority table. And determining whether or not the bandwidth allocation request message from the first communication device can be permitted based on the user priority UP related to the terminal. The communication system according to claim 7, wherein
The first communication device is:
Based on the difference X of the bandwidth allocation request occurrence time and the difference Y of the user priority UP,
Based on the following formula, a total priority difference P of requests is determined, and it is determined whether the bandwidth allocation request message from the first communication device can be permitted by its positive or negative. P = aX + bY
However, the values of a predetermined request generation time difference weight a and a priority difference weight b corresponding to the service identifier

A communication system characterized by the above. The communication system according to claim 1,
When the second communication device receives from the first communication device a message for updating the remaining bandwidth including the identifier of the service for updating the remaining bandwidth and the bandwidth remaining after the change for a service with MS, The second communication device designates an allocatable bandwidth remaining amount corresponding to the service designated by the received bandwidth remaining update message in the second bandwidth remaining amount table by the received bandwidth remaining update message. A communication system, wherein the communication system is updated to the updated value. A communication method for sharing and managing a remaining bandwidth that can be allocated for each service between a plurality of communication devices including a first communication device and a second communication device,
Each of the first communication device and the second communication device is:
A remaining bandwidth table that stores the remaining bandwidth that can be allocated in response to the service identifier,
In correspondence with the service identifier, a transmission destination table in which one or a plurality of communication devices of the remaining bandwidth allocation destination is stored is stored,
The first communication device includes, from the first terminal, an MS identifier of the first terminal that requests bandwidth allocation, a service identifier of a service for which the first terminal requests bandwidth, and the first terminal Receiving a first request message requesting bandwidth allocation for a service including a requested bandwidth requesting allocation;
The first communication device refers to the remaining bandwidth table and, based on the received first request message, assigns a requested bandwidth for a service of the first terminal to an available bandwidth remaining in the service. Judge whether the amount exceeds,
If not exceeded, the first communication device sets a destination address of one or more other communication devices corresponding to the service based on the destination table, and in the first request message Transmitting a second request message including the included MS identifier, service identifier, and requested bandwidth to one or more other communication devices;
When the first communication device receives permission messages from all the other communication devices that have transmitted the second request message within a predetermined time, the first communication device , Subtract the requested bandwidth from the allocatable bandwidth remaining for the service identifier of the requested service to calculate the changed allocated bandwidth remaining, update the bandwidth remaining table with the bandwidth remaining,
The first communication device transmits to the first terminal a permission message that permits assignment including an MS identifier, a service identifier, and a requested bandwidth, and all of the second request messages that have been transmitted. To the other communication device, a service identifier for changing the remaining bandwidth, and a bandwidth remaining amount change message including the changed allocated bandwidth remaining amount,
When the second communication device receives the second request message from the first communication device, the second request message is sent to the service with the service identifier included in the received second request message. Determining whether there is a bandwidth allocation request from the second terminal other than the first terminal of the MS identifier in
When there is a bandwidth allocation request of the second terminal for the service, the second communication device refers to the bandwidth remaining amount table and allocates the requested bandwidth for the service of the service identifier included in the second request message. And the sum of the allocation request bandwidth requested from the second terminal for the service is less than or equal to the remaining bandwidth that can be allocated for the service,
When the total exceeds the remaining bandwidth, the second communication device allocates a bandwidth based on the second request message from the first communication device based on the priority and / or request generation time of each terminal. And whether the bandwidth allocation request from the second terminal can be permitted,
When it is determined that the bandwidth allocation request received from the first communication device is rejected, the second communication device rejects the bandwidth allocation for the first terminal to the rejected first communication device. A message is returned, and the second communication device sets a destination address of one or more other communication devices corresponding to the service based on the destination table and is permitted. An MS identifier for requesting the bandwidth of the other second terminal, a service identifier for requesting the bandwidth by the second terminal, and a third request message for requesting bandwidth allocation including the allocation request bandwidth of the second terminal. And transmitting to one or a plurality of other communication devices. A communication device,
A remaining bandwidth table that stores the remaining bandwidth that can be allocated for each service corresponding to the service identifier,
Corresponding to the service identifier, a storage unit that stores a destination table in which one or a plurality of communication devices of the remaining bandwidth available for each service is stored;
The MS includes the MS identifier of the first terminal requesting bandwidth allocation from the first terminal, the service identifier of the service for which the first terminal requests bandwidth, and the requested bandwidth for which the first terminal requests allocation. A request message receiving unit for receiving a first request message for requesting bandwidth allocation for a certain service;
With reference to the remaining bandwidth table, based on the received first request message, it is determined whether an allocation request bandwidth for a service of the first terminal exceeds an allocatable bandwidth remaining amount of the service. A bandwidth remaining excess determination unit;
If not exceeded, the destination address of one or more other communication devices corresponding to the service is set based on the destination table, and the MS identifier and service identifier included in the first request message A first request message transmission unit that transmits a second request message including a request band to one or more other communication devices;
When a permission message is received from all the other communication devices that have transmitted the second request message within a predetermined time, an allocatable bandwidth for the service identifier of the requested service is referred to the remaining bandwidth table An update unit that subtracts the requested bandwidth from the remaining amount to calculate the allocated bandwidth remaining after the change, and updates the bandwidth remaining amount table with the bandwidth remaining;
To the first terminal, a permission message for permitting allocation including an MS identifier, a service identifier, and a request bandwidth is transmitted to all the other communication devices that have transmitted the second request message. A service identifier for changing the remaining bandwidth, a remaining bandwidth change message sending unit for sending a remaining bandwidth change message including the assigned remaining bandwidth, and
When the second request message including the MS identifier, the service identifier, and the request bandwidth included in the first request message is received from another communication device, the service with the service identifier included in the received second request message is received. On the other hand, a bandwidth allocation request presence / absence determining unit that determines presence / absence of a bandwidth allocation request from the second terminal other than the first terminal of the MS identifier in the second request message;
When there is a bandwidth allocation request of the second terminal for the service, the bandwidth remaining table is referred to, an allocation request bandwidth for the service of the service identifier included in the second request message, and the service for the service A remaining bandwidth determination unit that determines whether the sum of the allocation request bandwidth requested from the second terminal is less than or equal to the remaining bandwidth that can be allocated to the service;
If the total exceeds the remaining bandwidth, bandwidth allocation by the second request message from the certain communication device and bandwidth allocation from the second terminal based on the priority and / or request generation time of each terminal A request permission unit for determining which of the requests can be permitted; and
When it is determined that the bandwidth allocation request received from the certain communication device is rejected, a bandwidth allocation rejection message for the first terminal is returned to the certain communication device that has been rejected, and the transmission destination table Based on the MS identifier for setting the destination address of one or more communication devices corresponding to the service and requesting the bandwidth of the other authorized second terminal, and the second terminal assigning the bandwidth A second request message transmission unit for transmitting a third request message for requesting bandwidth allocation including a requested service identifier and an allocation request bandwidth of the second terminal to the one or more communication devices. A communication device characterized by the above.

Images