WO2017118225A1 - 双连接中实现重配置的方法、主服务基站及辅服务基站 - Google Patents

双连接中实现重配置的方法、主服务基站及辅服务基站 Download PDF

Info

Publication number
WO2017118225A1
WO2017118225A1 PCT/CN2016/106274 CN2016106274W WO2017118225A1 WO 2017118225 A1 WO2017118225 A1 WO 2017118225A1 CN 2016106274 W CN2016106274 W CN 2016106274W WO 2017118225 A1 WO2017118225 A1 WO 2017118225A1
Authority
WO
WIPO (PCT)
Prior art keywords
senb
target
source
target senb
data
Prior art date
Application number
PCT/CN2016/106274
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 WO2017118225A1 publication Critical patent/WO2017118225A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the embodiments of the present invention relate to a mobile communication technology, and in particular, to a method for implementing reconfiguration in a dual connectivity, a primary serving base station, and a secondary serving base station.
  • FIG. 1 is a schematic diagram of a network architecture of a dual connectivity (DC) in the related art.
  • a primary serving base station MeNB
  • MME Mobility Management Entity
  • S1-MME Serving Mobility Management Entity
  • Secondary eNB Secondary eNB
  • MCG bearer the primary cell group bearer
  • S-GW Serving Gateway
  • SeNB does not participate in data transmission to the user plane.
  • the MeNB is connected to the S-GW through S1-U, and the MeNB is connected to the SeNB through X2-U.
  • the SeNB connects to the S-GW through the S1-U, and the MeNB does not participate in data transmission to the user plane.
  • LTE 2 is a user plane data protocol stack of Long Term Evolution (LTE) in the related art, as shown in FIG. 2, through a user plane GPRS tunneling protocol (GTP-U, GPRS Tunnelling Protocol for the User Plane).
  • GTP-U user plane GPRS tunneling protocol for the User Plane.
  • the received downlink data is unpacked and then passed through the Packet Data Convergence Protocol (PDCP) sublayer, the Radio Link Control (RLC) protocol sublayer, and the medium access control (MAC, Medium).
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC medium access control
  • PHY physical layer
  • the uplink data is transmitted in the opposite direction to the downlink data.
  • 3GPP 3rd Generation Partnership Project
  • 1A that is, the UE carries the user plane directly on the MeNB and the SeNB.
  • 3C that is, the MeNB does the shunt anchor point.
  • the data is split between the PDCP layer and the RLC layer and sent to the MeNB and the SeNB for transmission, as shown in FIG. 4 .
  • the purpose of the dual connectivity is to reduce the signaling impact on the core network and ensure the data throughput and user experience of the UE when the user plane of the UE is transferred between SeNBs under the same MeNB.
  • the user plane still has a large interruption due to the reconstruction of the PDCP layer during reconfiguration.
  • the UE still performs the operation of disconnecting and then connecting, that is, the UE establishes a connection with the target SeNB after disconnecting from the source SeNB.
  • the role of the SeNB is assumed by the micro base station or the low power node, and the role of the MeNB is assumed by the macro base station node.
  • the SeNB Since the micro base station or the low power node is closer to the UE and the coverage is smaller, the SeNB will carry more user plane offload data than the MeNB. Therefore, even if the UE is temporarily disconnected from the SeNB, the user throughput is sharp. decline.
  • the embodiments of the present invention provide a method for implementing reconfiguration in dual connectivity, a primary serving base station, and a secondary serving base station, which can avoid a sharp drop in user plane data throughput.
  • an embodiment of the present invention provides a method for implementing reconfiguration in a dual connectivity.
  • the method includes:
  • the target SeNB forwards the uplink radio link control RLC data protocol data unit PDU to the source SeNB, and the source SeNB offloads the downlink packet data convergence protocol PDCP data PDU to the target SeNB.
  • the method further includes: the source SeNB maintains data transmission with the UE until reconfiguration is successful.
  • the method further includes:
  • the MeNB instructs the target SeNB to establish a corresponding offload bearer split bearer protocol entity for one or more secondary cell group bearer SCG bearers to be transferred to the target SeNB.
  • the user plane interface that provides the uplink data service and the downlink data service between the source SeNB and the target SeNB for the UE includes:
  • the MeNB receives the allocated transport layer address from the source SeNB and sends it to the target SeNB, so as to establish a user plane interface for providing the uplink data offload service for the UE between the source SeNB and the target SeNB.
  • the MeNB indicates that the target SeNB establishes a corresponding split bearer protocol entity for the SCG bearer that is to be transferred to the target SeNB on the source SeNB, including:
  • the MeNB sends an admission request message to the target SeNB, where the admission request message carries the split bearer configuration information or the indication information of the split bearer.
  • the split bearer configuration information or the indication information of the split bearer is used to establish, on the source SeNB, one or more split bearer protocols corresponding to the SCG bearer to be transferred to the target SeNB on the target SeNB. entity.
  • the MeNB sends the transport layer address that is allocated by the target SeNB to the source SeNB, so that the user plane interface that provides the downlink data offload service for the UE between the source SeNB and the target SeNB includes:
  • the target SeNB After completing the resource configuration of the UE, the target SeNB replies an acknowledgement message to the MeNB, where the acknowledgement message carries a transport layer address allocated for receiving the downlink PDCP data PDU of the established split bearer;
  • the MeNB After receiving the acknowledgement message, the MeNB sends a modify request message to the source SeNB, where the modify request message carries the transport layer address allocated by the target SeNB, and the purpose is to establish the source SeNB and the target SeNB. For providing downlink data offloading services for UEs User interface.
  • the MeNB receives the allocated transport layer address from the source SeNB and sends the information to the target SeNB, so that the user plane interface for providing the uplink data offload service for the UE between the source SeNB and the target SeNB includes:
  • the source SeNB sends a modify request acknowledgement message to the MeNB, where the modify request acknowledgement message carries a transport layer address allocated for receiving the uplink RLC data PDU of the established split bearer;
  • the MeNB After receiving the modification request acknowledgement message of the source SeNB, the MeNB sends an X2 notification message to the target SeNB, where the X2 notification message carries the transport layer address allocated by the source SeNB, and the purpose is to establish the A user plane interface for providing an uplink data offload service between the source SeNB and the target SeNB.
  • the method further includes:
  • the MeNB After receiving the modification request acknowledgement message of the source SeNB, the MeNB forms a radio resource control RRC signaling for the UE according to the information carried in the received acknowledgement message and sends the RRC signaling to the UE; Instructing the MeNB to synchronize the RRC signaling of the first or more SCGbearers from the source SeNB to the target SeNB, and synchronize with the target SeNB according to the information carried in the obtained RRC signaling.
  • the target SeNB initiates random access, establishes an SCG bearer according to the new configuration, and establishes a corresponding split bearer protocol entity.
  • the forwarding, by the target SeNB, the uplink RLC data PDU to the source SeNB includes: forwarding the uplink RLC data PDU to the source by using a transport layer address allocated for receiving the uplink RLC data PDU of the established split bearer SeNB;
  • the offloading of the downlink PDCP data PDU to the target SeNB by the source SeNB includes: offloading part or all of the downlink PDCP data PDU to the target SeNB by using a transport layer address allocated for receiving the downlink PDCP PDU of the established split bearer transmission.
  • data is split between the PDCP layer and the RLC layer of the source SeNB, And transmitting to the source SeNB and the target SeNB respectively, where the target SeNB only establishes a protocol entity under the PDCP layer; after receiving the two downlink data from the air interface, the UE performs merging at the PDCP layer;
  • the data On the uplink, the data is split between the RLC layer and the MAC of the UE, and is sent to the source SeNB and the target SeNB through an air interface, and only the protocol entity under the RLC layer is established on the target SeNB; After receiving the uplink data, the target SeNB sends the data to the source SeNB, and performs merging at the RLC layer of the source SeNB.
  • the method further includes:
  • the target SeNB After the UE accesses the target SeNB and completes the configuration update, if the target SeNB has received the offloaded downlink PDCP data PDU from the source SeNB through the X2-U, the target SeNB starts to pass the downlink PDCP data PDU through the split.
  • the bearer's lower layer protocol entity processes and sends it to the UE.
  • the method further includes:
  • the uplink data packet is sent to the target SeNB by using a split bearer and/or an SCG bearer protocol entity corresponding to the target SeNB.
  • the method further includes:
  • the source SeNB After the source SeNB allocates the SN number of the PDCP sublayer for all the downlink data packets, the SN status transmission message is sent to the target SeNB, and the target SeNB starts to receive the downlink data from the S-GW according to the SN status transmission message.
  • the SN number of the PDCP sub-layer is allocated by the packet; after the source SeNB completes the sending and/or forwarding of all downlink data, requesting the MeNB to perform the release of the source SeNB;
  • the target SeNB successfully sends all downlink forwarding data, or has received uplink data packets from the UE from the SCG bearer protocol entity and has completed all forwarding uplink data. Sorting the packets, requesting the MeNB to delete the split bearer protocol entity;
  • the MeNB After the MeNB receives the message that the source SeNB and the target SeNB release the source SeNB and deletes the split bearer protocol entity, the MeNB sends an SeNB release confirmation message to the source SeNB, where the MeNB The target SeNB sends an SeNB modification acknowledgement message, and the MeNB sends an RRC connection reconfiguration message to the UE, requesting the UE to delete the corresponding split bearer.
  • the embodiment of the present invention further provides a primary serving base station, including a first processing unit, configured to establish a user plane interface between the source SeNB and the target SeNB to provide an uplink data service and a downlink data service for the UE.
  • a primary serving base station including a first processing unit, configured to establish a user plane interface between the source SeNB and the target SeNB to provide an uplink data service and a downlink data service for the UE.
  • the first processing unit includes a first establishing module, and a second establishing module, where
  • a first establishing module configured to send a transport layer address allocated from the target SeNB to a source SeNB, so as to establish a user plane interface for providing a downlink data offload service for the UE between the source SeNB and the target SeNB;
  • a second establishing module configured to receive an allocated transport layer address from the source SeNB, and send the information to the target SeNB, so as to establish an uplink data offload service for the UE between the source SeNB and the target SeNB User plane interface; constitutes UE-oriented RRC signaling and sends it to the UE.
  • the first establishing module is further configured to: instruct the target SeNB to establish a corresponding split bearer protocol entity for one or more SCG bearers on the source SeNB to be transferred to the target SeNB.
  • the first establishing module is specifically configured to:
  • the second establishing module is specifically configured to:
  • the X2 notification message of the transport layer address allocated by the uplink RLC data PDU of the split bearer; the RRC signaling for the UE is formed according to the information carried in the received acknowledgement message and sent to the UE.
  • the second establishing module is further configured to:
  • the present invention further provides a secondary serving base station, comprising: a second processing unit, and/or a third processing unit; wherein
  • a second processing unit configured to establish, according to an indication from the MeNB, a corresponding split bearer protocol entity for one or more SCG bearers to be transferred to the target SeNB on the source SeNB; to receive the downlink PDCP data PDU of the established split bearer Allocating a transport layer address; receiving a transport layer address allocated by the source SeNB from the MeNB, establishing a user plane interface for providing an uplink data offload service for the UE between the source SeNB and the target SeNB;
  • a third processing unit configured to allocate a transport layer address for receiving an uplink RLC data PDU of the established split bearer; receive an allocated transport layer address of the target SeNB from the MeNB; and establish downlink data for the UE between the source SeNB and the target SeNB The user plane interface of the offload service.
  • the second processing unit is specifically configured to:
  • a modification request acknowledgement message carrying a transport layer address allocated by the source SeNB for receiving an uplink RLC data PDU of the established split bearer; establishing between the source SeNB and the target SeNB The UE provides a user plane interface of the uplink data offload service;
  • the uplink RLC data PDU is forwarded to the source SeNB.
  • the third processing unit is specifically configured to:
  • the downlink PDCP data PDU is offloaded to the target SeNB.
  • the third processing unit is further configured to: maintain data transmission with the UE until reconfiguration succeeds.
  • the third processing unit is further configured to: after receiving the SN number of the PDCP sublayer for all downlink data packets when receiving the end identifier from the S-GW, send an SN status transmission message to the target SeNB, and complete After transmitting and/or forwarding all downlink data, requesting the MeNB to perform the source SeNB release; accordingly,
  • the second processing unit is further configured to: according to the SN status transmission message, start to allocate the SN number of the PDCP sublayer for receiving the downlink data packet from the S-GW; after all the downlink forwarding data has been successfully sent, or has been from the SCG
  • the bearer protocol entity receives the uplink data packet from the UE and has completed all the sorting of the forwarded uplink data packet, and requests the MeNB to delete the split bearer protocol entity.
  • a computer storage medium is further provided, and the computer storage medium may store an execution instruction for performing a method for implementing reconfiguration in the dual connection in the foregoing embodiment.
  • the technical solution of the present application includes: in the process of reconfiguring the user plane bearer of the UE from the source SeNB to the target SeNB in the same MeNB, establishing an uplink data service between the source SeNB and the target SeNB for the UE And the user plane interface of the downlink data service; in the reconfiguration process, the target SeNB forwards the uplink RLC data PDU to the source SeNB, and the source SeNB offloads the downlink PDCP data PDU to the target SeNB.
  • the UE establishes a user plane interface for providing the uplink/downlink data service between the source SeNB and the target SeNB in the process of establishing the connection with the target SeNB, thereby solving the problem that the UE synchronizes with the target SeNB and establishes a connection.
  • the problem of data transmission with the network side at the micro base station or the low power node level cannot be avoided, thereby avoiding a sharp drop in user plane data throughput and ensuring the user experience of the UE in user plane reconfiguration.
  • the target SeNB does not need to re-transmit the downlink data that has been sent to the source SeNB before the reconfiguration occurs, and then sends the downlink data to the UE through the PDCP layer. That is, the downlink data that has been sent to the source SeNB does not need to be forwarded to the target SeNB through data pre-transmission. It also does not need to be repackaged by the PDCP layer of the target SeNB and then sent to the UE, thereby reducing the waste of repeated processing.
  • FIG. 1 is a schematic diagram of a network architecture of a DC in a related art
  • FIG. 3 is a schematic diagram of a dual connectivity user plane 1A in the related art
  • FIG. 4 is a schematic diagram of a dual connectivity user plane 3C in the related art
  • FIG. 5 is a flowchart of a method for implementing reconfiguration in dual connectivity according to the present invention.
  • FIG. 6 is a schematic flowchart of an embodiment of implementing reconfiguration in dual connectivity according to the present invention.
  • FIG. 7 is a schematic diagram of a first embodiment of a user plane protocol entity and downlink data transmission according to the present invention.
  • FIG. 8 is a schematic diagram of a second embodiment of a user plane protocol entity and downlink data transmission according to the present invention.
  • FIG. 9 is a schematic diagram of a third embodiment of a user plane protocol entity and uplink data transmission according to the present invention.
  • FIG. 10 is a schematic diagram of a fourth embodiment of a user plane protocol entity and uplink data transmission according to the present invention.
  • FIG. 11 is a schematic structural diagram of a structure of a primary serving base station according to the present invention.
  • FIG. 12 is a schematic structural diagram of a structure of a secondary serving base station according to the present invention.
  • the user plane bearer of the UE is transferred from the source SeNB to the target SeNB under the same MeNB.
  • the MeNB performs the process of adding the target SeNB first and then deleting the source SeNB, the actual UE needs to be performed.
  • the connection is disconnected from the source SeNB, and the connection with the target SeNB is established. Therefore, there is also a problem that the user throughput is drastically reduced due to the short disconnection of the UE and the SeNB.
  • the UE establishes a user plane interface for providing uplink/downlink data service between the source SeNB and the target SeNB in the process of establishing the connection with the target SeNB, thereby solving the UE in and
  • the target SeNB performs uplink and downlink synchronization and establishes a connection, it cannot communicate with the network side at the micro base station or the low power node level, thereby avoiding a sharp drop in user plane data throughput and ensuring that the UE is reconfigured at the user plane.
  • the target SeNB does not need to re-transmit the downlink data that has been sent to the source SeNB before the reconfiguration occurs, and then sends the downlink data to the UE through the PDCP layer. That is, the downlink data that has been sent to the source SeNB does not need to be forwarded to the target SeNB through data pre-transmission. It also does not need to be repackaged by the PDCP layer of the target SeNB and then sent to the UE, thereby reducing the waste of repeated processing.
  • FIG. 5 is a flowchart of a method for implementing reconfiguration in a dual connectivity according to the present invention.
  • the method includes:
  • Step 500 Establish a user plane interface between the source SeNB and the target SeNB to provide an uplink data service and a downlink data service for the UE.
  • the MeNB indicates that the target SeNB establishes a corresponding split bearer protocol entity for the SCG bearer on the source SeNB that is to be transferred to the target SeNB.
  • the MeNB sends an accept request message to the target SeNB, where the bearer request message carries the key information, the UE security capability information, the SCG bearer configuration information, and the like in addition to the X2-AP message (SeNB addition request) in the related protocol.
  • the split bearer configuration information or the indication information of the split bearer is used to establish a corresponding split bearer protocol entity on the target SeNB for one or more SCG bearers on the source SeNB to be transferred to the target SeNB.
  • the implementation of this step includes: the MeNB sends a transport layer address, such as a GPRS Tunneling Protocol (TTM) Tunnel Endpoint Identity (TEID), from the target SeNB to the source SeNB, so that the source SeNB and A user plane interface for providing downlink data offloading services for the UE is established between the target SeNBs.
  • a transport layer address such as a GPRS Tunneling Protocol (TTM) Tunnel Endpoint Identity (TEID)
  • TTM GPRS Tunneling Protocol
  • TEID Tunnel Endpoint Identity
  • the target SeNB determines, based on the received information, whether there are sufficient resources to allow access by the UE. If the access is allowed, the target SeNB, after completing the resource configuration of the UE, replies to the MeNB with an acknowledgement message, and in the admission confirmation message, the SeNB adds a request to the target SeNB to accept the admission.
  • the SCG bearer configuration information at least the downlink PDCP data protocol for the split bearer established for reception is carried.
  • the MeNB After receiving the admission confirmation message, the MeNB sends a modification request message to the source SeNB.
  • the modification request message carries a transport layer address, such as a GTP TEID, allocated by the target SeNB, and the purpose is to establish a user plane interface between the source SeNB and the target SeNB to provide a downlink data offload service for the UE.
  • the bearer type on the source SeNB is changed from SCG bearer to split bearer.
  • the MeNB receives the allocated transport layer address from the source SeNB, such as the GTP TEID, and sends it to the target SeNB, so as to establish a user plane interface between the source SeNB and the target SeNB to provide the uplink data offload service for the UE.
  • the source SeNB such as the GTP TEID
  • the target SeNB so as to establish a user plane interface between the source SeNB and the target SeNB to provide the uplink data offload service for the UE.
  • the source SeNB such as the GTP TEID
  • the source SeNB sends a modification request acknowledgement message to the MeNB.
  • the modification request acknowledgement message carries a transport layer address, such as a GTP TEID, allocated for receiving the uplink RLC data PDU of the split bearer established;
  • the MeNB After receiving the modification request acknowledgement message of the source SeNB, the MeNB sends an X2 notification message to the target SeNB.
  • the X2 notification message carries a transport layer address, such as a GTPTEID, allocated by the active SeNB, and the purpose is to establish a user plane interface between the source SeNB and the target SeNB to provide an uplink data offload service for the UE.
  • the step further includes: after receiving the modification request acknowledgement message of the source SeNB, the MeNB forms a radio resource control (RRC) signaling for the UE according to the information carried in the received acknowledgement message.
  • RRC radio resource control
  • the UE After receiving the indication from the MeNB to transfer the RRC signaling of the first or multiple SCG bearers from the source SeNB to the target SeNB, the UE synchronizes with the target SeNB according to the information carried in the RRC signaling, and initiates a random to the target SeNB. Access, establish an SCG bearer according to the new configuration, and establish a corresponding split bearer protocol entity.
  • Step 501 In the reconfiguration process, the target SeNB forwards the uplink RLC data PDU to the source SeNB, and the source SeNB offloads the downlink PDCP data PDU to the target SeNB and maintains data transmission with the UE until the reconfiguration succeeds.
  • the source SeNB may offload some or all of the downlink PDCP data PDUs to the destination by using a transport layer address, such as a GTP TEID, allocated for receiving the downlink PDCP PDU of the established split bearer.
  • the SeNB performs transmission;
  • the target SeNB may forward the uplink RLC data PDU to the source SeNB through a transport layer address, such as a GTP TEID, allocated for receiving the uplink RLC data PDU of the established split bearer.
  • a transport layer address such as a GTP TEID
  • the RLC control PDU corresponding to the uplink RLC data PDU may be directly fed back by the source SeNB; the target SeNB may also be notified by the source SeNB, and then fed back by the target SeNB.
  • data is split between the PDCP layer and the RLC layer of the source SeNB, and is sent to the source SeNB and the target SeNB for transmission. Only the protocol entity under the PDCP layer is established on the target SeNB; the UE receives two from the air interface. After the downlink data is downlinked, the merge is performed at the PDCP layer;
  • the data is split between the RLC layer and the MAC of the UE, and is sent to the source SeNB and the target SeNB through the air interface, and only the protocol entity under the RLC layer is established on the target SeNB; after the target SeNB receives the uplink data, The signal is sent to the source SeNB for merging at the RLC layer of the source SeNB.
  • the source SeNB is configured to: split the downlink PDCP data PDU to the target SeNB for transmission, or offload all downlink PDCP data PDUs to the target SeNB for transmission:
  • the source SeNB may only offload a part of the downlink PDCP data PDU to the target SeNB, and maintain data transmission with the UE; when the signal quality of the source SeNB is already poor, the source SeNB may downlink most or all of the downlink.
  • the PDCP data PDCU is offloaded to the target SeNB, but at this time, since the UE has not yet accessed the target SeNB, the data transmission throughput of the UE will be slightly decreased.
  • the method of the present invention selects to disconnect or maintain data transmission with the source SeNB according to the signal quality of the source SeNB, so that the UE maintains the signal transmission with the source SeNB in the case that the source SeNB signal quality is still relatively good.
  • step 500 of the method of the present invention the method further includes:
  • the target SeNB accesses the target SeNB and completes the configuration update, if the target SeNB has received the offloaded downlink PDCP data PDU from the source SeNB through the X2-U, the target SeNB The downlink PDCP data PDU is processed by the lower layer protocol entity of the split bearer, and then sent to the UE.
  • the split bearer and/or the SCG bearer protocol entity corresponding to the target SeNB may be started to send the uplink data packet to the target SeNB.
  • the method further includes: the MeNB initiating a path conversion procedure to the core network to request a change of the downlink tunnel end point of all or part of the downlink data bearer.
  • the target SeNB After the source SeNB allocates the SN number of the PDCP sublayer for all the downlink data packets, the SN status transmission message is sent to the target SeNB, and the target SeNB may start to allocate the PDCP sublayer for receiving the downlink data packet from the S-GW according to the SN status transmission message.
  • SN number SN number;
  • the MeNB After the source SeNB completes transmission and/or forwarding of all downlink data, the MeNB is requested to perform source SeNB release.
  • the target SeNB also requests the MeNB to delete the split bearer protocol entity. Before the MeNB deletes the split bearer protocol entity, the target SeNB has successfully sent all the downlink forwarding data, or the target SeNB has received the uplink data packet from the UE from the SCG bearer protocol entity before requesting the MeNB to delete the split bearer protocol entity. And the ordering of all forwarded uplink packets has been completed.
  • the MeNB After the MeNB receives the release source SeNB from the source SeNB and the target SeNB and deletes the message of the split bearer protocol entity, the MeNB sends an SeNB release confirm message to the source SeNB, and sends a SeNB modification acknowledgement message to the target SeNB. Confirm), sending the RRC connection reconfiguration message to the UE requires the UE to delete the corresponding split bearer.
  • FIG. 6 is a schematic flowchart of an embodiment of implementing reconfiguration in a dual connectivity according to the present invention.
  • this embodiment describes that a user plane bearer of a UE is transferred after receiving a UE measurement report by the MeNB in the present invention.
  • the MeNB requests the target SeNB in addition to
  • the target SeNB is also required to establish a corresponding split bearer protocol entity for the allowed SCG bearer. Specifically, the following steps are included:
  • Step 601 The MeNB makes a decision that requires user plane reconfiguration according to the measurement report of the UE (or the result of other radio resource management functions, such as excessive load), and assumes that the user plane bearer of the UE is transferred from the source SeNB.
  • the target SeNB to the same MeNB allows the UE to continue to obtain communication services from the secondary serving base station.
  • Step 602 The MeNB sends an admission request message to the target SeNB.
  • the admission request message carries at least the split bearer configuration information or the instruction to establish a split bearer, in addition to the reference information about the related protocol X2-AP message (SeNB addition request), including the key information, the UE security capability information, and the SCG bearer configuration information. information.
  • the split bearer configuration information or the indication information of the split bearer is used to establish a corresponding split bearer protocol entity on the target SeNB for one or more SCG bearers on the source SeNB to be transferred to the target SeNB.
  • data is split between the PDCP layer and the RLC layer of the source SeNB, and is sent to the source SeNB and the target SeNB for transmission. Only the protocol entity under the PDCP layer is established on the target SeNB. After the UE receives two downlink data from the air interface, it merges at the PDCP layer.
  • the data On the uplink, the data is split between the RLC layer and the MAC of the UE, and is sent to the source SeNB and the target SeNB through the air interface, and only the protocol entity under the RLC layer is established on the target SeNB.
  • the target SeNB After receiving the uplink data, the target SeNB sends the data to the source SeNB, and performs merging at the RLC layer of the source SeNB.
  • Step 603 After receiving the admission request message, the target SeNB determines whether the UE can be admitted according to its own resource status.
  • the specific implementation of this step is well known to those skilled in the art and is not intended to limit the scope of the present invention, and details are not described herein.
  • Step 604 If the target SeNB determines that the access of the UE can be accepted, return to the MeNB. And the acknowledgement message, in addition to the SCG bearer list that the target SeNB agrees to accept, in addition to the SeNB addition request acknowledge, the at least acknowledgment message carries at least the downlink PDCP data PDU for receiving the split bearer.
  • the assigned transport layer address is GTP TEID.
  • Step 605 After receiving the admission confirmation message, the MeNB sends a modification request message to the source SeNB.
  • the modification request message informs the source SeNB of the GTP TEID received by the target SeNB through the admission confirmation message, and the purpose is to establish a user plane interface between the source SeNB and the target SeNB to provide the downlink data offload service for the UE.
  • the source SeNB may use the GTP TEID to offload some or all of the downlink PDCP data PDUs to the target SeNB for transmission by X2-U.
  • the bearer type on the source SeNB is changed from SCG bearer to split bearer.
  • Step 606 The source SeNB sends a modification request acknowledgement message to the MeNB, informing the MeNB that the configuration modification is successful.
  • the modification request acknowledgement message further carries a GTP TEID allocated for receiving the uplink RLC data PDU of the split bearer.
  • the source SeNB After the source SeNB sends the modification request acknowledgement message to the MeNB, the source SeNB starts to offload some or all of the downlink PDCP data PDUs to the target SeNB through the GTP TEID provided by the target SeNB.
  • the source SeNB may only offload a part of the downlink PDCP data PDU to the target SeNB, and maintain data transmission with the UE. If the source SeNB signal quality is already poor, the source SeNB may offload most or all of the downlink PDCP data PDCU to the target SeNB, but in this case, since the UE has not yet accessed the target SeNB, the data transmission throughput of the UE will be slightly There is a drop.
  • the source SeNB After the source SeNB sends the modification request acknowledgement message to the MeNB, the source SeNB starts to send the uplink data packet that has not been sorted to the target SeNB.
  • the sorting function of the PDCP layer of the source SeNB stops working; the source SeNB decrypts all the uplink PDCP data PDUs received subsequently, and then sends the target SeNB, and the PDCP layer of the target SeNB completes the sorting.
  • Step 607 After receiving the modification request acknowledgement message of the source SeNB, the MeNB sends the request SeNB to the target SeNB. Send an X2 notification message.
  • the X2 notification message is used to notify the target SeNB of the GTP TEID received by the source SeNB by modifying the request acknowledgement message, and the purpose is to establish a user plane interface between the source SeNB and the target SeNB to provide the uplink data offload service for the UE.
  • the target SeNB may forward the uplink RLC data PDU received by the target SeNB from the UE to the source SeNB through the GTP TEID.
  • Step 608 After receiving the modification request acknowledgement message of the source SeNB, the MeNB forms a radio resource control (RRC) signaling for the UE according to the information carried in the received acknowledgement message and sends the signal to the UE.
  • RRC radio resource control
  • Step 609 After receiving the RRC signaling from the MeNB indicating that the first or multiple SCG bearers are transferred from the source SeNB to the target SeNB, the UE determines whether the RRC connection reconfiguration request can be performed according to the requirements in the RRC signaling. If yes, the UE sends an RRC Connection Reconfiguration Complete message to the MeNB, indicating that the UE has enabled new radio resource configuration.
  • Step 610 The UE synchronizes with the target SeNB according to the information carried in the signaling, initiates random access to the target SeNB, establishes an SCG bearer according to the new configuration, and establishes a corresponding split bearer protocol entity.
  • the target SeNB After the UE accesses the target SeNB and completes the configuration update, if the target SeNB has received the offloaded downlink PDCP data PDU from the source SeNB through the X2-U, the target SeNB starts to process the downlink PDCP data PDU through the lower layer protocol entity of the split bearer. Send to the UE;
  • the split bearer or the SCG bearer protocol entity corresponding to the target SeNB may be started to send the uplink data packet to the target SeNB.
  • Step 611 After receiving the RRC connection reconfiguration complete message of the UE, the MeNB initiates a path conversion procedure to the core network to request a change of the downlink tunnel endpoint of all or part of the downlink data bearer.
  • Step 612 After receiving the end identifier from the S-GW, and allocating the SN number of the PDCP sublayer for all downlink data packets, the source SeNB sends an SN status transmission message to the target SeNB, and the target SeNB may start transmitting the message according to the SN status.
  • the SN number of the PDCP sublayer is allocated from the S-GW to receive the downlink data packet.
  • Step 613 After receiving the end identifier from the S-GW and completing all the downlink data transmission and/or forwarding, the source SeNB requests the MeNB to perform the source SeNB release.
  • Step 614 The target SeNB requests the MeNB to delete the split bearer protocol entity.
  • the target SeNB Before requesting the MeNB to delete the split bearer protocol entity, the target SeNB has successfully sent all downlink forwarding data. as well as,
  • the target SeNB Before requesting the MeNB to delete the split bearer protocol entity, the target SeNB has received the uplink data packet from the UE from the SCG bearer protocol entity, and has completed the ordering of all the forwarded uplink data packets.
  • Step 615 After receiving the message in step 613 and step 614, the MeNB sends a SeNB release confirm message to the source SeNB, and sends a SeNB modification confirm message to the target SeNB.
  • the RRC connection reconfiguration message requires the UE to delete the corresponding split bearer.
  • FIG. 7 is a schematic diagram of a first embodiment of a user plane protocol entity and downlink data transmission according to the present invention.
  • the first embodiment describes a user plane protocol entity and a downlink data on a source SeNB, a target SeNB, and a UE after path conversion is completed.
  • the source SeNB has transmitted PDCP data PDUs with SN numbers 1 to 5.
  • the UE only receives PDCP data PDUs with SN numbers 1, 2, and 4 and makes a message to the source SeNB. confirm.
  • the UE only receives partial RLC data PDUs.
  • the source SeNB forwards the PDCP data PDUs with SN numbers 3 and 5 to the target SeNB, which are processed and transmitted by the split bearer protocol entity of the target SeNB. All downlink data received from the S-GW and not yet transmitted before receiving the end identifier, such as PDCP data SDUs with SN numbers 6 to 9, are processed by the PDCP layer and then forwarded to the target SeNB by the target SeNB.
  • the split bearer protocol entity processes and sends.
  • the PDCP entity corresponding to the target SeNB starts to deliver data to the upper layer to prevent the upper layer from receiving the out-of-order data packet.
  • FIG. 8 is a schematic diagram of a second embodiment of a user plane protocol entity and downlink data transmission according to the present invention.
  • the second embodiment describes a user plane protocol entity and a downlink data on a source SeNB, a target SeNB, and a UE after path conversion is completed.
  • the source SeNB has transmitted PDCP data PDUs with SN numbers 1 to 5.
  • the UE only receives PDCP data PDUs with SN numbers 1, 2, and 4 and makes a message to the source SeNB. confirm.
  • PDCP data PDUs with SN numbers 3 and 5 the UE only receives partial RLC data PDUs.
  • the source SeNB may continue to maintain data transmission with the UE at least for a period of time, and the source SeNB may continue to send at least the RLC corresponding to the PDCP data PDUs with SN numbers 3 and 5 that have not received the UE confirmation reply.
  • Data PDU or RLC Data PDU segmentation All downlink data received from the S-GW and not yet transmitted before receiving the end identifier, such as PDCP data SDUs with SN numbers 6 to 9, are processed by the PDCP layer and then transmitted to the source SeNB or the target SeNB. As shown in FIG. 7, the source SeNB receives the PDCP data SDUs with the SN numbers of 6, 7, 8, and 9 after receiving the end identifier.
  • the source SeNB After processing through the PDCP layer, the source SeNB sets the SN number to 8, 9 The PDCP data PDU is offloaded to the target SeNB for transmission, and the PDCP data PDUs with the SN numbers of 6, 7 are left to be transmitted by the source SeNB, ensuring that the UE and the source SeNB remain in a certain state when the UE synchronizes and accesses to the target SeNB. Data transfer.
  • the PDCP entity corresponding to the target SeNB starts to deliver data to the upper layer to prevent the upper layer from receiving the out-of-order data packet.
  • FIG. 9 is a schematic diagram of a third embodiment of a user plane protocol entity and uplink data transmission according to the present invention.
  • the third embodiment describes a user plane protocol entity and uplink data transmission on a source SeNB, a target SeNB, and a UE after path conversion is completed.
  • schematic diagram As shown in FIG. 9, it is assumed that the UE has transmitted PDCP data PDUs with SN numbers 1 to 5.
  • the source SeNB When reconfiguration occurs, the source SeNB only receives PDCP data PDUs with SN numbers 1, 2, and 4 and confirms to the UE. .
  • the source SeNB only receives partial RLC data PDUs.
  • the bearer protocol entity sends to the target SeNB.
  • the target SeNB After receiving the RLC data PDU or the RLC data PDU segment, the target SeNB forwards the RLC data PDU or the RLC data PDU segment to the source SeNB, and the source SeNB combines the PDCP data PDUs with the SN numbers 3 and 5.
  • the subsequent uplink data packet such as the data packet with the SN number of 6 or later, is processed by the SCG bearer protocol entity corresponding to the target SeNB and then sent to the target SeNB.
  • the target SeNB starts to deliver data to the S-GW to prevent the upper layer from receiving the out-of-order data packet.
  • FIG. 10 is a schematic diagram of a fourth embodiment of a user plane protocol entity and uplink data transmission according to the present invention.
  • the fourth embodiment describes a user plane protocol entity and uplink data transmission on a source SeNB, a target SeNB, and a UE after path conversion is completed.
  • schematic diagram As shown in FIG. 10, it is assumed that the UE has transmitted PDCP data PDUs with SN numbers 1 to 5.
  • the source SeNB When reconfiguration occurs, the source SeNB only receives PDCP data PDUs with SN numbers 1, 2, and 4 and confirms to the UE. .
  • the source SeNB only receives partial RLC data PDUs.
  • the UE will segment the RLC data PDU or RLC data PDU that has not been sent or not successfully transmitted. And sent to the source SeNB by the split bearer protocol entity, and combined with the already received RLC data PDU or RLC data PDU segment into PDCP data PDUs with SN numbers 3 and 5.
  • the subsequent uplink data packet such as the data packet with the SN number of 6 or later, may be processed by the SCG bearer protocol entity corresponding to the target SeNB and then sent to the target SeNB.
  • the target SeNB starts to deliver data to the S-GW to prevent the upper layer from receiving the out-of-order data packet.
  • FIG. 11 is a schematic structural diagram of a primary serving base station according to the present invention.
  • a first processing unit is configured to establish a user plane interface for providing uplink data services and downlink data services between a source SeNB and a target SeNB. . among them,
  • the first processing unit includes: a first establishing module, and a second establishing module; wherein
  • a first establishing module configured to send a transport layer address allocated from the target SeNB to the source a SeNB, so as to establish a user plane interface for providing a downlink data offload service for the UE between the source SeNB and the target SeNB;
  • a second establishing module configured to receive the allocated transport layer address from the source SeNB, and send the signal to the target SeNB, and establish a user plane interface for providing an uplink data offload service for the UE between the source SeNB and the target SeNB;
  • the RRC signaling is sent to the UE.
  • the first establishing module is further configured to: indicate that the target SeNB establishes a corresponding split bearer protocol entity for one or more SCG bearers on the source SeNB that are to be transferred to the target SeNB.
  • the first establishing module is specifically configured to: send an admission request message carrying the split bearer configuration information or the indication information of the split bearer to the target SeNB.
  • the split bearer configuration information or the indication information of the split bearer is used to establish a corresponding split bearer protocol entity on the target SeNB for one or more SCG bearers on the source SeNB that are to be transferred to the target SeNB.
  • the second establishing module is specifically configured to: receive a modification request acknowledgement message from the source SeNB that carries the transport layer address allocated for receiving the uplink RLC data PDU of the established split bearer; and send the bearer carrying the active SeNB to the target SeNB to receive The X2 notification message of the transport layer address allocated by the uplink RLC data PDU of the split bearer; the RRC signaling for the UE is formed according to the information carried in the received acknowledgement message and sent to the UE.
  • the second establishing module is further configured to: when receiving the RRC connection reconfiguration complete message from the UE, initiate a path conversion procedure to the core network, requesting a change of the downlink tunnel endpoint of all or part of the downlink data bearer.
  • FIG. 12 is a schematic structural diagram of a secondary service base station according to the present invention, as shown in FIG. Comprising: a second processing unit, and/or a third processing unit; wherein
  • a second processing unit configured to establish, according to an indication from the MeNB, a corresponding split bearer protocol entity for one or more SCG bearers to be transferred to the target SeNB on the source SeNB; to receive the downlink PDCP data PDU of the established split bearer
  • the transport layer address is allocated; the transport layer address allocated by the source SeNB from the MeNB is received, and a user plane interface for providing the uplink data offload service for the UE is established between the source SeNB and the target SeNB.
  • the SCG bearer on the source SeNB that is to be transferred to the target SeNB establishes a corresponding split bearer protocol on the target SeNB. entity;
  • the uplink RLC data PDU is forwarded to the source SeNB.
  • a third processing unit configured to allocate a transport layer address for receiving an uplink RLC data PDU of the established split bearer; receive an allocated transport layer address of the target SeNB from the MeNB; and establish downlink data for the UE between the source SeNB and the target SeNB
  • the user plane interface of the offload service Specifically used for:
  • the downlink PDCP data PDU is offloaded to the target SeNB.
  • the third processing unit is further configured to: maintain data transmission with the UE until reconfiguration is successful.
  • the third processing unit is further configured to: after receiving the SN number of the PDCP sublayer for all downlink data packets when receiving the end identifier from the S-GW, send an SN status transmission message to the target SeNB, complete all downlink data transmission and/or After forwarding, requesting the MeNB to perform source SeNB release; accordingly,
  • the second processing unit is further configured to: according to the SN status transmission message, start to allocate the SN number of the PDCP sublayer for receiving the downlink data packet from the S-GW; all the downlink forwarding data has been successfully transmitted, or has been from the SCG bearer protocol
  • the entity receives the uplink data packet from the UE, and has completed all the sorting of the forwarded uplink data packet, and requests the MeNB to delete the split bearer protocol entity;
  • the second establishing module in the primary serving base station is further configured to: receive the release source SeNB from the source SeNB and the target SeNB, and delete the message of the split bearer protocol entity, send an SeNB release confirmation message to the source SeNB, and send the SeNB release confirmation message to the target SeNB.
  • the SeNB modifies the acknowledgment message, and sends an RRC connection reconfiguration message to the UE, requesting the UE to delete the corresponding split bearer.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the target SeNB forwards the uplink radio link control RLC data protocol data unit PDU to the source SeNB, and the source SeNB offloads the downlink packet data convergence protocol PDCP data PDU to the target SeNB.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the source SeNB and the target SeNB are provided to provide the uplink data service and the downlink data service for the UE.
  • the user plane interface in the reconfiguration process, the target SeNB forwards the uplink RLC data PDU to the source SeNB, and the source SeNB offloads the downlink PDCP data PDU to the target SeNB.
  • the UE establishes a user plane interface for providing the uplink/downlink data service between the source SeNB and the target SeNB in the process of establishing the connection with the target SeNB, thereby solving the problem that the UE synchronizes with the target SeNB and establishes a connection.
  • the problem of data transmission with the network side at the micro base station or the low power node level cannot be avoided, thereby avoiding a sharp drop in user plane data throughput and ensuring the user experience of the UE in user plane reconfiguration.
  • the target SeNB does not need to re-transmit the downlink data that has been sent to the source SeNB before the reconfiguration occurs, and then sends the downlink data to the UE through the PDCP layer.
  • the downlink data that has been sent to the source SeNB does not need to be forwarded to the target SeNB through data pre-transmission. It also does not need to be repackaged by the PDCP layer of the target SeNB and then sent to the UE, thereby reducing the waste of repeated processing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例公开了一种双连接中实现重配置的方法、主服务基站及辅服务基站，在将UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB的过程中，建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口；在重配置过程中，目标SeNB将上行RLC数据PDU转发给源SeNB，源SeNB将下行PDCP数据PDU分流给目标SeNB并保持和UE的数据传输直到重配置成功。UE在建立和目标SeNB的连接的过程中，建立源SeNB与目标SeNB之间为UE提供上行/下行数据服务的用户面接口，从而解决了UE在和目标SeNB进行上下行同步并建立连接时，无法和网络侧在微基站或低功率节点层面有数据传输的问题，避免了避免用户面数据吞吐量的急剧下降，保证了UE在用户面重配置时的用户体验。

