WO2016161915A1 - 数据无线承载配置方法、数据传输方法及设备 - Google Patents

数据无线承载配置方法、数据传输方法及设备 Download PDF

Info

Publication number
WO2016161915A1
WO2016161915A1 PCT/CN2016/078310 CN2016078310W WO2016161915A1 WO 2016161915 A1 WO2016161915 A1 WO 2016161915A1 CN 2016078310 W CN2016078310 W CN 2016078310W WO 2016161915 A1 WO2016161915 A1 WO 2016161915A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
access device
entity
data packet
protocol
Prior art date
Application number
PCT/CN2016/078310
Other languages
English (en)
French (fr)
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
Application filed by 电信科学技术研究院 filed Critical 电信科学技术研究院
Publication of WO2016161915A1 publication Critical patent/WO2016161915A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • the present disclosure relates to the field of wireless communications, and in particular, to a data radio bearer configuration method, a data transmission method, and a device.
  • the protocol layer of the Long Term Evolution (LTE) system includes the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer from top to bottom.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the Media Access Control (MAC) layer and the Physical (PHY) layer; from the control plane, the Radio Resource Control (RRC) layer on the PDCP layer is also included.
  • MAC Media Access Control
  • PHY Physical
  • RRC Radio Resource Control
  • the eNB After the user equipment (UE), that is, the terminal accesses the network and establishes a connection with the evolved NodeB (eNB), that is, the base station, the eNB configures multiple radio bearers to the UE by using the RRC message.
  • the radio bearers are classified into a Data Radio Bearer (DRB) and a Signaling Radio Bearer (SRB) according to their functions.
  • DRB Data Radio Bearer
  • SRB Signaling Radio Bearer
  • the data of the DRB comes from the core network (Core Network, CN), and the PDCP layer is layer by layer to the physical layer.
  • the data of the SRB comes from the eNB, and the PDCP layer is layer by layer to the physical layer.
  • the eNB finally passes the signal of the physical layer to the information. Send to the UE.
  • the UE reversely parses the data of the eNB through its own PDCP layer, RLC layer, MAC layer, and physical layer.
  • the PDCP layer sends data to the data receiving entity of the UE, such as an application.
  • the UE may packetize its own data from the PDCP layer to the physical layer, and send the signal to the eNB through the physical layer.
  • Figure 1 shows a user plane protocol stack in an LTE system.
  • the connection of the UE on the MeNB may have an independent bearer, and the connection on the SeNB is to transmit a part of data carried by the same Evolved Packet System (EPS) on the MeNB to the SeNB for transmission.
  • EPS Evolved Packet System
  • the EPS bearer PDCP entity is still in the MeNB, and the SeNB has an independent RLC entity.
  • EPS is a system that supports multiple access technologies and mobility between multiple accesses.
  • the terminal may be under common coverage of multiple 3rd Generation Partnership Projects (3GPPs) and/or non-3GPP access networks.
  • 3GPPs 3rd Generation Partnership Projects
  • These access networks may use different access technologies, may belong to different operators, or may provide access to different core networks.
  • FIG. 3 is a scenario in which a typical Universal Mobile Telecommunications System (UMTS)/LTE and WLAN network coexist.
  • UMTS Universal Mobile Telecommunications System
  • FIG. 2 in a coverage area of a UMTS/LTE base station (Node B in UMTS, eNB in LTE), there are multiple WLAN access points (APs). The coverage of the access point is relatively small compared to the base station.
  • the embodiment of the present disclosure provides a data radio bearer configuration method, a data transmission method, and a device thereof, to implement offloading of user plane data on one access device side on another access device side.
  • the first access device obtains capability information of the terminal, where the capability information is used to indicate that the terminal supports the user plane data offload transmission;
  • the first access device requests the terminal to configure, between the terminal and the first access device, according to the capability information of the terminal and the second access device that performs data offloading for the terminal.
  • a data radio bearer (DRB) of the second access device wherein the first access device and the second access device support different access technologies;
  • the bearer channel of the DRB is established between the first access device and the terminal.
  • the terminal reports the capability information of the terminal to the first access device, where the capability information is used to indicate that the terminal supports the user plane data offload transmission;
  • the terminal receives the configuration request sent by the first access device, where the configuration request is used to request the terminal to configure data wirelessly disconnected between the terminal and the first access device via the second access device.
  • a bearer DRB
  • the first access device and the second access device support different access modes
  • the bearer channel of the DRB is established between the terminal and the first access device.
  • the first access device receives the user plane data from the core network, and sends the user plane data to the terminal by using a bearer channel of the DRB of the second access device with the terminal, where the An access device and a second access device use different access technologies; and/or,
  • the first access device receives user plane data from the terminal through the bearer channel, and sends the user plane data to the core network.
  • the terminal sends the user plane data to the first access device by using a bearer channel between the first receiving device and the DRB of the second access device, where the first access device and the second access device
  • the device uses different access technologies; and/or,
  • the terminal receives user plane data from the first access device through the bearer channel.
  • An obtaining module configured to obtain capability information of the terminal, where the capability information is used to indicate that the terminal supports the user plane data offload transmission;
  • a bearer configuration requesting module configured to request the terminal to configure, between the terminal and the first access device, according to the capability information of the terminal and the second access device used for data offloading the terminal a data radio bearer (DRB) of the second access device; wherein the first access device and the second access device support different access technologies;
  • DRB data radio bearer
  • the bearer configuration module is configured to establish a bearer channel of the DRB with the terminal.
  • the reporting module is configured to report the capability information of the terminal to the first access device, where the capability information is used to indicate that the terminal supports the user plane data offload transmission;
  • a bearer configuration receiving module configured to receive a configuration request sent by the first access device, where the configuration request is used to request the terminal to configure the second access device between the terminal and the first access device a split data radio bearer (DRB); wherein the first access device and the second access device support different access modes;
  • DRB split data radio bearer
  • the bearer configuration module is configured to establish a bearer channel of the DRB with the first access device.
  • Some embodiments of the present disclosure provide an access device including a processor, a transceiver, and a memory;
  • the processor is configured to read a computer readable program in the memory to perform the following operations:
  • Obtaining capability information of the terminal where the capability information is used to indicate that the terminal supports the user plane data offload transmission;
  • DRB Data radio bearer
  • the transceiver is configured to receive and transmit data
  • the memory is used to store data used by the processor to perform operations.
  • Some embodiments of the present disclosure provide a terminal including a processor, a transceiver, and a memory;
  • the processor is configured to read a computer readable program in the memory to perform the following operations:
  • DRB data radio bearer
  • the transceiver is configured to receive and transmit data
  • the memory is used to store data used by the processor to perform operations.
  • the first access device and the second access device support different access modes.
  • the terminal reports the support capability information of the user plane data offloading to the first access device, so that the first access device configures the terminal to establish a DRB bearer channel with the first access device according to the capability information of the terminal,
  • the bearer channel is transmitted through the second access device, so that the terminal and the first access device can perform user plane data transmission through the bearer channel, that is, the user plane data between the terminal and the first access device is passed.
  • the second access device performs the purpose of offloading.
  • FIG. 1 is a schematic diagram of a user plane protocol stack of an LTE system in related art
  • FIG. 2 is a schematic diagram of an LTE dual connectivity architecture in the related art
  • FIG. 3 is a schematic diagram of a scenario in which a UMTS/LTE and a WLAN network coexist in the related art
  • FIG. 4 is a schematic diagram of a DRB configuration process implemented by a network side according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a DRB configuration process implemented by a terminal side according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of data offload transmission in a downlink direction according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of data offload transmission in an uplink direction according to an embodiment of the present disclosure.
  • FIG. 8A is a schematic structural diagram of a user plane protocol stack according to Embodiment 1 of the present disclosure.
  • FIG. 8B and FIG. 8C are schematic diagrams of downlink data transmission and reception according to Embodiment 1 of the present disclosure.
  • FIG. 8D and FIG. 8E are schematic diagrams of uplink data transmission and reception according to Embodiment 1 of the present disclosure.
  • FIG. 9A is a schematic diagram of downlink data transmission according to Embodiment 2 of the present disclosure.
  • FIG. 9B is a schematic diagram of uplink data reception according to Embodiment 2 of the present disclosure.
  • 10A is a schematic structural diagram of a user plane protocol stack according to Embodiment 3 of the present disclosure.
  • FIG. 10B and FIG. 10C are schematic diagrams of downlink data transmission and reception according to Embodiment 3 of the present disclosure.
  • FIG. 10D and FIG. 10E are schematic diagrams of uplink data transmission and reception according to Embodiment 3 of the present disclosure.
  • 11A is a schematic structural diagram of a user plane protocol stack according to Embodiment 4 of the present disclosure.
  • FIG. 11B and FIG. 11C are schematic diagrams of downlink data transmission and reception according to Embodiment 4 of the present disclosure.
  • FIG. 11D and FIG. 11E are schematic diagrams of uplink data transmission and reception according to Embodiment 4 of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a user plane protocol stack according to Embodiment 5 of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a user plane protocol stack according to Embodiment 6 of the present disclosure.
  • FIG. 14 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a network device according to another embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of a terminal according to another embodiment of the present disclosure.
  • a data radio bearer configuration method is proposed, and a data transmission method based on the configured radio bearer is implemented to implement an access device side.
  • the user plane data is offloaded on the other access device side.
  • the scenario in which the LTE and the WLAN are in common is used to perform the method of controlling the user plane data of the UE to be flexibly transmitted on the LTE and the WLAN side, and the LTE bearer data and the WLAN bearer data may be concurrently implemented, and the WLAN is not modified. Diversion of data carried by LTE over WLAN in the case of an AP Sending, effectively utilizing traditional WLAN APs, improves the efficiency of splitting and the flexibility of deployment.
  • FIG. 4 is a schematic diagram of a DRB configuration process implemented by a network side according to an embodiment of the present disclosure.
  • the process may be implemented by a network side device.
  • the process can include the following steps:
  • Step 401 The first access device obtains capability information of the terminal, where the capability information is used to indicate that the terminal supports the user plane data offload transmission.
  • Step 402 The first access device requests the terminal to configure the terminal and the first access device according to the capability information of the terminal and the second access device that performs data offloading for the terminal. a DRB that is offloaded by the second access device; wherein the first access device and the second access device support different access technologies;
  • Step 403 The bearer channel of the DRB is established between the first access device and the terminal.
  • FIG. 5 shows a DRB configuration process implemented by the terminal side, and the process may include the following steps:
  • Step 501 The terminal reports the capability information of the terminal to the first access device, where the capability information is used to indicate that the terminal supports the user plane data offload transmission.
  • Step 502 The terminal receives the configuration request sent by the first access device, where the configuration request is used to request the terminal to configure the terminal to be offloaded between the terminal and the first access device by using the second access device. a DRB; wherein the first access device and the second access device support different access modes;
  • Step 503 The bearer channel of the DRB is established between the terminal and the first access device.
  • the first access device may be a base station in LTE or its evolved system, and the second access device may be an AP in a WLAN.
  • the capability information sent by the terminal to the first access device may include one of the following contents: Or any combination:
  • protocol type indication information is used to indicate a protocol used by the terminal to establish the bearer channel
  • the terminal supports the indication information that the user plane data is offloaded via the second access device.
  • the capability information may further include: information about a port that the terminal has occupied, and/or information about a port that the terminal recommends to use.
  • the information that is sent by the first access device to the terminal for instructing the terminal to configure the DRB may include one or any combination of the following:
  • protocol type indication information is used to indicate a protocol used by the terminal to establish the bearer channel
  • the configuration information of the bearer channel includes: at least: a correspondence between a PDCP entity and a logical channel identifier in the bearer channel;
  • the identifier of the DRB is the identifier of the DRB.
  • the protocol used for establishing the bearer channel may include one of the following: an Internet Protocol (IP), a Transmission Control Protocol (TCP), a User Datagram Protocol (UDP), and a User Area General Packet Radio Service Protocol (GTP-U).
  • IP Internet Protocol
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • GTP-U User Area General Packet Radio Service Protocol
  • HTTP Hypertext Transfer Protocol
  • HTTPS Hypertext Transfer Security Protocol
  • the configuration information of the bearer channel may further include: port information of the TCP or UDP connection.
  • the first access device may further confirm the location according to the capability information of the terminal before the terminal configures the DRB.
  • the LC entity corresponding to the terminal is allocated a TCP or UDP port, and the DRB of the terminal is configured with an LC entity.
  • the first access device may also allocate a TCP or UDP port to the LC entity in advance.
  • the configuration information of the carrying channel further includes an identifier of the terminal, where multiple DRB bearers of the terminal are configured with one LC entity.
  • the first access device may further confirm, according to the capability information of the terminal, before instructing the terminal to configure the DRB.
  • the terminal supports the user plane data to be offloaded by the second access device, and allocates a corresponding TCP or UDP port to the DRB corresponding to the terminal that needs to be offloaded by the second access device.
  • the configuration information of the bearer channel further includes: identifier information of the terminal.
  • the terminal and the second access device are connected by an air interface GTP-U established by using the GTP-U protocol, and the configuration information of the bearer channel further includes: the terminal and the The configuration information of the air interface GTP-U connection between the second access devices.
  • the configuration information of the bearer channel further includes: between the terminal and the second access device The configuration information of the air interface UDP or TCP link.
  • the UDP or TCP connection uniquely corresponds to the terminal, or uniquely corresponds to a DRB of the terminal that needs to be offloaded by the second access device.
  • the configuration information of the bearer channel further includes: an air interface between the terminal and the second access device Configuration information of the IP connection.
  • the GTP-U connection configuration information includes:
  • the protocol type indication information where the protocol indicated by the protocol type indication information is a GTP-U protocol;
  • Configuration information of the air interface GTP-U connection between the terminal and the second access device and configuration information of the GTP-U connection between the first access device and the second access device;
  • the identifier of the DRB is the identifier of the DRB.
  • the bearer channel includes a downlink channel and/or an uplink channel.
  • the user plane data can be offloaded by the second access device through the bearer channel.
  • the first access device receives user plane data from the core network, and passes the user plane data through the DRB of the second access device with the terminal.
  • the bearer channel is sent to the terminal, and the terminal receives user plane data from the first access device through the bearer channel.
  • the dotted line in FIG. 6 indicates that the downlink data sent by the first access device can be transmitted through the wireless link with the terminal while being transmitted by the second access device.
  • the terminal sends the user plane data to the first access device by using a bearer channel between the first receiving device and the DRB of the second access device, where An access device receives user plane data from the terminal through the bearer channel, and sends the user plane data to the core network.
  • the dotted line in FIG. 7 indicates that the uplink data sent by the terminal can be transmitted through the wireless link with the first access device while being transmitted by the second access device.
  • the first access device and the second access device support different access modes.
  • the terminal reports the support capability information of the user plane data offloading to the first access device, so that the first access device configures the terminal to establish a DRB bearer channel with the first access device according to the capability information of the terminal,
  • the bearer channel is transmitted through the second access device, so that the terminal and the first access device can perform user plane data transmission through the bearer channel, that is, the user plane data between the terminal and the first access device is passed.
  • the second access device performs the purpose of offloading.
  • the configuration process of the bearer channel and the process of data offload transmission through the bearer channel are also different according to the protocol used to establish the bearer channel.
  • the configuration process of the bearer channel established by different protocols and the data offload transmission process performed by the bearer channel will be described in detail below with reference to specific embodiments.
  • the first embodiment describes a scheme for establishing a bearer channel of a DRB between a UE and an eNB by using a TCP protocol, so as to implement a scheme for offloading user plane data between an eNB and a UE by using a WLAN AP.
  • the LTE wireless communication protocol is used for interaction between the UE and the eNB
  • the Wi-Fi wireless communication protocol is used for interaction between the UE and the WLAN AP
  • the eNB and the WLAN AP are connected by wire, and the cable is used.
  • the communication protocol interacts.
  • FIG. 8A is a user plane protocol stack architecture corresponding to the first embodiment.
  • the LTE protocol stack in the UE includes a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from an upper layer to a lower layer;
  • the Wi-Fi protocol stack in the UE includes a TCP layer, an IP layer, and a MAC/PHY layer from an upper layer to a lower layer;
  • the eNB's LTE protocol stack includes a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from the upper layer to the lower layer;
  • the eNB's wired communication protocol stack includes a TCP layer, an IP layer, and a data link layer from the upper layer to the lower layer (shown as Layer-2).
  • the UE1 and the UE2 that access the eNB are respectively configured with an LC entity (ie, a logical channel entity).
  • UE1 and UE2 are respectively configured with two EPS bearers, and the corresponding PDCP entities of the two EPS bearers are respectively represented as PDCP1 and PDCP2.
  • Both the UE1 and the UE2 support the user plane data offloading. Therefore, the corresponding LC entity of the two UEs is assigned a TCP port number, and the TCP port number assigned to the LC entity corresponding to the UE1 is represented as Port1, which is allocated for the LC entity corresponding to the UE2.
  • the TCP port is represented as Port2.
  • the correspondence between the PDCP entity and the logical channel identifier is: PDCP1 corresponds to LC1, and PDCP2 corresponds to LC2.
  • the signaling process of configuring the DRB between the UE and the eNB via the WLAN AP may specifically include the following:
  • Step 1 The UE reports the capability information of the UE to the eNB, and the capability information may indicate the UE's support capability for the user plane data offload transmission.
  • the capability information may include the following content:
  • the protocol type indication information indicates the protocol used by the UE to establish a DRB bearer channel; in this embodiment, the protocol type is TCP;
  • the address of the UE such as the IP address of the UE
  • the indication information may be identification information of one bit or multiple bits, and indicates whether the UE supports the offloading of the user plane data via the WLAN AP by using different values.
  • the indication information indicates that the UE supports the user plane data via the WLAN AP. Diversion
  • the port list may specifically include a list of ports that the UE has occupied, and/or a list of ports recommended by the UE.
  • Step 2 The eNB configures the UE to measure the WLAN AP.
  • Step 3 The UE measures the WLAN AP according to the configuration of the eNB, and reports the measurement result, where the measurement result includes information such as the identifier of the WLAN AP measured by the UE.
  • Step 4 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and if the WLAN AP measured by the UE is obtained, sends a reconfiguration message to the UE to request the UE to configure the UE to communicate with the eNB. DRB of the WLAN AP.
  • the reconfiguration message may include the following content:
  • the TCP protocol type indication information is used to indicate that the UE establishes a bearer channel of the DRB by using the TCP protocol;
  • the configuration information of the bearer channel of the DRB that is, the configuration information required to establish the bearer channel of the DRB; specifically, the address of the eNB, the TCP port number, and the PDCP entity and the LCID (Logic Channel ID, logic) in the DRB channel.
  • Information about the correspondence between the channel identifiers and the like; wherein, a TCP port number identifies a TCP channel between the LC entity and the TCP entity; in this embodiment, the UE that supports the user plane data to be shunted via the WLAN AP may be allocated.
  • the UE uniquely corresponds to a TCP port number;
  • the identifier of the DRB that needs to be reconfigured in this embodiment, the identifier of the DRB between the UE and the eNB via the WLAN AP;
  • the other configuration information may include one or a combination of the following: information of a PDCP entity, a logical channel identifier (LCID), logical channel configuration information, information of a MAC entity, information of a physical layer entity, and the like.
  • a PDCP entity a logical channel identifier
  • LCID logical channel identifier
  • MAC entity information of a MAC entity
  • physical layer entity information of a physical layer entity
  • Step 5 After receiving the reconfiguration message sent by the eNB, the UE passes the configuration information according to the configuration information.
  • the WLAN access network initiates a connection setup request to the eNB.
  • the UE may feedback the response information of the DRB configuration, or feed back to the eNB for the occupied or recommended use of the UE.
  • a list of ports if the TCP port number in the configuration information received by the UE conflicts with the port number used by other applications, the UE may feedback the response information of the DRB configuration, or feed back to the eNB for the occupied or recommended use of the UE.
  • Step 6 The UE establishes a bearer channel based on the TCP protocol between the WLAN AP and the eNB.
  • the UE may notify the eNB of the information that the bearer channel establishment fails.
  • the eNB may be configured to perform the WLAN AP measurement and the WLAN AP measurement result reported by the UE, and the UE may directly report the information of the available WLAN AP and the information measured by the UE to the eNB.
  • the UE may send user plane data to the eNB through the bearer channel. If the bearer channel connection fails during the data transmission process, the UE may notify the eNB of the bearer channel connection failure information.
  • the user plane data offload transmission process between the UE and the eNB can be as shown in FIGS. 8B and 8C and FIGS. 8D and 8E.
  • 8B and FIG. 8C respectively show the user plane data transmission flow in the downlink direction implemented on the eNB side and the UE side
  • FIG. 8D and FIG. 8E respectively show the uplink direction implemented on the eNB side and the UE side.
  • the user plane data transmission process in the downlink direction implemented by the eNB side may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 PDCP1 in the eNB receives data packets from higher layers, such as PDCP PDUs.
  • Step 2 PDCP1 processes the received data packet, and sends the processed data packet to the LC entity corresponding to the PDCP.
  • Step 3 The LC entity processes the received data packet, maps the processed data packet to a logical channel, and adds an LCID (the value of the LCID is represented as LC1), the added LCID corresponds to PDCP1, and the LC entity is allocated according to the allocation.
  • the TCP port Port1 sends the processed data packet to the TCP entity through the corresponding TCP channel.
  • Step 4 The TCP entity encapsulates the received data packet, obtains a TCP data packet, and sends the TCP data packet to the IP entity.
  • Step 5 The IP entity encapsulates the received TCP packet, obtains an IP packet, and sends the IP packet to the WLAN AP through IP routing.
  • the IP data packet sequentially passes through a data link layer entity and a physical layer entity in the eNB.
  • the IP data packet sent by the eNB sequentially passes through a physical layer entity, an LLC entity, a MAC entity, an IP entity in the wired communication protocol stack, and an IP entity and a MAC/PHY entity in the Wi-Fi wireless communication protocol stack. Send to the UE.
  • the process of the UE may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 The data link layer entity (shown as WLAN MAC+PHY+LLC) in the Wi-Fi wireless communication protocol stack in the UE sends the received data packet to the IP entity.
  • the data link layer entity shown as WLAN MAC+PHY+LLC
  • Step 2 The IP entity decapsulates and parses the received data packet, and sends the processed data packet to the TCP entity according to the protocol type.
  • Step 3 The TCP entity sends the received data packet to the LC entity through the corresponding TCP channel according to the TCP port number Port1 allocated to the LC entity of the UE.
  • the TCP entity may also send the received data packet to the LC entity through the corresponding TCP channel according to the TCP port number allocated for the adaptation layer entity.
  • the adaptation layer refers to a protocol layer used to send a PDCP layer data packet to an LC layer or to send an LC layer data packet to a PDCP layer.
  • Step 4 The LC entity sends the received data packet to the corresponding PDCP entity according to the LCID in the header of the received data packet and the correspondence between the LCID and the PDCP entity: PDCP1.
  • Step 5 PDCP1 sends the received data packet to the IP entity.
  • Step 6 The IP entity sends the received data packet to the TCP entity according to the protocol type.
  • Step 7 The TCP entity sends the TCP packet to the application layer entity (shown as APP1 in the figure) through the TCP channel corresponding to the TCP port according to the TCP port number Port2 allocated for the application.
  • the application layer entity shown as APP1 in the figure
  • the flow described in FIG. 8B and FIG. 8C described above only describes the transmission process of user plane data in the downlink direction through the WLAN AP.
  • the user plane data in the downlink direction between the eNB and the UE may be transmitted to the UE through the WLAN AP, or part of the data may be offloaded to the UE through the WLAN AP, and another part of the data still passes through the LTE between the eNB and the UE.
  • the communication link of the protocol is sent to the UE, so that the concurrent transmission of the LTE bearer data and the WLAN bearer data can be implemented.
  • the process of the eNB transmitting downlink data to the UE through the communication link of the LTE protocol and the related protocol stack architecture can be referred to the LTE protocol.
  • the sending process of the user plane data in the uplink direction implemented on the UE side may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 The application layer entity (APP1 shown in the figure) sends the data packet to the TCP entity through the corresponding TCP channel according to the assigned TCP port number Port2.
  • Step 2 The TCP entity processes the received data packet and sends the processed data packet to the IP entity.
  • Step 3 The IP entity sends the data packet to the corresponding PDCP1 according to the IP header of the received data packet.
  • Step 4 PDCP1 processes the received data packet and sends the processed data packet to the LC entity.
  • Step 5 The LC entity processes the received data packet, maps the processed data packet to a logical channel, and adds an LCID (the value of the LCID is expressed as LC1), according to the TCP port number Port1 allocated for the LC entity.
  • the processed data packet is sent to the TCP entity through the corresponding TCP channel.
  • Step 6 The TCP entity processes the received data packet and sends the processed data packet to the IP entity.
  • Step 7 The IP entity processes the received data packet, and sends the processed data packet to the data link layer entity (shown as WLAN MAC+PHY+LLC) entity in the Wi-Fi wireless communication protocol stack. .
  • the data packet passes through the data link layer entity and the physical layer entity in the UE in sequence.
  • the IP data packet sent by the UE sequentially passes through the data link layer entity, the IP entity in the Wi-Fi wireless communication protocol stack, and the IP entity and the MAC/PHY entity in the wired communication protocol stack. Send to the eNB.
  • the processing flow after the eNB receives the user plane data may be as shown by a thick solid line in the figure, and includes the following steps:
  • Step 1 The IP entity processes the data packet received from the WLAN AP, and sends the processed data packet to the TCP entity according to the protocol type.
  • Step 2 The TCP entity sends the received data packet to the corresponding LC entity through the corresponding TCP channel according to the TCP port number Port1 allocated for the LC entity.
  • Step 3 The LC entity processes the data packet, and sends the processed data packet to the LCID in the packet header of the received data packet (the LCID value is represented as LC1) and the correspondence between the LCID and the PDCP entity. Corresponding PDCP1.
  • Step 4 PDCP1 processes the received data packet and sends the processed data packet to the upper layer.
  • the flow described in FIG. 8D and FIG. 8E described above only describes the transmission process of user plane data in the uplink direction through the WLAN AP.
  • the user plane data in the uplink direction between the eNB and the UE may be transmitted to the eNB through the WLAN AP, or part of the data may be offloaded to the eNB through the WLAN AP, and another part of the data still passes through the LTE between the eNB and the UE.
  • the communication link of the protocol is sent to the eNB, so that the concurrent transmission of the LTE bearer data and the WLAN bearer data can be implemented.
  • the process of the UE transmitting uplink data to the eNB through the communication link of the LTE protocol and the related protocol stack architecture can be referred to the LTE protocol.
  • the first embodiment is described by taking a TCP connection between a UE and an eNB and via a WLAN AP as a TCP connection.
  • the bearer channel may also be replaced by a UDP connection. If the bearer channel is a UDP connection, The process of the bearer channel configuration process and the data offloading process may reuse the above process, except that the UDP protocol type is specified in step 4 of the signaling configuration flow of the bearer channel, and refers to The port number of the UDP protocol.
  • a UDP connection is established between the subsequent UE and the network side and data can be sent and received through the UDP port.
  • the second embodiment describes a scheme for establishing a bearer channel of a DRB by using a TCP protocol to implement splitting of user plane data between an eNB and a UE by using a WLAN AP.
  • the user plane protocol stack architecture of the second embodiment is the same as that of the first embodiment. For details, refer to FIG. 8A.
  • the UE1 and the UE2 that access the eNB share an LC entity and share a TCP port.
  • the port number of the TCP port is represented as Port1.
  • UE1 and UE2 are respectively configured with two EPS bearers, and the corresponding PDCP entities of the two EPS bearers are respectively represented as PDCP1 and PDCP2.
  • Both UE1 and UE2 support user plane data offloading.
  • the correspondence between the PDCP entity and the logical channel identifier is: PDCP1 corresponds to LC1, and PDCP2 corresponds to LC2.
  • the signaling process of configuring the DRB between the UE and the eNB via the WLAN AP may specifically include the following:
  • Step 1 The UE reports the capability information of the UE to the eNB, and the capability information may indicate that the UE supports the user plane data by using the WLAN AP for offload transmission.
  • the capability information For the content that can be included in the capability information, refer to the related description in Embodiment 1.
  • Step 2 The eNB configures the UE to measure the WLAN AP.
  • Step 3 The UE measures the WLAN AP according to the configuration of the eNB, and reports the measurement result, where the measurement result includes information such as the identifier of the WLAN AP measured by the UE.
  • Step 4 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and if the WLAN AP measured by the UE is obtained, sends a reconfiguration message to the UE to request the UE to configure the UE to communicate with the eNB. DRB of the WLAN AP.
  • DRB of the WLAN AP For the content that can be included in the reconfiguration message, refer to the related description in Embodiment 1.
  • the TCP port number allocated to the UE is also shared by the UEs.
  • the TCP port number can be statically allocated by the eNB, that is, pre-allocated.
  • UEs based on all access eNBs share a TCP port number, so the reconfiguration is required
  • the set message includes the identifier information of the UE, so that the eNB distinguishes uplink data from different UEs according to the identifier information of the UE.
  • Step 5 After receiving the reconfiguration message sent by the eNB, the UE initiates a connection establishment request to the eNB through the WLAN access network according to the configuration information therein.
  • the UE may feedback the response information of the DRB configuration, or feed back to the eNB for the occupied or recommended use of the UE.
  • a list of ports if the TCP port number in the configuration information received by the UE conflicts with the port number used by other applications, the UE may feedback the response information of the DRB configuration, or feed back to the eNB for the occupied or recommended use of the UE.
  • Step 6 The UE establishes a bearer channel based on the TCP protocol between the WLAN AP and the eNB.
  • the UE may notify the eNB of the information that the bearer channel establishment fails.
  • the eNB may be configured to perform the WLAN AP measurement and the WLAN AP measurement result reported by the UE, and the UE may directly report the information of the available WLAN AP and the information measured by the UE to the eNB.
  • the UE may send user plane data to the eNB through the bearer channel. If the bearer channel connection fails during the data transmission process, the UE may notify the eNB of the bearer channel connection failure information.
  • the same LC entity is configured for UE1 and UE2 that access the eNB.
  • UE1 and UE2 are respectively configured with two EPS bearers, and the corresponding PDCP entities of the two EPS bearers are respectively represented as PDCP1 and PDCP2.
  • Both UE1 and UE2 support user plane data offloading, and UE1 and UE2 share the same TCP port number Port1.
  • the correspondence between the PDCP entity and the logical channel identifier is: PDCP1 corresponds to LC1, and PDCP2 corresponds to LC2.
  • the process of the eNB transmitting the downlink data is as shown in FIG. 9A; the process of the UE receiving the downlink data is the same as the related process in the first embodiment.
  • FIG. 8C The process of sending the uplink data by the UE and the related process in the first embodiment are basically For example, the process shown in FIG. 8D is different from the process shown in FIG. 8D.
  • step 5 before the LC entity sends the data packet to the TCP entity, the identifier information of the UE needs to be added in the data packet;
  • the process of receiving uplink data can be as shown in FIG. 9B. Only below in conjunction with Figure 9A FIG. 9B and FIG. 9B describe the processing procedure on the eNB side. For the processing procedure on the UE side, refer to the first embodiment, which is not repeated here.
  • the process for the eNB to send downlink data may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 PDCP1 in the eNB receives data packets from higher layers, such as PDCP PDUs.
  • Step 2 PDCP1 processes the received data packet and sends the processed data packet to the LC entity shared with all accessing UEs.
  • Step 3 The LC entity processes the received data packet, maps the processed data packet to a logical channel, and adds an LCID (the value of the LCID is represented as LC1), the added LCID corresponds to PDCP1, and the LC entity is based on multiple The TCP port Port1 shared by the UE sends the processed data packet to the TCP entity through the corresponding TCP channel.
  • Step 4 The TCP entity encapsulates the received data packet, obtains a TCP data packet, and sends the TCP data packet to the IP entity.
  • Step 5 The IP entity encapsulates the received TCP packet, obtains an IP data packet, and sends the IP data packet to the WLAN AP by using an IP route.
  • the IP data packet sequentially passes through a data link layer entity and a physical layer entity in the eNB.
  • the above figure flow only describes the transmission process of user plane data in the downlink direction through the WLAN AP.
  • the user plane data in the downlink direction between the eNB and the UE may be transmitted to the UE through the WLAN AP, or part of the data may be offloaded to the UE through the WLAN AP, and another part of the data still passes through the LTE between the eNB and the UE.
  • the communication link of the protocol is sent to the UE, so that the concurrent transmission of the LTE bearer data and the WLAN bearer data can be implemented.
  • the process of the eNB transmitting downlink data to the UE through the communication link of the LTE protocol and the related protocol stack architecture can be referred to the LTE protocol.
  • the process for the eNB to receive the uplink data may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 The IP entity processes the data packet received from the WLAN AP, and sends the processed data packet to the TCP entity.
  • Step 2 The TCP entity sends the received data packet to the LC entity shared by multiple UEs through the corresponding TCP channel according to the TCP port number Port1 shared by multiple UEs.
  • Step 3 The LC entity processes the data packet according to the identifier information of the UE in the packet header of the received data packet, and the LCID (the value of the LCID is represented as LC1), the correspondence between the LCID and the PDCP entity, and the processing is performed.
  • the data packet is sent to the PDCP1 corresponding to the UE.
  • Step 4 PDCP1 processes the received data packet and sends the processed data packet to the upper layer.
  • the foregoing process only describes the transmission process of user plane data in the uplink direction through the WLAN AP.
  • the user plane data in the uplink direction between the eNB and the UE may be transmitted to the eNB through the WLAN AP, or part of the data may be offloaded to the eNB through the WLAN AP, and another part of the data still passes through the LTE between the eNB and the UE.
  • the communication link of the protocol is sent to the eNB, so that the concurrent transmission of the LTE bearer data and the WLAN bearer data can be implemented.
  • the process of the UE transmitting uplink data to the eNB through the communication link of the LTE protocol and the related protocol stack architecture can be referred to the LTE protocol.
  • the second embodiment is described by taking the case that the bearer channel between the UE and the eNB and the WLAN AP is a TCP connection, and the bearer channel can also be replaced by a UDP connection.
  • the bearer channel is a UDP connection
  • the process of the bearer channel configuration process and the data offloading process may reuse the foregoing process, except that the UDP protocol type is specified in step 4 of the signaling configuration flow of the bearer channel, and the UDP protocol is specified. Port number.
  • a UDP connection is established between the subsequent UE and the network side and data can be sent and received through the UDP port.
  • the third embodiment describes a scheme for establishing a bearer channel of a DRB by using an IP protocol to implement splitting of user plane data between an eNB and a UE by using a WLAN AP.
  • the LTE wireless communication protocol is used for interaction between the UE and the eNB
  • the Wi-Fi wireless communication protocol is used for interaction between the UE and the WLAN AP
  • the eNB and the WLAN AP are connected by wire, and the cable is used.
  • the communication protocol interacts.
  • FIG. 10A is a user plane protocol stack architecture in Embodiment 3.
  • the LTE protocol stack in the UE includes a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from an upper layer to a lower layer;
  • the Wi-Fi protocol stack in the UE includes an IP layer and a MAC/PHY layer from an upper layer to a lower layer;
  • LTE of the eNB The PDCP layer, the RLC layer, the MAC layer and the PHY layer are included in the protocol stack from the upper layer to the lower layer;
  • the IP layer and the data link layer (shown as layer-2 in the figure) are included in the wired communication protocol stack of the eNB from the upper layer to the lower layer.
  • the shared LC entity is configured for UE1 and UE2 accessing the eNB.
  • UE1 and UE2 are respectively configured with two EPS bearers, and the corresponding PDCP entities of the two EPS bearers are respectively represented as PDCP1 and PDCP2.
  • UE1 and UE2 support user plane data offloading.
  • the correspondence between the PDCP entity and the logical channel identifier is: PDCP1 corresponds to LC1, and PDCP2 corresponds to LC2.
  • the signaling process of configuring the DRB between the UE and the eNB via the WLAN AP may specifically include the following:
  • Step 1 The UE reports the capability information of the UE to the eNB, and the capability information may indicate the UE's support capability for the user plane data offload transmission.
  • the capability information may indicate the UE's support capability for the user plane data offload transmission.
  • Step 2 The eNB configures the UE to measure the WLAN AP.
  • Step 3 The UE measures the WLAN AP according to the configuration of the eNB, and reports the measurement result, where the measurement result includes information such as the identifier of the WLAN AP measured by the UE.
  • Step 4 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and if the WLAN AP measured by the UE is obtained, sends a reconfiguration message to the UE to request the UE to configure the UE to communicate with the eNB. DRB of the WLAN AP.
  • the reconfiguration message may include the following content:
  • the IP protocol type indication information is used to indicate that the UE establishes the bearer channel of the DRB by using the IP protocol; the configuration information of the bearer channel of the DRB, that is, the configuration information required for establishing the bearer channel of the DRB; specifically, the address of the eNB and the UE And the information of the correspondence between the PDCP entity and the LCID in the DRB channel;
  • the identifier of the DRB that needs to be reconfigured in this embodiment, the WLAN AP between the UE and the eNB.
  • the identity of the DRB is the identity of the DRB;
  • the other configuration information may specifically include one or a combination of the following: information of a PDCP entity, information of a MAC entity, information of a physical layer entity, and the like.
  • Step 5 After receiving the reconfiguration message sent by the eNB, the UE initiates a connection establishment request to the eNB through the WLAN access network according to the configuration information therein.
  • Step 6 The UE establishes an IP-based bearer channel between the WLAN AP and the eNB.
  • step 5 of the foregoing process after receiving the reconfiguration message, the UE may not initiate a connection establishment request to the eNB through the WLAN access network, but directly send data to the eNB through the WLAN access network.
  • step 6 after receiving the data sent by the UE, the eNB feeds back to the UE a response message that the bearer channel is successfully established, or directly sends data to the UE through the WLAN access network.
  • the eNB may be configured to perform the WLAN AP measurement and the WLAN AP measurement result reported by the UE, and the UE may directly report the information of the available WLAN AP and the information measured by the UE to the eNB.
  • the UE may send user plane data to the eNB through the bearer channel. If the bearer channel connection fails during the data transmission process, the UE may notify the eNB of the bearer channel connection failure information.
  • the process for the eNB to send downlink data may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 PDCP1 in the eNB receives data packets from higher layers, such as PDCP PDUs.
  • Step 2 PDCP1 processes the received data packet, and sends the processed data packet to the LC entity shared by multiple UEs.
  • Step 3 The LC entity processes the received data packet, maps the processed data packet to a logical channel, and adds an LCID (the value of the LCID is represented as LC1), and the added LCID corresponds to PDCP1, and the LC entity will process The data packet is sent to the IP entity.
  • Step 4 The IP entity encapsulates the received data packet, specifies a new protocol type for the LC layer data packet transmission in the IP packet header, and sends the encapsulated data packet by IP routing.
  • the IP data packet sequentially passes through a data link layer entity and a physical layer entity in the eNB.
  • the new protocol type is an LC layer packet protocol type, which can be expressed as "LC protocol”.
  • the process of the UE may be as shown by the thick solid line in the figure, and may include the following steps:
  • Step 1 The data link layer entity (shown as WLAN MAC+PHY+LLC) in the Wi-Fi wireless communication protocol stack in the UE sends the received data packet to the IP entity.
  • the data link layer entity shown as WLAN MAC+PHY+LLC
  • Step 2 The IP entity decapsulates and parses the received data packet, and sends the processed data packet to the LC entity according to the protocol type.
  • the protocol type may be a new protocol type used by the IP layer for LC layer data packet transmission.
  • Step 3 The LC entity sends the received data packet to the corresponding PDCP entity according to the LCID in the packet header of the received data packet and the correspondence between the LCID and the PDCP entity: PDCP1.
  • Step 4 PDCP1 sends the received data packet to the IP entity.
  • Step 5 The IP entity sends the received data packet to the TCP entity according to the protocol type.
  • Step 6 The TCP entity sends the TCP packet to the application layer entity (shown as APP1 in the figure) through the TCP channel corresponding to the TCP port according to the TCP port number Port1 allocated for the application.
  • the application layer entity shown as APP1 in the figure
  • the above figure flow only describes the transmission process of user plane data in the downlink direction through the WLAN AP.
  • the user plane data in the downlink direction between the eNB and the UE may be transmitted to the UE through the WLAN AP, or part of the data may be offloaded to the UE through the WLAN AP, and another part of the data still passes through the LTE between the eNB and the UE.
  • the communication link of the protocol is sent to the UE, so that the concurrent transmission of the LTE bearer data and the WLAN bearer data can be implemented.
  • the process of the eNB transmitting downlink data to the UE through the communication link of the LTE protocol and the related protocol stack architecture can be referred to the LTE protocol.
  • the sending process of the user plane data in the uplink direction implemented on the UE side may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 The application layer entity (APP1 shown in the figure) sends the data packet to the TCP entity through the corresponding TCP channel according to the assigned TCP port number Port2.
  • Step 2 The TCP entity processes the received data packet and sends the processed data packet. Give the IP entity.
  • Step 3 The IP entity sends the data packet to the corresponding PDCP1 according to the IP header of the received data packet.
  • Step 4 PDCP1 processes the received data packet and sends the processed data packet to the LC entity.
  • Step 5 The LC entity processes the received data packet, maps the processed data packet to a logical channel, adds an LCID (the value of the LCID is expressed as LC1), and then sends the processed data packet to the IP entity.
  • LCID the value of the LCID is expressed as LC1
  • Step 6 The IP entity processes the received data packet, and according to the data packet from the LC layer, for example, according to the LCID in the data packet, specifies a new protocol type for the LC layer data packet transmission in the IP packet header, and The processed data packet is sent to a data link layer entity (shown as WLAN MAC+PHY+LLC) entity in the Wi-Fi wireless communication protocol stack.
  • a data link layer entity shown as WLAN MAC+PHY+LLC
  • the new protocol type is an LC layer packet protocol type, which can be expressed as "LC protocol”.
  • the IP data packet sent by the UE passes through the data link layer entity, the IP entity in the Wi-Fi wireless communication protocol stack, and the IP entity and the MAC/PHY entity in the wired communication protocol stack, and sends the IP data packet to the eNB. .
  • the processing flow after the eNB receives the user plane data may be as shown by a thick solid line in the figure, and includes the following steps:
  • Step 1 The IP entity processes the data packet received from the WLAN AP, and sends the processed data packet to the LC entity according to the protocol type of the data packet.
  • the protocol type may be a new protocol type used by the IP layer for LC layer packet transmission.
  • the new protocol type is an LC layer packet protocol type, which can be expressed as "LC protocol”.
  • Step 2 The LC entity processes the received data packet, and according to the LCID in the packet header of the received data packet (the value of the LCID is represented as LC1), and the correspondence between the LCID and the PDCP entity, the processed data packet is processed. Send to the corresponding PDCP1.
  • Step 3 PDCP1 processes the received data packet and sends the processed data packet to the upper layer.
  • the flow described in FIG. 10D and FIG. 10E described above only describes the transmission process of user plane data in the uplink direction through the WLAN AP.
  • the user plane data in the uplink direction between the eNB and the UE may be transmitted to the eNB through the WLAN AP, or part of the data may be offloaded to the eNB through the WLAN AP, and another part of the data still passes through the LTE between the eNB and the UE.
  • the communication link of the protocol is sent to the eNB, so that the concurrent transmission of the LTE bearer data and the WLAN bearer data can be implemented.
  • the process of the UE transmitting uplink data to the eNB through the communication link of the LTE protocol and the related protocol stack architecture can be referred to the LTE protocol.
  • the fourth embodiment describes a scheme for establishing a bearer channel of a DRB by using a GTP-U protocol to implement splitting of user plane data between an eNB and a UE by using a WLAN AP.
  • the LTE wireless communication protocol is used for interaction between the UE and the eNB
  • the Wi-Fi wireless communication protocol is used for interaction between the UE and the WLAN AP
  • the eNB and the WLAN AP are connected by wire, and the cable is used.
  • the communication protocol interacts.
  • FIG. 11A is a user plane protocol stack architecture in Embodiment 4.
  • the LTE protocol stack in the UE includes a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from an upper layer to a lower layer;
  • the Wi-Fi protocol stack in the UE includes a GTP-U layer, a UDP layer, an IP layer, and an upper layer from the upper layer to the lower layer.
  • the MAC/PHY layer includes the PDCP layer, the RLC layer, the MAC layer, and the PHY layer from the upper layer to the lower layer in the LTE protocol stack of the eNB; the GTP-U layer, the UDP layer, and the IP layer are included in the wired communication protocol stack of the eNB from the upper layer to the lower layer.
  • the data link layer (shown as layer-2 in the figure).
  • an LC entity is configured for UE1 and UE2 that access the eNB, respectively.
  • UE1 and UE2 are respectively configured with two EPS bearers, and the corresponding PDCP entities of the two EPS bearers are respectively represented as PDCP1 and PDCP2.
  • the correspondence between the PDCP entity and the logical channel identifier is: PDCP1 corresponds to LC1, PDCP2 corresponds to LC2.
  • the signaling process of configuring the DRB between the UE and the eNB via the WLAN AP may specifically include the following:
  • Step 1 The UE reports the capability information of the UE to the eNB, and the capability information may indicate the UE's support capability for the user plane data offload transmission.
  • the capability information may include the following content:
  • the protocol type indication information indicates the protocol used by the UE to establish a DRB bearer channel.
  • the protocol type is GTP-U;
  • the indication information indicates that the UE supports the user plane data to be offloaded via the WLAN AP.
  • Step 2 The eNB configures the UE to measure the WLAN AP.
  • Step 3 The UE measures the WLAN AP according to the configuration of the eNB, and reports the measurement result, where the measurement result includes information such as the identifier of the WLAN AP measured by the UE.
  • Step 4 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and sends a configuration message to the WLAN AP, so that the WLAN AP configures the WLAN AP and the UE, in the case that the WLAN AP measured by the UE is obtained.
  • the configuration information sent by the eNB to the WLAN AP may include the following connection configuration information:
  • the configuration information of the GTP-U connection between the UE and the WLAN AP may include: the GTP-U tunnel end identifier (TEID) of the GTP-U connected to the WLAN AP on the WLAN AP side, and the air interface GTP -U is connected to the GTP-U TEID of the UE, and is used to identify the GTU-U air interface connection of the UE;
  • TEID GTP-U tunnel end identifier
  • the configuration information of the GTP-U connection between the eNB and the WLAN AP, the GTP-U connection corresponding to the UE; the configuration information of the GTP-U connection may specifically include: the GTP-U connection between the eNB and the WLAN AP.
  • Step 5 The WLAN AP establishes the air interface GTP-U connection of the UE on the WLAN AP side (referred to as GTP-U connection 1 for convenience of description) and establishes the WLAN AP according to the configuration information in step 4.
  • the GTP-U connection with the eNB (referred to as GTP-U connection 2 for convenience of description), and establishes the correspondence between the above GTP-U connection 1 and GTP-U connection 2.
  • the GTP-U connection between the WLAN AP and the eNB corresponds to the UE.
  • the WLAN AP sends a configuration confirmation message to the eNB.
  • the configuration confirmation message may include the following information: the GTP-U TEID of the GTP-U connection 1 may also include the configuration information of the GTP-U connection 2, for example, the GTP of the GTP-U connection 1 on the WLAN AP side. U TEID, and GTP-U TEID on the UE side.
  • Step 6 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and if the WLAN AP measured by the UE is obtained, sends a reconfiguration message to the UE to request the UE to configure the UE to communicate with the eNB. DRB of the WLAN AP.
  • the reconfiguration message may include the following content:
  • the GTP-U protocol type indication information is used to indicate that the UE establishes a bearer channel of the DRB by using the GTP-U protocol;
  • Configuration information of the bearer channel of the DRB may be The GTP-U TEID of the WLAN AP is connected to the GTP-U TEID of the UE, and the GTP-U TEID of the UE is connected to the GTP-U TEID of the UE.
  • the identifier of the DRB that needs to be reconfigured in this embodiment, the identifier of the DRB between the UE and the eNB via the WLAN AP;
  • the other configuration information may include one or a combination of the following: information of a PDCP entity, a logical channel identifier (LCID), logical channel configuration information, information of a MAC entity, information of a physical layer entity, and the like.
  • a PDCP entity a logical channel identifier
  • LCID logical channel identifier
  • MAC entity information of a MAC entity
  • physical layer entity information of a physical layer entity
  • Step 7 After receiving the reconfiguration message sent by the eNB, the UE establishes an air interface GTP-U connection with the WLAN AP according to the configuration information therein, and connects through the air interface GTP-U, and performs data transmission and reception through the WLAN access network. . Further, the UE may feed back a configuration success message to the eNB.
  • Step 8 After receiving the configuration success message of the UE, or according to the configuration confirmation message in step 5, the eNB connects to the GTP-U (the GTP-U connection 2) and the WLAN AP corresponding to the UE. The UE performs data transmission and reception.
  • the eNB may be configured to perform the WLAN AP measurement and the WLAN AP measurement result reported by the UE, and the UE may directly report the information of the available WLAN AP and the information measured by the UE to the eNB.
  • step 4 and step 6 are not strictly required.
  • step 6 may be performed first and then step 4 may be performed, or may be performed simultaneously.
  • the UE may send user plane data to the eNB through the bearer channel. If the bearer channel connection fails during the data transmission process, the UE may notify the eNB of the bearer channel connection failure information.
  • the user plane data offload transmission process between the UE and the eNB may be as shown in FIGS. 11B and 11C and FIGS. 11D and 11E.
  • 11B and FIG. 11C respectively show the user plane data transmission flow in the downlink direction implemented on the eNB side and the UE side
  • FIG. 11D and FIG. 11E respectively show the uplink direction implemented on the eNB side and the UE side.
  • the downlink data sending process on the eNB side may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 PDCP1 in the eNB receives data packets from higher layers, such as PDCP PDUs.
  • Step 2 PDCP1 processes the received data packet, and sends the processed data packet to the LC entity corresponding to the PDCP.
  • Step 3 The LC entity processes the received data packet, maps the processed data packet to a logical channel, and adds an LCID (the value of the LCID is represented as LC1), and the added LCID corresponds to PDCP1, and the LC entity will process The subsequent data packets are sent to the GTP-U entity.
  • Step 4 The GTP-U entity sends the data to the WLAN AP through the corresponding GTP-U tunnel according to the correspondence between the GTP-U TEID and the LC entity.
  • the WLAN AP sends the received data to the UE through the GTP-U connection of the air interface of the WLAN AP on the WLAN AP according to the mapping between the Xw TEID of the GTP-U of the Xw interface and the WLAN TEID of the GTP-U of the WLAN air interface.
  • the downlink data receiving process on the UE side may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 The data link layer entity (shown as WLAN MAC+PHY+LLC) in the Wi-Fi wireless communication protocol stack in the UE sends the received data packet to the IP entity according to the protocol type.
  • the data link layer entity shown as WLAN MAC+PHY+LLC
  • Step 2 The IP entity decapsulates and parses the received data packet according to the protocol type, obtains a UDP packet, and sends the UDP packet to the UDP entity.
  • Step 3 The UDP entity processes the received data packet to obtain a GTP data packet, and sends the GTP data packet to the GTP-U entity according to the protocol type.
  • Step 4 The GTP-U entity sends the GTP data packet to the LC entity according to the supported protocol type or application type.
  • the protocol type or application type is a new type defined for LC layer data transceiving.
  • Step 5 The LC entity sends the data packet to the corresponding PDCP entity according to the LCID in the header of the received data packet and the correspondence between the LCID and the PDCP entity: PDCP1.
  • Step 5 PDCP1 sends the received data packet to the IP entity.
  • Step 6 The IP entity sends the UDP data packet to the UDP entity according to the protocol type.
  • Step 7 The UDP entity sends the UDP packet to the application layer entity (shown as APP1 in the figure) through the UDP channel corresponding to the UDP port according to the TCP port number Port2 allocated for the application.
  • the application layer entity shown as APP1 in the figure
  • the GTP-U connection in the above process is based on the UDP protocol. If the GTP-U connection is based on the TCP protocol, then in step 2, the IP entity sends the data packet to the TCP entity; in step 3, the TCP entity sends the data packet to the GTP-U entity; in step 6, the IP The entity sends the data packet to the TCP entity; in step 7, the TCP entity sends the data packet to the application layer entity.
  • the flow described above in FIG. 11B and FIG. 11C only describes the passage of user plane data in the downlink direction.
  • the transmission process of WLAN AP offloading.
  • the user plane data in the downlink direction between the eNB and the UE may be transmitted to the UE through the WLAN AP, or part of the data may be offloaded to the UE through the WLAN AP, and another part of the data still passes through the LTE between the eNB and the UE.
  • the communication link of the protocol is sent to the UE, so that the concurrent transmission of the LTE bearer data and the WLAN bearer data can be implemented.
  • the process of the eNB transmitting downlink data to the UE through the communication link of the LTE protocol and the related protocol stack architecture can be referred to the LTE protocol.
  • the sending process of the user plane data in the uplink direction implemented on the UE side may be as shown by a thick solid line in the figure, and may include the following steps:
  • Step 1 The application layer entity (APP1 shown in the figure) sends the data packet to the UDP entity through the corresponding UDP channel according to the assigned UDP port number Port2.
  • Step 2 The UDP entity processes the received data packet and sends the processed data packet to the IP entity.
  • Step 3 The IP entity sends the data packet to the corresponding PDCP1 according to the IP header of the received data packet.
  • Step 4 PDCP1 processes the received data packet and sends the processed data packet to the LC entity.
  • Step 5 The LC entity processes the received data packet, maps the processed data packet to a logical channel, adds an LCID (the value of the LCID is expressed as LC1), and sends the processed data packet to the GTP-U entity. .
  • Step 6 The GTP-U entity sends a GTP header to the UDP entity according to the correspondence between the GTP-U TEID and the LC entity, and sends the data packet to the WLAN through the GTP-U tunnel corresponding to the WLAN AP air interface. AP.
  • Step 7 The UDP entity sends the data packet to the IP entity.
  • Step 8 The IP entity processes the received data packet, and sends the processed data packet to the data link layer entity (shown as WLAN MAC+PHY+LLC) entity in the Wi-Fi wireless communication protocol stack. .
  • the data packet passes through the data link layer entity and the physical layer entity in the UE in sequence.
  • the GTP-U connection in the above process is based on the UDP protocol. If the GTP-U connection is based on TCP In the protocol, in step 1, the application layer entity sends the data packet to the TCP entity; in step 2, the TCP entity sends the data packet to the IP entity; in step 6, the GTP-U entity sends the data packet to the TCP. Entity; In step 7, the TCP entity sends the packet to the IP entity.
  • the WLAN AP After receiving the data sent by the UE, the WLAN AP connects the WLAN TEID of the GTP-U connected to the WLAN air interface according to the Xw TEID of the GTP-U of the Xw interface, and passes the received data to the GTP of the UE on the eNB side.
  • the U connection is sent to the eNB.
  • the processing flow after the eNB receives the user plane data may be as shown by a thick solid line in the figure, and includes the following steps:
  • Step 1 The GTP-U entity sends the data packet to the LC entity corresponding to the UE according to the protocol type or application type of the data packet and the Xw TEID of the UE.
  • Step 2 The LC entity processes the data packet, and sends the processed data packet to the LCID in the packet header of the received data packet (the LCID value is represented as LC1) and the correspondence between the LCID and the PDCP entity. Corresponding PDCP1.
  • Step 3 PDCP1 processes the received data packet and sends the processed data packet to the upper layer.
  • the flow described in FIG. 11D and FIG. 11E described above only describes the transmission process of user plane data in the uplink direction through the WLAN AP.
  • the user plane data in the uplink direction between the eNB and the UE may be transmitted to the eNB through the WLAN AP, or part of the data may be offloaded to the eNB through the WLAN AP, and another part of the data still passes through the LTE between the eNB and the UE.
  • the communication link of the protocol is sent to the eNB, so that the concurrent transmission of the LTE bearer data and the WLAN bearer data can be implemented.
  • the process of the UE transmitting uplink data to the eNB through the communication link of the LTE protocol and the related protocol stack architecture can be referred to the LTE protocol.
  • the fifth embodiment describes that the bearer channel between the UE and the WLAN AP is an air interface UDP connection, and the user plane between the eNB and the UE is implemented by the WLAN AP in the case that the bearer channel between the WLAN AP and the eNB is a GTP-U connection.
  • the scheme for data splitting is an air interface UDP connection, and the user plane between the eNB and the UE is implemented by the WLAN AP in the case that the bearer channel between the WLAN AP and the eNB is a GTP-U connection.
  • the UE and the eNB interact using an LTE wireless communication protocol
  • the UE interacts with the WLAN AP using a Wi-Fi wireless communication protocol
  • the eNB and the WLAN AP are connected by wire, and interact using a wired communication protocol.
  • the LTE protocol stack in the UE includes a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from an upper layer to a lower layer;
  • the Wi-Fi protocol stack in the UE includes a UDP layer, an IP layer, and a MAC/PHY layer from an upper layer to a lower layer;
  • the eNB's LTE protocol stack includes a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from the upper layer to the lower layer;
  • the eNB's wired communication protocol stack includes a GTP-U layer, a UDP layer, an IP layer, and a data link layer from the upper layer to the lower layer. (shown as layer-2 in the figure).
  • the signaling process of configuring the DRB between the UE and the eNB via the WLAN AP may specifically include the following:
  • Step 1 The UE reports the capability information of the UE to the eNB, and the capability information may indicate the UE's support capability for the user plane data offload transmission.
  • the capability information may include the following content:
  • the protocol type indication information indicates the protocol used by the UE to establish a DRB bearer channel.
  • the protocol type is UDP;
  • the indication information indicates that the UE supports the user plane data to be offloaded via the WLAN AP.
  • Step 2 The eNB configures the UE to measure the WLAN AP.
  • Step 3 The UE measures the WLAN AP according to the configuration of the eNB, and reports the measurement result, where the measurement result includes information such as the identifier of the WLAN AP measured by the UE.
  • Step 4 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and sends a configuration message to the WLAN AP, so that the WLAN AP configures the WLAN AP and the UE, in the case that the WLAN AP measured by the UE is obtained. Between the UDP connection and the GTP-U connection between the WLAN AP and the eNB.
  • the configuration information sent by the eNB to the WLAN AP may include the following connection configuration information:
  • the configuration information of the UDP connection between the UE and the WLAN AP may specifically include: the UE and the WLAN AP.
  • Step 5 After receiving the configuration, the WLAN AP establishes the air interface UDP connection of the UE on the WLAN AP side, and establishes a GTP-U connection between the WLAN AP and the eNB according to the configuration information in step 4, and establishes a correspondence between the two. Relationships, the correspondence between the two can be represented by the correspondence between the port number of the air interface UDP connection and the TEID of the GTP-U connection.
  • the GTP-U connection between the WLAN AP and the eNB corresponds to the UE.
  • the WLAN AP sends a configuration confirmation message to the eNB.
  • the configuration confirmation message may include the following information: the GTP-U TEID of the GTP-U connection may also include the configuration information of the air interface UDP connection, for example, the port number and IP address of the air interface UDP connection on the WLAN AP side, and The port number and the IP address of the UE side may further include a correspondence between the air interface UDP connection and the GTP-U connection.
  • Step 6 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and if the WLAN AP measured by the UE is obtained, sends a reconfiguration message to the UE to request the UE to configure the UE to communicate with the eNB. DRB of the WLAN AP.
  • the reconfiguration message may include the following content:
  • the UDP protocol type indication information is used to indicate that the UE establishes a bearer channel of the DRB by using the UDP protocol;
  • Configuration information of the bearer channel of the DRB may include: the air interface UDP connection is on the WLAN AP side. Port number and IP address, the port number and IP address of the air interface UDP connection on the UE side.
  • the identifier of the DRB that needs to be reconfigured in this embodiment, the WLAN AP between the UE and the eNB.
  • the identity of the DRB is the identity of the DRB;
  • the other configuration information may include one or a combination of the following: information of a PDCP entity, a logical channel identifier (LCID), logical channel configuration information, information of a MAC entity, information of a physical layer entity, and the like.
  • a PDCP entity a logical channel identifier
  • LCID logical channel identifier
  • MAC entity information of a MAC entity
  • physical layer entity information of a physical layer entity
  • Step 7 After receiving the reconfiguration message sent by the eNB, the UE establishes an air interface UDP connection with the WLAN AP according to the configuration information therein, and performs data transmission and reception through the WLAN access network through the air interface UDP connection. Further, the UE may feed back a configuration success message to the eNB.
  • Step 8 After receiving the configuration success message of the UE, or according to the configuration confirmation message in step 5, the eNB performs data transmission and reception with the UE through a GTP-U connection with the WLAN AP corresponding to the UE.
  • the eNB may be configured to perform the WLAN AP measurement and the WLAN AP measurement result reported by the UE, and the UE may directly report the information of the available WLAN AP and the information measured by the UE to the eNB.
  • step 4 and step 6 are not strictly required.
  • step 6 may be performed first and then step 4 may be performed, or may be performed simultaneously.
  • an air interface TCP connection may be established between the UE and the WLAN AP instead of the air interface UDP connection. If the air interface TCP connection is established between the UE and the WLAN AP, the bearer channel configuration process is similar to the above process except that the UDP protocol type is replaced with the TCP protocol type, and the UDP port is replaced with a TCP port.
  • the UE may send user plane data to the eNB through the bearer channel. If the bearer channel connection fails during the data transmission process, the UE may notify the eNB of the bearer channel connection failure information.
  • the process of the eNB transmitting the downlink data is similar to the related process in the fourth embodiment. For details, see 11B.
  • the difference from the flow shown in FIG. 11B is that after receiving the data sent by the eNB, the WLAN AP passes the received data to the UE according to the correspondence between the GTP-U connection of the Xw interface and the UDP (or TCP) connection of the WLAN air interface.
  • the UDP (or TCP) connection of the air interface on the WLAN AP side is sent to the UE.
  • the WLAN AP is based on the mapping between the GTP-U connection of the Xw interface and the UDP (or TCP) connection of the WLAN air interface.
  • the WLAN AP can be represented by the correspondence between the TEID of the GTP-U connection of the Xw interface and the port number of the UDP (or TCP) connection of the WLAN air interface.
  • the process of receiving the downlink data by the UE is basically the same as the related process in the first embodiment. For details, refer to FIG. 8C.
  • the process of sending the uplink data by the UE is basically the same as the related process in the first embodiment. For details, refer to FIG. 8D.
  • the process of receiving the uplink data by the eNB is similar to the related process in the fourth embodiment. For details, refer to FIG. 11E.
  • the difference from the flow shown in FIG. 11E is that the UDP (or TCP) entity of the WLAN AP receives the corresponding UDP (or TCP) data from the UE peer UDP (or TCP) entity, and the WLAN AP is based on the GTP-U of the Xw interface.
  • the data is sent to the GTP-U entity of the eNB through the GTP-U connection between the eNB and the WLAN AP of the UE on the WLAN AP side.
  • the GTP-U entity of the eNB sends the data packet to the LC entity corresponding to the UE according to the protocol type (or application type) of the data packet and the Xw TEID of the UE.
  • the WLAN AP can connect to the UDP (or TCP) connection of the WLAN air interface according to the GTP-U connection of the Xw interface and the UDP (or TCP) connection of the WLAN air interface according to the mapping between the GTP-U connection of the Xw interface and the UDP (or TCP) connection of the WLAN air interface.
  • the correspondence between the port numbers is represented.
  • the fifth embodiment is described by taking a bearer channel between the UE and the WLAN AP as a TCP connection, and the bearer channel may also be replaced by a UDP connection.
  • the bearer channel is a UDP connection
  • the process of the bearer channel configuration process and the data offloading process may reuse the foregoing process, except that the UDP protocol type is specified in step 4 of the signaling configuration flow of the bearer channel, and the UDP protocol is specified. Port number.
  • a UDP connection is established between the subsequent UE and the network side and data can be sent and received through the UDP port.
  • the sixth embodiment describes that the bearer channel between the UE and the WLAN AP is an air interface IP connection, and the user plane between the eNB and the UE is implemented by the WLAN AP when the bearer channel between the WLAN AP and the eNB is a GTP-U connection.
  • the scheme for data splitting is described.
  • the UE and the eNB use the LTE wireless communication protocol to interact,
  • the UE interacts with the WLAN AP using a Wi-Fi wireless communication protocol, and the eNB and the WLAN AP are connected by wire, and interact using a wired communication protocol.
  • FIG. 13 is a user plane protocol stack architecture in Embodiment 6.
  • the LTE protocol stack in the UE includes a PDCP layer, an RLC layer, a MAC layer, and a PHY layer from an upper layer to a lower layer;
  • the Wi-Fi protocol stack in the UE includes an IP layer and a MAC/PHY layer from an upper layer to a lower layer;
  • LTE of the eNB In the protocol stack, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer are included from the upper layer to the lower layer;
  • the GTP-U layer, the UDP layer, the IP layer, and the data link layer are included in the wired communication protocol stack of the eNB from the upper layer to the lower layer (in the figure) Shown as layer-2).
  • the signaling process of configuring the DRB between the UE and the eNB via the WLAN AP may specifically include the following:
  • Step 1 The UE reports the capability information of the UE to the eNB, and the capability information may indicate the UE's support capability for the user plane data offload transmission.
  • the capability information may include the following content:
  • the protocol type indication information indicates the protocol used by the UE to establish a DRB bearer channel.
  • the protocol type is GTP-U;
  • the indication information indicates that the UE supports the user plane data to be offloaded via the WLAN AP.
  • Step 2 The eNB configures the UE to measure the WLAN AP.
  • Step 3 The UE measures the WLAN AP according to the configuration of the eNB, and reports the measurement result, where the measurement result includes information such as the identifier of the WLAN AP measured by the UE.
  • Step 4 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and sends a configuration message to the WLAN AP, so that the WLAN AP configures the WLAN AP and the UE, in the case that the WLAN AP measured by the UE is obtained. Between the UDP connection and the GTP-U connection between the WLAN AP and the eNB.
  • the configuration information sent by the eNB to the WLAN AP may include the following connection configuration information:
  • the indication information of the IP protocol to indicate that the WLAN AP establishes an IP connection with the UE;
  • the configuration information of the IP connection between the UE and the WLAN AP may specifically include: the UE and the WLAN AP.
  • the air interface IP address is connected to the IP address of the WLAN AP side, and the air interface UDP is connected to the IP address of the UE side;
  • the configuration information of the GTP-U connection between the eNB and the WLAN AP, the GTP-U connection corresponding to the UE; the configuration information of the GTP-U connection may specifically include: the GTP-U connection between the eNB and the WLAN AP.
  • Step 5 After receiving the configuration, the WLAN AP establishes the air interface IP connection of the UE on the WLAN AP side, and establishes a GTP-U connection between the WLAN AP and the eNB according to the configuration information in step 4, and establishes a correspondence between the two. Relationships, the correspondence between the two can be represented by the correspondence between the port number of the air interface UDP connection and the TEID of the GTP-U connection.
  • the GTP-U connection between the WLAN AP and the eNB corresponds to the UE.
  • the WLAN AP sends a configuration confirmation message to the eNB.
  • the configuration confirmation message may include the following information: the GTP-U TEID of the GTP-U connection, and the configuration information of the air interface IP connection, for example, the port number and IP address of the air interface UDP connection on the WLAN AP side, and The port number and the IP address of the UE side may further include a correspondence between the air interface UDP connection and the GTP-U connection.
  • Step 6 The eNB confirms that the UE supports the offloading of the user plane data via the WLAN AP, and if the WLAN AP measured by the UE is obtained, sends a reconfiguration message to the UE to request the UE to configure the UE to communicate with the eNB. DRB of the WLAN AP.
  • the reconfiguration message may include the following content:
  • the IP protocol type indication information is used to indicate that the UE uses the UDP protocol to establish a bearer channel of the DRB, and the configuration information of the bearer channel of the DRB.
  • the information may include: information about the correspondence between the PDCP entity and the LCID in the DRB channel, and the UE.
  • the configuration information of the air interface IP connection with the WLAN AP may include: an IP address of the air interface IP connection on the WLAN AP side, an IP address of the air interface IP connection on the UE side, and the like;
  • the identifier of the DRB that needs to be reconfigured in this embodiment, the WLAN AP between the UE and the eNB.
  • the identity of the DRB is the identity of the DRB;
  • the other configuration information may include one or a combination of the following: information of the PDCP entity, information of the LC entity, channel identifier between the PDCP and the LC, configuration information of the channel between the PDCP and the LC, and a logical channel identifier (LCID). , logical channel configuration information, information of the MAC entity, information of the physical layer entity, and the like.
  • Step 7 After receiving the reconfiguration message sent by the eNB, the UE establishes an air interface IP connection with the WLAN AP according to the configuration information therein, and performs data transmission and reception through the WLAN access network through the air interface IP connection. Further, the UE may feed back a configuration success message to the eNB.
  • Step 8 After receiving the configuration success message of the UE, or according to the configuration confirmation message in step 5, the eNB performs data transmission and reception with the UE through a GTP-U connection with the WLAN AP corresponding to the UE.
  • the eNB may be configured to perform the WLAN AP measurement and the WLAN AP measurement result reported by the UE, and the UE may directly report the information of the available WLAN AP and the information measured by the UE to the eNB.
  • step 4 and step 6 are not strictly required.
  • step 6 may be performed first and then step 4 may be performed, or may be performed simultaneously.
  • the UE may send user plane data to the eNB through the bearer channel. If the bearer channel connection fails during the data transmission process, the UE may notify the eNB of the bearer channel connection failure information.
  • the process of the eNB transmitting the downlink data is similar to the related process in the fourth embodiment. For details, see 11B.
  • the difference from the flow shown in FIG. 11B is that the WLAN AP receives the data sent by the eNB, according to the correspondence between the GTP-U connection of the Xw interface and the IP connection of the WLAN air interface, for example, according to the IP address or WLAN MAC address of the UE. And sending the received data to the UE through the IP connection of the UE on the air interface of the WLAN AP side.
  • the process of receiving the downlink data by the UE is basically the same as the related process in the third embodiment. For details, refer to FIG. 10C.
  • the process of sending uplink data by the UE is basically the same as the related process in the third embodiment. For details, see Figure 10D.
  • the process of receiving the uplink data by the eNB is similar to the related process in the fourth embodiment. For details, refer to FIG. 11E.
  • the difference from the flow shown in FIG. 11E is that the IP entity of the WLAN AP receives the IP data packet from the UE's peer IP entity, and the WLAN AP associates with the IP connection of the WLAN air interface according to the GTP-U connection of the Xw interface, for example,
  • the data is transmitted to the GTP-U entity of the eNB through a GTP-U connection between the eNB and the WLAN AP according to the IP address or WLAN MAC address of the UE.
  • the GTP-U entity of the eNB sends the data packet to the LC entity corresponding to the UE according to the protocol type (or application type) of the data packet and the Xw TEID of the UE.
  • the seventh embodiment describes a scheme for establishing a bearer channel of a DRB by using a TCP protocol to implement splitting of user plane data between an eNB and a UE by using a WLAN AP.
  • the user plane protocol stack architecture in the seventh embodiment is the same as the user plane protocol stack architecture in the first embodiment. For details, refer to FIG. 8A.
  • the bearer configuration process in the seventh embodiment is basically the same as the related process in the first embodiment, except that in step 4, the TCP port number in the configuration information required for the TCP connection uniquely corresponds to one DRB. Since one DRB corresponds to one PDCP entity, the TCP port number has a one-to-one correspondence with the PDCP entity.
  • the UE may send user plane data to the eNB through the bearer channel. If the bearer channel connection fails during the data transmission process, the UE may notify the eNB of the bearer channel connection failure information.
  • the process of the eNB transmitting the downlink data is similar to the related process in the first embodiment. For details, refer to FIG. 8B.
  • the difference between this embodiment and the first embodiment is that the operation of step 3 is omitted, and in step 2, the PDCP entity according to the The TCP port number corresponding to the PDCP entity, and the data packet is sent to the TCP entity through the TCP port.
  • the process of receiving the downlink data by the UE is the same as the related process in the first embodiment. For details, refer to FIG. 8C.
  • the difference between the embodiment and the first embodiment is that, in step 4, the PDCP entity is configured according to the TCP port corresponding to the PDCP entity. Number, the packet is sent to the TCP entity through the TCP port.
  • the process of sending the uplink data by the UE is the same as the related process in the first embodiment. For details, refer to FIG. 8D.
  • the difference between the embodiment and the first embodiment is that, in step 4, the PDCP entity is configured according to the TCP port number corresponding to the PDCP. Send the packet to the TCP entity through the TCP port.
  • the process of receiving the uplink data by the eNB is similar to the related process in the first embodiment. For details, refer to FIG. 8E.
  • the difference between this embodiment and the first embodiment is that, in step 2, the TCP entity performs data according to the DRB corresponding to the TCP port. The packet is sent to the corresponding PDCP entity of the corresponding UE through the TCP port. If the eNB allocates the same TCP port to different UEs, the eNB distinguishes different PDCP entities according to the IP address and TCP port number of the UE side that receives the data from the TCP port, and then sends the data packet to the PDCP corresponding to the corresponding UE. entity.
  • the seventh embodiment is described by taking a TCP connection between the UE and the eNB and via the WLAN AP as a TCP connection.
  • the bearer channel may also be replaced by a UDP connection. If the bearer channel is a UDP connection, The process of the bearer channel configuration process and the data offloading process can reuse the above process, except that the UDP protocol type is specified in step 4 of the signaling configuration flow of the bearer channel, and the port number of the UDP protocol is specified.
  • a UDP connection is established between the subsequent UE and the network side and data can be sent and received through the UDP port.
  • Embodiment 8 describes a scheme for establishing a bearer channel of a DRB by using a GTP-U protocol to implement splitting of user plane data between an eNB and a UE by using a WLAN AP.
  • the user plane protocol stack architecture in the eighth embodiment is the same as the user plane protocol stack architecture in the fifth embodiment. For details, refer to FIG.
  • the bearer configuration process in the eighth embodiment is basically the same as the related process in the fifth embodiment, except that the UDP (or TCP) connection between the UE and the WLAN AP corresponds to the DRB in the terminal, that is, A DRB uniquely needs to be shunted via a WLAN AP, correspondingly:
  • step 5 in the configuration information of the UDP (or TCP) connection of the air interface between the UE and the WLAN AP, the UDP (or TCP) port number of the WLAN AP air interface connection corresponds to the DRB of the UE; in step 6, the UE is established in the WLAN.
  • the port number of the air interface UDP (or TCP) connection between the WLAN AP and the UE corresponds to the DRB of the UE.
  • the UE may send user plane data to the eNB through the bearer channel. If the bearer channel connection fails during the data transmission process, the UE may notify the eNB of the bearer channel connection failure information.
  • step 3 is omitted, and:
  • step 2 the PDCP entity sends the data packet to the GTP-U entity according to the GTP-U TEID corresponding to each DRB.
  • the WLAN AP passes the UDP (or UDP) of the air interface of the UE on the WLAN AP side according to the correspondence between the Xw TEID of the GTP-U of the Xw interface and the UDP (or UDP) connection (such as a port) of the WLAN air interface.
  • the connection is sent to the DRB corresponding to the UE.
  • the process of receiving downlink data by the UE is basically the same as the related process in Embodiment 7.
  • the process of the UE transmitting the uplink data is basically the same as the related process in the seventh embodiment.
  • step 2 is omitted, and:
  • the UDP (or TCP) entity of the WLAN AP receives the corresponding UDP (or TCP) data from the UE peer UDP (or TCP) entity, and the WLAN AP is based on the Xw TEID of the GTP-U of the Xw interface and the WLAN air interface.
  • the correspondence between the UDP (or TCP) connection (such as a port) is sent to the GTP-U entity of the eNB through the GTP-U connection between the eNB and the WLAN AP of the UE on the WLAN AP side.
  • the WLAN AP distinguishes different UEs according to the IP address and TCP port number of the UE side that receives the data from the TCP port, and then sends the TCP data to the GTP corresponding to the corresponding UE.
  • TEID connection The GTP-U layer of the eNB sends the data packet to the PDCP entity corresponding to the UE according to the protocol type (or application type) of the data packet and the Xw TEID of the UE.
  • the UE can be connected to other access technologies (such as WLAN APs) on the eNB at the same time.
  • the PDCP data of the eNB can be transparently transmitted to other access technologies, and the data on the LTE side can be flexibly split. Efficient use of existing WLAN AP resources.
  • an embodiment of the present disclosure further provides an access device and a terminal.
  • FIG. 14 is a schematic structural diagram of an access device according to an embodiment of the present disclosure.
  • the access device may be the first access device in the foregoing process, such as a base station.
  • the access device may include: an obtaining module 1401, a bearer configuration requesting module 1402, and a bearer configuration module 1403, where:
  • the obtaining module 1401 is configured to obtain capability information of the terminal, where the capability information is used to indicate that the terminal supports the user plane data offload transmission;
  • the bearer configuration requesting module 1402 is configured to request the terminal to configure the terminal between the terminal and the first access device according to the capability information of the terminal and the second access device that performs data offloading for the terminal. Transmitting a DRB via the data of the second access device; wherein the first access device and the second access device support different access technologies;
  • the bearer configuration module 1403 is configured to establish a bearer channel of the DRB with the terminal.
  • the capability information includes one or any combination of the following:
  • protocol type indication information is used to indicate a protocol used by the terminal to establish the bearer channel
  • the terminal supports the indication information that the user plane data is offloaded via the second access device.
  • the information used to indicate that the terminal configures the DRB includes one or any combination of the following:
  • protocol type indication information is used to indicate a protocol used by the terminal to establish the bearer channel
  • the configuration information of the bearer channel includes: at least: a correspondence between a PDCP entity and a logical channel identifier in the bearer channel;
  • the identifier of the DRB is the identifier of the DRB.
  • the protocol used by the bearer channel includes one of the following: an internet protocol IP, a transmission control protocol TCP, a user datagram protocol UDP, a user plane general packet radio service protocol GTP-U, a hypertext transfer protocol HTTP, and a hypertext transmission security. Protocol HTTPS.
  • the bearer channel is a TCP or UDP connection established by using a TCP protocol
  • the configuration information of the bearer channel further includes: port information of the TCP or UDP connection.
  • the bearer configuration module is further configured to: before instructing the terminal to configure the DRB, confirming, according to the capability information of the terminal, that the terminal supports user plane data to be offloaded by using the second access device, where the terminal is the terminal.
  • the corresponding LC entity allocates a TCP or UDP port, wherein the DRB of the terminal is configured with an LC entity; or the bearer configuration module is further configured to: allocate a TCP or UDP port to the LC entity in advance.
  • the configuration information of the bearer channel further includes an identifier of the terminal, where the multiple DRB bearers of the terminal are configured with one LC entity, or the bearer configuration module is further configured to: Before the DRB, according to the capability information of the terminal, it is confirmed that the terminal supports the user plane data to be offloaded by the second access device, and the corresponding DR/BB corresponding to the terminal needs to be allocated by the second access device to allocate a corresponding TCP or UDP port.
  • the bearer channel is an IP connection established by using an IP protocol
  • the configuration information of the bearer channel further includes: identifier information of the terminal.
  • the terminal and the second access device are connected by an air interface GTP-U established by using the GTP-U protocol
  • the configuration information of the bearer channel further includes: The configuration information of the air interface GTP-U connection between the terminal and the second access device.
  • the bearer channel is an air interface UDP or TCP connection between the terminal and the second access device
  • the configuration information of the bearer channel further includes: the terminal and the second interface Configuration information of the air interface UDP or TCP link between the devices.
  • the bearer channel is an air interface IP connection between the terminal and the second access device
  • the configuration information of the bearer channel further includes: the terminal and the second access device Configuration information of the air interface IP connection.
  • the bearer configuration requesting module is further configured to: if the connection between the first access device and the second access device is a GTP-U connection, in the bearer channel, the second connection
  • the inbound device sends the GTP-U connection configuration information, where the GTP-U connection configuration information includes:
  • the protocol type indication information where the protocol indicated by the protocol type indication information is a GTP-U protocol;
  • Configuration information of the air interface GTP-U connection between the terminal and the second access device and configuration information of the GTP-U connection between the first access device and the second access device;
  • the identifier of the DRB is the identifier of the DRB.
  • the access device further includes: a transmission module, configured to receive user plane data from the core network, and pass the user plane data to a bearer channel between the terminal and the terminal via a DRB of the second access device. Sending to the terminal; and/or receiving user plane data from the terminal through the bearer channel, and transmitting the user plane data to the core network.
  • a transmission module configured to receive user plane data from the core network, and pass the user plane data to a bearer channel between the terminal and the terminal via a DRB of the second access device. Sending to the terminal; and/or receiving user plane data from the terminal through the bearer channel, and transmitting the user plane data to the core network.
  • FIG. 15 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • the terminal may include: a reporting module 1501, a bearer configuration receiving module 1502, and a bearer configuration module 1503, where:
  • the reporting module 1501 is configured to report the capability information of the terminal to the first access device, where the capability information is used to indicate that the terminal supports the user plane data offload transmission;
  • the bearer configuration receiving module 1502 is configured to receive a configuration request sent by the first access device, where the configuration request is used to request the terminal to configure a second access between the terminal and the first access device.
  • the data offloaded by the device is a radio bearer DRB; wherein the first access device and the second access device support different access modes;
  • the bearer configuration module 1503 is configured to establish a bearer channel of the DRB with the first access device.
  • the capability information includes one or any combination of the following:
  • protocol type indication information is used to indicate a protocol used by the terminal to establish the bearer channel
  • the terminal supports the indication information that the user plane data is offloaded via the second access device.
  • the information used to indicate that the terminal configures the DRB includes one or any combination of the following:
  • protocol type indication information is used to indicate a protocol used by the terminal to establish the bearer channel
  • the configuration information of the bearer channel includes: at least: a correspondence between a PDCP entity and a logical channel identifier in the bearer channel;
  • the identifier of the DRB is the identifier of the DRB.
  • the protocol used by the bearer channel includes one of the following: an internet protocol IP, a transmission control protocol TCP, a user datagram protocol UDP, a user plane general packet radio service protocol GTP-U, a hypertext transfer protocol HTTP, hypertext. Transmission security protocol HTTPS.
  • the bearer channel is a TCP or UDP connection established by using a TCP protocol
  • the configuration information of the bearer channel further includes: port information of the TCP or UDP connection.
  • the bearer channel is an IP connection established by using an IP protocol
  • the configuration information of the bearer channel further includes: identifier information of the terminal.
  • the terminal and the second access device are connected by an air interface GTP-U established by using the GTP-U protocol
  • the configuration information of the bearer channel further includes: The configuration information of the air interface GTP-U connection between the terminal and the second access device.
  • the bearer channel is an air interface UDP or TCP connection between the terminal and the second access device
  • the configuration information of the bearer channel further includes: the terminal and the second interface Configuration information of the air interface UDP or TCP link between the devices.
  • the bearer channel is an air interface IP connection between the terminal and the second access device
  • the configuration information of the bearer channel further includes: between the terminal and the second access device Configuration information for the air interface IP connection.
  • the terminal further includes: a transmission module, configured to send user plane data to the first access device by using a bearer channel between the first receiving device and the DRB of the second access device
  • the first access device and the second access device adopt different access technologies; and/or receive user plane data from the first access device through the bearer channel.
  • FIG. 16 is a schematic structural diagram of an access device according to another embodiment of the present disclosure.
  • the access device may be the first access device in the foregoing embodiment, and may be, for example, a base station.
  • the access device can include a processor 1601, a memory 1602, a transceiver 1603, and a bus interface.
  • the processor 1601 is responsible for managing the bus architecture and general processing, and the memory 1602 can store data used by the processor 1601 in performing operations.
  • the transceiver 1603 is configured to receive and transmit data under the control of the processor 1601.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 1601 and various circuits of memory represented by memory 1602.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 1603 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 1601 is responsible for managing the bus architecture and general processing, and the memory 1602 can store data used by the processor 1601 in performing operations.
  • the flow of the wireless data bearer configuration of the user plane and the flow of data transmission through the channel of the wireless data bearer disclosed in the embodiment of the present disclosure may be applied to the processor 1601 or implemented by the processor 1601.
  • each step of the processing method of the control plane may be completed by an integrated logic circuit of hardware in the processor 1601 or an instruction in a form of software.
  • the processor 1601 can be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or perform the embodiments of the present disclosure.
  • Various methods, steps, and logic blocks of the disclosure are examples of the disclosure.
  • a general purpose processor can be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly implemented as hardware processor execution completion or performed by a combination of hardware and software modules in the processor.
  • Software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory or The rewritable programmable memory, registers, and the like are well-known in the storage medium.
  • the storage medium is located in the memory 1602, and the processor 1601 reads the information in the memory 1602, in conjunction with its hardware, to complete the steps of the processing method of the control plane.
  • the terminal may include: a processor 1701, a memory 1702, a transceiver 1703, and a bus interface.
  • the processor 1701 is responsible for managing the bus architecture and general processing, and the memory 1702 can store data used by the processor 1701 in performing operations.
  • the transceiver 1703 is for receiving and transmitting data under the control of the processor 1701.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 1701 and various circuits of memory represented by memory 1702.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 1703 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 1701 is responsible for managing the bus architecture and general processing, and the memory 1702 can store data used by the processor 1701 in performing operations.
  • the flow of the wireless data bearer configuration of the user plane disclosed in the embodiment of the present disclosure and the flow of data transmission through the channel of the wireless data bearer may be applied to the processor 1701 or implemented by the processor 1701.
  • each step of the processing method of the control plane may be completed by an integrated logic circuit of hardware in the processor 1701 or an instruction in a form of software.
  • the processor 1701 can be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or perform the embodiments of the present disclosure.
  • Various methods, steps, and logic blocks of the disclosure are examples of the disclosure.
  • a general purpose processor can be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly implemented as hardware processor execution completion or performed by a combination of hardware and software modules in the processor.
  • Software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory or The rewritable programmable memory, registers, and the like are well-known in the storage medium.
  • the storage medium is located in the memory 1702, and the processor 1701 reads the information in the memory 1702, in conjunction with its hardware, to complete the steps of the processing method of the control plane.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

