The present disclosure is a communication system, control apparatus, a communication terminal, communication apparatus, and relates to a communication method, particularly a communication system that performs communication using a plurality of radio bearers, the control device, a communication terminal, communication apparatus, and communication method.
BACKGROUND
[0002]
　In standard 3GPP mobile communication system (3rd Generation Partnership Project), the communication terminal UE (User Equipment) as a technique for performing broadband and low-latency communication, there is a Dual Connectivity. Dual Connectivity is, for example, the UE connects with LTE (Long Term Evolution) the first base station MeNB that communicates (Master evolved NodeB) and the second base station SeNB (Secondary eNB), SeNB both UE in addition to the MeNB it is a technique for performing communication. Thus, it is possible to improve the communication throughput.
[0003]
　Non-Patent Document 1, as the procedure of Dual Connectivity, the UE, in a state that is connected to the MeNB, flow, etc. of a process of newly adding the SeNB as eNB that communicates with the UE is shown.
[0004]
　Meanwhile, although the area covered compared to the mobile communication system is narrow, in a wireless LAN (Local Area Network) communication to enable high-speed communication, in recent years, the available area have been expanded. Therefore, UE is by applying the Dual Connectivity technology, the eNB performing mobile communication, to connect with the access point AP for performing wireless LAN communication, UE have been studied to communicate with AP in addition to eNB . Specifically, in Non-Patent Document 2, the background of the study, and purpose and the like is shown.
[0005]
　Here, the billing rate applied to the UE, radio access technology the UE uses (Radio Access Technology: RAT) is determined based on. For example, UE is, if you are LTE communication using the MeNB and SeNB in ​​Dual Connectivity, billing rate defined when LTE communication is applied to the UE. Non-Patent Document 3, the structure of the PCC (Policy and Charging Control) Architecture for performing policy control and charging control is shown.
[0006]
　Non-Patent Document 4 (TS 23.401), the gateway device PGW (Packet Date Network Gateway) is, as parameters relating to charging, has been shown to manage the RAT type to the UE units. RAT type is a parameter indicating the RAT that the UE is currently using.
CITATION
Non-patent literature
[0007]
Non-Patent Document 1: 3GPP TS 36.300 V13.3.0 (2016-03 ) Section 5.7, Section 10.1.2.8
Non-Patent Document 2: 3GPP TSG RAN Meeting # 67 (2015-03) RP-150510
Non-Patent Document 3: 3GPP TS 23.203 V13.7.0 (2016-03) section 5, A.4.2 section
non-Patent Document 4: 3GPP TS 23.401 V13.6.1 (2016-03 ) section 5.7.4
Summary of the Invention
Problems that the Invention is to Solve
[0008]
　When performing Dual Connectivity listed in 10.1.2.8 Section Non-Patent Document 1, UE communicates with one common RAT to MeNB and SeNB. In this case, as described in Non-Patent Document 4, PGW manages the RAT type of the charging parameters to UE basis. That, PGW is due to the use of common RAT for communication between the communication and the UE and SeNB between the UE and the MeNB, it is impossible to distinguish them communication. Therefore, the communication between the communication and UE and SeNB between the UE and the MeNB, it is not possible to apply different charging rates. As an example, as described in Section 5.7 of Non-Patent Document 1, the communication with the mobile operator with a spectrum mobile operator is licensed by the communication using the spectrum unlicensed Dual Connectivity (Licensed sometimes -Assisted Access (LAA)) is formed. In this case, it is possible that different charging rates for these communications are applied. However, these communications, if a Dual Connnectivity using the same RAT type, it is not possible to distinguish between those communications, there is a problem that it is not possible to apply different charging rates.
[0009]
　Further, as described in Non-Patent Document 2, UE is in performing Dual Connectivity, there is a case where the eNB performing mobile communication, a communication with the access point AP for performing wireless LAN communication. In this case, UE communicates using two RAT simultaneously. Therefore, PGW as Non-Patent Document 4, when managing RAT type to the UE unit, PGW is, the RAT type of management, it is possible that the RAT different the UE is actually using. As a result, if the UE is communicating with two or more types of RAT, (applying the charging rate) is performed properly charging control in accordance with the actual communication that there is a problem that it is impossible.
[0010]
　Purposes of this disclosure, a communication system capable of performing various processes related to radio bearer communication terminal uses to communicate, control device, communication terminal, communication device, and to provide a communication method.
Means for Solving the Problems
[0011]
　Communication system according to a first aspect of the present disclosure, the communication terminal and adapted to communicate with the plurality of communication devices using different radio bearers for each of the plurality of communication devices, the communication device, each radio bearer and configured controller to determine whether to measure the amount of communication in which comprises a.
[0012]
　Control apparatus according to a second aspect of the present disclosure, when the communication terminal communicates with the plurality of communication devices using different radio bearers for each of the plurality of communication devices, at least one communication among the plurality of communication devices device, in which a control unit determines whether to measure the traffic of each radio bearer.
[0013]
　Communication terminal according to the third aspect of the present disclosure, a transmission unit that transmits the support information indicating whether it is possible to the plurality of communication with the different radio bearers for each of the plurality of communication devices to the controller, the support information, and, based on the communication permission information indicating whether or not the own device is allowed to communicate with a plurality of communication devices using a plurality of radio bearers, the device itself by using a plurality of radio bearers instructing a receiver to whether communication with a plurality of communication apparatus receives a result of determination from the control device, on the determination result, to communicate with a plurality of communication devices using a plurality of radio bearers if it contains information, in which and a control unit that executes a process of setting a plurality of communication devices and a plurality of radio bearers, the.
[0014]
　Communication method according to the fourth aspect of the present disclosure, when the communication terminal communicates with the plurality of communication devices using different radio bearers for each of the plurality of communication devices, at least one communication among the plurality of communication devices the device determines whether or not to measure the communication amount for each radio bearer, and transmits the determination result to the communication device.
The invention's effect
[0015]
　The present disclosure, a communication system capable of performing various processes related to radio bearer communication terminal uses to communicate, control device, communication terminal, communication device, and can provide a communication method.
BRIEF DESCRIPTION OF THE DRAWINGS
[0016]
FIG. 1 is a configuration diagram of a communication system in the first embodiment.
FIG. 2 is a configuration diagram of a communication system according to the second embodiment.
3 is a block diagram of a UE according to the second embodiment.
4 is a configuration diagram of a MME according to the second embodiment.
5 is a configuration diagram of a MeNB according to the second embodiment.
6 is a diagram showing a protocol stack in the MeNB and SeNB according to a second embodiment.
7 is a diagram showing the flow of S1 setup processing according to the second embodiment.
8 is a diagram showing the flow of X2 setup processing according to the second embodiment.
9 is a diagram showing the flow of Attach processing according to the second embodiment.
10 is a diagram showing the flow of the Attach process according to the second embodiment.
11 is a diagram showing such Access Restriction Data to a second embodiment.
[Figure 12] MeNB according to the second embodiment, a diagram showing the flow of processing for reporting the count packet amount for each radio bearer relating to UE.
13 is a diagram showing a flow of a plurality PDN Connectivity establishing process according to the third embodiment.
14 is a diagram showing a flow of a plurality PDN Connectivity establishing process according to the third embodiment.
15 is a diagram showing an E-UTRAN initiated E-RAB modification procedure according to the fourth embodiment.
16 is a diagram showing an S1 release procedure according to the fifth embodiment.
17 is a diagram showing a PDN GW initiated bearer deactivation procedure according to the fifth embodiment.
18 is a diagram showing such MME initiated bearer deactivation procedure in the fifth embodiment.
19 is a diagram showing an X2 HO procedure according to the sixth embodiment.
FIG. 20 is a diagram showing an X2 HO procedure according to the sixth embodiment.
21 is a diagram showing an X2 HO procedure according to the sixth embodiment.
22 is a diagram showing such S1 HO procedure in the sixth embodiment.
23 is a diagram showing such S1 HO procedure in the sixth embodiment.
FIG. 24 is a diagram showing an S1 HO procedure according to the sixth embodiment.
[FIG 25 is a diagram showing an S1 HO procedure according to the sixth embodiment.
FIG. 26 is a diagram showing such S1 HO procedure in the sixth embodiment.
FIG. 27 is a configuration diagram of a MeNB in each embodiment.
[FIG. 28] is a configuration diagram of a UE in each embodiment.
FIG. 29 is a configuration diagram of a MME in each embodiment.
DESCRIPTION OF THE INVENTION
[0017]
　(Embodiment 1)
　Hereinafter, with reference to the drawings will be described embodiments of the present disclosure. Configuration Example of the present disclosure a communication system according to a first embodiment of will be described with reference to FIG. Communication system of FIG. 1, the communication terminal 11, the communication device 12, the communication device 13, and has a control device 14. Communication terminal 11, the communication device 12, the communication device 13, and the controller 14 may be a computer system that operates by the processor executing the program stored in the memory.
[0018]
　Communication terminal 11 is configured to communicate with a plurality of communication devices using different radio bearers for each of the plurality of communication devices. Communication terminal 11, a mobile phone terminal, a smartphone terminal, may be a tablet-type terminal or the like. Further, the communication terminal 11, M2M (Machine to Machine) terminal or MTC (Machine Type Communication) may be a terminal or the like. Radio bearer, for example, between the communication device 12 and the communication terminal 11, furthermore, a data communication path between the communication terminal 11 and the communication device 13. Communication terminal 11 is, for example, as shown in FIG. 1, between the communication device 12 and communication device 13 may set the radio bearer. The dotted line of FIG. 1 shows a communication terminal 11, the radio bearer 121, 131 to be set between the communication device 12 and communication device 13.
[0019]
　The communication device 12 and communication device 13 may be, for example, a base station used in mobile communications. Or, a communication device 12 and communication device 13 may be a AP used in wireless LAN communications (Access Point) or WT (Wireless LAN Termination). The communication device 12 is a base station, the communication device 13 is AP or WT (hereinafter represented by WT) may be.
[0020]
　Communication terminal 11 may set a plurality of radio bearers using one RAT. For example, the communication terminal 11 may set a plurality of radio bearers using LTE as RAT. Or, the communication terminal 11 may set a plurality of radio bearers using the plurality of RAT. For example, the communication terminal 11 may set a plurality of radio bearers using the RAT that is defined as a so-called 3G in LTE and 3GPP. Further, for example, communication terminal 11 includes a radio communication scheme defined in 3GPP, it may be set a plurality of radio bearers using the wireless LAN.
[0021]
　Controller 14, the communication device 12, configured to determine whether to measure the traffic of each radio bearer. Controller 14, for example, transmits an instruction signal instructing to measure the traffic of each radio bearer to the communication device 12. When the communication terminal 11 to communicate with two or more communication devices, the control device 14, the communication terminal 11 may transmit an instruction signal to the two or more communication devices that communicate. Or, the control unit 14 may transmit an instruction signal to the communication device 12 as a representative of the two or more communication devices. Communication device 12 as a representative, with measures the traffic of the radio bearer 121 between the communication terminal 11 with its own device 12, the traffic of the radio bearer 131 between the communication device 11 and other communication devices 13 may be measured by the own apparatus 12, it may be collected from the other communication device 13. Specifically, if the communication with the communication terminal 11 and the communication device 13 are aggregated in the communication device 12 (for Aggregation), the communication device 12, also measured traffic of a radio bearer 131. Even in such a case, the communication device 12 may collect the traffic radio bearer 131 which is measured by the communication device 13 from the communication device 13. On the other hand, if the communication with the communication terminal 11 and the communication device 13 is not aggregated by the communication device 12, the communication device 12 collects traffic radio bearer 131 which is measured by the communication device 13 from the communication device 13.
[0022]
　As described above, in the communication system of FIG. 1, the control unit 14, the communication device 12 determines whether to measure the traffic of each radio bearer. Further, the communication device 12, in accordance with the result determined in the controller 14, measures or collect traffic for each radio bearer. Thus, for example, when performing charging of telecommunications carriers in accordance with the traffic of the communication terminal 11, it is possible to charge according to the communication amount for each radio bearer.
[0023]
　For example, by the communication device 12 measures the communication amount for each radio bearer, operators may set different packet unit price for each radio bearer, it is possible to charge for each radio bearer.
[0024]
　(Second Embodiment)
　Subsequently, configuration of the present disclosure exemplary communication system according to a second embodiment of the will be described with reference to FIG. Communication system of FIG. 2 shows a block diagram of a communication system defined in 3GPP. Communication system of FIG. 2, UE20, MeNB21, SeNB22, MME (Mobility Management Entity) 23, HSS (Home Subscriber Server) 24, SGW (Serving Gateway) 25, PGW26, PCRF (Policy and Charging Rule Function) entity 27 (hereinafter , and PCRF27), AF (Application Function) entity 28 (hereinafter referred to as AF28), OFCS29 (Offline Charging System ), and has an OCS (Online Charging System) 30.
[0025]
　UE20 corresponds to the communication terminal 11 of FIG. 1. UE20 is used as a general term for a communication terminal in 3GPP. MeNB21 corresponds to the communication device 12 of FIG. 1. SeNB22 corresponds to the communication device 13 of FIG. 1. MeNB21 and SeNB22 is a base station used when UE20 performs Dual Connectivity. MME23 corresponds to the control device 14 of FIG. 1. MME23 mainly mobility management of UE 20, bearer setup request, setting instruction bearer, bearer deletion request, or an apparatus for performing the delete instruction bearer.
[0026]
　SGW25 is connected to the radio access system, a device for transferring the user data between the radio access system and PGW26. PGW26 the external network: performing a connection to the (PDN Packet Data Network, etc.). PCRF27 determines MeNB21, SeNB22 and QoS in PGW26 (Quality of Service) control or charging control of the policy of the (billing system).
[0027]
　AF28 is a device that provides an application performs control related to the application service to be provided to UE 20. OCS30 and OFCS29 performs charging control and the like in accordance with the billing agreement UE 20. For example, if the billing agreement, such as prepaid service, OCS 30 performs billing processing with the ability to monitor constantly traffic. On the other hand, in the case of such as billing contract of monthly OFCS29 performs the billing process.
[0028]
　Subsequently, exemplary configuration of UE20 according to the second embodiment of the present disclosure will be described with reference to FIG. UE20 includes a transmitting and receiving unit 41, transceiver 42, and a control unit (Controller) 43. Transceiver 41, transceiver 42 and, components constituting the UE20 such as the control unit 43, the processor may be a module or software processing by executing a program stored in the memory is executed. Or, the components constituting the UE20 may be hardware such as a chip or circuit. Transceiver 41 and transceiver 42 may be a transmission unit (Transmitter) and receiver (Receiver).
[0029]
　Transceiver unit 41 communicates with MeNB21. Transceiver unit 41, for example, may be performed MeNB21 wireless communication using the LTE is defined as a wireless communication system in 3GPP. Transceiver 42 communicates with SeNB22. Transceiver 42 may perform SeNB22 and wireless communication using the LTE. The transmitting and receiving unit 42, using different wireless communication systems and LTE, may communicate with different communication device with SeNB22. For example, transceiver unit 42 uses the wireless LAN communication may communicate with WT. In this case, WT is assumed to be a communication apparatus which can communicate with MeNB21. That is, transceiver 42 communicates with MeNB21 via SeNB22 or WT.
[0030]
　Control unit 43, in the case of using the Dual Connectivity, performs control of distributing the transmission data to the transceiver 41 and the transceiver 42. Control unit 43 may further performs modulation processing of transmission data. The control unit 43 may execute the decoding process on the received data output from the transceiver 41 and the transceiver 42.
[0031]
　Subsequently, configuration examples of MME23 according to the second embodiment of the present disclosure will be described with reference to FIG. MME23 includes a base station communication unit 51, SGW communication unit 52, HSS communication unit 53, and has a control unit 54. Components comprising these MME23, the processor may be a module or software processing by executing a program stored in the memory is executed. Or, the components constituting these MME23 may be hardware such as a chip or circuit. Incidentally, the communication unit may be a transmission unit (Transmitter) and receiver (Receiver).
[0032]
　Base station communication unit 51 performs transmission and reception of control signals between the MeNB21. The base station reference point between the communication unit 51 and MeNB21 is defined as S1-MME. The base station communication unit 51 transmits and receives NAS (Non Access Stratum) message between a UE20 via MeNB21. NAS message is transmitted in MeNB21, it is transmitted between the base station communication unit 51 UE 20.
[0033]
　SGW communication unit 52 performs transmission and reception of control signals between the SGW25. SGW reference point between the communication unit 52 and SGW25 is specified to S11. SGW communication unit 52 receives information concerning accounting transmitted from PGW26 through SGW25.
[0034]
　HSS communication unit 53 performs transmission and reception of control signals between the HSS24. Reference point between the HSS communication unit 53 and HSS24 is specified to S6a. HSS communication unit 53 receives the subscriber information relating to UE20 from HSS24. The subscriber information, for example, UE 20 is included information as to whether may be implemented or configure Dual Connectivity.
[0035]
　Control unit 54 uses the information sent from MeNB21 and HSS24, determines whether to implement the Dual Connectivity to MeNB21. Further, the control unit 54, when it perform Dual Connectivity in MeNB21, relative MeNB21, determines whether to measure the traffic of each radio bearer. Control unit 54 via the base station communication unit 51, sends an indication message indicating the determination result to MeNB21. Indication message, for example, may be a message instructing the implementation of the Dual Connectivity respect MeNB21. Furthermore, instruction message, to the MeNB21, in implementing the Dual Connectivity, it may be a message instructing to measure the traffic of each bearer. The control unit 54, via the SGW communication unit 52 and SGW25, may send an indication message to the PGW26. This indication message, the PGW26, and the Dual Connectivity is implemented, it is traffic measurement or collection of each radio bearer at MeNB21, and to receive charging information for the communication amount is informed. Thereby, PGW26 is later that it is not necessary to measure the traffic is seen in its own device. Further, PGW26 is performed ready for performing a billing process on the basis of the received billing information.
[0036]
　Subsequently, configuration examples of MeNB21 according to the second embodiment of the present disclosure will be described with reference to FIG. MeNB21 is, UE communication unit 61, the base station communication unit 62, C-Plane communication unit 63, U-Plane communication unit 64, the control unit 65 and,, a data measuring section 66. UE communication unit 61, the base station communication unit 62, C-Plane communication unit 63, U-Plane communication unit 64, the control unit 65 and, components constituting the MeNB21 such as data measurement unit 66 stores the processor in the memory it may be a module or software processing is performed by executing a program. Or, the components constituting the MeNB21 may be hardware such as a chip or circuit. Incidentally, the communication unit may be a transmission unit (Transmitter) and receiver (Receiver).
[0037]
　UE communication unit 61 performs transmission and reception of data between the UE 20. Reference point between the UE communication part 61 and UE20 are defined as LTE-Uu. Base station communication unit 62 transmits and receives data between the SeNB22. The base station reference point between the communication unit 62 and SeNB22 is defined as X2.
[0038]
　C-Plane communication unit 63 exchanges C (Control) -plane data between a MME23. C-Plane data may be paraphrased as control signals. U-Plane communication unit 64 performs transmission and reception of U (User) -plane data between a SGW25. U-Plane data may be paraphrased as user data.
[0039]
　Controller 65, to MME23 through a C-Plane communication unit 63 transmits the information about the Dual Connectivity. Information regarding Dual Connectivity may be, for example, information indicating whether or not it is possible MeNB21 to implement Dual Connectivity. Further, information on Dual Connectivity may be information about the SeNB implementing the Dual Connectivity with MeNB21.
[0040]
　The control unit 65, when instructed to implementation of Dual Connectivity from MME23, implements the control to add SeNB22 via the base station communication unit 62. The control unit 65, when instructed to measure the traffic of each radio bearer from MME23, the data measuring section 66, and outputs a message instructing the measurement of the traffic of each radio bearer. The control unit 65 via the C-Plane communication unit 63 transmits the measurement result in the data measuring section 66 to MME23.
[0041]
　Data measurement unit 66, when instructed to measure the traffic of each radio bearer, to measure the amount of communication between UE20 and MeNB21. Data measuring section 66, when a plurality of radio bearers is configured between the UE 20, to measure the amount of communication for each radio bearer. Moreover, the data measurement unit 66 obtains via the base station communication unit 62 of information regarding the communication amount for each radio bearer from SeNB22 between UE20 and SeNB22.
[0042]
　Here, the protocol stack will be described in MeNB21 and SeNB22 with reference to FIG. MeNB21 and SeNB22 is, MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, and constituted by PDCP (Packet Data Convergence Protocol) layer. UE20 and PDCP layer of the radio bearer is set between the PDCP layer of MeNB21 or SeNB22.
[0043]
　Here, the configuration of the Dual Connectivity carried out in MeNB21 and SeNB22. As Dual Connectivity implemented in MeNB21 and SeNB22, certain configurations and using MCG (Master Cell Group) Bearer and SCG (Secondary Cell Group) Bearer, the configuration using the Split Bearer is.
[0044]
　MCG Bearer is a communication bearer which is set between the MeNB21 and SGW25. MCG Bearer corresponds to the radio bearer and one to one that is set between the UE20 and MeNB21. SCG Bearer is between SeNB22 and SGW25, or a communication bearer which is set between the SeNB22 and other SGW. The other SGW, which is different from the SGW and SGW25. When performing Dual Connectivity using MCG Bearer and SCG Bearer, SCG Bearer corresponds to the radio bearer and one to one that is set between the UE20 and SeNB22.
[0045]
　Split Bearer is a communication bearer which is set between the MeNB21 and SGW25. Split Bearer is associated with a radio bearer that is set directly between the UE20 and MeNB21. Additionally, Split Bearer is associated with a radio bearer is set between the MeNB21 through UE20 and SeNB22. In other words, MeNB21 includes data transmitted via the configured radio bearer directly between UE20 and MeNB21, sent through the radio bearer is set between the MeNB21 through UE20 and SeNB22 and data is transmitted to SGW25 via the Split Bearer. MeNB21 the data transmitted from the UE20 to SeNB22, received via the X2 is a reference point between the MeNB21 and SeNB22. Communication using the Split Bearer, may be referred to as aggregation communication.
[0046]
　Subsequently, with reference to FIG. 7, a description is given of the flow of S1 setup process between the MeNB21 and MME23. First, MeNB21 is started (S11). For example, MeNB21 is activated by the power supply is turned on.
[0047]
　Then, MeNB21 transmits the S1 SETUP REQUEST message to the MME23 (S12). S1 SETUP REQUEST message, as parameters, including DC Support, DC Combination, the DC Traffic count support indication.
[0048]
　DC Support is information indicating whether or not it is possible MeNB21 constitutes a Dual Connectivity. DC Combination is information indicating whether to configure which device or which RAT and Dual Connectivity is MeNB21. For example, MeNB21 may configure SeNB22 and Dual Connectivity. Or, MeNB21 may constitute the WT and Dual Connectivity for performing wireless LAN communication. Or, MeNB21 may constitute a base station and a Dual Connectivity for performing communication using a wireless communication system defined as 3G in 3GPP. Or, MeNB21 may constitute a base station and a Dual Connectivity for performing communication using a wireless communication system that may be defined as a 5G future in 3GPP. Wireless communication system prescribed as 5G may be high-speed communication and method for realizing a short communication delay or the like than LTE using a wider bandwidth than LTE.
[0049]
　DC Traffic count support indication is information indicating whether MeNB21 supports the ability to measure the amount of communication for each radio bearer. Amount of communication, for example, amount of packets (including such as packet number and the data volume. Hereinafter, these are represented by the packet volume.) May be used. And measuring the amount of communication for each radio bearer, when configuring the Dual Connectivity with MeNB21 is Split Bearer, and the amount of communication data and MeNB21 and UE20 are directly transmitted and received, data MeNB21 to UE20 and received through the SeNB22 and to measure and differentiate between the traffic. Further, when configuring the Dual Connectivity with MeNB21 is MCG Bearer and SCG Bearer, and measures the communication amount for each radio bearer, MeNB21 and the amount of communication data transmitted and received with UE 20, the data SeNB22 to receive the UE 20 and to measure and distinguish between traffic.
[0050]
　Then, MME23 sends the S1 SETUP RESPONSE message to MeNB21 (S13). S1 SETUP RESPONSE message, as parameters, including DC Traffic count support indication. S1 SETUP RESPONSE DC contained in the message Traffic count support indication is, MME23 is information indicating whether or not it corresponds to the count of the packet amount of each radio bearer in MeNB21. For example, DC Traffic count support indication is, MME23 is, the information about the packet amount of each radio bearer received from MeNB21, be information indicating whether it is possible to transmit the charging information to the PGW26 through SGW25 good.
[0051]
　By executing the processing in steps S12 and S13, MeNB21 and MME23 can exchange information about Dual Connectivity. In other words, by executing the processing in steps S12 and S13, MeNB21 and MME23 can negotiate information about Dual Connectivity.
[0052]
　Subsequently, the flow of X2 setup process between the MeNB21 and SeNB22 be described with reference to FIG. X2 setup process is a process MeNB21 is executed after being started. First, MeNB21 transmits the X2 SETUP REQUEST message to the SeNB22 (S21). X2 SETUP REQUEST message includes the same parameters as parameters included in the S1 SETUP REQUEST message of FIG.
[0053]
　Then, SeNB22 transmits the X2 SETUP RESPONSE message to MeNB21 (S22). X2 SETUP RESPONSE message, as parameters, including DC Support, DC Combination, the DC Traffic count support indication. X2 SETUP RESPONSE DC contained in the message Traffic count support indication is information indicating whether SeNB22 supports function of counting the amount of packets for each radio bearer.
[0054]
　For example, in a case where MeNB21 and SeNB22 constitute a Dual Connectivity, further, SeNB22 is, a case that supports the function of counting the amount of packets for each radio bearer. In this case, SeNB22 transmits the packet amount of transmitted and received in the radio bearer associated with the SCG Bearer to MeNB21.
[0055]
　By executing the processing in step S21 and S22, MeNB21 and SeNB22 can exchange information about Dual Connectivity. In other words, by executing the processing in step S21 and S22, MeNB21 and SeNB22 can negotiate information about Dual Connectivity.
[0056]
　Further, in FIG. 8, an example has been described in which MeNB21 sends X2 SETUP REQUEST message to the SeNB22, SeNB22 is to MeNB21, it may transmit the X2 SETUP REQUEST message.
[0057]
　Subsequently, the flow of Attach processing relating UE20 will be described with reference to FIGS. Attach process is a process performed in order to send and receive data via the UE20 core network.
[0058]
　First, UE 20 transmits an Attach request message to MME23 through MeNB21 (S31). Attach request message includes a DC Support, DC Combination as parameters. DC Support included Attach request message is information indicating whether it is possible to UE20 constitutes a Dual Connectivity. That, DC Support included Attach request message, UE 20 is information indicating whether it is possible to communicate using a plurality of radio bearers simultaneously. Also, DC Combination contained Attach request message, UE 20 is information indicating whether it is possible to which RAT combination of constituting the Dual Connectivity with. UE20 is a combination of same RAT may constitute Dual Connectivity, may constitute a Dual Connectivity by combining different RAT.
[0059]
　Then, MME23 sends a Update the Location request message to the HSS24 (S32). Then, HSS24 transmits the Update the Location Ack message to MME23 (S33). Update the Location Ack message includes Access Restriction Data, the DC not allowd as a parameter. Access Restriction Data, DC not allowd is managed in HSS24 as a subscriber information of the UE20.
[0060]
　DC not allowed A is information indicating whether UE20 is allowed to configure the Dual Connectivity. For example, DC not allowed A information may be used as the flag information. Specifically, when a "1" to the DC not allowed A is set, it indicates that the UE 20 is authorized to configure the Dual Connectivity, when "0" is set, UE 20 is Dual Connectivity it may indicate that it is not allowed to configure.
[0061]
　Access Restriction Data is information indicating a RAT that can not UE20 is used. Here, a description will be given Access Restriction Data with reference to FIG. Figure 11 shows that the bit position is set to Access Restriction Data, and a RAT whose use is restricted is associated. For example, when 1 is set to 0-th bit of the Access Restriction Data, UE can not use the UTRAN. Further, when 1 is set in the seventh bit Access Restriction Data, UE may not be able to use the wireless communication scheme defined as 5G.
[0062]
　Returning to Figure 9, then, MME23, based on the DC Traffic count support indication transmitted from the DC Support, MeNB21 transmitted from MeNB21 and UE 20, whether or not to count the packet amount of each radio bearer MeNB21 It is determined (S34). For example, MME23 is, MeNB21 and UE20 is, it is possible to configure the Dual Connectivity, further, when the MeNB21 supports function of counting the amount of packets per radio bearer, a packet for each radio bearer MeNB21 It determines that to count the amount. For example, MME23, if either the MeNB21 and UE20 can not constitute a Dual Connectivity, or, MeNB21 may not support the function of counting the amount of packets per radio bearer, for each radio bearer MeNB21 packet amount determined not to count the.
[0063]
　Further, in step S34, MME23, in DC not allowed A transmitted from HSS24, if UE20 has been shown to not be allowed to configure the Dual Connectivity, counting the packet amount of each radio bearer MeNB21 let not and may be determined. Further, in step S34, MME23, when RAT shown in DC Combination transmitted from UE20 and MeNB21 have been shown to have limited use in the transmitted Access Restriction Data from HSS24, MeNB21 it may be determined that does not count the amount of packets per radio bearer.
[0064]
　Then, MME23 sends the Create Session Request message to SGW25 (S35). MME23 sets the DC Traffic count support indication indicating the determination result in step S34 in the Create Session Request message. Or, MME23, when judging that the MeNB21 in step S34 does not count the amount of packets per radio bearer, in the Create Session Request message may not set the DC Traffic count support indication.
[0065]
　Then, SGW25 sends the Create Session Request message received to PGW26 in step S35 (S36). Then, PGW26, in between the PCRF27, perform QoS negotiation for a communication quality of the UE 20 (S37).
[0066]
　Then, PGW26 sends the Create Session Response message to the SGW25 (S38). Create Session Response message includes DC Traffic count support indication as a parameter, count rule, the DC not allowed. DC Traffic count support indication contained in the create Session Response message, PGW26 is the information indicating whether it is possible to output OFCS29 and to OCS30 information about packet amount of each radio bearer transmitted from MeNB21 as billing information is there.
[0067]
　DC not allowed A contained in the create Session Response message is information indicating whether to permit the UE20 constitutes a Dual Connectivity. For example, PGW26, depending on the APN UE20 connects (Access Point Name), may be set whether to allow configuring the Dual Connectivity. In other words, for each APN the UE20 is connected, whether to allow configuring the Dual Connectivity may be predetermined. The create count rule included in Session Response message is information MeNB21 indicates detailed conditions for counting the amount of packets per radio bearer. For example, the count rule, RAT of RAT type for which to count, count to a target traffic Traffic type, and may include at least one of the Report period indicating a period for counting.
[0068]
　For example, the RAT type, will be described the case where LTE is specified. In this case, MeNB21, when constituting the Dual Connectivity with LTE and wireless LAN communication, and counts only the number of packets transmitted and received in the LTE. Meanwhile, MeNB21, when constituting the SeNB22 and Dual Connectivity performing LTE communication, counts all packets amount sent and received in each radio bearer.
[0069]
　Traffic type, for example, to count only the Downlink user data, counts only Uplink user data, or to count both Downlink user data and Uplink user data, indicating the like. Report period may be, for example, the specified period, such as every hour, and the start time and end time for counting the amount of packets may be shown.
[0070]
　Then, SGW25 sends the Create Session Response message received to MME23 in step S38 (S39). MME23 is transmitted Access Restriction Data and DC not allowed A from HSS24, further using a DC not allowed A received from PGW26, UE20, MeNB21, and, whether the Dual Connectivity and active in SeNB22, i.e., Dual It determines whether to configure the Connectivity (S40). For example, MME23 is, Access Restriction Data and DC not allowed A transmitted from HSS24, and, if UE20 are shown not to allow configuring the Dual Connectivity in any of DC not allowed A transmitted from PGW26 , UE 20, MeNB21, and may determine that the Dual Connectivity in SeNB22 an inert.
[0071]
　Turning to FIG. 10, MME23 is to MeNB21, sends the Initial Context Setup message including the ATTACH Accept message (S41). ATTACH Accept message is transmitted in MeNB21, it is transmitted to the UE 20.
[0072]
　ATTACH Accept message includes a DC not allowed as a parameter. DC not allowed A contained ATTACH Accept message is information indicating whether to permit the UE20 constitutes a Dual Connectivity. Initial Context Setup message includes in addition to the ATTACH Accept message, DC Traffic count support indication as a parameter, count rule, the DC not allowed. DC not allowed A contained in Initial Context Setup message is information indicating whether to permit MeNB21 constitutes a Dual Connectivity. MME23, when indicating that permit MeNB21 is in DC not allowed A constituting the Dual Connectivity, the DC Traffic count support indication, relative MeNB21, indicates whether or not to count the amount of packets for each radio bearer .
[0073]
　Then, MeNB21, in Initial Context Setup message received at step S41, if shown to allow configuring the Dual Connectivity, was instructed to count the amount of packets for each radio bearer, in accordance with count rule starts counting the amount of packets (S42). Furthermore, MeNB21 is the amount counted packets in SeNB22, may be received from SeNB22.
[0074]
　Then, MeNB21 is to UE 20, and transmits the RRC Connection Reconfiguration message including an ATTACH Accept message (S43). ATTACH Accept message contained in RRC Connection Reconfiguration message is the same as the ATTACH Accept message contained in Initial Context Setup message. RRC Connection Reconfiguration message, in addition to the ATTACH Accept message as parameters, including DC not allowed A.
[0075]
　Then, UE 20 is to MeNB21, transmits the RRC Connection Reconfiguration complete message (S44). Then, MeNB21 is to MME23, sends the Initial Context Setup Response message (S45). Initial Context Setup Response message includes a DC Charging activated as a parameter. DC Charging activated, in MeNB21, used to notify that it has started an operation for counting the amount of packets for each radio bearer.
[0076]
　Then, MME23 sends a Modify Bearer Request message to the SGW25 (S46). Modify Bearer Request message includes a DC Charging activated acquired in step S45. Then, SGW25 sends a Modify Bearer Request message to the PGW26 (S47). Modify Bearer Request message includes a DC Charging activated acquired in step S46.
[0077]
　PGW26, prior to obtaining the DC Charging activated counts the amount of packets sent and received for each UE. PGW26 is, DC Charging in after getting the activated, to recognize that it is counted packets of each radio bearer in MeNB21, may stop the counting of the amount packet sent and received in each UE. Or, PGW26 is, DC Charging even after getting activated, it may continue to count the amount packets transmitted and received for each UE.
[0078]
　Then, PGW26 is to SGW25, sends a Modify Bearer Response message (S48). Then, SGW25 is to MME23, sends a Modify Bearer Response message (S49).
[0079]
　Subsequently, with reference to FIG. 12, MeNB21 is, explaining the flow of processing for reporting the count packet amount for each radio bearer relating to UE 20. First, MeNB21 in accordance with count rule, in order to gather information about the amount counted packets in SeNB22, transmits a Traffic count report request message to the SeNB22 (S51). For example, MeNB21, when the count period determined in count rule is expired, may send a Traffic count report request message to the SeNB22. Or, MeNB21 may be applied to any timing may transmit Traffic count report request message to the SeNB22.
[0080]
　Then, SeNB22 transmits a Traffic count report message to MeNB21 (S52). Traffic count report message, including the Traffic data as a parameter. Traffic data is the information about the packet amount counted for each radio bearer in SeNB22. Specifically, Traffic data is, RAT type indicating the RAT counted, Measured indicates the count packet amount traffic, may include Measured period indicating the counting period.
[0081]
　Measured traffic includes a packet quantity in the Downlink user data, it may indicate to distinguish between packet amount in Uplink user data. Further, Measured period, for example, it may indicate the time and the completion of the time starts to count and counts.
[0082]
　Then, MeNB21 transmits the E-RAB MODIFICATION INDICATION message to MME23 (S53). E-RAB MODIFICATION INDICATION message, MeNB21, along with Traffic data collected from SeNB22, including Traffic data is information about the amount of packets counted in MeNB21.
[0083]
　Then, MME23 is to SGW25, sends a Modify Bearer Request message (S54). Modify Bearer Request message includes a Traffic data similar Traffic data contained in the E-RAB MODIFICATION INDICATION. Then, SGW25 is to PGW26, sends a Modify Bearer Request message (S55). Traffic data contained in Modify Bearer Request message in step S55 is similar to the Traffic data contained in the Modify Bearer Request message in step S54.
[0084]
　Then, PGW26 sends a Modify Bearer Response message to the SGW25 (S56). Then, SGW25 sends a Modify Bearer Response message to the MME23 (S57). Then, MME23 is to MeNB21, transmits an E-RAB MODIFICATION CONFIRM message (S58).
[0085]
　PGW26 in step S55, in MeNB21 and SeNB22 constituting the Dual Connectivity, receives information on the counted amount of packets for each radio bearer. Than this, PGW26 generates billing ticket corresponding to the counted amount of packets for each radio bearer (CDR), and transmits the generated billing ticket to OFCS29 or OCS 30. OFCS29 or OCS30 is the count packet amount for each radio bearer, for example, the charging rate is determined for each radio bearer may calculate the fee by multiplying the amount of packets. For example, RAT using mobile communication such as LTE or 5G may be equal to higher than RAT using wireless LAN communication.
[0086]
　Further, in FIG. 12, in step S51, with respect MeNB21 is SeNB22, processing for transmitting the Traffic count report request message to request transmission of Traffic data is shown. In contrast, SeNB22, without receiving a Traffic count report request message, in accordance with count rule, autonomously may send Traffic count report message to MeNB21. For example, SeNB22 is the timing when Report period indicated in count rule is expired, may send a Traffic count report message to MeNB21.
[0087]
　The message used to send the Traffic data is not limited to the message shown in Figure 12. Shown in FIG. 12, step S53 and subsequent message is a message defined in 3GPP. For example, a step S53 subsequent messages may be a new message is used not currently defined in 3GPP. For example, instead of the E-RAB MODIFICATION INDICATION message may be a new message is used to TRAFFIC REPORT INDICATION message. Further, instead of the E-RAB MODIFICATION CONFIRM message may be a new message is used to TRAFFIC REPORT CONFIRM message. Further, instead of the Modify Bearer Request message may be a new message is used to Traffic Report Request message. Further, instead of the Modify Bearer Response message may be a new message is used to Traffic Report Response message.
[0088]
　As described above, by using the communication system according to a second embodiment of the present disclosure, may be in MeNB21, counting the amount of packets sent and received for each radio bearer. Further, PGW26 is able to use the information about the amount of counted packets in MeNB21, generates billing information. Than this, PGW26, even if the Dual Connectivity is configured in MeNB21 and SeNB22, it is possible to charge for each radio bearer.
[0089]
　Furthermore, HSS24 as subscriber information of UE 20, or permitted to configure the Dual Connectivity, further holds information on RAT to limit the use in Dual Connectivity as subscriber information. From this, it is possible to UE20 is prevented from constituting the Dual Connectivity using RAT that is not allowed by the subscriber information. For example, UE 20 is, the case where RAT which can be used are entered into cheap contract is limited to 2G and 3G will be described. In this case, it is possible to prevent the use UE20 is, when constructing the Dual Connectivity, the RAT of 5G like that can be used by entering into expensive contracts.
[0090]
　(Third Embodiment)
　Subsequently, the flow of multiple PDN Connectivity establishing process according to the third embodiment of the present disclosure will be described with reference to FIGS. 13 and 14. 13 and 14, UE 20 is shows the flow of processing when connected to a plurality of PDN. Before the process of FIG. 13 is executed, the process of FIG. 9 and FIG. 10 is executed, UE 20 is assumed to establish the PGW26 and PDN Connectivity.
[0091]
　First, UE 20 sends a PDN Connectivity Request message to MME23 through MeNB21 (S61). PDN Connectivity Request message includes an APN which is information for identifying a PDN that UE20 is connected.
[0092]
　Then, MME23 is, S1 Setup process in FIG. 7, X2 Setup process in FIG. 8, using the information acquired in the Attach process in FIGS. 9 and 10, with respect to data via the PDN Connectivity to establish new, the MeNB21 It determines whether to count the packet amount of each radio bearer (S62). The information obtained in the Attach process, for example, comprise a DC not allowed A relates Access Restriction Data and UE20 about UE20 obtained from HSS24. Further, S1 Setup process, X2 Setup process, the information obtained in the Attach process, DC Support transmitted from MeNB21 and UE 20, and includes a DC Traffic count support indication sent from MeNB21.
[0093]
　Step S68 in step S63 to 14 in FIG. 13, a detailed description thereof will be omitted because it is similar to that of step S35 to step S40 of FIG. 9. However, 13 and 14, SGW25, between the PGW26 different PGW26_1, sending and receiving the Create Session Request message and the Create Session Response message.
[0094]
　Then, MME23 is to MeNB21, transmits a Bearer Setup Request message including the PDN Connectivity Accept message (S69). PDN Connectivity Accept message is transmitted through the MeNB21, it is transmitted to the UE 20.
[0095]
　PDN Connectivity Accept message includes a DC not allowed as a parameter. DC not allowed A contained in PDN Connectivity Accept message is information indicating whether to permit the UE20 constitutes a Dual Connectivity. Bearer Setup Request message includes in addition to the PDN Connectivity Accept message, DC Traffic count support indication as a parameter, count rule, the DC not allowed A. DC not allowed A contained Bearer Setup Request message is information indicating whether to permit MeNB21 constitutes a Dual Connectivity. MME23, when indicating that permit MeNB21 is in DC not allowed A constituting the Dual Connectivity, the DC Traffic count support indication, relative MeNB21, indicating that counting the amount of packets for each radio bearer.
[0096]
　Step S70 ~ S77 are omitted steps S42 ~ S49 and hence detailed similar description of Figure 10. However, RRC Connection Reconfiguration message in step S71 includes a PDN Connectivity Accept message instead of ATTACH Accept message. Further, in step S73, instead of the Initial Context Setup Response message step S45 in FIG. 10, Bearer Setup Response message is sent.
[0097]
　As described above, by executing the PDN Connectivity establishment process of FIG. 13 and FIG. 14, for each PDN Connectivity, it is possible to determine whether to count the packet amount of each radio bearer eNB.
[0098]
　(Embodiment 4)
　Next, with reference to FIG. 15, described E-UTRAN initiated E-RAB modification procedure. Figure 15 refers to the E-UTRAN initiated E-RAB modification procedure that is described in 3GPP TS 23.401 V13.6.1 (2016-03) 5.4.7 Section. 15, when MeNB21 executes Dual Connectivity, shows a flow of processing for adding a SeNB22.
[0099]
　First, MeNB21 sends a SeNB Addition Request message to SeNB22 (S81). SeNB Addition Request message, as a parameter, including the count rule.
[0100]
　Then, SeNB22 transmits the SeNB Addition, Request Acknowledge message to the MeNB21 (S82). Then, MeNB21 is to UE 20, and transmits the RRC Connection Reconfiguration message (S83). Then, UE 20 is to MeNB21, transmits the RRC Connection Reconfiguration complete message (S84). Then, SeNB22 is to MeNB21, transmits the SeNB Addition, Request Complete message (S85). By processing is executed in steps S81 ~ S85, SeNB22 is added as eNB constituting the Dual Connectivity.
[0101]
　Then, MeNB21 is to MME23, transmits an E-RAB Modification Indication message (S86). E-RAB Modification Indication message includes a DC Charging activated as a parameter. Step S87 ~ S90 are omitted and a detailed description is the same as the steps S46 ~ S49 of FIG. 10.
[0102]
　Then, MME23 is to MeNB21, transmits an E-RAB Modification Confirm message (S91).
[0103]
　As described above, by executing the E-UTRAN initiated E-RAB modification procedure of FIG. 15, MeNB21, when you add the SeNB22 as eNB constituting the Dual Connectivity, be transmitted DC Charging activated to MME23 it can.
[0104]
　On the other hand, in FIG. 10, the Attach processing UE 20, MeNB21 transmits the DC Charging activated to MME23. That is, FIG. 15, actually in a wireless network, since the configuration Dual Connectivity, MeNB21 has been shown to count the packets of each radio bearer. From this, by running the E-UTRAN initiated E-RAB modification procedure of FIG. 15, until Dual Connectivity is constructed, it is possible to perform the charging processing by PGW counts the amount of packets.
[0105]
　In the case of executing the E-UTRAN initiated E-RAB modification procedure of FIG. 15, in step S73 in step S45 and 14 in FIG. 10, MeNB21 is the message to be transmitted, and not to include DC Charging activated.
[0106]
　(Embodiment 5)
　Subsequently, with reference to FIG. 16, described S1 release procedure according to the fifth embodiment. Figure 16 shows the processing executed at the time of shifting the UE20 to Idle state. Specifically, FIG. 16 shows a process of releasing the communication bearer related UE20 between the MeNB21 and the core network.
[0107]
　First, MeNB21 is, with the transition to the Idle state of the UE 20, decides to start the S1 release procedure (S101). Then, MeNB21 is to SeNB22, transmits a Traffic count report request message (S102). MeNB21, in order to transmit data relating to packet amount of each radio bearer counted in SeNB22, transmits a Traffic count report request message to the SeNB22.
[0108]
　Then, SeNB22 transmits a Traffic count report message to MeNB21 (S103). Traffic count report message includes a Traffic data indicating the data concerning packet amount of each radio bearer SeNB22 has counted.
[0109]
　Then, MeNB21 transmits the S1 UE Context Release Request message to MME23 (S104). S1 UE Context Release Request message, MeNB21, along with Traffic data collected from SeNB22, including Traffic data is information about the amount of packets counted in MeNB21.
[0110]
　Then, MME23 is to SGW25, transmits a Release Access Bearers Request message (S105). Modify Bearer Request message includes the same Traffic data and Traffic data contained in S1 UE Context Release Request message. Then, SGW25 is to PGW26, sends a Modify Bearer Request message (S106). Traffic data contained in Modify Bearer Request message in step S106 is similar to the Traffic data contained in the Modify Bearer Request message in step S105.
[0111]
　Then, PGW26 sends a Modify Bearer Response message to the SGW25 (S107). Then, SGW25 sends a Release Access Bearers Response message to the MME23 (S108). Then, MME23 is to MeNB21, transmits the S1 UE Context Release Command message (S109).
[0112]
　The message used to send the Traffic data is not limited to the message shown in Figure 16. Shown in FIG. 16, step S104 and subsequent message is a message defined in 3GPP. For example, in step S104 subsequent messages may be a new message is used not currently defined in 3GPP. For example, instead of the Modify Bearer Request message may be a new message is used to Traffic Report Request message. Further, instead of the Modify Bearer Response message may be a new message is used to Traffic Report Response message.
[0113]
　Subsequently, with reference to FIG. 17, PDN GW initiated bearer deactivation procedure is described according to the fifth embodiment. 17, PGW26 have shown the process to be executed when it is decided to drop the communication bearer related UE 20. This process, UE 20 is may be performed in the active state.
[0114]
　First, PGW26 is to SGW25, sends a Delete Bearer Request message (S 111). Delete Bearer Request message includes the identification information of the UE20. Then, SGW25 sends a Delete Bearer Request message sent from PGW26 to MME23 (S112). Then, MME23 sends a Delete Bearer Request message sent from SGW25 to MeNB21 (S113). Then, MeNB21 is to UE 20, and transmits the RRC Connection Reconfiguration message (S114). Then, UE 20 is to MeNB21, transmits the RRC Connection Reconfiguration complete message (S115).
[0115]
　Then, MeNB21 is to SeNB22, transmits a Traffic count report request message (S116). MeNB21, in order to transmit data relating to packet amount of each count radio bearers in SeNB22, transmits a Traffic count report request message to the SeNB22.
[0116]
　Then, SeNB22 transmits a Traffic count report message to MeNB21 (S117). Traffic count report message includes a Traffic data indicating the data concerning packet amount of each radio bearer SeNB22 has counted.
[0117]
　Then, MeNB21 transmits a Deactive Bearer Response message to the MME23 (S118). Deactive Bearer Response message, MeNB21, along with Traffic data collected from SeNB22, including Traffic data is information about the amount of packets counted in MeNB21.
[0118]
　Then, MME23 sends a Deactive Bearer Response message sent from MeNB21 to SGW25 (S119). Furthermore, SGW25 transmits a Deactive Bearer Response message sent from MME23 to PGW26 (S120).
[0119]
　Subsequently, with reference to FIG. 18, a description will be given MME initiated bearer deactivation procedure according to the fifth embodiment. 18, MME23 have shown the process to be executed when it is decided to drop the communication bearer related UE 20. This process, UE 20 is may be performed in the active state.
[0120]
　First, MME23 is, to SGW25, to send a Delete Bearer Command message (S131). Delete Bearer Command message includes the identification information of the UE 20. Then, SGW25 sends a Delete Bearer Command message sent from MME23 to PGW26 (S132).
[0121]
　Step S133 ~ S142 is omitted steps S 111 ~ S120 and hence detailed similar description of Figure 17.
[0122]
　As described above, by executing the processing in FIGS. 16 to 18, when releasing the communication bearer relating UE 20, MeNB21 can collect data on packet amount of each radio bearer counted in SeNB22 .
[0123]
　(Embodiment 6)
　Subsequently, the X2 HO (Hand Over) procedure will be described with reference to FIG. 19. Figure 19 shows a flow of a handover process that does not involve a change in MME23. Further, FIG. 19, the handover target eNB may indicate a flow of the handover process in the case where it is possible to count the amount of packets for each radio bearer.
[0124]
　First, a handover source Source eNB determines to perform a handover process of UE 20 (S151). For example, MeNB21 may be a Source eNB. In this case, MeNB21 first, between SeNB22, collects Traffic data measured by it in SeNB22 follow the steps indicated in step S51, and step S52 in FIG. 12. Next, Source eNB is to Target eNB, and transmits a Handover Request message (S152). Target eNB is the eNB forms a communication area of ​​the destination UE 20. Handover Request message, Count rule, Traffic data, and includes a DC not allowed. Count rule is, Source eNB is a Count rule that was applied when counting the amount of packets for each radio bearer. Traffic data is, Source eNB is information about the amount of packets counted for each radio bearer. DC not allowed A is information indicating whether UE20 is permitted to configure the Dual Connectivity.
[0125]
　Then, Target eNB is to Source eNB, and transmits a Handover Request Ack message (S153). Handover Request message, including a DC Traffic count support indication as a parameter. DC Traffic count support indication is, Target eNB is information indicating that it is possible to count the amount of packets for each radio bearer.
[0126]
　Next, Source eNB is to UE 20, and transmits the RRC Connection Reconfiguration message (S154). Then, UE 20 is to Target eNB, and transmits an RRC Connection Reconfiguration complete message (S155).
[0127]
　Then, Target eNB in ​​order to switch the eNB of the destination UE 20, transmits a Path Switch Request message to the MME23 (S156). Then, MME23 is to SGW25, sends a Modify Bearer Request message (S157). Then, SGW25 is to MME23, sends a Modify Bearer Response message (S158). Then, MME23 is to Target eNB, and transmits a Path swithc Request Ack message (S159). Then, Target eNB is to Source eNB, and transmits a UE Context Release message (S160).
[0128]
　By executing the processing in FIG. 19, between the Source eNB and the Target eNB, the handover process is completed. Further, by executing the processing in FIG. 19, the processing for counting the amount of packets for each radio bearer, is taken over from the Source eNB to the Target eNB.
[0129]
　Subsequently, with reference to FIGS. 20 and 21, it will be described X2 HO (Hand Over) procedure. 20 and 21 show a flow of the handover processing without change of MME23. Further, FIGS. 20 and 21, the handover target eNB may indicate a flow of the handover process when it is not possible to count the amount of packets for each radio bearer.
[0130]
　Step S171 and S172 are omitted and a detailed description is the same as the steps S151 and S152 in FIG. 19. Then, Target eNB is to Source eNB, and transmits a Handover Request Ack message (S173). Handover Request Ack message does not include the DC Traffic count support indication, or, including the DC Traffic count not support indication. Target eNB is the Handover Request Ack message, not including DC Traffic count support indication, or by including a DC Traffic count not support indication, and notifies the inability counting the amount of packets for each radio bearer to the Source eNB.
[0131]
　Next, Source eNB is to MME23, transmits an E-RAB MODIFICATION INDICATION message (S174). E-RAB MODIFICATION INDICATION message includes a Traffic data and DC Traffic count stop. DC Traffic count stop is information indicating to stop the counting of the packet amount of each radio bearer in Source eNB. Or, DC Traffic count stop may be information indicating that stops counting the packet amount of each radio bearer in Source eNB.
[0132]
　Then, MME23 is to SGW25, sends a Modify Bearer Request message (S175). Modify Bearer Request message includes a Traffic data and DC Traffic count stop contained in the E-RAB MODIFICATION INDICATION message received at step S174. Then, SGW25 sends a Modify Bearer Request message received from MME23 to PGW26 (S176).
[0133]
　Then, PGW26 is to SGW25, sends a Modify Bearer Response message (S177). Then, SGW25 sends a Modify Bearer Response message received from the PGW26 to MME23 (S178). Then, MME23 is to Source eNB, and transmits an E-RAB MODIFICATION CONFIRM message (S179).
[0134]
　Steps S180 ~ in Figure 21 S186 is omitted steps S154 ~ S160 and hence detailed similar description of Figure 19.
[0135]
　By executing the processing in FIGS. 20 and 21, Target eNB is, if it is not possible to count the amount of packets for each radio bearer, Source eNB via MME23 and SGW25, the PGW26, packets for each radio bearer it can be notified to stop the counting of the amount. From this, PGW26 may initiate the process of counting the amount of packets relating to UE 20. In other words, PGW26 can take over the process of counting the amount of packets relating to UE 20, the Source eNB.
[0136]
　Subsequently, the S1 HO procedure will be described with reference to FIGS. 22 and 23. 22 and 23 show a flow of the handover process involving a change of MME23. Further, FIGS. 22 and 23, the handover target eNB may indicate a flow of the handover process in the case where it is possible to count the amount of packets for each radio bearer.
[0137]
　First, a handover source Source eNB determines to perform a handover process of UE 20 (S191). For example, MeNB21 may be a Source eNB. In this case, MeNB21 first, between SeNB22, collects Traffic data measured by it in SeNB22 follow the steps indicated in step S51, and step S52 in FIG. 12. Next, Source eNB is to Source MME, transmits the Handover Required message (S192). Source MME may be a MME23. Handover Required message, including the Source to Target transparent container. In addition, Source to Target transparent container is information including a count rule and Traffic data.
[0138]
　Next, Source MME is to Target MME, transmits the Forward Relocation Request message (S193). Forward Relocation Request message, including the Source to Target transparent container. Source MME is, the Source to Target transparent container that has been transmitted from the Source eNB, to add a DC not allowed. Source MME sends a Forward Relocation Request message that contains the Source to Target transparent container you add a DC not allowed. DC not allowed A to Source MME adds is information indicating whether it is possible UE20 constitutes a Dual Connectivity. DC not allowed to Source MME has been added, Source MME is, is a subscriber information obtained from the HSS24.
[0139]
　Then, Target MME is the Target eNB, and transmits a Handover Request message (S194). Handover Request message, including the Source to Target transparent container that has been transmitted from the Source MME. Then, Target eNB is to Target MME, transmits the Handover Request Acknowledge message (S195). Handover Request Acknowledge include Traget to Source transparent container. In addition, Target to Source transparent container comprises a DC Traffic count support indication. DC Traffic count support is, Target eNB is information indicating that it is possible to count the amount of packets for each radio bearer.
[0140]
　Then, Target MME is the Source MME, transmits a Forward Relocation Response message (S196). Forward Relocation Response message includes a DC Traffic count support indication and Target to Source transparent container. DC Traffic count support indication is, Target MME is information indicating whether or not it corresponds to the count of the packet amount of each radio bearer in Target eNB. Target to Source transparent container is the same as the transmitted Target to Source transparent container from Target eNB.
[0141]
　Next, Source MME is the Source eNB, and transmits a Handover Command message (S197). Handover Command message includes a DC Traffic count support indication and Target to Source transparent container. Target to Source transparent container is the same as the transmitted Target to Source transparent container from Target MME. Next, Source eNB is to UE 20, transmits the Handover Command message (S198).
[0142]
　Turning to FIG. 23, then, UE 20 transmits a Handover Confirm message to the Target eNB (S199). Then, Target eNB sends a Handover Notify message to Target MME (S200). Then, Target MME is the Source MME, transmits the Forward Relocation Complete Notification message (S201). Next, Source MME is to Target MME, transmits the Forward Relocation Complete Acknowledge message (S202).
[0143]
　Then, Target MME is to SGW25, sends a Modify Bearer Request message (S203). Then, SGW25 is to Target MME, transmits a Modify Bearer Response message (S204). Then, UE 20, Target eNB, and in Target MME, TAU (Tracking Area Update) Procedure is performed (S205).
[0144]
　Next, Source MME is the Source eNB, and transmits a UE Context Release Command message (S206). Next, Source eNB is to Source MME, transmits a UE Context Release Complete message (S207).
[0145]
　Subsequently, with reference to FIGS. 24 to 26, will be described S1 HO procedure. 24 to 26 show a flow of the handover process involving a change of MME23. Further, FIGS. 24 to 26, the handover target eNB may indicate a flow of the handover process when it is not possible to count the amount of packets for each radio bearer.
[0146]
　Step S211 ~ S214, the detailed description thereof is omitted because it is similar to that of steps S191 ~ S194 in FIG. 22. Then, Target eNB is to Target MME, transmits the Handover Request Acknowledge message (S215). Handover Request Acknowledge include Traget to Source transparent container. In addition, Target to Source transparent container does not include a DC Traffic count support indication, or, including the DC Traffic count not support indication. That, Target eNB is to Target MME, notifying that it is impossible to count the amount of packets for each radio bearer.
[0147]
　Then, Target MME is the Source MME, transmits a Forward Relocation Response message (S216). Forward Relocation Response message does not include the DC Traffic count support indication, or, including the DC Traffic count not support indication. In addition, Forward Relocation Response message includes the Target to Source transparent container. Not including DC Traffic count support indication, or to include a DC Traffic count not support indication is, Target MME is information indicating that it can not correspond to the count of the packet amount of each radio bearer in Target eNB. Target to Source transparent container is the same as the transmitted Target to Source transparent container from Target eNB.
[0148]
　Next, Source MME is the Source eNB, and transmits a Handover Command message (S217). Handover Command message does not include the DC Traffic count support indication, or, including the DC Traffic count not support indication. In addition, Handover Command message includes a Target to Source transparent container. Information included in the Handover Command message was received in step S216, it is similar to the information included in the Forward Relocation Response message.
[0149]
　Step S218 ~ S225 are substantially the same as the steps S174 ~ S179 in FIG. 20. However, in FIG. 25 shows a flow of the handover process involving a change of MME. Therefore, FIG. 25, between the Source MME and Target MME, indicating that the Modify Bearer Request message and Modify Bearer Response messages are transmitted and received.
[0150]
　Step S227 ~ S235 in step S226 and FIG. 26 in FIG. 25, a detailed description thereof will be omitted because it is similar to that of steps S199 ~ S207 in step S198 and FIG. 23 in FIG. 22.
[0151]
　As described above, by executing the processing according to the sixth embodiment, when the handover processing relating to UE20 performs a packet amount of each radio bearer Source eNB has been counted, be taken over into the Target eNB it can. Also, Target eNB is, if it is not possible to count the packets of each radio bearer, PGW26 is able to take over the count of the amount of packets for UE 20.
[0152]
　Then hereinafter, UE 20 has been described in several embodiments above, MeNB21, and configuration examples of MME23 will be described. Figure 27 is a block diagram showing a configuration example of MeNB21. Referring to FIG. 27, MeNB21 includes an RF transceiver 1001, a network interface 1003, a processor 1004, and memory 1005. RF transceiver 1001 performs an analog RF signal processing to communicate with the UEs. RF transceiver 1001 may include a plurality of transceivers. RF transceiver 1001 is coupled to antenna 1002 and the processor 1004. RF transceiver 1001 receives the modulated symbol data (or OFDM symbol data) from the processor 1004, generates a transmission RF signal and provides a transmit RF signal to the antenna 1002. Also, RF transceiver 1001 to generate a baseband received signal based on the reception RF signal received by an antenna 1002, and supplies it to the processor 1004.
[0153]
　Network interface 1003, network node (eg, other eNBs, Mobility Management Entity (MME), Serving Gateway (S-GW), and TSS or ITS servers) is used to communicate with. Network interface 1003 may include, for example, a network interface card that complies with the IEEE 802.3 series (NIC).
[0154]
　The processor 1004, performs data plane processing and control plane processing including digital baseband signal processing for wireless communication. For example, in the case of LTE and LTE-Advanced, a digital baseband signal processing by the processor 1004, PDCP layer, RLC layer may include a signal processing of the MAC layer, and the PHY layer. Further, the signal processing by the processor 1004 may include signal processing GTP-U · UDP / IP layer in the X2-U interface and S1-U interface. The control plane processing by the processor 1004, X2AP protocol may include a process of S1-MME protocol and the RRC protocol.
[0155]
　Processor 1004 may include multiple processors. For example, the processor 1004 is a modem processor that performs digital baseband signal processing (eg, DSP), X2-U interface and S1-U interface of the GTP-U · UDP / IP layer processor for performing signal processing (eg, DSP), and a protocol stack processor for performing control plane processing (eg, may include a CPU or MPU).
[0156]
　Memory 1005 is constituted by a combination of volatile and nonvolatile memory. Memory 1005 may include a physically independent plurality of memory devices. Volatile memory may be, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. The non-volatile memory, a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. Memory 1005 may include a storage that is remotely located from the processor 1004. In this case, the processor 1004 may access the memory 1005 via the I / O interfaces that are not network interface 1003 or illustrated.
[0157]
　Memory 1005 may store software modules (computer program) including instructions and data for processing by MeNB21 described in several embodiments described above. In some implementations, the processor 1004, the software module that executes from the memory 1005 may be configured to perform processing of MeNB21 described in the above embodiments.
[0158]
　Figure 28 is a block diagram showing a configuration example of a UE 20. Radio Frequency (RF) transceiver 1101 performs an analog RF signal processing for communicating with MeNB21 and SeNB22. Analog RF signal processing performed by the RF transceiver 1101 includes a frequency up-conversion, the frequency down-conversion, and amplification. RF transceiver 1101 is coupled to antenna 1102 and the base band processor 1103. That, RF transceiver 1101 receives the modulated symbol data (or OFDM symbol data) from the baseband processor 1103, generates a transmission RF signal and provides a transmit RF signal to the antenna 1102. Also, RF transceiver 1101 to generate a baseband received signal based on the reception RF signal received by an antenna 1102, and supplies it to the baseband processor 1103.
[0159]
　Baseband processor 1103 performs control plane processing and digital baseband signal processing for wireless communication (data plane processing). Digital baseband signal processing, (a) data compression / decompression, (b) segmentation / concatenation of data, generation / decomposition of (c) transmission format (transmission frame), (d) transmission channel coding / decoding , including generation of (e) modulation (symbol mapping) / demodulation, and OFDM symbol data by (f) Inverse Fast Fourier Transform (IFFT) (baseband OFDM signal). On the other hand, the control plane processing, layer 1 (eg, transmission power control), Layer 2 (eg, radio resource management, and hybrid automatic repeat request (HARQ) process), and layer 3 (eg, attach, mobility and call management including communication management signaling) related.
[0160]
　For example, in the case of LTE and LTE-Advanced, a digital baseband signal processing by a baseband processor 1103, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, includes a signal processing of the MAC layer, and a PHY layer But good. Further, the control plane processing by baseband processor 1103, Non-Access Stratum (NAS) protocol, RRC protocol, and may include a process of MAC CE.
[0161]
　Baseband processor 1103, a modem processor that performs digital baseband signal processing (eg, Digital Signal Processor (DSP)) and protocol stack processor for performing control plane processing (eg, Central Processing Unit (CPU), or Micro Processing Unit it may include (MPU)). In this case, the protocol stack processor for performing control plane processing may be shared with an application processor 1104 which will be described later.
[0162]
　The application processor 1104, CPU, MPU, also referred to as a microprocessor or processor cores. The application processor 1104 may include a plurality of processors (multiple processor cores). The application processor 1104, a memory 1106 or illustrated which do not result system read from the memory a software program (Operating System (OS)) and various application programs (e.g., call application, WEB browser, a mailer, a camera operation application, music playback by running the application), to implement the various functions of the UE 20.
[0163]
　In some implementations, as indicated by the dashed line (1105) in FIG. 29, the baseband processor 1103 and an application processor 1104 may be integrated on a single chip. In other words, the baseband processor 1103 and an application processor 1104 may be implemented as a single System on Chip (SoC) device 1105. SoC devices, sometimes referred to as system Large Scale Integration (LSI) or chipset.
[0164]
　Memory 1106 is a volatile memory or nonvolatile memory, or a combination thereof. Memory 1106 may include a physically independent plurality of memory devices. Volatile memory may be, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. The non-volatile memory, a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. For example, memory 1106, a baseband processor 1103, an application processor 1104, and may contain accessible external memory device from SoC1105. Memory 1106, within baseband processor 1103, within the application processor 1104, or may include an integrated chip memory device within SoC1105. Furthermore, memory 1106 may include a memory in the Universal Integrated Circuit Card (UICC).
[0165]
　Memory 1106 may store software modules (computer program) including instructions and data for processing by the UE20 described in several embodiments described above. In some implementations, the baseband processor 1103 or the application processor 1104, the software module that executes from the memory 1106 may be configured to perform processing of UE20 described in the above embodiments.
[0166]
　Figure 29 is a block diagram showing a configuration example of MME23. Referring to FIG. 29, MME23 a network interface 1201, a processor 1202, and memory 1203. Network interface 1201, network node (eg, eNodeB130, MME, P-GW) are used to communicate with. Network interface 1201 may include, for example, a network interface card that complies with the IEEE 802.3 series (NIC).
[0167]
　The processor 1202 reads and executes the software from the memory 1203 (a computer program), the process of MME23 described with reference to sequence diagrams and flowcharts in the above embodiments. The processor 1202, e.g., a microprocessor, MPU, or a CPU. Processor 1202 may include multiple processors.
[0168]
　Memory 1203 is constituted by a combination of volatile and nonvolatile memory. Memory 1203 may include a storage that is remotely located from the processor 1202. In this case, the processor 1202 may access the memory 1203 via the I / O interface (not shown).
[0169]
　In the example of FIG. 29, the memory 1203 is used for storing software modules. Processor 1202, these software modules that run from the memory 1203, it is possible to perform the processing of MME23 described in the above embodiment.
[0170]
　As described with reference to FIGS. 27 to 29, each of the processors UE 20, MeNB21, and MME23 has in the above embodiment includes instructions for causing the algorithm described with reference to the drawings in the computer executing one or more programs.
[0171]
　In the above example, the program may be stored using a non-transitory computer readable media of various types (non-transitory computer readable medium), it can be supplied to the computer. Non-transitory computer readable media include with various types of entities (tangible storage medium). Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tape, hard disk drive), magneto-optical recording medium (e.g. optical disk), CD-ROM (Read Only Memory), CD-R, CD-R / W, a semiconductor memory (e.g., a mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access memory)) includes a. The program may be provided to a computer using a temporary computer readable media of various types (transitory computer readable medium). Examples of transitory computer readable media include electric signals, optical signals, and electromagnetic waves. Transitory computer readable media, wired communication path such as electrical wires and optical fibers, or via a wireless communication path can provide the program to a computer.
[0172]
　The present disclosure is not limited to the above embodiments, but can be appropriately changed without departing from the spirit. The present disclosure may be implemented in combination in the form of respective embodiments as appropriate.
[0173]
　Having described the present disclosure with reference to the embodiment, the present disclosure is not intended to be limited by the foregoing. The present disclosure of the configuration and details may be various modifications that those skilled in the art within the scope of disclosure can be understood.
[0174]
　This application claims priority based on Japanese Patent Application No. 2016-105254, filed on May 26, 2016, the entire disclosure of which is incorporated herein.
[0175]
　Some or all of the above embodiments, can be described as the following notes, not limited to the following.
　(Supplementary Note 1)
　and a communication terminal configured to communicate with the plurality of communication devices using different radio bearers for each of the plurality of communication devices,
　the communication device, whether to measure the traffic of each radio bearer communication system and a configured controller to determine a.
　(Supplementary Note 2)
　The control device,
　wherein the communication device receives the count support information on whether the communication device can measure the communication amount for each radio bearer, the communication system of statement 1.
　(Supplementary Note 3)
　The control device,
　using said count support information, and a communication permission information indicating whether or not it is permitted to communicate with the plurality of communication devices by using the communication terminal a plurality of radio bearers , to the communication device, a communication system according determines, in appendix 2 whether to measure the traffic of each radio bearer.
　(Supplementary Note 4)
　The control device,
　a gateway device to be connected to the billing system, and receives the communication permission information from the subscriber information management device, a communication system according to Appendix 3.
　(Supplementary Note 5)
　The control device,
　From the communication device receives the start information indicating the start of process of measuring the communication traffic for each radio bearer, transmitting the start information to the gateway device, a communication system according to Appendix 4.
　(Supplementary Note 6)
　The control device,
　a communication system according to the communication apparatus, and transmits the count support information, and transmits the count rule information, any one of Appendices 2-5.
　(Supplementary Note 7)
　The communication apparatus
　receives the instruction information instructing to measure the communication amount for each radio bearer from the control unit, transmits the traffic information including a traffic measured for each radio bearer to the control device to, the communication system according to any one of Supplementary Notes 1 to 6.
　(Supplementary Note 8)
　The control device,
　when receiving the traffic information, and transmits the traffic information to the gateway device to be connected to the charging system, the communication system according to Appendix 7.
　(Supplementary Note 9)
　when the communication terminal communicates with the plurality of communication devices using different radio bearers for each of the plurality of communication devices, at least one communication device of the plurality of communication devices, the communication amount for each radio bearer the a control unit determines whether or not to measure, control device.
　(Supplementary Note 10)
　a transmission unit that transmits to the controller the support information indicating whether or not it is possible to the plurality of communication with the different radio bearers for each of the plurality of communication devices,
　The support information, and, based on the communication permission information indicating whether or not the own device is allowed to communicate with a plurality of communication devices using a plurality of radio bearers, the device itself by using a plurality of radio bearers a receiving unit that whether communication with a plurality of communication apparatus receives a result of determination from the control device,
　instructs the determination result, to communicate with a plurality of communication devices using a plurality of radio bearers if it contains information, the communication terminal comprising: a control unit that executes a process of setting a plurality of communication devices and a plurality of radio bearers, the.
　(Supplementary Note 11)
　when the communication terminal communicates with the plurality of communication devices using different radio bearers for each of the plurality of communication devices, at least one communication device of the plurality of communication devices, the communication amount for each radio bearer the determination whether or not to measure,
　transmits the determination result to the communication device, a communication method.
　(Supplementary Note 12)
　A communication method in a communication system,
　the control device from the communication device for communicating with the communication terminal and the wireless transmits the information about the radio bearer used for communications of the communication terminal, a communication method.
　(Supplementary Note 13)
　information about the radio bearer is information indicating whether or not to support measuring the communication amount for each radio bearer The communication method according to Supplementary Note 12.
　(Supplementary Note 14)
　The control device, based on the information on the radio bearer, the communication device determines whether to measure the communication amount for each radio bearer The communication method according to Supplementary Note 12 or 13.
　(Note 15)
　Wherein the control device, the information on the radio bearer, and transmits to the gateway device for transferring communication related to the communication terminal, communication method according to any one of Appendixes 12 to 14.
　(Supplementary Note 16)
　A communication system,
　a communication device for communicating with the communication terminal and the wireless,
　and a control device,
　transmitted to the control device from the communication device, information about the radio bearer used for communications of the communication terminal to, communication system.
　(Supplementary Note 17)
　The information about the radio bearer is information indicating whether or not to support measuring the communication amount for each radio bearer, the communication system of statement 16.
　(Supplementary Note 18)
　The control device, based on said information about the radio bearer, the communication device determines whether to measure the communication amount for each radio bearer, the communication system of statement 16 or 17.
　(Supplementary Note 19)
　The control device, the information on the radio bearer, and transmits to the gateway device for transferring communication related to the communication terminal, a communication system according to any one of appendixes 16 to 18.
　(Supplementary Note 20)
　A communication device,
　means for communicating with the communication terminal and the wireless,
　and means for transmitting information on radio bearers used for communication of the communication terminal, the control device, the communication device.
　(Supplementary Note 21)
　information about the radio bearer is information indicating whether or not to support measuring the communication amount for each radio bearer, the communication apparatus according to note 20.
DESCRIPTION OF SYMBOLS
[0176]
　11 the communication terminal
　12 the communication device
　13 the communication device
　14 the control device
　20 UE
　21 MeNB
　22 SeNB
　23 MME
　24 HSS
　25 SGW
　26 PGW
　27 PCRF
　28 AF
　29 OFCS
　30 OCS
　41 transceiver
　42 transmitting and receiving unit
　43 control unit
　51 base station communication unit
　52 SGW The communication unit
　53 HSS communication unit
　54 control unit
　61 UE communication unit
　62 base station communication unit
　63 C-Plane communication unit
　64 U-Plane communication unit
　65 control unit
　66 data measuring section

