Title: Radio communication system, base station, mobile station and processing method
Technical field

[0001]
　The present invention relates to a radio communication system, a base station, a mobile station, and a processing method.
BACKGROUND ART

[0002]
　Conventionally, mobile communication such as LTE (Long Term Evolution) is known (for example, see Non-Patent Documents 1 to 13 below). In LTE, aggregation that cooperates with WLAN (Wireless Local Area Network) at a level of radio access is under study (for example, see Non-Patent Documents 14 and 15 below). Integration and interworking at the wireless level between LTE and WLAN are being studied (for example, see Non-Patent Document 16 below).
[0003]
　In addition, when a WLAN is used, a technique of transferring data from RRC (Radio Resource Control) to MAC (Media Access Control) layer is known (for example, see the following Patent Document 1). . Also, a technique for sharing LTE PDCP (Packet Data Convergence Protocol) between LTE and WLAN is known (see, for example, Patent Document 2 below). Further, in WLAN or the like, a technique for controlling transmission of data based on QoS (Quality of Service) information is known.
Prior Art Document

Patent literature

[0004]
Patent Document 1: International Publication No. 2012/121757
Patent Document 2: International Publication No. 2013/068787
Non-patent literature

[0005]
Non-patent document 1: 3 GPP TS 36.300 v 12.5.0, March 2015
Non-patent document 2: 3 GPP TS 36.211 v 12.5.0, March 2015
Non-Patent Document 3: 3 GPP TS 36.212 v 12.4 . 0, March 2015
Non-Patent Document 4: 3 GPP TS 36.213 v 12.5.0, March 2015
Non-Patent Document 5: 3 GPP TS 36.321 v 12.5.0, March 2015
Non-Patent Document 6: 3 GPP TS 36.322 v 12.2.0, March 2015
Non-Patent Document 7: 3 GPP TS 36.323 v 12.3.0, March 2015
Non-Patent Document 8: 3 GPP TS 36.331 v 12.5.0, 2015 March
Non-Patent Document 9: 3 GPP TS 36.413 v 12.5.0, March 2015
Non-Patent Document 10: 3 GPP TS 36.423 v 12.5.0, March 2015
Non-Patent Document 11: 3 GPP TS 36.425 v 12.1.0, March 2015
Non-Patent Document 12: 3
GPP TR 36.842 v 12.0.0, December 2013 Non-Patent Document 13: 3 GPP TR 37. 834
v 12.0.0, December 2013 Non-Patent Document 14: 3 GPP RWS-140027, June 2014
Non-Patent Document 15: 3 GPP RP-140237, March 2014
Non-Patent Document 16: 3 GPP RP-150510, 2015 March
Summary of the invention

Problem to be Solved by Invention

[0006]
　However, in the above-described conventional technique, when data is transmitted by simultaneously using the first wireless communication such as LTE and the second wireless communication such as WLAN, the data received by the first wireless communication on the receiving side and the data It is difficult to control the order between the data received by the wireless communication of FIG. For this reason, data transmission using the first wireless communication and the second wireless communication at the same time can not be performed in some cases.
[0007]
　In one aspect, the present invention aims at providing a wireless communication system, a base station, a mobile station and a processing method capable of performing data transmission using the first wireless communication and the second wireless communication at the same time .
Means for solving the problem

[0008]
　According to an aspect of the present invention, in order to solve the above-described problems and achieve the object, the base station transmits a second wireless communication different from the first wireless communication by a control unit that controls the first wireless communication , And the mobile station can perform data transmission with the base station using the first radio communication or the second radio communication, and the mobile station can perform data transmission between the base station and the mobile station When transmitting data by using the second wireless communication, a processing section in a station on the transmitting side out of the base station and the mobile station, the processing section for performing the first wireless communication performs processing Performs tunneling processing on the data after the processing of the convergence layer for performing the first wireless communication and transmits the data to the station on the receiving side among the base station and the mobile station, The data transmitted from the station on the transmitting side by the first wireless communication And the data transmitted from the station on the transmitting side by the second wireless communication, based on a first wireless communication process, a base station, a mobile station, and a base station A processing method is proposed.
Effect of the Invention

[0009]
　According to one aspect of the present invention, there is the effect that it is possible to perform data transmission using the first wireless communication and the second wireless communication at the same time.
Brief Description of the Drawings

[0010]
FIG. 1 is a diagram showing an example of a wireless communication system according to a first embodiment.
FIG. 2 is a diagram showing another example of the wireless communication system according to the first embodiment.
3 is a diagram showing an example of a wireless communication system according to Embodiment 2. FIG.
FIG. 4 is a diagram showing an example of a terminal according to a second embodiment.
FIG. 5 is a diagram showing an example of a hardware configuration of a terminal according to a second embodiment.
FIG. 6 is a diagram showing an example of a base station according to a second embodiment.
FIG. 7 is a diagram showing an example of a hardware configuration of a base station according to a second embodiment.
FIG. 8 is a diagram showing an example of a protocol stack in the wireless communication system according to the second embodiment.
9 is a diagram showing an example of layer 2 in the wireless communication system according to Embodiment 2. FIG.
FIG. 10 is a diagram showing an example of an IP header of an IP packet transmitted in the radio communication system according to the second embodiment.
FIG. 11 is a diagram showing an example of values ​​of a ToS field included in an IP header of an IP packet transmitted in the wireless communication system according to the second embodiment.
FIG. 12 is a diagram showing an example of aggregation by LTE-A and WLAN in the radio communication system according to the second embodiment.
FIG. 13 is a diagram showing an example of QoS control based on a ToS field in the radio communication system according to the second embodiment.
FIG. 14 is a diagram showing an example of AC classification in the wireless communication system according to the second embodiment.
FIG. 15 is a diagram showing an example of aggregation in the wireless communication system according to the second embodiment.
FIG. 16 is a diagram showing an example of mapping of QoS classes to ACs applicable to the radio communication system according to the second embodiment.
FIG. 17 is a flowchart illustrating an example of processing by a transmitting-side apparatus in a wireless communication system according to a second embodiment.
FIG. 18 is a diagram showing an example of a case where a plurality of EPS bearers have the same QoS class in the radio communication system according to the second embodiment.
FIG. 19 is a diagram showing an example of implementation of an outer IP layer using 3GPP protocol in the second embodiment.
20 is a diagram showing another example of the implementation of the outer IP layer using the 3GPP protocol in the second embodiment. FIG.
FIG. 21 is a diagram showing still another example of the implementation of the outer IP layer using the 3GPP protocol in the second embodiment.
FIG. 22 is a diagram showing an example of implementation of an outer IP layer using the new tunneling protocol in the second embodiment.
FIG. 23 is a diagram showing another example of the implementation of the outer IP layer using the new tunneling protocol in the second embodiment.
FIG. 24 is a diagram showing still another example of the implementation of the outer IP layer using the new tunneling protocol in the second embodiment.
25 is a diagram showing an example of a method for identifying EPS bearers using UL TFTs in the radio communication system according to Embodiment 3. FIG.
FIG. 26 is a diagram showing another example of a method for identifying EPS bearers using UL TFTs in the radio communication system according to the third embodiment.
FIG. 27 is a diagram showing an example of a TFT acquisition method in the wireless communication system according to the third embodiment.
FIG. 28 is a diagram showing an example of a method for identifying an EPS bearer using a DL TFT in the wireless communication system according to the third embodiment.
FIG. 29 is a diagram showing another example of a method of identifying EPS bearers using DL TFTs in the radio communication system according to the third embodiment.
30 is a diagram showing an example of a method of identifying an EPS bearer using a virtual IP flow in the wireless communication system according to the third embodiment. FIG.
31 is a diagram showing another example of a method for identifying an EPS bearer using a virtual IP flow in the wireless communication system according to the third embodiment. FIG.
32 is a diagram showing an example of a method for identifying an EPS bearer using a VLAN in the wireless communication system according to Embodiment 3. FIG.
FIG. 33 is a diagram showing another example of a method of identifying an EPS bearer using a VLAN in the wireless communication system according to the third embodiment.
FIG. 34 is a diagram showing an example of a method of identifying an EPS bearer using GRE tunneling in the radio communication system according to the third embodiment.
FIG. 35 is a diagram showing another example of a method for identifying an EPS bearer using GRE tunneling in the radio communication system according to the third embodiment.
FIG. 36 is a diagram showing an example of a method of identifying an EPS bearer using PDCPoIP in the radio communication system according to the third embodiment.
37 is a diagram showing another example of a method of identifying EPS bearers using PDCPoIP in the radio communication system according to Embodiment 3. FIG.
[FIG. 38] FIG. 38 is a diagram (No. 1) for explaining processing on data transmitted by the WLAN in the radio communication system according to the fourth embodiment.
[FIG. 39] FIG. 39 is a diagram (part 2) for explaining processing on data transmitted by the WLAN in the radio communication system according to Embodiment 4.
FIG. 40 is a sequence diagram showing an example of processing in the wireless communication system according to the fourth embodiment.
FIG. 41 is a sequence diagram showing a method of notifying a MAC address by another RRC message in processing in the radio communication system according to the fourth embodiment.
FIG. 42 is a sequence diagram showing a method of notifying the MAC address by another RRC message in the process in the radio communication system according to the fourth embodiment.
FIG. 43 is a sequence diagram showing another example of processing in the wireless communication system according to the fourth embodiment.
FIG. 44 is a diagram showing an example of a packet format in ARP applicable to the fourth embodiment.
MODE FOR CARRYING OUT THE INVENTION