Description

双连接中实现重配置的方法、主服务基站及辅服务基站 技术领域
本发明实施例涉及移动通信技术，尤指一种双连接中实现重配置的方法、主服务基站及辅服务基站。
背景技术
图1为相关技术中双连接(DC，Dual connectivity)的网络架构示意图，如图1所示，对于每一个用户设备(UE，User equipment)来说，在控制面上，主服务基站(MeNB，Master eNB)如宏基站节点通过S1-MME连接到移动管理实体(MME，Mobility Management Entity)，MeNB和辅服务基站(SeNB，Secondary eNB)如微基站或低功率节点之间通过X2-C连接。在用户面上，对于主小区组承载(MCG bearer，Master cell group bearer),MeNB通过S1-U连接到服务网关(S-GW，Serving Gateway)，SeNB不参加到用户面的数据传输。对于分流承载(split bearer)，MeNB通过S1-U连接到S-GW，MeNB通过X2-U连接到SeNB。对于辅小区组承载(SCG bearer，Secondary cell group bearer)，SeNB通过S1-U连接到S-GW，MeNB不参加到用户面的数据传输。
图2为相关技术中长期演进(LTE，Long-term evolution)的用户面数据协议栈，如图2所示，从核心网经用户层面GPRS隧道协议(GTP-U，GPRS Tunnelling Protocol for the User Plane)收到的下行数据，经解包后通过分组数据汇聚协议(PDCP，Packet Data Convergence Protocol)子层、无线链路控制(RLC，Radio Link Control)协议子层、媒体接入控制(MAC，Medium Access Control)协议子层和物理层(PHY)处理后发送给UE；上行数据的发送与下行数据正好相反。第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)在讨论Release 12双连接时，提到过两种用户面的分流方式：一种是1A，即UE在MeNB和SeNB上的承载用户面直接连接在S-GW上，如图3所示；一种是3C，即MeNB做分流锚点， 数据在PDCP层与RLC层发生分流，分别发送给MeNB和SeNB进行传递，如图4所示。
双连接的目的，是UE的用户面承载在同一MeNB下的SeNB之间转移时，能够减少对核心网的信令冲击，同时保证UE的数据吞吐量和用户体验。然而，对于SCG bearer来说，由于重配置时PDCP层的重建，用户面仍然会出现较大的中断。即使考虑不需要PDCP层重建的split bearer，UE依旧执行的是先断后连的操作，即UE从源SeNB断开连接后，再建立和目标SeNB的连接。通常情况下，SeNB的角色由微基站或低功率节点承担，MeNB的角色由宏基站节点承担。由于微基站或低功率节点距离UE较近，覆盖范围较小，SeNB会承载比MeNB更多的用户面分流数据，因此，即使是UE短暂的和SeNB断开连接仍然会造成用户吞吐量的急剧下降。
发明内容
本发明实施例提供一种双连接中实现重配置的方法、主服务基站及辅服务基站，能够避免用户面数据吞吐量的急剧下降。
为了达到本发明目的，本发明实施例提供了一种双连接中实现重配置的方法，在将UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB的重配置过程中，包括：
建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口；
在重配置过程中，目标SeNB将上行无线链路控制RLC数据协议数据单元PDU转发给源SeNB，源SeNB将下行分组数据汇聚协议PDCP数据PDU分流给目标SeNB。
可选地，该方法还包括：所述源SeNB保持和所述UE的数据传输直到重配置成功。
可选地，所述建立用户面接口之前还包括：
所述MeNB指示所述目标SeNB为源SeNB上一个或多个将要转移到目标SeNB上的辅小区组承载SCG bearer建立对应的分流承载split bearer协议实体。
可选地，所述建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口包括：
所述MeNB将来自所述目标SeNB分配的传输层地址发送给源SeNB，以使在所述源SeNB和所述目标SeNB之间建立为UE提供下行数据分流服务的用户面接口；
所述MeNB接收来自所述源SeNB的分配的传输层地址后发送给目标SeNB，以使在所述源SeNB和所述目标SeNB之间建立为UE提供上行数据分流服务的用户面接口。
可选地，所述MeNB指示目标SeNB为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer建立对应的split bearer协议实体包括：
所述MeNB向所述目标SeNB发送接纳请求消息，在接纳请求消息中携带有split bearer配置信息或建立split bearer的指示信息；
其中，split bearer配置信息或建立split bearer的指示信息用于为所述源SeNB上一个或多个将要转移到所述目标SeNB上的SCG bearer在所述目标SeNB上建立对应的所述split bearer协议实体。
可选地，所述MeNB将来自目标SeNB分配的传输层地址发送给源SeNB，以使在源SeNB和目标SeNB之间建立为UE提供下行数据分流服务的用户面接口包括：
所述目标SeNB完成对UE的资源配置后，向所述MeNB回复接纳确认消息，在接纳确认消息中携带有为接收所述建立的split bearer的下行PDCP数据PDU而分配的传输层地址；
所述MeNB收到接纳确认消息后，向所述源SeNB发送修改请求消息，在修改请求消息中携带有所述目标SeNB分配的传输层地址，其目的是建立所述源SeNB和所述目标SeNB之间为UE提供下行数据分流服务的用 户面接口。
可选地，所述MeNB接收来自源SeNB的分配的传输层地址后发送给目标SeNB，以使在源SeNB和目标SeNB之间建立为UE提供上行数据分流服务的用户面接口包括：
所述源SeNB向所述MeNB发送修改请求确认消息，在修改请求确认消息中携带有为接收所述建立的split bearer的上行RLC数据PDU而分配的传输层地址；
所述MeNB在收到所述源SeNB的修改请求确认消息后，向所述目标SeNB发送X2通知消息，在X2通知消息中携带有所述源SeNB分配的传输层地址，其目的是建立所述源SeNB和所述目标SeNB之间为UE提供上行数据分流服务的用户面接口。
可选地，该方法还包括：
所述MeNB在收到所述源SeNB的修改请求确认消息后，根据接收到的接纳确认消息中所携带的信息组成面向UE的无线资源控制RRC信令并发送给UE；UE在收到来自所述MeNB的指示将第一个或多个SCGbearer从所述源SeNB转移到所述目标SeNB的RRC信令后，按照获得的RRC信令中携带的信息，与所述目标SeNB进行同步、向所述目标SeNB发起随机接入，按照新的配置建立SCG bearer，并建立对应的split bearer协议实体。
可选地，所述目标SeNB将上行RLC数据PDU转发给源SeNB包括：通过为接收所述建立的split bearer的上行RLC数据PDU而分配的传输层地址，将上行RLC数据PDU转发给所述源SeNB；
所述源SeNB将下行PDCP数据PDU分流给目标SeNB包括：通过为接收所述建立的split bearer的下行PDCP PDU而分配的传输层地址，将部分或全部下行PDCP数据PDU分流给所述目标SeNB进行传输。
可选地，对于所述建立的split bearer，
在下行链路上，数据在所述源SeNB的PDCP层和RLC层之间分流， 分别发送给所述源SeNB和所述目标SeNB进行传递，所述目标SeNB上仅建立PDCP层之下的协议实体；所述UE从空口收到两路下行数据后，在PDCP层进行合并；
在上行链路上，数据在所述UE的RLC层和MAC之间分流，分别通过空口发送给所述源SeNB和所述目标SeNB，所述目标SeNB上仅建立RLC层之下的协议实体；所述目标SeNB收到上行数据后，发送给所述源SeNB，在所述源SeNB的RLC层进行合并。
可选地，所述建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口之后，该方法还包括：
在UE接入所述目标SeNB并完成配置更新后，如果所述目标SeNB已经通过X2-U从所述源SeNB收到分流的下行PDCP数据PDU，所述目标SeNB开始将下行PDCP数据PDU通过split bearer的下层协议实体处理后发送给UE。
可选地，所述建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口之后，该方法还包括：
UE接入所述目标SeNB并完成配置更新后，通过和所述目标SeNB对应的split bearer和/或SCG bearer协议实体，向所述目标SeNB发送上行数据包。
可选地，当所述源SeNB收到来自S-GW的结束标识时，该方法还包括：
在所述源SeNB为所有下行数据包分配PDCP子层的SN号后，向所述目标SeNB发送SN状态传输消息，所述目标SeNB根据SN状态传输消息，开始为从S-GW收到下行数据包分配PDCP子层的SN号；在所述源SeNB完成所有下行数据的发送和/或转发后，向所述MeNB请求进行所述源SeNB释放；相应地，
所述目标SeNB成功发送所有的下行转发数据，或者已经从SCG bearer协议实体收到来自UE的上行数据包且已经完成所有转发上行数据 包的排序，向所述MeNB请求删除所述split bearer协议实体；
所述MeNB收到来自所述源SeNB和所述目标SeNB的释放所述源SeNB及删除所述split bearer协议实体的消息后，所述MeNB向源SeNB发送SeNB释放确认消息，所述MeNB向所述目标SeNB发送SeNB修改确认消息，所述MeNB向UE发送RRC连接重配置消息要求UE删除对应split bearer。
本发明实施例还提供了一种主服务基站，包括第一处理单元，设置为建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口。
可选地，所述第一处理单元包括第一建立模块，第二建立模块；其中，
第一建立模块，设置为将来自所述目标SeNB分配的传输层地址发送给源SeNB，以使在所述源SeNB和所述目标SeNB之间建立为UE提供下行数据分流服务的用户面接口；
第二建立模块，设置为接收来自所述源SeNB的分配的传输层地址后发送给所述目标SeNB，并以使在所述源SeNB和所述目标SeNB之间建立为UE提供上行数据分流服务的用户面接口；组成面向UE的RRC信令并发送给UE。
可选地，所述第一建立模块还设置为：指示所述目标SeNB为所述源SeNB上一个或多个将要转移到所述目标SeNB上的SCG bearer建立对应的split bearer协议实体。
可选地，所述第一建立模块具体设置为：
向所述目标SeNB发送携带有split bearer配置信息或建立split bearer的指示信息的接纳请求消息；其中，split bearer配置信息或建立split bearer的指示信息用于为所述源SeNB上一个或多个将要转移到所述目标SeNB上的SCG bearer在所述目标SeNB上建立对应的split bearer协议实体；
接收来自所述目标SeNB的携带有为接收建立的split bearer的下行PDCP数据PDU而分配的传输层地址的接纳确认消息，向所述源SeNB发 送携带有所述目标SeNB分配的传输层地址的修改请求消息。
可选地，所述第二建立模块具体设置为：
接收来自所述源SeNB的携带有为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的修改请求确认消息；向所述目标SeNB发送携带有所述源SeNB分配的为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的X2通知消息；根据接收到的接纳确认消息中所携带的信息组成面向UE的RRC信令并发送给UE。
可选地，所述第二建立模块还设置为：
收到来自所述源SeNB和所述目标SeNB的释放所述源SeNB及删除所述split bearer协议实体的消息，向所述源SeNB发送SeNB释放确认消息，向所述目标SeNB发送SeNB修改确认消息，向所述UE发送RRC连接重配置消息要求UE删除对应split bearer。
本发明又提供了一种辅服务基站，包括：第二处理单元，和/或第三处理单元；其中，
第二处理单元，设置为按照来自MeNB的指示，为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer建立对应的split bearer协议实体；为接收建立的split bearer的下行PDCP数据PDU而分配传输层地址；接收来自MeNB的源SeNB分配的传输层地址，在源SeNB和目标SeNB之间建立为UE提供上行数据分流服务的用户面接口；
第三处理单元，用为接收建立的split bearer的上行RLC数据PDU而分配传输层地址；接收来自MeNB的目标SeNB的分配的传输层地址；在源SeNB和目标SeNB之间建立为UE提供下行数据分流服务的用户面接口。
可选地，所述第二处理单元具体设置为：
接收到来自所述MeNB的携带有split bearer配置信息或建立split bearer的指示信息的接纳请求消息，为所述源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer在所述目标SeNB上建立对应的split  bearer协议实体；
向所述MeNB发送携带有为接收建立的split bearer的下行PDCP数据PDU而分配的传输层地址的接纳确认消息；
接收来自所述MeNB的携带有所述源SeNB分配的为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的修改请求确认消息；建立所述源SeNB和所述目标SeNB之间为UE提供上行数据分流服务的用户面接口；
在重配置过程中，将上行RLC数据PDU转发给所述源SeNB。
可选地，所述第三处理单元具体设置为：
接收来自所述MeNB的携带有所述目标SeNB分配的传输层地址的修改请求消息；建立所述源SeNB和所述目标SeNB之间为UE提供下行数据分流服务的用户面接口；
向所述MeNB发送携带有为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的修改请求确认消息；
在重配置过程中，将下行PDCP数据PDU分流给所述目标SeNB。
可选地，所述第三处理单元还设置为：保持和所述UE的数据传输直到重配置成功。
可选地，所述第三处理单元还设置为：收到来自S-GW的结束标识时为所有下行数据包分配PDCP子层的SN号后，向所述目标SeNB发送SN状态传输消息，完成所有下行数据的发送和/或转发后，向所述MeNB请求进行所述源SeNB释放；相应地，
所述第二处理单元还设置为：根据SN状态传输消息，开始为从S-GW收到下行数据包分配PDCP子层的SN号；在已经成功发送所有的下行转发数据，或者，已经从SCG bearer协议实体收到来自UE的上行数据包且已经完成所有转发上行数据包的排序，向所述MeNB请求删除所述split bearer协议实体。
在本发明实施例中，还提供了一种计算机存储介质，该计算机存储介质可以存储有执行指令，该执行指令用于执行上述实施例中的双连接中实现重配置的方法。
与相关技术相比，本申请技术方案包括：在将UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB的重配置过程中，建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口；在重配置过程中，目标SeNB将上行RLC数据PDU转发给源SeNB，源SeNB将下行PDCP数据PDU分流给目标SeNB。UE在建立和目标SeNB的连接的过程中，建立源SeNB与目标SeNB之间为UE提供上行/下行数据服务的用户面接口，从而解决了UE在和目标SeNB进行上下行同步并建立连接时，无法和网络侧在微基站或低功率节点层面有数据传输的问题，避免了避免用户面数据吞吐量的急剧下降，保证了UE在用户面重配置时的用户体验。
同时，目标SeNB不需要对发生重配置前已经发送给源SeNB的下行数据重新通过PDCP层打包后发给UE，也就是说，已经发送给源SeNB的下行数据不需要通过数据前传转发给目标SeNB，也不需要由目标SeNB的PDCP层重新打包后发送给UE，从而减少了重复处理的浪费。
本发明的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本发明而了解。本发明的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为相关技术中DC的网络架构示意图；
图2为相关技术中LTE的用户面数据协议栈；
图3为相关技术中双连接用户面1A的示意图；
图4为相关技术中双连接用户面3C的示意图；
图5为本发明双连接中实现重配置的方法的流程图；
图6为本发明双连接中实现重配置的实施例的流程示意图；
图7为本发明用户面协议实体及下行数据传输的第一实施例的示意图；
图8为本发明用户面协议实体及下行数据传输的第二实施例的示意图；
图9为本发明用户面协议实体及上行数据传输的第三实施例的示意图；
图10为本发明用户面协议实体及上行数据传输的第四实施例的示意图
图11为本发明主服务基站的组成结构示意图；
图12为本发明辅服务基站的组成结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚明白，下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在双连接的1A架构的相关技术中，将UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB，虽然MeNB执行的是先添加目标SeNB，再删除源SeNB的流程，但实际UE需要先从源SeNB断开连接，再建立和目标SeNB的连接，因此，同样会存在由于UE短暂的和SeNB断开连接而造成的用户吞吐量的急剧下降的问题。
而本发明实施例提供的技术方案中，UE在建立和目标SeNB的连接的过程中，建立源SeNB与目标SeNB之间为UE提供上行/下行数据服务的用户面接口，从而解决了UE在和目标SeNB进行上下行同步并建立连接时，无法和网络侧在微基站或低功率节点层面有数据传输的问题，避免了用户面数据吞吐量的急剧下降，保证了UE在用户面重配置时的用户体 验。
同时，目标SeNB不需要对发生重配置前已经发送给源SeNB的下行数据重新通过PDCP层打包后发给UE，也就是说，已经发送给源SeNB的下行数据不需要通过数据前传转发给目标SeNB，也不需要由目标SeNB的PDCP层重新打包后发送给UE，从而减少了重复处理的浪费。
图5为本发明双连接中实现重配置的方法的流程图，在将UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB的重配置过程中，如图5所示，包括：
步骤500：建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口。
本步骤之前还包括：MeNB指示目标SeNB为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer建立对应的split bearer协议实体。具体包括：MeNB向目标SeNB发送接纳请求消息，在接纳请求消息中除了参考相关协议中X2-AP消息(SeNB addition request)而携带密钥信息、UE安全能力信息、SCG bearer配置信息等外，还至少携带有split bearer配置信息或建立split bearer的指示信息。其中，split bearer配置信息或建立split bearer的指示信息用于为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer在目标SeNB上建立对应的split bearer协议实体。
本步骤的实现包括：MeNB将来自目标SeNB分配的传输层地址如GPRS隧道协议(GTP，GPRS Tunnelling Protocol)隧道端点标识符(TEID，Tunnel Endpoint Identity)等发送给源SeNB，以使在源SeNB和目标SeNB之间建立为UE提供下行数据分流服务的用户面接口。具体包括：
目标SeNB根据接收到的信息判断是否有足够的资源以允许UE的接入。如果允许接入，则目标SeNB完成对UE的资源配置后，向MeNB回复接纳确认消息，在接纳确认消息中除参考相关协议中X2-AP消息(SeNB addition request acknowledge)而携带目标SeNB同意接纳的SCG bearer配置信息外，还至少携带有为接收建立的split bearer的下行PDCP数据协议 数据单元(PDU，Protocol Data Unit)而分配的传输层地址如GTP TEID；
MeNB收到接纳确认消息后，向源SeNB发送修改请求消息。在修改请求消息中携带有目标SeNB分配的传输层地址如GTP TEID，其目的是建立源SeNB和目标SeNB之间为UE提供下行数据分流服务的用户面接口。源SeNB上的承载类型由SCG bearer变更为split bearer。
MeNB接收来自源SeNB的分配的传输层地址如GTP TEID后发送给目标SeNB，以使在源SeNB和目标SeNB之间建立为UE提供上行数据分流服务的用户面接口。具体包括：
源SeNB向MeNB发送修改请求确认消息。在修改请求确认消息中携带有为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址如GTP TEID；
MeNB在收到源SeNB的修改请求确认消息后，向目标SeNB发送X2通知消息。在X2通知消息中携带有源SeNB分配的传输层地址如GTPTEID，其目的是建立源SeNB和目标SeNB之间为UE提供上行数据分流服务的用户面接口。
同时，本步骤还包括：MeNB在收到源SeNB的修改请求确认消息后，根据接收到的接纳确认消息中所携带的信息组成面向UE的无线资源控制(RRC，Radio Resource Control)信令并发送给UE。UE在收到来自MeNB的指示将第一个或多个SCG bearer从源SeNB转移到目标SeNB的RRC信令后，按照RRC信令中携带的信息，与目标SeNB进行同步、向目标SeNB发起随机接入，按照新的配置建立SCG bearer，并建立对应的split bearer协议实体。
步骤501：在重配置过程中，目标SeNB将上行RLC数据PDU转发给源SeNB，源SeNB将下行PDCP数据PDU分流给目标SeNB并保持和UE的数据传输直到重配置成功。
源SeNB可以通过为接收建立的split bearer的下行PDCP PDU而分配的传输层地址如GTP TEID，将部分或全部下行PDCP数据PDU分流给目 标SeNB进行传输；
目标SeNB可以通过为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址如GTP TEID，将上行RLC数据PDU转发给源SeNB。
需要说明的是，上行RLC数据PDU对应的RLC控制PDU可以由源SeNB直接反馈；也可以由源SeNB通知目标SeNB，再由目标SeNB反馈。
对于split bearer，具体地，
在下行链路上，数据在源SeNB的PDCP层和RLC层之间分流，分别发送给源SeNB和目标SeNB进行传递，目标SeNB上仅建立PDCP层之下的协议实体；UE从空口收到两路下行数据后，在PDCP层进行合并；
在上行链路上，数据在UE的RLC层和MAC之间分流，分别通过空口发送给源SeNB和目标SeNB，目标SeNB上仅建立RLC层之下的协议实体；目标SeNB收到上行数据后，发送给源SeNB，在源SeNB的RLC层进行合并。
其中，源SeNB是将部分下行PDCP数据PDU分流给目标SeNB进行传输，还是将全部下行PDCP数据PDU分流给目标SeNB进行传输可以考虑：
当源SeNB信号质量还比较好，源SeNB可以只将一部分下行PDCP数据PDU分流给目标SeNB，并保持和UE的数据传输；当源SeNB信号质量已经很差，源SeNB可以将大部分甚至全部下行PDCP数据PDCU分流给目标SeNB，但是，此时由于UE还没有接入目标SeNB，UE的数据传输吞吐量将会稍有下降。从这里可见，本发明方法根据源SeNB的信号质量选择断开或者保持和源SeNB的数据传输，这样，在源SeNB信号质量还比较好的情况下，让UE保持了和源SeNB的信号传输。
本发明方法的步骤500之后，还包括：
一方面，在UE接入目标SeNB并完成配置更新后，如果目标SeNB已经通过X2-U从源SeNB收到分流的下行PDCP数据PDU，目标SeNB 开始将下行PDCP数据PDU通过split bearer的下层协议实体处理后，发送给UE。
另一方面，UE接入目标SeNB并完成配置更新后，可以开始通过和目标SeNB对应的split bearer和/或SCG bearer协议实体，向目标SeNB发送上行数据包。
当MeNB收到来自UE的RRC连接重配置完成消息后，该方法还包括：MeNB向核心网发起路径转换程序，请求全部或部分下行数据承载的下行隧道端点的变更。
当源SeNB收到来自S-GW的结束标识时，
在源SeNB为所有下行数据包分配PDCP子层的SN号后，向目标SeNB发送SN状态传输消息，目标SeNB根据SN状态传输消息，可以开始为从S-GW收到下行数据包分配PDCP子层的SN号；
在源SeNB完成所有下行数据的发送和/或转发后，向MeNB请求进行源SeNB释放。
而目标SeNB也会向MeNB请求删除split bearer协议实体。在请求MeNB删除split bearer协议实体之前，目标SeNB已经成功发送所有的下行转发数据，或者，在请求MeNB删除split bearer协议实体之前，目标SeNB已经从SCG bearer协议实体收到来自UE的上行数据包，且已经完成所有转发上行数据包的排序。
在MeNB收到来自源SeNB和目标SeNB的释放源SeNB及删除split bearer协议实体的消息后，MeNB向源SeNB发送SeNB释放确认消息(SeNB release confirm)，向目标SeNB发送SeNB修改确认消息(SeNB modification confirm)，向UE发送RRC连接重配置消息要求UE删除对应split bearer。
图6为本发明双连接中实现重配置的实施例的流程示意图，如图6所示，本实施例描述的是本发明中MeNB收到UE测量报告后，对UE的用户面承载进行转移的流程。在转移执行阶段，MeNB除了请求目标SeNB 为UE在源SeNB上的SCG bearer执行接纳判决外，还需要目标SeNB为允许接纳的SCG bearer建立对应的split bearer协议实体。具体包括以下步骤：
步骤601：MeNB根据UE的测量上报(或其他无线资源管理功能得出的结果，如负荷过重)做出需要用户面重配置的决定，假设决定是将该UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB让该UE继续从辅服务基站获得通信服务。
步骤602：MeNB向目标SeNB发送接纳请求消息。
其中，接纳请求消息除参考相关协议X2-AP消息(SeNB addition request)而携带密钥信息、UE安全能力信息、SCG bearer配置信息等外，还至少携带有split bearer配置信息或建立split bearer的指示信息。其中，split bearer配置信息或建立split bearer的指示信息用于为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer在目标SeNB上建立对应的split bearer协议实体。
对于split bearer，
在下行链路上，数据在源SeNB的PDCP层和RLC层之间分流，分别发送给源SeNB和目标SeNB进行传递，目标SeNB上仅建立PDCP层之下的协议实体。UE从空口收到两路下行数据后，在PDCP层进行合并‘
在上行链路上，数据在UE的RLC层和MAC之间分流，分别通过空口发送给源SeNB和目标SeNB，目标SeNB上仅建立RLC层之下的协议实体。目标SeNB收到上行数据后，发送给源SeNB，在源SeNB的RLC层进行合并。
步骤603：目标SeNB接收到接纳请求消息后，结合自身的资源状况判断是否可接纳UE接入。本步骤的具体实现是本领域技术人员熟知的，并不用于限定本发明的保护范围，这里不再赘述。
步骤604：如果目标SeNB判断可以接纳UE的接入，则向MeNB回 复接纳确认消息，在接纳确认消息中除参考相关协议X2-AP消息(SeNB addition request acknowledge)而携带目标SeNB同意接纳的SCG bearer列表外，还至少携带有为接收split bearer的下行PDCP数据PDU而分配的传输层地址如GTP TEID。
步骤605：MeNB收到接纳确认消息后，向源SeNB发送修改请求消息。其中，修改请求消息通知源SeNB从目标SeNB通过接纳确认消息收到的GTP TEID，其目的是建立源SeNB和目标SeNB之间为UE提供下行数据分流服务的用户面接口。这样，源SeNB可以通过所述GTP TEID将部分或全部下行PDCP数据PDU，通过X2-U分流给目标SeNB进行传输。源SeNB上的承载类型由SCG bearer变更为split bearer。
步骤606：源SeNB向MeNB发送修改请求确认消息，通知MeNB配置修改成功。其中，修改请求确认消息中还携带有为接收所述split bearer的上行RLC数据PDU而分配的GTP TEID。
本步骤中，在源SeNB向MeNB发送修改请求确认消息的同时或之后，源SeNB开始通过目标SeNB提供的GTP TEID将部分或全部下行PDCP数据PDU分流给目标SeNB。
其中，如果源SeNB信号质量还比较好，源SeNB可以只将一部分下行PDCP数据PDU分流给目标SeNB，并保持和UE的数据传输。如果源SeNB信号质量已经很差，源SeNB可以将大部分甚至全部下行PDCP数据PDCU分流给目标SeNB，但是这种情况下，由于UE还没有接入目标SeNB，UE的数据传输吞吐量将会稍有下降。
本步骤中，在源SeNB向MeNB发送修改请求确认消息的同时或之后，源SeNB开始将还没有完成排序的上行数据包发送给目标SeNB。同时，源SeNB的PDCP层的排序功能停止工作；源SeNB将后续收到的所有上行PDCP数据PDU解密后，发送目标SeNB，由目标SeNB的PDCP层完成排序。
步骤607：MeNB在收到源SeNB的修改请求确认消息后，向目标SeNB 发送X2通知消息。其中，X2通知消息用于通知目标SeNB从源SeNB通过修改请求确认消息收到的GTP TEID，其目的是建立源SeNB和目标SeNB之间为UE提供上行数据分流服务的用户面接口。这样，目标SeNB可以通过该GTP TEID将目标SeNB从UE收到的上行RLC数据PDU，转发给源SeNB。
步骤608：MeNB在收到源SeNB的修改请求确认消息后，根据接收到的接纳确认消息中所携带的信息组成面向UE的无线资源控制(RRC，Radio Resource Control)信令并发送给UE。
步骤609：UE在收到来自MeNB的指示将第一个或多个SCG bearer从源SeNB转移到目标SeNB的RRC信令后，判断是否能按照RRC信令中的要求执行RRC连接重配置请求。如果能，UE向MeNB发送RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，指示UE已启用新的无线资源配置。
步骤610：UE按照信令中携带的信息，与目标SeNB进行同步、向目标SeNB发起随机接入，按照新的配置建立SCG bearer，并建立对应的split bearer协议实体。
UE接入目标SeNB并完成配置更新后，如果此时目标SeNB已经通过X2-U从源SeNB收到分流的下行PDCP数据PDU，目标SeNB开始将下行PDCP数据PDU通过split bearer的下层协议实体处理后发送给UE；
UE接入目标SeNB并完成配置更新后，可以开始通过和目标SeNB对应的split bearer或SCG bearer协议实体，向目标SeNB发送上行数据包。
步骤611：MeNB收到UE的RRC连接重配置完成消息后，向核心网发起路径转换程序，请求全部或部分下行数据承载的下行隧道端点的变更。
步骤612：源SeNB收到来自S-GW的结束标识，并为所有下行数据包分配PDCP子层的SN号后，向目标SeNB发送SN状态传输消息，目标SeNB根据SN状态传输消息，可以开始为从S-GW收到下行数据包分配PDCP子层的SN号。
步骤613：源SeNB收到来自S-GW的结束标识，并完成所有下行数据的发送和/或转发后，请求MeNB进行源SeNB释放。
步骤614：目标SeNB请求MeNB删除split bearer协议实体。
在请求MeNB删除split bearer协议实体之前，目标SeNB已经成功发送所有的下行转发数据。以及，
在请求MeNB删除split bearer协议实体之前，目标SeNB已经从SCG bearer协议实体收到来自UE的上行数据包，且已经完成所有转发上行数据包的排序。
步骤615：在MeNB收到上述步骤613和步骤614中的消息后，MeNB向源SeNB发送SeNB释放确认(SeNB release confirm)消息；向目标SeNB发送SeNB修改确认(SeNB modification confirm)消息；向UE发送RRC连接重配置消息要求UE删除对应split bearer。
图7为本发明用户面协议实体及下行数据传输的第一实施例的示意图，第一实施例描述的是路径转换完成后源SeNB、目标SeNB和UE上的用户平面协议实体及一种下行数据传输示意图。如图7所示，假设源SeNB已经传输了SN号为1到5的PDCP数据PDU，重配置发生时，UE只收到了SN号为1，2和4的PDCP数据PDU并向源SeNB做了确认。对于SN号为3和5的PDCP数据PDU，UE只收到了部分RLC数据PDU。此时，如果源SeNB信号质量已经不足以支持继续向UE发送数据，源SeNB会将SN号为3和5的PDCP数据PDU转发给目标SeNB，由目标SeNB的split bearer协议实体处理并发送。所有在收到结束标识之前从S-GW收到的还没有开始发送的下行数据，如SN号为6到9的PDCP数据SDU，都经由PDCP层处理后，转发给目标SeNB，由目标SeNB的split bearer协议实体处理并发送。
对于下行数据，UE与源SeNB对应的PDCP实体完成所有向上层递交数据的工作后，与目标SeNB对应的PDCP实体才开始向上层递交数据，避免上层收到乱序的数据包。
图8为本发明用户面协议实体及下行数据传输的第二实施例的示意图，第二实施例描述的是路径转换完成后源SeNB、目标SeNB和UE上的用户平面协议实体及一种下行数据传输示意图。如图8所示，假设源SeNB已经传输了SN号为1到5的PDCP数据PDU，重配置发生时，UE只收到了SN号为1，2和4的PDCP数据PDU并向源SeNB做了确认。对于SN号为3和5的PDCP数据PDU，UE只收到了部分RLC数据PDU。此时，至少在一段时间内，源SeNB还可以继续保持和UE之间的数据传输，源SeNB至少会继续发送SN号为3和5的PDCP数据PDU对应的还没有收到UE确认回复的RLC数据PDU或RLC数据PDU分段。所有在收到结束标识之前从S-GW收到的还没有开始发送的下行数据，如SN号为6到9的PDCP数据SDU，都经由PDCP层处理后，分流给源SeNB或目标SeNB发送。如图7所示，源SeNB在收到结束标识前，还会收到SN号为6、7、8、9的PDCP数据SDU，经由PDCP层处理后，源SeNB将SN号为8、9的PDCP数据PDU分流给目标SeNB发送，而将SN号为6、7的PDCP数据PDU留在源SeNB发送，保证了UE在向目标SeNB进行同步和接入时，UE和源SeNB之间依旧保持一定的数据传输。
对于下行数据，UE与源SeNB对应的PDCP实体完成所有向上层递交数据的工作后，与目标SeNB对应的PDCP实体才开始向上层递交数据，避免上层收到乱序的数据包。
图9为本发明用户面协议实体及上行数据传输的第三实施例的示意图，第三实施例描述的是路径转换完成后，源SeNB、目标SeNB和UE上的用户平面协议实体及上行数据传输示意图。如图9所示，假设UE已经传输了SN号为1到5的PDCP数据PDU，重配置发生时，源SeNB只收到了SN号为1,2和4的PDCP数据PDU并向UE做了确认。对于SN号为3和5的PDCP数据PDU，源SeNB只收到了部分RLC数据PDU。
此时，如果源SeNB和UE之间的信号质量已经不能支持UE向源SeNB发送数据，对于SN号为3和5的PDCP数据PDU，UE会将没有发送或没有发送成功的RLC数据PDU或RLC数据PDU分段，通过split  bearer协议实体发送给目标SeNB。目标SeNB收到所述RLC数据PDU或RLC数据PDU分段后，将所述RLC数据PDU或RLC数据PDU分段转发给源SeNB，由源SeNB组合成SN号为3和5的PDCP数据PDU。后续上行数据包，如SN号为6及以后的数据包，UE使用和目标SeNB对应的SCG bearer协议实体处理后发送给目标SeNB。
对于上行数据，目标SeNB在源SeNB向S-GW递交数据完成以后，才开始向S-GW递交数据，避免上层收到乱序的数据包。
图10为本发明用户面协议实体及上行数据传输的第四实施例的示意图，第四实施例描述的是路径转换完成后，源SeNB、目标SeNB和UE上的用户平面协议实体及上行数据传输示意图。如图10所示，假设UE已经传输了SN号为1到5的PDCP数据PDU，重配置发生时，源SeNB只收到了SN号为1,2和4的PDCP数据PDU并向UE做了确认。对于SN号为3和5的PDCP数据PDU，源SeNB只收到了部分RLC数据PDU。
此时，如果源SeNB和UE之间的信号质量还足够好，至少，对于SN号为3和5的PDCP数据PDU，UE会将没有发送或没有发送成功的RLC数据PDU或RLC数据PDU分段，通过split bearer协议实体发送给源SeNB，并和已经收到RLC数据PDU或RLC数据PDU分段组合成SN号为3和5的PDCP数据PDU。后续上行数据包，如SN号为6及以后的数据包，UE可以使用和目标SeNB对应的SCG bearer协议实体处理后发送给目标SeNB。
对于上行数据，目标SeNB在源SeNB向S-GW递交数据完成以后，才开始向S-GW递交数据，避免上层收到乱序的数据包。
图11为本发明主服务基站的组成结构示意图，如图11所示，至少包括第一处理单元，设置为建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口。其中，
第一处理单元包括：第一建立模块，第二建立模块；其中，
第一建立模块，设置为将来自目标SeNB分配的传输层地址发送给源 SeNB，以使在源SeNB和目标SeNB之间建立为UE提供下行数据分流服务的用户面接口；
第二建立模块，设置为接收来自源SeNB的分配的传输层地址后发送给目标SeNB，并以使在源SeNB和目标SeNB之间建立为UE提供上行数据分流服务的用户面接口；组成面向UE的RRC信令并发送给UE。
其中，第一建立模块还设置为：指示目标SeNB为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer建立对应的split bearer协议实体。
其中，
第一建立模块具体设置为：向目标SeNB发送携带有split bearer配置信息或建立split bearer的指示信息的接纳请求消息。其中，split bearer配置信息或建立split bearer的指示信息用于为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer在目标SeNB上建立对应的split bearer协议实体；
接收来自目标SeNB的携带有为接收建立的split bearer的下行PDCP数据PDU而分配的传输层地址的接纳确认消息，向源SeNB发送携带有目标SeNB分配的传输层地址的修改请求消息。
第二建立模块具体设置为：接收来自源SeNB的携带有为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的修改请求确认消息；向目标SeNB发送携带有源SeNB分配的为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的X2通知消息；根据接收到的接纳确认消息中所携带的信息组成面向UE的RRC信令并发送给UE。
进一步地，
第二建立模块还设置为：当收到来自UE的RRC连接重配置完成消息，向核心网发起路径转换程序，请求全部或部分下行数据承载的下行隧道端点的变更。
图12为本发明辅服务基站的组成结构示意图，如图12所示，至少包 括：第二处理单元，和/或第三处理单元；其中，
第二处理单元，设置为按照来自MeNB的指示，为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer建立对应的split bearer协议实体；为接收建立的split bearer的下行PDCP数据PDU而分配传输层地址；接收来自MeNB的源SeNB分配的传输层地址，在源SeNB和目标SeNB之间建立为UE提供上行数据分流服务的用户面接口。具体用于：
接收到来自MeNB的携带有split bearer配置信息或建立split bearer的指示信息的接纳请求消息，为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer在目标SeNB上建立对应的split bearer协议实体；
向MeNB发送携带有为接收建立的split bearer的下行PDCP数据PDU而分配的传输层地址的接纳确认消息；
接收来自MeNB的携带有源SeNB分配的为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址修改请求确认消息；建立源SeNB和目标SeNB之间为UE提供上行数据分流服务的用户面接口；
在重配置过程中，将上行RLC数据PDU转发给源SeNB。
第三处理单元，用为接收建立的split bearer的上行RLC数据PDU而分配传输层地址；接收来自MeNB的目标SeNB的分配的传输层地址；在源SeNB和目标SeNB之间建立为UE提供下行数据分流服务的用户面接口。具体用于：
接收来自MeNB的携带有目标SeNB分配的传输层地址的修改请求消息；建立源SeNB和目标SeNB之间为UE提供下行数据分流服务的用户面接口；
向MeNB发送携带有为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的修改请求确认消息；
在重配置过程中，将下行PDCP数据PDU分流给目标SeNB。
第三处理单元还设置为：保持和UE的数据传输直到重配置成功。
进一步地，
第三处理单元还设置为：收到来自S-GW的结束标识时为所有下行数据包分配PDCP子层的SN号后，向目标SeNB发送SN状态传输消息，完成所有下行数据的发送和/或转发后，向MeNB请求进行源SeNB释放；相应地，
第二处理单元还设置为：根据SN状态传输消息，开始为从S-GW收到下行数据包分配PDCP子层的SN号；在已经成功发送所有的下行转发数据，或者，已经从SCG bearer协议实体收到来自UE的上行数据包，且已经完成所有转发上行数据包的排序，向MeNB请求删除split bearer协议实体；
此时，主服务基站中的第二建立模块还设置为：收到来自源SeNB和目标SeNB的释放源SeNB及删除split bearer协议实体的消息，向源SeNB发送SeNB释放确认消息，向目标SeNB发送SeNB修改确认消息，向UE发送RRC连接重配置消息要求UE删除对应split bearer。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，在将UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB的重配置过程中，建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口；
S2，在重配置过程中，目标SeNB将上行无线链路控制RLC数据协议数据单元PDU转发给源SeNB，源SeNB将下行分组数据汇聚协议PDCP数据PDU分流给目标SeNB。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的较佳实例而已，并非用于限定本发明的保护范围。凡在本发明的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
在本发明实施例中，在将UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB的重配置过程中，建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口；在重配置过程中，目标SeNB将上行RLC数据PDU转发给源SeNB，源SeNB将下行PDCP数据PDU分流给目标SeNB。UE在建立和目标SeNB的连接的过程中，建立源SeNB与目标SeNB之间为UE提供上行/下行数据服务的用户面接口，从而解决了UE在和目标SeNB进行上下行同步并建立连接时，无法和网络侧在微基站或低功率节点层面有数据传输的问题，避免了避免用户面数据吞吐量的急剧下降，保证了UE在用户面重配置时的用户体验。同时，目标SeNB不需要对发生重配置前已经发送给源SeNB的下行数据重新通过PDCP层打包后发给UE，也就是说，已经发送给源SeNB的下行数据不需要通过数据前传转发给目标SeNB，也不需要由目标SeNB的PDCP层重新打包后发送给UE，从而减少了重复处理的浪费。