本公开揭露了一种数据无线承载配置方法、数据传输方法及设备。本公开方法包括：第一接入设备获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；所述第一接入设备根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备之间经由所述第二接入设备的数据无线承载(DRB)；其中，第一接入设备与第二接入设备支持不同的接入技术；所述第一接入设备与所述终端之间建立所述DRB的承载通道。

Description

数据无线承载配置方法、数据传输方法及设备
相关申请的交叉引用
本申请主张在2015年4月10日在中国提交的中国专利申请号No.201510170313.6的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及无线通信领域，尤其涉及一种数据无线承载配置方法、数据传输方法及设备。
背景技术
长期演进(Long Term Evolution，LTE)系统的协议层，从用户面考虑，从上至下包括分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路控制(Radio link Control，RLC)层、媒体接入控制(Media Access Control，MAC)层、物理(Physical，PHY)层；从控制面考虑，还包括PDCP层之上的无线资源控制(Radio Resource Control，RRC)层。
用户设备(User Equipment，UE)，即终端接入网络并与演进节点B(evolved NodeB，eNB)，即基站建立连接后，eNB利用RRC消息向UE配置多个无线承载。无线承载根据其功能不同，分为数据无线承载(Data Radio Bearer，DRB)和信令无线承载(Signaling Radio Bearer，SRB)。
在用户面，DRB的数据来自核心网(Core Network，CN)，经过PDCP层逐层到物理层，SRB的数据来自eNB，经过PDCP层逐层到物理层，eNB最终通过物理层的信号将信息发送给UE。UE则通过自己的PDCP层、RLC层、MAC层、物理层逆向解析eNB的数据，最终，PDCP层将数据发送给UE的数据接收实体，如应用程序(application)。UE可将自己的数据从PDCP层往下打包到物理层，通过物理层的信号发送给eNB。图1示出了LTE系统中的用户面协议栈。
随着LTE网络结构的进一步演进，业界开始考虑小型基站和宏基站同时给 UE提供服务。目前，引入了双连接的概念，即当多个基站给UE提供服务时，其中一个基站为UE的主基站(Master eNB，MeNB)，其余基站为UE的辅基站(Second eNB，SeNB)。如图2所示，UE在MeNB上的连接可以有独立的承载，在SeNB上的连接是将MeNB上的同一个演进的分组系统(Evolved Packet System，EPS)承载的一部分数据分流到SeNB上传输，该EPS承载PDCP实体仍然在MeNB，而SeNB上是有独立的RLC实体。
其中，EPS是一个支持多种接入技术以及在多种接入间移动性的系统。在多接入场景下，终端可能处于多个第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)和/或非3GPP接入网络的共同覆盖下。这些接入网络可能使用不同的接入技术，可能属于不同的运营商，也可能提供到不同核心网的接入。
随着用户需求的增长和通信技术的发展，出现了越来越多无线通信技术和相关网络，例如可以提供广覆盖的2G/3G/4G移动通信技术及网络，以及可以提供热点覆盖的无线局域网(Wireless LAN，WLAN)网络，因此也大量出现了不同的通信网络共存的场景，例如，LTE网络和WLAN共存的场景。图3是一种典型的通用移动通信系统(Universal Mobile Telecommunications System，UMTS)/LTE和WLAN网络共存的场景。如图2所示，在UMTS/LTE的基站(UMTS中的Node B，LTE中的eNB)覆盖范围内，存在多个WLAN的接入点(Access Point，AP)。接入点的覆盖范围相对基站来说比较小。
在LTE聚合WLAN的情况，如何实现LTE侧的用户面数据在WLAN AP侧的分流，是当前业界需要解决的问题。
发明内容
本公开实施例提供了一种数据无线承载配置方法、数据传输方法及其设备，用以实现一个接入设备侧的用户面数据在另一个接入设备侧的分流。
本公开一些实施例提供的数据无线承载配置方法，包括：
第一接入设备获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
所述第一接入设备根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备之间经由所述第二接入设备的数据无线承载(DRB)；其中，第一接入设备与第二接入设备支持不同的接入技术；
所述第一接入设备与所述终端之间建立所述DRB的承载通道。
本公开一些实施例提供的数据无线承载配置方法，包括：
终端向第一接入设备上报所述终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
所述终端接收所述第一接入设备发送的配置请求，所述配置请求用于请求所述终端配置所述终端与所述第一接入设备之间经由第二接入设备分流的数据无线承载(DRB)；其中，所述第一接入设备与所述第二接入设备支持不同的接入方式；
所述终端与所述第一接入设备之间建立所述DRB的承载通道。
本公开一些实施例提供的数据传输方法，包括：
第一接入设备接收来自于核心网的用户面数据，将所述用户面数据通过与所述终端之间经由第二接入设备的DRB的承载通道发送给所述终端，其中，所述第一接入设备与第二接入设备采用不同的接入技术；和/或，
所述第一接入设备通过所述承载通道接收来自于所述终端的用户面数据，并将所述用户面数据向所述核心网发送。
本公开一些实施例提供的数据传输方法，包括：
终端将用户面数据通过与所述第一接收设备之间经由第二接入设备的DRB的承载通道发送给所述第一接入设备，其中，所述第一接入设备与第二接入设备采用不同的接入技术；和/或，
所述终端通过所述承载通道接收来自于所述第一接入设备的用户面数据。
本公开一些实施例提供的接入设备，包括：
获取模块，用于获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
承载配置请求模块，用于根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备之间经由所述第二接入设备的数据无线承载(DRB)；其中，第一接入设备与第二接入设备支持不同的接入技术；
承载配置模块，用于与所述终端之间建立所述DRB的承载通道。
本公开一些实施例提供的终端，包括：
上报模块，用于向第一接入设备上报所述终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
承载配置接收模块，用于接收所述第一接入设备发送的配置请求，所述配置请求用于请求所述终端配置所述终端与所述第一接入设备之间经由第二接入设备分流的数据无线承载(DRB)；其中，所述第一接入设备与所述第二接入设备支持不同的接入方式；
承载配置模块，用于与所述第一接入设备之间建立所述DRB的承载通道。
本公开一些实施例提供了一种接入设备，包括处理器，收发机和存储器；其中
所述处理器用于读取所述存储器中的计算机可读程序以执行下列操作：
获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备之间经由所述第二接入设备的数据无线承载(DRB)；其中，第一接入设备与第二接入设备支持不同的接入技术；
与所述终端之间建立所述DRB的承载通道；
所述收发机用于接收和发送数据；
所述存储器用于保存所述处理器执行操作时所使用的数据。
本公开一些实施例提供了一种终端，包括处理器，收发机和存储器；其中
所述处理器用于读取所述存储器中的计算机可读程序以执行下列操作：
向第一接入设备上报所述终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
接收所述第一接入设备发送的配置请求，所述配置请求用于请求所述终端配置所述终端与所述第一接入设备之间经由第二接入设备分流的数据无线承载(DRB)；其中，所述第一接入设备与所述第二接入设备支持不同的接入方式；
与所述第一接入设备之间建立所述DRB的承载通道；
所述收发机用于接收和发送数据；
所述存储器用于保存所述处理器执行操作时所使用的数据。
本公开的实施例中，第一接入设备和第二接入设备支持不同的接入方式。终端向第一接入设备上报其对用户面数据分流的支持能力信息，以使第一接入设备根据终端的该能力信息配置该终端建立与第一接入设备间的DRB的承载通道，该承载通道经由第二接入设备，从而使所述终端与所述第一接入设备可以通过该承载通道进行用户面数据的传输，即实现终端与第一接入设备之间的用户面数据通过第二接入设备进行分流的目的。
附图说明
图1为相关技术中LTE系统用户面协议栈示意图；
图2为相关技术中LTE双连接架构示意图；
图3为相关技术中UMTS/LTE和WLAN网络共存的场景示意图；
图4为本公开实施例提供的网络侧实现的DRB配置流程示意图；
图5为本公开实施例提供的终端侧实现的DRB配置流程示意图；
图6为本公开实施例提供的下行方向上的数据分流传输示意图；
图7为本公开实施例提供的上行方向上的数据分流传输示意图；
图8A为本公开实施例一的用户面协议栈结构示意图；
图8B和图8C为本公开实施例一的下行数据发送和接收示意图；
图8D和图8E为本公开实施例一的上行数据发送和接收示意图；
图9A为本公开实施例二的下行数据发送示意图；
图9B为本公开实施例二的上行数据接收示意图；
图10A为本公开实施例三的用户面协议栈结构示意图；
图10B和图10C为本公开实施例三的下行数据发送和接收示意图；
图10D和图10E为本公开实施例三的上行数据发送和接收示意图；
图11A为本公开实施例四的用户面协议栈结构示意图；
图11B和图11C为本公开实施例四的下行数据发送和接收示意图；
图11D和图11E为本公开实施例四的上行数据发送和接收示意图；
图12为本公开实施例五的用户面协议栈结构示意图；
图13为本公开实施例六的用户面协议栈结构示意图；
图14为本公开实施例提供的网络设备的结构示意图；
图15为本公开实施例提供的终端的结构示意图；
图16为本公开另一实施例提供的网络设备的结构示意图；
图17为本公开另一实施例提供的终端的结构示意图。
具体实施方式
本公开实施例，针对采用不同协议栈的接入设备共覆盖的场景，提出了一种数据无线承载配置方法，以及基于所配置的无线承载实现的数据传输方法，用以实现一个接入设备侧的用户面数据在另一个接入设备侧的分流。
以LTE与WLAN共覆盖的场景为例，本公开实施例提出了控制UE的用户面数据在LTE和WLAN侧灵活发送的方法，可以实现LTE承载数据和WLAN承载数据的并发，实现在不修改WLAN AP的情况下LTE承载的数据在WLAN上的分流 发送，有效利用了传统WLAN AP，提高了分流的效率和部署的灵活性。
为了使本公开的技术方案和优点更加清楚，下面将结合附图对本公开作进一步地详细描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本公开保护的范围。
参见图4，为本公开实施例提供的网络侧实现的DRB配置流程示意图，该流程可由网络侧设备实现。该流程可包括以下步骤：
步骤401：第一接入设备获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
步骤402：所述第一接入设备根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备之间经由所述第二接入设备分流的DRB；其中，第一接入设备与第二接入设备支持不同的接入技术；
步骤403：所述第一接入设备与所述终端之间建立所述DRB的承载通道。
相应地，根据上述流程，图5示出了终端侧实现的DRB配置流程，该流程可包括如下步骤：
步骤501：终端向第一接入设备上报所述终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
步骤502：所述终端接收所述第一接入设备发送的配置请求，所述配置请求用于请求所述终端配置所述终端与所述第一接入设备之间经由第二接入设备分流的DRB；其中，所述第一接入设备与所述第二接入设备支持不同的接入方式；
步骤503：所述终端与所述第一接入设备之间建立所述DRB的承载通道。
所述第一接入设备可以是LTE或其演进系统中的基站，所述第二接入设备可以是WLAN中的AP。
上述流程中，终端向第一接入设备发送的能力信息中可包括以下内容之一 或任意组合：
协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
所述终端的地址；
所述终端是否支持用户面数据经由第二接入设备分流的指示信息。
其中，所述能力信息中还可包括：所述终端已占用的端口的信息，和/或，所述终端建议使用的端口的信息。
上述流程中，第一接入设备发送给终端的用于指示所述终端配置所述DRB的信息，可包括以下内容之一或任意组合：
协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
所述承载通道的配置信息，所述承载通道的配置信息中至少包括：所述承载通道中的PDCP实体与逻辑信道标识的对应关系；
所述DRB的标识。
其中，建立所述承载通道所用的协议可包括以下之一：网际协议(IP)，传输控制协议(TCP)，用户数据报协议(UDP)，用户面通用分组无线业务协议(GTP-U)，超文本传输协议(HTTP)，超文本传输安全协议(HTTPS)。
如果所述承载通道为使用TCP协议建立的TCP或UDP连接，则所述承载通道的配置信息中还可包括：所述TCP或UDP连接的端口信息。
进一步地，在所述承载通道为使用TCP协议建立的TCP或UDP连接的情况下，所述第一接入设备指示所述终端配置所述DRB之前，还可根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流后，为所述终端对应的LC实体分配一个TCP或UDP端口，其中，所述终端的所述DRB对应配置有一个LC实体。
进一步地，在所述承载通道为使用TCP协议建立的TCP或UDP连接的情况下，所述第一接入设备也可预先为LC实体分配一个TCP或UDP端口，所述承 载通道的配置信息中还包括所述终端的标识，其中，所述终端的多个DRB承载对应配置有一个LC实体。
进一步地，在所述承载通道为使用TCP协议建立的TCP或UDP连接的情况下，所述第一接入设备还可在指示所述终端配置所述DRB之前，根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的需要经由第二接入设备分流的DRB分配对应的一个TCP或UDP端口。
如果所述承载通道为使用IP协议建立的IP连接，所述承载通道的配置信息中还包括：所述终端的标识信息。
如果所述承载通道中，所述终端与所述第二接入设备之间为用GTP-U协议建立的空口GTP-U连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息。
如果所述承载通道中，所述终端与所述第二接入设备之间为空口UDP或TCP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口UDP或TCP链接的配置信息。其中，所述UDP或TCP连接与所述终端唯一对应，或者与所述终端的需要经由第二接入设备分流的DRB唯一对应。
如果所述承载通道中，所述终端与所述第二接入设备之间为空口IP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口IP连接的配置信息。
如果所述承载通道中，所述第一接入设备与所述第二接入设备间的连接为GTP-U连接，则所述第一接入设备还要向所述第二接入设备发送GTP-U连接配置信息，所述GTP-U连接配置信息包括：
协议类型指示信息，所述协议类型指示信息指示的协议为GTP-U协议；
所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息，以及所述第一接入设备与所述第二接入设备之间的GTP-U连接的配置信息；
所述DRB的标识。
需要说明的是，所述承载通道包括下行通道和/或上行通道。
在终端与第一接入设备建立上述经由第二接入设备的承载通道后，就可以通过该承载通道进行用户面数据经第二接入设备进行分流传输。
具体来说，如图6所示，在下行方向上，第一接入设备接收来自于核心网的用户面数据，将所述用户面数据通过与所述终端之间经由第二接入设备的DRB的承载通道发送给所述终端，所述终端通过所述承载通道接收来自于所述第一接入设备的用户面数据。图6中的虚线表示第一接入设备发送的下行数据在通过第二接入设备进行分流传输的同时，也可以通过与终端之间的无线链路进行传输。
如图7所示，在上行方向上，终端将用户面数据通过与所述第一接收设备之间经由第二接入设备的DRB的承载通道发送给所述第一接入设备，所述第一接入设备通过所述承载通道接收来自于所述终端的用户面数据，并将所述用户面数据向所述核心网发送。图7中的虚线表示终端发送的上行数据在通过第二接入设备进行分流传输的同时，也可以通过与第一接入设备之间的无线链路进行传输。
本公开的上述实施例中，第一接入设备和第二接入设备支持不同的接入方式。终端向第一接入设备上报其对用户面数据分流的支持能力信息，以使第一接入设备根据终端的该能力信息配置该终端建立与第一接入设备间的DRB的承载通道，该承载通道经由第二接入设备，从而使所述终端与所述第一接入设备可以通过该承载通道进行用户面数据的传输，即实现终端与第一接入设备之间的用户面数据通过第二接入设备进行分流的目的。
根据建立所述承载通道所使用的协议的不同，该承载通道的配置过程以及通过该承载通道进行数据分流传输的过程也有所区别。下面将结合具体实施例对不同协议建立的承载通道的配置过程以及通过该承载通道进行的数据分流传输过程进行详细描述。
为了更清楚地理解本公开实施例，下面以LTE与WLAN共覆盖的场景为例，通过优选实施例对上述DRB配置流程以及用户面数据传输流程进行详细描述。
实施例一描述了采用TCP协议建立UE与eNB之间的DRB的承载通道，以实现通过WLAN AP对eNB与UE之间的用户面数据进行分流的方案。
实施例一的网络架构中，UE与eNB之间使用LTE无线通信协议进行交互，UE与WLAN AP之间使用Wi-Fi无线通信协议进行交互，eNB与WLAN AP之间通过有线方式连接，使用有线通信协议进行交互。
图8A为对应于实施例一的用户面协议栈架构。其中，UE中的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；UE中的Wi-Fi协议栈从上层到下层包括TCP层、IP层和MAC/PHY层；eNB的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；eNB的有线通信协议栈中从上层到下层包括TCP层、IP层和数据链路层(图中示为layer-2)。
实施例一中，对于接入eNB的UE1和UE2分别配置有LC实体(即逻辑信道实体)。UE1和UE2分别配置有两个EPS承载，两个EPS承载各自对应的PDCP实体分别表示为PDCP1和PDCP2。UE1和UE2均支持用户面数据分流，因此分别为两个UE各自对应的LC实体分配有TCP端口号，为UE1对应的LC实体分配的TCP端口号表示为Port1，为UE2对应的LC实体分配的TCP端口表示为Port2。PDCP实体与逻辑信道标识的对应关系为：PDCP1对应LC1，PDCP2对应LC2。
基于图8A所示的用户面协议栈架构并结合图4和图5所示的DRB配置流程，配置UE与eNB之间经由WLAN AP的DRB的信令流程具体可包括如下内容：
步骤1：UE向eNB上报该UE的能力信息，所述能力信息可以表明该UE对用户面数据分流传输的支持能力。
所述能力信息可包括如下内容：
协议类型指示信息，表明该UE建立DRB承载通道所使用的协议；本实施例中，该协议类型为TCP；
UE的地址，比如UE的IP地址；
UE是否支持用户面数据经由WLAN AP分流的指示信息；比如，该指示 信息可以是1个比特或多个比特的标识信息，通过不同的取值表示UE是否支持将用户面数据经由WLAN AP分流传输；本实施例中，该指示信息表明UE支持用户面数据经由WLAN AP分流；
端口列表，具体可包括UE已经占用的端口的列表，和/或，UE建议使用的端口的列表。
步骤2：eNB配置UE对WLAN AP进行测量。
步骤3：UE根据eNB的配置对WLAN AP进行测量并上报测量结果，所述测量结果中包括UE测量到的WLAN AP的标识等信息。
步骤4：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该UE发送重配置消息，以请求UE配置该UE与eNB之间经由WLAN AP的DRB。
其中，该重配置消息中可包括以下内容：
TCP协议类型指示信息，用以指示UE使用TCP协议建立DRB的承载通道；
DRB的承载通道的配置信息，即，建立该DRB的承载通道所需的配置信息；具体可包括：eNB的地址、TCP端口号，以及所述DRB通道中的PDCP实体与LCID(Logic ChannelID，逻辑信道标识)的对应关系等信息；其中，一个TCP端口号标识一个LC实体与TCP实体之间的TCP通道；本实施例中，可为每个支持将用户面数据经由WLAN AP分流的UE分配该UE唯一对应的一个TCP端口号；
需要重配置的DRB的标识，本实施例中即为UE与eNB之间经由WLAN AP的DRB的标识；
其他配置信息，具体可包括以下内容之一或组合：PDCP实体的信息、逻辑信道标识(LCID)、逻辑信道配置信息、MAC实体的信息、物理层实体的信息等。
步骤5：UE接收到eNB发送的重配置消息后，根据其中的配置信息，通过 WLAN接入网络向eNB发起连接建立请求。
进一步地，如果UE接收到的配置信息中的TCP端口号和其他应用使用的端口号发生了冲突，则UE可以反馈拒绝该DRB配置的响应信息，或者向eNB反馈该UE已占用的或建议使用的端口的列表。
步骤6：UE通过WLAN AP与eNB之间建立起基于TCP协议的承载通道。
进一步地，如果UE基于TCP协议的承载通道建立失败，则UE可以将承载通道建立失败的信息通知给eNB。
在上述流程中，也可以省略eNB配置UE进行WLAN AP测量以及接收UE上报的WLAN AP测量结果的步骤，UE可以直接向eNB上报该UE测量到的可用的WLAN AP的标识等信息。
UE通过WLAN接入网络与eNB在建立起上述承载通道后，可通过该承载通道向eNB发送用户面数据。如果UE在数据发送过程中，该承载通道连接失败，则UE可以将该承载通道连接失败的信息通知该eNB。
UE与eNB之间的用户面数据分流传输过程可如图8B和图8C以及图8D和图8E所示。其中，图8B和图8C分别示出了在eNB侧和UE侧实现的下行方向上的用户面数据传输流程，图8D和图8E分别示出了在eNB侧和UE侧实现的上行方向上的用户面数据传输流程。
参见图8B，eNB侧实现的下行方向上的用户面数据传输流程可如图中的粗实线所示，可包括如下步骤：
步骤1：eNB内的PDCP1接收来自高层的数据包，比如PDCP PDU。
步骤2：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给与该PDCP对应的LC实体。
步骤3：该LC实体对接收到的数据包进行处理，将处理后的数据包映射到逻辑信道并添加LCID(该LCID的值表示为LC1)，所添加的LCID与PDCP1对应，LC实体根据分配的TCP端口Port1，将处理后的数据包通过对应的TCP通道发送给TCP实体。
步骤4：TCP实体对接收到的数据包进行封装，得到TCP数据包，并将该TCP数据包发送给IP实体。
步骤5：IP实体对接收到的TCP数据包进行封装，得到IP数据包，并将该IP数据包通过IP路由方式发送给WLAN AP。该过程中，该IP数据包依次经过eNB中的数据链路层实体和物理层实体。
在WLAN AP中，eNB发送的IP数据包依次经过有线通信协议栈中的物理层实体、LLC实体、MAC实体、IP实体，以及Wi-Fi无线通信协议栈中的IP实体和MAC/PHY实体，向UE方向发送。
如图8C所示，UE从WLAN AP接收到数据后，其处理流程可如图中的粗实线所示，可包括如下步骤：
步骤1：UE内的Wi-Fi无线通信协议栈中的数据链路层实体(图中示为WLAN MAC+PHY+LLC)将接收到的数据包发送给IP实体。
步骤2：IP实体对接收到的数据包进行解封装和解析，根据协议类型将处理后的数据包发送给TCP实体。
步骤3：TCP实体根据为该UE的LC实体分配的TCP端口号Port1，将接收到的数据包通过对应的TCP通道发送给LC实体。
可选地，步骤3中，TCP实体也可以根据为适配层实体分配的TCP端口号，将接收到的数据包通过对应的TCP通道发送给LC实体。其中，所述适配层是指用于将PDCP层数据包发送给LC层，或将LC层数据包发送给PDCP层的协议层。
步骤4：LC实体根据接收到的数据包的包头中的LCID，以及LCID与PDCP实体的对应关系，将接收到的数据包发送给对应的PDCP实体：PDCP1。
步骤5：PDCP1将接收到的数据包发送给IP实体。
步骤6：IP实体根据协议类型将接收到的数据包发送给TCP实体。
步骤7：TCP实体根据为应用程序分配的TCP端口号Port2，将该TCP数据包通过该TCP端口对应的TCP通道发送给应用层实体(图中示为APP1)。
上述图8B和图8C所述的流程仅描述了下行方向上的用户面数据通过WLAN AP分流的传输过程。在实际应用中，eNB与UE间的下行方向上的用户面数据可以全部通过WLAN AP分流传输给UE，也可以部分数据通过WLAN AP分流到UE，另一部分数据仍通过eNB与UE之间的LTE协议的通信链路发送给UE，从而可以实现LTE承载数据和WLAN承载数据的并发。eNB通过LTE协议的通信链路向UE发送下行数据的过程以及相关的协议栈架构可参见LTE协议规定。
参见图8D，在UE侧实现的上行方向上的用户面数据的发送流程可如图中的粗实线所示，可包括如下步骤：
步骤1：应用层实体(图中所示的APP1)根据分配的TCP端口号Port2，将数据包通过对应的TCP通道发送给TCP实体。
步骤2：TCP实体将接收到的数据包进行处理，并将处理后的数据包发送给IP实体。
步骤3：IP实体根据接收到的数据包的IP头，将该数据包发送给对应的PDCP1。
步骤4：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给LC实体。
步骤5：LC实体对接收到的数据包进行处理，将处理后的数据包映射到逻辑信道并添加LCID(该LCID的值表示为LC1)后，根据为该LC实体分配的TCP端口号Port1，通过对应的TCP通道将处理后的数据包发送给TCP实体。
步骤6：TCP实体对接收到的数据包进行处理，并将处理后的数据包发送给IP实体。
步骤7：IP实体对接收到的数据包进行处理，并将处理后的数据包发送给Wi-Fi无线通信协议栈中的数据链路层实体(图中示为WLAN MAC+PHY+LLC)实体。该过程中，该数据包依次经过UE中的数据链路层实体和物理层实体。
在WLAN AP中，UE发送的IP数据包依次经过Wi-Fi无线通信协议栈中的数据链路层实体、IP实体，以及有线通信协议栈中的IP实体和MAC/PHY实体， 向eNB方向发送。
参见图8E，eNB接收到该用户面数据后的处理流程可如图中的粗实线所示，包括如下步骤：
步骤1：IP实体对从WLAN AP接收到的数据包进行处理，根据协议类型将处理后的数据包发送给TCP实体。
步骤2：TCP实体根据为LC实体分配的TCP端口号Port1，将接收到的数据包通过对应的TCP通道发送给对应的LC实体。
步骤3：LC实体对该数据包进行处理，根据接收到数据包的包头中的LCID(该LCID的值表示为LC1)，以及LCID与PDCP实体的对应关系，将该处理后的数据包发送给对应的PDCP1。
步骤4：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给高层。
上述图8D和图8E所述的流程仅描述了上行方向上的用户面数据通过WLAN AP分流的传输过程。在实际应用中，eNB与UE间的上行方向上的用户面数据可以全部通过WLAN AP分流传输给eNB，也可以部分数据通过WLAN AP分流到eNB，另一部分数据仍通过eNB与UE之间的LTE协议的通信链路发送给eNB，从而可以实现LTE承载数据和WLAN承载数据的并发。UE通过LTE协议的通信链路向eNB发送上行数据的过程以及相关的协议栈架构可参见LTE协议规定。
需要说明的是，上述图8B、图8C、图8D和图8E所述的流程中，未对各协议实体的数据处理过程进行详细说明，上述各协议实体的数据处理过程可参见相关通信协议的规定。
需要说明的是，实施例一是以UE与eNB之间且经由WLAN AP的承载通道是TCP连接为例描述的，该承载通道也可以用UDP连接代替，如果该承载通道为UDP连接，则其承载通道配置过程以及数据分流的过程可重用上述流程，不同之处在于：在承载通道的信令配置流程中步骤4中指定UDP协议类型，并指 定UDP协议的端口号。后续UE和网络侧之间建立UDP连接并可通过UDP端口发送和接收数据。
实施例二描述了采用TCP协议建立DRB的承载通道以实现通过WLAN AP对eNB与UE之间的用户面数据进行分流的方案。
实施例二的用户面协议栈架构与实施例一相同，具体可参见图8A。
实施例二中，对于接入eNB的UE1和UE2，共享一个LC实体，并共享一个TCP端口，该TCP端口的端口号表示为Port1。UE1和UE2分别配置有两个EPS承载，两个EPS承载各自对应的PDCP实体分别表示为PDCP1和PDCP2。UE1和UE2均支持用户面数据分流。PDCP实体与逻辑信道标识的对应关系为：PDCP1对应LC1，PDCP2对应LC2。
基于图8A所示的用户面协议栈架构并结合图4和图5所示的DRB配置流程，配置UE与eNB之间经由WLAN AP的DRB的信令流程具体可包括如下内容：
步骤1：UE向eNB上报该UE的能力信息，所述能力信息可以表明该UE对用户面数据经由WLAN AP分流传输的支持能力。所述能力信息中可包含的内容可参见实施例一中的相关描述。
步骤2：eNB配置UE对WLAN AP进行测量。
步骤3：UE根据eNB的配置对WLAN AP进行测量并上报测量结果，所述测量结果中包括UE测量到的WLAN AP的标识等信息。
步骤4：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该UE发送重配置消息，以请求UE配置该UE与eNB之间经由WLAN AP的DRB。所述重配置消息中可包含的内容可参见实施例一中的相关描述。
由于本实施例二中，接入eNB的多个UE共享一个LC实体，因此为UE分配的TCP端口号也为这些UE所共享，该TCP端口号可由eNB静态分配，即预先分配。基于所有接入eNB的UE共享一个TCP端口号，因此需要在所述重配 置消息中包含UE的标识信息，以使eNB根据UE的标识信息区分来自不同UE的上行数据。
步骤5：UE接收到eNB发送的重配置消息后，根据其中的配置信息，通过WLAN接入网络向eNB发起连接建立请求。
进一步地，如果UE接收到的配置信息中的TCP端口号和其他应用使用的端口号发生了冲突，则UE可以反馈拒绝该DRB配置的响应信息，或者向eNB反馈该UE已占用的或建议使用的端口的列表。
步骤6：UE通过WLAN AP与eNB之间建立起基于TCP协议的承载通道。
进一步地，如果UE基于TCP协议的承载通道建立失败，则UE可以将承载通道建立失败的信息通知给eNB。
在上述流程中，也可以省略eNB配置UE进行WLAN AP测量以及接收UE上报的WLAN AP测量结果的步骤，UE可以直接向eNB上报该UE测量到的可用的WLAN AP的标识等信息。
UE通过WLAN接入网络与eNB在建立起上述承载通道后，可通过该承载通道向eNB发送用户面数据。如果UE在数据发送过程中，该承载通道连接失败，则UE可以将该承载通道连接失败的信息通知该eNB。
实施例二中，对于接入eNB的UE1和UE2配置有同一个LC实体。UE1和UE2分别配置有两个EPS承载，两个EPS承载各自对应的PDCP实体分别表示为PDCP1和PDCP2。UE1和UE2均支持用户面数据分流，且UE1和UE2共享同一个TCP端口号Port1。PDCP实体与逻辑信道标识的对应关系为：PDCP1对应LC1，PDCP2对应LC2。
eNB发送下行数据的过程可如图9A所示；UE接收下行数据的过程与实施例一中的相关过程相同，具体可参见图8C；UE发送上行数据的过程与实施例一中的相关过程基本相同，具体可参见图8D，与图8D所示流程有所区别的是，在步骤5中，LC实体将数据包发送给TCP实体之前，需要在该数据包中添加该UE的标识信息；eNB接收上行数据的过程可如图9B所示。下面仅结合图9A 和图9B描述eNB侧的处理过程，UE侧的处理过程可参见实施例一，在此不再重复。
参见图9A，eNB发送下行数据的流程可如图中的粗实线所示，可包括如下步骤：
步骤1：eNB内的PDCP1接收来自高层的数据包，比如PDCP PDU。
步骤2：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给与所有接入UE共享的LC实体。
步骤3：LC实体对接收到的数据包进行处理，将处理后的数据包映射到逻辑信道并添加LCID(该LCID的值表示为LC1)，所添加的LCID与PDCP1对应，LC实体根据多个UE共享的TCP端口Port1，将处理后的数据包通过对应的TCP通道发送给TCP实体。
步骤4：TCP实体对接收到的数据包进行封装，得到TCP数据包，并将该TCP数据包发送给IP实体。
步骤5：IP实体对接收到的TCP包进行封装，得到IP数据包，并将该IP数据包通过IP路由方式发送给WLAN AP。该过程中，该IP数据包依次经过eNB中的数据链路层实体和物理层实体。
上述图流程仅描述了下行方向上的用户面数据通过WLAN AP分流的传输过程。在实际应用中，eNB与UE间的下行方向上的用户面数据可以全部通过WLAN AP分流传输给UE，也可以部分数据通过WLAN AP分流到UE，另一部分数据仍通过eNB与UE之间的LTE协议的通信链路发送给UE，从而可以实现LTE承载数据和WLAN承载数据的并发。eNB通过LTE协议的通信链路向UE发送下行数据的过程以及相关的协议栈架构可参见LTE协议规定。
参见图9B，eNB接收上行数据的流程可如图中的粗实线所示，可包括如下步骤：
步骤1：IP实体对从WLAN AP接收到的数据包进行处理，将处理后的数据包发送给TCP实体。
步骤2：TCP实体根据多个UE共享的TCP端口号Port1，将接收到的数据包通过对应的TCP通道发送给多个UE共享的LC实体。
步骤3：LC实体对该数据包进行处理，根据接收到数据包的包头中的UE的标识信息，以及LCID(该LCID的值表示为LC1)、LCID与PDCP实体的对应关系，将该处理后的数据包发送给该UE对应的PDCP1。
步骤4：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给高层。
上述流程仅描述了上行方向上的用户面数据通过WLAN AP分流的传输过程。在实际应用中，eNB与UE间的上行方向上的用户面数据可以全部通过WLAN AP分流传输给eNB，也可以部分数据通过WLAN AP分流到eNB，另一部分数据仍通过eNB与UE之间的LTE协议的通信链路发送给eNB，从而可以实现LTE承载数据和WLAN承载数据的并发。UE通过LTE协议的通信链路向eNB发送上行数据的过程以及相关的协议栈架构可参见LTE协议规定。
需要说明的是，上述流程中，未对各协议实体的数据处理过程进行详细说明，上述各协议实体的数据处理过程可参见相关通信协议的规定。
需要说明的是，实施例二是以UE与eNB之间且经由WLAN AP的承载通道是TCP连接为例描述的，该承载通道也可以用UDP连接代替。如果该承载通道为UDP连接，则其承载通道配置过程以及数据分流的过程可重用上述流程，不同之处在于：在承载通道的信令配置流程中步骤4中指定UDP协议类型，并指定UDP协议的端口号。后续UE和网络侧之间建立UDP连接并可通过UDP端口发送和接收数据。
实施例三描述了采用IP协议建立DRB的承载通道以实现通过WLAN AP对eNB与UE之间的用户面数据进行分流的方案。
实施例三的网络架构中，UE与eNB之间使用LTE无线通信协议进行交互，UE与WLAN AP之间使用Wi-Fi无线通信协议进行交互，eNB与WLAN AP之间通过有线方式连接，使用有线通信协议进行交互。
图10A为实施例三中的用户面协议栈架构。其中，UE中的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；UE中的Wi-Fi协议栈从上层到下层包括IP层和MAC/PHY层；eNB的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；eNB的有线通信协议栈中从上层到下层包括IP层和数据链路层(图中示为layer-2)。
实施例三中，对于接入eNB的UE1和UE2配置有共享的LC实体。UE1和UE2分别配置有两个EPS承载，两个EPS承载各自对应的PDCP实体分别表示为PDCP1和PDCP2。UE1和UE2均支持用户面数据分流，PDCP实体与逻辑信道标识的对应关系为：PDCP1对应LC1，PDCP2对应LC2。
基于图10A所示的用户面协议栈架构并结合图4和图5所示的DRB配置流程，配置UE与eNB之间经由WLAN AP的DRB的信令流程具体可包括如下内容：
步骤1：UE向eNB上报该UE的能力信息，所述能力信息可以表明该UE对用户面数据分流传输的支持能力。所述能力信息中可包含的内容可参见实施例一中的相关描述。
步骤2：eNB配置UE对WLAN AP进行测量。
步骤3：UE根据eNB的配置对WLAN AP进行测量并上报测量结果，所述测量结果中包括UE测量到的WLAN AP的标识等信息。
步骤4：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该UE发送重配置消息，以请求UE配置该UE与eNB之间经由WLAN AP的DRB。
其中，该重配置消息中可包括以下内容：
IP协议类型指示信息，用以指示UE使用IP协议建立DRB的承载通道；DRB的承载通道的配置信息，即，建立该DRB的承载通道所需的配置信息；具体可包括：eNB的地址、UE的标识，以及所述DRB通道中的PDCP实体与LCID的对应关系等信息；
需要重配置的DRB的标识，本实施例中即为UE与eNB之间经由WLAN AP 的DRB的标识；
其他配置信息，具体可包括以下内容之一或组合：PDCP实体的信息、MAC实体的信息、物理层实体的信息等。
步骤5：UE接收到eNB发送的重配置消息后，根据其中的配置信息，通过WLAN接入网络向eNB发起连接建立请求。
步骤6：UE通过WLAN AP与eNB之间建立起基于IP协议的承载通道。
在上述流程的步骤5中，UE在接收到重配置消息后，也可不通过WLAN接入网络向eNB发起连接建立请求，而是直接通过WLAN接入网络向eNB发送数据。相应地，在步骤6中，eNB在接收到UE发送的数据后，向UE反馈承载通道建立成功的响应消息，或者直接通过WLAN接入网络向该UE发送数据。
在上述流程中，也可以省略eNB配置UE进行WLAN AP测量以及接收UE上报的WLAN AP测量结果的步骤，UE可以直接向eNB上报该UE测量到的可用的WLAN AP的标识等信息。
UE通过WLAN接入网络与eNB在建立起上述承载通道后，可通过该承载通道向eNB发送用户面数据。如果UE在数据发送过程中，该承载通道连接失败，则UE可以将该承载通道连接失败的信息通知该eNB。
参见图10B，eNB发送下行数据的流程可如图中的粗实线所示，可包括如下步骤：
步骤1：eNB内的PDCP1接收来自高层的数据包，比如PDCP PDU。
步骤2：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给多个UE共享的LC实体。
步骤3：LC实体对接收到的数据包进行处理，将处理后的数据包映射到逻辑信道并添加LCID(该LCID的值表示为LC1)，所添加的LCID与PDCP1对应，LC实体将处理后的数据包发送给IP实体。
步骤4：IP实体对接收到的数据包进行封装，在IP包头中指定用于LC层数据包传输的新的协议类型，并将封装后的数据包通过IP路由方式发送。 该过程中，该IP数据包依次经过eNB中的数据链路层实体和物理层实体。所述新的协议类型为LC层数据包协议类型，可表示为“LC协议”。
如图10C所示，UE从WLAN AP接收到数据后，其处理流程可如图中的粗实线所示，可包括如下步骤：
步骤1：UE内的Wi-Fi无线通信协议栈中的数据链路层实体(图中示为WLAN MAC+PHY+LLC)将接收到的数据包发送给IP实体。
步骤2：IP实体对接收到的数据包进行解封装和解析，根据协议类型将处理后的数据包发送给LC实体。其中，所述协议类型可以是IP层用于LC层数据包传输的新的协议类型。
步骤3：LC实体根据接收到的数据包的包头中的LCID，以及LCID与PDCP实体的对应关系，将接收到的数据包发送给对应的PDCP实体：PDCP1。
步骤4：PDCP1将接收到的数据包发送给IP实体。
步骤5：IP实体根据协议类型将接收到的数据包发送给TCP实体。
步骤6：TCP实体根据为应用程序分配的TCP端口号Port1，将该TCP数据包通过该TCP端口对应的TCP通道发送给应用层实体(图中示为APP1)。
上述图流程仅描述了下行方向上的用户面数据通过WLAN AP分流的传输过程。在实际应用中，eNB与UE间的下行方向上的用户面数据可以全部通过WLAN AP分流传输给UE，也可以部分数据通过WLAN AP分流到UE，另一部分数据仍通过eNB与UE之间的LTE协议的通信链路发送给UE，从而可以实现LTE承载数据和WLAN承载数据的并发。eNB通过LTE协议的通信链路向UE发送下行数据的过程以及相关的协议栈架构可参见LTE协议规定。
参见图10D，在UE侧实现的上行方向上的用户面数据的发送流程可如图中的粗实线所示，可包括如下步骤：
步骤1：应用层实体(图中所示的APP1)根据分配的TCP端口号Port2，将数据包通过对应的TCP通道发送给TCP实体。
步骤2：TCP实体将接收到的数据包进行处理，并将处理后的数据包发送 给IP实体。
步骤3：IP实体根据接收到的数据包的IP头，将该数据包发送给对应的PDCP1。
步骤4：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给LC实体。
步骤5：LC实体对接收到的数据包进行处理，将处理后的数据包映射到逻辑信道并添加LCID(该LCID的值表示为LC1)后，将处理后的数据包发送给IP实体。
步骤6：IP实体对接收到的数据包进行处理，根据来自LC层的数据包，比如根据该数据包中的LCID，在IP包头中指定用于LC层数据包传输的新的协议类型，并将处理后的数据包发送给Wi-Fi无线通信协议栈中的数据链路层实体(图中示为WLAN MAC+PHY+LLC)实体。该过程中，该数据包依次经过UE中的数据链路层实体和物理层实体。所述新的协议类型为LC层数据包协议类型，可表示为“LC协议”。
在WLAN AP中，UE发送的IP数据包依次经过Wi-Fi无线通信协议栈中的数据链路层实体、IP实体，以及有线通信协议栈中的IP实体和MAC/PHY实体，向eNB方向发送。
参见图10E，eNB接收到该用户面数据后的处理流程可如图中的粗实线所示，包括如下步骤：
步骤1：IP实体对从WLAN AP接收到的数据包进行处理，根据该数据包的协议类型将处理后的数据包发送给LC实体。所述协议类型可以是IP层用于LC层数据包传输的新的协议类型。所述新的协议类型为LC层数据包协议类型，可表示为“LC协议”。
步骤2：LC实体对接收到的数据包进行处理，根据接收到数据包的包头中的LCID(该LCID的值表示为LC1)，以及LCID与PDCP实体的对应关系，将该处理后的数据包发送给对应的PDCP1。
步骤3：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给高层。
上述图10D和图10E所述的流程仅描述了上行方向上的用户面数据通过WLAN AP分流的传输过程。在实际应用中，eNB与UE间的上行方向上的用户面数据可以全部通过WLAN AP分流传输给eNB，也可以部分数据通过WLAN AP分流到eNB，另一部分数据仍通过eNB与UE之间的LTE协议的通信链路发送给eNB，从而可以实现LTE承载数据和WLAN承载数据的并发。UE通过LTE协议的通信链路向eNB发送上行数据的过程以及相关的协议栈架构可参见LTE协议规定。
需要说明的是，上述图10B、图10C、图10D和图10E所述的流程中，未对各协议实体的数据处理过程进行详细说明，上述各协议实体的数据处理过程可参见相关通信协议的规定。
实施例四描述了采用GTP-U协议建立DRB的承载通道以实现通过WLAN AP对eNB与UE之间的用户面数据进行分流的方案。
实施例四的网络架构中，UE与eNB之间使用LTE无线通信协议进行交互，UE与WLAN AP之间使用Wi-Fi无线通信协议进行交互，eNB与WLAN AP之间通过有线方式连接，使用有线通信协议进行交互。
图11A为实施例四中的用户面协议栈架构。其中，UE中的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；UE中的Wi-Fi协议栈从上层到下层包括GTP-U层、UDP层、IP层和MAC/PHY层；eNB的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；eNB的有线通信协议栈中从上层到下层包括GTP-U层、UDP层、IP层和数据链路层(图中示为layer-2)。
实施例四中，对于接入eNB的UE1和UE2分别配置有LC实体。UE1和UE2分别配置有两个EPS承载，两个EPS承载各自对应的PDCP实体分别表示为PDCP1和PDCP2。PDCP实体与逻辑信道标识的对应关系为：PDCP1对应LC1， PDCP2对应LC2。
基于图11A所示的用户面协议栈架构并结合图4和图5所示的DRB配置流程，配置UE与eNB之间经由WLAN AP的DRB的信令流程具体可包括如下内容：
步骤1：UE向eNB上报该UE的能力信息，所述能力信息可以表明该UE对用户面数据分流传输的支持能力。
所述能力信息可包括如下内容：
协议类型指示信息，表明该UE建立DRB承载通道所使用的协议。本实施例中，该协议类型为GTP-U；
UE是否支持用户面数据经由WLAN AP分流的指示信息；本实施例中，该指示信息表明UE支持用户面数据经由WLAN AP分流。
步骤2：eNB配置UE对WLAN AP进行测量。
步骤3：UE根据eNB的配置对WLAN AP进行测量并上报测量结果，所述测量结果中包括UE测量到的WLAN AP的标识等信息。
步骤4：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该WLAN AP发送配置消息，以使该WLAN AP配置该WLAN AP与UE间的空口GTP-U连接，以及该WLAN AP与eNB间的GTP-U连接。
eNB向WLAN AP发送的配置消息中可包括以下连接配置信息：
GTP-U协议的指示信息，以指示WLAN AP建立GTP-U连接；
UE与WLAN AP之间的空口GTP-U连接的配置信息，具体可包括：UE与WLAN AP之间的空口GTP-U连接在WLAN AP侧的GTP-U隧道端点标识(TEID)，该空口GTP-U连接在UE侧的GTP-U TEID等，用于标识UE的GTU-U空口连接；
eNB与WLAN AP之间的GTP-U连接的配置信息，该GTP-U连接与该UE对应；该GTP-U连接的配置信息具体可包括：eNB与WLAN AP之间的GTP-U连接在该eNB和该WLAN AP侧的接口的GTP-U TEID；
重配置的DRB标识。
步骤5：WLAN AP根据步骤4中的配置信息，在接受该配置后，建立UE在WLAN AP侧的空口GTP-U连接(为便于描述，称其为GTP-U连接1)，以及建立WLAN AP和eNB之间的GTP-U连接(为便于描述，称其为GTP-U连接2)，并建立上述GTP-U连接1和GTP-U连接2的对应关系。其中，WLAN AP和eNB之间的GTP-U连接与该UE对应。
进一步地，WLAN AP向eNB发送配置确认消息。所述配置确认消息中可包括以下信息：上述GTP-U连接1的GTP-U TEID，还可以包括上述GTP-U连接2的配置信息，比如，GTP-U连接1在WLAN AP侧的GTP-U TEID，以及在UE侧的GTP-U TEID等。
步骤6：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该UE发送重配置消息，以请求UE配置该UE与eNB之间经由WLAN AP的DRB。
其中，该重配置消息中可包括以下内容：
GTP-U协议类型指示信息，用以指示UE使用GTP-U协议建立DRB的承载通道；
DRB的承载通道的配置信息。具体可包括：所述DRB通道中的PDCP实体与逻辑信道标识(Logic Channel ID，LCID)的对应关系等信息，以及该UE与该WLAN AP之间的空口GTP-U连接的配置信息，比如可包括：该空口GTP-U连接在WLAN AP侧的GTP-U TEID，该空口GTP-U连接在UE侧的GTP-U TEID等，用于标识UE的GTU-U空口连接；
需要重配置的DRB的标识，本实施例中即为UE与eNB之间经由WLAN AP的DRB的标识；
其他配置信息，具体可包括以下内容之一或组合：PDCP实体的信息、逻辑信道标识(LCID)、逻辑信道配置信息、MAC实体的信息、物理层实体的信息等。
步骤7：UE接收到eNB发送的重配置消息后，根据其中的配置信息，建立与WLAN AP之间的空口GTP-U连接，并通过该空口GTP-U连接，通过WLAN接入网络进行数据收发。进一步地，UE可向eNB反馈配置成功消息。
步骤8：eNB在接收到UE的配置成功消息后，或根据步骤5中的配置确认消息，通过与该UE对应的与WLAN AP之间的GTP-U连接(上述GTP-U连接2)与该UE进行数据收发。
在上述流程中，也可以省略eNB配置UE进行WLAN AP测量以及接收UE上报的WLAN AP测量结果的步骤，UE可以直接向eNB上报该UE测量到的可用的WLAN AP的标识等信息。
上述承载配置流程中，步骤4和步骤6的执行顺序没有严格要求，比如可以先执行步骤6再执行步骤4，也可以同时执行。
UE通过WLAN接入网络与eNB在建立起上述承载通道后，可通过该承载通道向eNB发送用户面数据。如果UE在数据发送过程中，该承载通道连接失败，则UE可以将该承载通道连接失败的信息通知该eNB。
UE与eNB之间的用户面数据分流传输过程可如图11B和图11C以及图11D和图11E所示。其中，图11B和图11C分别示出了在eNB侧和UE侧实现的下行方向上的用户面数据传输流程，图11D和图11E分别示出了在eNB侧和UE侧实现的上行方向上的用户面数据传输流程。
参见图11B，eNB侧的下行数据发送流程可如图中的粗实线所示，可包括如下步骤：
步骤1：eNB内的PDCP1接收来自高层的数据包，比如PDCP PDU。
步骤2：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给与该PDCP对应的LC实体。
步骤3：该LC实体对接收到的数据包进行处理，将处理后的数据包映射到逻辑信道并添加LCID(该LCID的值表示为LC1)，所添加的LCID与PDCP1对应，LC实体将处理后的数据包发送给GTP-U实体。
步骤4：GTP-U实体根据GTP-U TEID与LC实体的对应关系，将该数据通过对应的GTP-U隧道发送给WLAN AP。
WLAN AP根据Xw接口的GTP-U的Xw TEID与WLAN空口的GTP-U连接的WLAN TEID的对应关系，将接收到的数据通过UE在WLAN AP侧的空口的GTP-U连接发送给UE。
如图11C所示，UE侧的下行数据接收流程可如图中的粗实线所示，可包括如下步骤：
步骤1：UE内的Wi-Fi无线通信协议栈中的数据链路层实体(图中示为WLAN MAC+PHY+LLC)根据协议类型，将接收到的数据包发送给IP实体。
步骤2：IP实体根据协议类型对接收到的数据包进行解封装和解析，得到UDP包，将该UDP包发送给UDP实体。
步骤3：UDP实体对接收到的数据包进行处理得到GTP数据包，根据协议类型将该GTP数据包发送给GTP-U实体。
步骤4：GTP-U实体根据支持的协议类型或应用类型，将该GTP数据包发送给LC实体。所述协议类型或应用类型是为LC层数据收发定义的新的类型。
步骤5：LC实体根据接收到的数据包的包头中的LCID，以及LCID与PDCP实体的对应关系，将该数据包发送给对应的PDCP实体：PDCP1。
步骤5：PDCP1将接收到的数据包发送给IP实体。
步骤6：IP实体根据协议类型，将该UDP数据包发送给UDP实体。
步骤7：UDP实体根据为应用程序分配的TCP端口号Port2，将该UDP数据包通过该UDP端口对应的UDP通道发送给应用层实体(图中示为APP1)。
上述流程中的GTP-U连接是基于UDP协议的。如果GTP-U连接是基于TCP协议的，则在步骤2中，IP实体将数据包发送给TCP实体；在步骤3中，TCP实体将数据包发送给GTP-U实体；在步骤6中，IP实体将数据包发送给TCP实体；在步骤7中，TCP实体将数据包发送给应用层实体。
上述图11B和图11C所述的流程仅描述了下行方向上的用户面数据通过 WLAN AP分流的传输过程。在实际应用中，eNB与UE间的下行方向上的用户面数据可以全部通过WLAN AP分流传输给UE，也可以部分数据通过WLAN AP分流到UE，另一部分数据仍通过eNB与UE之间的LTE协议的通信链路发送给UE，从而可以实现LTE承载数据和WLAN承载数据的并发。eNB通过LTE协议的通信链路向UE发送下行数据的过程以及相关的协议栈架构可参见LTE协议规定。
参见图11D，在UE侧实现的上行方向上的用户面数据的发送流程可如图中的粗实线所示，可包括如下步骤：
步骤1：应用层实体(图中所示的APP1)根据分配的UDP端口号Port2，将数据包通过对应的UDP通道发送给UDP实体。
步骤2：UDP实体将接收到的数据包进行处理，并将处理后的数据包发送给IP实体。
步骤3：IP实体根据接收到的数据包的IP头，将该数据包发送给对应的PDCP1。
步骤4：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给LC实体。
步骤5：LC实体对接收到的数据包进行处理，将处理后的数据包映射到逻辑信道并添加LCID(该LCID的值表示为LC1)后，将处理后的数据包发送给GTP-U实体。
步骤6：GTP-U实体根据GTP-U TEID与LC实体的对应关系，在数据包中加上GTP头后发送给UDP实体，以便将数据包通过WLAN AP空口对应的GTP-U隧道发送给WLAN AP。
步骤7：UDP实体将数据包发送给IP实体。
步骤8：IP实体对接收到的数据包进行处理，并将处理后的数据包发送给Wi-Fi无线通信协议栈中的数据链路层实体(图中示为WLAN MAC+PHY+LLC)实体。该过程中，该数据包依次经过UE中的数据链路层实体和物理层实体。
上述流程中的GTP-U连接是基于UDP协议的。如果GTP-U连接是基于TCP 协议的，则在步骤1中，应用层实体将数据包发送给TCP实体；在步骤2中，TCP实体将数据包发送给IP实体；在步骤6中，GTP-U实体将数据包发送给TCP实体；在步骤7中，TCP实体将数据包发送给IP实体。
WLAN AP接收到该UE发送的数据后，根据Xw接口的GTP-U的Xw TEID连接与WLAN空口的GTP-U连接的WLAN TEID的对应关系，将接收到的数据通过UE在eNB侧的GTP-U连接发送给eNB。
参见图10E，eNB接收到该用户面数据后的处理流程可如图中的粗实线所示，包括如下步骤：
步骤1：GTP-U实体根据数据包的协议类型或应用类型，以及UE的Xw TEID，将数据包发送给该UE对应的LC实体。
步骤2：LC实体对该数据包进行处理，根据接收到数据包的包头中的LCID(该LCID的值表示为LC1)，以及LCID与PDCP实体的对应关系，将该处理后的数据包发送给对应的PDCP1。
步骤3：PDCP1对接收到的数据包进行处理，并将处理后的数据包发送给高层。
上述图11D和图11E所述的流程仅描述了上行方向上的用户面数据通过WLAN AP分流的传输过程。在实际应用中，eNB与UE间的上行方向上的用户面数据可以全部通过WLAN AP分流传输给eNB，也可以部分数据通过WLAN AP分流到eNB，另一部分数据仍通过eNB与UE之间的LTE协议的通信链路发送给eNB，从而可以实现LTE承载数据和WLAN承载数据的并发。UE通过LTE协议的通信链路向eNB发送上行数据的过程以及相关的协议栈架构可参见LTE协议规定。
实施例五描述了UE与WLAN AP之间的承载通道为空口UDP连接，WLAN AP与eNB之间的承载通道为GTP-U连接的情况下，实现通过WLAN AP对eNB与UE之间的用户面数据进行分流的方案。
实施例五的网络架构中，UE与eNB之间使用LTE无线通信协议进行交互， UE与WLAN AP之间使用Wi-Fi无线通信协议进行交互，eNB与WLAN AP之间通过有线方式连接，使用有线通信协议进行交互。
图12为实施例五中的用户面协议栈架构。其中，UE中的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；UE中的Wi-Fi协议栈从上层到下层包括UDP层、IP层和MAC/PHY层；eNB的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；eNB的有线通信协议栈中从上层到下层包括GTP-U层、UDP层、IP层和数据链路层(图中示为layer-2)。
基于图12所示的用户面协议栈架构并结合图4和图5所示的DRB配置流程，配置UE与eNB之间经由WLAN AP的DRB的信令流程具体可包括如下内容：
步骤1：UE向eNB上报该UE的能力信息，所述能力信息可以表明该UE对用户面数据分流传输的支持能力。
所述能力信息可包括如下内容：
协议类型指示信息，表明该UE建立DRB承载通道所使用的协议。本实施例中，该协议类型为UDP；
UE是否支持用户面数据经由WLAN AP分流的指示信息；本实施例中，该指示信息表明UE支持用户面数据经由WLAN AP分流。
步骤2：eNB配置UE对WLAN AP进行测量。
步骤3：UE根据eNB的配置对WLAN AP进行测量并上报测量结果，所述测量结果中包括UE测量到的WLAN AP的标识等信息。
步骤4：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该WLAN AP发送配置消息，以使该WLAN AP配置该WLAN AP与UE间的UDP连接，以及该WLAN AP与eNB间的GTP-U连接。
eNB向WLAN AP发送的配置消息中可包括以下连接配置信息：
UDP协议的指示信息，以指示WLAN AP建立UDP连接；
UE与WLAN AP之间的UDP连接的配置信息，具体可包括：UE与WLAN AP 之间的空口UDP连接在WLAN AP侧的端口号，该空口UDP连接在UE侧的端口号，用于建立该空口UDP连接的UE的IP地址以及WALN AP的IP地址等；其中，该UDP连接与该UE相对应，如果该UE存在多个DRB，则该UE的这些DRB共享该UDP连接；
重配置的DRB标识。
步骤5：WLAN AP根据步骤4中的配置信息，在接受该配置后，建立UE在WLAN AP侧的空口UDP连接，以及建立WLAN AP和eNB之间的GTP-U连接，并建立两者的对应关系，两者的对应关系可通过空口UDP连接的端口号与GTP-U连接的TEID之间的对应关系来表示。其中，WLAN AP和eNB之间的GTP-U连接与该UE对应。
进一步地，WLAN AP向eNB发送配置确认消息。所述配置确认消息中可包括以下信息：上述GTP-U连接的GTP-U TEID，还可以包括上述空口UDP连接的配置信息，比如，空口UDP连接在WLAN AP侧的端口号和IP地址，以及在UE侧的端口号和IP地址等，还可以包括上述空口UDP连接与上述GTP-U连接的对应关系。
步骤6：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该UE发送重配置消息，以请求UE配置该UE与eNB之间经由WLAN AP的DRB。
其中，该重配置消息中可包括以下内容：
UDP协议类型指示信息，用以指示UE使用UDP协议建立DRB的承载通道；
DRB的承载通道的配置信息。具体可包括：所述DRB通道中的PDCP实体与LCID的对应关系等信息，以及该UE与该WLAN AP之间的空口UDP连接的配置信息，比如可包括：该空口UDP连接在WLAN AP侧的端口号和IP地址，该空口UDP连接在UE侧的端口号和IP地址等。
需要重配置的DRB的标识，本实施例中即为UE与eNB之间经由WLAN AP 的DRB的标识；
其他配置信息，具体可包括以下内容之一或组合：PDCP实体的信息、逻辑信道标识(LCID)、逻辑信道配置信息、MAC实体的信息、物理层实体的信息等。
步骤7：UE接收到eNB发送的重配置消息后，根据其中的配置信息，建立与WLAN AP之间的空口UDP连接，并通过该空口UDP连接，通过WLAN接入网络进行数据收发。进一步地，UE可向eNB反馈配置成功消息。
步骤8：eNB在接收到UE的配置成功消息后，或根据步骤5中的配置确认消息，通过与该UE对应的与WLAN AP之间的GTP-U连接与该UE进行数据收发。
在上述流程中，也可以省略eNB配置UE进行WLAN AP测量以及接收UE上报的WLAN AP测量结果的步骤，UE可以直接向eNB上报该UE测量到的可用的WLAN AP的标识等信息。
上述承载配置流程中，步骤4和步骤6的执行顺序没有严格要求，比如可以先执行步骤6再执行步骤4，也可以同时执行。
可选地，UE与WLAN AP之间也可以建立空口TCP连接来取代上述空口UDP连接。如果UE与WLAN AP之间建立空口TCP连接，则其承载通道配置过程与上述流程类似，只是需要将UDP协议类型替换为TCP协议类型，将UDP端口替换为TCP端口。
UE通过WLAN接入网络与eNB在建立起上述承载通道后，可通过该承载通道向eNB发送用户面数据。如果UE在数据发送过程中，该承载通道连接失败，则UE可以将该承载通道连接失败的信息通知该eNB。
eNB发送下行数据的过程与实施例四中的相关过程类似，具体可参见11B。与图11B所示的流程的区别在于：WLAN AP接收到eNB发送的数据后，根据Xw接口的GTP-U连接与WLAN空口的UDP(或TCP)连接的对应关系，将接收到的数据通过UE在WLAN AP侧的空口的UDP(或TCP)连接发送给UE。其中，WLAN AP根据Xw接口的GTP-U连接与WLAN空口的UDP(或TCP)连接的对应关系， 可以用WLAN AP根据Xw接口的GTP-U连接的TEID，WLAN空口的UDP(或TCP)连接的端口号之间的对应关系来表示。
UE接收下行数据的过程与实施例一中的相关过程基本相同，具体可参见图8C。
UE发送上行数据的过程与实施例一中的相关过程基本相同，具体可参见图8D。
eNB接收上行数据的过程与实施例四中的相关过程类似，具体可参见图11E。与图11E所示的流程的区别在于：WLAN AP的UDP(或TCP)实体从UE对端UDP(或TCP)实体收到对应的UDP(或TCP)数据，WLAN AP根据Xw接口的GTP-U连接与WLAN空口的UDP(或TCP)连接的对应关系，将该数据通过UE在WLAN AP侧的eNB和WLAN AP间的GTP-U连接发送给eNB的GTP-U实体。eNB的GTP-U实体根据数据包的协议类型(或应用类型)以及UE的Xw TEID将该数据包发送给UE对应的LC实体。其中，WLAN AP根据Xw接口的GTP-U连接与WLAN空口的UDP(或TCP)连接的对应关系，可以用WLAN AP根据Xw接口的GTP-U连接的TEID，WLAN空口的UDP(或TCP)连接的端口号之间的对应关系来表示。
需要说明的是，实施例五是以UE与WLAN AP间的承载通道是TCP连接为例描述的，该承载通道也可以用UDP连接代替。如果该承载通道为UDP连接，则其承载通道配置过程以及数据分流的过程可重用上述流程，不同之处在于：在承载通道的信令配置流程中步骤4中指定UDP协议类型，并指定UDP协议的端口号。后续UE和网络侧之间建立UDP连接并可通过UDP端口发送和接收数据。
实施例六描述了UE与WLAN AP之间的承载通道为空口IP连接，WLAN AP与eNB之间的承载通道为GTP-U连接的情况下，实现通过WLAN AP对eNB与UE之间的用户面数据进行分流的方案。
实施例六的网络架构中，UE与eNB之间使用LTE无线通信协议进行交互， UE与WLAN AP之间使用Wi-Fi无线通信协议进行交互，eNB与WLAN AP之间通过有线方式连接，使用有线通信协议进行交互。
图13为实施例六中的用户面协议栈架构。其中，UE中的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；UE中的Wi-Fi协议栈从上层到下层包括IP层和MAC/PHY层；eNB的LTE协议栈中从上层到下层包括PDCP层、RLC层、MAC层和PHY层；eNB的有线通信协议栈中从上层到下层包括GTP-U层、UDP层、IP层和数据链路层(图中示为layer-2)。
基于图13所示的用户面协议栈架构并结合图4和图5所示的DRB配置流程，配置UE与eNB之间经由WLAN AP的DRB的信令流程具体可包括如下内容：
步骤1：UE向eNB上报该UE的能力信息，所述能力信息可以表明该UE对用户面数据分流传输的支持能力。
所述能力信息可包括如下内容：
协议类型指示信息，表明该UE建立DRB承载通道所使用的协议。本实施例中，该协议类型为GTP-U；
UE是否支持用户面数据经由WLAN AP分流的指示信息；本实施例中，该指示信息表明UE支持用户面数据经由WLAN AP分流。
步骤2：eNB配置UE对WLAN AP进行测量。
步骤3：UE根据eNB的配置对WLAN AP进行测量并上报测量结果，所述测量结果中包括UE测量到的WLAN AP的标识等信息。
步骤4：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该WLAN AP发送配置消息，以使该WLAN AP配置该WLAN AP与UE间的UDP连接，以及该WLAN AP与eNB间的GTP-U连接。
eNB向WLAN AP发送的配置消息中可包括以下连接配置信息：
IP协议的指示信息，以指示WLAN AP与UE建立IP连接；
UE与WLAN AP之间的IP连接的配置信息，具体可包括：UE与WLAN AP 之间的空口IP连接在WLAN AP侧的IP地址，该空口UDP连接在UE侧的IP地址等；
eNB与WLAN AP之间的GTP-U连接的配置信息，该GTP-U连接与该UE对应；该GTP-U连接的配置信息具体可包括：eNB与WLAN AP之间的GTP-U连接在该eNB和该WLAN AP侧的接口的GTP-U TEID；
重配置的DRB标识。
步骤5：WLAN AP根据步骤4中的配置信息，在接受该配置后，建立UE在WLAN AP侧的空口IP连接，以及建立WLAN AP和eNB之间的GTP-U连接，并建立两者的对应关系，两者的对应关系可通过空口UDP连接的端口号与GTP-U连接的TEID之间的对应关系来表示。其中，WLAN AP和eNB之间的GTP-U连接与该UE对应。
进一步地，WLAN AP向eNB发送配置确认消息。所述配置确认消息中可包括以下信息：上述GTP-U连接的GTP-U TEID，还可以包括上述空口IP连接的配置信息，比如，空口UDP连接在WLAN AP侧的端口号和IP地址，以及在UE侧的端口号和IP地址等，还可以包括上述空口UDP连接与上述GTP-U连接的对应关系。
步骤6：eNB在确认UE支持将用户面数据经由WLAN AP分流传输，并在获得UE测量到的WLAN AP的情况下，向该UE发送重配置消息，以请求UE配置该UE与eNB之间经由WLAN AP的DRB。
其中，该重配置消息中可包括以下内容：
IP协议类型指示信息，用以指示UE使用UDP协议建立DRB的承载通道；DRB的承载通道的配置信息；具体可包括：所述DRB通道中的PDCP实体与LCID的对应关系等信息，以及该UE与该WLAN AP之间的空口IP连接的配置信息，比如可包括：该空口IP连接在WLAN AP侧的IP地址，该空口IP连接在UE侧的IP地址等；
需要重配置的DRB的标识，本实施例中即为UE与eNB之间经由WLAN AP 的DRB的标识；
其他配置信息，具体可包括以下内容之一或组合：PDCP实体的信息、LC实体的信息、PDCP和LC之间的信道标识、PDCP和LC之间的信道的配置信息、逻辑信道标识(LCID)、逻辑信道配置信息、MAC实体的信息、物理层实体的信息等。
步骤7：UE接收到eNB发送的重配置消息后，根据其中的配置信息，建立与WLAN AP之间的空口IP连接，并通过该空口IP连接，通过WLAN接入网络进行数据收发。进一步地，UE可向eNB反馈配置成功消息。
步骤8：eNB在接收到UE的配置成功消息后，或根据步骤5中的配置确认消息，通过与该UE对应的与WLAN AP之间的GTP-U连接与该UE进行数据收发。
在上述流程中，也可以省略eNB配置UE进行WLAN AP测量以及接收UE上报的WLAN AP测量结果的步骤，UE可以直接向eNB上报该UE测量到的可用的WLAN AP的标识等信息。
上述承载配置流程中，步骤4和步骤6的执行顺序没有严格要求，比如可以先执行步骤6再执行步骤4，也可以同时执行。
UE通过WLAN接入网络与eNB在建立起上述承载通道后，可通过该承载通道向eNB发送用户面数据。如果UE在数据发送过程中，该承载通道连接失败，则UE可以将该承载通道连接失败的信息通知该eNB。
eNB发送下行数据的过程与实施例四中的相关过程类似，具体可参见11B。与图11B所示的流程的区别在于：WLAN AP接收到eNB发送的数据后，根据Xw接口的GTP-U连接与WLAN空口的IP连接的对应关系，比如，根据UE的IP地址或WLAN MAC地址，将接收到的数据通过UE在WLAN AP侧的空口的IP连接发送给UE。
UE接收下行数据的过程与实施例三中的相关过程基本相同，具体可参见图10C。
UE发送上行数据的过程与实施例三中的相关过程基本相同，具体可参见 图10D。
eNB接收上行数据的过程与实施例四中的相关过程类似，具体可参见图11E。与图11E所示的流程的区别在于：WLAN AP的IP实体从UE对端IP实体收到IP数据包，WLAN AP根据Xw接口的GTP-U连接与WLAN空口的IP连接的对应关系，比如，根据UE的IP地址或WLAN MAC地址，将该数据通过eNB与WLAN AP间的GTP-U连接发送给eNB的GTP-U实体。eNB的GTP-U实体根据数据包的协议类型(或应用类型)以及UE的Xw TEID，将该数据包发送给UE对应的LC实体。
实施例七描述了采用TCP协议建立DRB的承载通道以实现通过WLAN AP对eNB与UE之间的用户面数据进行分流的方案。
实施例七中的用户面协议栈架构与实施例一中的用户面协议栈架构相同，具体可参见图8A。
实施例七中的承载配置过程与实施例一中的相关过程基本相同，不同之处在于：步骤4中，TCP连接所需的配置信息中的TCP端口号唯一对应一个DRB。由于一个DRB对应一个PDCP实体，因此TCP端口号与PDCP实体存在一一对应的关系。
UE通过WLAN接入网络与eNB在建立起上述承载通道后，可通过该承载通道向eNB发送用户面数据。如果UE在数据发送过程中，该承载通道连接失败，则UE可以将该承载通道连接失败的信息通知该eNB。
eNB发送下行数据的过程与实施例一中的相关过程类似，具体可参见8B，本实施例与实施例一的不同之处在于：省略步骤3的操作，并且在步骤2中，PDCP实体根据该PDCP实体对应的TCP端口号，将数据包通过该TCP端口发送给TCP实体。
UE接收下行数据的过程与实施例一中的相关过程基本相同，具体可参见图8C，本实施例与实施例一的不同之处在于：步骤4中，PDCP实体根据该PDCP实体对应的TCP端口号，将数据包通过该TCP端口发送给TCP实体。
UE发送上行数据的过程与实施例一中的相关过程基本相同，具体可参见图8D，本实施例与实施例一的不同之处在于：步骤4中，PDCP实体根据该PDCP对应的TCP端口号，将数据包通过该TCP端口发送给TCP实体。
eNB接收上行数据的过程与实施例一中的相关过程类似，具体可参见图8E，本实施例与实施例一的不同之处在于：步骤2中，TCP实体根据TCP端口对应的DRB，将数据包通过该TCP端口发送给对应的UE的对应PDCP实体。如果eNB为不同UE分配了相同的TCP端口，则eNB根据该TCP端口接收到数据的UE侧的IP地址和TCP端口号来区分不同的PDCP实体，然后将数据包发送给对应的UE对应的PDCP实体。
需要说明的是，实施例七是以UE与eNB之间且经由WLAN AP的承载通道是TCP连接为例描述的，该承载通道也可以用UDP连接代替，如果该承载通道为UDP连接，则其承载通道配置过程以及数据分流的过程可重用上述流程，不同之处在于：在承载通道的信令配置流程中步骤4中指定UDP协议类型，并指定UDP协议的端口号。后续UE和网络侧之间建立UDP连接并可通过UDP端口发送和接收数据。
实施例八描述了采用GTP-U协议建立DRB的承载通道以实现通过WLAN AP对eNB与UE之间的用户面数据进行分流的方案。
实施例八中的用户面协议栈架构与实施例五中的用户面协议栈架构相同，具体可参见图12。
实施例八中的承载配置过程与实施例五中的相关过程基本相同，不同之处在于，UE与WLAN AP之间的空口的UDP(或TCP)连接与该终端中的DRB对应，即，与一个需要经由WLAN AP分流的DRB唯一对应，相应地：
步骤5中，UE与WLAN AP之间的空口的UDP(或TCP)连接的配置信息中，WLAN AP空口连接的UDP(或TCP)端口号对应于UE的DRB；步骤6中，建立UE在WLAN AP侧的空口的UDP(或TCP)的连接的配置信息中，WLAN AP与UE之间的空口UDP(或TCP)连接的端口号对应于该UE的DRB。
UE通过WLAN接入网络与eNB在建立起上述承载通道后，可通过该承载通道向eNB发送用户面数据。如果UE在数据发送过程中，该承载通道连接失败，则UE可以将该承载通道连接失败的信息通知该eNB。
eNB发送下行数据的过程与实施例四中的相关过程类似，具体可参见11B，本实施例与实施例一的不同之处在于：省略了步骤3，并且：
步骤2中，PDCP实体根据各个DRB对应的GTP-U TEID，将数据包发送给GTP-U实体；
步骤4中，WLAN AP根据Xw接口的GTP-U的Xw TEID和WLAN空口的UDP(或UDP)连接(如端口)的对应关系，将数据包通过UE在WLAN AP侧的空口的UDP(或UDP)连接发送给UE对应的DRB。
UE接收下行数据的过程与实施例七中的相关过程基本相同。
UE发送上行数据的过程与实施例七中的相关过程基本相同。
eNB接收上行数据的过程与实施例一中的相关过程类似，具体可参见图8E，本实施例与实施例一的不同之处在于：省略步骤2，并且：
步骤1中，WLAN AP的UDP(或TCP)实体从UE对端UDP(或TCP)实体收到对应的UDP(或TCP)数据，WLAN AP根据Xw接口的GTP-U的Xw TEID和WLAN空口的UDP(或TCP)的连接(如端口)的对应关系，将该数据通过UE在WLAN AP侧的eNB和WLAN AP间的GTP-U连接发送给eNB的GTP-U实体。如果WLAN AP为不同UE分配了相同的TCP端口，则WLAN AP根据该TCP端口接收到数据的UE侧的IP地址和TCP端口号区分不同的UE，然后将TCP数据发送给对应的UE对应的GTP TEID连接。eNB的GTP-U层根据数据包的协议类型(或应用类型)和UE的Xw TEID将该数据包发送给UE对应的PDCP实体。
通过以上对优选实施例的描述可以看出，在宏小区覆盖下，同时部署大量热点覆盖的WLAN AP，UE可以同时在eNB上和其他接入技术(如WLAN AP)上有连接。通过在eNB和UE的WLAN AP接入实体建立连接通道，实现eNB的PDCP数据对于在其他接入技术上的透明传输，可以实现LTE侧数据的灵活分流，更 高效的利用现有的WLAN AP资源。
本公开的上述各实施例均以LTE与WLAN共覆盖的场景为例描述，当然将本公开实施例的思想推广到其它类型网络共覆盖的场景，也可实现一个接入设备侧的用户面数据在另一个接入设备侧的分流。
基于相同的技术构思，本公开实施例还提供了一种接入设备和一种终端。
参见图14，为本公开实施例提供的接入设备的结构示意图。该接入设备可以是前述流程中的第一接入设备，比如可以是基站。如图所示，该接入设备可包括：获取模块1401、承载配置请求模块1402、承载配置模块1403，其中：
获取模块1401，用于获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
承载配置请求模块1402，用于根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备之间经由所述第二接入设备的数据无线承载DRB；其中，第一接入设备与第二接入设备支持不同的接入技术；
承载配置模块1403，用于与所述终端之间建立所述DRB的承载通道。
可选的，所述能力信息中包括以下内容之一或任意组合：
协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
所述终端的地址；
所述终端是否支持用户面数据经由第二接入设备分流的指示信息。
可选的，用于指示所述终端配置所述DRB的信息，包括以下内容之一或任意组合：
协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
所述承载通道的配置信息，所述承载通道的配置信息中至少包括：所述承载通道中的PDCP实体与逻辑信道标识的对应关系；
所述DRB的标识。
其中，所述承载通道所用的协议包括以下之一：网际协议IP，传输控制协议TCP，用户数据报协议UDP，用户面通用分组无线业务协议GTP-U，超文本传输协议HTTP，超文本传输安全协议HTTPS。
可选的，所述承载通道为使用TCP协议建立的TCP或UDP连接，所述承载通道的配置信息中还包括：所述TCP或UDP连接的端口信息。
其中，所述承载配置模块还用于：在指示所述终端配置所述DRB之前，根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的LC实体分配一个TCP或UDP端口，其中，所述终端的所述DRB对应配置有一个LC实体；或者，所述承载配置模块还用于：预先为LC实体分配一个TCP或UDP端口，所述承载通道的配置信息中还包括所述终端的标识，其中，所述终端的多个DRB承载对应配置有一个LC实体；或者，所述承载配置模块还用于：在指示所述终端配置所述DRB之前，根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的需要经由第二接入设备分流的DRB分配对应的一个TCP或UDP端口。
可选的，所述承载通道为使用IP协议建立的IP连接，所述承载通道的配置信息中还包括：所述终端的标识信息。
可选的，所述承载通道中，所述终端与所述第第二接入设备之间为所用GTP-U协议建立的空口GTP-U连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息。
可选的，所述承载通道中，所述终端与所述第二接入设备之间为空口UDP或TCP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口UDP或TCP链接的配置信息。
可选的，所述承载通道中，所述终端与所述第二接入设备之间为空口IP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口IP连接的配置信息。
可选的，所述承载配置请求模块还用于，若承载通道中，所述第一接入设备与所述第二接入设备间的连接为GTP-U连接，则向所述第二接入设备发送GTP-U连接配置信息，所述GTP-U连接配置信息包括：
协议类型指示信息，所述协议类型指示信息指示的协议为GTP-U协议；
所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息，以及所述第一接入设备与所述第二接入设备之间的GTP-U连接的配置信息；
所述DRB的标识。
进一步地，所述接入设备还包括：传输模块，用于接收来自于核心网的用户面数据，将所述用户面数据通过与所述终端之间经由第二接入设备的DRB的承载通道发送给所述终端；和/或，通过所述承载通道接收来自于所述终端的用户面数据，并将所述用户面数据向所述核心网发送。
参见图15，为本公开实施例提供的终端的结构示意图，如图所示，该终端可包括：上报模块1501、承载配置接收模块1502、承载配置模块1503，其中：
上报模块1501，用于向第一接入设备上报所述终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
承载配置接收模块1502，用于接收所述第一接入设备发送的配置请求，所述配置请求用于请求所述终端配置所述终端与所述第一接入设备之间经由第二接入设备分流的数据无线承载DRB；其中，所述第一接入设备与所述第二接入设备支持不同的接入方式；
承载配置模块1503，用于与所述第一接入设备之间建立所述DRB的承载通道。
可选的，所述能力信息中包括以下内容之一或任意组合：
协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
所述终端的地址；
所述终端是否支持用户面数据经由第二接入设备分流的指示信息。
可选的，用于指示所述终端配置所述DRB的信息，包括以下内容之一或任意组合：
协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
所述承载通道的配置信息，所述承载通道的配置信息中至少包括：所述承载通道中的PDCP实体与逻辑信道标识的对应关系；
所述DRB的标识。
可选的，所述承载通道所用的协议包括以下之一：网际协议IP，传输控制协议TCP，用户数据报协议UDP，用户面通用分组无线业务协议GTP-U，超文本传输协议HTTP，超文本传输安全协议HTTPS。
可选的，所述承载通道为使用TCP协议建立的TCP或UDP连接，所述承载通道的配置信息中还包括：所述TCP或UDP连接的端口信息。
可选的，所述承载通道为使用IP协议建立的IP连接，所述承载通道的配置信息中还包括：所述终端的标识信息。
可选的，所述承载通道中，所述终端与所述第第二接入设备之间为所用GTP-U协议建立的空口GTP-U连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息。
可选的，所述承载通道中，所述终端与所述第二接入设备之间为空口UDP或TCP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口UDP或TCP链接的配置信息。
优选地，所述承载通道中，所述终端与所述第二接入设备之间为空口IP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口IP连接的配置信息。
进一步地，所述终端还包括：传输模块，用于将用户面数据通过与所述第一接收设备之间经由第二接入设备的DRB的承载通道发送给所述第一接入设 备，其中，所述第一接入设备与第二接入设备采用不同的接入技术；和/或，通过所述承载通道接收来自于所述第一接入设备的用户面数据。
参见图16，为本公开另一实施例提供的接入设备的结构示意图，该接入设备可以是前述实施例中的第一接入设备，比如可以是基站。如图所示，该接入设备可包括：处理器1601、存储器1602、收发机1603以及总线接口。
处理器1601负责管理总线架构和通常的处理，存储器1602可以存储处理器1601在执行操作时所使用的数据。收发机1603用于在处理器1601的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器1601代表的一个或多个处理器和存储器1602代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1603可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器1601负责管理总线架构和通常的处理，存储器1602可以存储处理器1601在执行操作时所使用的数据。
本公开实施例揭示的用户面的无线数据承载配置流程以及通过该无线数据承载的通道进行数据传输的流程，可以应用于处理器1601中，或者由处理器1601实现。在实现过程中，控制面的处理方法的各步骤可以通过处理器1601中的硬件的集成逻辑电路或者软件形式的指令完成。处理器1601可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电 可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1602，处理器1601读取存储器1602中的信息，结合其硬件完成控制面的处理方法的步骤。
参见图17，为本公开另一实施例提供的终端的结构示意图，如图所示，该终端可包括：处理器1701、存储器1702、收发机1703以及总线接口。
处理器1701负责管理总线架构和通常的处理，存储器1702可以存储处理器1701在执行操作时所使用的数据。收发机1703用于在处理器1701的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器1701代表的一个或多个处理器和存储器1702代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1703可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器1701负责管理总线架构和通常的处理，存储器1702可以存储处理器1701在执行操作时所使用的数据。
本公开实施例揭示的用户面的无线数据承载配置流程以及通过该无线数据承载的通道进行数据传输的流程，可以应用于处理器1701中，或者由处理器1701实现。在实现过程中，控制面的处理方法的各步骤可以通过处理器1701中的硬件的集成逻辑电路或者软件形式的指令完成。处理器1701可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电 可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1702，处理器1701读取存储器1702中的信息，结合其硬件完成控制面的处理方法的步骤。
本公开是参照根据本公开实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本公开的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本公开范围的所有变更和修改。
显然，本领域的技术人员可以对本公开进行各种改动和变型而不脱离本公开的精神和范围。这样，倘若本公开的这些修改和变型属于本公开权利要求及其等同技术的范围之内，则本公开也意图包含这些改动和变型在内。

