JP5736617B2 - Communication system control method, communication system, and communication apparatus - Google Patents

Description

  The present invention relates to a communication system and a communication apparatus, and more particularly to a technique for applying QoS or charging control to a packet transmitted and received between a terminal and a service providing server.

  In recent years, research and standardization activities for the 3.9th generation mobile communication system and the 4th generation mobile communication system have been promoted as a method for realizing higher speed and higher quality of mobile radio communication. 3GPP (3rd Generation Partnership Project), a standardization organization that formulates LTE (Long Term Evolution), one of the 3.9th generation mobile communication systems, and LTE Advanced, which is one of the 4th generation mobile communication systems. ) Defines TS (Technical Specification) as the specification of the standard.

  In 3GPP TS, a downlink direction packet (hereinafter referred to as a DL packet) transmitted from a service providing server belonging to an IP (Internet Protocol) network to the terminal, and an uplink direction transmitted from the terminal to the service providing server. For each packet (hereinafter referred to as UL packet), packet filtering for associating charging conditions or QoS (Quality of Service) conditions applied to each packet is performed at the gateway, and charging control and QoS control are performed based on the result. The specifications for applying are specified. Here, the QoS control is, for example, priority control, packet transfer rate control, or packet discard. Also, in TS, a group associated with one or more services of a certain user is set in advance, the number of bytes of packets transmitted by the gateway is integrated for each group, and the integrated value reaches the threshold set in the gateway. As a result, specifications for notifying the accounting server or policy management server are defined.

  In Non-Patent Document 1, the definition of PCC Rule (Policy and Charging Control Rule) and the specification of the Usage Monitoring function are defined. PCC Rule is one of the gateways in 3GPP from the node PCRF (Policy and Charging Rule Function) that manages QoS and charging policy, including filter conditions for linking packets defining groups and groups that define integration ranges P-GW (PDN Gateway, PDN is an abbreviation of Packet Data Network) is notified or preset in P-GW. The Usage Monitoring function detects the trigger when the integrated value reaches the threshold value of the integrated value of the number of bytes for each group specified by the PCRF or preset in the P-GW, and sends a message from the P-GW to the PCRF. It is a function to transmit.

  Non-Patent Document 2 describes that the specification rule of “QoS Control Based on Subscriber Spending Limits” is one of Release 11 Work Items in 3GPP. “QoS Control Based on Subscriber Sending Limits” is defined by OCS (Online Charging Server), which is an online charging server in 3GPP, or integrated to the threshold value of the number of bytes for each group preset in P-GW. This is a function capable of sending a message from the P-GW to the OCS when the value reaches, and notifying the PCRF from the OCS of a change in charging status based on the charging policy set in the OCS.

  Further, Patent Document 1 discloses a technique for charging based on a charging policy for each terminal group to which one or a plurality of terminals belong, regarding an electronic mail charging system and an electronic mail charging method.

JP 2006-101008 A

3GPP TS 23.203 V11.2.0, (2011-6), Technical Specification 3GPP contributions SP-110086, (2011-3), SA Plenary # 51 meeting contributions

  In the above-described integration function of the number of bytes of transmission packets in the P-GW according to the 3GPP TS, and the notification function to the OCS or PCRF when the integration value reaches the threshold value, various functions such as time or standards used for wireless communication are available. When the QoS or charging policy determined based on the conditions is different or changes, it is necessary to perform integration using a plurality of counters each having a different threshold defined in the P-GW. As a result, information such as the number of counters set in the internal memory and filter conditions necessary for associating the packets with the counters increases as the QoS or billing conditions increase, and the time required for associating the packets with the counters increases. Furthermore, an increase in the memory capacity inside the P-GW for holding the counter affects the memory read / write performance of the P-GW. As a result, packet processing delay in the P-GW increases, and problems such as communication performance deterioration or erroneous charging such as discarding of packets that cannot be processed occur.

  In addition, in the OCS and PCRF, when a QoS or charging policy is determined by combining various conditions, a threshold for the number of bytes is set for each condition, and a message regarding the arrival of the threshold for the number of bytes accumulated in the P-GW is displayed. They need to be received individually and combined to determine the policy. As a result, the number of messages between the P-GW and the OCS or PCRF increases, the message processing delay increases, and problems such as communication performance degradation such as discarding of messages that cannot be processed occur. .

  A wide range of services can be developed for mobile terminals due to the expansion of wireless connection bandwidth and the spread of smartphones, etc., and it is predicted that the differentiation competition between services will progress due to the entry of MVNO (Mobile Virtual Network Operator). Under the present circumstances, it is predicted that the problem of the communication performance deterioration due to an increase in conditions for determining the QoS or charging policy will become serious. Similarly, even in the fixed network, there is a concern about the above-mentioned problem of deterioration in communication performance due to an increase in conditions for determining QoS and charging policy due to service diversification.

  In view of the above problems, the object of the present invention is to provide the number of counters used for the integration inside the communication device and the result of the integration to one or both of the communication device and the accounting server or policy management server in a wireless or wired communication system. PROBLEM TO BE SOLVED: To provide a communication system and apparatus capable of switching QoS or charging control parameters at an accurate timing based on QoS or charging policy while preventing deterioration of packet transfer performance without increasing the number of messages related to reaching the threshold value It is in.

A typical example of the present invention is as follows. A control method for a communication system, comprising: a server device connected to a network; a terminal device connected to the network and communicating packets with the server device; and a communication device relaying communication of the packets The communication device associates a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet; and Holding information that associates the received packet with a counter that accumulates at least one of the number of packets and the amount of data to which the weight value is applied, and the number of received packets and the number of received packets A weight value applied to at least one of the data amounts included in the received packet Kicking information includes information that associates with the weight value and the reception time of the packet, the control method of the communication system includes a first procedure for specifying the weight value by the communication device associated with the received packet, At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. wherein a second procedure for integrating with the counter, based on the integrated value with the counter, a third procedure for changing the parameters relating to the control of the QoS or billing associated with said counter, the said first One procedure specifies the weight value associated with the packet received by the communication device based on the reception time of the packet. Characterized in that it comprises a procedure.

  According to an embodiment of the present invention, in a wireless or wired communication system, when switching QoS or charging control parameters when one or both of the number of packets and / or the number of bytes transmitted by a communication device reach a certain threshold, QoS or charging control parameters can be switched at an accurate timing based on QoS or charging policy while preventing transfer performance deterioration.

It is a conceptual diagram for demonstrating the function structure of the communication system based on a 1st Example. It is a block diagram which shows one structural example of the communication system based on 1st Example. It is a functional block diagram which shows an example of the gateway (GW) based on a 1st Example. It is a block diagram of the memory part of GW based on a 1st Example. An example of the table which shows the information for determining the identifier and weight value of the accumulation | aggregation group in the weighted accumulation | storage which GW hold | maintains based on the 1st Example from the terminal (MS) in connection with the communication of the said packet, and the service to which the said packet belongs FIG. It is a figure which shows an example of the table which shows the information for determining the integration threshold value in weighted integration from the integration group to which the said packet belongs based on a 1st Example. It is a figure which shows an example of the table which shows the information of the integrated value for every integration group based on a 1st Example. It is a figure which shows an example of the table which shows the information for determining the weight value based on the time in the weighting integration based on 1st Example from MS related to the communication of the said packet, and the service to which the said packet belongs. It is a figure which shows an example of the table which shows the information for determining the weight value based on the time in weighted integration based on the 1st Example from the integration group to which the said packet belongs. It is a figure which shows an example of the table which shows the information for determining the weight value based on the congestion degree of BS in weighted integration from the base station (BS) related to the communication of the said packet based on a 1st Example. It is a figure which shows an example of the table which shows the information of MS connected to BS based on 1st Example. It is a figure which shows an example of the table which shows the information for determining the weight value based on the congestion degree of BS in weighted integration from BS which concerns on the communication of the said packet based on a 1st Example. It is a figure which shows an example of the table which shows the information for determining the weight value based on the transmission success or failure of the said DL packet to MS in the weighting integration with respect to DL packet transmitted to several BS based on 1st Example. . It is a figure which shows an example of the table which shows the information for determining the comprehensive weight value regarding BS in the weighting integration with respect to the DL packet transmitted to several BS based on 1st Example. It is a functional block diagram which shows an example of the policy management apparatus (PS) based on a 1st Example. It is a functional block diagram which shows an example of the accounting server (CS) based on a 1st Example. It is a figure which shows an example of the weighting integration | accumulation process of one or both of the packet number or byte number with respect to one or both of UL packet or DL packet in GW based on 1st Example. It is a figure which shows an example of the process of reception of the accumulation threshold value reaching message in PS based on 1st Example. It is a figure which shows an example of the process of reception of the integration threshold value arrival message in CS based on 1st Example. It is a figure which shows an example of the process of status change message reception in PS based on 1st Example. It is a figure which shows an example of the process of status change message reception in CS based on a 1st Example. It is a figure which shows an example of the process which corrects the weighted integration value in GW based on 1st Example based on whether the packet was discarded by BS.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. Before describing various embodiments, an outline thereof will be described.

  FIG. 1 is a functional configuration diagram for explaining an outline of a communication system according to the present invention. In FIG. 1, when the gateway (Gateway, hereinafter referred to as GW) 2 receives the UL packet or the DL packet (step S100), the GW 2 sets the QoS and charging parameters (described later) associated with the packet to the QoS and charging parameters. A decision is made based on the policy (step S101).

  Then, the GW 2 determines the weight value associated with the packet based on the QoS or charging policy (step S102), performs one or both of weighted packet number accumulation and weighted byte number accumulation for the packet, Is stored in the corresponding counter (step S103). As a result of these integrations, when the integrated values reach the threshold values set in the respective counters (step S104), the GW 2 creates a message including information on the reached threshold values (threshold arrival information), and sets the threshold values to the threshold values. Transmission is made to the associated destination (steps S106 and S107).

  In the following description, an example is shown in which the number of packets or the amount of data contained in a packet is used as an index indicating the amount of communication in the network. As an example of the index indicating the amount of data included in the packet, the number of bytes of the packet is used, but other indexes may be used. Here, the number of bytes of the packet may be, for example, the number of bytes of the entire packet or a so-called payload length.

  One or both of the policy management apparatus (Policy Server, hereinafter referred to as PS) 3 or the charging server (hereinafter referred to as CS) 6 that has received the message receives the threshold arrival information included in the received message, and the QoS or charging. Based on the policy, whether or not there is a parameter change relating to QoS or charging (that is, whether or not the parameter needs to be changed) is determined. As a result, when it is determined that it is necessary to change QoS or charging parameters, either PS3 or CS6 creates a message including QoS or charging parameter change information (step S108). The message is transmitted to the destination associated with the content (step S109).

  When the GW 2 receives the message transmitted in step S 109, the GW 2 changes the QoS or charging parameter applied in the GW 2, and changes the changed QoS or charging parameter to the UL packet or DL packet received thereafter. Apply.

  By this communication system, QoS or charging parameters determined under various conditions can be uniformly reflected in the integrated value as a weight for each packet. Therefore, even when a plurality of QoS or charging parameter determination conditions are reflected, the gateway Without increasing the number of counters that accumulate the number of packets or bytes according to the number of parameter determination conditions, and without increasing the number of messages used for notification of detection results to PS3 or CS6 according to the number of parameter determination conditions The timing for switching QoS or charging parameters can be accurately detected in packet units, and can be applied to communication control such as bandwidth limitation based on QoS or charging parameters in the gateway. As a result, it is possible to prevent the occurrence of problems such as a heavy user's band oligopoly due to communication performance degradation of the gateway or a delay in application of communication control such as band limitation.

  Hereinafter, a first embodiment of the present invention will be sequentially described with reference to the drawings.