Claims (24)

  1. 一种双连接中实现重配置的方法，在将UE的用户面承载从源SeNB转移到同一MeNB下的目标SeNB的重配置过程中，包括：
    建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口；
    在重配置过程中，目标SeNB将上行无线链路控制RLC数据协议数据单元PDU转发给源SeNB，源SeNB将下行分组数据汇聚协议PDCP数据PDU分流给目标SeNB。
  2. 根据权利要求1所述的方法，其中，该方法还包括：所述源SeNB保持和所述UE的数据传输直到重配置成功。
  3. 根据权利要求1所述的方法，其中，所述建立用户面接口之前还包括：
    所述MeNB指示所述目标SeNB为源SeNB上一个或多个将要转移到目标SeNB上的辅小区组承载SCG bearer建立对应的分流承载split bearer协议实体。
  4. 根据权利要求3所述的方法，其中，所述建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口包括：
    所述MeNB将来自所述目标SeNB分配的传输层地址发送给源SeNB，以使在所述源SeNB和所述目标SeNB之间建立为UE提供下行数据分流服务的用户面接口；
    所述MeNB接收来自所述源SeNB的分配的传输层地址后发送给目标SeNB，以使在所述源SeNB和所述目标SeNB之间建立为UE提供上行数据分流服务的用户面接口。
  5. 根据权利要求3所述的方法，其中，所述MeNB指示目标SeNB为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer建立对应的split bearer协议实体包括：
    所述MeNB向所述目标SeNB发送接纳请求消息，在接纳请求消息中携带有split bearer配置信息或建立split bearer的指示信息；
    其中，split bearer配置信息或建立split bearer的指示信息用于为所述源SeNB上一个或多个将要转移到所述目标SeNB上的SCG bearer在所述目标SeNB上建立对应的所述split bearer协议实体。
  6. 根据权利要求4所述的方法，其中，所述MeNB将来自目标SeNB分配的传输层地址发送给源SeNB，以使在源SeNB和目标SeNB之间建立为UE提供下行数据分流服务的用户面接口包括：
    所述目标SeNB完成对UE的资源配置后，向所述MeNB回复接纳确认消息，在接纳确认消息中携带有为接收所述建立的split bearer的下行PDCP数据PDU而分配的传输层地址；
    所述MeNB收到接纳确认消息后，向所述源SeNB发送修改请求消息，在修改请求消息中携带有所述目标SeNB分配的传输层地址，其目的是建立所述源SeNB和所述目标SeNB之间为UE提供下行数据分流服务的用户面接口。
  7. 根据权利要求4所述的方法，其中，所述MeNB接收来自源SeNB的分配的传输层地址后发送给目标SeNB，以使在源SeNB和目标SeNB之间建立为UE提供上行数据分流服务的用户面接口包括：
    所述源SeNB向所述MeNB发送修改请求确认消息，在修改请求确认消息中携带有为接收所述建立的split bearer的上行RLC数据PDU而分配的传输层地址；
    所述MeNB在收到所述源SeNB的修改请求确认消息后，向所述目标SeNB发送X2通知消息，在X2通知消息中携带有所述源SeNB分配的传输层地址，其目的是建立所述源SeNB和所述目标SeNB之间为UE提供上行数据分流服务的用户面接口。
  8. 根据权利要求2～7任一项所述的方法，其中，该方法还包括：
    所述MeNB在收到所述源SeNB的修改请求确认消息后，根据接收到的接纳确认消息中所携带的信息组成面向UE的无线资源控制RRC信令并发送给UE；UE在收到来自所述MeNB的指示将第一个或多个SCG bearer从所述源SeNB转移到所述目标SeNB的RRC信令后，按照获得的RRC信令中携带的信息，与所述目标SeNB进行同步、向所述目标SeNB发起随机接入，按照新的配置建立SCG bearer，并建立对应的split bearer协议实体。
  9. 根据权利要求1所述的方法，其中，所述目标SeNB将上行RLC数据PDU转发给源SeNB包括：通过为接收所述建立的split bearer的上行RLC数据PDU而分配的传输层地址，将上行RLC数据PDU转发给所述源SeNB；
    所述源SeNB将下行PDCP数据PDU分流给目标SeNB包括：通过为接收所述建立的split bearer的下行PDCP PDU而分配的传输层地址，将部分或全部下行PDCP数据PDU分流给所述目标SeNB进行传输。
  10. 根据权利要求1所述的方法，其中，对于所述建立的split bearer，
    在下行链路上，数据在所述源SeNB的PDCP层和RLC层之间分流，分别发送给所述源SeNB和所述目标SeNB进行传递，所述目标SeNB上仅建立PDCP层之下的协议实体；所述UE从空口收到两 路下行数据后，在PDCP层进行合并；
    在上行链路上，数据在所述UE的RLC层和MAC之间分流，分别通过空口发送给所述源SeNB和所述目标SeNB，所述目标SeNB上仅建立RLC层之下的协议实体；所述目标SeNB收到上行数据后，发送给所述源SeNB，在所述源SeNB的RLC层进行合并。
  11. 根据权利要求4所述的方法，其中，所述建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口之后，该方法还包括：
    在UE接入所述目标SeNB并完成配置更新后，如果所述目标SeNB已经通过X2-U从所述源SeNB收到分流的下行PDCP数据PDU，所述目标SeNB开始将下行PDCP数据PDU通过split bearer的下层协议实体处理后发送给UE。
  12. 根据权利要求4所述的方法，其中，所述建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口之后，该方法还包括：
    UE接入所述目标SeNB并完成配置更新后，通过和所述目标SeNB对应的split bearer和/或SCG bearer协议实体，向所述目标SeNB发送上行数据包。
  13. 根据权利要求3、4、11或12所述的方法，其中，当所述源SeNB收到来自S-GW的结束标识时，该方法还包括：
    在所述源SeNB为所有下行数据包分配PDCP子层的SN号后，向所述目标SeNB发送SN状态传输消息，所述目标SeNB根据SN状态传输消息，开始为从S-GW收到下行数据包分配PDCP子层的SN号；在所述源SeNB完成所有下行数据的发送和/或转发后，向所 述MeNB请求进行所述源SeNB释放；相应地，
    所述目标SeNB成功发送所有的下行转发数据，或者已经从SCG bearer协议实体收到来自UE的上行数据包且已经完成所有转发上行数据包的排序，向所述MeNB请求删除所述split bearer协议实体；
    所述MeNB收到来自所述源SeNB和所述目标SeNB的释放所述源SeNB及删除所述split bearer协议实体的消息后，所述MeNB向源SeNB发送SeNB释放确认消息，所述MeNB向所述目标SeNB发送SeNB修改确认消息，所述MeNB向UE发送RRC连接重配置消息要求UE删除对应split bearer。
  14. 一种主服务基站，包括第一处理单元，设置为建立源SeNB与目标SeNB之间为UE提供上行数据服务和下行数据服务的用户面接口。
  15. 根据权利要求14所述的主服务基站，其中，所述第一处理单元包括第一建立模块，第二建立模块；其中，
    第一建立模块，设置为将来自所述目标SeNB分配的传输层地址发送给源SeNB，以使在所述源SeNB和所述目标SeNB之间建立为UE提供下行数据分流服务的用户面接口；
    第二建立模块，设置为接收来自所述源SeNB的分配的传输层地址后发送给所述目标SeNB，并以使在所述源SeNB和所述目标SeNB之间建立为UE提供上行数据分流服务的用户面接口；组成面向UE的RRC信令并发送给UE。
  16. 根据权利要求15所述的主服务基站，其中，所述第一建立模块还设置为：指示所述目标SeNB为所述源SeNB上一个或多个将要转移到所述目标SeNB上的SCG bearer建立对应的split bearer协议 实体。
  17. 根据权利要求16所述的主服务基站，其中，所述第一建立模块具体设置为：
    向所述目标SeNB发送携带有split bearer配置信息或建立split bearer的指示信息的接纳请求消息；其中，split bearer配置信息或建立split bearer的指示信息用于为所述源SeNB上一个或多个将要转移到所述目标SeNB上的SCG bearer在所述目标SeNB上建立对应的split bearer协议实体；
    接收来自所述目标SeNB的携带有为接收建立的split bearer的下行PDCP数据PDU而分配的传输层地址的接纳确认消息，向所述源SeNB发送携带有所述目标SeNB分配的传输层地址的修改请求消息。
  18. 根据权利要求15所述的主服务基站，其中，所述第二建立模块具体设置为：
    接收来自所述源SeNB的携带有为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的修改请求确认消息；向所述目标SeNB发送携带有所述源SeNB分配的为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的X2通知消息；根据接收到的接纳确认消息中所携带的信息组成面向UE的RRC信令并发送给UE。
  19. 根据权利要求18所述的主服务基站，其中，所述第二建立模块还设置为：
    收到来自所述源SeNB和所述目标SeNB的释放所述源SeNB及删除所述split bearer协议实体的消息，向所述源SeNB发送SeNB释放确认消息，向所述目标SeNB发送SeNB修改确认消息，向所述UE 发送RRC连接重配置消息要求UE删除对应split bearer。
  20. 一种辅服务基站，包括：第二处理单元，和/或第三处理单元；其中，
    第二处理单元，设置为按照来自MeNB的指示，为源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer建立对应的split bearer协议实体；为接收建立的split bearer的下行PDCP数据PDU而分配传输层地址；接收来自MeNB的源SeNB分配的传输层地址，在源SeNB和目标SeNB之间建立为UE提供上行数据分流服务的用户面接口；
    第三处理单元，用为接收建立的split bearer的上行RLC数据PDU而分配传输层地址；接收来自MeNB的目标SeNB的分配的传输层地址；在源SeNB和目标SeNB之间建立为UE提供下行数据分流服务的用户面接口。
  21. 根据权利要求20所述的辅服务基站，其中，所述第二处理单元具体设置为：
    接收到来自所述MeNB的携带有split bearer配置信息或建立split bearer的指示信息的接纳请求消息，为所述源SeNB上一个或多个将要转移到目标SeNB上的SCG bearer在所述目标SeNB上建立对应的split bearer协议实体；
    向所述MeNB发送携带有为接收建立的split bearer的下行PDCP数据PDU而分配的传输层地址的接纳确认消息；
    接收来自所述MeNB的携带有所述源SeNB分配的为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的修改请求确认消息；建立所述源SeNB和所述目标SeNB之间为UE提供上行数 据分流服务的用户面接口；
    在重配置过程中，将上行RLC数据PDU转发给所述源SeNB。
  22. 根据权利要求20所述的辅服务基站，其中，所述第三处理单元具体设置为：
    接收来自所述MeNB的携带有所述目标SeNB分配的传输层地址的修改请求消息；建立所述源SeNB和所述目标SeNB之间为UE提供下行数据分流服务的用户面接口；
    向所述MeNB发送携带有为接收建立的split bearer的上行RLC数据PDU而分配的传输层地址的修改请求确认消息；
    在重配置过程中，将下行PDCP数据PDU分流给所述目标SeNB。
  23. 根据权利要求22所述的辅服务基站，其中，所述第三处理单元还设置为：保持和所述UE的数据传输直到重配置成功。
  24. 根据权利要求20～23任一项所述的辅服务基站，其中，
    所述第三处理单元还设置为：收到来自S-GW的结束标识时为所有下行数据包分配PDCP子层的SN号后，向所述目标SeNB发送SN状态传输消息，完成所有下行数据的发送和/或转发后，向所述MeNB请求进行所述源SeNB释放；相应地，
    所述第二处理单元还设置为：根据SN状态传输消息，开始为从S-GW收到下行数据包分配PDCP子层的SN号；在已经成功发送所有的下行转发数据，或者，已经从SCG bearer协议实体收到来自UE的上行数据包且已经完成所有转发上行数据包的排序，向所述MeNB请求删除所述split bearer协议实体。