Claims (67)

  1. 一种数据无线承载配置方法，包括：
    第一接入设备获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
    所述第一接入设备根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备之间经由所述第二接入设备的数据无线承载(DRB)；其中，第一接入设备与第二接入设备支持不同的接入技术；
    所述第一接入设备与所述终端之间建立所述DRB的承载通道。
  2. 如权利要求1所述的方法，其中，所述能力信息中包括以下内容之一或任意组合：
    协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
    所述终端的地址；以及
    所述终端是否支持用户面数据经由第二接入设备分流的指示信息。
  3. 如权利要求2所述的方法，其中，所述能力信息中还包括：所述终端已占用的端口的信息，和/或，所述终端建议使用的端口的信息。
  4. 如权利要求1所述的方法，其中，用于指示所述终端配置所述DRB的信息，包括以下内容之一或任意组合：
    协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
    所述承载通道的配置信息，所述承载通道的配置信息中至少包括：所述承载通道中的PDCP实体与逻辑信道标识的对应关系；以及
    所述DRB的标识。
  5. 如权利要求4所述的方法，其中，所述承载通道所用的协议包括以下 之一：网际协议(IP)，传输控制协议(TCP)，用户数据报协议(UDP)，用户面通用分组无线业务协议(GTP-U)，超文本传输协议(HTTP)，超文本传输安全协议(HTTPS)。
  6. 如权利要求1所述的方法，其中，
    所述承载通道为使用TCP协议建立的TCP或UDP连接，所述承载通道的配置信息中还包括：所述TCP或UDP连接的端口信息。
  7. 如权利要求6所述的方法，其中，在所述第一接入设备指示所述终端配置所述DRB之前，所述方法还包括：所述第一接入设备根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的逻辑信道(LC)实体分配一个TCP或UDP端口，其中，所述终端的所述DRB对应配置有一个LC实体；或者，
    所述第一接入设备预先为LC实体分配一个TCP或UDP端口，所述承载通道的配置信息中还包括所述终端的标识，其中，所述终端的多个DRB承载对应配置有一个LC实体；或者，
    所述第一接入设备指示所述终端配置所述DRB之前，还包括：所述第一接入设备根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的需要经由第二接入设备分流的DRB分配对应的一个TCP或UDP端口。
  8. 如权利要求1所述的方法，其中，所述承载通道为使用IP协议建立的IP连接，所述承载通道的配置信息中还包括：所述终端的标识信息。
  9. 如权利要求1所述的方法，其中，所述承载通道中，所述终端与所述第二接入设备之间为所用GTP-U协议建立的空口GTP-U连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息。
  10. 如权利要求1所述的方法，其中，所述承载通道中，所述终端与所述第二接入设备之间为空口UDP或TCP连接，所述承载通道的配置信息中还包括： 所述终端与所述第二接入设备间的空口UDP或TCP链接的配置信息。
  11. 如权利要求10所述的方法，其中，所述UDP或TCP连接与所述终端唯一对应，或者与所述终端的需要经由第二接入设备分流的DRB唯一对应。
  12. 如权利要求1所述的方法，其中，所述承载通道中，所述终端与所述第二接入设备之间为空口IP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口IP连接的配置信息。
  13. 如权利要求1所述的方法，其中，所述承载通道中，所述第一接入设备与所述第二接入设备间的连接为GTP-U连接，所述方法还包括：
    所述第一接入设备向所述第二接入设备发送GTP-U连接配置信息，所述GTP-U连接配置信息包括：
    协议类型指示信息，所述协议类型指示信息指示的协议为GTP-U协议；
    所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息，以及所述第一接入设备与所述第二接入设备之间的GTP-U连接的配置信息；以及
    所述DRB的标识。
  14. 如权利要求1至13中任一项所述的方法，其中，所述第一接入设备为长期演进(LTE)或其演进系统中的基站，所述第二接入设备为无线局域网(WLAN)中的接入点(AP)。
  15. 一种数据无线承载配置方法，包括：
    终端向第一接入设备上报所述终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
    所述终端接收所述第一接入设备发送的配置请求，所述配置请求用于请求所述终端配置所述终端与所述第一接入设备之间经由第二接入设备分流的数据无线承载(DRB)；其中，所述第一接入设备与所述第二接入设备支持不同的接入方式；
    所述终端与所述第一接入设备之间建立所述DRB的承载通道。
  16. 如权利要求15所述的方法，其中，所述能力信息中包括以下内容之 一或任意组合：
    协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
    所述终端的地址；
    所述终端是否支持用户面数据经由第二接入设备分流的指示信息。
  17. 如权利要求16所述的方法，其中，所述能力信息中还包括：所述终端已占用的端口的信息，和/或，所述终端建议使用的端口的信息。
  18. 如权利要求15所述的方法，其中，用于指示所述终端配置所述DRB的信息，包括以下内容之一或任意组合：
    协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
    所述承载通道的配置信息，所述承载通道的配置信息中至少包括：所述承载通道中的PDCP实体与逻辑信道标识的对应关系；以及
    所述DRB的标识。
  19. 如权利要求18所述的方法，其中，所述承载通道所用的协议包括以下之一：网际协议(IP)，传输控制协议(TCP)，用户数据报协议(UDP)，用户面通用分组无线业务协议(GTP-U)，超文本传输协议(HTTP)，超文本传输安全协议(HTTPS)。
  20. 如权利要求15所述的方法，其中，
    所述承载通道为使用TCP协议建立的TCP或UDP连接，所述承载通道的配置信息中还包括：所述TCP或UDP连接的端口信息。
  21. 如权利要求20所述的方法，其中，在所述第一接入设备指示所述终端配置所述DRB之前，所述方法还包括：所述第一接入设备根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的LC实体分配一个TCP或UDP端口，其中，所述终端的所述DRB对应配置有一个LC实体；或者，
    所述第一接入设备预先为LC实体分配一个TCP或UDP端口，所述承载通道的配置信息中还包括所述终端的标识，其中，所述终端的多个DRB承载对应配置有一个LC实体；或者，
    所述第一接入设备指示所述终端配置所述DRB之前，还包括：所述第一接入设备根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的需要经由第二接入设备分流的DRB分配对应的一个TCP或UDP端口。
  22. 如权利要求15所述的方法，其中，所述承载通道为使用IP协议建立的IP连接，所述承载通道的配置信息中还包括：所述终端的标识信息。
  23. 如权利要求15所述的方法，其中，所述承载通道中，所述终端与所述第第二接入设备之间为所用GTP-U协议建立的空口GTP-U连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息。
  24. 如权利要求15所述的方法，其中，所述承载通道中，所述终端与所述第二接入设备之间为空口UDP或TCP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口UDP或TCP链接的配置信息。
  25. 如权利要求24所述的方法，其中，所述UDP或TCP连接与所述终端唯一对应，或者与所述终端的需要经由第二接入设备分流的DRB唯一对应。
  26. 如权利要求15所述的方法，其中，所述承载通道中，所述终端与所述第二接入设备之间为空口IP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口IP连接的配置信息。
  27. 如权利要求15至26中任一项所述的方法，其中，所述第一接入设备为长期演进(LTE)或其演进系统中的基站，所述第二接入设备为无线局域网(WLAN)中的接入点(AP)。
  28. 一种数据传输方法，包括：
    第一接入设备接收来自于核心网的用户面数据，将所述用户面数据通过与 所述终端之间经由第二接入设备的数据无线承载(DRB)的承载通道发送给所述终端，其中，所述第一接入设备与第二接入设备采用不同的接入技术；和/或，
    所述第一接入设备通过所述承载通道接收来自于所述终端的用户面数据，并将所述用户面数据向所述核心网发送。
  29. 如权利要求28所述的方法，其中，所述第一接入设备接收来自于核心网的用户面数据，将所述用户面数据通过与终端之间经由第二接入设备的DRB的承载通道发送给所述终端，包括：
    所述第一接入设备中所述承载通道中的分组数据汇聚协议(PDCP)实体接收来自于核心网的数据包，并将所述数据包发送给无线链路控制(RLC)实体；
    所述RLC实体将来自于所述PDCP实体的数据包映射到逻辑信道，在所述数据包中添加映射到的逻辑信道标识，并根据分配的传输控制协议(TCP)或用户数据报协议(UDP)端口，将所述数据包发送给TCP或UDP实体；
    所述TCP或UDP实体将来自于所述RLC实体的数据包发送给网际协议(IP)实体；
    所述IP实体通过IP路由方式，通过所述第二接入设备将所述数据包向所述终端发送。
  30. 如权利要求28所述的方法，其中，所述第一接入设备接收来自于核心网的用户面数据，将所述用户面数据通过与终端之间经由第二接入设备的DRB的承载通道发送给所述终端，包括：
    所述第一接入设备中所述承载通道中的PDCP实体接收来自于核心网的数据包，并将所述数据包发送给RLC实体；
    所述RLC实体将来自于所述PDCP实体的数据包映射到逻辑信道，在所述数据包中添加映射到的逻辑信道标识，并将所述数据包发送给IP实体；
    所述IP实体在接收到的数据包中指定用于RLC层数据包传输的新的协议类型，并通过IP路由方式，通过所述第二接入设备将所述数据包向所述终端 发送。
  31. 如权利要求28所述的方法，其中，所述第一接入设备接收来自于核心网的用户面数据，将所述用户面数据通过与终端之间经由第二接入设备的DRB的承载通道发送给所述终端，包括：
    所述第一接入设备中所述承载通道中的PDCP实体接收来自于核心网的数据包，并将所述数据包发送给RLC实体；
    所述RLC实体将来自于所述PDCP实体的数据包映射到逻辑信道，在所述数据包中添加映射到的逻辑信道标识，并将所述数据包发送给用户面通用分组无线业务协议(GTP-U)实体；
    所述GTP-U实体根据GTP-U连接的隧道标识与RLC实体的对应关系，将来自于所述RLC实体的数据包通过对应的隧道发送给所述第二接入设备。
  32. 如权利要求28所述的方法，其中，所述第一接入设备通过所述DRB的承载通道接收来自于所述终端的上行用户面数据，包括：
    所述第一接入设备中的IP实体接收来自于所述终端的数据包，将所述数据包发送给TCP实体；
    所述TCP实体根据为RLC实体分配的TCP端口，将所述数据包发送给RLC实体；
    所述RLC实体根据来自于所述TCP实体的数据包中包含的逻辑信道标识，将所述数据包发送给与所述逻辑信道标识对应的PDCP实体。
  33. 如权利要求28所述的方法，其中，所述第一接入设备通过所述DRB的承载通道接收来自于所述终端的上行用户面数据，包括：
    所述第一接入设备中的IP实体接收来自于所述第二接入设备的数据包，根据所述数据包的新的协议类型将所述数据包发送给RLC实体，所述新的协议类型为IP层用于RLC层数据包传输的协议类型；
    所述RLC实体根据来自于所述TCP实体的数据包中包含的逻辑信道标识，将所述数据包发送给与所述逻辑信道标识对应的PDCP实体。
  34. 如权利要求28所述的方法，其中，所述第一接入设备通过所述DRB的承载通道接收来自于所述终端的上行用户面数据，包括：
    所述第一接入设备中的GTP-U实体接收来自于所述第二接入设备的数据包，根据所述数据包的协议类型或应用类型，以及所述终端与所述第二接入设备间的GTP-U连接在所述第二接入设备侧的隧道标识，将所述数据包发送给所述终端对应的RLC实体；
    所述RLC实体根据来自于所述TCP实体的数据包中包含的逻辑信道标识，将所述数据包发送给与所述逻辑信道标识对应的PDCP实体。
  35. 如权利要求29或32所述的方法，其中，所述TCP或UDP端口与所述终端对应；或者，
    所述TCP或UDP端口为包含所述终端在内的多个终端所共享；或者，
    所述TCP或UDP端口与所述终端的需要分流传输的一个DRB对应。
  36. 一种数据传输方法，包括：
    终端将用户面数据通过与所述第一接收设备之间经由第二接入设备的数据无线承载(DRB)的承载通道发送给所述第一接入设备，其中，所述第一接入设备与第二接入设备采用不同的接入技术；和/或，
    所述终端通过所述承载通道接收来自于所述第一接入设备的用户面数据。
  37. 如权利要求36所述的方法，其中，所述终端将用户面数据通过与所述第一接收设备之间经由第二接入设备的DRB的承载通道发送给所述第一接入设备，包括：
    所述终端的应用层实体将数据包发送给传输控制协议(TCP)或用户数据报协议(UDP)实体；
    所述TCP或UDP实体将所述数据包发送给网际协议(IP)实体；
    所述IP实体根据所述数据包的IP头，将所述数据包发送给逻辑信道(LC)实体；
    所述LC实体将所述数据包映射到逻辑信道，在所述数据包中添加逻辑信 道标识，并根据为所述LC实体分配的TCP或UDP端口，将所述数据包发送给TCP或UDP实体；
    所述TCP或UDP实体将所述数据包发送给IP实体；
    所述IP实体将数据包发送给与所述第二接入设备协议层对等的链路控制层实体，通过所述链路控制实体将所述数据包发送给所述第二接入设备。
  38. 如权利要求37所述的方法，其中，所述TCP或UDP端口与所述终端对应；或者，
    所述TCP或UDP端口为包含所述终端在内的多个终端所共享；或者，
    所述TCP或UDP端口与所述终端的需要分流传输的一个DRB对应。
  39. 如权利要求36所述的方法，其中，所述终端将用户面数据通过与所述第一接收设备之间经由第二接入设备的DRB的承载通道发送给所述第一接入设备，包括：
    所述终端的应用层实体将数据包发送给TCP或UDP实体；
    所述TCP或UDP实体将所述数据包发送给IP实体；
    所述IP实体根据所述数据包的IP头，将所述数据包发送给分组数据汇聚协议(PDCP)实体；
    所述PDCP实体将所述数据包发送给LC实体；
    所述LC实体将所述数据包映射到逻辑信道，在所述数据包中添加逻辑信道标识，将所述数据包发送给IP实体；
    所述IP实体在所述数据包的IP头中指定用于LC层数据包传输的新的协议类型后，发送给与所述第二接入设备协议层对等的数据链路层实体，通过所述数据链路层实体将所述数据包发送给所述第二接入设备。
  40. 如权利要求36所述的方法，其中，所述终端将用户面数据通过与所述第一接收设备之间经由第二接入设备的DRB的承载通道发送给所述第一接入设备，包括：
    所述终端的应用层实体将数据包发送给TCP或UDP实体；
    所述TCP或UDP实体将所述数据包发送给IP实体；
    所述IP实体根据所述数据包的IP头，将所述数据包发送给PDCP实体；
    所述PDCP实体将所述数据包发送给LC实体；
    所述LC实体将所述数据包映射到逻辑信道，在所述数据包中添加逻辑信道标识，将所述数据包发送给用户面通用分组无线业务协议(GTP-U)实体；
    所述GTP-U实体根据GTP-U连接的隧道标识与LC实体的对应关系，在所述数据包中添加GTP头后发送给TCP或UDP实体；
    所述TCP或UDP实体将所述数据包发送给IP实体；
    所述IP实体将所述数据包发送给与所述第二接入设备协议层对等的数据链路层实体，通过所述数据链路层实体将所述数据包发送给所述第二接入设备。
  41. 如权利要求36所述的方法，其中，所述终端通过所述承载通道接收来自于所述第一接入设备的用户面数据，包括：
    所述终端内的与所述第二接入设备协议层对等的数据链路层实体将从所述第二接入设备接收到的数据包发送给IP实体；
    所述IP实体将所述数据包发送给TCP或UDP实体；
    所述TCP或UDP实体根据为所述终端的LC实体分配的TCP或UDP端口，将所述数据包发送给LC实体；
    所述LC实体根据所述数据包的包头中的逻辑信道标识，将所述数据包发送给对应的PDCP实体；
    所述PDCP实体将所述数据包发送给IP实体；
    所述IP实体根据协议类型将所述数据包发送给TCP实体；
    所述TCP实体将所述数据包发送给应用层实体。
  42. 如权利要求36所述的方法，其中，所述终端通过所述承载通道接收来自于所述第一接入设备的用户面数据，包括：
    所述终端内的与所述第二接入设备协议层对等的数据链路层实体将从所 述第二接入设备接收到的数据包发送给IP实体；
    所述IP实体根据IP层用于传输LC层数据包的新的协议类型，将所述数据包发送给LC实体；
    所述LC实体根据所述数据包的包头中的逻辑信道标识，将所述数据包发送给对应的PDCP实体；
    所述PDCP实体将所述数据包发送给IP实体；
    所述IP实体根据协议类型将所述数据包发送给TCP实体；
    所述TCP实体将所述数据包发送给应用层实体。
  43. 如权利要求36所述的方法，其中，所述终端通过所述承载通道接收来自于所述第一接入设备的用户面数据，包括：
    所述终端内的与所述第二接入设备协议层对等的数据链路层实体将从所述第二接入设备接收到的数据包发送给IP实体；
    所述IP实体将所述数据包发送给TCP或UDP实体；
    所述TCP或UDP实体将所述数据包发送给GTP-U实体；
    所述GTP-U实体根据LC层数据收发对应的协议类型或应用类型，将所述数据包发送给LC实体；
    所述LC实体根据所述数据包的包头中的逻辑信道标识，将所述数据包发送给对应的PDCP实体；
    所述PDCP实体将所述数据包发送给IP实体；
    所述IP实体根据协议类型将所述数据包发送给TCP或UDP实体；
    所述TCP或UDP实体将所述数据包发送给应用层实体。
  44. 一种接入设备，包括：
    获取模块，用于获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
    承载配置请求模块，用于根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备 之间经由所述第二接入设备的数据无线承载(DRB)；其中，第一接入设备与第二接入设备支持不同的接入技术；
    承载配置模块，用于与所述终端之间建立所述DRB的承载通道。
  45. 如权利要求44所述的接入设备，其中，所述能力信息中包括以下内容之一或任意组合：
    协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
    所述终端的地址；
    所述终端是否支持用户面数据经由第二接入设备分流的指示信息。
  46. 如权利要求44所述的接入设备，其中，用于指示所述终端配置所述DRB的信息，包括以下内容之一或任意组合：
    协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
    所述承载通道的配置信息，所述承载通道的配置信息中至少包括：所述承载通道中的分组数据汇聚协议(PDCP)实体与逻辑信道标识的对应关系；
    所述DRB的标识。
  47. 如权利要求46所述的接入设备，其中，所述承载通道所用的协议包括以下之一：网际协议(IP)，传输控制协议(TCP)，用户数据报协议(UDP)，用户面通用分组无线业务协议(GTP-U)，超文本传输协议(HTTP)，超文本传输安全协议(HTTPS)。
  48. 如权利要求44所述的接入设备，其中，
    所述承载通道为使用TCP协议建立的TCP或UDP连接，所述承载通道的配置信息中还包括：所述TCP或UDP连接的端口信息。
  49. 如权利要求48所述的接入设备，其中，所述承载配置模块还用于：在指示所述终端配置所述DRB之前，根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的逻辑信道(LC)实 体分配一个TCP或UDP端口，其中，所述终端的所述DRB对应配置有一个LC实体；或者，
    所述承载配置模块还用于：预先为LC实体分配一个TCP或UDP端口，所述承载通道的配置信息中还包括所述终端的标识，其中，所述终端的多个DRB承载对应配置有一个LC实体；或者，
    所述承载配置模块还用于：在指示所述终端配置所述DRB之前，根据所述终端的能力信息确认所述终端支持用户面数据经由第二接入设备分流，则为所述终端对应的需要经由第二接入设备分流的DRB分配对应的一个TCP或UDP端口。
  50. 如权利要求44所述的接入设备，其中，所述承载通道为使用IP协议建立的IP连接，所述承载通道的配置信息中还包括：所述终端的标识信息。
  51. 如权利要求44所述的接入设备，其中，所述承载通道中，所述终端与所述第第二接入设备之间为所用GTP-U协议建立的空口GTP-U连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息。
  52. 如权利要求44所述的接入设备，其中，所述承载通道中，所述终端与所述第二接入设备之间为空口UDP或TCP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口UDP或TCP链接的配置信息。
  53. 如权利要求44所述的接入设备，其中，所述承载通道中，所述终端与所述第二接入设备之间为空口IP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口IP连接的配置信息。
  54. 如权利要求44所述的接入设备，其中，所述承载配置请求模块还用于，若承载通道中，所述第一接入设备与所述第二接入设备间的连接为GTP-U连接，则向所述第二接入设备发送GTP-U连接配置信息，所述GTP-U连接配置信息包括：
    协议类型指示信息，所述协议类型指示信息指示的协议为GTP-U协议；
    所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息，以及所述第一接入设备与所述第二接入设备之间的GTP-U连接的配置信息；
    所述DRB的标识。
  55. 如权利要求44至54中任一项所述的接入设备，还包括：
    传输模块，用于接收来自于核心网的用户面数据，将所述用户面数据通过与所述终端之间经由第二接入设备的DRB的承载通道发送给所述终端；和/或，
    通过所述承载通道接收来自于所述终端的用户面数据，并将所述用户面数据向所述核心网发送。
  56. 一种终端，包括：
    上报模块，用于向第一接入设备上报所述终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
    承载配置接收模块，用于接收所述第一接入设备发送的配置请求，所述配置请求用于请求所述终端配置所述终端与所述第一接入设备之间经由第二接入设备分流的数据无线承载(DRB)；其中，所述第一接入设备与所述第二接入设备支持不同的接入方式；
    承载配置模块，用于与所述第一接入设备之间建立所述DRB的承载通道。
  57. 如权利要求56所述的终端，其中，所述能力信息中包括以下内容之一或任意组合：
    协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
    所述终端的地址；
    所述终端是否支持用户面数据经由第二接入设备分流的指示信息。
  58. 如权利要求56所述的终端，其中，用于指示所述终端配置所述DRB的信息，包括以下内容之一或任意组合：
    协议类型指示信息，所述协议类型指示信息用于指示所述终端建立所述承载通道所用的协议；
    所述承载通道的配置信息，所述承载通道的配置信息中至少包括：所述承载通道中的分组数据汇聚协议(PDCP)实体与逻辑信道标识的对应关系；
    所述DRB的标识。
  59. 如权利要求58所述的终端，其中，所述承载通道所用的协议包括以下之一：网际协议(IP)，传输控制协议(TCP)，用户数据报协议(UDP)，用户面通用分组无线业务协议(GTP-U)，超文本传输协议(HTTP)，超文本传输安全协议(HTTPS)。
  60. 如权利要求56所述的终端，其中，所述承载通道为使用TCP协议建立的TCP或UDP连接，所述承载通道的配置信息中还包括：所述TCP或UDP连接的端口信息。
  61. 如权利要求56所述的终端，其中，所述承载通道为使用IP协议建立的IP连接，所述承载通道的配置信息中还包括：所述终端的标识信息。
  62. 如权利要求56所述的终端，其中，所述承载通道中，所述终端与所述第第二接入设备之间为所用GTP-U协议建立的空口GTP-U连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备之间的空口GTP-U连接的配置信息。
  63. 如权利要求56所述的终端，其中，所述承载通道中，所述终端与所述第二接入设备之间为空口UDP或TCP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口UDP或TCP链接的配置信息。
  64. 如权利要求56所述的终端，其中，所述承载通道中，所述终端与所述第二接入设备之间为空口IP连接，所述承载通道的配置信息中还包括：所述终端与所述第二接入设备间的空口IP连接的配置信息。
  65. 如权利要求56至64中任一项所述的终端，还包括：
    传输模块，用于将用户面数据通过与所述第一接收设备之间经由第二接入设备的DRB的承载通道发送给所述第一接入设备，其中，所述第一接入设备与第二接入设备采用不同的接入技术；和/或，
    通过所述承载通道接收来自于所述第一接入设备的用户面数据。
  66. 一种接入设备，包括处理器，收发机和存储器；其中
    所述处理器用于读取所述存储器中的计算机可读程序以执行下列操作：
    获得终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
    根据所述终端的能力信息以及用于为所述终端进行数据分流的第二接入设备，请求所述终端配置所述终端与所述第一接入设备之间经由所述第二接入设备的数据无线承载(DRB)；其中，第一接入设备与第二接入设备支持不同的接入技术；
    与所述终端之间建立所述DRB的承载通道；
    所述收发机用于接收和发送数据；
    所述存储器用于保存所述处理器执行操作时所使用的数据。
  67. 一种终端，包括处理器，收发机和存储器；其中
    所述处理器用于读取所述存储器中的计算机可读程序以执行下列操作：
    向第一接入设备上报所述终端的能力信息，所述能力信息用以表明所述终端对用户面数据分流传输的支持能力；
    接收所述第一接入设备发送的配置请求，所述配置请求用于请求所述终端配置所述终端与所述第一接入设备之间经由第二接入设备分流的数据无线承载(DRB)；其中，所述第一接入设备与所述第二接入设备支持不同的接入方式；
    与所述第一接入设备之间建立所述DRB的承载通道；
    所述收发机用于接收和发送数据；
    所述存储器用于保存所述处理器执行操作时所使用的数据。