<System configuration>
FIG. 2 is a diagram illustrating a configuration example of the communication system according to the first embodiment. The communication system according to the first embodiment includes a terminal (Mobile Station, hereinafter referred to as MS) 5 that performs wireless communication or wired communication with a base station (Base Station, hereinafter referred to as BS) 4, and a GW 2 that communicates with the MS 5 via the BS4. And a service providing server (Service Server, hereinafter referred to as SS) 1 that communicates with GW2, PS3 that communicates with GW2 and CS6, and CS6 that communicates with GW2 and PS3.

  Here, PS3 may be mounted on the same device as GW2, or may be mounted on the same device as CS6. Further, CS6 may be mounted on the same device as GW2, or may be mounted on the same device as PS3. BS4 can be omitted. In this case, MS5 communicates with GW2 without going through BS4, and GW2 communicates with MS5 without going through BS4. Also, the interface between PS3 and CS6 can be omitted, in which case PS3 and CS6 do not communicate directly with each other.

  FIG. 2 shows the components of the communication system of the present embodiment one by one, but the number of these components is actually arbitrary. For example, the communication system of the present embodiment may include a plurality of MSs 5 communicating with one BS 4, may further include a plurality of BSs 4, and may further include a plurality of GWs 2.

  In the communication system of FIG. 2, the GW 2 performs the QoS packet or charging parameter, the weight, the integration threshold, and the UL packet received from the BS 4 and the DL packet received from the SS 1 according to the conditions for associating those values with the packet. Apply QoS and accounting parameters and weights. Here, QoS or charging parameters, weights, integration thresholds, and conditions for associating those values with packets may be notified from at least one of PS3 or CS6, or set in advance in GW2. It may be. The GW 2 forwards the received packet to the SS 1 if it is a UL packet, and forwards it to the BS 4 if it is a DL packet.

  In addition, when the weighted integration result (that is, at least one of the weighted packet count integration value or the weighted byte count integration value) reaches the integration threshold, the GW 2 determines the destination of the integration threshold and the integration threshold arrival message. Is transmitted to one or both of PS3 and CS6 in accordance with the condition relating to. Here, the condition for associating the integration threshold and the destination of the integration threshold arrival message may be notified from PS3 or CS6, or may be preset in GW2.

  PS3 is a QoS or charging parameter applied in GW2 in accordance with the accumulated threshold reaching message transmitted from GW2, the QoS or charging parameter determination condition set in PS3, or the status change message transmitted from CS6. Whether or not the weight or the integration threshold is changed (that is, whether or not to change) is determined. When it is determined that it is necessary to change the QoS or charging parameter, weight, or integration threshold applied in the GW 2, the PS 3 updates the parameter update message including the changed QoS or charging parameter, weight, or integration threshold. To GW2. If the QoS or charging status is changed, PS3 may send a status change message to CS6.

  CS6 follows the charging threshold reaching message transmitted from GW2, the charging parameter determination condition set in CS6, or the status change message transmitted from PS3, and charging parameters, weights or integration applied in GW2. It is determined whether or not the threshold is changed. When it is determined that it is necessary to change the charging parameter, weight, or integration threshold applied in GW2, CS6 transmits a parameter update message including the changed charging parameter, weight, or integration threshold to GW2. . When the charging status is changed, the CS 6 may transmit a status change message to the PS 3.

  In the present embodiment, when the GW 2 receives the UL packet or the DL packet, the GW 2 determines a QoS or charging parameter associated with the received packet based on the QoS or charging policy. Then, GW 2 determines a weight value associated with the received packet based on QoS or charging policy, performs one or both of weighted packet number accumulation and weighted byte number accumulation for the packet, and sets the accumulated value respectively. Is held in the counter corresponding to. When the integrated value reaches the threshold value associated with the counter, the GW 2 creates an integrated threshold value reaching message including information on the reached threshold value, and transmits the message to the destination associated with the threshold value. One or both of PS3 and CS6 that received the message transmitted by GW2 determines whether or not there is a parameter change related to QoS or charging based on threshold arrival information included in the received message and QoS or charging policy, and QoS Alternatively, if it is determined that it is necessary to change the parameter relating to charging, a message including QoS or charging parameter change information is created and transmitted to the destination associated with the change content. When GW2 receives a message from PS3 or CS6, it changes the QoS or charging parameter applied by GW2, and applies the changed QoS or charging parameter to the UL packet or DL packet received thereafter. To do.