PCT/CN2016/106274 2016-01-04 2016-11-17 双连接中实现重配置的方法、主服务基站及辅服务基站 WO2017118225A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610006280.6 2016-01-04
CN201610006280.6A CN106941733B (zh) 2016-01-04 2016-01-04 双连接中实现重配置的方法、主服务基站及辅服务基站

Publications (1)

Publication Number Publication Date
WO2017118225A1 true WO2017118225A1 (zh) 2017-07-13

Family

ID=59273182

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/106274 WO2017118225A1 (zh) 2016-01-04 2016-11-17 双连接中实现重配置的方法、主服务基站及辅服务基站

Country Status (2)

Country Link
CN (1) CN106941733B (zh)
WO (1) WO2017118225A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110188990A (zh) * 2019-04-26 2019-08-30 阿里巴巴集团控股有限公司 一种资源请求和资金请求分流方法、装置及设备
CN111654883A (zh) * 2018-06-15 2020-09-11 Oppo广东移动通信有限公司 数据按序递交的方法、网络设备及终端设备
CN111918415A (zh) * 2019-05-10 2020-11-10 大唐移动通信设备有限公司 一种双连接修改的方法和设备

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI687122B (zh) * 2017-08-04 2020-03-01 聯發科技股份有限公司 多連接配置之方法及其使用者設備
WO2019030981A1 (ja) * 2017-08-09 2019-02-14 日本電気株式会社 無線アクセスネットワークノード、コアネットワークノード、及び無線端末並びにこれらの方法
CN109391362B (zh) * 2017-08-11 2022-07-29 中兴通讯股份有限公司 一种信令传输方法及装置
CN108882334B (zh) 2017-08-11 2019-11-05 华为技术有限公司 一种数据传输方法、核心网用户面设备和源基站
CN109802982B (zh) * 2017-11-17 2021-04-20 中兴通讯股份有限公司 一种双连接实现方法、装置及系统
US11032866B2 (en) * 2017-11-27 2021-06-08 FG Innovation Company Limited Methods and related devices for multi-connectivity
CN110691424B (zh) 2018-01-12 2020-09-18 华为技术有限公司 一种cu-du架构下重复模式的通信处理方法和设备
CN114125961A (zh) * 2018-02-13 2022-03-01 华为技术有限公司 传输控制方法、装置和系统
CN113873601A (zh) 2018-03-14 2021-12-31 中兴通讯股份有限公司 地址协同方法、装置、基站、smf网元及存储介质
CN113099442B (zh) * 2018-04-04 2023-09-15 中兴通讯股份有限公司 地址分配方法、装置、核心网、节点、网络系统及介质
CN110445589B (zh) * 2018-05-04 2021-11-12 大唐移动通信设备有限公司 一种业务数据包的处理方法及装置
CN110932986B (zh) * 2018-09-20 2023-04-07 中国电信股份有限公司 数据包分流方法、装置及计算机可读存储介质
CN110944368A (zh) * 2018-09-25 2020-03-31 电信科学技术研究院有限公司 一种切换过程中传输数据的方法和设备
CN111225423B (zh) * 2018-11-27 2022-04-01 中国移动通信有限公司研究院 一种数据前转的方法和设备
CN113196827A (zh) * 2019-03-18 2021-07-30 苹果公司 Mr-dc中利用涉及sn改变的5gc操作的数据转发
CN109819491B (zh) * 2019-03-21 2021-07-06 创新维度科技（北京）有限公司 切换控制方法、基站和存储介质
CN111757397B (zh) * 2019-03-28 2021-11-16 大唐移动通信设备有限公司 一种进行数据前转的方法及设备
CN111866963B (zh) * 2019-04-28 2021-12-31 华为技术有限公司 通信方法、通信装置、计算机存储介质及通信系统
CN111867141B (zh) * 2019-04-29 2022-07-19 大唐移动通信设备有限公司 一种数据传输方法及装置
CN111800831B (zh) * 2019-08-01 2021-09-07 维沃移动通信有限公司 路径变换方法、设备、通信系统及计算机可读存储介质
CN112533256A (zh) * 2019-09-17 2021-03-19 维沃移动通信有限公司 数据传输方法、终端及网络节点
CN112788787A (zh) * 2019-11-07 2021-05-11 Oppo（重庆）智能科技有限公司 网络连接的控制方法、终端及存储介质
CN112822698B (zh) * 2019-11-15 2022-04-05 大唐移动通信设备有限公司 一种上行数据分流方法及装置
CN113613244A (zh) * 2020-04-17 2021-11-05 华为技术有限公司 一种节点切换方法和装置
CN113784391B (zh) * 2020-06-09 2023-08-15 中国移动通信集团设计院有限公司 自适应数据分流方法及装置
CN117098198A (zh) * 2020-08-04 2023-11-21 大唐移动通信设备有限公司 基于mbms业务的切换方法、装置及处理器可读存储介质
CN115002827A (zh) * 2021-03-01 2022-09-02 中兴通讯股份有限公司 一种本地边缘分流方法、系统以及分流服务装置和基站

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888222A (zh) * 2014-03-21 2014-06-25 电信科学技术研究院 一种数据包处理方法及装置
US20150215824A1 (en) * 2014-01-29 2015-07-30 Samsung Electronics Co., Ltd. Method and apparatus for performing handover of user equipment in wireless communication system supporting dual connectivity
CN104935414A (zh) * 2014-03-21 2015-09-23 上海贝尔股份有限公司 一种在双连接系统中传输信息的方法和装置
CN105103610A (zh) * 2013-04-02 2015-11-25 Lg电子株式会社 在无线通信系统中执行小区变化过程的方法及其装置

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2452469A1 (en) * 2009-07-10 2012-05-16 Nokia Siemens Networks OY Method and device for conveying traffic
CN102469557B (zh) * 2010-11-15 2014-08-13 华为技术有限公司 接入基站方法、基站和用户设备
CN103582124B (zh) * 2012-07-24 2016-12-21 电信科学技术研究院 一种业务建立的方法、系统和设备
EP3522601B1 (en) * 2012-08-07 2021-12-01 Huawei Technologies Co., Ltd. Handover processing method and base station
CN103687047B (zh) * 2012-09-07 2017-12-19 京信通信系统（中国）有限公司 通用分组无线服务业务数据传输方法、装置及系统
CN103945470A (zh) * 2013-01-18 2014-07-23 华为技术有限公司 切换方法、源通信节点和目标通信节点
EP2811808A1 (en) * 2013-04-01 2014-12-10 Innovative Sonic Corporation Method and Apparatus for Triggering a Regular Buffer Status Report (BSR) in Dual Connectivity
CN104378841A (zh) * 2013-08-12 2015-02-25 中兴通讯股份有限公司 一种连接移动性管理方法及节点设备
CN104378793B (zh) * 2013-08-12 2019-06-14 中兴通讯股份有限公司 一种切换方法、主控基站及受控基站
CN104468029A (zh) * 2013-09-18 2015-03-25 中国移动通信集团公司 一种移动终端通信方法、装置及相关设备
CN104469869B (zh) * 2013-09-23 2019-08-13 中兴通讯股份有限公司 一种小小区切换方法和基站
CN104602307A (zh) * 2013-10-30 2015-05-06 北京三星通信技术研究有限公司 切换方法及系统
KR102025420B1 (ko) * 2013-11-01 2019-09-25 이노스카이 주식회사 이중연결 방식을 이용하는 무선통신 시스템에서 불연속 수신을 위한 파라미터 구성 방법 및 장치
CN104811924B (zh) * 2014-01-24 2018-07-13 上海诺基亚贝尔股份有限公司 用于双连接系统的用户设备历史信息的管理方法
CN104812000A (zh) * 2014-01-27 2015-07-29 中兴通讯股份有限公司 一种实现数据传输的方法及装置
CN104821859B (zh) * 2014-01-30 2018-08-14 上海诺基亚贝尔股份有限公司 用于在分组数据汇聚协议层处理数据的方法和设备
WO2015119410A1 (en) * 2014-02-06 2015-08-13 Lg Electronics Inc. Method for processing a packet data convergence protocol service data unit at a user equipment in a dual connectivity system and device therefor
CN104902580B (zh) * 2014-03-05 2021-06-01 北京三星通信技术研究有限公司 一种小小区系统中支持数据转发的方法
CN104936175B (zh) * 2014-03-21 2018-11-16 上海诺基亚贝尔股份有限公司 在双连接的通信环境下进行密钥更新的方法和装置
CN103888981B (zh) * 2014-03-25 2017-12-29 电信科学技术研究院 一种通信路径的确定方法和装置
CN104980980A (zh) * 2014-04-10 2015-10-14 电信科学技术研究院 一种建立连接的方法、系统和设备
CN104301955A (zh) * 2014-09-02 2015-01-21 中兴通讯股份有限公司 一种用户设备切换基站的方法及基站、用户设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105103610A (zh) * 2013-04-02 2015-11-25 Lg电子株式会社 在无线通信系统中执行小区变化过程的方法及其装置
US20150215824A1 (en) * 2014-01-29 2015-07-30 Samsung Electronics Co., Ltd. Method and apparatus for performing handover of user equipment in wireless communication system supporting dual connectivity
CN103888222A (zh) * 2014-03-21 2014-06-25 电信科学技术研究院 一种数据包处理方法及装置
CN104935414A (zh) * 2014-03-21 2015-09-23 上海贝尔股份有限公司 一种在双连接系统中传输信息的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Correction on Dual Connectivity Stage 2,", 3GPP TSG-RAN WG3 MEETING #87BIS-R3-150810, 24 April 2015 (2015-04-24), XP050954509 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111654883A (zh) * 2018-06-15 2020-09-11 Oppo广东移动通信有限公司 数据按序递交的方法、网络设备及终端设备
CN111654883B (zh) * 2018-06-15 2023-01-31 Oppo广东移动通信有限公司 数据按序递交的方法、网络设备及终端设备
US11689334B2 (en) 2018-06-15 2023-06-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for submitting data in sequence, network device and terminal device
CN110188990A (zh) * 2019-04-26 2019-08-30 阿里巴巴集团控股有限公司 一种资源请求和资金请求分流方法、装置及设备
CN110188990B (zh) * 2019-04-26 2023-09-08 创新先进技术有限公司 一种资源请求和资金请求分流方法、装置及设备
CN111918415A (zh) * 2019-05-10 2020-11-10 大唐移动通信设备有限公司 一种双连接修改的方法和设备