PCT/CN2016/078310 2015-04-10 2016-04-01 数据无线承载配置方法、数据传输方法及设备 WO2016161915A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510170313.6A CN104869666B (zh) 2015-04-10 2015-04-10 数据无线承载配置方法、数据传输方法及设备
CN201510170313.6 2015-04-10

Publications (1)

Publication Number Publication Date
WO2016161915A1 true WO2016161915A1 (zh) 2016-10-13

Family

ID=53915072

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/078310 WO2016161915A1 (zh) 2015-04-10 2016-04-01 数据无线承载配置方法、数据传输方法及设备

Country Status (3)

Country Link
CN (1) CN104869666B (zh)
TW (1) TWI638575B (zh)
WO (1) WO2016161915A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109451593A (zh) * 2017-08-17 2019-03-08 宏达国际电子股份有限公司 处理用于无线承载的承载型态改变的装置及方法
WO2019137473A1 (zh) * 2018-01-12 2019-07-18 华为技术有限公司 通信方法和装置
CN110035566A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 数据传输方法、网络设备及存储介质
KR20190133239A (ko) * 2017-03-31 2019-12-02 후아웨이 테크놀러지 컴퍼니 리미티드 중계 통신 방법과 중계 통신 장치 및 시스템
US20210377840A1 (en) * 2019-02-15 2021-12-02 Huawei Technologies Co., Ltd. Communication Method And Related Apparatus
WO2023151585A1 (zh) * 2022-02-11 2023-08-17 维沃移动通信有限公司 终端目标面能力上报、获取方法、终端及网络设备

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104869666B (zh) * 2015-04-10 2019-05-21 电信科学技术研究院 数据无线承载配置方法、数据传输方法及设备
CN106376095A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种融合组网系统中建立传输通道的方法和装置
US10251052B2 (en) * 2015-08-27 2019-04-02 Mediatek Inc. Method of dynamic PDCP status report polling for LTE-WLAN aggregation
WO2017076826A1 (en) * 2015-11-04 2017-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Method, system and device for providing flow control in a split bearer environment
CN105682150A (zh) * 2016-02-25 2016-06-15 努比亚技术有限公司 多链路智能分流方法及移动终端
CN107659956B (zh) * 2016-07-26 2021-03-30 财团法人工业技术研究院 以用户设备反馈控制可配置承载的基站、用户设备及方法
CN107682878B (zh) 2016-08-01 2020-06-30 北京佰才邦技术有限公司 一种指示终端能力的方法、装置、终端及基站
CN107979853B (zh) * 2016-10-25 2022-08-02 中兴通讯股份有限公司 数据的传输方法和装置、用户设备及基站
WO2018094693A1 (zh) * 2016-11-25 2018-05-31 华为技术有限公司 数据传输方法、装置和系统
CN108631940B (zh) * 2017-03-24 2019-10-18 维沃移动通信有限公司 一种数据传输方法、发送端设备及接收端设备
CN109150388B (zh) * 2017-06-16 2022-06-21 北京三星通信技术研究有限公司 支持pdcp重复功能的系统、数据传输方法及网络设备
KR20240010085A (ko) 2017-05-05 2024-01-23 삼성전자주식회사 패킷 데이터 수렴 프로토콜 복제 기능을 지원하는 시스템, 데이터 송신 방법 및 네트워크 장비, 및 부가적 상향링크 반송파 구성 정보를 전송하는 방법 및 장치 그리고 연결 이동성 조정을 수행하는 방법 및 장치
CN109246837B (zh) 2017-06-12 2023-05-05 华为技术有限公司 通信方法和装置以及无线接入网络
CN109151891B (zh) * 2017-06-15 2022-04-05 华为技术有限公司 一种通信处理方法和通信装置
JP7085002B2 (ja) * 2018-01-05 2022-06-15 オッポ広東移動通信有限公司 データ無線ベアラの識別子の割り当て方法、ネットワークノード及びコンピュータ記憶媒体
CN112153758B (zh) 2018-04-10 2021-10-15 华为技术有限公司 通信方法和通信装置
SG11202110001SA (en) * 2019-03-11 2021-10-28 Spreadtrum Communications Shanghai Co Ltd Data sending method, terminal device, and storage medium
CN109769290B (zh) * 2019-04-10 2019-07-19 展讯通信（上海）有限公司 数据发送方法和终端设备
CN110071869B (zh) * 2019-04-10 2022-04-05 展讯通信（上海）有限公司 数据发送方法、Wi-Fi设备和存储介质
CN113543367B (zh) * 2020-04-20 2024-04-02 大唐移动通信设备有限公司 一种信息传输方法、装置、设备及计算机可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220721A (zh) * 2012-01-20 2013-07-24 中兴通讯股份有限公司 无线接入能力上报方法和基站、策略控制方法和系统
CN103517255A (zh) * 2012-06-15 2014-01-15 中兴通讯股份有限公司 一种业务分流方法、移动性管理实体及终端
CN103582011A (zh) * 2012-07-26 2014-02-12 中兴通讯股份有限公司 一种进行多网络联合传输的系统、用户设备及方法
EP2744260A1 (en) * 2011-09-06 2014-06-18 Huawei Technologies Co., Ltd Data transmission method and device
CN104869666A (zh) * 2015-04-10 2015-08-26 电信科学技术研究院 数据无线承载配置方法、数据传输方法及设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2688363B1 (en) * 2011-05-31 2017-11-29 Huawei Technologies Co., Ltd. System, device for convergence transmission and method for data distribution convergence
US8711699B2 (en) * 2011-10-31 2014-04-29 Amazon Technologies, Inc. Prioritizing application data for transmission in a wireless user device
CN104185209B (zh) * 2013-05-24 2019-11-19 中兴通讯股份有限公司 一种小蜂窝基站接入系统及其实现网络接入的方法
CN104219722B (zh) * 2014-05-23 2019-07-23 中兴通讯股份有限公司 双连接无线承载的迁移处理、迁移方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2744260A1 (en) * 2011-09-06 2014-06-18 Huawei Technologies Co., Ltd Data transmission method and device
CN103220721A (zh) * 2012-01-20 2013-07-24 中兴通讯股份有限公司 无线接入能力上报方法和基站、策略控制方法和系统
CN103517255A (zh) * 2012-06-15 2014-01-15 中兴通讯股份有限公司 一种业务分流方法、移动性管理实体及终端
CN103582011A (zh) * 2012-07-26 2014-02-12 中兴通讯股份有限公司 一种进行多网络联合传输的系统、用户设备及方法
CN104869666A (zh) * 2015-04-10 2015-08-26 电信科学技术研究院 数据无线承载配置方法、数据传输方法及设备

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11229067B2 (en) 2017-03-31 2022-01-18 Huawei Technologies Co., Ltd. Relay communication method and relay communications apparatus and system
US11770865B2 (en) 2017-03-31 2023-09-26 Huawei Technologies Co., Ltd. Relay communication method and relay communications apparatus and system
KR20190133239A (ko) * 2017-03-31 2019-12-02 후아웨이 테크놀러지 컴퍼니 리미티드 중계 통신 방법과 중계 통신 장치 및 시스템
KR102305715B1 (ko) 2017-03-31 2021-09-27 후아웨이 테크놀러지 컴퍼니 리미티드 중계 통신 방법과 중계 통신 장치 및 시스템
CN109451593A (zh) * 2017-08-17 2019-03-08 宏达国际电子股份有限公司 处理用于无线承载的承载型态改变的装置及方法
CN109451593B (zh) * 2017-08-17 2022-06-03 宏达国际电子股份有限公司 处理用于无线承载的承载型态改变的装置及方法
US11516862B2 (en) 2018-01-12 2022-11-29 Huawei Technologies Co., Ltd. Communication method and apparatus
CN113038542A (zh) * 2018-01-12 2021-06-25 华为技术有限公司 通信方法和装置
CN110035566A (zh) * 2018-01-12 2019-07-19 华为技术有限公司 数据传输方法、网络设备及存储介质
CN110035566B (zh) * 2018-01-12 2023-04-28 华为技术有限公司 数据传输方法、网络设备及存储介质
WO2019137473A1 (zh) * 2018-01-12 2019-07-18 华为技术有限公司 通信方法和装置
US11856627B2 (en) 2018-01-12 2023-12-26 Huawei Technologies Co., Ltd. Communication method and apparatus
US20210377840A1 (en) * 2019-02-15 2021-12-02 Huawei Technologies Co., Ltd. Communication Method And Related Apparatus
WO2023151585A1 (zh) * 2022-02-11 2023-08-17 维沃移动通信有限公司 终端目标面能力上报、获取方法、终端及网络设备