<Apparatus configuration: GW2>
FIG. 3 shows a functional block of a configuration example of the GW 2 used in this embodiment. The GW 2 includes, for example, an SS interface unit 21, a BS interface unit 22, a PS interface unit 23, a CS interface unit 24, a memory unit 25, and a processing unit 26.

  The SS interface unit 21 is an interface with SS1. The GW 2 transmits and receives IP packets to and from the SS 1 using the SS interface unit 21.

  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 using the BS interface unit 22. In the case of a communication system in which the BS 4 is omitted, the GW 2 directly transmits and receives IP packets to and from the MS 5 without using the BS 4 by using the BS interface unit 22.

  The PS interface unit 23 is an interface with PS3. The GW 2 transmits and receives IP packets to and from the PS 3 using the PS interface unit 23. In the present embodiment, the GW 2 may use the PS interface unit 23 to transmit an accumulated threshold reaching message to the PS 3 and receive a response message from the PS 3.

  The CS interface unit 24 is an interface with CS6. Using the CS interface unit 24, the GW 2 transmits and receives IP packets to and from the CS 6. In the present embodiment, the GW 2 may use the CS interface unit 24 to transmit a cumulative threshold reaching message to the CS 6 or receive a response message from the CS 6.

  The memory unit 25 includes IP packets to be transmitted / received, addresses of SS1, BS4, PS3 and CS6 to be connected, QoS or accounting parameters applied to UL packets or DL packets received by each of the above-mentioned interface units, weights or integration thresholds and packets Information such as conditions for associating is stored and managed as necessary.

  The interface unit 21-24 in the GW 2 described above may be collectively referred to as an interface unit of the GW 2 or a network interface unit. These interface units are connected to the memory unit 25 and the processing unit 26 by an internal bus.

  The processing unit 26 is configured by, for example, a central processing unit (CPU). The processing unit 26 manages information held in the memory unit 25, and further executes various programs stored in the memory unit 25, thereby performing various processes such as IP packet construction or analysis. Packet transmission / reception processing, QoS or charging parameters applied to UL packets or DL packets received by the interface unit, association of weights or integration thresholds with packets, and weighted integration of the number of packets or bytes of received packets are performed.

  Note that PS3 and CS6, which are components other than GW2 constituting the communication system of the present embodiment, which will be described below in sequence, similarly include a network interface unit, a memory unit, and a processing unit therein (see FIG. (See FIG. 15 and FIG. 16). These processing units are also realized by the CPU, like the processing unit 26 of the GW 2, and execute and process function programs specific to the PS3, CS6, and the like. Further, although detailed description of the internal configuration is omitted, it goes without saying that SS1, BS4 and MS5 also have a configuration including a network interface unit, a memory unit, and a processing unit therein.

  FIG. 4 shows a block diagram of a configuration example of the memory unit of the GW 2 of this embodiment.

  For example, as illustrated in FIG. 4, the memory unit 25 holds tables 251 to 260.

  The table 251 relates the identifier and weight value of an accumulation group (refer to FIG. 5 to be described later) in the weighted accumulation for the received UL packet or DL packet to the communication of the packet (that is, the transmission source or transmission destination of the packet). ) Indicates information to be determined based on the MS 5 and the service to which the packet belongs. By using the table 251, information such as the MS5 identifier, service identifier, integration group identifier, byte count weight value, and packet count weight value can be managed. Details of the table 251 will be described later (see FIG. 5).

  The table 252 shows information for determining an integration threshold in weighted integration for the received UL packet or DL packet based on the integration group to which the packet belongs. By using the table 252, information such as an integration group identifier, a byte count integration threshold, and a packet count integration threshold can be managed. Details of the table 252 will be described later (see FIG. 6).

  The table 253 shows information on the integrated value for each integration group. By using the table 253, information such as an integration group identifier, a byte count integration value, and a packet count integration value can be managed. Details of the table 253 will be described later (see FIG. 7).

  The table 254 shows information for determining a weight value based on the time in weighted integration for the received UL packet or DL packet based on the MS 5 related to communication of the packet and the service to which the packet belongs. By using the table 254, it is possible to manage information such as the identifier of the MS 5, the identifier of the service, the byte number weight value and its switching time, and the packet number weight value and its switching time. Details of the table 254 will be described later (see FIG. 8).

  The table 255 shows information for determining a weight value based on the time in weighted integration for the received UL packet or DL packet based on the integration group to which the packet belongs. By using the table 255, it is possible to manage information such as the identifier of the accumulation group, the byte number weight value and its switching time, the packet number weight value and its switching time, and the like. Details of the table 255 will be described later (see FIG. 9).

  The table 256 shows information for determining a weight value based on the congestion degree of the BS 4 in the weighted integration for the received UL packet or DL packet based on the BS 4 related to the communication of the packet. By using the table 256, it is possible to manage information such as the identifier of the BS 4, the threshold of the ratio of the cell throughput of the BS 4 and the number of MSs 5 connected to the BS 4, the byte number weight value, the packet number weight value, and the like. Details of the table 256 will be described later (see FIG. 10).

  The table 257 shows information on the MS 5 connected to each BS 4. By using the table 257, information such as the identifier of the BS 4 and the identifier of the MS 5 connected to each BS 4 can be managed. Details of the table 257 will be described later (see FIG. 11).

  The table 258 shows information for determining a weight value based on the congestion degree of the BS 4 in the weighted integration for the received UL packet or DL packet based on the BS 4 related to the communication of the packet. By using the table 258, it is possible to manage information such as the identifier of the BS 4, the threshold of the ratio of the cell throughput of the BS 4 and the total transmission throughput of the MS 5 connected to the BS 4, the byte number weight value, the packet number weight value, and the like. it can. Details of the table 258 will be described later (see FIG. 12).

  A table 259 indicates whether or not there is a DL packet transmission failure notification. By using the table 259, it is possible to manage information such as packet identifiers, weighted byte counts, weighted packet counts, BS4 identifiers related to communication of each packet, and timeout times. Details of the table 259 will be described later (see FIG. 13).

  The table 260 shows the weight value and weight value determination priority of each BS4. By using the table 260, information such as the identifier of the BS 4, the weight value determination priority, the byte number weight value, and the packet number weight value can be managed. Details of the table 260 will be described later (see FIG. 14).

  FIG. 5 shows a table 251 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. The table 251 shows information for determining the identifier and weight value of the integration group in the weighted integration for the received UL packet or DL packet based on the MS 5 related to the communication of the packet and the service to which the packet belongs.

  The table 251 includes, for example, an MS5 identifier (MS ID) 501, a service identifier (Service ID) 502, an integration group identifier (Group ID) 503, a byte count weight value (Weight (for bytes)), and a packet count weight. The value (Weight (for packets)) is stored. The byte count weight value includes a UL packet byte count weight value 504 and a DL packet byte count weight value 506. The packet number weight value includes a packet number weight value 505 for the UL packet and a packet number weight value 507 for the DL packet.

  The MS5 identifier 501 is a parameter for identifying each MS5. The MS5 involved in communication of the UL packet or DL packet received by the GW 2 (that is, the MS5 that is the source of the UL packet or the MS5 that is the destination of the DL packet), Used to correlate integration groups or weight values. For example, when all the MSs 5 are associated with the same integration group or the same weight value, the identifier 501 of the MS 5 may be omitted.

  The service identifier 502 is a parameter for identifying the service to which the UL packet or DL packet received by the GW 2 belongs, and is used to associate the service with the integration group or the weight value. For example, when all the services are associated with the same integration group or the same weight value, the service identifier 502 may be omitted.

  The integration group identifier 503 is a parameter indicating to which integration group counter the number of UL packets or DL packets received by the GW 2 or the number of bytes of each packet is integrated.

  Here, the accumulation group will be described. In this embodiment, the number of packets passing through the GW 2 or the number of packet bytes is integrated in order to control QoS or billing. An accumulation group is a concept that defines a range in which the number of packets or bytes can be accumulated using one counter.

  For example, when the number of packets or the number of bytes is accumulated for the purpose of charging for each user, each MS 5 used by each different user is associated with a different accumulation group. When a single user uses a plurality of services using one MS 5, each service may be associated with a different accumulation group, but a plurality of services may be associated with one accumulation group. For example, if a user uses a plurality of services provided by one service provider and the parameters (billing parameters) related to the charging of the services are the same, the services are associated with one integration group. Can do.

  Here, the charging parameter is a parameter for calculating the charging amount based on the integrated value, for example. Specifically, for example, when pay-per-use is applied, if a charge amount (that is, a charge ratio) per number of transmitted packets or bytes is determined, that ratio is a charge parameter. If the threshold value of the integrated value of the number of packets or bytes (that is, the integrated threshold value in FIG. 6) and the charge amount when the integrated value exceeds the threshold value are determined, the threshold value and the charge amount Is a charging parameter. For example, when a service provider provides a plurality of services with common charging parameters to one user, the integrated value of the number of packets or the number of bytes related to the plurality of services is integrated by one counter, and the integrated value The amount of money can be calculated based on the billing parameter, and the amount can be billed to the user collectively as usage fees for the plurality of services.

  Alternatively, when it is desired to control charging for the purpose of limiting the bandwidth used for each MS 5, all the services used by one MS 5 may be associated with one integration group. In this case, for example, a charging ratio with respect to the integrated value and a threshold value of the integrated value are set as the charging parameters. When the integrated value exceeds the threshold value, the charging ratio is increased (that is, the charge is high). May be changed).

  The basic concept of the accumulation group and parameters as described above can also be applied to the accumulation of the number of packets or the number of bytes for QoS control. For example, in order to reduce the occupation of the bandwidth by a specific user, a specific MS5, or a specific service, when the integrated value for the user, MS5, or service exceeds a predetermined threshold, the bandwidth for the user, MS5, or service Controls such as changing the limit value in a direction to reduce the use band, or lowering the transmission priority of the packet related to the user, the MS 5 or the service may be executed. In this case, the QoS-related parameters (QoS parameters) are a threshold value and a bandwidth limit value associated therewith or a packet transmission priority.

  The parameters associated with the received packet can be specified based on the transmission destination of the packet, the transmission source of the packet, the service to which the packet belongs, or the like. Normally, the association between packets and QoS parameters is managed by PS3, and the association between packets and charging parameters is managed by CS6. PS3 may further manage the association between packets and charging parameters.

  Note that the parameters as described above are examples, and in this embodiment, the number of packets is used for control or management of communication of packets or data included in the packets (an example of which is the QoS or charging control). Or it can be applied to any kind of parameter associated with the number of bytes in the packet.

  Conventionally, unless the parameters related to QoS or charging associated with received packets are common, the number of those packets or the number of those bytes cannot be accumulated by one counter. On the other hand, according to the present invention, in a specific case, the number of packets associated with different parameters or the number of bytes thereof can be integrated by one counter. An example of the weight value and weighted integration based thereon will be described later.

  The number-of-bytes weight value (that is, the number-of-byte weight value 504 of the UL packet and the number-of-byte weight value 506 of the DL packet) is a weight based on the MS 5 and the service when the number of bytes of the UL packet or DL packet received by the GW 2 is weighted. This is a parameter indicating the value. If the byte number weight value is not registered, it may be handled in the same manner as the case of weight value = 1, or it may be determined that the weighted integration relating to the number of bytes is not performed (in other words, weight value = 0). May be handled in the same way as However, it is necessary to determine in advance which treatment is applied. Separate values may be set for the byte weight value 504 applied to the UL packet and the byte weight value 506 applied to the DL packet, or the same weight value may be applied to the UL packet and the DL packet. May be. In the latter case, only one of the byte number weight value 504 of the UL packet and the byte number weight value 506 of the DL packet may be set, and the value may be applied to the other.

  The packet number weight values (that is, the packet number weight value 505 of the UL packet and the packet number weight value 507 of the DL packet) are weights based on the MS 5 and the service when the number of UL packets or DL packets received by the GW 2 is weighted and integrated. This is a parameter indicating the value. When the packet number weight value is not registered, it may be handled in the same manner as when the weight value = 1, or it may be determined not to perform weighted integration regarding the number of packets (in other words, weight value = 0). May be handled in the same way as However, it is necessary to determine in advance which treatment is applied. Separate values may be set for the packet number weight value 505 applied to the UL packet and the packet number weight value 507 applied to the DL packet, or the same weight value is applied to the UL packet and the DL packet. May be. In the latter case, only one of the packet number weight value 505 of the UL packet and the packet number weight value 507 of the DL packet may be set, and that value may be applied to the other.

  In the example of FIG. 5, the identifier 502 is the identifier 502 among a plurality of services used by the MS 5 whose identifier 501 is “MS # 1” (hereinafter also simply referred to as “MS # 1”. The same applies to other identifiers 501). A service that is “Service # 1” and a service whose identifier 502 is “Service # 3” (hereinafter also simply referred to as “Service # 1” and “Service # 3”, respectively, and the same applies to other identifiers 502). , Associated with the accumulation group identified by the identifier 503 “A” (hereinafter also simply referred to as “accumulation group A”. The same applies to the other identifiers 503). Further, the pair of MS # 1 and Service # 1 is associated with the value “0.8” of the byte number weight value 504 of the UL packet, the pair of MS # 1 and Service # 3, and the byte of the UL packet The value “1.5” of the number weight value 504 is associated.

  In this case, for example, the number of bytes of the UL packet belonging to Service # 3 transmitted from MS # 1 is multiplied by the weight “0.8” and the number of bytes of the UL packet belonging to Service # 1 transmitted from MS # 1. Is multiplied by a weight of “1.5” and these values are accumulated by the same counter. Thus, for example, when the integrated value is used for charging, it is possible to perform charging that accurately reflects the price difference between the two services. Further, when the integrated value threshold is provided, the integrated value is integrated. The timing at which the value exceeds the threshold can be accurately specified. Note that the above examples of weight values mean that Service # 3 is more expensive than Service # 1 when they are used for billing.

  In this way, by weighting and integrating the number of packets or the number of bytes, there may be a case where the difference in parameters can be absorbed without increasing the number of counters used. When the value accumulated by the counter exceeds the threshold value, it is necessary to send a message for each counter, so if the number of counters increases, not only the memory area for the counter is required, but also the message The amount of processing also increases, which may reduce packet transfer performance. In this embodiment, since the counters can be integrated by weighted integration as described above, processing such as parameter change is performed at an appropriate timing when the integrated value exceeds the threshold while suppressing the influence on the packet transfer performance. It can be carried out.

  In the example of FIG. 5, in addition to the set of MS # 1 and Service # 1, and the set of MS # 1 and Service # 3, the set of MS # 1 and Service # 1 is also associated with the accumulation group A. ing. In such a case, a different counter may be used for each MS 5 or the same counter may be used for a plurality of MSs 5. For example, when it is desired to control QoS or charging for each terminal, a different counter is used for each MS 5. On the other hand, for example, when MS # 1 and MS # 2 are used by the same user when QoS or charging for each user is desired to be controlled, the same counter is used for MS # 1 and MS # 2. Alternatively, for example, the same counter can be used for a plurality of MSs 5 when it is desired to control QoS or billing related to services to which so-called family discounts are applied or services for companies.

  The GW 2 can specify the identifier of the MS 5 of the transmission source (or transmission destination) of the packet and the identifier of the service to which the packet belongs by referring to the header of the received packet. For this reason, the GW 2 refers to the header of the packet and the identifier 501 of the MS 5 to the identifier 503 of the integration group in the table 251 to thereby calculate the integration group corresponding to the received packet (in other words, the counter corresponding to the received packet). ) Can be specified. Even in the case where the memory unit 25 does not hold the table 251 (for example, holds the table 254 instead of the table 251), the memory unit 25 does not have the MS5 identifier 501 to the integration group identifier 503 in the table 251. It is necessary to hold information that associates a packet with a counter that accumulates the number of packets or bytes of the packet.

  Note that the initial value of the information included in the table 251 may be set in GW2, or may be set by a message received by GW2 from PS3, CS6, or BS4. Also, these pieces of information can be updated by a message received by GW2 from PS3, CS6 or BS4.

  FIG. 6 shows a table 252 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. The table 252 shows information for determining an integration threshold in weighted integration for the received UL packet or DL packet from the integration group to which the packet belongs.

  The table 252 stores, for example, an integration group identifier (Group ID) 601, a byte count integration threshold (Threshold (for bytes)), and a packet count integration threshold (Threshold (for packets)). The byte count integration threshold includes a byte count integration threshold 602 of the UL packet and a byte count integration threshold 604 of the DL packet. The packet number integration threshold includes a packet number integration threshold 603 for UL packets and a packet number integration threshold 605 for DL packets.

  The integration group identifier 601 is a parameter indicating to which integration group counter the number of UL packets or DL packets received by the GW 2 or the number of bytes of each packet is integrated.

  The byte count integration threshold (that is, the byte count integration threshold 602 of the UL packet and the byte count integration threshold 604 of the DL packet) is an integration threshold in each integration group when the number of bytes of the UL packet or DL packet received by the GW 2 is weighted. It is a parameter which shows. Different values may be set for the byte count threshold 602 applied to the UL packet and the byte count threshold 604 applied to the DL packet, or the same byte count threshold is applied to the UL packet and DL packet. May be. In the latter case, only one of the UL packet byte count threshold value 602 and the DL packet byte count threshold value 604 may be set, and the value may be sent to the other.

  The packet number integration threshold (that is, the packet number integration threshold 603 of the UL packet and the packet number integration threshold 605 of the DL packet) is an integration threshold in each integration group when weighted integration of the number of UL packets or DL packets received by the GW 2 is performed. It is a parameter which shows. Different values may be set for the packet count integration threshold 603 applied to the UL packet and the packet count integration threshold 605 applied to the DL packet, or the same packet count integration threshold is applied to the UL packet and the DL packet. May be. In the latter case, only one of the UL packet count threshold 603 or the DL packet count threshold 605 may be set, and that value may be applied to the other.

  Note that the initial value of the information included in the table 252 may be set in GW2, or may be set by a message received by GW2 from PS3, CS6, or BS4. Also, these pieces of information can be updated by a message received by GW2 from PS3, CS6 or BS4.

  FIG. 7 shows a table 253 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. The table 253 shows information on the integrated value for each integration group.

  The table 253 stores, for example, an integration group identifier (Group ID) 701, a byte count integration value (Integration (Mbytes)), and a packet count integration value (Integration (kpackets)). The byte count integrated value includes a UL packet byte count integrated value 702 and a DL packet byte count integrated value 704. The packet number integrated value includes a UL packet number integrated value 703 and a DL packet number integrated value 705.

  The accumulation group identifier 701 is a parameter indicating the number of UL packets or DL packets received by the GW 2 or the number of bytes of each packet, and which accumulation group counter is accumulated.

  The byte count integrated value (that is, the UL packet byte count integrated value 702 and the DL packet byte count integrated value 704) is an integrated value in each integration group when the number of bytes of the UL packet or DL packet received by the GW 2 is weighted integrated. (Ie, the number of bytes weighted and accumulated by the counter of each integration group). The weighted integration may be performed without distinguishing whether the packet received by GW2 is a UL packet or a DL packet. In this case, the weighted integration result of the number of bytes of the received packet corresponding to each integration group Is stored in the table 253.

  The packet number integrated value (that is, the packet number integrated value 703 of the UL packet and the packet number integrated value 705 of the DL packet) is an integrated value in each integration group when the number of UL packets or DL packets received by the GW 2 is weighted integrated. This is a parameter indicating the number of packets weighted and accumulated by the counter of each accumulation group. Note that the weighted integration may be performed without distinguishing whether the packet received by the GW 2 is a UL packet or a DL packet, in which case the weighted integration result of the number of received packets corresponding to each integration group is indicated. The parameters are stored in table 253.

  FIG. 8 shows a table 254 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. The table 254 shows information for determining the weight value based on the time in the weighted integration for the received UL packet or DL packet from the MS 5 related to the communication of the packet and the service to which the packet belongs.

  The table 254 includes, for example, an MS5 identifier (MS ID) 801, a service identifier (Service ID) 802, a UL packet byte weight value and its switching time (Weight Timeline (for bytes)) 803, and a DL packet byte. The number weight value and its switching time 805, the packet number weight value of the UL packet and its switching time (Weight Timeline (for packets)) 804, the packet number weight value of the DL packet and its switching time 806 are stored.

  The identifier 801 of the MS 5 is a parameter for identifying each MS 5 and is used for associating the MS 5 related to the communication of the UL packet or the DL packet received by the GW 2 with a weight value based on time. Note that when the weight value based on the corresponding time is commonly applied to all the MSs 5, the identifier 801 of the MS 5 may be omitted.

  The service identifier 802 is a parameter for associating the service to which the UL packet or DL packet received by the GW 2 belongs with a weight value based on time. When a weight value based on the corresponding time is applied regardless of the service to which the packet belongs, the service identifier 802 may be omitted.

  The byte number weight value of the UL packet and its switching time 803 are parameters indicating the weight value based on the time when the number of bytes of the UL packet received by the GW 2 is weighted and its switching time. The DL packet byte count weight value and its switching time 805 are parameters indicating the weight value based on the time when the number of DL packet bytes received by the GW 2 is weighted and the switching time thereof.

  The packet number weight value of UL packet and its switching time 804 are parameters indicating the weight value based on the time when the number of UL packets received by the GW 2 is weighted and the switching time thereof. The packet number weight value of the DL packet and its switching time 806 are parameters indicating the weight value based on the time when the number of DL packets received by the GW 2 is weighted and integrated and the switching time thereof.

  For example, if “18: 00 = 0.8, 23: 00 = 0.5” is set in the above weight values and the switching times 803 to 806, the time period of 18:00 to 23:00 It represents that “0.8” is applied as the weight value based on time, and “0.5” is applied as the weight value based on time in the time zone from 23:00 to 18:00 on the next day.

  As in the case of the table 251, when the registration of the weight value based on the time is omitted in the table 254, it may be handled in the same manner as the case of the weight value = 1, and it is determined that the weighting integration regarding the number of bytes is not performed. May be. In the table 254, as illustrated in FIG. 8, different values may be set for the weight value applied to the UL packet and the weight value applied to the DL packet. The same weight value may be applied to. In the latter case, only one of the weight value applied to the UL packet or the weight value applied to the DL packet may be set, and the weight value may be applied to the other.

  The initial value of the information included in the table 254 may be set in GW2, or may be set by a message received by GW2 from PS3, CS6, or BS4. Also, these pieces of information can be updated by a message received by GW2 from PS3, CS6 or BS4.

  FIG. 9 shows a table 255 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. The table 255 shows information for determining a weight value based on the time in weighted integration for the received UL packet or DL packet from the integration group to which the packet belongs.

  The table 255 includes, for example, an integration group identifier (Group ID) 901, a byte count weight value for each UL packet integration group and its switching time (Group Weight Timeline (for bytes)) 902, and an DL group integration group unit. Byte number weight value and its switching time 904, UL packet packet number weight value and its switching time (Group Weight Timeline (for packets)) 903, DL packet packet group weight value and its The switching time 905 is stored.

  The integration group identifier 901 is a parameter indicating to which integration group counter the UL packet or DL packet received by the GW 2 is integrated.

  The number-of-bytes weight value and the switching time 902 of the UL packet accumulation group are parameters indicating the weight value based on the time when the number of bytes of the UL packet received by the GW 2 is weighted and the switching time. The DL packet integration group unit byte weight value and its switching time 904 are parameters indicating the weight value based on the time when the DL number of DL packets received by the GW 2 is integrated and the switching time thereof.

  The number-of-packets weight value of the UL packet integration group and its switching time 903 are parameters indicating the weight value based on the time when the number of UL packets received by the GW 2 is weighted and the switching time thereof. The packet number weight value of DL packet integration group unit and its switching time 905 are parameters indicating the weight value based on the time when weighted integration of the number of DL packets received by the GW 2 and its switching time.

  For example, when “18: 00 = 1.0, 23: 00 = 2.0” is set in the weight value and the switching times 903 to 905, the time period of 18:00 to 23:00 “1.0” is applied as the weight value based on time, and “2.0” is applied as the weight value based on time in the time zone from 23:00 to 18:00 on the next day.

  As in the case of the table 251, when the registration of the weight value based on the time is omitted in the table 255, it may be handled in the same manner as the case of the weight value = 1, and it is determined that the weighting integration regarding the number of bytes is not performed. May be. In the table 255, as illustrated in FIG. 9, different values may be set for the weight value applied to the UL packet and the weight value applied to the DL packet. The same weight value may be applied to. In the latter case, only one of the weight value applied to the UL packet or the weight value applied to the DL packet may be set, and the weight value may be applied to the other.

  The initial value of information included in the table 255 may be set in GW2, or may be set by a message received by GW2 from PS3, CS6, or BS4. Also, these pieces of information can be updated by a message received by GW2 from PS3, CS6 or BS4.

  As shown in FIG. 8 or FIG. 9, by applying different weight values according to time zones, it is possible to perform optimal QoS or charging control for each time zone. For example, by setting the weight value for the time zone when the line is congested higher than the weight value for the time period when the line is free, the service charge for the time period when the line is congested will It is possible to set it higher, or to set the band limit of the time zone when the line is congested more severely than other time zones. As a result, it is possible to distribute traffic in a time zone where the line is congested to other time zones. As a result, a decrease in communication quality due to congestion is improved.

  FIG. 10 shows a table 256 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. The table 256 shows information for determining a weight value based on the degree of congestion of the BS 4 in the weighted integration for the received UL packet or DL packet from the BS 4 related to communication of the packet.

  The table 256 includes, for example, an identifier (BS ID) 1001 of BS4, a threshold value (Threshold Ratio (Num / Mbps)) 1002 of a ratio between the cell throughput of BS4 and the number of MSs 5 connected to the BS4, and weight of the number of bytes. A value (Weight (for bytes)) and a packet number weight value (Weight (for packets)) are stored. The byte number weight value includes a byte number weight value 1003 of the UL packet and a byte number weight value 1005 of the DL packet. The packet number weight value includes a packet number weight value 1004 of the UL packet and a packet number weight value 1006 of the DL packet.

  The identifier 1001 of the BS 4 is a parameter for identifying each BS 4 and is related to the communication of the UL packet or the DL packet received by the GW 2 (that is, the BS 4 on the communication path of the UL packet or the DL packet, more specifically, , The transmission source BS4 of the UL packet or the transmission destination BS4 of the DL packet) and the information such as the weight value are associated with each other.

  The threshold 1002 of the ratio between the cell throughput of the BS 4 and the number of MSs 5 connected to the BS 4 is a parameter for associating the BS 4 related to the communication of the UL packet or DL packet received by the GW 2 with the weight value. The cell throughput of the BS 4 may be acquired by the BS 4 at a periodic acquisition opportunity by a timer, or it is detected that the cell throughput of the BS 4 has exceeded a preset upper threshold or less than the lower threshold. It may be acquired by the BS 4 in response to this. In addition, the number of MSs 5 connected to the BS 4 may be acquired by the BS 4 at a periodic acquisition opportunity by a timer, or the number of MSs 5 connected to the BS 4 exceeds a preset upper threshold. Or it may be acquired by the BS 4 when triggered by the fact that it is less than the lower limit threshold.

  The cell throughput of the acquired BS 4 and the number of MSs 5 connected to the BS 4 may be notified to the GW 2 by a message transmitted from the BS 4 to the GW 2 or a message from a server that acquires statistical items. The processing unit 26 of the GW 2 calculates the ratio between the acquired cell throughput of the BS 4 and the number of MSs 5 connected to the BS 4, and when it is determined that this value is different from the value 1002 set in the table 256, The value 1002 set in the table 256 may be updated to the calculated value.

  The number-of-byte weight values (that is, the number-of-byte weight value 1003 of the UL packet and the number-of-byte weight value 1005 of the DL packet) are based on the degree of congestion of the BS 4 when the number of bytes of the UL packet or DL packet received by the GW 2 is weighted. It is a parameter indicating a weight value.

  The packet number weight values (that is, the packet number weight value 1004 of the UL packet and the packet number weight value 1006 of the DL packet) are based on the congestion degree of the BS 4 when the number of UL packets or DL packets received by the GW 2 is weighted and integrated. It is a parameter indicating a weight value.

  In the example of FIG. 10, the threshold number 1002 “0” and “5” of the ratio between the cell throughput of BS # 1 and the number of MSs 5 connected to BS # 1 are set to the UL packet byte count weight value 1003 “ “0.8” and “1.2” are associated. This is because the weight value “0.8” is applied when the ratio between the cell throughput of BS # 1 and the number of MSs 5 connected to BS # 1 is “0” or more and less than “5”. This means that the weight value “1.2” is applied when the ratio between the cell throughput of the mobile station and the number of MSs 5 connected to BS # 1 is “5” or more and less than “10”. The larger the ratio between the cell throughput of the BS 4 and the number of MSs 5 connected to the BS 4, the higher the congestion level of the BS 4, and in the example of FIG. 10, the higher the congestion level of the BS 4, the higher the associated weight. The value increases.

  As in the case of the table 251, if the registration of the weight value based on the degree of congestion of the BS 4 is omitted in the table 256, it may be handled in the same manner as in the case of the weight value = 1, and the weighting integration regarding the number of packets is performed. It may be determined that there is not. In the table 256, as illustrated in FIG. 10, different values may be set for the weight value applied to the UL packet and the weight value applied to the DL packet. The same value may be applied to. In the latter case, only one of the weight value applied to the UL packet or the weight value applied to the DL packet may be set, and the weight value may be applied to the other.

  The initial value of the information included in the table 256 may be set in GW2, or may be set by a message received by GW2 from PS3, CS6, or BS4. Also, these pieces of information can be updated by a message received by GW2 from PS3, CS6 or BS4.

  FIG. 11 shows a table 257 indicating information of the MS 5 connected to the BS 4 as an example of information held in the memory unit 25 of the GW 2 of the present embodiment. The table 257 stores, for example, an identifier (BS ID) 1101 of BS4 and an identifier (MS ID) 1102 of MS5.

  The BS4 identifier 1101 is a parameter for identifying the BS4 used by the MS5 for communication.

  The identifier 1102 of the MS 5 is a parameter for identifying the MS 5 that uses each BS 4 for communication. When one MS 5 establishes connections with a plurality of BSs 4, the same MS 5 identifiers may be registered for different BSs 4, respectively.

  These pieces of information can be updated by a message received by GW2 from PS3, CS6 or BS4.

  FIG. 12 shows a table 258 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. The table 258 shows information for determining a weight value based on the degree of congestion of the BS 4 in the weighted integration for the received UL packet or DL packet from the BS 4 related to the communication of the packet.

  The table 258 includes, for example, an identifier (BS ID) 1201 of BS4, a threshold of a ratio of the cell throughput of BS4 and the total transmission throughput of UL packets of MS5 connected to the BS4 (Threshold Ratio (kbps / kbps)). 1202, UL packet weight value (Weight (for bytes)) 1203, UL packet number weight value (Weight (for packets)) 1204, cell throughput of BS4 and DL packet of MS5 connected to BS4 The threshold 1205 of the ratio with respect to the total transmission throughput, the byte number weight value 1206 of the UL packet, and the packet number weight value 1207 of the UL packet are stored.

  The identifier 1201 of the BS 4 is a parameter for identifying each BS 4 and corresponds to the BS 4 related to the communication of the UL packet or the DL packet received by the GW 2 (that is, the BS 4 that is the transmission source of the UL packet or the BS 4 that is the transmission destination of the DL packet). Used to link information such as weight values.

  The threshold 1202 of the ratio between the cell throughput of the BS 4 and the total transmission throughput of the UL packet of the MS 5 connected to the BS 4 is a parameter for associating the BS 4 to which the UL packet received by the GW 2 belongs and the weight value. The threshold 1205 of the ratio between the cell throughput of the BS 4 and the total transmission throughput of the DL packets of the MS 5 connected to the BS 4 is a parameter for associating the BS 4 to which the DL packet received by the GW 2 belongs and the weight value.

  The cell throughput of the BS 4 may be acquired by the BS 4 at a periodic acquisition opportunity by a timer, or it is detected that the cell throughput of the BS 4 has exceeded a preset upper threshold or less than the lower threshold. It may be acquired by the BS 4 when triggered by this. Further, the total transmission throughput of the MS 5 connected to the BS 4 may be acquired by the BS 4 at a periodic acquisition timing by a timer, or the total transmission throughput of the MS 5 connected to the BS 4 is a preset upper limit. It may be acquired by the BS 4 when triggered by the fact that the threshold is exceeded or less than the lower threshold.

  The cell throughput of the acquired BS 4 and the total transmission throughput of the MS 5 connected to the BS 4 may be notified to the GW 2 by a message transmitted from the BS 4 to the GW 2 or a message from a server that acquires statistical items. . The processing unit 26 of the GW 2 calculates the ratio between the acquired cell throughput of the BS 4 and the total transmission throughput of the MS 5 connected to the BS 4, and determines that this value is different from the value 1202 or 1205 set in the table 258. If it is, the value 1202 or 1205 set in the table 258 may be updated to the calculated value.

  The number-of-byte weight values (that is, the number-of-byte weight value 1203 of the UL packet and the number-of-byte weight value 1206 of the DL packet) are based on the degree of congestion of the BS 4 when the number of bytes of the UL packet or DL packet received by the GW 2 is weighted. It is a parameter indicating a weight value.

  The packet number weight value (that is, the packet number weight value 1204 of the UL packet and the packet number weight value 1207 of the DL packet) is based on the congestion degree of the BS 4 when the number of UL packets or DL packets received by the GW 2 is weighted and integrated. It is a parameter indicating a weight value.

  In the example of FIG. 11, the threshold packets 1202 “0” and “0.5” of the ratio between the cell throughput of BS # 1 and the total transmission throughput of the UL packet of MS5 connected to BS # 1 are respectively set to UL packets. Byte number weight values 1203 “0.8” and “1.2” are associated with each other. This is a weight value “0.8” when the ratio between the cell throughput of BS # 1 and the total transmission throughput of the UL packet of MS5 connected to BS # 1 is “0” or more and less than “0.5”. Is applied and the weight value “1” is obtained when the ratio between the cell throughput of BS # 1 and the total transmission throughput of the UL packet of MS5 connected to BS # 1 is “0.5” or more and less than “0.8”. .2 "applies. The larger the ratio of the cell throughput of the BS 4 and the total transmission throughput of the MS 5 connected to the BS 4 is, the higher the congestion degree of the BS 4 is. In the example of FIG. The weight value to be increased.

  As in the case of the table 251, when the registration of the weight value based on the degree of congestion of the BS 4 is omitted in the table 258, it may be handled in the same manner as in the case of the weight value = 1, and the weighting integration regarding the number of packets is performed. It may be determined that there is not. Also, as shown in FIG. 12, different values may be set in the table 258 for the weight value applied to the UL packet and the weight value applied to the DL packet. The same value may be applied to. In the latter case, only one of the weight value applied to the UL packet or the weight value applied to the DL packet may be set, and the weight value may be applied to the other.

  The initial value of the information included in the table 258 may be set in GW2, or may be set by a message received by GW2 from PS3, CS6, or BS4. Also, these pieces of information can be updated by a message received by GW2 from PS3, CS6 or BS4.

  As shown in FIG. 10 or FIG. 12, traffic can be distributed to a plurality of BSs 4 by applying different weight values according to the degree of congestion of the BSs 4. Specifically, by setting the weight value related to BS4 with a high degree of congestion higher than the weight value related to BS4 with a low degree of congestion, the charge of the service using the congested BS4 can be set to another BS4. It is possible to set higher than that to be used, or to set the bandwidth limit of the communication path via the congested BS 4 more strictly than those via other BS 4. As a result, the deterioration of communication quality due to the congestion of the BS 4 is improved.

  Note that the ratio of the cell throughput of the BS 4 shown in FIG. 10 to the number of MSs 5 connected to the BS 4 and the total transmission throughput of the cell throughput of the BS 4 shown in FIG. 12 and the UL packets of the MS 5 connected to the BS 4 are shown. These ratios are all indices indicating the degree of congestion of BS4, and the larger the value, the higher the degree of congestion. However, in the example of FIG. 10, the large number of MSs 5 connected to the BS 4 does not necessarily mean that the BS 4 is congested. However, if the number of MSs 5 connected to the BS 4 is large, the ratio of the cell throughput of the BS 4 to the number of MSs 5 connected to the BS 4 is calculated based on the prediction that the BS 4 is likely to be congested. It can be used as an indicator of the degree of congestion of BS4. On the other hand, the total transmission throughput (FIG. 11) regarding the UL packet of the MS 5 connected to the BS 4 shows the past congestion record. An appropriate index of congestion can be used according to the purpose of QoS or billing, and an index other than the above indicating the degree of congestion of the BS 4 may be used.

  FIG. 13 shows a table 259 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. The table 259 shows information for determining a weight value based on the success or failure of transmission of the DL packet to the MS 5 in the weighted integration for the DL packet transmitted to the plurality of BSs 4. The table 259 includes, for example, a packet identifier (Packet ID) 1301, a packet weighted byte count (Weighted Bytes) 1302, a packet weighted packet count (Weighted Packets) 1303, a BS4 identifier (BS ID) 1304-1306, and A packet information holding timeout time (Timeout) 1307 is stored.

  The packet identifier 1301 is an identifier of a DL packet transmitted from the GW 2 to the BS 4. As the packet identifier 1301, for example, information originally included in the packet such as a UDP header sequence number set by the GW 2 may be used, or a field or header for setting the identifier is newly added by the GW 2. Also good.

  The weighted byte number 1302 of the packet is a value calculated by the GW2 by weighted integration of the number of bytes for the DL packet. When the number of bytes of the DL packet is not included in the weighted integration target, the number of weighted bytes 1302 of the packet may be omitted.

  The packet weight packet number 1303 is a value calculated by the GW 2 by weighted integration of the packet number for the DL packet. When the number of DL packets is not included in the weighted accumulation target, the number of weighted packets 1303 of packets may be omitted.

  The BS4 identifiers 1304 to 1306 are identifiers of the destination BS4 to which the GW 2 has transmitted the DL packet. Furthermore, the table 259 can record information indicating whether or not a message for notifying the discard of the DL packet has been received from each BS 4 of the transmission destination corresponding to the identifiers 1304 to 1306 of the BS 4. In the example of FIG. 13, “x” recorded corresponding to the identifiers 1304 to 1306 of the BS 4 indicates that a message notifying the discard of the DL packet has been received from the corresponding BS 4.

  For example, in the example of FIG. 13, regarding a DL packet whose packet identifier 1301 is “11” (hereinafter referred to as “DL packet # 11”), BS4 whose identifier is “BS4 # 2” (hereinafter “BS4 #”). 2 ”and the other BS4 are described in the same rule), and the message indicating that the DL packet # 11 has been discarded is received from the BS4 # 3. In this case, communication of DL packet # 11 transmitted to BS4 # 2 and DL packet # 11 transmitted to BS4 # 3 failed (that is, those DL packets # 11 do not arrive at the destination MS5). It is determined.

  On the other hand, in the example of FIG. 13, the GW 2 has not received a message indicating that the DL packet # 11 has been discarded from the BS 4 # 1. When the GW 2 does not receive the message by the time-out time (12:00:22 in the example of FIG. 13), the communication of the DL packet # 11 transmitted to the BS 4 # 1 has succeeded (that is, the DL packet # 11 Has arrived at the destination MS5 via BS4 # 1).

  In the above example, DL packet # 11 to be transmitted to the same MS 5 is transmitted to three BSs 4 (ie, BS 4 # 1 to # 3). That is, the three DL packets # 11 transmitted to the three BSs 4 correspond to the duplication of each other, and their contents are the same. Such transmission of a plurality of packets having the same content to a plurality of BSs 4 may be performed during a handover sequence between the plurality of BSs 4, or for improving communication reliability by making communication paths redundant. It may be done. Actually, it is sufficient that one of the plurality of packets having the same contents arrives at the transmission destination MS 5.

  Although FIG. 13 shows an example in which the combination of the transmission destination BS4 of all packets is the same, the combination of the transmission destination BS4 may be different for each packet.

  The packet information retention timeout time 1307 is a time at which the GW 2 may delete information related to the DL packet from the table 259. As the time-out time 1307 for holding the packet information, for example, the standard time at the place where the GW 2 is installed or the standard time set by the operator managing the GW 2 may be used, or the number of seconds elapsed from a certain reference time. You may use what digitized.

  Information included in table 259 can be updated by transmission of DL packets to a plurality of BSs 4 in GW 2 and messages received from PS 3, CS 6, or BS 4.

  FIG. 14 shows a table 260 as an example of information held in the memory unit 25 of the GW 2 of this embodiment. Table 260 shows information for determining an overall weight value related to BS4 in weighted accumulation for DL packets transmitted to a plurality of BS4s. The table 260 includes, for example, an identifier (BS ID) 1401 of BS4, a weight priority (Weight Priority) 1402 of BS4, a weight weight value (Weight (for bytes)) 1403, and a packet weight value (Weight (for packets). )) 1404 is stored.

  The identifier 1401 of the BS 4 is a parameter for identifying each BS 4 and is used to associate the BS 4 related to the communication of the DL packet transmitted by the GW 2 with information such as a weight value.

  The weight priority 1402 of BS4 is a parameter for determining a weight value corresponding to BS4 related to communication of the DL packet transmitted by GW2. When the GW 2 transmits DL packets to a plurality of BSs 4, for example, the weight value associated with the BS 4 having the smallest weight priority value among the BSs 4 that have successfully transmitted the DL packet is set as the weight value corresponding to the DL packet. You may decide.

  The byte count weight value 1403 is a parameter indicating a weight value based on the congestion degree of the BS 4 when the number of bytes of the DL packet transmitted by the GW 2 is weighted and integrated. As in the case of the table 251, when the byte number weight value 1403 is omitted in the table 260, it may be handled in the same manner as the case of the weight value = 1, and it is determined that the weighting integration regarding the number of bytes is not performed. Also good.

  The packet number weight value 1404 is a parameter indicating a weight value based on the congestion degree of the BS 4 when the number of DL packets transmitted by the GW 2 is weighted and integrated. As in the case of the table 251, if the packet number weight value 1404 is omitted in the table 260, it may be handled in the same manner as the case of the weight value = 1, and it is determined that the weighted integration regarding the number of packets is not performed. Also good.

  Note that the initial value of the information included in the table 260 may be set in GW2, or may be set by a message received by GW2 from PS3, CS6, or BS4. Also, these pieces of information can be updated by a message received by GW2 from PS3, CS6 or BS4.

  As described above, in this embodiment, the tables 251 (FIG. 5), 254 (FIG. 8), the table 255 (FIG. 9), the table 256 (FIG. 10), and the table 258 (FIG. ). The memory unit 25 may hold only one of these tables, and the processing unit 26 of the GW 2 may determine the weight value based on the table. Alternatively, the memory unit 25 may hold some or all of these tables, and the processing unit 26 of the GW 2 may determine the weight value based on one of these tables as necessary. Alternatively, the processing unit 26 of the GW 2 determines a plurality of weight values for one received packet based on a plurality of tables, and finally determines a weight value to be applied based on the plurality of weight values. (It will be described later). Note that each of the above tables merely shows an example of the weight value determination conditions, and determination conditions other than the above may be held in the memory unit 25.