WE claims

A communication terminal configured to communicate with the plurality of communication devices using different radio bearers for each of the plurality of communication devices,
　the communication device, to determine whether to measure the traffic of each radio bearer communication system and a configured control apparatus.
[Requested item 2]
　The control device,
　from the communication device, receiving the count support information on whether the communication device can measure the communication amount for each radio bearer, the communication system according to claim 1.
[Requested item 3]
　Wherein the control device,
　using said count support information, and a communication permission information indicating whether or not it is permitted to communicate with the plurality of communication devices by using the communication terminal a plurality of radio bearers, the communication device to determine whether to measure the traffic of each radio bearer, the communication system according to claim 2.
[Requested item 4]
　It said control device,
　a gateway device to be connected to the billing system, and receives the communication permission information from the subscriber information management device, a communication system according to claim 3.
[Requested item 5]
　The control device,
　from the communication device receives the start information indicating the start of process of measuring the communication traffic for each radio bearer, transmitting the start information to the gateway device, a communication according to claim 4 system.
[Requested item 6]
　Wherein the control device,
　a communication system according to the communication apparatus, and transmits the count support information, and transmits the count rule information, in any one of claims 2 to 5.
[Requested item 7]
　The communication device,
　when receiving the instruction information instructing to measure the traffic for each radio bearer from the control device, transmits the traffic information including a traffic measured for each radio bearer to the control device, according to claim communication system according to any one of 1 to 6.
[Requested item 8]
　It said controller,
　when receiving the traffic information, and transmits the traffic information to the gateway device to be connected to the charging system, the communication system according to claim 7.
[Requested item 9]
　When the communication terminal communicates with the plurality of communication devices using different radio bearers for each of the plurality of communication devices, wherein the at least one communication device of the plurality of communication devices, or to measure the communication amount for each radio bearer comprises determining control means whether the controller.
[Requested item 10]
　Transmitting means and, for transmitting the support information indicating whether or not it is possible to the plurality of communication with the different radio bearers for each of the plurality of communication devices to the controller
　the support information, and the own device is a plurality of radio bearers based on the communication permission information indicating whether it is permitted to communicate with the plurality of communication devices using, whether or not the own device communicates with a plurality of communication devices using a plurality of radio bearers it is judged and receiving means for the determination result received from the control device,
　on the determination result, when using a plurality of radio bearers includes information for instructing to communicate with a plurality of communication devices, a plurality of communication devices and a plurality of communication terminal and a control unit, a for executing processing of setting a radio bearer.
[Requested item 11]
　When the communication terminal communicates with the plurality of communication devices using different radio bearers for each of the plurality of communication devices, wherein the at least one communication device of the plurality of communication devices, or to measure the communication amount for each radio bearer It determines whether,
　and transmits the determination result to the communication device, a communication method.
[Requested item 12]
　A communication method in a communication system,
　the control device from the communication device for communicating with the communication terminal and the wireless transmits the information about the radio bearer used for communications of the communication terminal, a communication method.
[Requested item 13]
　The information about the radio bearer is information indicating whether or not to support measuring the communication amount for each radio bearer The communication method according to claim 12.
[Requested item 14]
　The controller, based on the information on the radio bearer, the communication device determines whether to measure the communication amount for each radio bearer The communication method according to claim 12 or 13.
[Requested item 15]
　Wherein the control device, the information on the radio bearer, and transmits to the gateway device for transferring communication related to the communication terminal, communication method according to any one of claims 12 to 14.
[Requested item 16]
　A communication system,
　a communication device for communicating with the communication terminal and the wireless,
　and a control unit,
　and transmits to the control device from the communication device, information about the radio bearer used for communications of the communication terminal, the communication system .
[Requested item 17]
　The information about the radio bearer is information indicating whether or not to support measuring the communication amount for each radio bearer, the communication system according to claim 16.
[Requested item 18]
　Wherein the control device, based on said information about the radio bearer, the communication device determines whether to measure the communication amount for each radio bearer, the communication system according to claim 16 or 17.
[Requested item 19]
　Wherein the control device, the information about the radio bearer, and transmits to the gateway device for transferring communication related to the communication terminal, a communication system according to any one of claims 16 to 18.
[Requested item 20]
　A communication device,
　means for communicating with the communication terminal and the wireless,
　and means for transmitting information on radio bearers used for communication of the communication terminal, the control device, the communication device.
[Requested item 21]
　The information about the radio bearer is information indicating whether or not to support measuring the communication amount for each radio bearer, the communication apparatus according to claim 20.