WO2016163036A1 - Système de communication sans fil, station de base, station mobile, et procédé de traitement - Google Patents

Système de communication sans fil, station de base, station mobile, et procédé de traitement Download PDF

Info

Publication number
WO2016163036A1
WO2016163036A1 PCT/JP2015/063953 JP2015063953W WO2016163036A1 WO 2016163036 A1 WO2016163036 A1 WO 2016163036A1 JP 2015063953 W JP2015063953 W JP 2015063953W WO 2016163036 A1 WO2016163036 A1 WO 2016163036A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communication
data
station
wlan
base station
Prior art date
Application number
PCT/JP2015/063953
Other languages
English (en)
Japanese (ja)
Inventor
好明 太田
慎一郎 相川
大出　高義
純一 須加
武智　竜一
Original Assignee
富士通株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to CA2982804A priority Critical patent/CA2982804C/fr
Application filed by 富士通株式会社 filed Critical 富士通株式会社
Priority to BR112017021425-3A priority patent/BR112017021425A2/pt
Priority to JP2017511445A priority patent/JP6172419B2/ja
Priority to CN202310949372.8A priority patent/CN116744247A/zh
Priority to EP15888527.7A priority patent/EP3282747B1/fr
Priority to CN201580078671.2A priority patent/CN107534898A/zh
Priority to KR1020177028778A priority patent/KR102052466B1/ko
Priority to MX2017012980A priority patent/MX360887B/es
Priority to RU2017134998A priority patent/RU2682420C1/ru
Publication of WO2016163036A1 publication Critical patent/WO2016163036A1/fr
Priority to US15/725,890 priority patent/US11690092B2/en
Priority to US16/373,307 priority patent/US11737128B2/en
Priority to US17/890,432 priority patent/US20220394724A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/141—Indication of costs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/41—Flow control; Congestion control by acting on aggregated flows or links
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8214—Data or packet based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • the present invention relates to a radio communication system, a base station, a mobile station, and a processing method.
  • LTE Long Term Evolution
  • WLAN Wireless Local Area Network
  • WLAN when WLAN is used, a technique for transferring data from RRC (Radio Resource Control: Radio Resource Control) to a MAC (Media Access Control: Media Access Control) layer is known (for example, see Patent Document 1 below). . Also, a technique for sharing LTE PDCP (Packet Data Convergence Protocol) between LTE and WLAN is known (for example, see Patent Document 2 below). Also, a technique for performing data transmission control based on QoS (Quality of Service) information in a WLAN or the like is known.
  • RRC Radio Resource Control: Radio Resource Control
  • MAC Media Access Control: Media Access Control
  • LTE PDCP Packet Data Convergence Protocol
  • QoS Quality of Service
  • an object of the present invention is to provide a radio communication system, a base station, a mobile station, and a processing method capable of performing data transmission using the first radio communication and the second radio communication at the same time. To do.
  • the base station can perform second wireless communication different from the first wireless communication by a control unit that controls the first wireless communication.
  • the mobile station can transmit data to and from the base station using the first wireless communication or the second wireless communication, and the mobile station can transmit data between the base station and the mobile station.
  • the processing unit in the transmitting station of the base station and the mobile station, the processing unit for performing the first wireless communication The data after processing of the convergence layer for performing the first wireless communication is tunneled and transmitted to the receiving station among the base station and the mobile station, and the receiving station The data transmitted from the transmitting station by the first wireless communication.
  • a wireless communication system, a base station, and a mobile station that can perform reception of data transmitted from the transmitting station by the second wireless communication based on the first wireless communication processing And a processing method is proposed.
  • FIG. 1 is a diagram of an example of a wireless communication system according to the first embodiment.
  • FIG. 2 is a diagram illustrating another example of the wireless communication system according to the first embodiment.
  • FIG. 3 is a diagram of an example of the wireless communication system according to the second embodiment.
  • FIG. 4 is a diagram of an example of a terminal according to the second embodiment.
  • FIG. 5 is a diagram of an example of a hardware configuration of the terminal according to the second embodiment.
  • FIG. 6 is a diagram of an example of the base station according to the second embodiment.
  • FIG. 7 is a diagram of an example of a hardware configuration of the base station according to the second embodiment.
  • FIG. 8 is a diagram of an example of a protocol stack in the wireless communication system according to the second embodiment.
  • FIG. 1 is a diagram of an example of a wireless communication system according to the first embodiment.
  • FIG. 2 is a diagram illustrating another example of the wireless communication system according to the first embodiment.
  • FIG. 3 is a diagram of an example
  • FIG. 9 is a diagram of an example of layer 2 in the wireless communication system according to the second embodiment.
  • 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.
  • FIG. 11 is a diagram illustrating an example of the value of the ToS field included in the IP header of the IP packet transmitted in the wireless communication system according to the second embodiment.
  • FIG. 12 is a diagram of an example of aggregation by LTE-A and WLAN in the wireless communication system according to the second embodiment.
  • 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.
  • FIG. 14 is a diagram of an example of AC classification in the wireless communication system according to the second embodiment.
  • FIG. 15 is a diagram of an example of aggregation in the wireless communication system according to the second embodiment.
  • FIG. 16 is a diagram illustrating an example of QoS class mapping to AC applicable to the wireless communication system according to the second embodiment.
  • FIG. 17 is a flowchart of an example of processing performed by the transmission side device in the wireless communication system according to the second embodiment.
  • 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.
  • FIG. 19 is a diagram illustrating an example of implementation of an outer IP layer using the 3GPP protocol in the second embodiment.
  • FIG. 20 is a diagram illustrating another example of implementation of the outer IP layer using the 3GPP protocol in the second embodiment.
  • FIG. 21 is a diagram illustrating still another example of implementation of the outer IP layer using the 3GPP protocol in the second embodiment.
  • FIG. 22 is a diagram illustrating an example of an outer IP layer implementation that uses the new tunneling protocol in the second embodiment.
  • FIG. 23 is a diagram illustrating another example of implementation of the outer IP layer using the new tunneling protocol in the second embodiment.
  • FIG. 24 is a diagram illustrating still another example of implementation of the outer IP layer using the new tunneling protocol in the second embodiment.
  • FIG. 25 is a diagram illustrating an example of a method of identifying an EPS bearer using a UL TFT in the wireless communication system according to the third embodiment.
  • FIG. 22 is a diagram illustrating an example of an outer IP layer implementation that uses the new tunneling protocol in the second embodiment.
  • FIG. 23 is a diagram illustrating another example of implementation of the outer IP layer using the new tunneling protocol in the second embodiment.
  • FIG. 24 is a diagram illustrating still another example of implementation of the outer IP layer using the new tunnel
  • FIG. 26 is a diagram illustrating another example of the method for identifying the EPS bearer using the UL TFT in the wireless communication system according to the third embodiment.
  • FIG. 27 is a diagram illustrating an example of a TFT acquisition method in the wireless communication system according to the third embodiment.
  • FIG. 28 is a diagram illustrating an example of a method of identifying an EPS bearer using DL TFTs in the wireless communication system according to the third embodiment.
  • FIG. 29 is a diagram illustrating another example of a method of identifying an EPS bearer using DL TFTs in the wireless communication system according to the third embodiment.
  • FIG. 30 is a diagram illustrating an 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. 31 is a diagram illustrating 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 illustrating an example of a method of identifying an EPS bearer using a VLAN in the wireless communication system according to the third embodiment.
  • FIG. 33 is a diagram illustrating another example of the method for identifying the EPS bearer using the VLAN in the wireless communication system according to the third embodiment.
  • FIG. 34 is a diagram illustrating an example of a method of identifying an EPS bearer using GRE tunneling in the wireless communication system according to the third embodiment.
  • FIG. 35 is a diagram illustrating another example of a method for identifying an EPS bearer using GRE tunneling in the wireless communication system according to the third embodiment.
  • FIG. 36 is a diagram illustrating an example of a method for identifying an EPS bearer using PDCPoIP in the wireless communication system according to the third embodiment.
  • FIG. 37 is a diagram illustrating another example of a method of identifying an EPS bearer using PDCPoIP in the wireless communication system according to the third embodiment.
  • FIG. 38 is a diagram (No. 1) for explaining processing on data transmitted by the WLAN in the wireless communication system according to the fourth embodiment.
  • FIG. 39 is a diagram (part 2) illustrating the process for data transmitted by the WLAN in the wireless communication system according to the fourth embodiment.
  • FIG. 40 is a sequence diagram illustrating an example of processing in the wireless communication system according to the fourth embodiment.
  • FIG. 41 is a sequence diagram illustrating a method for notifying a MAC address using another RRC message in the processing in the wireless communication system according to the fourth embodiment.
  • FIG. 42 is a sequence diagram illustrating a method of notifying a MAC address using still another RRC message in the processing in the wireless communication system according to the fourth embodiment.
  • FIG. 43 is a sequence diagram illustrating another example of processing in the wireless communication system according to the fourth embodiment.
  • FIG. 44 is a diagram illustrating an example of a packet format in ARP applicable to the fourth embodiment.
  • FIG. 1 is a diagram of an example of a wireless communication system according to the first embodiment.
  • the wireless communication system 100 according to the first embodiment includes a base station 110 and a mobile station 120.
  • data transmission using the first wireless communication 101 and the second wireless communication 102 at the same time is possible between the base station 110 and the mobile station 120.
  • the first wireless communication 101 and the second wireless communication 102 are different wireless communication (wireless communication system).
  • the first wireless communication 101 is, for example, cellular communication such as LTE or LTE-A.
  • the second wireless communication 102 is, for example, a WLAN.
  • the first wireless communication 101 and the second wireless communication 102 are not limited to these, and various types of communication can be used.
  • the base station 110 is a base station capable of performing the first wireless communication 101 and the second wireless communication 102 with the mobile station 120, for example.
  • the base station 110 and the mobile station 120 use the first wireless for transmitting the data of the first wireless communication 101.
  • a communication path for communication 101 is set between base station 110 and mobile station 120.
  • the base station 110 and the mobile station 120 set the communication path of the second wireless communication 102 for transmitting the 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 transmit data using the set communication paths of the first wireless communication 101 and the second wireless communication 102 simultaneously.
  • the base station 110 includes a control unit 111 and a processing unit 112.
  • the control unit 111 controls the first wireless communication 101.
  • the control unit 111 controls the second wireless communication 102.
  • 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.
  • the control unit 111 is not limited to RRC, and can be various processing units that control the first wireless communication 101.
  • the processing unit 112 performs processing for performing the first wireless communication 101.
  • the processing unit 112 is a processing unit that processes data transmitted by the first wireless communication 101.
  • the processing unit 112 is a processing unit of a data link layer such as PDCP, RLC (Radio Link Control), and MAC.
  • PDCP Data Link Control
  • RLC Radio Link Control
  • MAC Media Access Control
  • the processing unit 112 is not limited to these, and can be various processing units for performing the first wireless communication 101.
  • 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 processing for dividing data to be transmitted between the base station 110 and the mobile station 120 into the first wireless communication 101 and the second wireless communication 102.
  • the convergence layer is not limited to the PDCP layer and can be various layers.
  • the convergence layer may be referred to as a convergence point, a termination point, a branch point, a split function, or a routing function, and if it is intended to be a schedule point for data of the first wireless communication 101 and the second wireless communication 102 It is not limited to such a name.
  • the convergence layer is used as such a representative name.
  • the processing unit 112 uses the sequence number (SN: Sequence Number) for the data after the convergence layer processing by the convergence layer processing.
  • a protocol data unit (PDU: Protocol Data Unit) to which a header including etc. is attached is transmitted to the mobile station 120 by tunneling. Thereby, 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.
  • the mobile station 120 performs first reception processing on the data transmitted from the base station 110 by the first wireless communication 101 and the data transmitted from the base station 110 by the second wireless communication 102. Based on the processing of the wireless communication 101. For example, the mobile station 120 can perform order control based on the sequence number. Thereby, it is possible to perform data transmission using the first wireless communication 101 and the second wireless communication 102 at the same time. For this reason, for example, the data transmission speed can be improved.
  • the mobile station 120 includes a processing unit 121.
  • the processing unit 121 is a processing unit for performing the first wireless communication 101 similarly to the processing unit 112 of the base station 110.
  • the processing unit 121 is a data link layer processing unit such as PDCP, RLC, or MAC.
  • the processing unit 121 is not limited to these, and can be various processing units for performing the first wireless communication 101.
  • 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.
  • this convergence layer includes processing for dividing data transmitted between the base station 110 and the mobile station 120 into the first wireless communication 101 and the second wireless communication 102.
  • the processing unit 121 adds, to the data transmitted from the mobile station 120 to the base station 110 using the second wireless communication 102, a header including a sequence number and the like after the processing of the convergence layer.
  • the transmitted PDU is transmitted to the base station 110 by tunneling. Thereby, the data to the base station 110 can be transmitted by the second wireless communication 102 while including the sequence number.
  • the base station 110 performs the sequence control of the data transmitted from the mobile station 120 by the first wireless communication 101 and the data transmitted from the mobile station 120 by the second wireless communication 102. Can be done based on the number. For this reason, it is possible to perform data transmission using the first wireless communication 101 and the second wireless communication 102 simultaneously.
  • the transmitting station of the base station 110 and the mobile station 120 attaches a header including the sequence number and the like attached by the process of the convergence layer to the data transmitted using the second wireless communication 102.
  • the transmitted PDU is transmitted by tunneling.
  • the order control between the data transmitted from the mobile station 120 by the first wireless communication 101 and the data transmitted from the mobile station 120 by the second wireless communication 102 is performed. This can be done based on the sequence number. For this reason, it is possible to perform data transmission using the first wireless communication 101 and the second wireless communication 102 simultaneously.
  • FIG. 2 is a diagram illustrating another example of the wireless communication system according to the first embodiment.
  • the base station 110A is a base station capable of performing the first wireless communication 101 with the mobile station 120.
  • the base station 110B is a base station connected to the base station 110A, and is a base station capable of performing the second wireless communication 102 with the mobile station 120.
  • the base station 110A performs data transmission using the second wireless communication 102 with the mobile station 120 via the base station 110B.
  • the control unit 111 and the processing unit 112 illustrated in FIG. 1 are provided in the base station 110A, for example.
  • the control unit 111 controls the second wireless communication 102 with the mobile station 120 via the base station 110B.
  • the processing unit 112 of the base station 110A adds, to the data transmitted to the mobile station 120 using the second wireless communication 102, a header including a sequence number and the like after the convergence layer processing is added to the data after the convergence layer processing.
  • the transmitted PDU is transferred to the base station 110B by tunneling. Accordingly, the data can be transmitted to the mobile station 120 via the base stations 110A and 110B.
  • the base station 110 ⁇ / b> B transmits the data transferred from the base station 110 ⁇ / b> A to the mobile station 120 through the second wireless communication 102.
  • the processing unit 121 of the mobile station 120 adds, to the data transmitted to the base station 110 using the second wireless communication 102, a header including a sequence number and the like after the processing of the convergence layer.
  • the transmitted PDU is transmitted to the base station 110B by tunneling.
  • the base station 110B transfers the data transmitted from the mobile station 120 through the second wireless communication 102 to the base station 110A.
  • data to the base station 110 ⁇ / b> A can be transmitted to the base station 110 ⁇ / b> A using the second wireless communication 102.
  • the wireless communication system 100 As described above, according to the wireless communication system 100 according to the first embodiment, data transmission using the first wireless communication 101 and the second wireless communication 102 simultaneously between the base station 110 and the mobile station 120 is performed. It becomes possible to do. For this reason, for example, the data transmission speed can be improved.
  • Embodiments 2 to 4 can be regarded as examples of the embodiment 1 described above, they can be implemented in combination with the embodiment 1.
  • FIG. 3 is a diagram of an example of the wireless communication system according to the second embodiment.
  • 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 radio communication system 300 is a mobile communication system such as LTE-A defined in 3GPP, for example, but the communication standard of the radio communication system 300 is not limited to these.
  • the packet core network 330 is an EPC (Evolved Packet Core) defined in 3GPP, but is not particularly limited thereto.
  • EPC Evolved Packet Core
  • SAE System Architecture Evolution
  • the packet core network 330 includes an SGW 331, a PGW 332, and an MME 333.
  • 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, E-UTRAN (Evolved Universal Terrestrial Access Network) defined in 3GPP, but is not limited thereto.
  • E-UTRAN Evolved Universal Terrestrial Access Network
  • the UE 311 is a terminal that is located in the cell of the eNB 321 and performs wireless communication with the eNB 321. As an example, the UE 311 communicates with other communication apparatuses through a route that passes through the eNB 321, the SGW 331, and the PGW 332. Other communication apparatuses that communicate with the UE 311 are, for example, a communication terminal or a server that is different from the UE 311.
  • the communication between the UE 311 and another communication device is, for example, data communication or voice communication, but is not particularly limited thereto.
  • the voice communication is, for example, VoLTE (Voice over LTE), but is not particularly limited thereto.
  • the eNB 321 is a base station that forms the cell 321a and performs wireless communication with the UE 311 located in the cell 321a.
  • the eNB 321 relays communication between the UE 311 and the SGW 331.
  • the eNB 322 is a base station that forms the cell 322a and performs radio communication with the UE located in the cell 322a.
  • the eNB 322 relays communication between the UE located in the cell 322a and the SGW 331.
  • the eNB 321 and the eNB 322 may be connected by, for example, a physical or logical interface between base stations.
  • the inter-base station interface is an X2 interface as an example, but the inter-base station interface is not particularly limited to this.
  • 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 an S1-U interface as an example, but is not particularly limited thereto.
  • 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.
  • U-plane User plane
  • the SGW 331 performs U-plane processing in the communication of the UE 311.
  • U-plane is a function group that transmits user data (packet data).
  • the SGW 331 may accommodate the eNB 322 and perform U-plane processing in communication via the eNB 322.
  • the PGW 332 is a packet data network gateway for connecting to an external network.
  • An example of the external network is the Internet, but is not limited thereto.
  • the PGW 332 relays user data between the SGW 331 and the external network. Further, for example, the PGW 332 performs an IP address allocation 301 for assigning an IP address to the UE 311 so that the UE 311 transmits and receives an IP flow.
  • 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 an S5 interface as an example, but is not particularly limited thereto.
  • the MME 333 (Mobility Management Entity: mobility management entity) accommodates the eNB 321 and performs C-plane (Control plane) processing in communication via the eNB 321.
  • C-plane Control plane
  • the MME 333 performs C-plane processing in communication of the UE 311 via the eNB 321.
  • C-plane is a function group for controlling calls and networks between devices, for example.
  • the C-plane is used for packet call connection, setting of a route for transmitting user data, handover control, and the like.
  • the MME 333 may accommodate the eNB 322 and perform C-plane processing in communication via the eNB 322.
  • 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 an S1-MME interface as an example, 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 an S11 interface as an example, but is not particularly limited thereto.
  • IP flows transmitted or received by the UE 311 are classified (sorted) into EPS bearers 341 to 34n, and transmitted via the PGW 332 and the SGW 331.
  • the EPS bearers 341 to 34n are IP flows in EPS (Evolved Packet System).
  • the EPS bearers 341 to 34n are radio bearers 351 to 35n (Radio Bearer) in the radio access network formed by the UE 311 and the eNBs 321 and 322.
  • the MME 333 performs overall communication control such as setting of the EPS bearers 341 to 34n, security setting, mobility management, and the like.
  • the IP flows classified into the EPS bearers 341 to 34n are transmitted in the LTE network by, for example, a GTP (GPRS Tunneling Protocol) tunnel set between the nodes.
  • the EPS bearers 341 to 34n are uniquely mapped to the radio bearers 351 to 35n, respectively, and are wirelessly transmitted in consideration of QoS.
  • the first wireless communication 101 shown in FIG. 1 can be wireless communication based on LTE-A, for example.
  • the second wireless communication 102 shown in FIG. 1 can be wireless communication by WLAN, for example.
  • the aggregation by LTE-A and WLAN will be described later.
  • 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 called integration in the sense that multiple systems are integrated and used. Hereinafter, aggregation is used as a representative name.
  • the mobile station 120 shown in FIGS. 1 and 2 can be realized by the UE 311, for example.
  • FIG. 4 is a diagram of an example of a terminal according to the second embodiment.
  • the UE 311 illustrated in FIG. 3 can be realized by the terminal 400 illustrated 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 components is connected so that signals and data can be input and output in one direction or in both directions.
  • the wireless communication unit 410 can perform, for example, wireless communication using LTE-A (first wireless communication 101) and wireless communication using WLAN (second wireless communication 102).
  • the wireless transmission unit 411 transmits user data and control signals by wireless communication via an antenna.
  • the wireless signal transmitted by the wireless transmission unit 411 can include arbitrary user data, control information, and the like (encoded or modulated).
  • the wireless reception unit 412 receives user data and control signals by wireless communication via an antenna.
  • the radio signal received by the radio reception unit 412 can include arbitrary user data, a control signal, and the like (encoded or modulated).
  • the antenna may be common for transmission and reception.
  • the control unit 420 outputs user data and control signals to be transmitted to other wireless stations to the wireless transmission unit 411. In addition, the control unit 420 acquires user data and control signals received by the wireless reception unit 412. The control unit 420 inputs and outputs user data, control information, programs, and the like with a storage unit 430 described later. In addition, the control unit 420 inputs / outputs user data and control signals transmitted / received to / from other communication devices and the like with the wireless communication unit 410. In addition to these, the control unit 420 performs various controls in the terminal 400.
  • the storage unit 430 stores various information such as user data, control information, and programs.
  • the processing unit 121 of the mobile station 120 shown in FIG. 1 can be realized by the control unit 420, for example.
  • FIG. 5 is a diagram of an example of a hardware configuration of the terminal according to the second embodiment.
  • Terminal 400 shown in FIG. 4 can be realized by, for example, terminal 500 shown in FIG.
  • the terminal 500 includes, for example, an antenna 511, an RF circuit 512, a processor 513, and a memory 514. These components are connected so that various signals and data can be input / output via a bus, for example.
  • the antenna 511 includes a transmission antenna that transmits a radio signal and a reception antenna that receives 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: high 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.
  • the processor 513 is, for example, a CPU (Central Processing Unit) or a DSP (Digital Signal Processor).
  • the processor 513 may be realized by a digital electronic circuit such as an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or an LSI (Large Scale Integration).
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • LSI Large Scale Integration
  • the memory 514 can be realized by a random access memory (RAM) such as SDRAM (Synchronous Dynamic Random Access Memory), a ROM (Read Only Memory), or a flash memory, for example.
  • RAM random access memory
  • SDRAM Serial Dynamic Random Access Memory
  • ROM Read Only Memory
  • flash memory for example.
  • the memory 514 stores, for example, user data, control information, programs, and the like.
  • the wireless communication unit 410 shown in FIG. 4 can be realized by the antenna 511 and the RF circuit 512, for example.
  • the control unit 420 illustrated in FIG. 4 can be realized by the processor 513, for example.
  • the storage unit 430 illustrated in FIG. 4 can be realized by the memory 514, for example.
  • FIG. 6 is a diagram of an example of a base station according to the second embodiment.
  • Each of the eNBs 321 and 322 illustrated in FIG. 3 can be realized by the base station 600 illustrated in FIG. 6, for example.
  • 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 components is connected so that signals and data can be input and output in one direction or in both directions.
  • the wireless communication unit 610 can perform, for example, wireless communication using LTE-A (first wireless communication 101) and wireless communication using WLAN (second wireless communication 102).
  • the wireless transmission unit 611 transmits user data and control signals by wireless communication via an antenna.
  • the wireless signal transmitted by the wireless transmission unit 611 can include arbitrary user data, control information, and the like (encoded or modulated).
  • the wireless reception unit 612 receives user data and control signals by wireless communication via an antenna.
  • the radio signal received by the radio reception unit 612 can include arbitrary user data, a control signal, and the like (encoded or modulated).
  • the antenna may be common for transmission and reception.
  • the control unit 620 outputs user data and control signals to be transmitted to other wireless stations to the wireless transmission unit 611. In addition, the control unit 620 acquires user data and control signals received by the wireless reception unit 612. The control unit 620 inputs and outputs user data, control information, programs, and the like with a storage unit 630 described later. In addition, the control unit 620 inputs and outputs user data and control signals that are transmitted to and received from other communication devices and the like with the communication unit 640 described later. In addition to these, the control unit 620 performs various controls in the base station 600.
  • the storage unit 630 stores various information such as user data, control information, and programs.
  • the communication unit 640 transmits / receives user data and control signals to / from other communication devices, for example, by wired signals.
  • control unit 111 and the processing unit 112 of the base station 110 illustrated in FIG. 1 can be realized by the control unit 620, for example.
  • FIG. 7 is a diagram of an example of a 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 components are connected so that various signals and data can be input / output via a bus, for example.
  • the antenna 711 includes a transmission antenna that transmits a radio signal and a reception antenna that receives a radio signal.
  • the antenna 711 may be a shared antenna that transmits and receives radio signals.
  • the RF circuit 712 performs RF processing on 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.
  • the processor 713 is, for example, a CPU or a DSP.
  • the processor 713 may be realized by a digital electronic circuit such as an ASIC, FPGA, LSI, or the like.
  • the memory 714 can be realized by a RAM such as SDRAM, a ROM, or a flash memory, for example.
  • the memory 714 stores user data, control information, programs, and the like, for example.
  • the network IF 715 is a communication interface that performs communication with the network by, for example, a wired connection.
  • the network IF 715 may include an Xn interface for performing wired communication between base stations, for example.
  • the control unit 620 illustrated in FIG. 6 can be realized by the processor 713, for example.
  • the storage unit 630 illustrated in FIG. 6 can be realized by the memory 714, for example.
  • the communication unit 640 illustrated in FIG. 6 can be realized by the network IF 715, for example.
  • FIG. 8 is a diagram illustrating an example of a protocol stack in the wireless communication system according to the second embodiment.
  • a 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 an LTE-A protocol stack defined in 3GPP.
  • Layer groups 801 to 805 are layer groups indicating processes in the UE 311, eNB 321, SGW 331, PGW 332, and external network server, respectively.
  • filtering of the IP flow is performed in order to handle each IP flow according to the QoS class.
  • the PGW 332 performs packet filtering on the IP flow and classifies the IP flow into EPS bearers 341 to 34n.
  • the PGW 332 For the uplink in which the UE 311 transmits the IP flow, the PGW 332 notifies the UE 311 of a packet filtering rule. Then, 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 34n.
  • the PGW 332 performs IP flow filtering by the filter layer 811 (Filter) included in the IP layer (IP) of the layer group 804 of the PGW 332.
  • the UE 311 performs IP flow filtering using a filter layer 812 (Filter) included in the IP layer (IP) of the layer group 801 of the UE 311.
  • the PGW 332 in the case of downlink or the UE 311 (in the case of uplink) has a QoS in the ToS (Type of Service) field of the header of the IP packet. Set the value.
  • Packet filtering by the PGW 332 or the UE 311 is performed using, for example, 5-tuple (transmission / reception source IP address, transmission / reception source port number, protocol type).
  • the filtering rule for packet filtering is called, for example, TFT (Traffic Flow Template).
  • TFT Traffic Flow Template
  • the IP flow can be classified into 11 types of EPS bearers at maximum.
  • One of the EPS bearers 341 to 34n 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 34n is called an individual bearer (Dedicated Bearer).
  • the individual bearer can be generated and released as appropriate according to the situation of user data to be transmitted.
  • FIG. 9 is a diagram of an example of layer 2 in the wireless communication system according to the second embodiment.
  • the process illustrated in FIG. 9 can be applied to the wireless communication system 300 according to the second embodiment as the layer 2 process.
  • the process shown in FIG. 9 is an LTE-A layer 2 process defined in 3GPP.
  • LTE-A layer 2 includes PDCP 910, RLC 920, and MAC 930.
  • PDCP 910 includes processing related to ROHC (Robust Header Compression) for performing header compression of incoming IP datagrams and security.
  • the security-related processing includes, for example, confidentiality and integrity protection.
  • user data is forwarded to a lower layer (for example, layer 1) after these processes of PDCP 910 are performed.
  • the UE 311 can simultaneously communicate with two base stations (for example, eNBs 321 and 322) at the maximum.
  • the MCG bearer 901 Master Cell Group Bearer
  • the MCG bearer 901 is a radio bearer of the main base station.
  • split bearer 902 Split Bearer
  • SCG bearer 903 Secondary Cell Group Bearer
  • the RLC 920 includes a primary process before wireless transmission of user data.
  • the RLC 920 includes user data division (Segm .: Segmentation) for adjusting the user data to a size corresponding to the radio quality.
  • the RLC 920 may include an ARQ (Automatic Repeat reQuest) or the like for retransmission of user data that could not be corrected in the lower layer.
  • ARQ Automatic Repeat reQuest
  • the EPS bearer is mapped to a corresponding logical channel (Logical Channel) and wirelessly transmitted.
  • the MAC 930 includes wireless transmission control.
  • the MAC 930 includes a process of performing packet scheduling and performing HARQ (Hybrid Automatic Repeat reQuest) of transmission data.
  • HARQ is performed for each carrier to be aggregated in carrier aggregation.
  • the transmission side adds the LCID (Logical Channel Identifier) to the MAC SDU (MAC Service Data Unit), which is user data, and transmits.
  • the receiving side converts the radio bearer into an EPS bearer using the LCID added by the transmitting side.
  • 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.
  • an IP packet having the 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.
  • the IP header 1000 includes a ToS field 1003 for performing QoS.
  • the above-described QoS control is performed based on the value of the ToS field 1003, for example.
  • the IP header 1000 includes a protocol field 1004 in which the protocol number of the transport layer corresponding to the upper layer is stored.
  • FIG. 11 is a diagram illustrating an example of the value of the ToS field included in the IP header of the IP packet transmitted in the wireless communication system according to the second embodiment.
  • IP precedence of the ToS field 1003 For example, “111” having the highest priority in the IP precedence of the ToS field 1003 indicates that the IP packet corresponds to network control, and is reserved for control of routing and the like. Further, “110” having the second highest priority in the IP precedence of the ToS field 1003 indicates that the IP packet corresponds to the Internet control, and is reserved for control of routing and the like.
  • the QoS priority information is not limited to this, for example, using a DSCP (Differentiated Services Code Point) field. Also good. DSCP is a field corresponding to the first 6 bits in the ToS field 1003.
  • DSCP is a field corresponding to the first 6 bits in the ToS field 1003.
  • FIG. 12 is a diagram illustrating an example of aggregation by LTE-A and WLAN in the wireless communication system according to the second embodiment.
  • the layer 2 processing in the aggregation by LTE-A and WLAN is based on the dual connectivity processing described above in consideration of backward compatibility of LTE-A, for example.
  • the IP flow 1201 is an IP flow between the UE 311 and the eNB 321 using HTTP (Hypertext Transfer Protocol).
  • the IP flow 1202 is an IP flow based on FTP (File Transfer Protocol) between the UE 311 and the eNB 321.
  • the non-aggregation process 1211 indicates a process when the IP flows 1201 and 1202 are transmitted by LTE-A without using the WLAN.
  • This non-aggregation process 1211 corresponds to data transmission using wireless communication by the first wireless communication 101 shown in FIG.
  • the processes are 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, for example, PDCP 910, RLC 920, and MAC 930 shown in FIG.
  • LTE-PHY is a physical layer in LTE-A.
  • Aggregation processing 1212 indicates processing when IP flows 1201 and 1202 are transmitted using LTE-A and WLAN simultaneously. This aggregation processing 1212 corresponds to data transmission using wireless communication by the first wireless communication 101 and the second wireless communication 102 shown in FIG.
  • the IP flow 1201 is divided into a packet transmitted by LTE-A and a packet transmitted by WLAN by PDCP.
  • a packet transmitted by LTE-A in the IP flow 1201 is processed in the order of RLC, LTE-MAC, and LTE-PHY.
  • a packet transmitted by the WLAN in the IP flow 1201 is tunneled by being transferred to the WLAN side with an outer IP header attached by the outer IP layer after PDCP processing.
  • the outer IP header is a copy of an IP header attached by an upper IP layer of PDCP, for example, and is an IP header that is not concealed by PDCP.
  • the packet transferred with the outer IP header of the IP flow 1201 to the WLAN side is. 11x MAC,. Processing is performed in the order of 11x PHY. . 11x MAC,. 11x PHY is a MAC layer and a PHY layer in WLAN (802.11x), respectively.
  • the outer IP layer can also be installed on the secondary base station (for example, secondary eNB 323 described later) side. That is, in order to attach an outer IP header, relevant information (parameters, etc.) may be notified from the master base station (e.g., eNB 321) to the secondary base station. Specific examples of parameters will be described.
  • the master base station e.g., eNB 321
  • the IP header version can be uniquely determined, so notification is not essential. Since the header length is the PDU length of the first wireless communication system (for example, LTE-A), notification is not essential.
  • the TOS is preferably notified because it is necessary to take over the QoS information of the first wireless communication system.
  • the QoS information used in the first wireless communication system for example, the QCI value is notified.
  • the second wireless communication system reconversion from the QCI value to the TOS value is performed, and the obtained value is set in the TOS field of the outer IP header. Since the ID, IP flag, and offset field related to fragmentation can be determined only by the second wireless communication system, notification is not essential. Since the protocol number can be uniquely determined by the second wireless communication system as will be described later, notification is not essential. Since the header checksum is a value calculated from the contents of the header, notification is not essential.
  • the TOS value related to QoS control from the first wireless communication system to the second wireless communication system.
  • the maximum communication rate (AMBR: Aggregated Maximum Bit Rate) supported by the mobile station the maximum communication rate (AMBR: Aggregated Maximum Bit Rate) supported by the mobile station, the TTW (Time to Wait) that controls the delay time, and the guaranteed bandwidth (GBR: (Guaranteed Bit Rate) may also be notified.
  • AMBR Aggregated Maximum Bit Rate
  • TTW Time to Wait
  • GRR Guarantee Bit Rate
  • the IP flow 1202 is divided into a packet transmitted by LTE-A and a packet transmitted by WLAN, by PDCP, similarly to the IP flow 1201.
  • a packet transmitted by LTE-A in the IP flow 1202 is processed in the order of RLC, LTE-MAC, and LTE-PHY.
  • a packet transmitted by the WLAN in the IP flow 1202 is tunneled by being transferred to the WLAN side with an outer IP header attached by the outer IP layer after PDCP processing.
  • the outer IP header is a copy of an IP header attached by an upper IP layer of PDCP, for example, and is an IP header that is not concealed by PDCP.
  • the packet transferred with the outer IP header of the IP flow 1202 to the WLAN side is. 11x MAC,. Processing is performed in the order of 11x PHY.
  • IP flows are classified into bearers and managed as bearers.
  • 802.11x of IEEE the Institute of Electrical and Electronics Engineers
  • the IP flow is managed as an IP flow instead of a bearer.
  • mapping management 1220 it is required to manage the mapping of which bearer belongs to which L2 layer and to perform the non-aggregation process 1211 and the aggregation process 1212 at high speed.
  • the mapping management 1220 is performed by RRC that performs radio control between the UE 311 and the eNB 321, for example.
  • the RRC supports a non-aggregation process 1211 that uses LTE-A radio communication and an aggregation process 1212 that uses LTE-A radio communication and WLAN radio communication at the radio bearer level.
  • the wireless communication system 300 adds an outer IP header to a packet transferred to the WLAN. This makes it possible to transmit LTE-A traffic in the WLAN. Further, in the WLAN, the ToS field included in the transferred IP flows 1201 and 1202 can be referred to.
  • the QoS is managed by aggregating IP flows into four types of AC (Access Category) with reference to the ToS field of the IP header.
  • AC Access Category
  • the eNB 321 on the transmission side when performing aggregation using LTE-A and WLAN at the same time, includes the quality of service information before PDCP processing in the data after processing by PDCP for transmission using WLAN.
  • the service quality information is QoS information indicating the priority of transmission such as a data service class.
  • the service quality information can be the ToS field described above, but the service quality information is not limited to this, and can be various information indicating the priority of data transmission.
  • a field for defining QoS is defined in a VLAN tag.
  • the QoS information is information set with a 5-tuple.
  • the 5-tuple is a source IP address and port number, a destination IP address and port number, and a protocol type.
  • the transmission control based on the service quality information is, for example, QoS control for controlling the priority of transmission according to the service quality information.
  • the transmission control based on the service quality information is not limited to this and can be various types of control.
  • the user data transferred to the WLAN is subjected to a concealment process in the WLAN. For this reason, even if user data with an outer header that is not concealed is transferred to the WLAN, it is possible to avoid the outer header being transmitted between the eNB 321 and the UE 311 without being concealed.
  • AES Advanced Encryption Standard
  • TKIP Temporal Key Integrity Protocol
  • WEP Wired Equivalent Privacy
  • the processing unit that establishes the convergence layer (branch point) when transferring to the WLAN is not limited to the PDCP processing unit, but may be an RLC or LTE-MAC processing unit.
  • the data link layer (layer 2) such as PDCP, RLC, LTE-MAC, etc. can grasp the traffic congestion status in the radio section between the UE 311 and the eNB 321. For this reason, by determining the convergence layer in the data link layer and performing the transfer to the WLAN, it is determined whether or not the aggregation process 1212 needs to be executed according to the communication congestion state in the wireless section between the UE 311 and the eNB 321. can do.
  • the outer IP layer that adds the outer IP header to the packet in the aggregation process 1212 is provided as a part of the PDCP layer, for example. However, as will be described later, the outer IP layer may be provided as a lower layer of PDCP.
  • 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.
  • the eNB 321 has a WLAN communication function and transmits an IP packet 1301 from the eNB 321 to the UE 311 will be described.
  • the eNB 321 Based on the ToS field in the IP header of the IP packet 1301, the eNB 321 classifies the IP packet 1301 into one of ACs 1311 to 1314 of voice, video, best effort, or background.
  • the eNB 321 can perform AC classification based on the ToS field with reference to the ToS field included in the outer IP header of the IP packet 1301 even in the WLAN processing.
  • the eNB 321 has the WLAN communication function
  • the IP packet 1301 is transmitted from the eNB 321 to the UE 311 (downlink)
  • FIG. 14 is a diagram of an example of AC classification in the wireless communication system according to the second embodiment.
  • the same parts as those shown in FIG. 14 are identical parts as those shown in FIG. 14, the same parts as those shown in FIG. 14, the same parts as those shown in FIG. 14, the same parts as those shown in FIG. 14, the same parts as those shown in FIG. 14, the same parts as those shown in FIG. 14, the same parts as those shown in FIG. 14, the same parts as those shown in FIG.
  • FIG. 14 describes a case where the eNB 321 has a WLAN communication function.
  • the IP packets 1401 and 1402 are packets that the eNB 321 transmits by WLAN in the aggregation that uses LTE-A and WLAN at the same time.
  • IP packets 1401 and 1402 are HTTP and FTP IP packets, respectively.
  • the eNB 321 performs the ToS value analysis classification 1410 for classifying the IP packets 1401 and 1402 into one of the ACs 1311 to 1314 based on the value of the ToS field included in the IP header.
  • the eNB 321 classifies the IP packet 1401 as AC1313 (best effort), and classifies the IP packet 1402 as AC1314 (background). Then, the eNB 321 transmits the IP packets 1401 and 1402 subjected to the ToS value analysis classification 1410 to the UE 311 via the WLAN.
  • the UE 311 terminates the IP packets 1401 and 1402 by PDCP by performing the ToS value analysis classification 1430 (declassification) corresponding to the ToS value analysis classification 1410 (classification) on the eNB 321 side.
  • IP packets 1401 and 1402 are transmitted from the eNB 321 to the UE 311 (downlink)
  • FIG. 15 is a diagram of an example of aggregation in the wireless communication system according to the second embodiment.
  • aggregation is performed using LTE-A and WLAN at the same time in a WLAN independent configuration using secondary eNB 323 having eNB and WLAN communication function (eNB + WLAN) as eNB 321 serving as a master eNB.
  • secondary eNB 323 having eNB and WLAN communication function (eNB + WLAN) as eNB 321 serving as a master eNB.
  • the secondary eNB 323 is a base station that can communicate with the eNB 321 via an inter-base station interface such as an X2 interface and can communicate with the UE 311 via WLAN.
  • EPS bearers 1500 to 150n are respectively connected to the LTE-A.
  • EPS bearers 1500 to 150n are downlink bearers from eNB 321 to UE 311.
  • FIG. 15 illustrates a case where n EPS bearers 1500 to 150n are set, the number of EPS bearers to be set is arbitrary.
  • the EPS bearers 1500 to 150n are n + 1 EPS bearers each having an EBI (EPS Bearer ID) of 0 to n.
  • the sources (src IP) of the EPS bearers 1500 to 150n are both core networks (CN).
  • the destinations (dst IP) of the EPS bearers 1500 to 150n are both UE 311 (UE).
  • the eNB 321 transfers the transfer packet to the WLAN in each of the EPS bearers 1500 to 150n to the secondary eNB 323 via the PDCP layers 1510 to 151n, respectively. That is, the eNB 321 controls the transfer of the EPS bearers 1500 to 150n to the WLAN by LTE-A layer 2 (PDCP in the example illustrated in FIG. 15).
  • LTE-A layer 2 PDCP in the example illustrated in FIG. 15
  • the eNB 321 adds an outer IP header to the packet transferred to the WLAN in each of the EPS bearers 1500 to 150n.
  • the EPS bearers 1500 to 150n are transferred to the secondary eNB 323 as IP packets. That is, the EPS bearers 1500 to 150n are transferred to the WLAN with the outer IP header including the ToS field (QoS information) described above and not being concealed.
  • the value of the protocol field (for example, the protocol field 1004 shown in FIG. 10) in the outer IP header can be set to “99” (any private encryption scheme), for example.
  • the value of the protocol field in the outer IP header is not limited to “99”, but may be “61” (any host internal protocol), “63” (any local network), “114” (any 0-hop protocol), etc. May be.
  • the EPS bearers 1500 to 150n can be transferred from the eNB 321 to the secondary eNB 323, for example, in the same manner as the LTE-A handover.
  • the transfer of the EPS bearers 1500 to 150n from the eNB 321 to the secondary eNB 323 can be performed using the GTP tunnels 1520 to 152n between the eNB 321 and the secondary eNB 323.
  • the GTP tunnels 1520 to 152n are GTP tunnels set for each EPS bearer between the eNB 321 and the secondary eNB 323.
  • this transfer is not limited to the GTP tunnel but can be performed by various methods such as Ethernet (registered trademark).
  • the eNB 321 does not add an outer IP header to a packet transmitted by the LTE-A in each of the EPS bearers 1500 to 150n, processes RLC, MAC, and PHY in this order, and wirelessly transmits the packet to the UE 311 through the LTE-A. Send.
  • the UE 311 receives the packet transmitted from the eNB 321 by LTE-A by processing the packet using PHY, MAC, RLC, and PDCP (PDCP layers 1570 to 157n).
  • Secondary eNB 323 receives EPS bearers 1500 to 150n transferred from eNB 321 via GTP tunnels 1520 to 152n, respectively. Then, the secondary eNB 323 performs AC classification 1540 based on the ToS field included in the outer IP header of each IP packet for each IP packet corresponding to the received EPS bearers 1500 to 150n.
  • AC classification 1540 is processing by the function of WLAN (802.11e) in the secondary eNB 323. According to AC classification 1540, for example, as shown in FIG. 13, each IP packet is classified into one of voice (VO), video (VI), best effort (BE), and background (BK) AC. .
  • Secondary eNB 323 transmits each IP packet classified by AC classification 1540 to UE 311 via WLAN 1550.
  • the SSID Service Set Identifier: service set identifier
  • the WLAN 1550 can be set to “offload”, for example.
  • the UE 311 performs AC declassification 1560 based on the ToS field included in the outer IP header of the IP packet for each IP packet received via the WLAN 1550.
  • the AC declassification 1560 is a process based on a WLAN (802.11e) function in the UE 311.
  • UE 311 reclassifies each IP packet received by AC declassification 1560 into EPS bearers 1500 to 150n based on the classified AC. Then, the UE 311 processes and receives the reclassified EPS bearers 1500 to 150n by the PDCP layers 1570 to 157n, respectively.
  • the layer group 1551 indicates each protocol of each IP packet received by the UE 311 through the PDCP layers 1570 to 157n. As shown in the layer group 1551, data transmitted by the WLAN is data processed by the application layer (APP), TCP / UDP layer, IP layer (inner layer), PDCP layer, and outer IP layer. Data (shaded portion) by the application layer, TCP / UDP layer, and IP layer is encrypted and transmitted by processing of the PDCP layer.
  • APP application layer
  • TCP / UDP layer IP layer (inner layer)
  • IP layer outer IP layer
  • Data (shaded portion) by the application layer, TCP / UDP layer, and IP layer is encrypted and transmitted by processing of the PDCP layer.
  • the UE 311 removes the outer IP header attached to each received IP packet.
  • a layer group 1552 indicates each protocol of the 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 the PDCP packet as shown in the layer group 1552.
  • the layer group 1553 indicates each protocol of the PDCP packet that the UE 311 receives from the eNB 321 via LTE-A. As shown in the layer group 1553, the eNB 321 transmits the PDCP packet to the UE 311 as it is without adding an outer IP header to the PDCP packet.
  • the UE 311 performs order 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 a sequence number included in the header added to the data by processing by the PDCP layer.
  • 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 transmitted by the eNB 321 after being divided into the LTE-A and the WLAN. .
  • the wireless communication system 300 when EPS bearers 1500 to 150n are divided into LTE-A and WLAN for transmission, PDCP packets transmitted by WLAN can be tunneled by outer IP. As a result, the receiving side receives the data transmitted by the WLAN as a PDCP packet, and uses the PDCP sequence number to control the order between the packet received by LTE-A and the packet received by the WLAN. It can be carried out. Therefore, data transmission using LTE-A and WLAN simultaneously becomes possible.
  • the secondary eNB 323 can refer to the ToS field of the outer IP header of each IP packet. Therefore, AC classification 1540 based on the ToS field can be performed on data transmitted by the WLAN 1550, and QoS control according to the nature of the traffic can be performed.
  • AC classification can be performed by referring to the priority value in the VLAN tag defined by IEEE802.1q.
  • the VLAN tag is a VLAN identifier.
  • the eNB 321 becomes the master eNB and performs aggregation using the LTE-A and the WLAN simultaneously in a WLAN independent configuration using the secondary eNB 323 having the function of eNB and WLAN communication (eNB + WLAN).
  • the aggregation is not limited to this.
  • the eNB 321 may perform the aggregation in a configuration having a WLAN communication function (eNB + WLAN).
  • the eNB 321 also performs communication with the UE 311 by WLAN, and the secondary eNB 323 may not be used.
  • FIG. 16 is a diagram illustrating an example of mapping of QoS classes to AC applicable to the wireless communication system according to the second embodiment.
  • the WLAN transmission side (for example, the secondary eNB 323) classifies the EPS bearer to be transmitted as AC, for example, as in a table 1600 of FIG.
  • the QoS class of the EPS bearer is identified by QCI (QoS Class Identifier).
  • Each QCI is classified into four ACs: voice (VO), video (VI), best effort (BE), and background (BK).
  • the WLAN receiving side (for example, UE 311) performs conversion from AC to QoS class.
  • the eNB 321 sets an EPS bearer to be transferred to the WLAN in the UE 311 in advance.
  • the UE 311 can specify the EPS bearer based on the EPS bearer set from the eNB 321.
  • the UE 311 can perform AC classification based on the EPS bearer set from the eNB 321.
  • FIG. 17 is a flowchart of an example of processing performed by the transmission side device in the wireless communication system according to the second embodiment.
  • the case of the downlink which transmits user data from eNB321 to UE311 is demonstrated.
  • the eNB 321 determines whether or not to perform aggregation using LTE-A and WLAN at the same time for user data to the UE 311 (step S1701).
  • the determination method in step S1701 will be described later.
  • step S1701 If it is determined in step S1701 that aggregation is not to be performed (step S1701: No), the eNB 321 transmits user data to the UE 311 by LTE-A (step S1702), and ends a series of processing.
  • step S1702 user data subjected to PDCP concealment and header compression is transmitted.
  • the UE 311 can receive user data transmitted from the eNB 321 by performing processing such as decryption for concealment and header decompression for header compression in the PDCP layer.
  • step S1701 If it is determined in step S1701 that 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 the own station.
  • the eNB 321 transmits user data to the UE 311 simultaneously using LTE-A and WLAN (step S1704), and ends a series of processing.
  • the eNB 321 tunnels and transmits user data transmitted by the WLAN by adding an outer IP header by the outer IP layer set in step S1703.
  • step S1704 if the eNB 321 has a WLAN communication function, the eNB 321 transmits user data to the UE 311 by the local station's LTE-A communication and WLAN communication functions. On the other hand, when the eNB 321 does not have the WLAN communication function, the eNB 321 transfers the user data to the UE 311 to the secondary eNB 323 having the WLAN communication function connected to the own station for user data to be transmitted by the WLAN. To do.
  • 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 is possible in the WLAN.
  • the determination in step S1701 described above can be made based on, for example, whether the UE 311 or the network side (for example, PGW 332) has instructed the user data of the UE 311 to be aggregated. Or judgment of Step S1701 can be performed based on whether the amount of user data to UE311 exceeded a threshold, for example.
  • the amount of user data may be the amount per time or the total amount of a series of user data of the UE 311.
  • the determination in step S1701 can be made based on, for example, the delay time of communication between the eNB 321 and the UE 311 by LTE-A, the delay time of communication between the eNB 321 and the UE 311 by WLAN, and the like.
  • eNB 321 transmits user data using only WLAN when aggregation is not performed. May be.
  • aggregation it is possible to determine whether to use LTE-A or WLAN based on an instruction from the UE 311 or the network side (for example, PGW 332), for example. Or this judgment can be performed based on whether the amount of user data to UE311 exceeded a threshold, for example.
  • the amount of user data may be the amount per time or the total amount of a series of user data of the UE 311.
  • this determination can be made based on, for example, the delay time of communication between the eNB 321 and the UE 311 by LTE-A, the delay time of communication between the eNB 321 and the UE 311 by WLAN, and the like.
  • step S1704 differs depending on whether or not the eNB 321 has a WLAN communication function.
  • the UE 311 directly transmits user data to the eNB 321 transmitted by the WLAN to the eNB 321.
  • the UE 311 transfers the user data to the eNB 321 transmitted by the WLAN to the secondary eNB 323 having the WLAN communication function connected to the eNB 321. Thereby, user data to eNB 321 can be transmitted via secondary eNB 323.
  • 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. 18, parts that are the same as the parts shown in FIG. 14 are given the same reference numerals, and descriptions thereof will be omitted. For example, when the IP packets 1401 and 1402 are both background IP packets, in the ToS value analysis classification 1410, the IP packets 1401 and 1402 are both classified as AC1314 (background).
  • the receiving side may not be able to uniquely identify the EPS bearer. That is, the receiving side may not be able to convert the received radio bearer into an EPS bearer.
  • the receiving side may not be able to convert the received radio bearer into an EPS bearer.
  • the IP flow between the eNB 321 and the PGW 332 is managed as an EPS bearer, when the eNB 321 cannot convert the radio bearer into the EPS bearer, it becomes difficult to transmit the IP flow from the eNB 321 to the PGW 332.
  • the transmitting side of the UE 311 and the eNB 321 does not perform aggregation on the EPS bearer having the same QoS class at the same time.
  • the transmitting side when transmitting a plurality of EPS bearers having the same QoS class to the UE 311, the transmitting side performs aggregation for only one of the plurality of EPS bearers. Then, the transmitting side transmits the remaining EPS bearer to the UE 311 by LTE-A without performing aggregation.
  • the transmission side when transmitting a plurality of EPS bearers having the same QoS class to the UE 311, the transmission side performs transmission by LTE-A without performing aggregation. Thereby, since a plurality of EPS bearers having the same QoS class are not simultaneously transferred to the WLAN, the UE 311 can uniquely identify the EPS bearer based on AC for each user data transferred to the WLAN.
  • the transmitting side of the UE 311 and the eNB 321 may perform a process of aggregating the plurality of EPS bearers into one bearer.
  • a process of aggregating a plurality of EPS bearers into one bearer for example, “UE requested bearer resource modification procedure” defined in TS23.401 of 3GPP can be used.
  • the UE 311 can uniquely identify the EPS bearer based on AC for each user data transferred to the WLAN.
  • 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. It is also possible. In this case, for each user data transferred to the WLAN, the UE 311 can uniquely specify an EPS bearer using the identification information.
  • FIG. 19 is a diagram showing an example of an outer IP layer implementation using the 3GPP protocol in the second embodiment.
  • the outer IP layer is provided as a part of the PDCP layer has been described, but the outer IP layer 1900 is provided as a lower layer of the PDCP layer 1901 as in the protocol stack shown in FIG. Also good.
  • the PDCP layer 1901 performs processing such as concealment by PDCP and adds a PDCP header, and an IP header added to the packet before performing processing such as concealment by PDCP, Are transferred to the outer IP layer 1900.
  • the PDCP header is a 2-byte header, for example.
  • the outer IP layer 1900 adds the IP header transferred from the PDCP layer 1901 to the PDCP packet transferred from the PDCP layer 1901 as an outer IP header. Thereby, the PDCP packet can be transmitted via the WLAN by tunneling.
  • the outer IP header is, for example, the same 20-byte header as the inner IP header.
  • FIG. 20 is a diagram illustrating another example of an outer IP layer implementation using the 3GPP protocol in the second embodiment. 20, parts that are the same as the parts shown in FIG. 19 are given the same reference numerals, and descriptions thereof will be omitted.
  • the outer IP layer 1900 may be provided as a lower layer of the PDCP layer 1901 and the RLC layer 1902.
  • the PDCP layer 1901 includes a PDCP packet that has been subjected to processing such as concealment by PDCP, and an IP header (inner IP header) that is added to the packet before processing such as concealment by PDCP, Are transferred to the RLC layer 1902.
  • the RLC layer 1902 adds an RLC header to the PDCP packet transferred from the PDCP layer 1901, and transfers the RLC packet with the RLC header added and the IP header transferred from the PDCP layer 1901 to the outer IP layer 1900. To do.
  • the RLC header is, for example, a variable length header.
  • the outer IP layer 1900 adds the IP header transferred from the RLC layer 1902 to the RLC packet transferred from the RLC layer 1902 as an outer IP header.
  • the RLC packet can be transmitted via the WLAN by tunneling.
  • retransmission control by RLC for example, is possible for data transmitted via WLAN by tunneling.
  • FIG. 21 is a diagram showing still another example of implementation of the outer IP layer using the 3GPP protocol in the second embodiment.
  • the same parts as those shown in FIG. 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.
  • the RLC layer 1902 transfers the RLC packet with the RLC header added thereto 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.
  • the outer IP layer 1900 adds the IP header transferred from the MAC layer 1903 to the MAC frame transferred from the MAC layer 1903 as an outer IP header. Thereby, a MAC frame can be transmitted via WLAN by tunneling. For this reason, for example, retransmission control by HARQ is possible for data transmitted via WLAN by tunneling.
  • FIG. 22 is a diagram illustrating an example of the implementation of the outer IP layer using the new tunneling protocol in the second embodiment.
  • a tunneling layer 2201 which is a new tunneling protocol, may be provided between the PDCP layer 1901 and the outer IP layer 1900.
  • the tunneling layer 2201 adds a tunneling header to the PDCP packet to which the PDCP header is added by the PDCP layer 1901. Also, the tunneling layer 2201 may add a tunneling header including bearer identification information to the PDCP packet, for example.
  • the outer IP layer 1900 adds an outer IP header to the packet to which the tunneling header is added by the tunneling layer 2201.
  • the bearer identification information is, for example, a bearer ID. The receiving station can identify the EPS bearer by referring to the bearer ID.
  • 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.
  • 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.
  • FIG. 24 is a diagram showing still another example of implementation of the outer IP layer using the new tunneling protocol in the second embodiment.
  • 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.
  • 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 below the PDCP layer 1901. Further, 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 part of the RLC layer 1902 and the MAC layer 1903.
  • the aggregation station that uses LTE-A and WLAN at the same time performs aggregation using the eNB 321 and the UE 311, the PDCP packet transmitted by the WLAN is tunneled by the outer IP. can do.
  • the receiving side receives the data transmitted by the WLAN as a PDCP packet, and uses the PDCP sequence number to control the order between the packet received by LTE-A and the packet received by the WLAN. It can be carried out. Therefore, data transmission using LTE-A and WLAN simultaneously becomes possible.
  • the data transmission speed can be improved.
  • the maximum transmission rate when only one of LTE-A and WLAN is used is the maximum transmission rate of LTE-A when LTE-A is used, and the maximum transmission rate of WLAN when WLAN is used.
  • the maximum transmission rate when LTE-A and WLAN are used simultaneously is the sum of the maximum transmission rate of LTE-A and the maximum transmission rate of WLAN.
  • 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.
  • an outer IP header which is a copy of the inner IP header
  • 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 data transmitted by the WLAN, and QoS control according to the nature of the traffic can be performed.
  • FIG. 25 is a diagram illustrating an example of a method for identifying an EPS bearer using a UL TFT in the wireless communication system according to the third embodiment.
  • FIG. 25 the same parts as those shown in FIG. 25
  • EPS bearers 1500 to 150n are bearers in the uplink direction from UE 311 to eNB 321. That is, the source (src IP) of the EPS bearers 1500 to 150n is UE 311 (UE). The destinations (dst IP) of the EPS bearers 1500 to 150n are both the core network (CN).
  • the UE 311 causes the EPS bearers 1500 to 150n to pass through the PDCP layers 1570 to 157n when performing aggregation using the LTE-A and the WLAN simultaneously for the EPS bearers 1500 to 150n. At this time, the UE 311 tunnels the PDCP packet by adding an outer IP header to the PDCP packet transmitted by the WLAN. Thereby, the PDCP packet transmitted by WLAN becomes an IP packet.
  • 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 150n via the PDCP layers 1570 to 157n.
  • the AC classification 2510 is a process based on a WLAN (802.11e) function in the UE 311.
  • Each IP packet classified by the AC classification 2510 is transmitted to the eNB 321 via the WLAN 1550.
  • the eNB 321 performs AC declassification 2520 on each IP packet received via the WLAN 1550 based on the ToS field included in the outer IP header of the IP packet.
  • the AC declassification 2520 is a process based on a WLAN (802.11e) function in the eNB 321.
  • the UE 311 does not add an outer IP header to the packets transmitted by the LTE-A in each of the EPS bearers 1500 to 150n, processes RLC, MAC, and PHY in this order and wirelessly transmits the packets to the eNB 321 through the LTE-A. Send.
  • the eNB 321 receives the packet transmitted from the UE 311 by LTE-A by processing the packet using PHY, MAC, RLC, and PDCP (PDCP layers 1570 to 157n).
  • the eNB 321 performs packet filtering 2530 based on UL (uplink) TFTs for each IP packet received by the AC declassification 2520.
  • packet filtering 2530 each IP packet is filtered according to whether or not each condition (f1 to f3) corresponding to the TFT is satisfied (match / no).
  • the EPS bearer classification 2531 which identifies an EPS bearer according to the result of this filtering is performed. Thereby, the EPS bearer corresponding to each IP packet transferred to the WLAN is identified.
  • a method of acquiring a UL TFT in the eNB 321 will be described later (see, for example, FIG. 27).
  • 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 151n based on the identification result by the EPS bearer classification 2531.
  • each IP packet (IP flow) transferred to the WLAN is converted into a corresponding EPS bearer and transferred to the PDCP layers 1510 to 151n.
  • ENB 321 obtains a PDCP packet by removing an outer IP header attached to each IP packet received by WLAN. Then, the eNB 321 performs order 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. Accordingly, 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 after being divided into the LTE-A and the WLAN. .
  • the eNB 321 can identify the EPS bearer of each IP packet transferred to the WLAN by performing the packet filtering 2530 based on the UL TFT for each IP packet transferred to the WLAN. Therefore, the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • FIG. 26 is a diagram illustrating another example of a method of identifying an EPS bearer using a UL TFT in the wireless communication system according to the third embodiment.
  • the eNB 321 becomes a master eNB and performs aggregation using the LTE-A and the WLAN simultaneously in a WLAN independent configuration using the secondary eNB 323 having a WLAN communication function with the eNB.
  • GTP tunnels 1520 to 152n for each EPS bearer are set between the eNB 321 and the secondary eNB 323.
  • Secondary eNB 323 receives each IP packet transmitted from UE 311 via WLAN 1550. Then, the secondary eNB 323 performs AC declassification 2520 and packet filtering 2530 similar to the example illustrated in FIG. 25 on each received IP packet. Thereby, EPS bearer classification 2531 in the packet filtering 2530 is performed for each IP packet, and the EPS bearer corresponding to each IP packet is identified.
  • Secondary eNB 323 transfers each IP packet to a GTP tunnel corresponding to the EPS bearer of the IP packet among GTP tunnels 1520 to 152n based on the identification result by EPS bearer classification 2531. As a result, each IP packet is transferred to the corresponding PDCP layer among the PDCP layers 1510 to 151n of the eNB 321.
  • the secondary eNB 323 can identify the EPS bearer of each IP packet transferred to the WLAN by performing packet filtering 2530 based on the UL TFT for each IP packet transferred to the WLAN. Then, the secondary eNB 323 transfers each IP packet through the GTP tunnels 1520 to 152n according to the identification result of the EPS bearer, so that the eNB 321 can receive each IP packet transferred to the WLAN as an EPS bearer.
  • the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • FIG. 27 is a diagram illustrating an example of a TFT acquisition method in the wireless communication system according to the third embodiment.
  • Each step shown in FIG. 27 is a process of “Dedicated Bearer Activation Procedure” defined in 3GPP TS23.401.
  • a 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 services.
  • the PGW 332 sets the UL and DL TFTs for the UE 311, stores the set TFTs in the create bearer request 2702 shown in FIG. 27, and transmits them to the SGW 331.
  • the SGW 331 transmits the create bearer request 2702 transmitted from the PGW 332 to the MME 333.
  • the MME 333 transmits a bearer setup request / session management request 2703 including a 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.
  • eNB321 can acquire TFT of UL and DL.
  • the eNB 321 transmits an RRC connection reconfiguration 2704 including a UL TFT among TFTs included in the bearer setup request / session management request 2703 transmitted from the MME 333 to the UE 311. Thereby, UE311 can acquire UL TFT.
  • the UL TFT can be specified in the RRC connection reconfiguration message, but is preferably specified in a NAS (Non Access Stratum) PDU transmitted in the message. The same applies thereafter.
  • the eNB 321 can perform the packet filtering 2530 using the UL TFT acquired from the bearer setup request / session management request 2703.
  • the eNB 321 transmits the UL TFT acquired from the bearer setup request / session management request 2703 to the secondary eNB 323.
  • the secondary eNB 323 can perform packet filtering 2530 based on the UL TFT transmitted from the eNB 321.
  • FIG. 28 is a diagram illustrating an example of a method for identifying an EPS bearer using DL TFTs in the wireless communication system according to the third embodiment.
  • the same parts as those shown in FIG. 28 are identical parts as those shown in FIG. 28.
  • EPS bearers 1500 to 150n are downlink bearers from eNB 321 to UE 311.
  • the UE 311 performs packet filtering 2810 based on DL (downlink) TFTs on each IP packet received by the AC declassification 1560.
  • the packet filtering 2810 by the UE 311 is a process based on the DL TFT, and is therefore the same process as the packet filtering by the filter layer 811 in the PGW 332 shown in FIG.
  • each IP packet is filtered according to whether or not each condition (f1 to f3) corresponding to the TFT is satisfied (match / no). Then, EPS bearer classification 2811 for identifying the EPS bearer according to the result of this filtering is performed. Thereby, the EPS bearer corresponding to each IP packet transferred to the WLAN is identified.
  • the eNB 321 stores the DL TFT in addition to the UL TFT in the RRC connection reconfiguration 2704 to the UE 311 illustrated in FIG. Accordingly, the UE 311 can acquire the DL TFT from the RRC connection reconfiguration 2704 and perform packet filtering 2810 based on the acquired DL TFT.
  • 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 157n 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 the PDCP layers 1570 to 157n.
  • the UE 311 can identify the EPS bearer of each IP packet transferred to the WLAN by performing packet filtering 2810 based on the DL TFT for each IP packet transferred to the WLAN. Therefore, the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • FIG. 29 is a diagram illustrating another example of a method for identifying an EPS bearer using DL TFTs in the wireless communication system according to the third embodiment. 29, the same parts as those shown in FIG. 15 or FIG.
  • the eNB 321 becomes the master eNB and performs aggregation using the LTE-A and the WLAN simultaneously in a WLAN independent configuration using the secondary eNB 323 having a WLAN communication function with the eNB.
  • GTP tunnels 1520 to 152n for each EPS bearer are set between the eNB 321 and the secondary eNB 323.
  • Secondary eNB 323 receives each IP packet transmitted from UE 311 via WLAN 1550. Then, the secondary eNB 323 transfers each received IP packet to the PDCP layers 1570 to 157n.
  • the UE 311 performs packet filtering 2810 based on DL TFTs on each IP packet transferred to the WLAN, whereby EPS of each IP packet transferred to the WLAN is obtained.
  • a bearer can be identified. Therefore, the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the number of EPS bearers that can be transferred to the WLAN is not limited by the number of bits of the VLAN tag, and the EPS bearer is identified. Is possible. Further, according to the method using the TFT 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.
  • FIG. 30 is a diagram illustrating an example of a method for identifying an EPS bearer using a virtual IP flow in the wireless communication system according to the third embodiment. 30, the same parts as those shown in FIG. 15 are denoted by the same reference numerals, and the description thereof is omitted.
  • FIG. 30 illustrates a case where aggregation is performed using the LTE-A and the WLAN at the same time in a configuration in which the eNB 321 has a WLAN communication function (eNB + WLAN) on the downlink.
  • EPS bearers 1500 to 150n are downlink bearers from eNB 321 to UE 311.
  • a virtual GW 3010 is set between the PDCP layers 1510 to 151n and the WLAN 1550 in the eNB 321.
  • the virtual GW 3010 includes NAT processing units 3020 to 302n 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 157n in the UE 311.
  • the virtual GW 3040 includes a MAC processing unit 3050 (802.3 MAC) and de-NAT processing units 3060 to 306n.
  • the EPS bearers 1500 to 150n via the PDCP layers 1510 to 151n are transferred to the NAT processing units 3020 to 302n of the virtual GW 3010.
  • the NAT processing units 3020 to 302n perform NAT (Network Address Translation) processing for classifying the EPS bearers 1500 to 150n into virtual IP flows according to virtual destination IP addresses.
  • the virtual IP flow is a local virtual data flow between the eNB 321 and the UE 311, for example.
  • the virtual destination IP address is a destination address of the virtual IP flow.
  • the NAT processing units 3020 to 302n transfer the classified virtual IP flows to the MAC processing unit 3030.
  • the NAT processing units 3020 to 302n map the EPS bearers 1500 to 150n 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 processing units 3020 to 302n can be, for example, the virtual GW 3010 (vGW).
  • the virtual destination IP address (dst IP) of each virtual IP flow transferred from the NAT processing units 3020 to 302n can be, for example, C-RNTI + 0 to C-RNTI + n, respectively.
  • the virtual destination IP address can be calculated from, for example, C-RNTI, but is not limited thereto.
  • the association between the EPS bearer identifier and the IP address may be notified to the UE 311 (mobile station) in advance by RRC signaling by the eNB 321 (master eNB) at the time of call setup or LTE-WLAN aggregation setup. .
  • C-RNTI Cell-Radio Network Temporary Identifier: cell radio network temporary identifier
  • C-RNTI Cell-Radio Network Temporary Identifier: cell radio network temporary identifier
  • C-RNTI has a 16-bit value.
  • an EPS bearer of about 24 bits that is sufficient for transmission by WLAN can be identified.
  • 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.
  • the MAC processing unit 3030 converts each virtual IP flow transferred from the NAT processing units 3020 to 302n into a MAC frame such as Ethernet or IEEE 802.3.
  • the source MAC address (src MAC) of the MAC frame can be any private address (any private) in the virtual GWs 3010 and 3040, for example.
  • the source MAC address of the MAC frame can be an address (x is an arbitrary value) with the first octet as “xxxxxxxx10”.
  • the destination MAC address (dst MAC) of the MAC frame can be the MAC address (UE MAC) of the UE 311, for example.
  • 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.
  • the UE 311 performs AC declassification 1560 on the MAC frame received from eNB 321 via WLAN 1550.
  • the MAC processing unit 3050 of the virtual GW 3040 receives the MAC frame subjected to AC declassification 1560 as a virtual IP flow.
  • the de-NAT processing units 3060 to 306n convert the virtual IP flow into the EPS bearer by referring to the virtual destination IP address (dst IP) of the virtual IP flow for the virtual IP flow received by the MAC processing unit 3050 . At this time, the virtual destination IP address of the virtual IP flow is converted to the original IP address by de-NAT by the de-NAT processing units 3060 to 306n.
  • the virtual GWs 3010 and 3040 can identify the EPS bearer as a virtual IP flow.
  • the IP address and the MAC address can be composed of private space addresses.
  • the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the downlink has been described, but the EPS bearer can be identified by the same method 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, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN in the uplink.
  • FIG. 31 is a diagram illustrating 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. 31 the same parts as those shown in FIG. 15 or FIG.
  • FIG. 31 illustrates a case in which aggregation is performed using the LTE-A and the WLAN at the same time in the WLAN independent configuration using the secondary eNB 323 having the eNB and the WLAN communication function as the eNB 321 on the downlink.
  • GTP tunnels 1520 to 152n for each EPS bearer are set between the eNB 321 and the secondary eNB 323.
  • the secondary eNB 323 receives each IP packet transmitted from the UE 311 via the WLAN 1550. Further, the secondary eNB 323 transfers each received IP packet to the NAT processing units 3020 to 302n of the virtual GW 3010.
  • the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the EPS bearer can be identified by the same method for the uplink. 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.
  • the number of EPS bearers that can be transferred to the WLAN is not limited to the number of bits of the VLAN tag, for example, when a VLAN tag is used. Can be identified.
  • the eNB 321 and the secondary eNB 323 can be connected not only by the GTP tunnel but also by Ethernet or the like.
  • the EPS bearer can be identified without setting a DL TFT in the UE 311 or a UL TFT in the eNB 321. It is. 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.
  • FIG. 32 is a diagram illustrating an example of a method of identifying an EPS bearer using a VLAN in the wireless communication system according to the third embodiment.
  • FIG. 32 the same parts as those shown in FIG. 15 or FIG.
  • FIG. 30 a method for identifying an EPS bearer by constructing a virtual IP network has been described.
  • FIG. 32 a method for identifying an EPS bearer by a VLAN that virtualizes Ethernet will be described.
  • the eNB 321 performs aggregation using the LTE-A and the WLAN simultaneously in a configuration in which the eNB 321 has a WLAN communication function (eNB + WLAN).
  • the EPS bearers 1500 to 150n are downlink bearers from the eNB 321 to the UE 311.
  • virtual GWs 3010 and 3040 are set in the eNB 321 and the UE 311 as in the example shown in FIG.
  • the virtual GW 3010 of the eNB 321 includes VLAN processing units 3210 to 321n and MAC processing units 3220 to 322n (802.3 MAC).
  • the virtual GW 3040 of the UE 311 includes MAC processing units 3230 to 323n (802.3 MAC) and de-VLAN processing units 3240 to 324n.
  • the EPS bearers 1500 to 150n via the PDCP layers 1510 to 151n are transferred to the VLAN processing units 3210 to 321n of the virtual GW 3010.
  • the VLAN processing units 3210 to 321n classify the EPS bearers 1500 to 150n into local IP flows between the eNB 321 and the UE 311 according to the VLAN, and transfer the classified IP flows to the MAC processing units 3220 to 322n.
  • the VLAN processing units 3210 to 321n map the EPS bearers 1500 to 150n and the VLAN tags on a one-to-one basis.
  • the VLAN identifier of each IP flow transferred from the VLAN processing units 3210 to 321n can be 0 to n, respectively.
  • the MAC processing units 3220 to 322n convert the IP flows transferred from the VLAN processing units 3210 to 321n into MAC frames such as Ethernet and IEEE 802.3, respectively.
  • the source MAC address (src MAC) of each MAC frame converted by the MAC processing units 3220 to 322n can be an arbitrary private address (any private) in the virtual GWs 3010 and 3040, for example.
  • the source MAC address of the MAC frame may be an address (x is an arbitrary value) with the first octet being “xxxxxx10”.
  • the destination MAC address (dst MAC) of each MAC frame converted by the MAC processing units 3220 to 322n can be, for example, the MAC address (UE MAC) of the UE 311.
  • the VLAN tag (VLAN tag) of each MAC frame converted by the MAC processing units 3220 to 322n can be set to 0 to n corresponding to each EPS bearer, for example.
  • a VLAN tag for each EPS bearer is added to each MAC frame.
  • the VLAN tag is a 12-bit tag, for example. Therefore, a maximum of 4094 VLANs can be constructed between the virtual GWs 3010 and 3040. If each UE including the UE 311 has all 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 actually used for communication, it is possible to transfer a sufficient number of EPS bearers to the WLAN using the VLAN.
  • the eNB 321 performs AC classification 1540 on the MAC frame with the VLAN tag converted by the MAC processing units 3220 to 322n. Then, the eNB 321 transmits the MAC frame with the VLAN tag subjected to AC classification 1540 to the UE 311 via the WLAN 1550.
  • the UE 311 performs AC declassification 1560 on the MAC frame with the VLAN tag received from the eNB 321 via the WLAN 1550.
  • the MAC processing units 3230 to 323n of the virtual GW 3040 are MAC processing units corresponding to the EPS bearers 1500 to 150n, respectively.
  • Each of the MAC processing units 3230 to 323n 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 subjected to AC declassification 1560. To do.
  • the de-VLAN processing units 3240 to 324n convert the IP flows received by the MAC processing units 3230 to 323n into EPS bearers 1500 to 150n, respectively.
  • the PDCP layers 1570 to 157n process EPS bearers 1500 to 150n converted by the de-VLAN processing units 3240 to 324n, respectively.
  • the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the downlink has been described, but the EPS bearer can be identified by the same method for the uplink. 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, the EPS bearer of each IP packet transferred to the WLAN in the uplink can be identified.
  • FIG. 33 is a diagram illustrating another example of the method of identifying the EPS bearer using the VLAN in the wireless communication system according to the third embodiment.
  • FIG. 33 illustrates a case where aggregation is performed using the LTE-A and the WLAN at the same time in a WLAN independent configuration using the secondary eNB 323 having the eNB and the WLAN communication function as the eNB 321 on the downlink.
  • GTP tunnels 1520 to 152n for each EPS bearer are set between the eNB 321 and the secondary eNB 323.
  • the VLAN processing units 3210 to 321n shown in FIG. 33 receives each IP packet transmitted from the UE 311 via the WLAN 1550. Then, the secondary eNB 323 transfers each received IP packet to the VLAN processing units 3210 to 321n of the virtual GW 3010.
  • the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the downlink has been described, but the EPS bearer can be identified by the same method 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, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN in the uplink.
  • the eNB 321 and the secondary eNB 323 can be connected not only by the GTP tunnel but also by Ethernet or the like.
  • the EPS bearer of each IP packet is identified by adding a VLAN tag without processing the packet referring to the IP header in the WLAN. be able to.
  • the EPS bearer can be identified without setting a DL TFT in the UE 311 or without setting a UL TFT in the eNB 321.
  • FIG. 34 is a diagram illustrating an example of a method of identifying an EPS bearer using GRE tunneling in the wireless communication system according to the third embodiment.
  • FIG. 34 parts similar to those shown in FIG. 15 or FIG.
  • FIG. 34 illustrates a case where aggregation is performed on the downlink by using the LTE-A and the WLAN simultaneously in a configuration in which the eNB 321 has a WLAN communication function (eNB + WLAN).
  • EPS bearers 1500 to 150n are downlink bearers from eNB 321 to UE 311.
  • a virtual GW 3010 is set between the PDCP layers 1510 to 151n and the WLAN 1550 in the eNB 321.
  • the virtual GW 3010 includes GRE processing units 3410 to 341n 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 157n in the UE 311.
  • the virtual GW 3040 includes a MAC processing unit 3050 (802.3 MAC) and de-GRE processing units 3420 to 342n.
  • the EPS bearers 1500 to 150n via the PDCP layers 1510 to 151n are transferred to the GRE processing units 3410 to 341n of the virtual GW 3010.
  • the GRE processing units 3410 to 341n classify the EPS bearers 1500 to 150n into local IP flows between the eNB 321 and the UE 311 using GRE (Generic Routing Encapsulation) tunneling, and the classified IP flows to the MAC processing unit. Transfer to 3030.
  • GRE Generic Routing Encapsulation
  • the GRE processing units 3410 to 341n add a GRE header to IP packets corresponding to the EPS bearers 1500 to 150n, add an IP header, and transfer the IP packet to the MAC processing unit 3030 as an IP flow.
  • the source IP address (src IP) of each IP flow transferred from the GRE processing units 3410 to 341n can be, for example, the virtual GW 3010 (vGW).
  • the destination IP address (dst IP) of each IP flow transferred from the GRE processing units 3410 to 341n can be, for example, C-RNTI + 0 to C-RNTI + n, respectively.
  • the MAC processing unit 3030 converts each IP flow transferred from the GRE processing units 3410 to 341n into an Ethernet (IEEE 802.3) MAC frame, for example, as in the example shown in FIG.
  • 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 user data through a WLAN GRE tunnel (encapsulated tunnel) set between the eNB 321 and the UE 311.
  • a WLAN GRE tunnel encapsulated tunnel
  • the UE 311 performs AC declassification 1560 on the MAC frame received from eNB 321 via WLAN 1550.
  • the MAC processing unit 3050 of the virtual GW 3040 receives the MAC frame on which AC declassification 1560 has been performed as an IP flow, for example, as in the example illustrated in FIG.
  • the de-GRE processing units 3420 to 342n convert the IP flow into an EPS bearer by referring to the IP address received by the MAC processing unit 3050 by referring to the destination IP address (dst IP) included in the IP header of the IP flow. To do.
  • EPS bearers can be identified as IP flows in virtual GWs 3010 and 3040.
  • the IP address and the MAC address can be composed of private space addresses.
  • the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the downlink has been described, but the EPS bearer can be identified by the same method for the uplink. That is, by constructing a 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.
  • FIG. 35 is a diagram illustrating another example of a method for identifying an EPS bearer using GRE tunneling in the wireless communication system according to the third embodiment.
  • the same portions as those shown in FIG. 15 or FIG. 34 are denoted by the same reference numerals and description thereof is omitted.
  • FIG. 35 illustrates a case where aggregation is performed using the LTE-A and the WLAN at the same time in the WLAN independent configuration using the secondary eNB 323 having the eNB and the WLAN communication function as the eNB 321 on the downlink.
  • GTP tunnels 1520 to 152n for each EPS bearer are set between the eNB 321 and the secondary eNB 323.
  • Secondary eNB 323 receives each IP packet transmitted from UE 311 via WLAN 1550. Then, the secondary eNB 323 transfers the received IP packets to the GRE processing units 3410 to 341n.
  • the UE 311 can identify the EPS bearer of each IP packet transferred to the WLAN by using GRE tunneling. Therefore, the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the number of EPS bearers transferred to the WLAN is not limited to the number of bits of the VLAN tag, and the EPS bearer is identified. Is possible.
  • the eNB 321 and the secondary eNB 323 can be connected not only by the GTP tunnel but also by Ethernet or the like.
  • the EPS bearer can be identified without setting a DL TFT in the UE 311 or without setting a UL TFT in the eNB 321. . Further, according to the method using GRE tunneling shown in FIGS. 34 and 35, the EPS bearer can be identified without adding a header such as a VLAN tag to the user data transferred to the WLAN.
  • FIG. 36 is a diagram illustrating an example of a method for identifying an EPS bearer using PDCPoIP in the wireless communication system according to the third embodiment.
  • FIG. 36 the same parts as those shown in FIG. 15 or FIG.
  • EPS bearers 1500 to 150n are downlink bearers from eNB 321 to UE 311.
  • a virtual GW 3010 is set between the PDCP layers 1510 to 151n and the WLAN 1550 in the eNB 321.
  • the virtual GW 3010 includes PDCPoIP processing units 3610 to 361n 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 157n in the UE 311.
  • the virtual GW 3040 includes a MAC processing unit 3050 (802.3 MAC) and a de-PDCPoIP processing units 3620 to 362n (de-PoIP).
  • the EPS bearers 1500 to 150n via the PDCP layers 1510 to 151n are transferred to the PDCPoIP processing units 3610 to 361n of the virtual GW 3010.
  • the PDCPoIP processing units 3610 to 361n perform PDCPoIP (Packet Data Convergence Protocol on IP) processing for classifying virtual IP flows by converting the addresses of the outer IP headers of the EPS bearers 1500 to 150n into virtual IP addresses, respectively.
  • the virtual IP flow is a local virtual data flow between the eNB 321 and the UE 311, for example.
  • the virtual destination IP address is a destination address of the virtual IP flow.
  • the PDPPoIP processing units 3610 to 361n transfer the classified virtual IP flows to the MAC processing unit 3030.
  • the PDPPoIP processing units 3610 to 361n map the EPS bearers 1500 to 150n 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 361n can be, for example, a virtual GW 3010 (vGW).
  • the virtual destination IP address (dst IP) of each virtual IP flow transferred from the PDCPoIP processing units 3610 to 361n can be, for example, C-RNTI + 0 to C-RNTI + n, respectively.
  • C-RNTI is temporarily assigned to UE 311 and is a unique identifier of UE 311 within the LTE-A cell.
  • C-RNTI has a 16-bit value.
  • an EPS bearer of about 24 bits that is sufficient for transmission by WLAN can be identified.
  • the method of generating the virtual source IP address is not limited to this.
  • the MAC processing unit 3030 converts each virtual IP flow transferred from the PDCPoIP processing units 3610 to 361n into a MAC frame such as Ethernet or IEEE 802.3.
  • the source MAC address (src MAC) of the MAC frame can be any private address (any private) in the virtual GWs 3010 and 3040, for example.
  • the source MAC address of the MAC frame can be an address (x is an arbitrary value) with the first octet as “xxxxxxxx10”.
  • the destination MAC address (dst MAC) of the MAC frame can be the MAC address (UE MAC) of the UE 311, for example.
  • 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.
  • the UE 311 performs AC declassification 1560 on the MAC frame received from eNB 321 via WLAN 1550.
  • the MAC processing unit 3050 of the virtual GW 3040 receives the MAC frame subjected to AC declassification 1560 as a virtual IP flow.
  • the de-PDCPoIP processing units 3620 to 362n convert the virtual IP flow into an EPS bearer by referring to the virtual destination IP address (dst IP) of the virtual IP flow for the virtual IP flow received by the MAC processing unit 3050 . At this time, the virtual destination IP address of the virtual IP flow is converted into the original IP address by de-PDCPoIP by the de-PDCPoIP processing units 3620 to 362n.
  • the EPS bearers can be identified as virtual IP flows in the virtual GWs 3010 and 3040.
  • the IP address and the MAC address can be composed of private space addresses.
  • the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the downlink has been described, but the EPS bearer can be identified by the same method 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, it is possible to identify the EPS bearer of each IP packet transferred to the WLAN in the uplink.
  • FIG. 37 is a diagram illustrating another example of a method of identifying an EPS bearer using PDCPoIP in the wireless communication system according to the third embodiment.
  • FIG. 37 the same parts as those shown in FIG. 15 or FIG.
  • FIG. 37 illustrates a case where, for downlink, aggregation is performed using LTE-A and WLAN simultaneously in a WLAN independent configuration using secondary eNB 323 having eNB 321 as a master eNB and having a WLAN communication function with eNB.
  • GTP tunnels 1520 to 152n for each EPS bearer are set between the eNB 321 and the secondary eNB 323.
  • the secondary eNB 323 receives each IP packet transmitted from the UE 311 via the WLAN 1550. Further, the secondary eNB 323 transfers each received IP packet to the PDCPoIP processing units 3610 to 361n of the virtual GW 3010.
  • the radio communication system 300 can perform aggregation without increasing the restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time, and can increase the amount of user data that can be transmitted.
  • the downlink has been described, but the EPS bearer can be identified by the same method for the uplink. 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.
  • the number of EPS bearers that can be transferred to the WLAN is not limited by the number of bits of the VLAN tag, for example, when a VLAN tag is used. A bearer can be identified.
  • the eNB 321 and the secondary eNB 323 can be connected not only by the GTP tunnel but also by Ethernet or the like.
  • the EPS bearer can be identified without setting a DL TFT in the UE 311 or a UL TFT in the eNB 321. Is possible. Further, according to the method using address translation by PDCPoIP shown in FIGS. 36 and 37, the EPS bearer can be identified without adding a header such as a VLAN tag to the user data transferred to the WLAN.
  • the third embodiment it is possible to perform aggregation using LTE-A and WLAN at the same time without providing a restriction that a plurality of EPS bearers having the same QoS class are not aggregated at the same time. Therefore, it is possible to increase the amount of user data that can be transmitted.
  • the UE 311 in the downlink from the eNB 321 to the UE 311, there is a case where user data received by the UE 311 as a radio bearer may be forwarded to an upper layer (for example, an application layer) of the own station without being converted into a bearer.
  • an upper layer for example, an application layer
  • the UE 311 can perform aggregation using LTE-A and WLAN simultaneously without identifying the bearers.
  • FIG. 38 and 39 are diagrams for explaining processing for data transmitted by WLAN in the wireless communication system according to the fourth embodiment.
  • the protocol stack shown in FIG. 38 has a PDCP layer 3801 (PDCP PDU), an outer IP layer 3802, and a WLAN MAC layer 3803 (WLAN MAC) for data transmitted by WLAN as in the second and third embodiments. The process performed in order is shown.
  • outer IP is used for convenience.
  • the outer IP is technically simply IP (Internet Protocol). This is the same in the present embodiment.
  • the PDCP layer 3801 corresponds to, for example, the PDCP layer in the aggregation processing 1212 illustrated in FIG. 12 and the PDCP layer 1901 illustrated in FIGS.
  • the outer IP layer 3802 corresponds to, for example, the outer IP processing in the aggregation processing 1212 shown in FIG. 12 and the outer IP layer 1900 shown in FIGS.
  • the MAC layer 3803 is, for example,... In the aggregation process 1212 illustrated in FIG. Supports 11x MAC processing.
  • the WLAN node (for example, eNB 321 or secondary eNB 323) can also operate in a mode like a router, for example.
  • the protocol stack shown in FIG. 39 shows processing for data transmitted by WLAN in the wireless communication system 300 according to the fourth embodiment.
  • PDCP layer 3801 processing, adaptation layer 3901 (Adaptation Layer) processing, and WLAN Processing of the MAC layer 3803 is performed.
  • a packet transmitted by the WLAN is tunneled by being transferred to the WLAN side with a predetermined header added by the adaptation layer 3901 after the process of the PDCP layer 3801.
  • the 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 a process 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.
  • the MAC address cannot be obtained from the IP address using ARP in IP.
  • the MAC address can be obtained from the IP address using the ARP in the adaptation layer 3901.
  • the WLAN node for example, eNB 321 or secondary eNB 323 operates in a mode like a bridge, for example.
  • Ethernet the upper layer of ARP is designated by Ethernet “EtherType”.
  • “EtherType” is undefined, but when a new “EtherType” is defined in the 3GPP protocol, ARP based on RFC826 can be applied to the adaptation layer 3901.
  • the WLAN node for example, eNB 321 or secondary eNB 323 can also operate in a mode such as a bridge.
  • the architecture of this unique address resolution method will be described below.
  • FIG. 40 is a sequence diagram illustrating an example of processing in the wireless communication system according to the fourth embodiment.
  • address resolution is realized by executing the steps shown in FIG. 40, for example.
  • a communication apparatus 4001 illustrated in FIG. 40 is a transmission source that transmits data to the UE 311 via the eNB 321.
  • the communication device 4001 is the PGW 332 of the packet core network 330 or the like.
  • the transmission path between the communication device 4001 and the eNB 321 is an IP network
  • the transmission path between the eNB 321 and the UE 311 is LTE or LTE-A.
  • a configuration of a WLAN independent type using the secondary eNB 323 in which the eNB 321 becomes a master eNB and has a function of WLAN communication with the eNB will be described.
  • the eNB 321 transmits an RRC connection reconfiguration including an LTE-WLAN configuration for setting LTE-WLAN aggregation to the UE 311 (step S4001).
  • UE311 transmits the RRC connection reconfiguration complete with respect to RRC connection reconfiguration to eNB321 (step S4002).
  • the UE 311 stores the MAC address of the UE 311 in the RRC connection reconfiguration complete transmitted in step S4002.
  • the eNB 321 transmits a WLAN addition request for setting the WLAN in LTE-WLAN aggregation to the secondary eNB 323 that is a WLAN node (step S4003). Also, the eNB 321 stores setting information including the MAC address of the UE 311 acquired from the RRC connection reconfiguration complete received in step S4002 in the WLAN addition request transmitted in step S4003.
  • 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.
  • 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 of data 4010 (for example, user data). Since the IP packet is originally transmitted through a GTP tunnel, a GTP header is added.
  • the eNB 321 converts the data received in step S4004 into a PDCP PDU and transfers it to the secondary eNB 323 (step S4005).
  • the secondary eNB 323 transmits the data converted into the PDCP PDU and transferred in step S4005 to the UE 311 by WLAN (IEEE MAC) (step S4006).
  • Data 4020 is data transmitted in step S4006.
  • the data 4020 is data in which the destination MAC address 4021 and the source MAC address 4022 are added as headers to the 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 S4003.
  • the transmission source MAC address 4022 is the MAC address of the secondary eNB 323 that is the transmission source of the data 4020.
  • the UE 311 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 the response signal. As a result, the eNB 321 and the secondary eNB 323 can acquire the MAC address of the UE 311 without using the IP ARP. Thus, the MAC address can be resolved using, for example, an RRC message.
  • the eNB 321 is a master eNB and the WLAN independent type configuration using the secondary eNB 323 having the WLAN communication function has been described, the secondary eNB 323 is not used, and the eNB 321 may have the WLAN communication function. In this case, for example, step S4003 becomes unnecessary, and the eNB 321 stores the MAC address of the UE 311 in association with the IP address of the UE 311.
  • eNB321 transmits the data 4020 which added the destination MAC address 4021 and the transmission origin MAC address 4022 to the data 4010 received from the communication apparatus 4001, to UE311.
  • the transmission source MAC address 4022 is the MAC address of the eNB 321 that is the transmission source of the data 4020.
  • the MAC address can be similarly resolved using RRC messages for uplink data transmitted from the UE 311 to the communication apparatus 4001.
  • 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 the eNB 321 and the secondary eNB 323 are connected, or may be acquired by the eNB 321 inquiring of the secondary eNB 323.
  • 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. And UE311 transmits this data to secondary eNB323, using the MAC address of the stored secondary eNB323 as a destination, when transmitting the data to the communication apparatus 4001 by WLAN.
  • the MAC address can be resolved using the RRC message for the uplink data transmitted from the UE 311 to the communication apparatus 4001.
  • FIG. 41 is a sequence diagram illustrating a method of notifying a MAC address using another RRC message in the processing in the wireless communication system according to the fourth embodiment.
  • the same parts as those shown in FIG. 40 are denoted by the same reference numerals and description thereof is omitted.
  • the UE 311 transmits an RRC connection setup to the eNB 321 before step S4001 (step S4101). Also, the UE 311 stores the MAC address of the UE 311 in the RRC connection setup transmitted in step S4101. In this case, the UE 311 may not store the MAC address of the UE 311 in the RRC connection reconfiguration complete transmitted in step S4002.
  • FIG. 42 is a sequence diagram illustrating a method for notifying a MAC address using still another RRC message in the processing in the wireless communication system according to the fourth embodiment.
  • UE311 transmits the RRC message different from RRC connection reconfiguration complete or RRC connection setup to eNB321 after step S4002 (step S4201).
  • the UE 311 stores the MAC address of the UE 311 in the RRC message transmitted in step S4201. In this case, the UE 311 may not store the MAC address of the UE 311 in the RRC connection reconfiguration complete transmitted in step S4002.
  • the RCC message used for notifying the MAC address of the UE 311 is not limited to the RRC connection reconfiguration complete, and can be various RRC messages.
  • FIG. 43 is a sequence diagram illustrating another example of processing in the wireless communication system according to the fourth embodiment. 43, the same parts as those shown in FIG. 40 are denoted by the same reference numerals, and description thereof is omitted.
  • address resolution may be realized by executing the steps shown in FIG.
  • step S4302 the UE 311 may not store the MAC address of the UE 311 in the RRC connection reconfiguration complete.
  • step S4303 the eNB 321 may not store the MAC address of the UE 311 in the WLAN addition request.
  • step S4305 the eNB 321 operates the ARP with the UE 311 using the 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. Thereby, the secondary eNB 323 can acquire the MAC address of the UE 311.
  • the ARP may be operated between the secondary eNB 323 and the UE 311. Thereby, the secondary eNB 323 can acquire the MAC address of the UE 311.
  • the ARP that operates in step S4306 is not an ARP based on RFC826, but may be an ARP that is uniquely designed in the adaptation layer 3901, for example.
  • the secondary eNB 323 can inquire the UE 311 about the MAC address using the ARP packet.
  • the ARP packet will be described later (see, for example, FIG. 44). Note that the order of step S4305 and step S4306 may be switched.
  • the secondary eNB 323 transmits the data transferred after being converted into the PDCP PDU in step S4305 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.
  • the destination MAC address 4021 in this case is the MAC address of the UE 311 acquired by the secondary eNB 323 by the ARP that was activated in step S4306.
  • the adaptation layer 3901 activates its own ARP, whereby the MAC address of the UE 311 can be acquired. In this manner, for example, the MAC address can be resolved using ARP uniquely designed in the adaptation layer 3901.
  • the eNB 321 is a master eNB and the WLAN independent type configuration using the secondary eNB 323 having the WLAN communication function has been described, the secondary eNB 323 is not used, and the eNB 321 may have the WLAN communication function. In this case, for example, step S4305 is not necessary, and the eNB 321 operates the ARP in its own device in step S4306. Thereby, eNB321 can acquire the MAC address of UE311.
  • eNB321 transmits the data 4020 which added the destination MAC address 4021 and the transmission origin MAC address 4022 to the data 4010 received from the communication apparatus 4001, to UE311.
  • the transmission source MAC address 4022 is the MAC address of the eNB 321 that is the transmission source of the data 4020.
  • the downlink data transmitted from the communication apparatus 4001 to the UE 311 has been described.
  • the uplink data transmitted from the UE 311 to the communication apparatus 4001 is similarly resolved using a uniquely designed ARP. be able to.
  • the UE 311 acquires the MAC address of the secondary eNB 323 by operating the unique ARP described above in the own device and inquiring the secondary eNB 323 when transmitting data to the communication device 4001 by WLAN.
  • the UE 311 transmits uplink data to the secondary eNB 323 using the acquired MAC address of the secondary eNB 323 as a destination.
  • the MAC address can be resolved also for the uplink data transmitted from the UE 311 to the communication device 4001 by using the ARP designed uniquely.
  • FIG. 44 is a diagram showing an example of a packet format in ARP applicable to the fourth embodiment.
  • ARP uniquely designed in the adaptation layer 3901 as shown in FIG. 43
  • a packet 4400 shown in FIG. 44 can be used.
  • “R” is a reserved bit (Reserved).
  • “D / C” is information indicating whether the packet 4400 is a data signal (data) or a control signal (control). In “D / C”, “D” (data) or “C” (control) is designated. When “D” is designated in “D / C”, it indicates that the second and subsequent lines of the packet 4400 are PDCP PDUs. When “C” is designated in “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”.
  • Type is information indicating whether the packet 4400 is a request signal or a response signal. “Type” is invalid when “D” is designated in “D / C”. In addition, “type” (Type) is designated as “request” or “response” when “C” is designated as “D / C”. “LCID” indicates LCID (Logical Channel ID) in LTE. “C-RNTI” (Cell-Radio Network Temporary Identifier) is a cell radio network temporary identifier of UE 311.
  • ARP control information is stored in the second and subsequent lines of the packet 4400 as described above.
  • the secondary eNB 323 which is the inquiry source of the MAC address, transmits a packet 4400 in which “Request” is specified for “Type”.
  • the MAC address (48 bits) of the secondary eNB 323 is stored in the “source MAC address” (Source MAC Address) of the packet 4400.
  • the “destination MAC address” (Destination MAC Address) of the packet 4400 stores the MAC address for broadcasting (48 bits).
  • the packet 4400 can be broadcast, and the MAC address can be inquired to the UE 311.
  • the UE 311 can receive the packet 4400 (request) from the secondary eNB 323 based on the “C-RNTI” of the packet 4400 by determining that the packet is addressed to itself. Then, when receiving the packet 4400 from the secondary eNB 323, the UE 311 transmits the packet 4400 in which “response” is specified as “type”. In this case, the MAC address (48 bits) of the UE 311 is stored in the “source MAC address” of the packet 4400. Further, the MAC address of the secondary eNB 323 is stored in the “destination MAC address” (Destination MAC Address) of the packet 4400. Thereby, the MAC address of UE311 can be notified with respect to secondary eNB323.
  • the ARP uniquely designed in the adaptation layer 3901 is not limited to the packet 4400 shown in FIG. 44, and packets of various formats can be used. For example, if the ARP uniquely designed in the adaptation layer 3901 includes destination identification information such as “C-RNTI”, “source MAC address”, and “destination MAC address”. Good. In addition, when it is determined that the UE can be identified only by the MAC address, “C-RNTI” may not be provided.
  • Embodiment 4 for example, when EPS bearers 1500 to 150n are divided into LTE-A and WLAN for transmission, PDCP packets transmitted by WLAN can be tunneled by adaptation layer 3901. As a result, the receiving side receives the data transmitted by the WLAN as a PDCP packet, and uses the PDCP sequence number to control the order between the packet received by LTE-A and the packet received by the WLAN. It can be carried out. Therefore, data transmission using LTE-A and WLAN simultaneously becomes possible.
  • the MAC address of the receiving station that can be used in WLAN can be stored in the RRC (Radio Resource Control) message transmitted from the receiving station to the transmitting station. .
  • the transmitting station can transmit data to the transmitting station with the MAC address acquired from the RRC message as the destination address. Therefore, it is possible to resolve the MAC address even when the adaptation layer 3901 is used without using IP (outer IP) in tunneling.
  • the transmitting station when transmitting data using WLAN, can transmit a first packet requesting the MAC address of the receiving station that can be used in the WLAN to the receiving station.
  • 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.
  • the transmitting station can transmit data to the receiving station using the MAC address of the transmitting station acquired from the second packet from the transmitting station as the destination address. Therefore, it is possible to resolve the MAC address even when the adaptation layer 3901 is used without using IP (outer IP) in tunneling.
  • the fourth embodiment can be implemented in combination with the first to third embodiments as appropriate.
  • the base station 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 simultaneously. For example, aggregation using LTE-A and WLAN at the same time is possible, so that the transmission rate of user data can be improved.
  • the ToS field can be referred to in the WLAN, and QoS control according to the nature of the traffic is possible. become.
  • VoLTE traffic is classified into voice (VO) and preferentially transmitted by WLAN, so that the communication quality of VoLTE can be improved.
  • 3GPP's LTE-A will also take into account fifth-generation mobile communications, aiming to cope with the increasing mobile traffic and improve user experience, so that system communications can be performed in cooperation with other wireless systems. Consideration is being made. In particular, cooperation with WLANs widely implemented in smart phones as well as homes and companies becomes an issue.
  • LAA Liense Assisted Access
  • LAA is a carrier aggregation of an unlicensed frequency band and a licensed frequency band for LTE-A, and is a layer 1 technique for controlling radio transmission of the unlicensed frequency band by an LTE-A control channel.
  • LTE-A and WLAN are aggregated at Layer 2, and standardization for cellular communication in cooperation with each other is about to start. This is called LTE-WLAN aggregation.
  • the LTE-WLAN aggregation has the following advantages compared to the method described above.
  • LTE-WLAN aggregation In LAA, high-speed aggregation corresponding to LTE-A radio quality is possible, but aggregation in cooperation with WLAN outside the LTE-A base station is difficult. In contrast, in LTE-WLAN aggregation, cooperative aggregation is possible by connecting an LTE-A base station and an installed WLAN access point at the layer 2 level.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une station de base (110) qui utilise une unité de commande (111) pour commander une première communication sans fil (101) afin de commander une seconde communication sans fil (102). Une transmission de données entre une station mobile (120) et la station de base (110) peut être réalisée à l'aide de la première communication sans fil (101) ou de la seconde communication sans fil (102). Lorsque la seconde communication sans fil (102) est utilisée pour transmettre des données entre la station de base (110) et la station mobile (120), des unités de traitement (112, 121) pour réaliser la première communication sans fil (101) dans la station côté transmission réalisent un traitement d'acheminement sur des données traitées d'une couche de convergence pour réaliser la première communication sans fil (101), et transmettent lesdites données à la station côté réception entre la station de base (110) et la station mobile (120).
PCT/JP2015/063953 2015-04-10 2015-05-14 Système de communication sans fil, station de base, station mobile, et procédé de traitement WO2016163036A1 (fr)

Priority Applications (12)

Application Number Priority Date Filing Date Title
CN201580078671.2A CN107534898A (zh) 2015-04-10 2015-05-14 无线通信***、基站、移动站和处理方法
BR112017021425-3A BR112017021425A2 (pt) 2015-04-10 2015-05-14 sistema de comunicações sem fio, estação base, estação móvel, e método de processamento
JP2017511445A JP6172419B2 (ja) 2015-04-10 2015-05-14 無線通信システム、基地局、移動局および処理方法
CN202310949372.8A CN116744247A (zh) 2015-04-10 2015-05-14 无线通信***、移动站和无线通信装置
EP15888527.7A EP3282747B1 (fr) 2015-04-10 2015-05-14 Système de communication sans fil, station de base, station mobile, et procédé de traitement
CA2982804A CA2982804C (fr) 2015-04-10 2015-05-14 Systeme de communication sans fil, station de base, station mobile, et procede de traitement
KR1020177028778A KR102052466B1 (ko) 2015-04-10 2015-05-14 무선 통신 시스템, 기지국, 이동국 및 처리 방법
MX2017012980A MX360887B (es) 2015-04-10 2015-05-14 Sistema de comunicaciones inalámbricas, estación base, estación móvil y método de procesamiento.
RU2017134998A RU2682420C1 (ru) 2015-04-10 2015-05-14 Система беспроводной связи, базовая станция, мобильная станция и способ обработки
US15/725,890 US11690092B2 (en) 2015-04-10 2017-10-05 Wireless communications system, base station, mobile station, and processing method
US16/373,307 US11737128B2 (en) 2015-04-10 2019-04-02 Wireless communications system, base station, mobile station, and processing method
US17/890,432 US20220394724A1 (en) 2015-04-10 2022-08-18 Wireless communications system, base station, mobile station, and processing method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JPPCT/JP2015/061293 2015-04-10
PCT/JP2015/061293 WO2016163032A1 (fr) 2015-04-10 2015-04-10 Système de communication sans fil, station de base, station mobile et procédé de traitement

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/725,890 Continuation US11690092B2 (en) 2015-04-10 2017-10-05 Wireless communications system, base station, mobile station, and processing method

Publications (1)

Publication Number Publication Date
WO2016163036A1 true WO2016163036A1 (fr) 2016-10-13

Family

ID=57071861

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/JP2015/061293 WO2016163032A1 (fr) 2015-04-10 2015-04-10 Système de communication sans fil, station de base, station mobile et procédé de traitement
PCT/JP2015/063953 WO2016163036A1 (fr) 2015-04-10 2015-05-14 Système de communication sans fil, station de base, station mobile, et procédé de traitement

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/061293 WO2016163032A1 (fr) 2015-04-10 2015-04-10 Système de communication sans fil, station de base, station mobile et procédé de traitement

Country Status (10)

Country Link
US (3) US11690092B2 (fr)
EP (1) EP3282747B1 (fr)
JP (3) JP6172419B2 (fr)
KR (1) KR102052466B1 (fr)
CN (2) CN116744247A (fr)
BR (1) BR112017021425A2 (fr)
CA (1) CA2982804C (fr)
MX (1) MX360887B (fr)
RU (1) RU2682420C1 (fr)
WO (2) WO2016163032A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018078987A1 (fr) * 2016-10-31 2018-05-03 日本電気株式会社 Entité de gestion de mobilité, entité de réseau, procédés associés, et support lisible par ordinateur
WO2018136422A3 (fr) * 2017-01-18 2018-09-27 Qualcomm Incorporated Techniques de gestion de flux de protocole internet dans une architecture de couche 2 d'un dispositif sans fil
US20180288647A1 (en) * 2017-03-29 2018-10-04 Nanning Fugui Precision Industrial Co., Ltd. Wireless communication system and method
JPWO2021033268A1 (fr) * 2019-08-20 2021-02-25
JP2022528541A (ja) * 2019-04-08 2022-06-14 華為技術有限公司 データ送信方法および装置、ならびにコンピュータ可読記憶媒体

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109548160A (zh) * 2017-08-08 2019-03-29 ***通信有限公司研究院 数据传输方法、装置、相关设备及计算机可读存储介质
US10652951B1 (en) * 2018-02-22 2020-05-12 Sprint Spectrum L.P. Communicating with a wireless device via at least two access nodes
CN111163019B (zh) * 2018-11-07 2022-10-28 中兴通讯股份有限公司 处理数据包的方法、装置和存储介质
US10819620B2 (en) * 2019-02-07 2020-10-27 Dell Products, Lp System and method for optimizing layer three link aggregation in a mesh network
WO2020177856A1 (fr) * 2019-03-04 2020-09-10 Nokia Technologies Oy Appareils et procédés de duplication de données
US11683286B2 (en) * 2021-11-18 2023-06-20 Cisco Technology, Inc. Anonymizing server-side addresses

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011503914A (ja) * 2007-05-04 2011-01-27 株式会社東芝 多重インターフェースの同時使用のためのインテリジェントコネクティビティフレームワーク
JP2014003644A (ja) * 2008-06-09 2014-01-09 Qualcomm Incorporated デュアルアクセスネットワークのネットワークベース制御
JP2014027548A (ja) * 2012-07-27 2014-02-06 Fujitsu Ltd 基地局装置、無線端末装置及びパケット振分け方法

Family Cites Families (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7656880B1 (en) 2004-06-09 2010-02-02 Verizon Laboratories Inc. Prioritized segmentation and reassembly methods and systems
US8169891B2 (en) 2005-03-31 2012-05-01 Agere Systems Inc. Apparatus and method for handling lost cells in a communications system
US8626172B2 (en) * 2005-08-10 2014-01-07 Qualcomm Incorporated Method and apparatus for simultaneous communication utilizing multiple wireless communication systems
US7653037B2 (en) 2005-09-28 2010-01-26 Qualcomm Incorporated System and method for distributing wireless network access parameters
US20080076425A1 (en) * 2006-09-22 2008-03-27 Amit Khetawat Method and apparatus for resource management
US20080076412A1 (en) * 2006-09-22 2008-03-27 Amit Khetawat Method and apparatus for registering an access point
US20080076419A1 (en) * 2006-09-22 2008-03-27 Amit Khetawat Method and apparatus for discovery
US8036664B2 (en) * 2006-09-22 2011-10-11 Kineto Wireless, Inc. Method and apparatus for determining rove-out
US8204502B2 (en) * 2006-09-22 2012-06-19 Kineto Wireless, Inc. Method and apparatus for user equipment registration
US8041335B2 (en) * 2008-04-18 2011-10-18 Kineto Wireless, Inc. Method and apparatus for routing of emergency services for unauthorized user equipment in a home Node B system
JP5097620B2 (ja) * 2008-06-03 2012-12-12 株式会社日立製作所 マルチパス通信システム
KR20110083772A (ko) 2010-01-15 2011-07-21 삼성전자주식회사 무선통신 시스템에서 이더넷 프레임을 이용한 시스템 초기화 장치 및 방법
US9455897B2 (en) * 2010-04-06 2016-09-27 Qualcomm Incorporated Cooperative bandwidth aggregation using multipath transport
KR102073027B1 (ko) * 2011-04-05 2020-02-04 삼성전자 주식회사 반송파 집적 기술을 사용하는 무선통신시스템에서 복수 개의 타임 정렬 타이머 운용 방법 및 장치
US20130265984A1 (en) 2011-03-07 2013-10-10 Honggang Li Grouped machine-to-machine communications
WO2012139301A1 (fr) * 2011-04-15 2012-10-18 Renesas Mobile Corporation Configuration d'agrégation de porteuses lte sur bandes d'espace blanc tv
CN105704759A (zh) * 2011-05-27 2016-06-22 上海华为技术有限公司 一种数据流传输方法及网络设备
US10321419B2 (en) * 2011-08-10 2019-06-11 Samsung Electronics Co., Ltd. Method and apparatus for transmitting data using a multi-carrier in a mobile communication system
EP2744132A4 (fr) * 2011-08-10 2015-05-06 Samsung Electronics Co Ltd Procédé et appareil pour transmettre des données au moyen de multiples porteuses dans un système de communication mobile
EP3429307B1 (fr) * 2011-08-10 2022-06-15 Samsung Electronics Co., Ltd. Procédé et appareil pour transmettre des données au moyen de multiples porteuses dans un système de communication mobile
CN104025475B (zh) * 2011-10-03 2018-04-13 英特尔公司 装置到装置(d2d)通信机制
TW201330569A (zh) * 2011-10-07 2013-07-16 Interdigital Patent Holdings 整合使用載波聚集不同無線電存取技術方法及裝置
US9883441B2 (en) 2011-11-10 2018-01-30 Nokia Technologies Oy Method and apparatus to route packet flows over two transport radios
US11588729B2 (en) * 2012-01-04 2023-02-21 Ofinno, Llc Cell site gateway
US20130195012A1 (en) * 2012-01-30 2013-08-01 Nokia Siemens Networks Oy Network attach procedure for long term evolution local area network
US9414223B2 (en) * 2012-02-17 2016-08-09 Nokia Technologies Oy Security solution for integrating a WiFi radio interface in LTE access network
WO2013123643A1 (fr) * 2012-02-21 2013-08-29 Nokia Siemens Networks Oy Interfaces de signalisation dans les communications
US9510387B2 (en) * 2012-05-04 2016-11-29 Nokia Technologies Oy Recovering connection in LTE local area network for EPS and local services
CN103582011A (zh) * 2012-07-26 2014-02-12 中兴通讯股份有限公司 一种进行多网络联合传输的***、用户设备及方法
WO2014047939A1 (fr) * 2012-09-29 2014-04-03 华为技术有限公司 Procédé et dispositif de répartition de données
US20190335551A1 (en) 2012-11-08 2019-10-31 Applied Biophotonics Ltd. Distributed Photobiomodulation Therapy Devices And Methods, Biofeedback, And Communication Protocols Therefor
US9686786B2 (en) * 2013-01-10 2017-06-20 Lg Electronics Inc. Method for updating base station information in converged network supporting multiple communication systems, and device therefor
WO2014110777A1 (fr) * 2013-01-18 2014-07-24 Broadcom Corporation Échange d'informations pour interréseautage cellulaire-non cellulaire
US10104540B2 (en) * 2013-01-23 2018-10-16 Qualcomm Incorporated Determining to use multi-RAN interworking by correlating different RAN identifiers
CN103974325B (zh) * 2013-01-31 2018-04-27 华为技术有限公司 多制式网络融合的方法、设备及***
CN110087272B (zh) * 2013-02-22 2021-10-08 三星电子株式会社 在多个e节点b和用户设备间提供同时连接的方法和***
US9474067B2 (en) * 2013-03-26 2016-10-18 Qualcomm Incorporated WLAN uplink scheduler for LTE-WLAN aggregation
US9538515B2 (en) * 2013-03-28 2017-01-03 Samsung Electronics Co., Ltd. Downlink signaling for adaptation of an uplink-downlink configuration in TDD communication systems
JP6105370B2 (ja) * 2013-04-25 2017-03-29 京セラ株式会社 ユーザ端末、セルラ基地局及びプロセッサ
US9642140B2 (en) * 2013-06-18 2017-05-02 Samsung Electronics Co., Ltd. Methods of UL TDM for inter-enodeb carrier aggregation
US9819469B2 (en) * 2013-07-01 2017-11-14 Qualcomm Incorporated Techniques for enabling quality of service (QoS) on WLAN for traffic related to a bearer on cellular networks
WO2015047237A1 (fr) * 2013-09-25 2015-04-02 Intel Corporation Tunnellisation de bout en bout (e2e) pour une technologie d'accès radio multiple (multi-rat)
US10757632B2 (en) * 2013-09-30 2020-08-25 Qualcomm Incorporated Public land mobile network identifier for non-mobile network operator networks
KR101918554B1 (ko) * 2013-12-17 2018-11-15 노키아 솔루션스 앤드 네트웍스 게엠베하 운트 코. 카게 소프트웨어 정의 네트워킹에서의 핸드오버
US20150189574A1 (en) * 2013-12-26 2015-07-02 Samsung Electronics Co., Ltd. Methods for dormant cell signaling for advanced cellular network
CN104812000A (zh) * 2014-01-27 2015-07-29 中兴通讯股份有限公司 一种实现数据传输的方法及装置
US11026136B2 (en) * 2014-03-07 2021-06-01 Parallel Wireless, Inc. Handovers with simplified network topology
US9596707B2 (en) * 2014-03-13 2017-03-14 Intel Corporation Bearer mobility and splitting in a radio access network-based, 3rd generation partnership project network having an integrated wireless local area network
US9788236B2 (en) * 2014-05-30 2017-10-10 Qualcomm Incorporated Interaction between WAN-WLAN interworking and WAN-WLAN aggregation
MX2017000004A (es) * 2014-06-30 2017-08-14 Interdigital Patent Holdings Inc Movilidad de flujo basada en red para dispositivos de conectividad multiple.
WO2016043513A1 (fr) * 2014-09-16 2016-03-24 엘지전자 주식회사 Procédé et dispositif pour émettre et recevoir un signal sans fil dans un système de communication sans fil
US10104705B2 (en) * 2014-11-05 2018-10-16 Intel IP Corporation Apparatus, system and method of communicating between a cellular manager and a user equipment (UE) via a WLAN access device
US10419942B2 (en) * 2014-11-28 2019-09-17 Lg Electronics Inc. Wireless signal transmission and reception method and device in wireless communication system involving a cell group including unlicensed band cells
WO2016090549A1 (fr) 2014-12-09 2016-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de résolution d'adresse
US10219310B2 (en) * 2014-12-12 2019-02-26 Alcatel Lucent WiFi boost with LTE IP anchor
US10708810B2 (en) * 2014-12-23 2020-07-07 Interdigital Patent Holdings, Inc. Methods for WiFi integration in cellular systems
US9794960B2 (en) * 2014-12-31 2017-10-17 Samsung Electronics Co., Ltd. Methods and apparatus for uplink channel access and transmissions for LTE on unlicensed spectrum
US11627639B2 (en) 2015-01-26 2023-04-11 Ievgen Verzun Methods and apparatus for HyperSecure last mile communication
US9998434B2 (en) 2015-01-26 2018-06-12 Listat Ltd. Secure dynamic communication network and protocol
US9781652B2 (en) * 2015-02-05 2017-10-03 Mediatek Inc. Method and apparatus of LWA PDU routing
CN107251644B (zh) * 2015-02-20 2022-06-03 富士通株式会社 无线通信***、基站和移动台
US20160255643A1 (en) 2015-02-27 2016-09-01 Qualcomm Incorporated Methods and apparatus for receiving lte-u network information
US10833892B2 (en) * 2015-03-05 2020-11-10 Blackberry Limited Bridged local area network communication between a device and a cellular access network node
JP2018512788A (ja) * 2015-03-10 2018-05-17 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． トラフィックフロー分割方法およびトラフィックフロー分割装置
US10869344B2 (en) * 2015-03-19 2020-12-15 Acer Incorporated Method of radio bearer transmission in dual connectivity
EP3281445A4 (fr) 2015-04-08 2018-11-21 LG Electronics Inc. Procédé pour faire fonctionner une nouvelle entité pour un système d'agrégation lte-wlan et dispositif associé
TW201941659A (zh) * 2015-04-08 2019-10-16 內數位專利控股公司 在風巢系統中無線區域網路(wlan)整合控制平面方法及裝置
US20200259896A1 (en) 2019-02-13 2020-08-13 Telefonaktiebolaget Lm Ericsson (Publ) Industrial Automation with 5G and Beyond

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011503914A (ja) * 2007-05-04 2011-01-27 株式会社東芝 多重インターフェースの同時使用のためのインテリジェントコネクティビティフレームワーク
JP2014003644A (ja) * 2008-06-09 2014-01-09 Qualcomm Incorporated デュアルアクセスネットワークのネットワークベース制御
JP2014027548A (ja) * 2012-07-27 2014-02-06 Fujitsu Ltd 基地局装置、無線端末装置及びパケット振分け方法

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018078987A1 (fr) * 2016-10-31 2018-05-03 日本電気株式会社 Entité de gestion de mobilité, entité de réseau, procédés associés, et support lisible par ordinateur
US11116029B2 (en) 2016-10-31 2021-09-07 Nec Corporation Mobility management entity, network entity, and method and computer readable medium therefor
WO2018136422A3 (fr) * 2017-01-18 2018-09-27 Qualcomm Incorporated Techniques de gestion de flux de protocole internet dans une architecture de couche 2 d'un dispositif sans fil
US10432761B2 (en) 2017-01-18 2019-10-01 Qualcomm Incorporated Techniques for handling internet protocol flows in a layer 2 architecture of a wireless device
US20180288647A1 (en) * 2017-03-29 2018-10-04 Nanning Fugui Precision Industrial Co., Ltd. Wireless communication system and method
CN108668299A (zh) * 2017-03-29 2018-10-16 南宁富桂精密工业有限公司 无线通信***及方法
CN108668299B (zh) * 2017-03-29 2021-07-13 南宁富桂精密工业有限公司 无线通信***及方法
JP2022528541A (ja) * 2019-04-08 2022-06-14 華為技術有限公司 データ送信方法および装置、ならびにコンピュータ可読記憶媒体
JP7177287B2 (ja) 2019-04-08 2022-11-22 華為技術有限公司 データ送信方法および装置、ならびにコンピュータ可読記憶媒体
JPWO2021033268A1 (fr) * 2019-08-20 2021-02-25
WO2021033268A1 (fr) * 2019-08-20 2021-02-25 富士通株式会社 Dispositif de station de base, dispositif de relai et système de communication
JP7401794B2 (ja) 2019-08-20 2023-12-20 富士通株式会社 基地局装置、中継装置、及び通信システム

Also Published As

Publication number Publication date
RU2682420C1 (ru) 2019-03-19
JP2017175668A (ja) 2017-09-28
EP3282747A4 (fr) 2018-02-28
US11690092B2 (en) 2023-06-27
MX2017012980A (es) 2017-11-28
CN116744247A (zh) 2023-09-12
JP6521156B2 (ja) 2019-05-29
US20220394724A1 (en) 2022-12-08
JPWO2016163036A1 (ja) 2017-08-17
JP6365740B2 (ja) 2018-08-01
WO2016163032A1 (fr) 2016-10-13
EP3282747B1 (fr) 2023-08-23
US11737128B2 (en) 2023-08-22
CA2982804A1 (fr) 2016-10-13
CA2982804C (fr) 2019-12-17
EP3282747A1 (fr) 2018-02-14
US20180035440A1 (en) 2018-02-01
JP6172419B2 (ja) 2017-08-02
KR102052466B1 (ko) 2019-12-05
US20190230676A1 (en) 2019-07-25
KR20170127536A (ko) 2017-11-21
MX360887B (es) 2018-11-20
BR112017021425A2 (pt) 2018-07-03
JP2018152920A (ja) 2018-09-27
CN107534898A (zh) 2018-01-02

Similar Documents

Publication Publication Date Title
JP6365740B2 (ja) 無線通信システム、移動局、無線局および通信方法
US11432346B2 (en) Wireless communications system, base station, and mobile station
US11102832B2 (en) Method and wireless communication system for handling offloading of DRBs to WLAN carrier
US9781652B2 (en) Method and apparatus of LWA PDU routing
Ohta et al. Link layer structure for LTE-WLAN aggregation in LTE-Advanced and 5G network
JP6551461B2 (ja) 無線通信システム、無線通信装置および無線通信装置の制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15888527

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017511445

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2982804

Country of ref document: CA

REEP Request for entry into the european phase

Ref document number: 2015888527

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2017134998

Country of ref document: RU

WWE Wipo information: entry into national phase

Ref document number: MX/A/2017/012980

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 20177028778

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017021425

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112017021425

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20171005