<Device configuration: PS3>
FIG. 15 shows a functional block diagram of an example of PS3 used in this embodiment. The PS 3 includes, for example, a GW interface unit 31, a CS interface unit 32, a memory unit 33, and a processing unit 34.

  The GW interface unit 31 is an interface with the GW 2. Using the GW interface unit 31, the PS 3 transmits and receives IP packets to and from the GW 2. In the present embodiment, the PS 3 may receive the accumulated threshold arrival message from the GW 2 using the GW interface unit 31.

  The CS interface unit 32 is an interface with CS6. Using the CS interface unit 32, PS3 transmits and receives IP packets to and from CS6. In the present embodiment, the PS 3 uses the CS interface unit 32 to transmit a status change message to the CS 6, receive a status change message from the CS 6, and send a response message to the CS 6 status change message to the CS 6. May be. When PS3 does not directly communicate with CS6, CS interface unit 32 may be omitted.

  The memory unit 33 stores and manages information such as IP packets to be transmitted / received and addresses of the connected GW 2 and CS 6 as necessary.

  The processing unit 34 performs management of information held in the memory unit 33, IP packet transmission / reception processing such as construction and analysis of IP packets, and determination of parameters relating to QoS or charging.

<Device configuration: CS6>
FIG. 16 shows a functional block diagram of an example of CS6 used in this embodiment. The CS 6 includes, for example, a GW interface unit 61, a PS interface unit 62, a memory unit 63, and a processing unit 64.

  The GW interface unit 61 is an interface with the GW 2. Using the GW interface unit 61, the CS 6 transmits and receives IP packets to and from the GW 2. In the present embodiment, the CS 6 may receive the accumulated threshold reach message from the GW 2 using the GW interface unit 61.

  The PS interface unit 62 is an interface with PS3. Using the PS interface unit 62, the CS 6 transmits and receives IP packets to and from the PS 3. In the present embodiment, the CS 6 uses the PS interface unit 62 to transmit a status change message to the PS 3, receive a status change message from the PS 3, and send a response message to the PS 3 status change message to the PS 3. May be. When the CS 6 does not directly communicate with the PS 3, the PS interface unit 62 may be omitted.

  The memory unit 63 stores and manages information such as IP packets to be transmitted / received and addresses of GW2 and PS3 to be connected as necessary.

  The processing unit 64 performs management of information held in the memory unit 63, IP packet transmission / reception processing such as construction and analysis of IP packets, and determination of parameters related to charging.

  This is the end of the description of the example of the apparatus configuration of the present embodiment, and then an example of the operation process of the present embodiment will be described with reference to the flowcharts of FIGS.