[0011]
　DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of a radio communication system, a base station, a mobile station and a processing method according to the present invention will be described in detail below with reference to the drawings.
[0012]
First Embodiment
　FIG. 1 is a diagram showing an example of a radio communication system according to a first embodiment. As shown in FIG. 1, the radio communication system 100 according to the first embodiment includes a base station 110 and a mobile station 120. In the radio communication system 100, data transmission using the first radio communication 101 and the second radio communication 102 at the same time can be performed between the base station 110 and the mobile station 120.
[0013]
　The first wireless communication 101 and the second wireless communication 102 are mutually different wireless communication (wireless communication method). The first wireless communication 101 is a cellular communication such as LTE or LTE-A as an example. The second wireless communication 102 is, for example, a WLAN. However, the first wireless communication 101 and the second wireless communication 102 are not limited to these, and communication of various methods can be used. In the example shown in FIG. 1, the base station 110 is a base station that can perform the first wireless communication 101 and the second wireless communication 102, for example, with the mobile station 120.
[0014]
　When transmitting data by simultaneously using the first wireless communication 101 and the second wireless communication 102, the base station 110 and the mobile station 120 transmit a first wireless And sets the communication path of the communication 101 between the base station 110 and the mobile station 120. The base station 110 and the mobile station 120 set the communication path of the second wireless communication 102 for transmitting data of the first wireless communication 101 between the base station 110 and the mobile station 120. Then, the base station 110 and the mobile station 120 simultaneously transmit the data by using the set communication paths of the first wireless communication 101 and the second wireless communication 102 simultaneously.
[0015]
　First, the downlink that transmits data from the base station 110 to the mobile station 120 will be described. The base station 110 includes a control unit 111 and a processing unit 112. The control unit 111 controls the first wireless communication 101. Further, the control unit 111 controls the second wireless communication 102. As an example, the control unit 111 is a processing unit such as RRC that performs radio control between the base station 110 and the mobile station 120. However, the control unit 111 is not limited to the RRC, but may be various processing units that control the first wireless communication 101.
[0016]
　The processing unit 112 performs processing for performing the first wireless communication 101. For example, the processing unit 112 is a processing unit that processes data to be transmitted in the first wireless communication 101. As an example, the processing unit 112 is a data link layer processing unit such as PDCP, RLC (Radio Link Control), MAC, etc. However, the processing unit 112 is not limited thereto, and various processing units for performing the first wireless communication 101 can be used.
[0017]
　The processing of the processing unit 112 for performing the first wireless communication 101 is controlled by the control unit 111. The processing unit 112 establishes a convergence layer for performing the first wireless communication 101 when transmitting data from the base station 110 to the mobile station 120 using the wireless communication of the second wireless communication 102. This convergence layer includes a process for dividing data to be transmitted between the base station 110 and the mobile station 120 into a first wireless communication 101 and a second wireless communication 102.
[0018]
　As an example, it is the PDCP layer to the convergence layer. However, the convergence layer is not limited to the PDCP layer, but can be various layers. The convergence layer may also be referred to as a convergence point, a termination point, a branch point, a split function, or a routing function, and if it means that it is a schedule point of data of the first wireless communication 101 and the second wireless communication 102 , It is not limited to such a designation. Hereafter, we will use a convergence layer as such a typical designation.
[0019]
　The processing unit 112 converts the data processed by the convergence layer for data to be transmitted from the base station 110 to the mobile station 120 using the second wireless communication 102 by a sequence number (SN: Sequence Number) And the like to the mobile station 120 by tunneling. As a result, the data to the mobile station 120 can be transmitted by the second wireless communication 102 while including the sequence number. In other words, the PDU of the first wireless communication 101 can be transmitted transparently by the second wireless communication 102.
[0020]
　On the other hand, the mobile station 120 performs the reception processing of the data transmitted from the base station 110 by the first radio communication 101 and the data transmitted from the base station 110 by the second radio communication 102 to the first Based on the processing of the radio communication 101 of FIG. For example, the mobile station 120 may perform sequence control based on the sequence number. This makes it possible to perform data transmission using the first wireless communication 101 and the second wireless communication 102 at the same time. Therefore, it is possible to improve the data transmission speed, for example.
[0021]
　Next, the uplink that transmits data from the mobile station 120 to the base station 110 will be described. The mobile station 120 includes a processing unit 121. Like the processing unit 112 of the base station 110, the processing unit 121 is a processing unit for performing the first wireless communication 101. As an example, the processing unit 121 is a data link layer processing unit such as PDCP, RLC, MAC, etc. However, the processing unit 121 is not limited thereto, and various processing units for performing the first wireless communication 101 can be used.
[0022]
　The processing of the processing unit 121 for performing the first wireless communication 101 is controlled by the control unit 111 of the base station 110. The processing unit 121 establishes a convergence layer for performing the first wireless communication 101 when transmitting data from the mobile station 120 to the base station 110 using the wireless communication of the second wireless communication 102. As described above, this convergence layer includes a process for dividing data transmitted between the base station 110 and the mobile station 120 into a first wireless communication 101 and a second wireless communication 102.
[0023]
　The processing unit 121 adds a header including a sequence number and the like by processing of the convergence layer with respect to data to be transmitted from the mobile station 120 to the base station 110 using the second wireless communication 102 after processing of the convergence layer And transmits the PDU to the base station 110 by tunneling. As a result, the data to the base station 110 can be transmitted by the second wireless communication 102 while including the sequence number.
[0024]
　On the other hand, the base station 110 controls the sequence control of the data transmitted from the mobile station 120 by the first radio communication 101 and the data transmitted from the mobile station 120 by the second radio communication 102 to the sequence It can be done based on number. Therefore, it is possible to perform data transmission using the first wireless communication 101 and the second wireless communication 102 at the same time.
[0025]
　As described above, the transmitting station of the base station 110 and the mobile station 120 transmits data to be transmitted using the second wireless communication 102 with a header including a sequence number or the like added by the processing of the convergence layer Transmitted PDU by tunneling. Thereby, in the station on the receiving side, the order control between the data transmitted from the mobile station 120 by the first radio communication 101 and the data transmitted from the mobile station 120 by the second radio communication 102 is It can be done based on the sequence number. Therefore, it is possible to perform data transmission using the first wireless communication 101 and the second wireless communication 102 at the same time.
[0026]
　FIG. 2 is a diagram showing another example of the radio communication system according to the first embodiment. In FIG. 2, parts similar to those shown in FIG. 1 are denoted by the same reference numerals, and description thereof is omitted. In FIG. 1, the base station 110 is a base station capable of performing the first radio communication 101 and the second radio communication 102 with the mobile station 120, but as shown in FIG. 2, Base stations 110 A and 110 B may be provided in place of station 110.
[0027]
　The base station 110 A is a base station capable of performing the first wireless communication 101 with the mobile station 120. The base station 110 B is a base station connected to the base station 110 A and capable of performing the second wireless communication 102 with the mobile station 120.
[0028]
　In the example shown in FIG. 2, the base station 110 A performs data transmission with the mobile station 120 using the second wireless communication 102 via the base station 110 B. In this case, the control unit 111 and the processing unit 112 shown in FIG. 1 are provided in the base station 110 A, for example. Further, the control unit 111 controls the second wireless communication 102 with the mobile station 120 via the base station 110 B.
[0029]
　First, the downlink that transmits data from the base station 110 A to the mobile station 120 will be described. The processing unit 112 of the base station 110 A uses the second wireless communication 102 to convert the data to be transmitted to the mobile station 120 after the processing of the convergence layer with the header including the sequence number etc. by the processing of the convergence layer And forwards the PDU to the base station 110 B by tunneling. Thereby, the data can be transmitted to the mobile station 120 via the base stations 110A and 110B. The base station 110 B transmits the data transferred from the base station 110 A to the mobile station 120 by the second wireless communication 102.
[0030]
　Next, the uplink that transmits data from the mobile station 120 to the base station 110 A will be described. The processing unit 121 of the mobile station 120 uses the second wireless communication 102 to convert the data to be transmitted to the base station 110 after the processing of the convergence layer with the header including the sequence number etc. by the processing of the convergence layer To the base station 110 B by tunneling. The base station 110B transfers the data transmitted from the mobile station 120 by the second wireless communication 102 to the base station 110A. As a result, data to the base station 110 A can be transmitted to the base station 110 A using the second wireless communication 102.
[0031]
　As described above, according to the radio communication system 100 of the first embodiment, data transmission using the first radio communication 101 and the second radio communication 102 at the same time between the base station 110 and the mobile station 120 is performed It is possible to do. Therefore, it is possible to improve the data transmission speed, for example.
[0032]
　Next, details of the wireless communication system 100 according to the first embodiment shown in FIG. 1 will be described using Embodiment Modes 2 to 4. Since Embodiments 2 to 4 can be regarded as examples embodying the above-described Embodiment 1, it is possible to implement in combination with Embodiment 1.
[0033]
Second Embodiment
　FIG. 3 is a diagram showing an example of a wireless communication system according to a second embodiment. As shown in FIG. 3, the radio communication system 300 according to the second embodiment includes a UE 311, eNBs 321 and 322, and a packet core network 330. The wireless communication system 300 is, for example, a mobile communication system such as LTE-A stipulated in 3 GPP, but the communication standard of the wireless communication system 300 is not limited thereto.
[0034]
　The packet core network 330 is, for example, EPC (Evolved Packet Core) defined in 3 GPP, but it is not particularly limited thereto. In addition, the core network defined in 3GPP may be called SAE (System Architecture Evolution) in some cases. The packet core network 330 includes an SGW 331, a PGW 332, and an MME 333.
[0035]
　The UE 311 and the eNBs 321 and 322 form a radio access network by performing radio communication. The radio access network formed by the UE 311 and the eNBs 321 and 322 is, for example, an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) defined in 3 GPP, but is not particularly limited thereto.
[0036]
　The UE 311 is a terminal located in the cell of the eNB 321 and performing radio communication with the eNB 321. As an example, the UE 311 communicates with another communication device via a path via the eNB 321, the SGW 331, and the PGW 332. As another example, another communication device that communicates with the UE 311 is a communication terminal different from the UE 311, a server, or the like. Communication between the UE 311 and another communication device is, for example, data communication or voice communication, but is not particularly limited thereto. Voice communication is, for example, VoLTE (Voice over LTE), but it is not particularly limited thereto.
[0037]
　The eNB 321 is a base station that forms a cell 321 a and performs radio communication with the UE 311 located in the cell 321 a. The eNB 321 relays communication between the UE 311 and the SGW 331. The eNB 322 is a base station that forms a cell 322 a and performs radio communication with UEs located in the cell 322 a. The eNB 322 relays communication between the UE located in the cell 322 a and the SGW 331.
[0038]
　The eNB 321 and the eNB 322 may be connected by, for example, a physical or logical interface between base stations. The interface between the base stations is, for example, the X 2 interface, but the interface between the base stations is not particularly limited thereto. The eNB 321 and the SGW 331 are connected by, for example, a physical or logical interface. The interface between the eNB 321 and the SGW 331 is, for example, the S1-U interface, but it is not particularly limited thereto.
[0039]
　The SGW 331 is a serving gateway that accommodates the eNB 321 and performs U-plane (User plane) processing in communication via the eNB 321. For example, the SGW 331 performs U-plane processing in communication of the UE 311. The U-plane is a function group for transmitting user data (packet data). Further, the SGW 331 may accommodate the eNB 322 and perform U-plane processing in communication via the eNB 322.
[0040]
　The PGW 332 is a packet data network gateway for connecting to an external network. The external network is, for example, the Internet, but it is not limited thereto. For example, the PGW 332 relays user data between the SGW 331 and the external network. Further, for example, the PGW 332 performs IP address allocation 301 for assigning an IP address to the UE 311 so that the UE 311 transmits and receives the IP flow.
[0041]
　The SGW 331 and the PGW 332 are connected by, for example, a physical or logical interface. The interface between the SGW 331 and the PGW 332 is, for example, the S5 interface, but is not particularly limited thereto.
[0042]
　The MME 333 (Mobility Management Entity: Mobility Management Entity) accommodates the eNB 321 and performs processing of C-plane (Control plane) in communication via the eNB 321. For example, the MME 333 performs processing of the C-plane in the communication of the UE 311 via the eNB 321. The C-plane is, for example, a group of functions for controlling a call and a network between devices. As an example, the C-plane is used for connection of a packet call, setting of a route for transmitting user data, control of a handover, and the like. Further, the MME 333 may accommodate the eNB 322 and perform C-plane processing in communication via the eNB 322.
[0043]
　The MME 333 and the eNB 321 are connected by, for example, a physical or logical interface. The interface between the MME 333 and the eNB 321 is, for example, the S1-MME interface, but is not particularly limited thereto. The MME 333 and the SGW 331 are connected by, for example, a physical or logical interface. The interface between the MME 333 and the SGW 331 is, for example, the S 11 interface, but is not particularly limited thereto.
[0044]
　In the wireless communication system 300, the IP flow to be transmitted or received by the UE 311 is classified (distributed) into EPS bearers 341 to 34 n and transmitted via the PGW 332 and the SGW 331. EPS bearers 341 to 34 n are IP flows in Evolved Packet System (EPS). The EPS bearers 341 to 34 n become radio bearers 351 to 35 n (Radio Bearer) in the radio access network formed by the UE 311 and the eNBs 321 and 322. Control of the entire communication such as setting of the EPS bearers 341 to 34 n, security setting, mobility management and the like is performed by the MME 333.
[0045]
　In the LTE network, IP flows classified as EPS bearers 341 to 34 n are transmitted by, for example, a GTP (GPRS Tunneling Protocol) tunnel set between the respective nodes. Each of the EPS bearers 341 to 34 n is uniquely mapped to the radio bearers 351 to 35 n and wirelessly transmitted in consideration of QoS.
[0046]
　In the communication between the UE 311 and the eNB 321 of the radio communication system 300, aggregation by LTE-A and WLAN is performed, in which the LTE-A traffic is transmitted using the LTE-A and the WLAN at the same time. As a result, the traffic between the UE 311 and the eNB 321 can be distributed to the LTE-A and the WLAN, and the throughput in the radio communication system 300 can be improved. The first wireless communication 101 shown in FIG. 1 can be, for example, wireless communication by LTE-A. The second wireless communication 102 shown in FIG. 1 can be, for example, wireless communication by WLAN. The aggregation by LTE-A and WLAN will be described later.
[0047]
　It should be noted that the designation of aggregation is an example and is often used in the sense of using a plurality of communication frequencies (carriers). Apart from aggregation, it is sometimes referred to as integration in the sense that multiple systems are integrated and used. Hereafter, aggregation is used as a representative designation.
[0048]
　The base stations 110, 110 A and 110 B shown in FIGS. 1 and 2 can be realized by eNBs 321 and 322, for example. The mobile station 120 shown in FIG. 1 and FIG. 2 can be realized by the UE 311, for example.
[0049]
　FIG. 4 is a diagram showing an example of the terminal according to the second embodiment. The UE 311 shown in FIG. 3 can be realized by the terminal 400 shown in FIG. 4, for example. The terminal 400 includes a wireless communication unit 410, a control unit 420, and a storage unit 430. The wireless communication unit 410 includes a wireless transmission unit 411 and a wireless reception unit 412. Each of these configurations is connected so as to be able to input and output signals and data in one direction or bidirectionally. Further, the wireless communication unit 410 can perform wireless communication (first wireless communication 101) by LTE-A, wireless communication by WLAN (second wireless communication 102), for example.
[0050]
　The radio transmission unit 411 transmits user data and a control signal by wireless communication via an antenna. The radio signal transmitted by the radio transmission unit 411 may include arbitrary user data, control information, and the like (to be encoded, modulated, etc.). The wireless reception unit 412 receives user data and control signals via wireless communication via an antenna. The wireless signal received by the wireless reception unit 412 may include arbitrary user data, control signals, etc. (to be encoded, modulated, etc.). Note that the antenna may be common for transmission and reception.
[0051]
　The control unit 420 outputs user data and control signals to be transmitted to other radio stations to the radio transmission unit 411. Further, the control unit 420 acquires the user data and the control signal received by the wireless reception unit 412. The control unit 420 performs input and output of user data, control information, programs, and the like with the storage unit 430 to be described later. In addition, the control unit 420 performs input and output of user data and control signals to be exchanged with other communication devices and the like with the wireless communication unit 410. The control unit 420 performs various controls in the terminal 400 besides these. The storage unit 430 stores various types of information such as user data, control information, and programs.
[0052]
　The processing unit 121 of the mobile station 120 shown in FIG. 1 can be realized by the control unit 420, for example.
[0053]
　FIG. 5 is a diagram showing an example of the hardware configuration of the terminal according to the second embodiment. The terminal 400 shown in FIG. 4 can be realized by the terminal 500 shown in FIG. 5, for example. The terminal 500 includes, for example, an antenna 511, an RF circuit 512, a processor 513, and a memory 514. These constituent elements are connected so that various signals and data can be inputted and outputted via a bus, for example.
[0054]
　The antenna 511 includes a transmission antenna for transmitting a radio signal and a reception antenna for receiving a radio signal. Further, the antenna 511 may be a shared antenna that transmits and receives radio signals. The RF circuit 512 performs RF (Radio Frequency) processing of a signal received by the antenna 511 and a signal transmitted by the antenna 511. The RF processing includes, for example, frequency conversion between the baseband band and the RF band.
[0055]
　The processor 513 is, for example, a CPU (Central Processing Unit), a DSP (Digital Signal Processor), or the like. Further, the processor 513 may be realized by a digital electronic circuit such as ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array), LSI (Large Scale Integration).
[0056]
　The memory 514 can be realized by a RAM (Random Access Memory) such as SDRAM (Synchronous Dynamic Random Access Memory), a ROM (Read Only Memory), and a flash memory. The memory 514 stores, for example, user data, control information, programs, and the like.
[0057]
　The wireless communication unit 410 shown in FIG. 4 can be realized by, for example, the antenna 511 and the RF circuit 512. The control unit 420 shown in FIG. 4 can be realized by the processor 513, for example. The storage unit 430 shown in FIG. 4 can be realized by a memory 514, for example.
[0058]
　FIG. 6 is a diagram illustrating an example of a base station according to the second embodiment. Each of the eNBs 321 and 322 shown in FIG. 3 can be realized by the base station 600 shown in FIG. 6, for example. As shown in FIG. 6, the base station 600 includes, for example, a wireless communication unit 610, a control unit 620, a storage unit 630, and a communication unit 640. The wireless communication unit 610 includes a wireless transmission unit 611 and a wireless reception unit 612. Each of these configurations is connected so as to be able to input and output signals and data in one direction or bidirectionally. Further, the wireless communication unit 610 can perform wireless communication (first wireless communication 101) by LTE-A, wireless communication by WLAN (second wireless communication 102), for example.
[0059]
　The wireless transmission unit 611 transmits the user data and the control signal by wireless communication via the antenna. The radio signal transmitted by the radio transmission unit 611 can include arbitrary user data, control information, and the like (to be encoded, modulated, etc.). The wireless reception unit 612 receives user data and control signals via wireless communication via an antenna. The wireless signal received by the wireless reception unit 612 can include arbitrary user data, control signals, etc. (to be encoded, modulated, etc.). Note that the antenna may be common for transmission and reception.
[0060]
　The control unit 620 outputs user data and control signals to be transmitted to other radio stations to the radio transmission unit 611. Further, the control unit 620 acquires the user data and the control signal received by the wireless reception unit 612. The control unit 620 performs input and output of user data, control information, programs, and the like with the storage unit 630 to be described later. Further, the control unit 620 performs input and output of user data and control signals to be exchanged with other communication devices and the like with the communication unit 640 to be described later. The control unit 620 performs various controls in the base station 600 in addition to these.
[0061]
　The storage unit 630 stores various types of information such as user data, control information, and programs. The communication unit 640 transmits and receives user data and control signals to and from other communication devices, for example, by wired signals.
[0062]
　The control unit 111 and the processing unit 112 of the base station 110 shown in FIG. 1 can be realized by the control unit 620, for example.
[0063]
　FIG. 7 is a diagram showing an example of the hardware configuration of the base station according to the second embodiment. The base station 600 shown in FIG. 6 can be realized by the base station 700 shown in FIG. 7, for example. The base station 700 includes an antenna 711, an RF circuit 712, a processor 713, a memory 714, and a network IF 715. These constituent elements are connected so that various signals and data can be inputted and outputted via a bus, for example.
[0064]
　The antenna 711 includes a transmission antenna for transmitting a radio signal and a reception antenna for receiving a radio signal. In addition, the antenna 711 may be a shared antenna that transmits and receives radio signals. The RF circuit 712 performs RF processing of a signal received by the antenna 711 and a signal transmitted by the antenna 711. The RF processing includes, for example, frequency conversion between the baseband band and the RF band.
[0065]
　The processor 713 is, for example, a CPU, a DSP, or the like. Further, the processor 713 may be realized by a digital electronic circuit such as ASIC, FPGA, LSI, or the like.
[0066]
　The memory 714 can be realized by, for example, a RAM such as an SDRAM, a ROM, or a flash memory. The memory 714 stores user data, control information, programs, and the like, for example.
[0067]
　The network IF 715 is a communication interface that communicates with the network, for example, by wire. The network IF 715 may include, for example, an Xn interface for performing wired communication between base stations.
[0068]
　The wireless communication unit 610 shown in FIG. 6 can be realized by, for example, the antenna 711 and the RF circuit 712. The control unit 620 shown in FIG. 6 can be realized by the processor 713, for example. The storage unit 630 shown in FIG. 6 can be realized by, for example, the memory 714. The communication unit 640 shown in FIG. 6 can be realized by the network IF 715, for example.
[0069]
　FIG. 8 is a diagram showing an example of a protocol stack in the wireless communication system according to the second embodiment. For example, the protocol stack 800 shown in FIG. 8 can be applied to the wireless communication system 300 according to the second embodiment. The protocol stack 800 is a LTE-A protocol stack defined in 3GPP. Layer groups 801 to 805 are layer groups indicating processes in the UE 311, the eNB 321, the SGW 331, the PGW 332, and the server of the external network, respectively.
[0070]
　In the case of transmitting the IP flow in the radio communication system 300, the IP flow is filtered in order to perform the handling according to the QoS class for each IP flow. For example, for the downlink where the UE 311 receives the IP flow, the PGW 332 performs packet filtering on the IP flow to classify the IP flow into the EPS bearers 341 to 34 n.
[0071]
　For the uplink where the UE 311 transmits the IP flow, the filtering rule of the packet is notified from the PGW 332 to the UE 311. Based on the filtering rule notified from the PGW 332, the UE 311 performs packet filtering on the IP flow and classifies the IP flow into EPS bearers 341 to 34 n.
[0072]
　For example, in the uplink, the PGW 332 performs filtering of the IP flow by the filter layer 811 (Filter) included in the IP layer (IP) in the layer group 804 of the PGW 332. In the downlink, the UE 311 performs filtering of the IP flow by a filter layer 812 (Filter) included in the IP layer (IP) in the layer group 801 of the UE 311.
[0073]
　Also, in order to perform QoS control (QoS management) in a router in the LTE network, the PGW 332 (in the case of downlink) or the UE 311 (in the case of uplink) adds QoS (Type of Service) to the ToS Set the value.
[0074]
　The packet filtering by the PGW 332 or the UE 311 is performed using, for example, 5-tuple (transmission source IP address, transmission source port number, protocol type). The filtering rule of packet filtering is called a TFT (Traffic Flow Template), for example. It should be noted that there may be EPS bearers for which no TFT is set among the EPS bearers 341 to 34 n.
[0075]
　When filtering IP flow using TFTs, IP flow can be classified into 11 types of EPS bearers at the maximum. One bearer of the EPS bearers 341 to 34 n is called a default bearer (default bearer). The default bearer is generated when the PGW 332 assigns an IP address to the UE 311 and always exists until the IP address assigned to the UE 311 is released. A bearer different from the default bearer among the EPS bearers 341 to 34 n is called a dedicated bearer. Dedicated bearers can be generated and released appropriately according to the situation of the user data to be transmitted.
[0076]
　FIG. 9 is a diagram illustrating an example of layer 2 in the wireless communication system according to the second embodiment. For the wireless communication system 300 according to the second embodiment, the processing shown in FIG. 9 can be applied as a layer 2 processing as an example. The process shown in FIG. 9 is Layer 2 processing of LTE-A stipulated by 3 GPP. As shown in FIG. 9, layer 2 of LTE-A includes PDCP 910, RLC 920, and MAC 930.
[0077]
　The PDCP 910 includes ROHC (Robust Header Compression) which performs header compression of incoming IP datagram and processing related to security. Processes related to security include confidentiality and integrity protection, for example. In normal LTE-A communication, the user data is forwarded to the lower layer (eg, layer 1) after these processes of the PDCP 910 are performed.
[0078]
　Also, for example, when implementing dual connectivity, the UE 311 can simultaneously communicate with two base stations (for example, eNBs 321 and 322) at the maximum. MCG Bearer 901 (Master Cell Group Bearer) is the radio base bearer of the main base station.
[0079]
　In addition, a split bearer 902 (split bearer) and an SCG bearer 903 (secondary cell group bearer) can be attached to the MCG bearer 901. In the case of using the split bearer 902, when the user data is forwarded from the layer 2 to the lower layer (for example, the layer 1), the user data is forwarded to only one base station or the user data is forwarded to the two base stations Can be selected.
[0080]
　The RLC 920 includes a primary process before wireless transmission of user data. For example, the RLC 920 includes a division of user data (Segm: SEGmentation) for adjusting the user data to a size corresponding to the radio quality. In addition, ARQ (Automatic Repeat reQuest) or the like may be included in the RLC 920 for retransmission of user data that could not be corrected in the lower layer. When the user data is forwarded to the lower layer, the EPS bearer is mapped to the corresponding logical channel (Logical Channel) and wirelessly transmitted.
[0081]
　The MAC 930 includes control of wireless transmission. For example, the MAC 930 includes a process of performing packet scheduling and performing HARQ (Hybrid Automatic Repeat reQuest) of transmission data. In carrier aggregation, HARQ is performed for each carrier to be aggregated.
[0082]
　The transmitting side adds an LCID (Logical Channel Identifier) ​​to the MAC SDU (MAC Service Data Unit) which is user data in the MAC 930 and transmits it. The receiving side converts the radio bearer into an EPS bearer by using the LCID added by the transmitting side in the MAC 930.
[0083]
　FIG. 10 is a diagram illustrating an example of an IP header of an IP packet transmitted in the wireless communication system according to the second embodiment. In the wireless communication system 300 according to the second embodiment, for example, an IP packet having an IP header 1000 shown in FIG. 10 is transmitted. The IP header 1000 includes, for example, a source address 1001 indicating a transmission source and a destination address 1002 indicating a destination.
[0084]
　In addition, the IP header 1000 includes a ToS field 1003 for QoS. The above-described QoS control is performed based on the value of the ToS field 1003, for example. In addition, the IP header 1000 includes a protocol field 1004 in which the protocol number of the transport layer corresponding to the higher layer is stored.
[0085]
　FIG. 11 is a diagram illustrating an example of values ​​of ToS fields included in an IP header of an IP packet transmitted in the wireless communication system according to the second embodiment. The "first 3 bits" in the table 1100 shown in FIG. 11 indicates the IP precidence corresponding to the first 3 bits in the ToS field 1003 shown in FIG. 10 and can take 2 3 = 8 patterns. In the table 1100, the patterns of the eight patterns indicate that the higher the priority (priority) is, the higher the pattern is.
[0086]
　For example, "111", which has the highest priority in the IP presence of the ToS field 1003, indicates that the IP packet corresponds to the network control, and is reserved for control of routing and the like. Also, "110" having the second highest priority in the IP pre-cid of the ToS field 1003 indicates that the IP packet corresponds to the Internet control, and is reserved for control such as routing.
[0087]
　In the example shown in FIG. 11, the case where the IP presence of the ToS field 1003 is used as the priority information of the QoS has been described. However, the priority information of the QoS is not limited to this, and for example, using the DSCP (Differentiated Services Code Point) field It is also good. DSCP is a field corresponding to the first 6 bits in the ToS field 1003.
[0088]
　FIG. 12 is a diagram showing an example of aggregation by LTE-A and WLAN in the radio communication system according to the second embodiment. Layer 2 processing in aggregation by LTE-A and WLAN is based on the processing of dual connectivity described above taking into consideration the backward compatibility of LTE-A, for example.
[0089]
　The IP flow 1201 is an IP flow by Hypertext Transfer Protocol (Hypertext Transfer Protocol) between the UE 311 and the eNB 321. The IP flow 1202 is an IP flow based on FTP (File Transfer Protocol) between the UE 311 and the eNB 321.
[0090]
　The non-aggregation processing 1211 shows the processing in the case where the IP flows 1201 and 1202 are transmitted by LTE-A without using a WLAN. This non-aggregation processing 1211 corresponds to transmission of data using wireless communication by the first wireless communication 101 shown in FIG. 1. In the non-aggregation processing 1211, processing is performed in the order of PDCP, RLC, LTE-MAC, and LTE-PHY for each of the IP flows 1201 and 1202. The PDCP, RLC, and LTE-MAC are PDCP 910, RLC 920 and MAC 930 shown in FIG. 9, for example. LTE-PHY is a physical layer in LTE-A.
[0091]
　The aggregation processing 1212 shows the processing in the case of transmitting the IP flows 1201 and 1202 simultaneously using LTE-A and WLAN. This aggregation processing 1212 corresponds to transmission of data using wireless communication by the first wireless communication 101 and the second wireless communication 102 shown in FIG. 1.
[0092]
　In the aggregation processing 1212, the IP flow 1201 is divided into PDCP-transmitted packets by LTE-A and packets transmitted by WLAN. Then, in the IP flow 1201, packets transmitted by LTE-A are processed in the order of RLC, LTE-MAC, and LTE-PHY.
[0093]
　Also, the packet transmitted by the WLAN in the IP flow 1201 is tunneled by processing the PDCP, by attaching the outer IP header by the outer IP layer and transferring it to the WLAN side. The outer IP header is an IP header that is a copy of an IP header attached by, for example, the upper IP layer of PDCP and is not concealed by PDCP. Packets transferred with the outer IP header of the IP flow 1201 to the WLAN side are:. 11 x MAC,. 11 × PHY in this order. . 11 x MAC,. The 11x PHY is the MAC layer and the PHY layer in the WLAN (802.11x), respectively.
[0094]
　It should be noted that the outer IP layer can also be installed on the secondary base station (for example, a secondary eNB 323 described later). That is, in order to attach the outer IP header, the master base station (eNB 321, for example) notifies the secondary base station of relevant information (parameters etc.). Specific examples of parameters are described. Assuming that the operator (operator) constructs a private IP network in the second wireless communication system (WLAN, for example), the version of the IP header can be determined independently, so notification is not indispensable. Since the header length is the PDU length of the first wireless communication system (eg, LTE-A), notification is not indispensable. For TOS, it is preferable to notify because QoS information of the first wireless communication system needs to be inherited. Therefore, it notifies QoS information used in the first wireless communication system, for example, the value of QCI. In the second wireless communication system, the value of QCI is reconverted to the value of TOS, and the obtained value is set in the TOS field of the outer IP header. Because the ID, IP flag, offset field related to fragmentation can be determined only by the second wireless communication system, notification is not indispensable. Since the protocol number can be uniquely determined by the second wireless communication system as described later, notification is not indispensable. Since the header checksum is a value calculated based on the contents of the header, notification is not indispensable.
[0095]
　In this way, it is preferable to notify the TOS value related to the QoS control from the first wireless communication system to the second wireless communication system. Furthermore, in order to carry out scheduling according to the QoS class, the maximum communication rate (AMBR: Aggregated Maximum Bit Rate) supported by the mobile station, the TTW (Time to Wait) which controls the delay time, and the guaranteed bandwidth (GBR: Guaranteed Bit Rate) and the like may also be notified. As described above, when attaching the IP header at the secondary base station, it is not absolutely necessary to copy the inner IP header.
[0096]
　In addition, in the aggregation processing 1212, the IP flow 1202 is divided into packets transmitted by the LTE-A and packets transmitted by the WLAN by the PDCP similarly to the IP flow 1201. Then, in the IP flow 1202, packets transmitted by LTE-A are processed in the order of RLC, LTE-MAC, and LTE-PHY.
[0097]
　Also, the packet transmitted by the WLAN in the IP flow 1202 is tunneled by processing the PDCP, by attaching the outer IP header by the outer IP layer and transferring it to the WLAN side. The outer IP header is an IP header that is a copy of an IP header attached by, for example, the upper IP layer of PDCP and is not concealed by PDCP. The packet attached with the outer IP header in the IP flow 1202 and transferred to the WLAN side is. 11 x MAC,. 11 × PHY in this order.
[0098]
　In LTE-A, IP flows are classified as bearers and managed as bearers. In contrast, in 802.11x of IEEE (the Institute of Electrical and Electronics Engineers) which is one example of WLAN, the IP flow is managed as IP flow instead of bearer. Therefore, it is required to manage the mapping of which bearer belongs to which L2 layer, as in the mapping management 1220, and to perform the non-aggregation processing 1211 and the aggregation processing 1212 at high speed.
[0099]
　Mapping management 1220 is performed, for example, by RRC which performs radio control between UE 311 and eNB 321. By managing the radio bearer, the RRC supports the non-aggregation processing 1211 using the LTE-A wireless communication and the radio bearer processing with the wireless communication by the LTE-A and the aggregation processing 1212 using the wireless communication by the WLAN. In the example shown in FIG. 12, IP flow 1201 with IP flow ID = 0 in HTTP is managed as a bearer with bearer ID = 0, IP flow 1202 with FTP IP flow ID = 0 is managed as a bearer with bearer ID = 1 ing.
[0100]
　In addition, the wireless communication system 300 according to the second embodiment adds an outer IP header to a packet to be transferred to the WLAN. This makes it possible to transmit the traffic of LTE-A in the WLAN. In the WLAN, the ToS field included in the transferred IP flows 1201 and 1202 can be referred to.
[0101]
　For example, in QoS in IEEE802.11e, QoS is managed by consolidating IP flows into four types of AC (Access Category) with reference to the ToS field etc. of the IP header. In the wireless communication system 300, it is possible to perform QoS processing based on the ToS field by referring to the ToS field included in the transferred IP flows 1201 and 1202 in the WLAN. Therefore, in the aggregation processing 1212, support of WLAN QoS becomes possible.
[0102]
　In this manner, the eNB 321 on the transmitting side, when performing aggregation using the LTE-A and the WLAN at the same time, adds the service quality information before processing of the PDCP to the data processed by the PDCP for transmission using the WLAN To the outer IP header.
[0103]
　This service quality information is, for example, QoS information indicating a transmission priority such as a service class of data. As an example, the quality of service information may be the ToS field described above, but the quality of service information is not limited to this and may be various types of information indicating the priority of data transmission. For example, in a VLAN (Virtual Local Area Network), a field specifying QoS is defined in a VLAN tag. Also, more generally, the QoS information is information set with 5 tuples. The 5-tuple is the source IP address and port number, the destination IP address and port number, and the protocol type.
[0104]
　For example, when LTE data is transferred to the WLAN by LTE radio control, if processing such as concealment is performed on the header of data by PDCP or the like, the QoS information included in the data can not be referred to in the WLAN. For this reason, transmission control of data based on QoS information can not be performed in the WLAN, and the communication quality in performing aggregation using LTE-A and WLAN at the same time may decrease.
[0105]
　On the other hand, by adding an outer IP header including quality of service information to the data to be transferred to the WLAN, transmission control based on the service quality information in WLAN processing becomes possible. Transmission control based on the service quality information is, for example, QoS control that controls the priority of transmission according to the quality of service information. However, the transmission control based on the service quality information is not limited to this, and can be various types of control.
[0106]
　In the aggregation process 1212, the user data transferred to the WLAN is subjected to an anonymization process in the WLAN and the like. Therefore, even when the user data attached with an outer header not concealed is transferred to the WLAN, the outer header can be prevented from being transmitted between the eNB 321 and the UE 311 without being concealed.
[0107]
　For concealing the WLAN, for example, AES (Advanced Encryption Standard), TKIP (Temporal Key Integrity Protocol), WEP (Wired Equivalent Privacy), or the like can be used.
[0108]
　In the example shown in FIG. 12, the case where the PDCP is set as the convergence layer (branch point) and the IP flows 1201 and 1202 do not pass through the RLC and the LTE-MAC when performing the aggregation processing 1212 has been described, but such processing . For example, when performing the aggregation processing 1212, RLC and LTE-MAC, which are lower layers of PDCP, are set as convergence layers (branch points), and IP flows 1201 and 1202 pass through RLC and LTE-MAC as well as PDCP You may do so. In this way, the processing unit for establishing the convergence layer (branch point) when transferring to the WLAN is not limited to the PDCP processing unit, and may be the RLC or LTE-MAC processing unit.
[0109]
　The data link layer (layer 2) such as PDCP, RLC, LTE-MAC, etc. can grasp the congestion state of communication in the radio section between the UE 311 and the eNB 321. Therefore, by establishing a convergence layer in the data link layer and transferring to the WLAN, it is judged whether or not the execution of the aggregation processing 1212 is required according to the congestion state of the communication in the wireless section between the UE 311 and the eNB 321 can do.
[0110]
　Further, in the aggregation process 1212, the outer IP layer that adds the outer IP header to the packet is provided as a part of the PDCP layer, for example. However, as described later, the outer IP layer may be provided as a lower layer of the PDCP.
[0111]
　FIG. 13 is a diagram illustrating an example of QoS control based on the ToS field in the wireless communication system according to the second embodiment. A case where the eNB 321 has the function of WLAN communication and the eNB 321 transmits the IP packet 1301 to the UE 311 will be described. Based on the ToS field in the IP header of the IP packet 1301, the eNB 321 classifies the IP packet 1301 into AC 1311 to 1314 of voice, video, best effort, or background.
[0112]
　In the wireless communication system 300, when aggregation using LTE-A and WLAN is performed at the same time, an outer IP header is added to a packet (PDCP packet) processed by the PDCP layer and transferred to the WLAN. Therefore, even in WLAN processing, the eNB 321 refers to the ToS field included in the outer IP header of the IP packet 1301 and can perform AC classification based on the ToS field.
[0113]
　The case where the eNB 321 has the function of the WLAN communication has been described, but the same applies to the case where the eNB 321 performs the aggregation using the LTE-A and the WLAN at the same time by transmitting the IP flow to the access point of the WLAN. Also, although the case of transmitting the IP packet 1301 from the eNB 321 to the UE 311 (downlink) has been described, the same applies to the case (IPlink) of transmitting the IP packet 1301 from the UE 311 to the eNB 321.
[0114]
　FIG. 14 is a diagram illustrating an example of AC classification in the wireless communication system according to the second embodiment. In FIG. 14, parts similar to those shown in FIG. 13 are denoted by the same reference numerals, and description thereof is omitted.
[0115]
　In FIG. 14, the case where the eNB 321 has the function of WLAN communication will be described. The IP packets 1401 and 1402 are packets transmitted by the eNB 321 by the WLAN in the aggregation using the LTE-A and the WLAN at the same time. IP packets 1401 and 1402 are IP packets of HTTP and FTP, respectively.
[0116]
　The eNB 321 performs ToS value analysis classification 1410 of classifying the IP packets 1401 and 1402 into one of AC 1311 to 1314 based on the value of the ToS field included in the IP header. In the example shown in FIG. 14, the eNB 321 classifies the IP packet 1401 into AC 1313 (best effort) and classifies the IP packet 1402 into AC 1314 (background). Then, the eNB 321 transmits the IP packets 1401 and 1402 for which the ToS value analysis classification 1410 has been performed to the UE 311 by WLAN.
[0117]
　In the mapping management 1420 by RRC between the eNB 321 and the UE 311, the HTTP IP packet 1401 is managed with IP flow ID = AC = 2 and bearer ID = 0. AC = 2 indicates AC 1313 (best effort). In the mapping management 1420, the FTP IP packet 1402 is managed with IP flow ID = AC = 3 and bearer ID = 1. AC = 3 indicates AC 1314 (background).
[0118]
　The UE 311 terminates the IP packets 1401 and 1402 by PDCP by performing a ToS value analysis classification 1430 (de-classification) corresponding to the ToS value analysis classification 1410 (classification) on the side of the eNB 321.
[0119]
　The case of transmitting the IP packets 1401 and 1402 from the eNB 321 to the UE 311 (downlink) has been described, but the same applies to the case of transmitting the IP packets 1401 and 1402 from the UE 311 to the eNB 321 (uplink).
[0120]
　FIG. 15 is a diagram illustrating an example of aggregation in the wireless communication system according to the second embodiment. In FIG. 15, concerning the case of performing aggregation in which the eNB 321 becomes the master eNB and the WLAN independent configuration using the secondary eNB 323 having the function (eNB + WLAN) of the eNB and the WLAN communication (eNB + WLAN) is used simultaneously for the LTE-A and the WLAN for the downlink explain.
[0121]
　This aggregation is the transmission of data using the first wireless communication 101 and the second wireless communication 102 simultaneously shown in FIG. 1. The secondary eNB 323 is a base station capable of communicating with the eNB 321 through an interface between base stations such as an X 2 interface and capable of communicating with the UE 311 in the WLAN.
[0122]
　In the example shown in FIG. 15, n (n is, for example, 10) EPS bearers 1500 to 150 n are set and communicated between the eNB 321 and the UE 311, and the EPS bearers 1500 to 150 n are respectively connected to the LTE- The case of dividing into WLANs and transmitting them will be described. It should be noted that only a part of the EPS bearers 1500 to 150 n may be divided into LTE-A and WLAN and transmitted. In the example shown in FIG. 15, the EPS bearers 1500 to 150 n are bearers in the downward direction from the eNB 321 to the UE 311. However, in FIG. 15, the case where n number of EPS bearers 1500 to 150 n are set will be described, but the number of EPS bearers to be set is arbitrary.
[0123]
　EPS bearers 1500 to 150 n are n + 1 EPS bearers with EBI (EPS Bearer ID) of 0 to n, respectively. Both the sender (src IP) of the EPS bearers 1500 to 150 n are the core network (CN). Both destinations (dst IP) of EPS bearers 1500 to 150 n are UE 311 (UE).
[0124]
　The eNB 321 transfers the transfer packet to the WLAN in each of the EPS bearers 1500 to 150 n to the secondary eNB 323 via the PDCP layers 1510 to 151 n, respectively. That is, the eNB 321 controls the transfer of the EPS bearers 1500 to 150 n to the WLAN by the LTE-A layer 2 (PDCP in the example shown in FIG. 15).
[0125]
　At this time, the eNB 321 adds the outer IP header to the packet to be transferred to the WLAN in each of the EPS bearers 1500 to 150 n. As a result, the EPS bearers 1500 to 150 n are transferred as IP packets to the secondary eNB 323. That is, the EPS bearers 1500 to 150 n are transferred to the WLAN in a state where the outer IP header not including the Toh field (QoS information) and not concealed as described above is attached.
[0126]
　In addition, the value of the protocol field (eg, the protocol field 1004 shown in FIG. 10) in the outer IP header can be, for example, "99" (any private encryption scheme). However, the value of the protocol field in the outer IP header is not limited to "99", but it may be set to "61" (any host internal protocol), "63" (any local network), "114" (any 0-hop protocol) May be used.
[0127]
　The EPS bearers 1500 to 150 n can be transferred from the eNB 321 to the secondary eNB 323 in the same way as the handover of the LTE-A, for example. For example, the transfer of the EPS bearers 1500 to 150 n from the eNB 321 to the secondary eNB 323 can be performed using the GTP tunnels 1520 to 152 n between the eNB 321 and the secondary eNB 323. The GTP tunnels 1520 to 152 n are GTP tunnels set for each EPS bearer between the eNB 321 and the secondary eNB 323. However, this transfer can be performed not only by the GTP tunnel but also by various methods such as Ethernet (registered trademark).
[0128]
　Further, the eNB 321 processes the RLC, the MAC, and the PHY in this order without adding the outer IP header to the packet transmitted by the LTE-A in each of the EPS bearers 1500 to 150 n and transmits the packet to the UE 311 by the LTE-A Send. The UE 311 receives the packet transmitted from the eNB 321 by the LTE-A by processing it with PHY, MAC, RLC, PDCP (PDCP layers 1570 to 157 n).
[0129]
　The secondary eNB 323 receives the EPS bearers 1500 to 150 n transferred from the eNB 321 via the GTP tunnels 1520 to 152 n, respectively. Then, for each IP packet corresponding to the received EPS bearers 1500 to 150 n, the secondary eNB 323 performs AC classification 1540 based on the ToS field included in the outer IP header of each IP packet.
[0130]
　The AC classification 1540 is processing by the function of the WLAN (802.11e) in the secondary eNB 323. By AC classification 1540, for example, as shown in FIG. 13, each IP packet is classified into AC of any one of Voice (VO), Video (VI), Best Effort (BE), and Background (BK) .
[0131]
　The secondary eNB 323 transmits each IP packet classified by the AC classification 1540 to the UE 311 via the WLAN 1550. In this case, the SSID (Service Set Identifier) ​​in the WLAN 1550 may be "offload", for example.
[0132]
　For each IP packet received via WLAN 1550, UE 311 performs AC declaration 1560 based on the ToS field included in the outer IP header of the IP packet. The AC declaration 1560 is processing by the function of the WLAN (802.11e) in the UE 311.
[0133]
　The UE 311 reclassifies each IP packet received by the AC declaration 1560 into EPS bearers 1500 to 150 n based on the classified ACs. Then, the UE 311 processes and re-classifies the re-classified EPS bearers 1500 to 150 n by the PDCP layers 1570 to 157 n, respectively.
[0134]
　The layer group 1551 indicates each protocol of each IP packet received by the UE 311 by the PDCP layers 1570 to 157 n. As shown in the layer group 1551, the data transmitted by the WLAN is data processed by the application layer (APP), the TCP / UDP layer, the IP layer (inner layer), the PDCP layer, and the outer IP layer. Data (hatched portion) by the application layer, the TCP / UDP layer, and the IP layer is encrypted by the processing of the PDCP layer and transmitted.
[0135]
　The UE 311 removes the outer IP header attached to each received IP packet. The layer group 1552 indicates each protocol of a PDCP packet obtained by removing the outer IP header from the IP packet received by the UE 311. By transmitting the PDCP packet from the eNB 321 using the tunneling by the outer IP layer, the UE 311 can receive the data transmitted by the WLAN as a PDCP packet as shown in the layer group 1552.
[0136]
　The layer group 1553 indicates each protocol of the PDCP packet received by the UE 311 from the eNB 321 by LTE-A. As shown in the layer group 1553, the eNB 321 transmits the PDCP packet as it is to the UE 311 without adding the outer IP header.
[0137]
　The UE 311 performs the sequence control between the PDCP packet received by the WLAN and the PDCP packet received by the LTE-A based on the sequence number included in the header of each PDCP packet. The sequence number included in the header of the PDCP packet is the sequence number contained in the header added to the data by the processing by the PDCP layer.
[0138]
　As a result, the UE 311 can arrange the PDCP packet received by the WLAN and the PDCP packet received by the LTE-A in the correct order, and can receive the data that the eNB 321 divided into the LTE-A and the WLAN .
[0139]
　As described above, in the radio communication system 300, when the EPS bearers 1500 to 150 n are divided into LTE-A and WLAN and transmitted, the PDCP packet transmitted by the WLAN can be tunneled with the outer IP. As a result, on the receiving side, the data transmitted by the WLAN is received as a PDCP packet and the sequence control between the packet received by the LTE-A and the packet received by the WLAN is performed using the sequence number of the PDCP . Therefore, data transmission using LTE-A and WLAN at the same time becomes possible.
[0140]
　By tunneling by adding an outer IP header which is a copy of the inner IP header to the PDCP packet transmitted by the WLAN, the ToS field of the outer IP header of each IP packet can be referred to in the secondary eNB 323. Therefore, AC classification 1540 based on the ToS field can be performed on the data transmitted by the WLAN 1550, and QoS control according to the traffic characteristics can be performed.
[0141]
　It is also possible for the WLAN 1550 to perform AC classification by referring to the priority value in the VLAN tag defined by IEEE 802.1q. The VLAN tag is an identifier of the VLAN.
[0142]
　In FIG. 15, the case where aggregation is performed in which the eNB 321 becomes the master eNB and the LTE-A and the WLAN are simultaneously used in the WLAN independent configuration using the secondary eNB 323 having the eNB and WLAN communication functions (eNB + WLAN) has been described. However, the aggregation is not limited to this, for example, aggregation may be performed in a configuration in which the eNB 321 also has the function of WLAN communication (eNB + WLAN). In this case, the eNB 321 may also communicate with the UE 311 by the WLAN, and the secondary eNB 323 may not be used.
[0143]
　FIG. 16 is a diagram showing an example of the mapping of the QoS class to AC that can be applied to the radio communication system according to the second embodiment. The transmitting side (for example, the secondary eNB 323) of the WLAN classifies the EPS bearer to be transmitted into AC as shown in the table 1600 of FIG. 16, for example. For example, the QoS class of the EPS bearer is identified by QCI (QoS Class Identifier).
[0144]
　Each QCI is classified into four ACs: Voice (VO), Video (VI), Best Effort (BE), and Background (BK). The receiving side (for example UE 311) of WLAN performs conversion from AC to QoS class. Therefore, the eNB 321 presets the EPS bearer to be transferred to the WLAN in the UE 311 in advance. On the other hand, for example, on the downlink, the UE 311 can specify the EPS bearer based on the EPS bearer set from the eNB 321. In the uplink, the UE 311 can perform AC classification based on the EPS bearer set from the eNB 321.
[0145]
　FIG. 17 is a flowchart showing an example of processing by the transmission side apparatus in the radio communication system according to the second embodiment. In FIG. 17, the case of downlink in which user data is transmitted from the eNB 321 to the UE 311 will be described.
[0146]
　First, the eNB 321 determines whether or not to perform aggregation that simultaneously uses LTE-A and WLAN for user data to the UE 311 (step S 1701). The determination method in step S1701 will be described later.
[0147]
　If it is determined in step S1701 that the aggregation is not to be executed (step S1701: No), the eNB 321 transmits the user data to the UE 311 by the LTE-A (step S1702), and ends the series of processing. In step S1702, user data on which PDCP concealment, header compression, etc., has been performed is transmitted. On the other hand, in the PDCP layer, the UE 311 can receive user data transmitted from the eNB 321 by performing processing such as decoding for privacy and header decompression for header compression.
[0148]
　In step S1701, if it is determined that the aggregation is to be executed (step S1701: Yes), the eNB 321 sets an outer IP layer for processing data to be transferred to the WLAN (step S1703). In step S1703, the eNB 321 may control the UE 311 to set the outer IP layer of the UE 311 according to its own station.
[0149]
　Next, eNB 321 simultaneously uses LTE-A and WLAN to transmit user data to UE 311 (step S 1704), and ends the series of processing. In step S1704, the eNB 321 tunnels and transmits the user data to be transmitted by the WLAN by adding an outer IP header according to the outer IP layer set in step S1703.
[0150]
　In step S1704, if the eNB 321 has the function of WLAN communication, the eNB 321 transmits the user data to the UE 311 through the functions of the LTE-A communication and the WLAN communication of its own station. On the other hand, if the eNB 321 does not have the function of WLAN communication, the eNB 321 transfers the user data to the UE 311 to the secondary eNB 323 having the function of the WLAN communication connected with the own station .
[0151]
　In addition, since the outer IP header is added to the data transferred to the WLAN by the outer IP layer set in step S1703, QoS control based on the ToS field included in the outer IP header can be performed in the WLAN.
[0152]
　The determination in step S1701 described above can be made based on whether or not it is instructed to perform aggregation on the user data of the UE 311 from, for example, the UE 311 or the network side (for example, the PGW 332). Alternatively, the determination in step S1701 can be made, for example, based on whether or not the amount of user data to the UE 311 exceeds a threshold. The amount of user data may be an amount per time or may be a total amount of a series of user data of the UE 311. Alternatively, the determination in step S1701 can be made based on, for example, a delay time of communication by LTE-A between the eNB 321 and the UE 311, a delay time of communication by the WLAN between the eNB 321 and the UE 311, and the like.
[0153]
　In addition, in FIG. 17, the case where user data is transmitted using only LTE-A when aggregation is not performed has been described, but in the case where aggregation is not performed, eNB 321 transmits user data using only WLAN May be used. Whether aggregation is not performed, whether to use LTE-A or WLAN can be judged, for example, based on an instruction from the UE 311 or the network side (for example, PGW 332). Alternatively, this determination can be made, for example, based on whether the amount of user data to the UE 311 has exceeded a threshold. The amount of user data may be an amount per time or may be a total amount of a series of user data of the UE 311. Alternatively, this determination can be made based on, for example, a delay time of communication by LTE-A between the eNB 321 and the UE 311, a delay time of communication by the WLAN between the eNB 321 and the UE 311, and the like.
[0154]
　17, processing by the eNB 321 in the case of downlink in which user data is transmitted from the eNB 321 to the UE 311 has been described, but processing by the UE 311 in the case of uplink in which the user data is transmitted from the UE 311 to the eNB 321 is similar. However, the processing in step S1704 varies depending on whether the eNB 321 has the function of WLAN communication or not. When the eNB 321 has the function of WLAN communication, the UE 311 directly transmits the user data to the eNB 321 to be transmitted by the WLAN to the eNB 321. On the other hand, when the eNB 321 does not have the function of the WLAN communication, the UE 311 transfers the user data to the eNB 321 to be transmitted by the WLAN to the secondary eNB 323 having the function of the WLAN communication connected to the eNB 321. As a result, it is possible to transmit the user data to the eNB 321 via the secondary eNB 323.
[0155]
　FIG. 18 is a diagram illustrating an example of a case where a plurality of EPS bearers have the same QoS class in the wireless communication system according to the second embodiment. In FIG. 18, parts similar to those shown in FIG. 14 are denoted by the same reference numerals, and description thereof is omitted. For example, when the IP packets 1401 and 1402 are both IP packets in the background, in the ToS value analysis classification 1410, both the IP packets 1401 and 1402 are classified as AC 1314 (background).
[0156]
　In this case, in the mapping management 1420 in the RRC between the UE 311 and the eNB 321, the HTTP IP packet 1401 is managed with IP flow ID = AC = 3 and bearer ID = 0. In the mapping management 1420, the FTP IP packet 1402 is managed with IP flow ID = AC = 3 and bearer ID = 1.
[0157]
　In this case, even if the To 3 value analysis classification 1430 corresponding to the ToS value analysis classification 1410 is performed, the UE 311 determines which of the received IP packets 1401 and 1402 is the EPS bearer with the bearer ID = 0 or 1 Can not be determined based on AC.
[0158]
　Also, when sending user data via WLAN, it is not possible to add LCID to IP datagram (PDCP SDU). Therefore, the eNB 321 can not determine which one of the received EPS bearers with the bearer ID = 0, 1, based on the LCID, of each of the received IP packets 1401, 1402.
[0159]
　In this way, when a plurality of EPS bearers have the same QoS class, the receiving side (the UE 311 in the example shown in FIG. 18) may not be able to uniquely identify EPS bearers in some cases. That is, the receiving side may not be able to convert the received radio bearer into an EPS bearer. Particularly, in the uplink, since the IP flow between the eNB 321 and the PGW 332 is managed as an EPS bearer, when the eNB 321 can not convert the radio bearer into the EPS bearer, it becomes difficult to transmit the IP flow from the eNB 321 to the PGW 332.
[0160]
　On the other hand, in the radio communication system 300 according to the second embodiment, for example, the transmitting side of the UE 311 and the eNB 321 does not simultaneously perform the aggregation on the EPS bearers having the same QoS class.
[0161]
　For example, when transmitting a plurality of EPS bearers having the same QoS class to the UE 311, the transmitting side performs aggregation with respect to only one of the plurality of EPS bearers. Then, on the transmitting side, the remaining EPS bearers transmit to the UE 311 by LTE-A without performing aggregation. Alternatively, when transmitting a plurality of EPS bearers having the same QoS class to the UE 311, the transmitting side performs transmission by LTE-A without performing aggregation. As a result, since a plurality of EPS bearers having the same QoS class are not simultaneously transferred to the WLAN, the UE 311 can uniquely specify the EPS bearer based on the AC for each user data transferred to the WLAN.
[0162]
　Alternatively, when the transmitting side of the UE 311 and the eNB 321 transmits a plurality of EPS bearers having the same QoS class to the UE 311, the transmitting side may perform a process of aggregating the plurality of EPS bearers into one bearer. For processing of aggregating a plurality of EPS bearers into one bearer, for example, "UE requested bearer resource modification procedure" defined in TS 23.401 of 3 GPP can be used. As a result, since a plurality of EPS bearers having the same QoS class are not simultaneously transferred to the WLAN, the UE 311 can uniquely specify the EPS bearer based on the AC for each user data transferred to the WLAN.
[0163]
　Further, as described below (for example, refer to FIGS. 22 to 24), a new tunneling layer is provided separately from the outer IP layer, and a tunneling header including identification information for each bearer is added to the data by the tunneling layer Can also be considered. In this case, for each user data transferred to the WLAN, the UE 311 can uniquely identify the EPS bearer using the identification information.
[0164]
　FIG. 19 is a diagram showing an example of implementation of an outer IP layer using the 3GPP protocol in the second embodiment. In the example shown in FIG. 15 and the like, the case where the outer IP layer is provided as a part of the PDCP layer has been described, but as in the protocol stack shown in FIG. 19, the outer IP layer 1900 is provided as the lower layer of the PDCP layer 1901 It is also good.
[0165]
　In this case, for example, the PDCP layer 1901 carries out processing such as anonymization by PDCP, adds a PDCP packet to which a PDCP header is attached, an IP header added to a packet before processing such as concealment by PDCP, To the outer IP layer 1900. The PDCP header is, for example, a 2-byte header.
[0166]
　The outer IP layer 1900 adds the IP header transferred from the PDCP layer 1901 as the outer IP header to the PDCP packet transferred from the PDCP layer 1901. As a result, PDCP packets can be transmitted via WLAN by tunneling. The outer IP header is, for example, the same 20 byte header as the inner IP header.
[0167]
　FIG. 20 is a diagram showing another example of the implementation of the outer IP layer using 3GPP protocol in the second embodiment. In FIG. 20, parts similar to those shown in FIG. 19 are denoted by the same reference numerals, and description thereof is omitted. As in the protocol stack shown in FIG. 20, the outer IP layer 1900 may be provided as a lower layer of the PDCP layer 1901 and the RLC layer 1902.
[0168]
　In this case, for example, the PDCP layer 1901 has a PDCP packet that has undergone processing such as concealment by PDCP, an IP header (inner IP header) added to a packet before processing such as concealment by PDCP, To the RLC layer 1902.
[0169]
　The RLC layer 1902 adds an RLC header to the PDCP packet transferred from the PDCP layer 1901, forwards the RLC packet to which the RLC header is added and the IP header transferred from the PDCP layer 1901 to the outer IP layer 1900 . The RLC header is, for example, a variable length header.
[0170]
　The outer IP layer 1900 adds the IP header transferred from the RLC layer 1902 as an outer IP header to the RLC packet transferred from the RLC layer 1902. As a result, RLC packets can be transmitted via WLAN through tunneling. Therefore, retransmission control by RLC, for example, of data to be transmitted via WLAN by tunneling becomes possible.
[0171]
　FIG. 21 is a diagram showing still another example of the implementation of the outer IP layer using 3GPP protocol in the second embodiment. In FIG. 21, parts similar to those shown in FIG. 20 are denoted by the same reference numerals, and description thereof is omitted. As in the protocol stack shown in FIG. 20, the outer IP layer 1900 may be provided as a lower layer of the PDCP layer 1901, the RLC layer 1902, and the MAC layer 1903.
[0172]
　In this case, the RLC layer 1902 transfers the RLC packet to which the RLC header is added and the IP header transferred from the PDCP layer 1901 to the MAC layer 1903. The MAC layer 1903 adds a MAC header to the PDCP packet transferred from the RLC layer 1902, and transfers the MAC frame to which the MAC header is added and the IP header transferred from the RLC layer 1902 to the outer IP layer 1900 . The MAC header is, for example, a variable length header.
[0173]
　The outer IP layer 1900 adds the IP header transferred from the MAC layer 1903 as the outer IP header to the MAC frame transferred from the MAC layer 1903. As a result, MAC frames can be transmitted via WLAN by tunneling. For this reason, retransmission control by HARQ, for example, of data to be transmitted via WLAN by tunneling becomes possible.
[0174]
　FIG. 22 is a diagram showing an example of implementation of the outer IP layer using the new tunneling protocol in the second embodiment. In FIG. 22, parts similar to those shown in FIG. 19 are denoted by the same reference numerals, and description thereof is omitted. As shown in FIG. 22, a tunneling layer 2201 (TUN) which is a new tunneling protocol may be provided between the PDCP layer 1901 and the outer IP layer 1900.
[0175]
　The tunneling layer 2201 adds a tunneling header to the PDCP packet to which the PDCP header is added by the PDCP layer 1901. Further, the tunneling layer 2201 may add a tunneling header including identification information of the bearer, for example, to the PDCP packet. The outer IP layer 1900 adds an outer IP header to a packet to which a tunneling header is attached by the tunneling layer 2201. The bearer identification information is, for example, the ID of the bearer. The receiving station can identify the EPS bearer by referring to the bearer ID.
[0176]
　FIG. 23 is a diagram showing another example of the implementation of the outer IP layer using the new tunneling protocol in the second embodiment. In FIG. 23, portions similar to those shown in FIG. 20 or 22 are denoted by the same reference numerals, and description thereof is omitted. As shown in FIG. 23, a tunneling layer 2201 may be provided between the RLC layer 1902 and the outer IP layer 1900. The tunneling layer 2201 adds a tunneling header to the RLC packet to which the RLC header is added by the RLC layer 1902.
[0177]
　FIG. 24 is a diagram showing still another example of the implementation of the outer IP layer using the new tunneling protocol in the second embodiment. In FIG. 24, parts similar to those shown in FIG. 21 or FIG. 23 are denoted by the same reference numerals, and description thereof is omitted. As shown in FIG. 24, a tunneling layer 2201 may be provided between the MAC layer 1903 and the outer IP layer 1900. The tunneling layer 2201 adds a tunneling header to the MAC frame to which the MAC header is added by the MAC layer 1903.
[0178]
　As shown in FIG. 19 to FIG. 24, the position where the outer IP layer 1900 is mounted is not limited to the PDCP layer 1901, and can be, for example, each position in the lower order of the PDCP layer 1901. Also, for example, the case where the outer IP layer 1900 is provided separately from the RLC layer 1902 and the MAC layer 1903 has been described, but the outer IP layer 1900 may be provided as a part of the RLC layer 1902 and the MAC layer 1903.
[0179]
　As described above, according to the second embodiment, when performing aggregation using the LTE-A and the WLAN at the same time, the transmission-side station out of the eNB 321 and the UE 311 tunnels the PDCP packet transmitted by the WLAN with the outer IP can do. As a result, on the receiving side, the data transmitted by the WLAN is received as a PDCP packet and the sequence control between the packet received by the LTE-A and the packet received by the WLAN is performed using the sequence number of the PDCP . Therefore, data transmission using LTE-A and WLAN at the same time becomes possible.
[0180]
　By enabling data transmission using LTE-A and WLAN at the same time, data transmission speed can be improved. For example, when only one of LTE-A and WLAN is used, the maximum transmission rate is the maximum transmission rate of LTE-A when LTE-A is used, and when using WLAN, the maximum transmission rate of WLAN and Become. On the other hand, the maximum transmission rate when using LTE-A and WLAN at the same time is the sum of the maximum transmission rate of LTE-A and the maximum transmission rate of WLAN.
[0181]
　Further, the transmitting station of the eNB 321 and the UE 311 can perform tunneling by adding an outer IP header, which is a copy of the inner IP header, to the PDCP packet transmitted by the WLAN. As a result, in the WLAN, the ToS field included in the outer IP header of each IP packet can be referred to. For this reason, AC classification based on the ToS field can be performed on the data transmitted by the WLAN, and QoS control can be performed according to the nature of the traffic.
[0182]
Embodiment 3 In
　Embodiment 3, a method that can eliminate the constraint of not simultaneously aggregating EPS bearers having the same QoS class and increase the amount of user data that can be aggregated will be described. Since the third embodiment can be regarded as an embodiment embodying the first embodiment as described above, it can be implemented in combination with the first embodiment. Further, in Embodiment 3, it is also possible to combine parts common to Embodiment 2.
[0183]
　FIG. 25 is a diagram illustrating an example of a method for identifying EPS bearers using UL TFTs in the radio communication system according to the third embodiment. In FIG. 25, parts similar to those shown in FIG. 15 are denoted by the same reference numerals, and description thereof is omitted.
[0184]
　In FIG. 25, a case where the eNB 321 performs the aggregation using the LTE-A and the WLAN at the same time in the configuration having the WLAN communication function (eNB + WLAN) for the uplink will be described. In the example shown in FIG. 25, the EPS bearers 1500 to 150 n are uplink bearers from the UE 311 to the eNB 321. That is, the sender (src IP) of the EPS bearers 1500 to 150 n are both UE 311 (UE). Both the destinations (dst IP) of the EPS bearers 1500 to 150 n are the core network (CN).
[0185]
　The UE 311 makes the EPS bearers 1500 to 150 n go through the PDCP layers 1570 to 157 n when performing aggregation using the LTE-A and the WLAN simultaneously for the EPS bearers 1500 to 150 n. At this time, the UE 311 performs tunneling of the PDCP packet by adding an outer IP header to the PDCP packet transmitted by the WLAN. As a result, the PDCP packet transmitted by the WLAN is an IP packet.
[0186]
　The UE 311 performs AC classification 2510 based on the ToS field included in the outer IP header of the IP packet for each IP packet corresponding to the EPS bearers 1500 to 150 n via the PDCP layers 1570 to 157 n. The AC classification 2510 is processing by the function of the WLAN (802.11 e) in the UE 311.
[0187]
　Each IP packet classified by the AC classification 2510 is transmitted to the eNB 321 via the WLAN 1550. For each IP packet received via the WLAN 1550, the eNB 321 performs AC declaration 2520 based on the ToS field included in the outer IP header of the IP packet. The AC declaration 2520 is processing by the function of the WLAN (802.11 e) in the eNB 321.
[0188]
　Also, the UE 311 processes the RLC, the MAC, and the PHY in this order without adding the outer IP header to the packet transmitted by the LTE-A in each of the EPS bearers 1500 to 150 n and transmits the packet to the eNB 321 by the LTE-A Send. The eNB 321 receives the packet transmitted from the UE 311 by the LTE-A by processing it with PHY, MAC, RLC, PDCP (PDCP layers 1570 to 157 n).
[0189]
　The eNB 321 performs packet filtering 2530 based on the UL (uplink) TFT for each IP packet received by the AC declaration 2520. In packet filtering 2530, each IP packet is filtered according to whether or not each condition (f 1 to f 3) corresponding to the TFT is satisfied (match / no). EPS bearer classification 2531 for identifying the EPS bearer is performed according to the result of this filtering. As a result, EPS bearers corresponding to each IP packet transferred to the WLAN are identified. A method of acquiring the UL TFT in the eNB 321 will be described later (see FIG. 27, for example).
[0190]
　the eNB 321 transfers each IP packet to the PDCP layer corresponding to the EPS bearer of the IP packet among the PDCP layers 1510 to 151 n based on the identification result by the EPS bearer classification 2531. As a result, each IP packet (IP flow) transferred to the WLAN is converted into a corresponding EPS bearer and transferred to the PDCP layers 1510 to 151 n.
[0191]
　The eNB 321 obtains the PDCP packet by removing the outer IP header attached to each IP packet received by the WLAN. Then, the eNB 321 performs the sequence control between the PDCP packet received by the WLAN and the PDCP packet received by the LTE-A based on the sequence number included in the header of each PDCP packet. Thereby, the eNB 321 can arrange the PDCP packet received by the WLAN and the PDCP packet received by the LTE-A in the correct order, and can receive the data transmitted by the eNB 321 by being divided into the LTE-A and the WLAN .
[0192]
　In this manner, the eNB 321 can perform packet filtering 2530 based on the UL TFT for each IP packet transferred to the WLAN, thereby identifying the EPS bearer of each IP packet transferred to the WLAN. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0193]
　FIG. 26 is a diagram showing another example of a method for identifying EPS bearers using UL TFTs in the radio communication system according to the third embodiment. In FIG. 26, parts similar to those shown in FIG. 15 or FIG. 25 are denoted by the same reference numerals, and description thereof is omitted.
[0194]
　In FIG. 26, a description will be given of a case where aggregation is performed in which the eNB 321 becomes the master eNB and the WLAN independent configuration using the secondary eNB 323 having the function of WLAN communication with the eNB is used for the uplink simultaneously using the LTE-A and WLAN. In this case, between the eNB 321 and the secondary eNB 323, for example, GTP tunnels 1520 to 152 n for each EPS bearer are set up.
[0195]
　The secondary eNB 323 receives each IP packet transmitted from the UE 311 via the WLAN 1550. Then, the secondary eNB 323 performs AC declaration 2520 and packet filtering 2530 similar to the example shown in FIG. 25 for each received IP packet. As a result, EPS bearer classification 2531 in packet filtering 2530 is performed for each IP packet, and the EPS bearer corresponding to each IP packet is identified.
[0196]
　The secondary eNB 323 transfers each IP packet to the GTP tunnel corresponding to the EPS bearer of the IP packet among the GTP tunnels 1520 to 152 n, based on the identification result by the EPS bearer classification 2531. As a result, each IP packet is transferred to the corresponding PDCP layer of the PDCP layers 1510 to 151 n of the eNB 321.
[0197]
　In this manner, the secondary eNB 323 can perform packet filtering 2530 based on the UL TFT for each IP packet transferred to the WLAN, thereby identifying the EPS bearer of each IP packet transferred to the WLAN. Then, the secondary eNB 323 transfers each IP packet through the GTP tunnels 1520 to 152 n according to the identification result of the EPS bearer, whereby the eNB 321 can receive each IP packet transferred to the WLAN as an EPS bearer.
[0198]
　For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0199]
　FIG. 27 is a diagram showing an example of a method of acquiring a TFT in the wireless communication system according to the third embodiment. Each step shown in FIG. 27 is "Dedicated Bearer Activation Procedure" defined in TS 23.401 of 3GPP. The PCRF 2701 (Policy and Charging Rules Function) shown in FIG. 27 is a processing unit connected to the packet core network 330 for setting priority control and charging rules according to the service.
[0200]
　For example, the PGW 332 sets the UL and DL TFTs for the UE 311, stores the set TFT in the create bearer request 2702 shown in FIG. 27, and transmits it to the SGW 331. The SGW 331 transmits the Create Bearer Request 2702 transmitted from the PGW 332 to the MME 333.
[0201]
　The MME 333 transmits the bearer setup request / session management request 2703 including the TFT included in the create bearer request 2702 transmitted from the SGW 331 to the eNB 321. The TFT is included in the session management request in the bearer setup request / session management request 2703, for example. As a result, the eNB 321 can acquire UL and DL TFTs.
[0202]
　The eNB 321 transmits the RRC connection reconfiguration 2704 including the UL TFT among the TFTs included in the bearer setup request / session management request 2703 transmitted from the MME 333 to the UE 311. As a result, the UE 311 can acquire the UL TFT. Although the UL TFT can be defined in the RRC connection reconfiguration message, it is preferably defined in the NAS (Non Access Stratum) PDU transmitted in the message. The same applies to the following description.
[0203]
　For example, in the example shown in FIG. 25, the eNB 321 can perform packet filtering 2530 using the UL TFT obtained from the bearer setup request / session management request 2703. In the example shown in FIG. 26, the eNB 321 transmits the UL TFT acquired from the bearer setup request / session management request 2703 to the secondary eNB 323. Then, the secondary eNB 323 can perform packet filtering 2530 based on the UL TFT transmitted from the eNB 321.
[0204]
　FIG. 28 is a diagram illustrating an example of a method of identifying an EPS bearer using a DL TFT in the wireless communication system according to the third embodiment. In FIG. 28, parts similar to those shown in FIG. 15 are denoted by the same reference numerals, and description thereof is omitted.
[0205]
　In FIG. 28, the case where the eNB 321 performs the aggregation using the LTE-A and the WLAN at the same time in the configuration having the WLAN communication function (eNB + WLAN) for the downlink will be described. In the example shown in FIG. 28, the EPS bearers 1500 to 150 n are bearers in the downstream direction from the eNB 321 to the UE 311.
[0206]
　The UE 311 performs packet filtering 2810 based on the DL (downlink) TFT for each IP packet received by the AC declaration 1560. Since the packet filtering 2810 by the UE 311 is a process based on the DL TFT, it is the same process as the packet filtering by the filter layer 811 in the PGW 332 shown in FIG. 8, for example.
[0207]
　In packet filtering 2810, each IP packet is filtered according to whether or not each condition (f 1 to f 3) corresponding to the TFT is satisfied (match / no). EPS bearer classification 2811 for identifying the EPS bearer is performed according to the result of this filtering. As a result, EPS bearers corresponding to each IP packet transferred to the WLAN are identified.
[0208]
　For example, the eNB 321 stores DL TFTs in addition to UL TFTs in the RRC connection reconfiguration 2704 to the UE 311 shown in FIG. 27. As a result, the UE 311 can acquire the DL TFT from the RRC connection reconfiguration 2704 and perform the packet filtering 2810 based on the acquired DL TFT.
[0209]
　The UE 311 transfers each IP packet to the PDCP layer corresponding to the EPS bearer of the IP packet among the PDCP layers 1570 to 157 n based on the identification result by the EPS bearer classification 2811. As a result, each IP packet (IP flow) transferred to the WLAN is converted into a corresponding EPS bearer and transferred to PDCP layers 1570 to 157 n.
[0210]
　In this manner, the UE 311 can perform packet filtering 2810 based on the DL TFT on each IP packet transferred to the WLAN, thereby identifying the EPS bearer of each IP packet transferred to the WLAN. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0211]
　FIG. 29 is a diagram showing another example of a method for identifying the EPS bearer using the DL TFT in the radio communication system according to the third embodiment. In FIG. 29, parts similar to those shown in FIG. 15 or FIG. 28 are denoted by the same reference numerals, and description thereof is omitted.
[0212]
　In FIG. 29, a description will be given of a case where aggregation is performed in which the eNB 321 becomes the master eNB and the WLAN-independent configuration using the secondary eNB 323 having the function of WLAN communication with the eNB is used for the downlink simultaneously using the LTE-A and the WLAN. In this case, between the eNB 321 and the secondary eNB 323, GTP tunnels 1520 to 152 n for each EPS bearer are set.
[0213]
　The secondary eNB 323 receives each IP packet transmitted from the UE 311 via the WLAN 1550. Then, the secondary eNB 323 transfers the received IP packets to the PDCP layers 1570 to 157 n.
[0214]
　Thus, similarly to the example shown in FIG. 28, the UE 311 performs packet filtering 2810 based on the DL TFT on each IP packet transferred to the WLAN, whereby the EPS of each IP packet transferred to the WLAN Bearers can be identified. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0215]
　According to the method using the TFTs shown in FIGS. 25 to 29, the number of EPS bearers that can be transferred to the WLAN as in the case of using a VLAN tag, for example, is not limited to the number of bits of the VLAN tag, and the EPS bearer is identified It is possible. Further, according to the method using the TFTs shown in FIGS. 25 to 29, the EPS bearer can be identified without adding a header such as a VLAN tag to the user data transferred to the WLAN.
[0216]
　FIG. 30 is a diagram illustrating an example of a method of identifying an EPS bearer using the virtual IP flow in the wireless communication system according to the third embodiment. In FIG. 30, parts similar to those shown in FIG. 15 are denoted by the same reference numerals, and description thereof is omitted.
[0217]
　In FIG. 30, the case where the eNB 321 performs the aggregation using the LTE-A and WLAN at the same time in the configuration having the WLAN communication function (eNB + WLAN) for the downlink will be described. In the example shown in FIG. 30, the EPS bearers 1500 to 150 n are bearers in the downward direction from the eNB 321 to the UE 311.
[0218]
　In the example shown in FIG. 30, the virtual GW 3010 is set between the PDCP layers 1510 - 151 n in the eNB 321 and the WLAN 1550. The virtual GW 3010 includes NAT processing units 3020 to 302 n and a MAC processing unit 3030 (802.3 MAC). A virtual GW 3040 is set between the WLAN 1550 and the PDCP layers 1570 to 157 n in the UE 311. The virtual GW 3040 includes a MAC processing unit 3050 (802.3 MAC) and de-NAT processing units 3060 to 306 n.
[0219]
　The EPS bearers 1500 to 150 n via the PDCP layers 1510 to 151 n are transferred to the NAT processing units 3020 to 302 n of the virtual GW 3010. The NAT processing units 3020 to 302 n perform NAT (Network Address Translation) processing for classifying the EPS bearers 1500 to 150 n into virtual IP flows according to the virtual destination IP address. The virtual IP flow is, for example, a local virtual data flow between the eNB 321 and the UE 311. The virtual destination IP address is the destination address of the virtual IP flow. The NAT processing units 3020 to 302 n transfer each classified virtual IP flow to the MAC processing unit 3030.
[0220]
　For example, the NAT processing units 3020 to 302 n map the EPS bearers 1500 to 150 n and the virtual destination IP address on a one-to-one basis. The virtual source IP address (src IP) of each virtual IP flow transferred from the NAT processors 3020 to 302 n can be, for example, a virtual GW 3010 (vGW). In addition, the virtual destination IP address (dst IP) of each virtual IP flow transferred from the NAT processing units 3020 to 302 n can be set to C-RNTI + 0 to C-RNTI + n, respectively.
[0221]
　It should be noted that the virtual destination IP address can be calculated from, for example, the C-RNTI, but it is not limited thereto. For example, the UE 311 (mobile station) may be notified of the association between the EPS bearer identifier and the IP address by RRC signaling by the eNB 321 (master eNB) in advance at the time of call setting, LTE-WLAN aggregation setting, or the like .
[0222]
　The C-RNTI (Cell-Radio Network Temporary Identifier) ​​is temporarily allocated to the UE 311 and is a unique identifier of the UE 311 within the LTE-A cell. For example, the C-RNTI has a value of 16 bits. As in the example shown in FIG. 30, by generating the virtual source IP address by adding the C-RNTI and the bearer identifier (0 to n), it is possible to avoid the occurrence of duplication of the virtual source IP address . For example, when using the IP address of class A, it becomes possible to identify EPS bearers of about 24 bits that are sufficient for transmission by the WLAN. Here, the case where the virtual source IP address is generated by adding the C-RNTI and the bearer identifier has been described, but the method of generating the virtual source IP address is not limited to this.
[0223]
　The MAC processing unit 3030 converts each virtual IP flow transferred from the NAT processing units 3020 to 302 n into MAC frames such as Ethernet and IEEE 802.3. In this case, the source MAC address (src MAC) of the MAC frame can be any private address (any private) in the virtual GW 3010, 3040, for example. For example, the source MAC address of the MAC frame can be an address (x is an arbitrary value) where the first octet is "xxxxxx10". Further, the destination MAC address (dst MAC) of the MAC frame can be, for example, the MAC address (UE MAC) of the UE 311.
[0224]
　The eNB 321 performs AC classification 1540 on the MAC frame converted by the MAC processing unit 3030, and transmits the MAC frame subjected to AC classification 1540 to the UE 311 via the WLAN 1550.
[0225]
　The UE 311 performs AC declaration 1560 on the MAC frame received from the eNB 321 via the WLAN 1550. The MAC processing unit 3050 of the virtual GW 3040 receives the MAC frame on which the AC declaration 1560 has been performed as a virtual IP flow.
[0226]
　With respect to the virtual IP flow received by the MAC processing unit 3050, the de-NAT processing units 3060 to 306 n convert the virtual IP flow into the EPS bearer by referring to the virtual destination IP address (dst IP) of the virtual IP flow . At this time, the virtual destination IP address of the virtual IP flow is converted into the original IP address by the de-NAT by the de-NAT processing units 3060 to 306 n.
[0227]
　In this manner, by setting the virtual GWs 3010 and 3040 respectively in the eNB 321 and the UE 311 and using the NAT, it is possible to identify the EPS bearer as the virtual IP flow in the virtual GWs 3010 and 3040. The IP address and the MAC address can be composed of addresses in the private space. By constructing the virtual IP network between the virtual GWs 3010 and 3040 in this manner, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0228]
　Although the downlink has been described in FIG. 30, the EPS bearer can also be identified for the uplink by the same method. That is, by constructing a virtual IP network between the virtual GWs 3010 and 3040 set in the eNB 321 and the UE 311, the EPS bearer of each IP packet transferred to the WLAN in the uplink can be identified.
[0229]
　FIG. 31 is a diagram showing another example of a method of identifying the EPS bearer using the virtual IP flow in the wireless communication system according to the third embodiment. In FIG. 31, parts similar to those shown in FIG. 15 or FIG. 30 are denoted by the same reference numerals, and description thereof is omitted.
[0230]
　31, a description will be given of a case where aggregation is performed in which the eNB 321 becomes the master eNB and the WLAN independent configuration using the secondary eNB 323 having the function of WLAN communication with the eNB is used for the downlink at the same time using the LTE-A and WLAN. In this case, between the eNB 321 and the secondary eNB 323, GTP tunnels 1520 to 152 n for each EPS bearer are set.
[0231]
　The NAT processing units 3020 to 302 n shown in FIG. 30 are set in the secondary eNB 323 in the example shown in FIG. 31. The secondary eNB 323 receives each IP packet transmitted from the UE 311 via the WLAN 1550. In addition, the secondary eNB 323 transfers the received IP packets to the NAT processing units 3020 to 302 n of the virtual GW 3010.
[0232]
　As a result, similarly to the example shown in FIG. 30, the virtual GWs 3010 and 3040 can identify EPS bearers as virtual IP flows. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0233]
　Although the downlink has been described in FIG. 31, EPS bearers can also be identified for the uplink by the same method. That is, by constructing a virtual IP network between the virtual GWs 3010 and 3040 set in the secondary eNB 323 and the UE 311, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN in the uplink.
[0234]
　According to the method using the virtual IP flow shown in FIGS. 30 and 31, the number of EPS bearers that can be transferred to the WLAN as in the case of using, for example, a VLAN tag is not limited to the number of bits of the VLAN tag but the EPS bearer Can be identified. In addition, according to the method using the virtual IP flow shown in FIGS. 30 and 31, the eNB 321 and the secondary eNB 323 can be connected not only by the GTP tunnel but also by Ethernet or the like.
[0235]
　Further, according to the method using the virtual IP flow shown in FIGS. 30 and 31, it is possible to identify the EPS bearer without setting the DL TFT in the UE 311 or setting the UL TFT in the eNB 321 . Further, according to the method using the virtual IP flow shown in FIGS. 30 and 31, the EPS bearer can be identified without adding a header such as a VLAN tag to the user data transferred to the WLAN.
[0236]
　FIG. 32 is a diagram showing an example of a method for identifying an EPS bearer using a VLAN in the wireless communication system according to the third embodiment. In FIG. 32, parts similar to those shown in FIG. 15 or FIG. 30 are denoted by the same reference numerals, and description thereof is omitted. In FIG. 30, a method of identifying an EPS bearer by constructing a virtual IP network has been described. In FIG. 32, a method of identifying an EPS bearer by a VLAN virtualizing Ethernet will be described.
[0237]
　In addition, in FIG. 32, a case where the eNB 321 performs aggregation using the LTE-A and the WLAN at the same time in a configuration having the WLAN communication function (eNB + WLAN) for the downlink will be described. In this case, the EPS bearers 1500 to 150 n are bearers in the downward direction from the eNB 321 to the UE 311.
[0238]
　In the example shown in FIG. 32, virtual GWs 3010 and 3040 are set in eNB 321 and UE 311, respectively, as in the example shown in FIG. 30. However, in the example shown in FIG. 32, the virtual GW 3010 of the eNB 321 includes VLAN processing units 3210 to 321 n and MAC processing units 3220 to 322 n (802.3 MAC). Also, the virtual GW 3040 of the UE 311 includes MAC processing units 3230 to 323 n (802.3 MAC) and de-VLAN processing units 3240 to 324 n.
[0239]
　The EPS bearers 1500 to 150 n via the PDCP layers 1510 to 151 n are transferred to the VLAN processing units 3210 to 321 n of the virtual GW 3010. The VLAN processors 3210 to 321n classify the EPS bearers 1500 to 150n into local IP flows between the eNBs 321 and 311 by VLANs and transfer the classified IP flows to the MAC processors 3220 to 322n.
[0240]
　For example, the VLAN processing units 3210 to 321 n map the VLAN tags to the EPS bearers 1500 to 150 n on a one-to-one basis. The VLAN identifiers of the IP flows transferred from the VLAN processing units 3210 to 321 n can be 0 to n, respectively.
[0241]
　The MAC processing units 3220 to 322 n convert the IP flows transferred from the VLAN processing units 3210 to 321 n into MAC frames such as Ethernet and IEEE 802.3. The source MAC address (src MAC) of each MAC frame converted by the MAC processing units 3220 to 322 n can be, for example, any private address (any private) in the virtual GW 3010 or 3040. For example, the source MAC address of the MAC frame can be an address (x is an arbitrary value) where the first octet is "xxxxxx10". Further, the destination MAC address (dst MAC) of each MAC frame converted by the MAC processing units 3220 to 322 n can be, for example, the MAC address (UE MAC) of the UE 311.
[0242]
　Further, the VLAN tag (VLAN tag) of each MAC frame converted by the MAC processing units 3220 to 322 n can be 0 to n corresponding to each EPS bearer, for example. In this manner, a VLAN tag for each EPS bearer is added to each MAC frame. The VLAN tag is, for example, a 12-bit tag. Therefore, it is possible to build up to 4094 VLANs among the virtual GWs 3010 and 3040. If each UE including the UE 311 has all the EPS bearers and all EPS bearers are transferred to the WLAN, it is possible to accommodate about 472 UEs in the WLAN. However, since it is unlikely that all EPS bearers are established and actually communicate, it is possible to transfer a sufficient number of EPS bearers to the WLAN by using VLANs.
[0243]
　The eNB 321 performs AC classification 1540 on the MAC frame with the VLAN tag converted by the MAC processing units 3220 to 322 n. Then, the eNB 321 transmits the MAC frame with the VLAN tag that has performed the AC classification 1540 to the UE 311 via the WLAN 1550.
[0244]
　The UE 311 performs AC declaration 1560 on the MAC frame with the VLAN tag received from the eNB 321 via the WLAN 1550. The MAC processing units 3230 to 323 n of the virtual GW 3040 are MAC processing units corresponding to the EPS bearers 1500 to 150 n, respectively. Each of the MAC processing units 3230 to 323 n receives the MAC frame of the corresponding EPS bearer as an IP flow by referring to the VLAN tag attached to the MAC frame for the MAC frame on which the AC declaration 1560 is performed .
[0245]
　The de-VLAN processing units 3240 to 324 n convert the IP flows received by the MAC processing units 3230 to 323 n into EPS bearers 1500 to 150 n, respectively. The PDCP layers 1570 to 157 n process the EPS bearers 1500 to 150 n converted by the de-VLAN processing units 3240 to 324 n, respectively.
[0246]
　In this manner, by setting the VLAN for each EPS bearer between the virtual GWs 3010 and 3040, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0247]
　Although the downlink has been described in FIG. 32, the EPS bearer can also be identified for the uplink by the same method. That is, by setting the VLAN for each EPS bearer between the virtual GWs 3010 and 3040 set in the eNB 321 and the UE 311, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN in the uplink.
[0248]
　FIG. 33 is a diagram showing another example of a method for identifying an EPS bearer using a VLAN in the radio communication system according to the third embodiment. In FIG. 33, parts similar to those shown in FIG. 15 or FIG. 32 are denoted by the same reference numerals, and description thereof is omitted.
[0249]
　33, a description will be given of a case where aggregation is performed in which the eNB 321 becomes the master eNB and the WLAN independent configuration using the secondary eNB 323 having the function of WLAN communication with the eNB is performed for the downlink simultaneously using the LTE-A and WLAN. In this case, between the eNB 321 and the secondary eNB 323, GTP tunnels 1520 to 152 n for each EPS bearer are set.
[0250]
　The VLAN processing units 3210 to 321 n shown in FIG. 32 are set in the secondary eNB 323 in the example shown in FIG. 33. The secondary eNB 323 receives each IP packet transmitted from the UE 311 via the WLAN 1550. Then, the secondary eNB 323 transfers the received IP packets to the VLAN processing units 3210 to 321 n of the virtual GW 3010.
[0251]
　As a result, similar to the example shown in FIG. 32, the virtual GWs 3010 and 3040 can identify EPS bearers as virtual IP flows. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0252]
　Although the downlink has been described in FIG. 33, the EPS bearer can also be identified in the same manner for the uplink. That is, by setting a VLAN for each EPS bearer between the virtual GWs 3010 and 3040 set in the secondary eNB 323 and the UE 311, the EPS bearer of each IP packet transferred to the WLAN in the uplink can be identified.
[0253]
　According to the method using the VLANs shown in FIG. 32 and FIG. 33, it is possible to connect between the eNB 321 and the secondary eNB 323 not only by the GTP tunnel but also by Ethernet or the like. In addition, according to the method using the VLANs shown in FIGS. 32 and 33, in the WLAN, EPS bearer of each IP packet is identified by adding a VLAN tag without processing the packet referring to the IP header be able to. In addition, according to the method using the VLANs shown in FIGS. 32 and 33, the EPS bearer can be identified without setting the DL TFT in the UE 311 or setting the UL TFT in the eNB 321.
[0254]
　FIG. 34 is a diagram illustrating an example of a method of identifying an EPS bearer using GRE tunneling in the radio communication system according to the third embodiment. In FIG. 34, parts similar to those shown in FIG. 15 or FIG. 30 are denoted by the same reference numerals, and description thereof is omitted.
[0255]
　In FIG. 34, the case where the eNB 321 performs the aggregation using the LTE-A and WLAN at the same time in the configuration having the function (WLAN communication) of the WLAN communication (eNB + WLAN) is described for the downlink. In the example shown in FIG. 34, the EPS bearers 1500 to 150 n are bearers in the downstream direction from the eNB 321 to the UE 311.
[0256]
　Further, in the example shown in FIG. 34, the virtual GW 3010 is set between the PDCP layers 1510 to 151 n in the eNB 321 and the WLAN 1550. The virtual GW 3010 includes GRE processing units 3410 to 341 n and a MAC processing unit 3030 (802.3 MAC). A virtual GW 3040 is set between the WLAN 1550 and the PDCP layers 1570 to 157 n in the UE 311. The virtual GW 3040 includes a MAC processing unit 3050 (802.3 MAC) and de-GRE processing units 3420 to 342 n.
[0257]
　The EPS bearers 1500 to 150 n via the PDCP layers 1510 to 151 n are transferred to the GRE processing units 3410 to 341 n of the virtual GW 3010. The GRE processing units 3410 to 341 n classify the EPS bearers 1500 to 150 n into local IP flows between the eNBs 321 and 311 using GRE (Generic Routing Encapsulation) tunneling, and classify each IP flow into MAC processing units 3030.
[0258]
　For example, the GRE processing units 3410 to 341 n add GRE headers to the IP packets corresponding to the EPS bearers 1500 to 150 n, add the IP headers, and transfer the IP packets to the MAC processing unit 3030 as IP flows. The transmission source IP address (src IP) of each IP flow transferred from the GRE processing units 3410 to 341 n can be, for example, a virtual GW 3010 (vGW). Further, the destination IP addresses (dst IP) of each IP flow transferred from the GRE processing units 3410 to 341 n can be set to C-RNTI + 0 to C-RNTI + n, respectively.
[0259]
　As in the example shown in FIG. 30, for example, the MAC processing unit 3030 converts each IP flow transferred from the GRE processing units 3410 to 341 n into a MAC frame of Ethernet (IEEE 802.3).
[0260]
　The eNB 321 performs AC classification 1540 on the MAC frame converted by the MAC processing unit 3030, and transmits the MAC frame subjected to AC classification 1540 to the UE 311 via the WLAN 1550. Thereby, the eNB 321 can transmit the user data with the GRE tunnel (encapsulation tunnel) of the WLAN set between the eNB 321 and the UE 311.
[0261]
　The UE 311 performs AC declaration 1560 on the MAC frame received from the eNB 321 via the WLAN 1550. As in the example shown in FIG. 30, for example, the MAC processing unit 3050 of the virtual GW 3040 receives the MAC frame on which the AC declassification 1560 has been performed as an IP flow.
[0262]
　The de-GRE processing units 3420 to 342 n convert the IP flow into the EPS bearer by referring to the destination IP address (dst IP) included in the IP header of the IP flow with respect to the IP flow received by the MAC processing unit 3050 .
[0263]
　In this way, by setting the virtual GWs 3010 and 3040 respectively in the eNB 321 and the UE 311 and using the GRE tunneling, it is possible to identify the EPS bearer as the IP flow in the virtual GWs 3010 and 3040. The IP address and the MAC address can be composed of addresses in the private space. By constructing the GRE tunnel between the virtual GWs 3010 and 3040 in this way, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0264]
　Although the downlink has been described in FIG. 34, the EPS bearer can also be identified for the uplink by the same method. That is, by constructing the GRE tunnel between the virtual GWs 3010 and 3040, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN in the uplink.
[0265]
　FIG. 35 is a diagram showing another example of a method of identifying an EPS bearer using GRE tunneling in the radio communication system according to the third embodiment. In FIG. 35, parts similar to those shown in FIG. 15 or FIG. 34 are denoted by the same reference numerals, and description thereof is omitted.
[0266]
　In FIG. 35, a description will be given of a case where aggregation is performed in which the eNB 321 becomes the master eNB and the WLAN independent configuration using the secondary eNB 323 having the function of WLAN communication with the eNB is used for the downlink simultaneously using LTE-A and WLAN. In this case, between the eNB 321 and the secondary eNB 323, GTP tunnels 1520 to 152 n for each EPS bearer are set.
[0267]
　The secondary eNB 323 receives each IP packet transmitted from the UE 311 via the WLAN 1550. Then, the secondary eNB 323 transfers the received IP packets to the GRE processing units 3410 to 341 n.
[0268]
　Thus, similarly to the example shown in FIG. 34, the UE 311 can use the GRE tunneling to identify the EPS bearer of each IP packet transferred to the WLAN. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0269]
　According to the method using GRE tunneling shown in FIGS. 34 and 35, the number of EPS bearers transferred to the WLAN is not limited to the number of bits of the VLAN tag, as in the case of using a VLAN tag, for example, the EPS bearer is identified It is possible. Also, according to the method using GRE tunneling shown in FIG. 34 and FIG. 35, it is possible to connect between the eNB 321 and the secondary eNB 323 not only by the GTP tunnel but also by Ethernet or the like.
[0270]
　In addition, according to the method using GRE tunneling shown in FIGS. 34 and 35, EPS bearers can be identified without setting DL TFTs in the UE 311 or setting UL TFTs in the eNB 321 . Further, according to the method using GRE tunneling shown in FIGS. 34 and 35, EPS bearers can be identified without adding a header such as a VLAN tag to the user data transferred to the WLAN.
[0271]
　FIG. 36 is a diagram showing an example of a method of identifying an EPS bearer using PDCPoIP in the radio communication system according to the third embodiment. In FIG. 36, parts similar to those shown in FIG. 15 or FIG. 30 are denoted by the same reference numerals, and description thereof is omitted.
[0272]
　36, a description will be given of a case where the eNB 321 performs aggregation using the LTE-A and the WLAN at the same time in a configuration having the WLAN communication function (eNB + WLAN) for the downlink. In the example shown in FIG. 36, the EPS bearers 1500 to 150 n are bearers in the downstream direction from the eNB 321 to the UE 311.
[0273]
　Further, in the example shown in FIG. 36, the virtual GW 3010 is set between the PDCP layers 1510 - 151 n in the eNB 321 and the WLAN 1550. The virtual GW 3010 includes PDCPoIP processing units 3610 to 361 n and a MAC processing unit 3030 (802.3 MAC). A virtual GW 3040 is set between the WLAN 1550 and the PDCP layers 1570 to 157 n in the UE 311. The virtual GW 3040 includes a MAC processing unit 3050 (802.3 MAC) and de-PDCPoIP processing units 3620 to 362 n (de-PoIP).
[0274]
　The EPS bearers 1500 to 150 n via the PDCP layers 1510 to 151 n are transferred to the PDCPoIP processing units 3610 to 361 n of the virtual GW 3010. The PDCPoIP processing units 3610 to 361 n perform PDCPoIP (Packet Data Convergence Protocol on IP) processing for classifying the addresses of the outer IP headers of the EPS bearers 1500 to 150 n into virtual IP addresses by classifying them into virtual IP addresses. The virtual IP flow is, for example, a local virtual data flow between the eNB 321 and the UE 311. The virtual destination IP address is the destination address of the virtual IP flow. The PDCPoIP processing units 3610 to 361 n transfer each classified virtual IP flow to the MAC processing unit 3030.
[0275]
　For example, the PDCPoIP processing units 3610 to 361 n map the EPS bearers 1500 to 150 n and the virtual destination IP address on a one-to-one basis. The virtual source IP address (src IP) of each virtual IP flow transferred from the PDCPoIP processing units 3610 to 361 n can be, for example, a virtual GW 3010 (vGW). In addition, the virtual destination IP address (dst IP) of each virtual IP flow transferred from the PDCPoIP processing units 3610 to 361 n can be set to C-RNTI + 0 to C-RNTI + n, respectively.
[0276]
　The C-RNTI is temporarily allocated to the UE 311 and is a unique identifier of the UE 311 within the LTE-A cell. For example, the C-RNTI has a value of 16 bits. As in the example shown in FIG. 36, by generating the virtual source IP address by adding the C-RNTI and the bearer identifiers (0 to n), it is possible to avoid occurrence of duplication of virtual source IP addresses . For example, when using the IP address of class A, it becomes possible to identify EPS bearers of about 24 bits that are sufficient for transmission by the WLAN. Here, the case where the virtual source IP address is generated by adding the C-RNTI and the bearer identifier has been described, but the method of generating the virtual source IP address is not limited to this.
[0277]
　The MAC processing unit 3030 converts each virtual IP flow transferred from the PDCPoIP processing units 3610 to 361 n into MAC frames such as Ethernet and IEEE 802.3. In this case, the source MAC address (src MAC) of the MAC frame can be any private address (any private) in the virtual GW 3010, 3040, for example. For example, the source MAC address of the MAC frame can be an address (x is an arbitrary value) where the first octet is "xxxxxx10". Further, the destination MAC address (dst MAC) of the MAC frame can be, for example, the MAC address (UE MAC) of the UE 311.
[0278]
　The eNB 321 performs AC classification 1540 on the MAC frame converted by the MAC processing unit 3030, and transmits the MAC frame subjected to AC classification 1540 to the UE 311 via the WLAN 1550.
[0279]
　The UE 311 performs AC declaration 1560 on the MAC frame received from the eNB 321 via the WLAN 1550. The MAC processing unit 3050 of the virtual GW 3040 receives the MAC frame on which the AC declaration 1560 has been performed as a virtual IP flow.
[0280]
　With respect to the virtual IP flow received by the MAC processing unit 3050, the de-PDCPoIP processing units 3620 to 362 n convert the virtual IP flow into the EPS bearer by referring to the virtual destination IP address (dst IP) of the virtual IP flow . At this time, the virtual destination IP address of the virtual IP flow is converted to the original IP address by de-PDCPoIP by the de-PDCPoIP processing units 3620 to 362 n.
[0281]
　In this manner, by setting the virtual GWs 3010 and 3040 respectively in the eNB 321 and the UE 311 and using the address translation by PDCPoIP, it is possible to identify the EPS bearer as the virtual IP flow in the virtual GWs 3010 and 3040. The IP address and the MAC address can be composed of addresses in the private space. By constructing the virtual IP network between the virtual GWs 3010 and 3040 in this manner, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0282]
　Although the downlink has been described in FIG. 36, the EPS bearer can also be identified in the same manner for the uplink. That is, by constructing a virtual IP network between the virtual GWs 3010 and 3040 set in the eNB 321 and the UE 311, the EPS bearer of each IP packet transferred to the WLAN in the uplink can be identified.
[0283]
　FIG. 37 is a diagram showing another example of a method of identifying an EPS bearer using PDCPoIP in the radio communication system according to the third embodiment. In FIG. 37, parts similar to those shown in FIG. 15 or FIG. 36 are denoted by the same reference numerals, and description thereof is omitted.
[0284]
　In FIG. 37, a description will be given of a case where aggregation is performed in which the eNB 321 becomes the master eNB and the WLAN independent configuration using the secondary eNB 323 having the function of WLAN communication with the eNB is used for the downlink simultaneously using LTE-A and WLAN. In this case, between the eNB 321 and the secondary eNB 323, GTP tunnels 1520 to 152 n for each EPS bearer are set.
[0285]
　The PDCPoIP processing units 3610 to 361 n shown in FIG. 36 are set in the secondary eNB 323 in the example shown in FIG. 37. The secondary eNB 323 receives each IP packet transmitted from the UE 311 via the WLAN 1550. In addition, the secondary eNB 323 transfers the received IP packets to the PDCPoIP processing units 3610 to 361 n of the virtual GW 3010.
[0286]
　As a result, similarly to the example shown in FIG. 36, EPS bearers can be identified as virtual IP flows in virtual GWs 3010 and 3040. For this reason, the wireless communication system 300 enables aggregation without increasing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class, thereby increasing the amount of user data that can be transmitted.
[0287]
　Although the downlink has been described in FIG. 37, the EPS bearer can be identified for the uplink by the same method. That is, by constructing a virtual IP network between the virtual GWs 3010 and 3040 set in the secondary eNB 323 and the UE 311, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN in the uplink.
[0288]
　According to the method using address conversion by PDCPoIP shown in FIG. 36 and FIG. 37, the number of EPS bearers that can be transferred to the WLAN as in the case of using a VLAN tag, for example, is not limited to the number of bits of the VLAN tag but EPS Bearer can be identified. In addition, according to the method using address conversion by PDCPoIP shown in FIG. 36 and FIG. 37, it is possible to connect between the eNB 321 and the secondary eNB 323 not only by the GTP tunnel but also by Ethernet or the like.
[0289]
　In addition, according to the method using address conversion by PDCPoIP shown in FIGS. 36 and 37, without setting the DL TFT in the UE 311 or setting the UL TFT in the eNB 321, it is possible to identify the EPS bearer It is possible. In addition, according to the method using address conversion by PDCPoIP shown in FIG. 36 and FIG. 37, it is possible to identify the EPS bearer without adding a header such as a VLAN tag to the user data transferred to the WLAN.
[0290]
　As described above, according to the third embodiment, it is possible to perform aggregation using LTE-A and WLAN at the same time without providing the constraint of not simultaneously aggregating a plurality of EPS bearers having the same QoS class. Therefore, it is possible to increase the amount of user data that can be transmitted.
[0291]
　In the downlink from the eNB 321 to the UE 311, however, there is a case where it is sufficient to forward the user data received by the UE 311 as a radio bearer to an upper layer (for example, an application layer) of the own station without converting it into a bearer. In such a case, even when a plurality of EPS bearers have the same QoS class, the UE 311 can perform aggregation using the LTE-A and the WLAN at the same time without identifying the bearer.
[0292]
(Embodiment 4)
　FIGS. 38 and 39 are diagrams for explaining processing on data transmitted by the WLAN in the radio communication system according to Embodiment 4. FIG. The protocol stack shown in FIG. 38 is different from the protocol stacks of the PDCP layer 3801 (PDCP PDU), the outer IP layer 3802, the MAC layer 3803 (WLAN MAC) of the WLAN, for the data transmitted by the WLAN as in the second and third embodiments Which are performed in order.
[0293]
　In the above-described embodiment, the term "outer IP" is used for convenience, but the outer IP is technically simply IP (Internet Protocol). This point also applies to this embodiment.
[0294]
　The PDCP layer 3801 corresponds to, for example, the PDCP layer in the aggregation processing 1212 shown in FIG. 12 and the PDCP layer 1901 shown in FIGS. 19 to 24. The outer IP layer 3802 corresponds to, for example, the processing of the outer IP in the aggregation processing 1212 shown in FIG. 12 and the outer IP layer 1900 shown in FIGS. 19 to 24. The MAC layer 3803, for example, in the aggregation processing 1212 shown in FIG. It corresponds to 11 × MAC processing.
[0295]
　In the protocol stack shown in FIG. 38, by using the outer IP layer 3802, when data is transmitted by WLAN, for example, ARP (Address Resolution Protocol) at IP addresses data The destination MAC address can be obtained. The ARP is, for example, ARP defined in RFC 826. In this case, the WLAN node (eNB 321 or secondary eNB 323, for example) can also operate in a mode like a router, for example.
[0296]
　The protocol stack shown in FIG. 39 shows processing for data transmitted by the WLAN in the radio communication system 300 according to the fourth embodiment. Like the protocol stack shown in FIG. 39, in the radio communication system 300 according to the fourth embodiment, the processing of the PDCP layer 3801, the processing of the adaptation layer 3901 (Adaptation Layer), the processing of the WLAN The processing of the MAC layer 3803 is performed. In the processing shown in FIG. 39, a packet transmitted by the WLAN is tunneled by being given a predetermined header by the adaptation layer 3901 after being processed by the PDCP layer 3801 and transferred to the WLAN side.
[0297]
　In this way, processing of the adaptation layer 3901 may be performed on the data transmitted by the WLAN instead of the processing of the outer IP layer 3802. Such processing shown in FIG. 39 may be effective depending on, for example, requirements of the LTE-WLAN architecture and problems in transmission of IP packets in the WLAN.
[0298]
　However, in the process shown in FIG. 39, it is not possible to obtain the MAC address from the IP address by using the ARP in the IP. On the other hand, for example, by providing the ARP processing based on RFC 826 in the adaptation layer 3901, it is possible to obtain the MAC address from the IP address by using the ARP in the adaptation layer 3901. In this case, the WLAN node (eNB 321 or secondary eNB 323, for example) operates in a mode like a bridge, for example.
[0299]
　For example, in ARP based on RFC 826, the upper layer of ARP is specified by "EtherType" of Ethernet. Although the "EtherType" is undefined in the current 3GPP protocol, ARP based on RFC 826 can be applied to the adaptation layer 3901 when a new "EtherType" is defined in the 3GPP protocol.
[0300]
　However, it may be difficult to apply the ARP based on RFC 826 to the adaptation layer 3901. On the other hand, instead of applying the ARP based on RFC 826 to the adaptation layer 3901, a unique address resolution method may be used. In this case, the WLAN node (eNB 321 or secondary eNB 323, for example) can also operate in a mode like a bridge, for example. The architecture of this unique address resolution method will be described below.
[0301]
　FIG. 40 is a sequence diagram showing an example of processing in the wireless communication system according to the fourth embodiment. In the radio communication system 300 according to the fourth embodiment, address resolution is realized by executing the respective steps shown in FIG. 40, for example. The communication apparatus 4001 shown in FIG. 40 is a transmission source that transmits data to the UE 311 via the eNB 321. For example, the communication device 4001 is the PGW 332 of the packet core network 330 or the like.
[0302]
　In FIG. 40, data transmitted from the communication device 4001 to the UE 311 by the WLAN will be described. In this case, the transmission path between the communication device 4001 and the eNB 321 is an IP network, and the transmission path between the eNB 321 and the UE 311 is LTE or LTE-A. Further, in the example shown in FIG. 40, a configuration of a WLAN independent type using the secondary eNB 323 having the eNB 321 as a master eNB and a function of the WLAN communication with the eNB will be described.
[0303]
　First, the eNB 321 transmits an RRC connection reconfiguration including the LTE-WLAN configuration for setting the LTE-WLAN aggregation to the UE 311 (step S 4001). Next, the UE 311 transmits an RRC connection reconfiguration complete for RRC connection reconfiguration to the eNB 321 (step S 4002). In addition, the UE 311 stores the MAC address of the UE 311 in the RRC connection reconfiguration completion transmitted in step S 4002.
[0304]
　Next, the eNB 321 transmits a WLAN addition request for setting the WLAN in the LTE-WLAN aggregation to the secondary eNB 323 which is the WLAN node (step S 4003). In addition, the eNB 321 stores the setting information including the MAC address of the UE 311 acquired from the RRC connection reconfiguration complete received in the step S 4002 in the WLAN addition request transmitted in the step S 4003.
[0305]
　On the other hand, the secondary eNB 323 stores the MAC address of the UE 311 acquired from the WLAN addition request from the eNB 321 in association with the IP address of the UE 311.
[0306]
　Next, it is assumed that the communication apparatus 4001 transmits data to the UE 311 to the eNB 321 (step S 4004). Data 4010 is data transmitted in step S4004. The data 4010 includes a source IP address 4011, a destination IP address 4012, and an IP payload 4013. The transmission source IP address 4011 is the IP address of the communication device 4001 that is the transmission source of the data 4010. The destination IP address 4012 is the IP address of the UE 311 that is the destination of the data 4010. The IP payload 4013 is a payload (for example, user data) of the data 4010. Since the IP packet is originally transmitted by the GTP tunnel, the GTP header is added, but it is proportionate here.
[0307]
　Next, the eNB 321 converts the data received in step S 4004 into PDCP PDU and transfers it to the secondary eNB 323 (step S 4005). Next, the secondary eNB 323 transmits the data converted into the PDCP PDU in step S4005 and transmitted to the UE 311 by WLAN (IEEE MAC) (step S4006). Data 4020 is data transmitted in step S4006.
[0308]
　The data 4020 is data in which a destination MAC address 4021 and a transmission source MAC address 4022 are added as a header to the transmission source IP address 4011, the destination IP address 4012 and the IP payload 4013 of the data 4010. The PDCP PDU is included in the IP payload. The destination MAC address 4021 is the MAC address of the UE 311 stored in the secondary eNB 323 in step S 4003. The source MAC address 4022 is the MAC address of the secondary eNB 323 that is the source of the data 4020.
[0309]
　As shown in FIG. 40, when the eNB 321 transmits the RRC connection reconfiguration to the UE 311 in the LTE-WLAN aggregation, the UE 311 stores its own MAC address in its response signal. This makes it possible for the eNB 321 and the secondary eNB 323 to acquire the MAC address of the UE 311 without using the IP ARP. In this way, it is possible to resolve the MAC address by using, for example, an RRC message.
[0310]
　the WLAN independent type configuration in which the eNB 321 becomes the master eNB and the secondary eNB 323 having the function of the WLAN communication with the eNB is used has been described, the eNB 321 may have a function of the WLAN communication without using the secondary eNB 323. In this case, for example, step S4003 is unnecessary, and the eNB 321 stores the MAC address of the UE 311 in association with the IP address of the UE 311.
[0311]
　Then, the eNB 321 transmits, to the UE 311, the data 4020 obtained by adding the destination MAC address 4021 and the transmission source MAC address 4022 to the data 4010 received from the communication device 4001. In this case, the transmission source MAC address 4022 is the MAC address of the eNB 321 that is the transmission source of the data 4020.
[0312]
　In addition, descending data transmitted from the communication device 4001 to the UE 311 has been described. Similarly, uplink data transmitted from the UE 311 to the communication device 4001 can be resolved using the RRC message. For example, the eNB 321 stores the MAC address of the secondary eNB 323 in the RRC connection reconfiguration transmitted by the communication device 4001. The MAC address of the secondary eNB 323 may be stored in the eNB 321 when connecting the eNB 321 and the secondary eNB 323 or may be acquired by inquiring the secondary eNB 323 by the eNB 321.
[0313]
　The UE 311 stores the MAC address of the secondary eNB 323 acquired from the RRC connection reconfiguration from the eNB 321 in association with the IP address of the secondary eNB 323. Then, when transmitting data to the communication device 4001 by WLAN, the UE 311 transmits the data to the secondary eNB 323 using the stored MAC address of the secondary eNB 323 as a destination. In this manner, with respect to uplink data transmitted from the UE 311 to the communication device 4001, the MAC address can also be resolved using the RRC message.
[0314]
　FIG. 41 is a sequence diagram showing a method of notifying the MAC address by another RRC message in the process in the radio communication system according to the fourth embodiment. In FIG. 41, parts similar to those shown in FIG. 40 are denoted by the same reference numerals, and description thereof is omitted. In the RRC connection establishment procedure, the UE 311 transmits an RRC connection setup to the eNB 321 before step S4001 (step S4101). In addition, the UE 311 stores the MAC address of the UE 311 in the RRC connection setup to be transmitted in step S 4101. In this case, the UE 311 may not store the MAC address of the UE 311 in the RRC connection reconfiguration completion transmitted in step S 4002.
[0315]
　FIG. 42 is a sequence diagram showing a method of notifying the MAC address by another RRC message in the processing in the radio communication system according to the fourth embodiment. In FIG. 42, parts similar to those shown in FIG. 40 are denoted by the same reference numerals, and description thereof is omitted. After step S4002, UE 311 transmits an RRC message different from RRC connection reconfiguration complete and RRC connection setup to eNB 321 (step S4201). In addition, the UE 311 stores the MAC address of the UE 311 in the RRC message transmitted in step S 4201. In this case, the UE 311 may not store the MAC address of the UE 311 in the RRC connection reconfiguration completion transmitted in step S 4002.
[0316]
　As shown in FIGS. 41 and 42, the RCC message used for notifying the MAC address of the UE 311 is not limited to the RRC connection reconfiguration complete, but can be various RRC messages.
[0317]
　FIG. 43 is a sequence diagram showing another example of processing in the wireless communication system according to the fourth embodiment. In FIG. 43, parts similar to those shown in FIG. 40 are denoted by the same reference numerals, and description thereof is omitted. In the wireless communication system 300 according to the fourth embodiment, address resolution may be realized by executing each step shown in FIG. 43.
[0318]
　Steps S4301 to S4305 shown in FIG. 43 are the same as steps S4001 to S4005 shown in FIG. However, in step S 4302, the UE 311 may not store the MAC address of the UE 311 in the RRC connection reconfiguration complete. Also, in step S 4303, the eNB 321 may not store the MAC address of the UE 311 in the WLAN addition request.
[0319]
　Following step S4305, eNB 321 operates ARP with UE 311 by adaptation layer 3901 (step S4306). Then, the eNB 321 notifies the secondary eNB 323 of the MAC address of the UE 311 acquired by ARP. As a result, the secondary eNB 323 can acquire the MAC address of the UE 311.
[0320]
　Alternatively, in step S 4306, ARP may be operated between the secondary eNB 323 and the UE 311. As a result, the secondary eNB 323 can acquire the MAC address of the UE 311.
[0321]
　The ARP operating in step S4306 may be ARP uniquely designed in the adaptation layer 3901 instead of ARP based on RFC 826, for example. The secondary eNB 323 can query the UE 311 for the MAC address using the ARP packet. The ARP packet will be described later (see, for example, FIG. 44). Note that the order of steps S4305 and S4306 may be interchanged.
[0322]
　Next, the secondary eNB 323 transmits the data converted into the PDCP PDU in step S4305 and transmitted to the UE 311 by WLAN (IEEE MAC) (step S4307). The data transmitted in step S4307 is the same as the data 4020 shown in FIG. 40, for example. In this case, the destination MAC address 4021 is the MAC address of the UE 311 acquired by the secondary eNB 323 by the ARP operated in step S 4306.
[0323]
　As shown in FIG. 43, when the eNB 321 sets the LTE-WLAN aggregation to the secondary eNB 323 (WLAN node), the adaptation layer 3901 operates its own ARP, so that the MAC address of the UE 311 can be acquired. In this manner, for example, the MAC address can be resolved by using the ARP designed independently in the adaptation layer 3901.
[0324]
　the WLAN independent type configuration in which the eNB 321 becomes the master eNB and the secondary eNB 323 having the function of the WLAN communication with the eNB is used has been described, the eNB 321 may have a function of the WLAN communication without using the secondary eNB 323. In this case, for example, step S4305 is unnecessary, and in step S4306 the eNB 321 activates the ARP in its own device. Thus, the eNB 321 can acquire the MAC address of the UE 311.
[0325]
　Then, the eNB 321 transmits, to the UE 311, the data 4020 obtained by adding the destination MAC address 4021 and the transmission source MAC address 4022 to the data 4010 received from the communication device 4001. In this case, the transmission source MAC address 4022 is the MAC address of the eNB 321 that is the transmission source of the data 4020.
[0326]
　Also, descending data transmitted from the communication device 4001 to the UE 311 has been described. Similarly, with regard to the uplink data transmitted from the UE 311 to the communication device 4001, the MAC address is similarly resolved by using the ARP designed independently be able to. For example, when transmitting data to the communication device 4001 by WLAN, the UE 311 activates the above-described unique ARP in its own device and obtains the MAC address of the secondary eNB 323 by making an inquiry to the secondary eNB 323.
[0327]
　Then, the UE 311 transmits the uplink data to the secondary eNB 323 using the acquired MAC address of the secondary eNB 323 as a destination. In this manner, with respect to the uplink data transmitted from the UE 311 to the communication device 4001, it is possible to resolve the MAC address by using the ARP designed independently.
[0328]
　FIG. 44 is a diagram showing an example of a packet format in ARP applicable to the fourth embodiment. As shown in FIG. 43, in the ARP uniquely designed in the adaptation layer 3901, for example, the packet 4400 shown in FIG. 44 can be used. In the packet 4400, "R" is a reserved bit (Reserved).
[0329]
　"D / C" is information indicating whether the packet 4400 is a data signal (data) or a control signal (control). "D" (data) or "C" (control) is specified for "D / C". When "D" is specified for "D / C", it indicates that the second and subsequent lines of the packet 4400 are PDCP PDUs. When "C" is specified for "D / C", it indicates that the second and subsequent lines of the packet 4400 are ARP control information. In the example shown in FIG. 44, since the packet 4400 is used as an ARP packet, "C" is designated as "D / C".
[0330]
　"Type" (Type) is information indicating whether the packet 4400 is a request signal or a response signal. "Type" (Type) is invalid if "D" is specified for "D / C". "Type" (Type) is specified as "Request" or "Response" when "C" is specified for "D / C". "LCID" indicates LCID (Logical Channel ID: logical channel ID) in LTE. "C-RNTI" (Cell-Radio Network Temporary Identifier) ​​is a cell radio network temporary identifier of the UE 311.
[0331]
　In the example shown in FIG. 44, since the packet 4400 is used as an ARP packet, ARP control information is stored in the second and subsequent rows of the packet 4400 as described above. For example, the secondary eNB 323 (WLAN node) that is the source of the MAC address inquiry transmits a packet 4400 specifying "request" as "type". In this case, the MAC address (48 bits) of the secondary eNB 323 is stored in the "source MAC address" of the packet 4400. Also, the MAC address (48 bits) for broadcasting is stored in the "destination MAC address" of the packet 4400. As a result, it is possible to broadcast the packet 4400 and make an inquiry about the MAC address to the UE 311.
[0332]
　The UE 311 can determine that the packet is addressed to its own terminal based on the "C-RNTI" of the packet 4400 with respect to the packet 4400 (request) from the secondary eNB 323. Upon receiving the packet 4400 from the secondary eNB 323, the UE 311 transmits a packet 4400 specifying "response" to "type". In this case, the MAC address (48 bits) of the UE 311 is stored in the "source MAC address" of the packet 4400. The MAC address of the secondary eNB 323 is stored in the "destination MAC address" of the packet 4400. As a result, the MAC address of the UE 311 can be notified to the secondary eNB 323.
[0333]
　However, not limited to the packet 4400 shown in FIG. 44, packets of various formats can be used for the ARP uniquely designed in the adaptation layer 3901. For example, if ARP uniquely designed in the adaptation layer 3901 includes identification information of a transmission destination such as "C-RNTI", "source MAC address" and "destination MAC address" Good. Also, when it is determined that the UE can be identified only by the MAC address, "C-RNTI" may be omitted.
[0334]
　As described above, according to the fourth embodiment, when, for example, the EPS bearers 1500 to 150 n are divided into LTE-A and WLAN for transmission, the PDCP packet transmitted by the WLAN can be tunneled by the adaptation layer 3901. As a result, on the receiving side, the data transmitted by the WLAN is received as a PDCP packet and the sequence control between the packet received by the LTE-A and the packet received by the WLAN is performed using the sequence number of the PDCP . Therefore, data transmission using LTE-A and WLAN at the same time becomes possible.
[0335]
　In addition, the receiving station can store the MAC address of the receiving station that can be used in the WLAN (second wireless communication) in the RRC (Radio Resource Control) message transmitted to the transmitting station . Thus, when data is transmitted using the WLAN, the transmitting station can transmit the data to the transmitting station with the MAC address acquired from the RRC message as the destination address. Therefore, even in the case of using adaptation layer 3901 without using IP (outer IP) in tunneling, MAC address can be resolved.
[0336]
　Alternatively, when transmitting data using the WLAN, the sending station may send a first packet to the receiving station requesting the MAC address of the receiving station available in the WLAN. In addition, in this case, the receiving station can transmit the second packet including the MAC address of the receiving station to the receiving station in response to the first packet from the transmitting station . This allows the transmitting station to transmit the data to the receiving station with the MAC address of the transmitting station acquired from the second packet from the transmitting station as the destination address. Therefore, even in the case of using adaptation layer 3901 without using IP (outer IP) in tunneling, MAC address can be resolved.
[0337]
　It should be noted that Embodiment 4 can be implemented in combination with any of Embodiments 1 to 3 described above as appropriate.
[0338]
　As described above, according to the wireless communication system, the base station, the mobile station and the processing method, it is possible to perform data transmission using the first wireless communication and the second wireless communication at the same time. For example, by allowing aggregation that simultaneously uses LTE-A and WLAN, it is possible to improve the transmission rate of user data.
[0339]
　If the ToS field can not be referred to in the WLAN when performing aggregation using the LTE-A and the WLAN at the same time, for example, it is conceivable that all traffic is best effort. However, in this case, QoS control according to the nature of traffic can not be performed. As an example, the traffic of VoLTE also becomes best effort, and the communication quality of VoLTE deteriorates.
[0340]
　On the other hand, according to the embodiments described above, by adding the outer IP header to the data to be transferred to the WLAN, the ToS field can be referred to in the WLAN and the QoS control according to the property of the traffic is possible become. As an example, traffic of VoLTE is classified as voice (VO) and transmitted by WLAN preferentially, whereby communication quality of VoLTE can be improved.
[0341]
　In addition, in 3GPP LTE-A, with a view to fifth-generation mobile communications, we aim to respond to increasing mobile traffic and improve the user experience, and to enhance cellular communications in cooperation with other wireless systems, Consideration of conversion is under way. Particularly in cooperation with WLAN, which is widely deployed in smart phones, in addition to home and business, it is a challenge.
[0342]
　In Release 8 of LTE, the technology for offloading user data to WLAN in the core network of LTE-A has been standardized. In Release 12 of LTE-A, it is now possible to offload considering the wireless channel usage rate of the WLAN, the user's offload preference, and the like. Also, dual connectivity has been standardized that aggregates (aggregates) frequency carriers among base stations of LTE-A and simultaneously transmits user data.
[0343]
　In Release 13 of LTE-A, the study of LAA (License Assisted Access), which is a radio access method utilizing the unlicensed frequency band, started. LAA is a carrier aggregation of an unlicensed frequency band and a licensed frequency band in LTE-A, and is a layer 1 technology for controlling radio transmission of an unlicensed frequency band by a control channel of LTE-A.
[0344]
　Also unlike LAA, standardization for LTE-A and WLAN to aggregate at Layer 2 and both to cooperate to perform cellular communication is about to be started. This is called LTE-WLAN aggregation. The LTE-WLAN aggregation has the following advantages compared with the above-described method.
[0345]
　First, with the aggregation technology in the core network, it is difficult to perform high-speed aggregation according to the radio quality of LTE-A, and overhead of the control signal transmitted to the core network occurs at the time of aggregation. In the LTE-WLAN aggregation, since the aggregation is performed in the layer 2 of the LTE-A, the radio quality of the LTE-A can be quickly reflected and a control signal to the core network is unnecessary.
[0346]
　In LAA, high-speed aggregation according to the radio quality of LTE-A is possible, but aggregation in cooperation with the WLAN outside the LTE-A base station is difficult. On the other hand, in LTE-WLAN aggregation, if LTE-A base stations are connected to the installed WLAN access points at the layer 2 level, cooperative aggregation becomes possible.
[0347]
　Currently, standardization is being promoted assuming not only the scenario where the WLAN is incorporated in the base station of the LTE-A, but also the scenario that is installed independently. In this case, it is important to establish a layer 2 configuration that enables user data transmission by identifying the LTE-A call (bearer) on the WLAN side and considering the QoS class of the LTE bearer. Therefore, it is required to ensure backward compatibility of LTE-A and not to impact the specification of WLAN. As for this, for example, a method of encapsulating the IP flow before layer 2 is conceivable, but there is room for discussion on the configuration of layer 2 that can identify the bearer of LTE-A on the WLAN side.
[0348]
　According to each of the embodiments described above, by devising the tunneling method of the PDCP packet obtained in Layer 2 of the LTE-A side, aggregation that simultaneously uses the LTE-A and the WLAN while considering the QoS class of the LTE bearer Becomes possible.
Explanation of sign