Also Published As

Publication number Publication date
TW201637506A (zh) 2016-10-16
TWI638575B (zh) 2018-10-11
CN104869666B (zh) 2019-05-21
CN104869666A (zh) 2015-08-26

Similar Documents

Publication Publication Date Title
TWI638575B (zh) Data radio bearer configuration method, data transmission method and device
CN108307472B (zh) 设备直通系统的通信方法及装置、通信系统
EP3213580B1 (en) Method and apparatus of lwa pdu routing
EP2672752B1 (en) Wireless bearing building method, access point equipment, user equipment and system
CN111212459B (zh) 一种中继通信方法及装置
CA2973048C (en) Bridged local area network communication between a device and a cellular access network node
EP3335520B1 (en) Methods of operating network nodes in a communication network, and network nodes implementing the same
US20160157155A1 (en) Selective Bearer Splitting in Cell System
US10219178B2 (en) Channel aggregation using Wi-Fi
CN106664624B (zh) 用于无线连接管理的方法和装置
US10506644B2 (en) Radio access network device, data processing method, and IP packet processing method
KR20180125450A (ko) 중계 전송 방법과 장치, 및 중계 단말 장비
JP7147883B2 (ja) ｇＮＢ－ＣＵ－ＵＰにおける完全性保護のハンドリング
WO2017118191A1 (zh) 一种控制面信息的传输方法及装置
WO2020244652A1 (zh) 一种通信方法及相关设备
US20230239940A1 (en) Data transmission method and apparatus
JP2022549953A (ja) データパケット送信方法および装置
US20200163004A1 (en) Multiple Air Interface Aggregation Supporting Multivendor 4G/5G Networks
US20230276313A1 (en) Managing sidelink communication
CN106465439B (zh) 多流聚合方法、装置及系统
RU2803196C1 (ru) Способ передачи пакета данных и устройство
WO2023286783A1 (ja) 通信制御方法
WO2016095586A1 (zh) 一种实现用户面地址绑定的方法和装置
WO2016074222A1 (zh) 数据传输方法及设备

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: 16776090

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16776090

Country of ref document: EP

Kind code of ref document: A1