<Operation processing: Weighted integration in GW2>
FIG. 17 shows an example of a weighted integration process of one or both of the number of packets and the number of bytes for one or both of the UL packet and DL packet in the GW 2 of the present embodiment.

  In step S <b> 201, the processing unit 26 of the GW 2 applies the packet and the UL packet received by the BS interface unit 22 or the DL packet received by the SS interface unit 21 according to the packet filtering condition held in the memory unit 25. Determine associated QoS or charging parameters. The determination of the packet filtering condition and the QoS or charging parameter associated with the packet may be performed by a method similar to, for example, Session Binding and Bearer Binding described in Non-Patent Document 1. As a result, information such as the UL / DL type, the source IP address, the source port number, the destination IP address, and the destination port number of the received packet is compared with the packet filtering conditions held in the memory unit 25. Based on the comparison, the applicable QoS or charging parameters include, for example, MS5 identifier, service identifier, integration group identifier, flag indicating whether or not the number of packets is included in the integration target, and the number of bytes as the integration target. Or not, a bandwidth limit value, a packet transmission priority, and the like are determined.

  The packet transmission processing may be performed as, for example, separate processing of the GW2 processing unit 26 in parallel with the present sequence, or after the determination result in step S204 of the present sequence is output, the GW2 processing unit 26. It may be performed as a separate process. The details of the transmission process are the same as, for example, the transmission process performed by a normal gateway, and thus the description thereof is omitted.

  In step S202, the processing unit 26 of the GW 2 applies the QoS or charging applied to the packet determined in step S201 for the UL packet received by the BS interface unit 22 or the DL packet received by the SS interface unit 21. The weight value associated with the packet and the integration threshold value are determined according to the parameters and the determination condition of the weight value and integration threshold value held in the memory unit 25. The determination condition of the weight value held in the memory unit 25 by the GW 2 is managed, for example, as a table 251 shown in FIG. 5, and the processing unit 26 of the GW 2 is associated with the packet specified in step S201. The corresponding weight value is determined based on the MS5 identifier and the service identifier. In addition, when determining the weight value, the weight determined by conditions other than the identifier of the MS 5 and the service identifier may be reflected, and an example of processing in that case will be described separately. The determination condition of the integration threshold stored in the memory unit 25 by the GW 2 is managed, for example, as a table 252 shown in FIG. 6, and the processing unit 26 of the GW 2 identifies the integration group identifier specified in step S201. Based on the above, the corresponding integration threshold is determined.

  In step S202, the processing unit 26 of the GW 2 may execute a process of determining a weight value based on time or a process of determining a weight value based on the degree of congestion of the BS 4. These processes will be described later.

  In step S203, the processing unit 26 of the GW 2 determines, for the UL packet received by the BS interface unit 22 or the DL packet received by the SS interface unit 21, the integration group to be applied to the packet determined in step S201. The number of packets or bytes of the packet according to the identifier, the flag indicating whether the number of packets is included in the accumulation target, the flag indicating whether the number of bytes is included in the accumulation target, and the weight value of the packet determined in step S202 One or both of the numbers are accumulated in a counter associated with the identifier of the accumulation group applied to the packet. Note that the flag indicating whether the number of packets applied to the packet is included in the integration target and the flag indicating whether the number of bytes is included in the integration target are both “not included in the integration target”. In this case, step S203 may be omitted.

  The integrated value of the counter associated with the identifier of the integrated group held in the memory unit 25 by the GW 2 is managed, for example, as a table 253 shown in FIG. 7, and is associated with the packet determined in step S201. For each identifier of the integration group, one or both of the packet number integration value and the byte number integration value before integration for the packet is held. The processing unit 26 of the GW 2 determines that the number of packets included in the integration target determined in step S201 indicates “included in the integration target”, the number of packets of the packet, and step S202. The product with the weight determined in step (b) is calculated, and the calculated product is added to the integrated value of the counter of the table 253 corresponding to the calculated product to update the table 253. Similarly, the processing unit 26 of the GW 2 determines that the number of bytes of the packet is determined when the flag determined in step S201 as to whether or not to include the number of bytes is included in the integration target. Then, the product with the weight determined in step S202 is calculated, and the calculated product is added to the integrated value of the counter of the table 253 corresponding thereto, thereby updating the table 253. The update result is stored in the memory unit 25.

  In step S204, the processing unit 26 of GW2 determines whether the integrated value of the counter related to one or both of the number of packets and the number of bytes updated in step S203 is equal to or greater than the integrated threshold associated with the counter determined in step S202. Determine whether or not.

  When the determination result in step S204 is “not equal to or greater than the integration threshold”, the processing unit 26 of the GW 2 ends the present sequence in step S205N.

  If the determination result in step S204 is “over the integration threshold”, the processing unit 26 of the GW 2 creates an integration threshold arrival message to be transmitted to the destination associated with the counter exceeding the integration threshold in step S205Y. Then, the integration threshold value reaching message is transmitted to the destination, and this sequence is completed. In the integration threshold arrival message, for example, as information associated with a counter exceeding the integration threshold, information such as a packet count integration value, a byte count integration value, an integration group identifier, an MS5 identifier, and a service identifier is set. Also good. Further, the destination associated with the counter exceeding the integration threshold held by the GW 2 in the memory unit 25 is managed, for example, in the same format as the table 252 shown in FIG. The destination associated with the counter determined to be “has become” is held.

  For example, a flag indicating one or both of PS3 and CS6 is set in a table having the same format as the table 252, and the destination IP address of one or both of PS3 and CS6 selected as the destination is the same as that of a normal gateway. May be held in the memory unit 25. Alternatively, the interface corresponding to the destination IP address may be directly set in a table having the same format as the table 252.