[Claim 1]
　A base station that controls a second radio communication different from the first radio communication by a control unit that controls a first radio communication; and a control unit that controls
　the second radio communication by using the first radio communication or the second radio communication, And a mobile station capable of
　performing data transmission between the base station and the mobile station, wherein, when transmitting data using the second wireless communication between the base station and the mobile station, the base station and the mobile station , And the processing section for performing the first wireless communication performs the tunneling processing on the data after the processing of the convergence layer for performing the first wireless communication, And transmits the data to the station on the receiving side out of the base station and the mobile station, and the station on the receiving side
　transmits the data transmitted from the station on the transmitting side by the first wireless communication and the data Data transmitted from the transmitting station by wireless communication If, for the reception, it makes it possible to perform on the basis of the first wireless communication processing,
　a wireless communication system, characterized in that.
[Claim 2]
　The processing unit transmits the sequence number assigned by the processing of the convergence layer to the station on the receiving side by the tunneling processing, and
　the first wireless communication processing is performed by the first wireless communication on the transmitting side And performing sequence control of data transmitted from the station and data transmitted from the transmitting station by the second wireless communication based on the sequence number. Radio communication system.
[Claim 3]
　3. The radio communication system according to claim 1, wherein data is transmitted by simultaneously using the first radio communication and the second radio communication between the base station and the mobile station.
[Claim 4]
　A processing unit for performing the first wireless communication in the station on the transmitting side, when transmitting data using the second wireless communication between the base station and the mobile station, And adding a header including the service quality information to the data after the processing of the convergence layer and transmitting the data to which the header is added to the station on the reception side To the radio communication system according to any one of claims 1 to 3.
[Claim 5]
　5. The radio communication system according to claim 4, wherein transmission control based on the service quality information is performed in the second radio communication.
[Claim 6]
　The wireless communication system according to claim 4 or 5, wherein the processing of the convergence layer includes at least one of concealment of the data, header compression, and addition of a sequence number.
[7]
　The processing unit for performing the first wireless communication in the station on the transmitting side aggregates a plurality of bearers of the mobile station in the convergence layer and transmits the data to the station on the receiving side by the aggregated bearer Wherein the wireless communication system further comprises:
[Claim 8]
　The control unit transmits the data of a plurality of bearers of the mobile station which are the same in service class to the station of the receiving side so as not to simultaneously transmit each data of the plurality of bearers using the second wireless communication Wherein the control unit controls the transmission of the data of the first radio communication system and the second radio communication system.
[Claim 9]
　When transmitting data from the base station to the mobile station using the second wireless communication, the mobile station transmits the data received by using the second wireless communication to the first mobile station And processes bearers corresponding to the data among the bearers of the radio communication of the first radio communication system without identifying bearers corresponding to the data.
[Claim 10]
　When data is transmitted from the mobile station to the base station using the second wireless communication, the base station transmits the data received using the second wireless communication from the mobile station Characterized by performing packet filtering using a filtering rule in an uplink to a base station to identify a bearer corresponding to the received data among the bearers of the first wireless communication of the mobile station Wherein said wireless communication system comprises:
[Claim 11]
　When transmitting data from the base station to the mobile station by using the second wireless communication, the mobile station transmits the data received using the second wireless communication from the base station Characterized by performing packet filtering using a filtering rule in a downlink to a mobile station to identify a bearer corresponding to the received data among the bearers of the first wireless communication of the mobile station The wireless communication system according to any one of claims 1 to 10.
[Claim 12]
　When data is transmitted between the base station and the mobile station by using the second wireless communication,
　the station on the transmission side transmits the data of the second base station, which is set between the base station and the mobile station
　Wherein the receiving station transmits data according to a virtual data flow of the first wireless communication of the mobile station according to a destination address of the virtual data flow that received the data, And identifies a bearer corresponding to the data
　that has been transmitted from the base station.
[Claim 13]
　When data is transmitted between the base station and the mobile station by using the second wireless communication,
　the station on the sending side transmits the second data set between the base station and the mobile station ,
　The station on the receiving side transmits the data by means of the identifier of the virtual local area communication network which has received the data and transmits the data of the bearer of the first wireless communication of the mobile station And identifies a bearer corresponding to the received data by comparing the received data with the received data
　.
[Claim 14]
　When data is transmitted between the base station and the mobile station by using the second wireless communication,
　the station on the sending side transmits the second data set between the base station and the mobile station , The
　receiving station transmits the data by means of a destination address of the encapsulated tunnel which has received the data and receives the bearer of the first radio communication of the mobile station And identifies a bearer corresponding to said data that has been transmitted by said
　first radio communication apparatus.
[Claim 15]
　When transmitting data using the second wireless communication between the base station and the mobile station, the base station and the mobile station transmit the data of the first wireless communication Setting a communication channel of a second wireless communication between the base station and the mobile station, and transmitting the data according to the set communication path. Radio communication system.
[Claim 16]
　The station on the receiving side stores the address of the station on the receiving side usable in the second wireless communication in a message of radio resource control to be transmitted to the station on the transmitting side,
　and the base station and the mobile station , The station on the transmitting side sets the address obtained from the message of the radio resource control as a destination address and transmits the data to the transmitting side at the sending side when data is transmitted using the second radio communication And transmits the
　result to the station . 17. The wireless communication system according to claim 1 , further comprising:
[Claim 17]
　When data is transmitted between the base station and the mobile station by using the second radio communication,
　the station on the transmission side transmits the data of the station on the reception side usable in the second radio communication Wherein the first station transmits a first packet requesting an address to the station on the receiving side and the station on the receiving side transmits a
　second packet including the address to the first packet from the station on the transmitting side The station on the transmitting side transmits the data to the station on the receiving side
　with the address acquired from the second packet from the station on the receiving side as a destination address,
　Wherein said wireless communication system comprises:
[Claim 18]
　A base station capable of data transmission with a mobile station by using a first wireless communication or a second wireless communication different from the first wireless communication, the base station
　comprising: a first wireless communication and a second wireless communication ,
　A processing unit for performing the first wireless communication, wherein when transmitting data from the base station to the mobile station using the second wireless communication, the first wireless communication is performed on the first And a processing unit which performs tunneling processing on the data after the processing of the convergence layer for performing wireless communication of
　the base station , and transmits the data to the mobile station.
[Claim 19]
　A mobile station capable of data transmission with a base station using a first wireless communication or a second wireless communication different from the first wireless communication, the mobile station
　comprising: a processing unit for performing the first wireless communication Wherein, when transmitting data from the mobile station to the base station using the second wireless communication, the data after the processing of the convergence layer for performing the first wireless communication is tunneled And to transmit the result to the base
　station.
[Claim 20]
　A processing method by a base station capable of data transmission with a mobile station using a first wireless communication or a second wireless communication different from the first wireless communication, the method
　comprising: A
　processor for controlling a second wireless communication and performing the first wireless communication, when transmitting data from the base station to the mobile station using the second wireless communication, controlling the first wireless communication, And performing the tunneling processing on the data after the processing of the convergence layer for performing the wireless communication of the mobile station, to the mobile station
　.
[Claim 21]
　A processing method by a mobile station capable of data transmission with a base station by using a first wireless communication or a second wireless communication different from the first wireless communication,
　wherein the first wireless communication is performed Wherein when the data is transmitted from the mobile station to the base station using the second wireless communication in the processing unit for processing the convergence layer for performing the first wireless communication,
　And performs tunneling processing and transmits the tunneling processing to the base station .