Also Published As

Publication number Publication date
CN106941733B (zh) 2022-05-13
CN106941733A (zh) 2017-07-11

Similar Documents

Publication Publication Date Title
WO2017118225A1 (zh) 双连接中实现重配置的方法、主服务基站及辅服务基站
US11477712B2 (en) Maintaining communication and signaling interfaces through a network role transition
US10085189B2 (en) Method of controlling handover procedure and base station
US10251111B2 (en) Base station handover method in heterogeneous network, and base station
WO2015184889A1 (zh) 一种用户设备切换基站的方法及基站、用户设备
WO2018219039A1 (zh) 一种移动切换的管理方法、装置、设备及存储介质
CN104349419B (zh) 终端多连接的管理方法、装置和系统
EP3253122A1 (en) Method, apparatus, and system for transmitting data during handover procedure
WO2017054538A1 (zh) 建立辅助信令链路的方法及其装置、基站及终端
US10278115B2 (en) Bearer admission control method and bearer admission control apparatus
WO2016161759A1 (zh) 数据的传输方法及装置
KR20230149884A (ko) 핸드오버를 지원하는 방법 및 상응하는 장치
WO2014094582A1 (zh) 分层组网时的承载转移方法和设备
WO2012019467A1 (zh) 获取邻接基站/中继节点接口信息的方法及无线中继系统
JPWO2016167212A1 (ja) 基地局及び通信制御方法
WO2014000684A1 (zh) 一种进行切换的方法、系统和设备
WO2017177950A1 (zh) 连接的建立方法、装置及系统
CN111405666A (zh) 一种rn支持多种无线接入系统的方法
WO2016155481A1 (zh) 用户数据的传输处理方法、装置、系统及计算机存储介质
WO2011113210A1 (zh) 多基站间本地交换的方法及装置
KR20210114572A (ko) 데이터 전송 시스템에서의 데이터 전송 방법 및 장치
WO2016101468A1 (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: 16883352

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

Country of ref document: EP

Kind code of ref document: A1