<Operational process: Receiving process of reaching accumulated threshold value in PS3>
FIG. 18 shows an example of processing for receiving the accumulated threshold reaching message in PS3.

  In step S <b> 301, the processing unit 34 of the PS 3 analyzes the accumulated threshold arrival message received by the GW interface unit 31. The processing unit 34 of the PS3, for example, as information set in the integration threshold arrival message, whether or not information such as the packet count integration value, the byte count integration value, the integration group identifier, the MS5 identifier, and the service identifier is set and Check for errors in the settings. Note that the processing unit 34 of PS3 may create a response message for the accumulated threshold arrival message received by the GW interface unit 31 after step S301, and transmit the response message to the GW 2 using the GW interface unit 31. . Also, the creation and transmission of the response message may be performed after step S303N or S303Y, or the response message may not be created and transmitted in the first place.

  Subsequently, in step S302, the processing unit 34 of the PS 3 determines whether or not a parameter relating to QoS or charging is changed based on the information read in step S301. The processing unit 34 of the PS3, for example, based on QoS or billing policy information managed by the memory unit 33, sets the packet number integrated value, the byte number integrated value, and the integrated group of the integrated threshold reaching message. A parameter relating to QoS or charging associated with information such as an identifier, an identifier of MS5, and an identifier of service is searched. Similarly, the processing unit 34 of the PS3 is currently applied with the QoS that is applied in the GW2 associated with information such as the identifier of the MS5 and the identifier of the service set in the cumulative threshold arrival message managed by the memory unit 33. Or search for parameters related to billing. Then, the processing unit 34 of the PS 3 determines that there is no change when the retrieved parameters match, and there is a change when they are different.

  If it is determined in step S302 that there is no change, the processing unit 34 of PS3 proceeds to step S304.

  When it is determined in step S302 that there is a change, the processing unit 34 of the PS3 creates a change request message for notifying the GW 2 of the change of the parameter regarding QoS or charging in step S303Y, and uses the GW interface unit 31. A change request message is transmitted to GW2, and the process proceeds to step S304. The change request message includes, for example, a bandwidth limit value, a packet transmission priority, a packet filtering condition that associates a packet with a parameter relating to QoS or charging, an identifier of an accumulation group, a flag indicating whether or not the number of packets is included in the accumulation target, Information such as a flag indicating whether or not to include the number of bytes as an accumulation target, an accumulation threshold, an identifier of MS5, and an identifier of a service are set.

  Subsequently, in step S304, the processing unit 34 of the PS 3 determines whether or not the status related to QoS or charging is changed from the information read out in step S301. The processing unit 34 of the PS3, for example, based on QoS or billing policy information managed by the memory unit 33, sets the packet number integrated value, the byte number integrated value, and the integrated group of the integrated threshold reaching message. The status related to QoS or charging associated with information such as the identifier, the identifier of the MS 5 and the identifier of the service is searched. Similarly, the processing unit 34 of the PS3 is currently applied with the QoS that is applied in the GW2 associated with information such as the identifier of the MS5 and the identifier of the service set in the cumulative threshold arrival message managed by the memory unit 33. Or search for billing status. Then, the processing unit 34 of PS3 determines that there is no change when both search results match, and that there is a change when they are different.

  When it is determined that there is no change in step S304, the processing unit 34 of PS3 ends this sequence in step S305N.

  If it is determined in step S304 that there is a change, the processing unit 34 of the PS3 creates a status change message for notifying the CS 6 of the status change related to QoS or charging in step S305Y, and uses the CS interface unit 32. Send status change message to CS6. In the status change message, for example, information such as QoS status, billing status, integration group identifier, MS5 identifier, and service identifier is set.

  Here, the status change message will be described.

  In the conventional communication system, the PS 3 manages a policy related to QoS and a part of information related to charging, while the CS 6 sometimes manages information related to charging. PS3 and CS6 do not exchange information with each other, and GW2 needs to exchange QoS information independently with PS3 and charging information with CS6.

  In contrast, in the present embodiment, PS3 has the CS interface unit 32 and CS6 has the PS interface unit 62, so that PS3 and CS6 can communicate with each other. For this reason, in this embodiment, as in the past, GW2 communicates with each of PS3 and CS6 independently (for example, transmission of an accumulated threshold arrival message), thereby causing PS3 and CS6 to change parameters, etc. However, GW2 communicates only with PS3, and PS3 sends predetermined information (for example, status change message) to CS6 as necessary (steps S304 and S305Y), so that the parameters of PS3 and CS6 are set respectively. Changes and the like can also be executed.

  As described above, the status change message includes information necessary for determining whether or not the CS 6 changes the parameter related to charging, and how to change the parameter. The CS 6 determines whether or not there is a parameter change based on the status change message received from the PS 3. This process will be described later (see FIG. 21).

  GW2 does not need to execute steps S304 and S305Y when communicating independently with each of PS3 and CS6 (that is, when PS3 and CS6 do not need to communicate with each other) as in the prior art.

  Note that the GW 2 in this embodiment communicates only with the CS 6, and the CS 6 transmits predetermined information (for example, a status change message) to the PS 3 as necessary, thereby executing a parameter change or the like for each of the PS 3 and the CS 6. It can also be made. The status change message transmitted at this time includes information necessary for determining whether or not the PS3 changes the parameter related to QoS or charging, and how to change the parameter. The PS 3 determines whether there is a parameter change based on the status change message received from the CS 6. Such processing of CS6 and PS3 will be described later (see FIGS. 19 and 20).

<Operation process: Receiving process of reaching integrated threshold in CS6>
FIG. 19 shows an example of processing for receiving the accumulated threshold reaching message in CS6.

  In step S <b> 601, the processing unit 64 of the CS 6 analyzes the accumulated threshold arrival message received by the GW interface unit 61. For example, the processing unit 64 of the CS 6 sets whether or not information such as a packet count integration value, a byte count integration value, an integration group identifier, an MS5 identifier, and a service identifier is set as information set in the integration threshold reaching message. Check for errors in the settings. Note that the processing unit 64 of the CS 6 may create a response message for the accumulated threshold arrival message received by the GW interface unit 61 after step S601 and transmit the response message to the GW 2 using the GW interface unit 61. . Further, the creation and transmission of the response message may be performed after step S603N or S603Y, or the response message may not be created and transmitted in the first place.

  Subsequently, in step S602, the processing unit 64 of the CS 6 determines whether or not the charging parameter has been changed based on the information read in step S601. The processing unit 64 of CS6, for example, based on the charging policy information managed by the memory unit 63, is set to the integration threshold reaching message, the packet number integration value, the byte number integration value, the integration group identifier, The accounting parameter associated with information such as the identifier of the MS 5 and the identifier of the service is searched. Similarly, the processing unit 64 of the CS 6 is currently charged with the GW 2 associated with information such as the MS 5 identifier and service identifier set in the cumulative threshold arrival message managed by the memory unit 63. Search for parameters. Then, the processing unit 64 of the CS 6 determines that there is no change when the retrieved parameters match, and that there is a change when they are different.

  If it is determined in step S602 that there is no change, the processing unit 64 of CS6 proceeds to step S604 in step S603N.

  If it is determined in step S602 that there is a change, the processing unit 64 of the CS 6 creates a change request message for notifying the GW 2 of the change of the charging parameter in step S603Y, and changes to the GW 2 using the GW interface unit 61. The request message is transmitted, and the process proceeds to step S604. The change request message includes, for example, a packet filtering condition for associating a packet with a charging parameter, an accumulation group identifier, a flag indicating whether the number of packets is included in the integration target, and a flag indicating whether the number of bytes is included in the integration target. Information such as an integration threshold, an identifier of MS5, and an identifier of service is set.

  Subsequently, in step S604, the processing unit 64 of the CS 6 determines whether or not the status related to charging is changed from the information read in step S601. The processing unit 64 of CS6, for example, based on the charging policy information managed by the memory unit 63, is set to the integration threshold reaching message, the packet number integration value, the byte number integration value, the integration group identifier, A status relating to charging associated with information such as the identifier of the MS 5 and the identifier of the service is searched. Similarly, the processing unit 64 of the CS 6 is currently charged with the GW 2 associated with information such as the MS 5 identifier and service identifier set in the cumulative threshold arrival message managed by the memory unit 63. Find the status about. Then, the processing unit 64 of the CS 6 determines that there is no change if both search results match, and that there is a change if they are different.

  If it is determined in step S604 that there is no change, the processing unit 64 of CS6 ends this sequence in step S605N.

  If it is determined in step S604 that there is a change, the processing unit 64 of the CS 6 creates a status change message for notifying the PS 3 of the status change related to charging in step S605Y, and uses the PS interface unit 62 to the PS 3 Send status change message. In the status change message, for example, information such as a charging status, an integration group identifier, an MS5 identifier, and a service identifier is set.

  Similarly to the case of FIG. 18, when the GW 2 communicates independently with each of the PS 3 and the CS 6, it is not necessary to execute the steps S 604 and S 605 Y.

<Operation processing: Status change message reception processing in PS3>
FIG. 20 shows an example of status change message reception processing in PS3.

  In step S311, the processing unit 34 of PS3 analyzes the status change message received by the CS interface unit 32. The processing unit 34 of the PS3, for example, as the information set in the status change message, information such as the charging status, the identifier of the integration group, the identifier of the MS5, the identifier of the service, the presence / absence of an error in the setting contents, etc. Check. The processing unit 34 of PS3 may create a response message for the status change message received by the CS interface unit 32 after step S311 and transmit the response message to the CS 6 using the CS interface unit 32. Further, the creation and transmission of the response message may be performed after step S313N or S313Y, or the response message may not be created and transmitted in the first place.

  Subsequently, in step S312, the processing unit 34 of the PS3 determines whether or not a parameter related to QoS or charging is changed based on the information read in step S311. The processing unit 34 of the PS3, for example, based on QoS or charging policy information managed by the memory unit 33, charging status, integration group identifier, MS5 identifier, and service Search for parameters related to QoS or billing associated with information such as identifiers. Similarly, the processing unit 34 of the PS3 is configured to use the QoS currently applied in the GW2 associated with information such as the MS5 identifier and the service identifier set in the status change message managed by the memory unit 33. Search for parameters related to billing. Then, the processing unit 34 of the PS 3 determines that there is no change when the retrieved parameters match, and there is a change when they are different.

  When it is determined that there is no change in step S312, the processing unit 34 of PS3 ends this sequence in step S313N.

  If it is determined that there is a change in step S312, the processing unit 34 of the PS3 creates a change request message for notifying the GW 2 of the change of the parameter related to QoS or charging in step S313Y, and uses the GW interface unit 31. A change request message is transmitted to GW2. The change request message includes, for example, a bandwidth limit value, a packet transmission priority, a packet filtering condition that associates a packet with a parameter relating to QoS or charging, an identifier of an accumulation group, a flag indicating whether or not the number of packets is included in the accumulation target, Information such as a flag indicating whether or not to include the number of bytes as an accumulation target, an accumulation threshold, an identifier of MS5, and an identifier of a service are set.

<Operation processing: Status change message reception processing in CS6>
FIG. 21 shows an example of status change message reception processing in CS6.

  In step S611, the processing unit 64 of CS6 analyzes the status change message received by the PS interface unit 62. The processing unit 64 of the CS 6 includes, for example, whether or not information such as a QoS status, a charging status, an integration group identifier, an MS5 identifier, and a service identifier is set as information set in the status change message and an error in setting contents. Check the presence or absence. Note that the processing unit 64 of the CS 6 may create a response message for the status change message received by the PS interface unit 62 after step S611 and transmit the response message to the PS 3 using the PS interface unit 62. Further, the creation and transmission of the response message may be performed after step S613N or S613Y, or the response message may not be created and transmitted in the first place.

  Subsequently, in step S612, the processing unit 64 of the CS 6 determines whether or not the parameter related to charging is changed based on the information read in step S611. The processing unit 64 of CS6, for example, based on the charging policy information managed by the memory unit 63, the charging status, charging status, integration group identifier, MS5 identifier, service set in the status change message Search for parameters related to billing associated with information such as identifiers. Similarly, the processing unit 64 of the CS 6 relates to the billing currently applied in the GW 2 associated with information such as the MS 5 identifier and service identifier set in the status change message managed by the memory unit 63. Search for parameters. Then, the processing unit 64 of the CS 6 determines that there is no change when the retrieved parameters match, and that there is a change when they are different.

  If it is determined in step S612 that there is no change, the processing unit 64 of CS6 ends this sequence in step S613N.

  If it is determined in step S612 that there is a change, the processing unit 64 of the CS 6 creates a change request message for notifying the GW 2 of the change of the parameter related to charging in step S613Y, and sends the change request message to the GW 2 using the GW interface unit 61. Send a change request message. The change request message includes, for example, a packet filtering condition for associating a packet with a charging parameter, an accumulation group identifier, a flag indicating whether the number of packets is included in the integration target, and a flag indicating whether the number of bytes is included in the integration target. Information such as an integration threshold, an identifier of MS5, and an identifier of service is set.

<Operation processing: Determination of weight value based on time in GW2>
Below, an example of the process which determines the weight value of one or both of the number of packets or the number of bytes with respect to one or both of UL packet or DL packet in GW2 of a present Example based on time is shown. This process is executed in step S202 of FIG.

  For the UL packet received by the BS interface unit 22 or the DL packet received by the SS interface unit 21 in step S201, the processing unit 26 of the GW 2 determines the reception time of the packet and the time held in the memory unit 25. The weight value based on the reception time corresponding to the packet is determined according to the determination condition of the weight value based on the packet. The weight value determination condition based on the time held by the GW 2 in the memory unit 25 may be managed as shown in the table 254 shown in FIG. 8 or as shown in the table 255 shown in FIG. It may be. The processing unit 26 of the GW 2 may determine the corresponding weight value based on the identifier of the MS 5 and the service identifier associated with the packet identified in step S201 with reference to the table 254, or the table 255. , The corresponding weight value may be determined based on the identifier of the integration group associated with the packet identified in step S201, or based on one or both of the MS5 identifier and the service identifier The total weight value may be determined using a plurality of weight values such as the determined weight value and the weight value determined based on the identifier of the integration group. Further, as the information regarding the time, for example, the standard time of the place where the GW 2 is installed or the standard time set by the operator managing the GW 2 may be used, or the number of seconds elapsed from a certain reference time may be used as a numerical value. You may use it. An example of the process for determining the overall weight value will be described separately.

<Operation processing: Determination of weight value based on congestion degree of BS4 in GW2>
Below, an example of the process which determines the weight value of one or both of the packet number or the byte number with respect to one or both of UL packet or DL packet in GW2 of a present Example based on the congestion degree of BS4 is shown. This process is executed in step S202 of FIG.

  The procedure of this process is the same as that shown in FIG. 17 except that the degree of congestion of BS4 is taken into consideration in step S202.

  For the UL packet received by the BS interface unit 22 or the DL packet received by the SS interface unit 21 in step S201, the processing unit 26 of the GW 2 stores the congestion degree of the BS 4 used for communication of the packet and the memory unit 25. The weight value based on the congestion degree of the BS 4 corresponding to the packet is determined according to the determination condition of the weight value based on the congestion degree of the BS 4 held.

  The determination condition of the weight value based on the degree of congestion of the BS 4 held in the memory unit 25 by the GW 2 may be managed as a table 256 shown in FIG. 10, for example. In this case, the processing unit 26 of the GW 2 calculates from the identifier of the BS 4 corresponding to the packet specified in step S201, the cell throughput acquired from the BS 4, and the number of transmission bytes per MS 5 measured by the processing unit 26 of the GW 2. The corresponding weight value may be determined based on the ratio between the total transmission throughput of all the MSs 5 connected to each BS 4 and the cell throughput.

  Or the determination conditions of the weight value based on the congestion degree of BS4 which GW2 hold | maintains at the memory part 25 may be managed like the table 258 shown in FIG. 12, for example. In this case, the processing unit 26 of the GW 2 calculates the ratio of the total number of MSs 5 connected to each BS 4 and the cell throughput calculated from the identifier of the BS 4 corresponding to the packet specified in step S201 and the cell throughput acquired from the BS 4, The corresponding weight value may be determined based on

  In any of the above cases, the processing unit 26 of the GW 2, for example, based on the correspondence between the identifier of the BS 4 managed by the table 257 (see FIG. 11) and the identifier of the MS 5 connected to the BS 4. The identifier of the MS 5 corresponding to the packet specified in step S201 may be specified. The correspondence relationship in the table 257 may be updated when the GW 2 receives the location registration message or the handover message of the MS 5. The cell throughput of the BS 4 may be received by the BS interface unit 22 of the GW 2 from the BS 4, for example, or a server that holds statistical information acquired for purposes other than the determination of the weight value such as maintenance. You may acquire from (illustration omitted).

  Further, the processing unit 26 of the GW 2 is based on, for example, the weight value determined based on the ratio of the transmission throughput of all the MSs 5 connected to each BS 4 and the cell throughput, and the ratio of the total number of MSs 5 connected to each BS 4 and the cell throughput. The overall weight value may be determined using a plurality of weight values such as the weight value determined in the above. An example of the process for determining the overall weight value will be described separately.

<Operation process: Weighted integrated value correction for BS4 discard packet in GW2>
Hereinafter, an example of a process for correcting the weighted integrated value of one or both of the number of packets or the number of bytes for one or both of the UL packet and the DL packet in the GW 2 according to the present embodiment based on whether or not the BS 4 has discarded the packet is shown. .

  When it is determined that the packet is discarded for the DL packet transmitted by the BS interface unit 22 or the UL packet transmitted by the SS interface unit 21, the processing unit 26 of the GW 2 reflects the weighted integrated value of the packet. You may remove | exclude the weighted integrated value regarding this packet from the integrated value of a counter.

  The removal of the weighted integrated value related to the packet may be executed, for example, by subtracting the weighted integrated value related to the packet already integrated from the integrated value of the counter when the notification indicating the discard of the packet is received. This may be executed by not adding the weighted integrated value related to the integrated packet to the integrated value of the counter until a notification indicating that the packet has not been discarded is received.

  The notification indicating the discard of the packet may be, for example, a message indicating the discard of the packet received by the BS interface unit 22 from the BS 4 or the packet received by the SS interface unit 21 from the SS 1. It may be a message indicating discarding, or a message indicating discarding of the packet received from a server that has acquired information about the packet discarded at each node such as BS4 and SS1 for the purpose of maintenance management. May be.

  Further, the notification indicating that the packet has not been discarded may be, for example, a message indicating the success of the reception process of the packet received by the BS interface unit 22 from the BS 4, or the SS interface unit from the SS1. 21 may be a message indicating the success of the reception process of the packet received, or from a server that acquires information on a packet that has been successfully received by each node such as BS4 and SS1 for the purpose of maintenance management. The received message may indicate a successful reception process for the packet.

  In addition, the weighted integrated value related to the packet may be specified as follows, for example. First, the processing unit 26 of the GW 2 stores the result of calculating the weighted integration value for each packet in the weighting integration process in the GW 2 in association with the packet identification information in the memory unit 25 of the GW 2 for a certain period of time. Thereafter, when the GW 2 receives the discard notification of the packet, the processing unit 26 of the GW 2 reads the weighted integrated value of the packet from the memory unit 25 based on the identification information of the packet included in the discard notification. As packet identification information, for example, a sequence number of a UDP header may be used.

  FIG. 22 shows a process of correcting the weighted integrated value of one or both of the number of packets and the number of bytes for one or both of the UL packet and the DL packet in the GW 2 of this embodiment based on whether or not the packet is discarded by the BS 4. Indicates. Specifically, as an example, a process in the case where the MS 5 may receive the same packet from the plurality of BSs 4 in a state where the MS 5 has established connections with the plurality of BSs 4 will be described. Such a case where the MS 5 receives the same packet from a plurality of BSs 4 is, for example, simultaneous communication using a plurality of paths via a plurality of BSs 4 during handover sequences between different BSs 4 or for ensuring redundancy. This can occur when Speaking of simultaneous communication using multiple paths, GW2 can reduce the probability that the packet will not reach MS5 by duplicating the packet and transmitting the same DL packet to multiple BS4. This is useful for communication of highly important packets such as emergency calls or emergency control signals.

  In step S211, the processing unit 26 of the GW 2 sets the identifier of the packet for the DL packet received by the SS interface unit 21 in step S201, and sends the BS interface unit 22 to a plurality of BSs 4 that are the destinations of the DL packet. Use to send each. As the identifier of the packet, for example, the sequence number of the UDP header is used. In the following, for example, a process in the case where the GW 2 transmits the same packet to three BSs 4 (hereinafter referred to as BS4 # 1, BS4 # 2, and BS4 # 3, respectively) will be described.

  In step S212, the processing unit 26 of the GW 2 adds, to the table 259, the identifier of the packet transmitted to each BS 4 in S211, the weighted integrated value regarding the packet, the identifier of the transmission destination BS 4, and the timeout time. The table 259 is managed as shown in FIG. 13, for example. The packet can include information indicating that the packet identifier is requested to be notified to the GW 2 when the packet is discarded by the BS 4. For example, depending on whether the sequence number in the UDP header is a value included in a specific range agreed with BS4, whether BS4 is requested to notify GW2 of the identifier of the packet when the packet is discarded You may specify whether or not. Alternatively, a flag indicating whether to request notification when the packet is discarded may be set in a newly added field or header. The timeout time may be set according to the setting policy of GW2. For example, a timer value until timeout may be set in advance in the GW 2, and a time when the timer value has elapsed from the current time may be set as the timeout time.

  In step S213, the processing unit 26 of the GW 2 refers to the table 259 and determines whether or not the message indicating the discard of the packet (hereinafter also referred to as a discard notification) is received from the BS 4 before the timeout time of the packet. Determine. The message indicating the discard of the packet includes the identifier of the BS 4 that is the transmission source of the message, the identifier of the discarded packet, and the like.

  When the time-out time is reached without receiving a message indicating the discard of the packet, the processing unit 26 of the GW 2 determines in step S214N that the MS 5 has successfully received the packet, and stores all the information on the packet from the table 259. Delete and finish the process. In this case, the packet is determined to be a successful transmission packet, and either or both of the number of packets and the number of bytes of the packet are included in the weighted integration target in GW2.

  When the message indicating the discard of the packet is received before the time-out time is reached, the processing unit 26 of the GW 2 stores the identifier of the BS 4 that is the transmission source of the received message in the table 259 in step S214Y. It is determined whether or not it is included in the identifier of the destination BS4 (in the example of FIG.

  If the identifier of the BS4 that is the source of the received message is not included in the identifier of the destination BS4 of the packet, the processing unit 26 of the GW2 discards the received message in step S215N and continues the processing from step S213. .

  When the identifier of the BS4 that is the transmission source of the received message is included in the identifier of the transmission destination BS4 of the packet, the processing unit 26 of the GW2 updates the table 259 in step S215Y and updates the transmission destination BS4 of the packet. Information (information corresponding to “x” illustrated in FIG. 13) indicating that the discard notification has been received is added to the field corresponding to the identifier. Note that the processing unit 26 of the GW 2 may update the timeout time of the packet in the table 259 when the discard notification is received. The update of the timeout time may be performed, for example, only when the first discard notification is received for the packet, or may be performed for all triggers when the discard notification is received.

  In step S216, the processing unit 26 of the GW 2 determines whether or not a discard notification has been received from all the transmission destination BSs 4 of the packet.

  When BS4 that has not yet received the discard notification remains in the transmission destination BS4 of the packet, the processing unit 26 of the GW2 continues the process from step S213 in step S217N.

  When the discard notification is received from all the transmission destination BSs 4 of the packet, the processing unit 26 of the GW 2 determines in step S217Y that the MS 5 has failed to receive the packet, and deletes all the information on the packet in the table 259. The process is terminated. In this case, either or both of the number of packets and the number of bytes of the packet are excluded from the targets of weighted integration in GW2.

  Here, the determination conditions of the weight in the packet duplication transmission case for the plurality of BSs 4 held in the memory unit 25 by the GW 2 may be managed, for example, as a table 260 illustrated in FIG. In this case, the processing unit 26 of the GW 2 calculates the weight value associated with the BS 4 having the smallest (or largest) weight priority value set for each BS 4 among the BSs 4 that have successfully transmitted the packet. It is determined as a weight value corresponding to the packet.

  Another example of the weight determination condition in the packet duplication transmission case for the plurality of BSs 4 held in the memory unit 25 by the GW 2 is, for example, weight priority set for each BS 4 from the table 260 shown in FIG. It may be managed as a table in which only the degree is deleted. In this case, the processing unit 26 of the GW 2 determines, for each BS 4 that has succeeded in packet transmission, the average value or the sum of the weight values set for each BS 4 as the weight value corresponding to the packet.

  As described above, when a plurality of packets having the same contents are transmitted in a multiplexed manner, the method for determining the weight value when two or more of the packets are successfully transmitted is determined based on the QoS or charging policy. May be. For example, in the case of billing, even if a plurality of packets having the same contents are received, since only one of them is actually used, there may be a policy of performing weighted integration only for one packet ( A case where the weight value related to one BS 4 is used based on the weight priority value). On the other hand, even though only one packet is actually used, resources are consumed to actually transmit multiple packets, and the user has enjoyed the benefits of ensuring communication through resource redundancy. There is also a policy that weighted integration is performed for all packets that have been successfully completed (the case of using the sum of weight values described above).

  Note that the processing unit 26 of the GW 2 does not transmit a packet even when only one packet with the same content is transmitted, not a plurality of packets with the same content as described above. Only when successful (that is, when the packet arrives at the transmission destination without being discarded by the BS 4), the weighted integration process can be executed so that the packet is included in the weighted integration target.

  Further, for example, in addition to the weight value in the packet replication transmission case for the plurality of BSs 4 determined here, the overall weight value using a plurality of weight values such as a weight value determined based on other conditions such as time May be determined. An example of the process for determining the overall weight value will be described separately.

<Operation processing: comprehensive weight determination based on a plurality of conditions in GW2>
Hereinafter, an example of processing for determining the weight value of one or both of the number of packets and the number of bytes for one or both of the UL packet and DL packet in the GW 2 of the present embodiment as a comprehensive weight value based on a plurality of conditions. Indicates.

  As already described, the memory unit 25 of the GW 2 may store a plurality of weight value determination conditions (in other words, a set of information that associates a received packet with a weight value). For example, the table 251 is one determination condition, and the table 254 is another determination condition. In such a case, different weight values may be determined for the same received packet based on the respective determination conditions. In such a case, an overall weight value finally applied to the number of packets or the number of bytes of the packet is determined by the following method, for example.

  The processing unit 26 of the GW 2 determines the packet and the UL packet received by the BS interface unit 22 or the DL packet received by the SS interface unit 21 in step S201 in accordance with a plurality of weight determination conditions as in the above example. A corresponding overall weight value may be determined.

  As a condition for the GW2 to determine the overall weight value based on a plurality of conditions, for example, the weight value for each determination condition for the plurality of weight determination conditions as in the above example is managed in the memory unit 25 of the GW2. Also good. In that case, the processing unit 26 of the GW 2 uses a weighted linear sum (that is, each determination condition) using a weight value for each determination condition with respect to each weight value determined based on each determination condition as in the above example. (Sum of products of weight values determined on the basis of) and weight values for each determination condition), and the calculation result is determined as a corresponding total weight value.

  Further, as another example in which the GW 2 determines the overall weight value based on a plurality of conditions, the processing unit 26 of the GW 2 is based on the weight value for each determination condition with respect to the plurality of weight determination conditions as in the above example. Then, for each weight value determined based on each determination condition as in the above example, a product of weight values for each determination condition is calculated, and the calculation result is used as a corresponding total weight value. You may decide.

<Operation processing: Notification of weight value determination result in GW2 to MS5>
Below, an example of the process which notifies MS5 of the weight value determination result in GW2 of a present Example is shown.

  The processing unit 26 of the GW 2 may notify the MS 5 of the weight value determined for the UL packet received by the BS interface unit 22 or the DL packet received by the SS interface unit 21 in step S201.

  The notification to the MS 5 may be executed by, for example, transmitting a weight value notification message to the BS 4 using the BS interface unit 22 and the BS 4 transmitting the weight value notification message to the MS 5. The weight value notification message is, for example, that the weight value determined by GW2 exceeds a certain upper threshold value set for GW2, or the weight value determined by GW2 falls below a certain lower threshold value set for GW2. It may be transmitted at an opportunity, or may be transmitted at an arbitrary opportunity requested by the MS 5. The weight value notification message includes information indicating the weight value. The information indicating the weight value may be, for example, a numerical value of the weight value itself, “High” when the upper limit threshold is exceeded, and “Low” when the lower limit threshold is exceeded. If it is neither, it may be converted into character string information such as “Middle”. In addition, the MS 5 that has received the weight value notification message converts the information indicating the weight value included in the message into an appropriate value or format using, for example, a liquid crystal display (not shown) mounted on the terminal. And may be clearly indicated to the user.

<Operation processing: Change of weight value and weight value determination condition in GW2>
Below, an example of the process which changes the weight value applied in GW2 of a present Example or weight value determination conditions is shown. Here, the change of the weight value determination condition refers to cases such as addition of a new weight value determination condition, change of the already set weight value determination condition, and deletion of the already set weight value determination condition. Including.

  The weight value or the weight value determination condition applied in the GW 2 is, for example, that the weight value determination condition held by the PS 3 is changed by the operator, or the wireless communication standard, the position information, or the BS 4 by handover between different BS 4 It may be updated when a parameter for determining a weight value such as the degree of congestion is changed. The process of changing the weight value or weight value determination condition applied in GW2 is performed by, for example, a node such as PS3, BS4, MS5, or GW2 that has detected a change in the weight value determination condition or the parameter used to determine the weight value. It may be performed by transmitting a message indicating the change to the GW 2 using an interface unit or the like.

  When the weight value or the weight value determination condition is changed, the processing unit 26 of the GW 2 completes the change process and first changes the weight value or change for the packet received in step S201 and the subsequent packets. The weight value determined based on the determined determination condition may be applied. Alternatively, the processing unit 26 of the GW 2 applies the weight value before the change or the weight value determination condition until the connection when the change process is performed is disconnected, and the weight changed in the connection after the next time. A value or changed weight value determination condition may be applied.

  Further, when the weight value or weight value determination condition held in GW 2 is changed, GW 2 may transmit a message indicating the change to a node such as PS3, BS4, or SS1.

  As is clear from the above description, the communication system of the present embodiment is a wireless or wired communication system, and the number of packets in a communication device such as a gateway is set with a condition for determining QoS or charging policy as a weight for each packet. Alternatively, a message about reaching the threshold value of the integration result is reflected when the integration result reflecting the weight of each packet in the communication device is reflected in the integration of one or both of the number of bytes and reaches a threshold value preset in the communication device. The data is transmitted from the communication device to one or both of the accounting server and policy management server. Thus, the packet transfer performance can be improved without increasing the number of counters used for integration in the communication device and the number of messages related to reaching the threshold of the integration result to one or both of the communication device and the accounting server or policy management server. It is possible to provide a communication system and apparatus capable of switching QoS or charging control parameters at an accurate timing based on QoS and charging policy while preventing deterioration.

  In addition, this invention is not limited to an above-described Example, Various modifications are included. The above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. Information such as programs, tables, and files for realizing each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or a recording medium such as an IC card or a DVD. It is also possible to download the program via a network or the like and install it in various storage devices.

  INDUSTRIAL APPLICABILITY The present invention can be used in, for example, a communication system that performs QoS control or charging for IP packets transmitted and received with wireless or wired terminals, and various communication devices such as GW, PS, CS, BS, MS, and SS. Can be applied to.

1 Service providing server (SS)
2 Gateway (GW)
21 SS interface unit 22 BS interface unit 23 PS interface unit 24 CS interface unit 25 Memory units 251 to 260 Table 26 Processing unit 3 Policy management server (PS)
31 GW interface unit 32 CS interface unit 33 Memory unit 34 Processing unit 4 Base station (BS)
5 Terminal (MS)
6 Billing server (CS)
61 GW interface unit 62 PS interface unit 63 Memory unit 64 Processing unit

Claims (13)

A control method of a communication system, comprising: a server device connected to a network; a terminal device connected to the network and communicating packets with the server device; and a communication device relaying communication of the packets. And
The communication device is configured to associate a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet, and the received packet. And a counter for accumulating at least one of the number of packets and the amount of data to which the weight value is applied,
Information associating the packet received by the communication device with the weight value applied to at least one of the number of received packets or the amount of data included in the received packet is the reception time of the packet and the weight value. Contains information to associate
The control method of the communication system is:
A first procedure for identifying the weight value associated with a packet received by the communication device;
At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. A second procedure for integrating using the counter,
Changing a parameter relating to QoS or charging control associated with the counter based on a value accumulated using the counter ; and
The first procedure includes a procedure for specifying the weight value associated with a packet received by the communication device based on a reception time of the packet . A server device connected to a network; a terminal device connected to the network and communicating packets with the server device; a communication device relaying communication of the packets; and the terminal device connected to the network A communication system comprising: a base station that communicates the packet with a base station;
  The communication device is configured to associate a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet, and the received packet. And a counter for accumulating at least one of the number of packets and the amount of data to which the weight value is applied,
  Information associating a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packets is the communication path of the received packets. Including information that associates the congestion level of the base station with the weight value,
  The control method of the communication system is:
  A first procedure for identifying the weight value associated with a packet received by the communication device;
  At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. A second procedure for integrating using the counter,
  Changing a parameter relating to QoS or charging control associated with the counter based on a value accumulated using the counter; and
  The first procedure includes a procedure of specifying the weight value associated with a packet received by the communication device based on a congestion degree of the base station on a communication path of the packet. Control method. The congestion degree of the base station is the ratio of the cell throughput of the base station and the number of terminal devices connected to the base station, or the terminal throughput connected to the base station and the cell throughput of the base station The communication system control method according to claim 2, wherein the communication system control method is determined based on any one of the ratios to the total transmission throughput. A server device connected to a network; a terminal device connected to the network and communicating packets with the server device; a communication device relaying communication of the packets; and the terminal device connected to the network A communication system comprising: a base station that communicates the packet with a base station;
  The communication device is configured to associate a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet, and the received packet. And a counter for accumulating at least one of the number of packets and the amount of data to which the weight value is applied,
  The control method of the communication system is:
  A first procedure for identifying the weight value associated with a packet received by the communication device;
  At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. A second procedure for integrating using the counter,
  A third procedure for changing a parameter relating to QoS or charging control associated with the counter based on a value accumulated using the counter;
  A fourth procedure in which the communication device transmits the received packet to the base station;
  And a fifth procedure for determining whether or not the transmitted packet has been discarded at the base station,
  In the second procedure, the number of received packets to which the specified weight value is applied, or the specified number based on a determination result of whether or not the transmitted packet is discarded in the base station A communication system comprising a step of determining whether or not to accumulate at least one of data amounts included in the received packet to which a weight value is applied, using a counter associated with the received packet. Control method. The communication system comprises a plurality of the base stations,
  Information associating a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packets is the communication path of the received packets. Further includes information associating a base station with the weight value, and information associating each of the plurality of base stations with a priority for determining the weight value,
  The fourth procedure includes a procedure in which the communication device transmits the received packet and a copy thereof to the plurality of base stations,
  In the first procedure, the weight value associated with the base station associated with the highest priority among the plurality of base stations determined to have not discarded the transmitted packet in the fifth procedure, The communication system control method according to claim 4, further comprising a step of specifying the weight value associated with the received packet. The communication system comprises a plurality of the base stations,
  Information associating a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packets is the communication path of the received packets. Further comprising information associating a base station with the weight value;
  The fourth procedure includes a procedure in which the communication device transmits the received packet and a copy thereof to the plurality of base stations,
  The first procedure specifies a sum of weight values associated with the plurality of base stations determined to have not discarded the transmitted packet in the fifth procedure as a weight value associated with the received packet. The communication system control method according to claim 4, further comprising: A control method of a communication system, comprising: a server device connected to a network; a terminal device connected to the network and communicating packets with the server device; and a communication device relaying communication of the packets. And
  The communication device
  Information associating a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet, and the received packet and the weight value Holds information that associates a counter that accumulates at least one of the number of packets and / or the amount of data to which
  A plurality of sets of information associating packets received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packets, and the weight of each set Hold the value,
  The control method of the communication system is:
  A first procedure for identifying the weight value associated with a packet received by the communication device;
  At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. A second procedure for integrating using the counter,
  Changing a parameter relating to QoS or charging control associated with the counter based on a value accumulated using the counter; and
  The first step is a step of specifying, as the weight value associated with the packet received by the communication device, a sum of products of the weight values specified based on the sets and the weight values of the sets. A control method for a communication system, comprising: A control method of a communication system, comprising: a server device connected to a network; a terminal device connected to the network and communicating packets with the server device; and a communication device relaying communication of the packets. And
  The communication device
  Information associating a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet, and the received packet and the weight value Holds information that associates a counter that accumulates at least one of the number of packets and / or the amount of data to which
  Holding a plurality of sets of information associating packets received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data contained in the received packets;
  The control method of the communication system is:
  A first procedure for identifying the weight value associated with a packet received by the communication device;
  At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. A second procedure for integrating using the counter,
  Changing a parameter relating to QoS or charging control associated with the counter based on a value accumulated using the counter; and
  The first procedure includes a procedure of specifying a product of a plurality of weight values specified based on the plurality of sets as the weight value associated with a packet received by the communication device. How to control the system. A server device connected to a network, a terminal device connected to the network and communicating packets with the server device, a communication device relaying communication of the packets, and a policy management device for determining parameters relating to QoS And a charging management apparatus for determining a charging-related parameter, and a communication system control method comprising:
  The communication device
  Information associating a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet, and the received packet and the weight value Holds information that associates a counter that accumulates at least one of the number of packets and / or the amount of data to which
  Holding information associating the counter with a threshold of values accumulated by the counter;
  The control method of the communication system is:
  A first procedure for identifying the weight value associated with a packet received by the communication device;
  At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. A second procedure for integrating using the counter,
  A third procedure for changing a parameter relating to QoS or charging control associated with the counter based on a value accumulated using the counter;
  When the value accumulated by the counter reaches a threshold value associated with the counter, the communication device transmits a message notifying the arrival of the threshold value to at least one of the policy management device or the accounting management device. Sixth procedure,
  Seventh procedure in which at least one of the policy management apparatus and the charging management apparatus that has received the message notifying the arrival of the threshold value transmits a message instructing a change of a parameter relating to the QoS or charging control to the communication apparatus And including
  In the third procedure, the communication apparatus changes a parameter relating to QoS or charging control associated with the counter according to a message received from at least one of the policy management apparatus or the charging management apparatus. How to control the system. In the sixth procedure, the communication device transmits a message notifying the arrival of the threshold value only to the policy management device,
  The seventh procedure is based on a procedure in which the policy management device transmits a message for instructing a change of a parameter relating to the QoS to the communication device, and a message in which the policy management device notifies the arrival of the threshold value. A procedure for transmitting information relating to determination of a parameter relating to charging to the charging management device; and a message instructing a change in the parameter relating to charging based on information received by the charging management device from the policy management device. The communication method control method according to claim 9, further comprising: a step of transmitting to the communication device. In the sixth procedure, the communication device transmits a message notifying the arrival of the threshold value only to the charge management device,
  The seventh procedure is based on a procedure in which the charging management device transmits a message for instructing change of a parameter related to charging to the communication device, and a message in which the charging management device notifies the arrival of the threshold value. A procedure for transmitting information relating to determination of a parameter relating to QoS to the policy management device, and a message for instructing change of the parameter relating to QoS based on information received from the charging management device by the policy management device. The communication method control method according to claim 9, further comprising: a step of transmitting to the communication device. A communication system comprising: a server device connected to a network; a terminal device connected to the network and communicating packets with the server device; and a communication device relaying communication of the packets,
  The communication device
  Information associating a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet, and the received packet and the weight value Holds information that associates a counter that accumulates at least one of the number of packets and / or the amount of data to which
  Holding a plurality of sets of information associating packets received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data contained in the received packets;
  Identifying a product of a plurality of weight values identified based on the plurality of sets as the weight value associated with a packet received by the communication device;
  At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. Using a counter
  A communication system characterized in that a parameter relating to QoS or accounting control associated with the counter is changed based on a value accumulated using the counter. A communication device that relays communication of the packet between a server device connected to a network and a terminal device that is connected to the network and communicates packets with the server device,
  The communication device
  Information associating a packet received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data included in the received packet, and the received packet and the weight value Holds information that associates a counter that accumulates at least one of the number of packets and / or the amount of data to which
  Holding a plurality of sets of information associating packets received by the communication device with a weight value applied to at least one of the number of received packets or the amount of data contained in the received packets;
  Identifying a product of a plurality of weight values identified based on the plurality of sets as the weight value associated with a packet received by the communication device;
  At least one of the number of received packets to which the specified weight value is applied or the amount of data included in the received packet to which the specified weight value is applied is associated with the received packet. Using a counter
  A communication apparatus that changes a parameter related to QoS or charging control associated with the counter based on a value accumulated using the counter.

Images