WO2017118186A1

WO2017118186A1 - Data transmission method and apparatus, and base station and ue

Info

Publication number: WO2017118186A1
Application number: PCT/CN2016/103935
Authority: WO
Inventors: 施小娟; 黄河
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-01-04
Filing date: 2016-10-31
Publication date: 2017-07-13
Also published as: CN106941700A; CN106941700B

Abstract

Disclosed are a data transmission method and apparatus, and a base station and a UE. The method comprises: establishing a standby data transmission channel on an MCG for an RB needing to use an SeNB resource; and during a change process of an SeNB, using the standby data transmission channel to transmit data, wherein the transmitted data comprises data that has been distributed to an RLC entity of a source SCG before the SeNB changes but is not completely transmitted in the source SCG.

Description

Data transmission method and device, base station and UE

Technical field

The present application relates to, but is not limited to, a mobile communication technology, and more particularly to a data transmission method and apparatus, and a base station and a UE (User Equipment, User Equipment/User Terminal).

Background technique

Cellular wireless mobile communication systems began in the 1980s and have evolved from the beginning to meet the needs of human voice communication to the basic needs of human data communication on the basis of voice services. The traditional cellular wireless communication system is deployed and operated by the wireless network operator. The network construction is carefully planned by the operator. Figure 1 is a schematic diagram of the network topology of the traditional cellular wireless access network. As shown in Figure 1, each macro base station (macro) (e) The location of the NB is determined by the operator's plan. Each macro base station can reach a wireless coverage of several hundred meters or even several kilometers, so that nearly continuous seamless coverage within the operator's operating area can be achieved.

With the advent of the mobile Internet era, the demand for new mobile applications, especially those requiring high quality, high speed, low latency, has exploded. According to industry forecasts, on the one hand, wireless mobile services will increase by a thousand times in the next 10 years. Traditional wireless communication systems that implement long-distance macro coverage cannot achieve such huge capacity requirements. On the other hand, the industry has adopted users. Statistics on communication behaviors and habits found that most of the high-traffic mobile services are concentrated in indoor environments and hotspots, such as shopping malls, schools, users' homes, large-scale performances, gathering places, etc., while indoor environments and hotspots have wide regional distribution. The characteristics of the scattered, single-area range and user concentration, that is to say, the wide coverage, uniform coverage and fixed coverage characteristics of the traditional cellular wireless network make it unable to adapt well to the characteristics of the concentrated business in such a small area. In addition, traditional cellular wireless networks may cause cellular wireless signals to be inferior to outdoor environments in indoor environments due to various reasons, such as building blocks, which also makes traditional cellular wireless networks unable to meet the demand for large data capacity in future indoor environments. .

In order to solve the above problem, a low power node (LPN, Low Power Node) came into being. Conceptually, LPN refers to a base station node whose transmission power is lower than that of a conventional macro base station and whose coverage is smaller than that of a conventional macro base station (for example, several tens of meters). It may be a Pico Node, a Femto/Home (e)NB, a Radio Relay Access Device (Relay), and any other network access that may occur to a base station node or a wireless network that satisfies the above concepts. node. Compared with a macro cell covering a macro base station coverage of several hundred meters or even several kilometers, a cell covering tens of meters covered by an LPN is called a small cell or a small cell.

In order to meet the huge capacity increase requirements of future wireless communication systems, especially in order to meet the demand for centralized large data volume in a specific area, the industry predicts that the density of LPN deployment can be increased in a specific area to achieve network capacity growth and meet user needs. . The industry refers to such a densely deployed network in a specific area as the Ultra Dense Network (UDN). 2 is a schematic diagram of deploying a UDN in a specific area of a conventional cellular radio access network. As shown in FIG. 2, a large number of low power nodes are deployed in the building 200, in the stadium 210, and in the hotspot 230 area.

After the UDN network is deployed, when the user equipment/user terminal (UE) moves in such a dense network, even if the UE moves at a walking speed compared to the original widely covered macro network, the small cell is frequently changed, as shown in FIG. 2 . The moving path 240 of the UE indicated by the thick black solid arrow indicates that the UE frequently changes the small cell in a short time. In the related art, when the UE moves between different cells, the handover technology is used to implement the connection transmission of data between different cells. The handover technology provided by the related technology is applicable to a wide coverage macro network or a non-dense deployment network, if It is directly applied to the UDN network that frequently changes the small cell. Although it can ensure the continuous transmission of data between the frequently changing small cells, it will inevitably lead to frequent jitter of the data rate, and ultimately reduce the user data transmission rate and affect the user experience.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The present invention provides a method and apparatus for implementing data transmission, and a base station and a UE, which can implement smooth transmission of data, improve user data transmission rate, and thereby enhance user experience.

A data transmission method includes: establishing, on a master serving cell group MCG, a backup data transmission path for a radio bearer RB that needs to use a secondary base station SeNB resource;

In the SeNB change process, the data is transmitted using the alternate data transmission path, wherein the transmitted data includes the radio link control RLC entity that has been distributed to the source secondary serving cell group S-SCG before the SeNB change but is not completed at the S-SCG. The data transferred.

Optionally, the method further includes: establishing the RB that needs to use the SeNB resource;

The establishing an alternate data transmission path includes:

When the RB that needs to use the SeNB resource is established, the standby data transmission path is established for the RB; or

When the SeNB changes, the standby data transmission path is established for the RB that needs to use the SeNB resource that has been established.

Optionally, the alternate data transmission path is: a standby forked bearer of an RB that needs to use the SeNB resource, or a standby forked logical channel of the RB that needs to use the SeNB resource.

Optionally, the standby data transmission path is a standby fork bearing;

The alternate fork bearer includes at least one alternate RLC entity and at least one alternate logical dedicated traffic channel DTCH.

Optionally, the standby data transmission path is a standby fork bearing;

The standby fork bearer uses a security configuration of the MCG, and the standby forked bearer includes a standby RLC entity connected to a packet data control protocol PDCP entity established on the MCG by an RB that needs to use the SeNB resource; or

The alternate fork bearer uses a security configuration of the S-SCG, and the alternate fork bearer includes a backup RLC entity connected to a PDCP entity established on the S-SCG by an RB that needs to use the SeNB resource.

Optionally, the standby data transmission path is a standby forked logical channel;

The alternate forked logical channel includes: at least one standby DTCH established for the RB using the SeNB resource; wherein the standby DTCH connection is between the RLC entity established on the MCG for the RB requiring the use of the SeNB resource and the medium access control MAC entity on the MCG .

Optionally, the performing, in the SeNB change process, after the MeNB to which the MCG belongs requests the target SeNB after the SeNB changes to allocate resources and receives a positive reply of the target SeNB response;

Or, after the MeNB to which the MCG belongs receives the RLC entity from the source SeNB that has been distributed to the source SeNB before the SeNB changes but does not complete the transmission of the data at the source SeNB;

Or after the user terminal UE receives the notification message sent by the MeNB to which the MCG belongs.

Optionally, the transmitting data by using the alternate data transmission path includes:

When the alternate data transmission path is a standby forked bearer, using at least one standby RLC entity and one of the at least one standby DTCH and one standby DTCH to transmit data;

When the alternate data transmission path is a standby forked logical channel, data is transmitted using one of the at least one standby DTCH and an RLC entity that has been established for the RB that needs to use the SeNB resource.

Optionally, when the standby forked bearer uses the security configuration of the MCG, and the standby RLC entity is connected to a PDCP entity established on the MCG by using an RB that needs to use the SeNB resource, the data that is transmitted includes:

A PDCP packet data packet PDU that is distributed by the PDCP entity of the MCG to the RLC entity of the S-SCG but not completed at the S-SCG.

Optionally, the transmitted data further includes:

a PDCP PDU issued by a PDCP entity of the MCG, except for a PDCP PDU that is distributed by the PDCP entity of the MCG to the RLC entity of the S-SCG but not completed by the S-SCG.

Optionally, when the standby forked bearer uses a security configuration of the S-SCG, where the standby RLC entity is connected to a PDCP entity established on the S-SCG by an RB that needs to use the SeNB resource, the transmission The data includes:

The downlink data received by the source SeNB from the core network but not completed by the source SeNB is processed by the PDCP entity established by the RB that needs to use the SeNB resource on the source SeNB to process the generated PDCP PDU.

Optionally, the transmitted data includes: a PDCP PDU that is distributed by the PDCP entity of the MCG to an RLC entity of the source SCG but does not complete transmission at the source SCG.

Optionally, the transmitted data further includes: a split by the PDCP entity of the MCG. A PDCP PDU that is distributed by the PDCP entity of the MCG to the RLC entity of the source SCG but not the PDCP PDU that completes the transmission at the source SCG.

Optionally, the method further includes: stopping the use of the alternate data transmission path to transmit data.

Optionally, when the standby data transmission path is a standby forked bearer and the standby forked bearer on the MCG uses the security configuration of the MCG, the standby RLC entity and the RB that needs to use the SeNB resource are established on the MCG. When the PDCP entity is connected, or when the alternate data transmission path is a standby forked logical channel,

The stopping the use of the alternate fork carrier to transmit data includes:

After the user equipment UE successfully accesses the target SeNB after the change of the SeNB, the MeNB that the MCG belongs to is notified, and the UE stops using the alternate data transmission path to transmit data, and the MeNB to which the MCG belongs receives the notification and stops using the alternate data transmission path to transmit. Data; or,

After the UE successfully accesses the target SeNB after the change of the SeNB, the target SeNB stops transmitting data using the alternate data transmission path, and the target SeNB sends a notification that the UE has successfully accessed the MeNB to which the MCG belongs, and the MeNB to which the MCG belongs receives the notification. Stop using the alternate data transfer path to transfer data; or,

The MeNB to which the MCG belongs sends a SeNB change notification to the UE for a predetermined period of time T, and then stops using the alternate data transmission path to transmit data, and the UE stops using after receiving the SeNB change notification sent by the MeNB to which the MCG belongs for a preset duration T. The alternate data transmission path transmits data.

Optionally, when the backup data transmission path is a standby forked bearer and the security configuration of the S-SCG, the standby RLC entity is connected to a PDCP entity established on the S-SCG by an RB that needs to use the SeNB resource. The stopping the use of the alternate fork carrier to transmit data includes:

When the downlink data received by the source SeNB from the core network but not completed by the source SeNB is transmitted on the backup data transmission path, the use of the alternate data transmission path to stop data transmission is stopped.

Optionally, the method further includes: the standby RLC entity is connected to the PDCP entity established on the target SCG T-SCG after the SeNB changes by using the RB that needs to use the SeNB resource, and uses the security configuration of the T-SCG.

A data transmission device comprising:

Establishing a module, configured to: establish an alternate data transmission path on the MCG for the RB that needs to use the SeNB resource;

The data transmission module is configured to: during the SeNB change process, transmit data using an alternate data transmission path, where the transmitted data includes an RLC entity that has been distributed to the S-SCG before the SeNB changes but does not complete the transmission at the S-SCG. data.

Optionally, the establishing module is configured to: when establishing the RB that needs to use the SeNB resource, establish an alternate data transmission path for the RB; or, when the SeNB changes, use the SeNB resource for the established needs. The RB establishes an alternate data transmission path.

Optionally, the standby data transmission path is a standby fork bearing;

The alternate fork bearer includes at least one standby RLC entity and at least one standby DTCH.

Optionally, the standby data transmission path is a standby fork bearing;

The standby forked bearer uses a security configuration of the MCG, and the standby split-branch bearer includes a backup RLC entity that is connected to a PDCP entity established on the MCG by an RB that needs to use the SeNB resource; or

The standby fork bearer uses a security configuration of the S-SCG, and the standby forked bearer includes a backup RLC entity connected to a PDCP entity established on the S-SCG by an RB that needs to use the SeNB resource.

The alternate forked logical channel includes at least one standby DTCH established for the RB using the SeNB resource; wherein the alternate DTCH connection is between the RLC entity established on the MCG for the RB that needs to use the SeNB resource and the MAC entity on the MCG.

Optionally, when the device is separately configured on the network side or the MeNB, the data transmission module is configured to:

After the MeNB to which the MCG belongs requests the target SeNB after the SeNB changes to allocate resources and receives a positive reply from the target SeNB, and uses the alternate data transmission path to transmit data;

Or, the MeNB to which the MCG belongs receives data from the source SeNB that has been distributed to the RLC entity of the source SeNB before the SeNB changes but does not complete the transmission at the source SeNB. After that, the data is transmitted using the alternate data transmission path.

Optionally, when the device is separately configured in the user side or the UE, the data transmission module is configured to: after receiving the notification message sent by the MeNB to which the MCG belongs, the UE uses the alternate data transmission path to transmit data.

Optionally, when the standby data transmission path is a standby forked bearer, the data transmission module is configured to: use one of at least one standby RLC entity and at least one standby DTCH established for an RB that needs to use the SeNB resource. The standby RLC entity and a standby DTCH transmit data;

When the alternate data transmission path is a standby forked logical channel, the data transmission module is configured to: use one of the at least one standby DTCH and the RLC entity that has been established for the RB that needs to use the SeNB resource to transmit data. .

Optionally, the standby splitting bearer established by the establishing module on the MCG uses a security configuration of the MCG, where the standby RLC entity is connected to the PDCP entity established on the MCG by the RB that needs to use the SeNB resource.

The data transmitted by the data transmission module includes: a PDCP PDU distributed by the PDCP entity of the MCG to the RLC entity of the S-SCG but not completed at the S-SCG.

Optionally, the data transmitted by the data transmission module further includes: an RLC entity that is delivered by the PDCP entity of the MCG to be distributed by the PDCP entity of the MCG to the S-SCG but not in the S- The SCG completes other PDCP PDUs other than the transmitted PDCP PDU.

Optionally, the standby splitting bearer established by the establishing module on the MCG uses a security configuration of the SCG, where the standby RLC entity is connected to the PDCP entity established on the SCG by the RB that needs to use the SeNB resource.

The data transmitted by the data transmission module includes: downlink data received by the source SeNB from the core network but not completed by the source SeNB, and PDCP generated by the PDCP entity established by the RB that needs to use the SeNB resource on the source SeNB. PDU.

Optionally, the data transmitted by the data transmission module includes: a PDCP PDU distributed by the PDCP entity of the MCG to an RLC entity of the source SCG but not completed at the source SCG.

Optionally, the data that is transmitted by the data transmission module further includes: an RLC entity that is delivered by the PDCP entity of the MCG but is not distributed by the PDCP entity of the MCG to the source SCG. The source SCG completes other PDCP PDUs than the transmitted PDCP PDU.

Optionally, the standby splitting bearer established by the establishing module on the MCG uses a security configuration of the MCG, where the established standby RLC entity is connected with a PDCP entity established on the MCG by using an RB that needs to use the SeNB resource, or When the alternate data transmission path is an alternate forked logical channel,

When the device is separately configured in the user side or the UE, the data transmission module is further configured to: after the UE successfully accesses the target SeNB after the SeNB changes, or the UE receives the SeNB sent by the MeNB to which the MCG belongs. After changing the notification for a preset duration T, stopping using the alternate data transmission path to transmit data;

When the device is separately disposed in the network side or the MeNB, the data transmission module is further configured to: after the MeNB to which the MCG belongs, receive the UE from the target SeNB after the UE or the SeNB changes, the UE successfully accesses the After the SeNB changes the notification of the target SeNB after the change, the use of the alternate data transmission path to stop data transmission is stopped.

Optionally, the standby splitting bearer established by the establishing module on the MCG uses a security configuration of the SCG, where the standby RLC entity is connected to the PDCP entity established on the SCG by the RB that needs to use the SeNB resource,

When the device is separately disposed on the network side or the MeNB, the data transmission module is configured to stop using the downlink data received by the source SeNB from the core network but not completed by the source SeNB after the transmission is completed. The alternate data transmission path transmits data.

A base station comprising the apparatus of any of the above.

A UE comprising the apparatus of any of the above.

A computer readable storage medium storing computer executable instructions for performing the data transfer method of any of the above.

Compared with the related art, the technical solution of the present application includes: establishing, on the MCG, an alternate data transmission path for an RB that needs to use the SeNB resource; in the SeNB changing process, transmitting data by using an alternate data transmission path, where the transmitted data is included in the SeNB. The data that has been previously distributed to the RLC entity of the source SCG but not completed at the source SCG is changed. The technical solution provided by the embodiment of the present invention uses the standby data in the process of changing the SeNB by establishing the standby data transmission path. The transmission path transmits data, which ensures the continuity of data transmission during the change of the SeNB, realizes smooth transmission of data, improves the data transmission rate of the user, and enhances the user experience.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a schematic diagram of a network topology of a related art cellular radio access network;

2 is a schematic diagram of deploying a UDN in a specific area of a conventional cellular radio access network;

3 is a schematic diagram of a DC 3C protocol architecture in the related art;

4 is a schematic diagram of a DC 1A protocol architecture in the related art;

FIG. 5 is a flowchart of a method for implementing data transmission according to an embodiment of the present invention;

FIG. 6 is a schematic flowchart diagram of a first embodiment of implementing data transmission according to the present invention; FIG.

7(a) is a diagram showing a wireless protocol architecture of a downlink split bearer and a standby fork bearer established by the base station side in the first embodiment of the present invention;

FIG. 7(b) is a diagram showing a radio protocol architecture of a UE side corresponding to the base station side radio protocol architecture diagram of FIG. 7(a) according to the first embodiment of the present invention;

FIG. 7(c) is a diagram showing a wireless protocol architecture of a downlink split bearer and a standby forked logical channel established on the base station side in the first embodiment of the present invention;

7(d) is a diagram showing a radio protocol architecture of a UE side corresponding to the base station side radio protocol architecture diagram of FIG. 7(c) in the first embodiment of the present invention;

FIG. 8 is a schematic diagram of a wireless protocol architecture of an uplink split bearer and a standby fork bearer established by the UE side according to the first embodiment of the present invention;

FIG. 9 is a schematic diagram of a wireless protocol architecture of a downlink split bearer and two standby fork bearers established according to an embodiment of the present invention; FIG.

FIG. 10 is a schematic flowchart diagram of another embodiment of implementing data transmission according to the present invention; FIG.

FIG. 11 is a schematic flowchart diagram of a second embodiment of implementing data transmission according to the present invention; FIG.

12(a) is a schematic diagram of a wireless protocol architecture in which a SeNB changes a front downlink split bearer according to a second embodiment of the present invention;

12(b) is a schematic diagram of a wireless protocol architecture of a downlink split bearer in a SeNB change process according to a second embodiment of the present invention;

FIG. 12(c) is a schematic diagram of a wireless protocol architecture of a downlink splitting bearer after a SeNB is changed according to a second embodiment of the present invention;

FIG. 13 is a schematic flowchart diagram of a third embodiment of implementing data transmission according to the present invention; FIG.

14(a) is a diagram showing a wireless protocol architecture of a downlink split bearer and a standby fork bearer established by a base station side according to a third embodiment of the present invention;

14(b) is a diagram showing a wireless protocol architecture of an uplink split bearer and a standby fork bearer established by the UE side in the third embodiment of the present invention;

FIG. 15 is a schematic flowchart diagram of a fourth embodiment of implementing data transmission according to the present invention; FIG.

16(a) is a schematic diagram of a wireless protocol architecture in which a SeNB changes a pre-downlink SCG bearer according to a fourth embodiment of the present invention;

16(b) is a schematic diagram of a wireless protocol architecture of a downlink SCG bearer in a process of changing an SeNB according to a fourth embodiment of the present invention;

16(c) is a schematic diagram of a wireless protocol architecture of a downlink SCG bearer after a SeNB is changed according to a fourth embodiment of the present invention;

FIG. 17 is a schematic structural diagram of a device for implementing data transmission according to an embodiment of the present invention.

Embodiments of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

Taking Long Term Evaluation (LTE) as an example, in a traditional macro network, when a UE that is performing service transmission moves from one macro cell to another, it adopts a hard handover mode, that is, the UE first from the source macro. The cell is disconnected and then accesses the target macro cell. In order to prevent data interruption in this process, the source macro cell will send data that has not been transmitted in the source macro cell or has been transmitted but has not been successfully transmitted to the target macro cell, and the industry refers to this behavior as data forwarding. (data forwarding), data forwarding is ensured during the hard handover process. Although data forwarding can guarantee lossless connection transmission during cell change, in the hard handover mode, the UE disconnects from the source cell to successfully access the target cell until data transmission can be started in the target cell ( In this paper, it is called data interruption transmission time. No data can be transmitted between the UE and the network, which inevitably causes the user data rate to drop. When the UE can start data transmission in the target cell, the data transmission rate decreases due to the previous data interruption transmission time, and the processing mechanism of the related communication protocol, such as the slow start mechanism of the Transmission Control Protocol (TCP) transmission window. Moreover, the rise of the data rate is a process of climbing uphill, and cannot directly restore the data transmission rate of the UE in the source cell before the handover, that is, the hard handover process necessarily leads to a decrease in the data transmission rate. Since the coverage radius of the traditional macro network cell is large, in terms of statistical probability, the UE has a lower probability of a cell change, that is, a hard handover, compared to the service transmission life cycle of the UE, and the impact on the overall service transmission rate of the UE is not Big.

In order to improve user throughput and system throughput, the dual connectivity (DC, Dual Connectivity) function is introduced in the 3GPP R12 phase. The UE can simultaneously connect to two base stations and simultaneously perform service data transmission on two base stations. Among the two base stations connected by the UE, one base station terminates the control plane interface between the radio access network and the core network, that is, the S1-Mobile Management Entity (S1-MME) interface, which is called the master base station (MeNB, Master eNB). One or more serving cells of the UE on the MeNB are called a master cell group (MCG), and one or more serving cells of the MCG, one of which is a primary cell (Pcell, Primary Cell) The Pcell establishes an initial connection between the UE and the MeNB, or reestablishes the connected cell, or the cell designated as the Pcell by the MeNB during the handover, and the remaining cells are the secondary cells on the MeNB, and the secondary cell on the MeNB provides the MeNB and the UE. Additional resources, when there is only one serving cell on the MCG, the serving cell is a Pcell; the other base station provides additional radio resources for the UE, called a secondary base station (SeNB, Secondly eNB), and the UE is on the SeNB or The multiple serving cells are called the Secondary Cell Group (SCG), and one of the one or more serving cells of the SCG, one of the cells is a Primary Secondary Cell (PScell), PScell A cell that performs random access between the UE and the SeNB, and the other remaining cells are the secondary cells on the SeNB, and the secondary cell on the SeNB provides additional resources between the SeNB and the UE. When there is only one serving cell on the SCG, the The serving cell is the PScell. In DC, UE is the same When connecting to two base stations, there are two architectures from the wireless protocol stack, which are called architecture 3C and architecture 1A.

3 is a schematic diagram of a DC 3C protocol architecture in the related art. As shown in FIG. 3, the UE is simultaneously connected to the MeNB and the SeNB, and the MeNB terminates the control plane interface between the radio access network and the core network, and terminates on the other hand. A user plane (S1-U, User plane) interface between the radio access network and the core network (the S1 interface is a user plane interface between the base station and the core network). In the 3C downlink architecture shown in FIG. 3, there are two radio bearers (RBs), namely, RB1 and RB2, wherein all radio protocol stacks of RB1 are located on the MeNB, and only the radio resources of the MeNB can be used. The master cell group bearer (MCG bearer), and the radio protocol stack of the RB2 can be located on the MeNB or the SeNB, and can simultaneously use the radio resources of the MeNB and the SeNB, and is called a split bearer (split). Bearer). The Packet Data Convergence Protocol (PDCP) of the RB2 is located on the MeNB, and the protocols below the PDCP include the Radio Link Control (RLC) protocol and the Media Access Control (MAC) protocol. The MeNB and the SeNB are both provided. Therefore, the following data is taken as an example. After the data packet arrives at the MeNB through the S1-U interface, the PDCP of the MeNB performs header compression, and the PDCP PDU is generated after the encryption and the like, and the MeNB generates the PDCP. The PDU part is sent to the RLC layer of the RB2 in the MeNB, and the part is sent to the RLC layer of the RB2 in the SeNB, so that the data of the RB2 is simultaneously transmitted in the MeNB and the SeNB, and the throughput rate of the user data is improved.

4 is a schematic diagram of a DC 1A protocol architecture in the related art. As shown in FIG. 4, the UE is simultaneously connected to the MeNB and the SeNB. In the 1A architecture, the MeNB and the SeNB and the core network respectively have independent S1-U interfaces. In the 1A downlink architecture shown in FIG. 4, there are two RBs, namely, RB3 and RB4, and all the radio protocol stacks of the two RBs are located independently on the eNB where the RB1 is located, and the RB1 can only use the radio resources of the MeNB, which is the MCG. Bearer; RB2 can only use the radio resources of the SeNB, called the SCG bearer (Secondary Cell Group bearer).

In the R12DC, the MeNB is generally a macro base station, and the SeNB is generally an LPN. The eNB needs to use the resources of the SeNB in both the DC 1A architecture and the DC 3C architecture. When the SeNB changes, the MeNB deletes the source SeNB on the radio interface. Adding a target SeNB, which is essentially a hard handover behavior, when the UE disconnects from the source SeNB to successfully access the target SeNB and can The time during which the target SeNB performs data transmission will result in a decrease in the user data rate, such as a decrease in the RB2 data rate in FIG. 3 and a decrease in the RB4 data rate in FIG. In a network where the SeNB is not densely deployed, frequent changes of the SeNB do not occur. Therefore, the above problem does not have a significant impact on the user service experience. However, in the future UDN, dense deployment of small cells may cause even if the UE moves at a walking speed. The SeNB is also frequently changed. At this time, the zigzag jitter of the user data throughput is inevitably caused, and the user cannot provide a smooth and consistent user experience.

FIG. 5 is a flowchart of a method for implementing data transmission according to an embodiment of the present invention. As shown in FIG. 5, the method includes:

Step 500: Establish an alternate data transmission path on the MCG for the RB that needs to use the SeNB resource.

The alternate data transmission path in this step is a standby forked bearer of an RB that needs to use the SeNB resource, or a standby forked logical channel that is an RB that needs to use the SeNB resource.

Wherein, when the alternate data transmission path is a standby fork carrier:

At least one standby RLC entity and at least one alternate logical dedicated traffic channel (DTCH) may be established on the MCG for the RBs that need to use the SeNB resources as the alternate forked bearer. The standby DTCH is connected to the standby RLC entity and the MAC entity on the MCG, that is, the standby RLC entity sends data to the MAC entity on the MCG through the standby DTCH, and the standby RLC entity receives the data sent by the MAC entity on the MCG through the standby DTCH. Here, the standby RLC entity sends data to the MAC entity on the MCG through the standby DTCH, that is, the standby RLC entity sends data to the standby DTCH, and the MAC entity on the MCG receives the data from the standby DTCH. Similarly, the standby RLC entity passes the standby DTCH. Receiving data sent by the MAC entity on the MCG means that the MAC entity on the MCG sends data to the standby DTCH, and the standby RLC entity receives the data from the standby DTCH. Here, the data is sent to each other (or called a transfer) between the standby RLC entity and the MAC entity on the MCG through the standby DTCH. In actual implementation, the data may be used by using different memory pointers for data transmitted through different DTCHs, for example, by using data. When the standby DTCH1 is sent from the standby RLC entity 1 to which the standby DTCH1 is connected to the MAC entity, the pointer 1 used by the standby DTCH1 is sent by the standby RLC entity 1 to the MAC entity, and the MAC entity accesses the pointer 1 according to the received pointer 1 Data, that is to say, in actual implementation, the data is sent (or called transfer) between the standby RLC entity and the MAC entity on the MCG through the standby DTCH. It is not necessary to actually move the actual data. The storage location in the storage space.

When the alternate data transmission path is a standby fork carrier:

The alternate fork bearer on the MCG uses the security configuration of the MCG, and the standby RLC entity connects with the PDCP entity established on the MCG by the RB that needs to use the SeNB resource; or

The alternate fork bearer on the MCG uses the security configuration of the SCG, and the standby RLC entity connects with the PDCP entity established on the source SCG (S-SCG) in the SCG, ie, the SeNB change process, the RB that needs to use the SeNB resource.

When the alternate data transmission path is a standby forked logical channel,

At least one alternate logical dedicated traffic channel (DTCH) may be established on the MCG for RBs that need to use SeNB resources. The alternate DTCH connects to the RLC entity that has been established on the MCG for the RBs that need to use the SeNB resources and the MAC entity on the MCG.

In this step, when establishing an RB that needs to use the SeNB resource, the standby bifurcation data transmission path may be established for the RB; or

It is also possible to establish an alternate data transmission path for an already established RB that needs to use the SeNB resource when the SeNB changes.

In the embodiment of the present invention, the MCG is located on the MeNB, and the physical characteristics of the MeNB may be a macro eNB or an LPN. When the MeNB is a macro eNB, each cell in the MCG is a macro cell. When the MeNB is an LPN, each cell in the MCG is a small cell.

Step 501: In the SeNB change process, the data is transmitted by using an alternate data transmission path, where the transmitted data includes at least data that has been distributed to the RLC entity of the source SCG before the SeNB changes but does not complete the transmission at the source SCG.

The SeNB change process in this step includes:

The MeNB to which the MCG belongs may request the target SeNB after the SeNB changes to allocate resources and receive a positive reply of the target SeNB response; or

The MeNB may also receive the RLC entity from the source SeNB that has been distributed to the source SeNB before the SeNB changes but does not complete the transmitted data at the source SeNB; or

The UE may also receive the notification message sent by the MeNB, where the notification message is an RRC layer message, such as an RRC connection reconfiguration message, or a MAC layer message.

The use of the alternate data transmission path to transmit data in this step includes: when the alternate data transmission path is a standby forked bearer, using at least one standby RLC entity established in step 500 for the RB that needs to use the SeNB resource and at least one standby DTCH One of the alternate RLC entities and one alternate DTCH to transmit data.

When the alternate data transmission path is a standby forked logical channel, use one of the at least one standby DTCH established in step 500 for the RB that needs to use the SeNB resource and the RLC entity that has been established for the RB that needs to use the SeNB resource. transfer data.

The data transmitted in this step, that is, the data that has been distributed to the RLC entity of the source SCG before the SeNB changes but not completed at the source SCG, when the backup data transmission path is the standby fork bearer, includes:

For the case where the alternate forked bearer on the MCG uses the security configuration of the MCG, and the backup RLC entity is connected to the PDCP entity established on the MCG by the RB that needs to use the SeNB resource, the data transmitted in this step includes: distributed by the PDCP entity of the MCG. a PDCP packet data packet (PDU, Packet Data Unit) to the RLC entity of the source SCG but not completed at the source SCG; or

For the case where the standby forked bearer on the MCG uses the security configuration of the SCG, and the standby RLC entity is connected to the PDCP entity established on the source SCG by the RB that needs to use the SeNB resource, the data transmitted in this step includes: the source SeNB from the core network The downlink data received but not completed by the source SeNB is processed by the PDCP entity established on the source SeNB by the RB that needs to use the SeNB resource to process the generated PDCP PDU.

Optionally, in the case that the standby forked bearer on the MCG uses the security configuration of the MCG, and the backup RLC entity is connected to the PDCP entity established on the MCG by the RB that needs to use the SeNB resource, the data transmitted in this step further includes: The PDCP PDU delivered by the PDCP entity of the MCG except the PDCP PDU that is distributed by the PDCP entity of the MCG to the RLC entity of the source SCG but does not complete the transmission at the source SCG.

The data transmitted in this step, that is, the data that has been distributed to the RLC entity of the source SCG before the SeNB changes but not completed at the source SCG, and the transmission in this step when the alternate data transmission path is the alternate forked logical channel The data includes:

Distributed by the PDCP entity of the MCG to the RLC entity of the source SCG but not completed at the source SCG The PDCP PDU that was lost.

Optionally, further comprising

A PDCP PDU issued by the PDCP entity of the MCG, except for the PDCP entity of the MCG that is distributed to the RLC entity of the source SCG but not the PDCP PDU that completes the transmission at the source SCG.

In the embodiment of the present invention, through the establishment of the alternate data transmission path, the data is transmitted by using the alternate data transmission path during the change of the SeNB, thereby ensuring the continuity of data transmission during the change of the SeNB, realizing smooth transmission of data, and improving user data transmission. Rate, which enhances the user experience.

The method of the embodiment of the present invention may further include:

Step 502: Stop using the alternate data transmission path to transmit data.

For the case where the alternate data transmission path is a standby forked bearer and the standby forked bearer on the MCG uses the security configuration of the MCG, the standby RLC entity is connected with the PDCP entity established on the MCG by the RB that needs to use the SeNB resource, or for the standby data transmission In the case where the path is a standby forked logical channel, this step may include:

After successfully accessing the target SeNB, the UE notifies the MeNB that the UE stops using the alternate data transmission path to transmit data, and after receiving the notification, the MeNB stops using the alternate data transmission path to transmit data; or

After the UE successfully accesses the target SeNB and stops using the alternate data transmission path to transmit data, the target SeNB sends a notification that the UE has successfully accessed the MeNB, and the MeNB stops using the alternate data transmission path to transmit data after receiving the notification; or

After the MeNB sends the SeNB change notification to the UE for a predetermined period of time T, the data transmission is stopped using the alternate data transmission path, and the UE stops using the alternate data transmission path to transmit data after receiving the SeNB change notification sent by the MeNB for a preset duration T.

The UE successfully accesses the target SeNB, including: the UE successfully accesses the random access on the target SeNB; or the UE receives the SeNB change notification sent by the MeNB, and completes device-related module adjustment and configuration.

For the case where the alternate data transmission path is a standby forked bearer and the standby splitting bearer on the MCG uses the security configuration of the SCG, and the standby RLC entity is connected to the PDCP entity established on the SCG by the RB that needs to use the SeNB resource, the step may include:

When the downlink data received by the source SeNB from the core network but not completed by the source SeNB is transmitted on the standby data transmission path, that is, the standby forked bearer, the use of the alternate data transmission path is stopped. The alternate fork carries the transmitted data.

After the downlink data received by the source SeNB from the core network but not transmitted by the source SeNB is transmitted on the backup data transmission path, that is, the standby forked bearer, the step further includes: the standby RLC entity and the RB that needs to use the SeNB resource. The PDCP entity connection established on the T-SCG uses the security configuration of the target SCG.

The embodiment of the invention further provides a computer readable storage medium storing computer executable instructions for performing the data transmission method of any of the above.

The technical solution for implementing data transmission proposed by the present application is described below in conjunction with the embodiments. Unless otherwise stated, the steps in the following embodiments of the present invention are described in the case where the alternate data transmission path is a standby fork bearing.

In the first embodiment and the second embodiment, it is assumed that there is a sufficiently large X2 interface between the MeNB and the SeNB. Therefore, a forked bearer can be established between the MeNB and the SeNB, and the S1-U interface is terminated on the MeNB, all The downlink data sent by the SeNB is generated by the MeNB after the PD is generated by the MeNB, and then sent to the SeNB through the X2 interface with sufficient capacity. Similarly, all uplink data received on the SeNB is sufficiently large. After being sent to the MeNB, the X2 interface is processed by the PDCP layer of the MeNB and then sent to the core network. The alternate data transmission path in the first embodiment and the second embodiment may be a standby forked bearer or may be a standby split logical channel. In the embodiment, unless otherwise specified, the overall implementation flow is described in the case where the alternate data transmission path is the standby forked bearer, and in the case where the alternate data transmission path is the standby branching logical channel, the first embodiment diagram and the second embodiment The implementation process (Fig. 6, Fig. 10, Fig. 11) is also applicable, and will not be described again in the embodiment of the present invention.

FIG. 6 is a schematic flowchart of a first embodiment of implementing data transmission according to the present invention. In the first embodiment, a forked bearer is established for the split bearer while establishing a split bearer, where the concept of a forked bearer is established. This includes both the case where the forked bearer is directly established when the bearer is established, and the case where the MCG bearer or the SCG bearer is initially established, and then re-established as a forked bearer. As shown in Figure 6, it includes:

Step 600: Establish a forked bearer and a standby forked bearer of the forked bearer, that is, when the forked bearer is established, at least one standby forked bearer of the forked bearer is established on the MCG.

For example, as shown in FIG. 7 (a), FIG. 7 is a schematic diagram of a radio protocol architecture of a downlink split bearer and a standby fork bearer established by the base station side in the first embodiment of the present invention, as shown in FIG. 7 (a). ), there are two RBs: RB1 establishes the MCG bearer, and RB2 establishes the split bearer. The PDCP700 entity of the RB2 is located on the MeNB (or the MCG of the MeNB, or the MCG, which is described later in this document, and is directly expressed by the MeNB or the MCG for convenience of description), and the MeNB and the source SeNB (S-SeNB, Source SeNB) (or SLC on the S-SeNB, or on the SCG, as described later in this document, for the convenience of description, directly using the SeNB or SCG), respectively, two RLC entities, namely the RLC 710 on the MeNB and The forked bearer RLC 730 on the S-SeNB, and the DTCH 710-1 between the RLC 710 and the MAC 740 of the MeNB and the DTCH 730-1 between the RLC 730 and the MAC 750 of the S-SeNB. In addition, when establishing RB2, an alternate fork bearer is also established for the RB2 on the MeNB, that is, the standby RLC 720 established on the MeNB as shown in FIG. 7(a) and the RLC720 in FIG. 7(a). Alternate DTCH720-1 between the MAC740 and the MAC740. The alternate fork bearer uses the security configuration of the MCG, such as using the user plane security key (K _UPenc ) of the MCG, and the RLC 720 is connected to the PDCP 700 of the RB2 on the MeNB.

FIG. 7(b) is a schematic diagram of a radio protocol architecture of a UE side corresponding to the base station side radio protocol architecture diagram of FIG. 7(a) according to the first embodiment of the present invention, where the protocol architecture is consistent with the base station side, and the difference is only the base station side MeNB and The S-SeNB is located on the same physical device, and the MeNB and the S-SeNB are connected through the X2 interface. On the UE side, the protocol architecture corresponding to the MeNB side and the protocol architecture corresponding to the S-SeNB side are located on the same physical device. The two are connected by an internal hardware interface or a software interface or software code. All the protocol stacks in the following embodiments are described by way of example only on the base station side or the UE side unless otherwise specified.

If the alternate data transmission path established in this embodiment is not a standby forked bearer but a standby split logical channel, FIG. 7(c) is a downlink protocol bearer established by the base station side and a wireless protocol architecture of the standby forked logical channel. In the figure, there are two RBs: RB1 establishes the MCG bearer, and RB2 establishes the split bearer. Similarly, the PDCP 700 entity of RB2 is located on the MeNB, and two RLC entities are respectively established on the MeNB and the source SeNB, namely, the RLC 710X on the MeNB and the RLC 720X on the S-SeNB, and the MAC 730X between the RLC 710X and the MeNB. The DTCH 710X-1 and the RTCH 720X and the S-SeNB's MAC 740X are forked to carry the DTCH720X-1. In addition, when RB2 is established, a RB2 is also established on the MeNB. The alternate forked logical channel 710X-2, that is, the standby DTCH 710X-2 located between the RLC 710X and the MAC 730X established on the MeNB as shown in FIG. 7(c). Here, both the DTCH 710X-1 and the alternate DTCH 710X-2 are connected as the RLC entity 710X and the MAC entity 730X established by the RB2 on the MeNB, but the DTCH 710X-2 may be configured with a higher logical channel priority than the DTCH 710X-1. FIG. 7(d) is a schematic diagram of a UE side radio protocol architecture corresponding to the base station side radio protocol architecture diagram of FIG. 7(c) in the first embodiment of the present invention, and illustrates the description of FIG. 7(b).

As shown in step 500 of FIG. 5, the standby DTCH is connected to the RLC entity established on the MCG for the RB that needs to use the SeNB resource and the MAC entity on the MCG. In the first embodiment, the standby forked logical channel is in the establishment of the fork. The bearer RB2 is established at the same time. Therefore, as shown in FIG. 7(c), the standby DTCH 710X-2 is connected to the MCG and simultaneously is the RLC entity 710X established by the RB2 that needs to use the SeNB resource and the MAC entity 730X on the MCG, that is, the DTCH710X. -2 and the DTCH 710X-1 established on the MCG for split RB2 share the protocol entities at both ends of its channel.

Similarly, for the case of establishing an uplink split bearer, FIG. 8 is a schematic diagram of a wireless protocol architecture of an uplink split bearer and a standby split bearer established by the UE side in the first embodiment of the present invention; The protocol layer entities are all located in the same physical device, such as in the same UE. Similar to FIG. 7(a), similarly, there are two RBs in FIG. 8: RB1 establishes an MCG bearer, RB2 establishes a split bearer, and RB2's PDCP800 entity is located on the MCG (ie, the UE side establishes RB2 on the MeNB). The PDCP entity has established two RLC entities on the MCG and the SCG, namely, the RLC 810 on the MCG (that is, the split RLC entity established by the RB2 on the MeNB on the UE side) and the RLC 830 on the SCG (that is, the RB2 on the UE side) The split RLC entity established on the S-SeNB, and the DTCH810-1 between the RLC 810 and the MAC 840 of the MCG, and the DTCH 830-1 between the RLC 830 and the MAC 850 of the SCG. In addition, when establishing RB2, an alternate fork bearer is also established for RB2 on the MCG, that is, the standby RLC entity 820 established on the MCG as shown in FIG. 8 and the standby DTCH820-1 between the RLC 820 and the MAC 840 ( That is, the UE side is a standby RLC entity and a standby DTCH established by the RB2 on the MeNB. The alternate fork bearer uses the security configuration of the MCG, such as the user plane security key (K _UPenc ) of the MCG, and the RLC 820 is connected to the PDCP 800 of the RB2 on the MCG. When establishing the RLC 820 and the standby DTCH between the RLC 820 and the MAC 840, the relevant parameters may be configured as the same parameters as the RLC 830 on the SCG and the DTCH between the RLC 830 and the MAC 850, or may be configured as different parameters, such as standby. DTCH configures higher logical channel priorities and the like.

As an example, a downlink forked bearer may be established, and multiple standby fork bearers may be established for the downlink split bearer. FIG. 9 is a schematic diagram of a radio protocol architecture of a downlink split bearer and two standby fork bearers established according to an embodiment of the present invention. As shown in FIG. 9 , when RB2 is established, two standby sub-nodes are also established for the RB2 on the MeNB. The fork carries, as shown in FIG. 9, the standby RLC 920 established on the MeNB, the standby RLC 930, and the standby DTCH 920-1 between the RLC 920 and the MAC 950, and the standby DTCH 930-1 between the RLC 930 and the MAC 950.

Step 601: When the MeNB determines that the SeNB needs to be initiated, the MeNB sends an SeNB Addition Request (SeNB Addition Request) to the target SeNB (T-SeNB, Target SeNB).

The SeNB adds a request for the MeNB to request the T-SeNB to allocate resources, that is, request the T-SeNB to allocate resources for migrating the split bearer of the RB2 on the S-SeNB to the T-SeNB.

Step 602: The T-SeNB sends an SeNB Addition Request Acknowledge to the MeNB.

Step 603: Transfer data using the alternate fork bearer. For downlink transmission, the MeNB uses the alternate split bearer to transmit data, and the transmitted data includes at least the RLC that the MeNB has distributed to the S-SeNB before the SeNB changes, such as the RLC 730 in FIG. 7(a) but does not complete the transmission at the S-SeNB. The data. For uplink transmission, the UE uses the alternate forked bearer to transmit data, and the transmitted data includes at least data that the PDCP entity of the MCG has distributed to the RLC entity of the SCG, such as the RLC 830 in FIG. 8 but not completed at the SCG, before the SeNB changes.

In the first embodiment, after the MeNB distributes the data to the S-SeNB, the distributed data is not deleted from the cache of the MeNB. Therefore, in this step, the data can be directly transmitted using the alternate fork bearer.

In another case, if the MeNB deletes the data from the cache of the MeNB after distributing the data to the S-SeNB, FIG. 10 is a schematic flowchart of another embodiment of implementing data transmission according to the present invention, then, as shown in FIG. 10 As shown, after receiving the SeNB addition confirmation from the T-SeNB (step 1003), the MeNB initiates an SeNB deletion request to the S-SeNB (step 1004), in which the MeNB provides data to the S-SeNB. The forwarded address, after receiving the data preamble address provided by the MeNB, the S-SeNB performs data pre-transmission in step 1005, that is, sends the data to the MeNB. Before the SeNB changes the data that the MeNB has distributed to the RLC entity of the S-SeNB but does not complete the transmission at the S-SeNB, the MeNB uses the alternate forked bearer to transmit the data forwarded by the S-SeNB (step 1006). The other steps of FIG. 10 are consistent with FIG. 6, and FIG. 10 will not be described in detail later.

For FIG. 7(a), in FIG. 8, only one spare fork bearing is established, and the standby fork is used to carry the data. For the case where two or more standby forked bearers are established when establishing RB2 in FIG. 9, the MeNB selects at least one of the alternate split bearer transmission data, wherein the MeNB can comprehensively consider the data that needs to be transmitted on the standby forked bearer. Business characteristics, logical channel priority, etc.

In the first embodiment, taking FIG. 7(a) as an example, it is assumed that the PDCP 700 of the MeNB has already distributed PDCP PDUs of SN=2, 3, 4, 6, 7, 8, 10 to the S-SeNB before the SeNB changes. , wherein the data packet of SN=2, 3, 4 is transmitted in the S-SeNB and receives successful reception feedback from the UE, and the data packet of SN=6 is sent to the UE through the radio frequency of the S-SeNB, but is not received. Successful reception feedback from the UE, data of SN=7, 8, 10 has not been sent via the SeNB. Then, in this step, the standby fork bearer on the MeNB is used to transmit at least the data packets of SN=6, 7, 8, and 10.

If the SeNB changes successfully, that is, before the UE successfully accesses the T-SeNB, the PDCP PDU that is distributed by the PDCP entity of the MCG to the RLC entity of the source SCG but not transmitted on the source SCG is transmitted on the standby forked bearer, and may also be The other PDCP PDUs delivered by the PDCP entity that transmits the MCG are carried by the alternate branching, such as the PDCP PDU processed by the MCG PDCP after the new data of the core network is changed in the SeNB.

In this embodiment, the uplink uses the alternate split bearer to transmit data, that is, the case where the UE sends data to the base station by using the alternate split bearer transmission data, and is executed after the UE receives the notification message sent by the MeNB, and the notification message is an RRC layer message (such as subsequent The RRC connection reconfiguration message of step 605) or the MAC layer message.

The above is a technical solution for transmitting data using the alternate data transmission path in the case where the alternate data transmission path is the standby branching bearer. Similarly, all the above descriptions are equally applicable when the alternate data transmission path is the alternate branching logical channel. Taking FIG. 7(c) as an example, the only difference is that when the data is transmitted using the alternate forked logical channel, the alternate forked logical channel is connected to the RLC 710X-1 and the MAC 730X-1 established by the RB2 on the MeNB, and the transmission is between the two. The data. And the same, for Figure 7(c) shows the case where only one alternate forked logical channel is established, and the data is transmitted by the alternate forked logical channel, and when two or more spare forked logical channels are established for RB2, the MeNB selects At least one alternate forked logical channel transmits data.

Step 604: The MeNB sends an SeNB Release Request to the S-SeNB.

Step 605: The MeNB sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) to the UE to notify the UE to change the split bearer of the RB2 on the S-SeNB to the T-SeNB.

Step 606: The UE feeds back the RRC Connection Reconfiguration Complete to the MeNB.

Step 607: The MeNB sends an SeNB Reconfiguration Complete to the T-SeNB.

Step 608: If a random access operation needs to be performed on the T-SeNB, the UE performs random access on the T-SeNB. This step is an optional step.

Step 609: The MeNB and/or the UE stop using the alternate fork bearer to transmit data.

In this step, after the UE successfully accesses the T-SeNB, the SeNB changes successfully, and the MeNB and/or the UE stops using the alternate split bearer to transmit data. The UE may notify the MeNB after successfully accessing the T-SeNB, and the UE stops using the standby point. The bearer carries the transmission data, and the MeNB stops using the alternate forked bearer to transmit data after receiving the notification; or, after the UE successfully accesses the T-SeNB, stops using the alternate split bearer to transmit data, and the T-SeNB notifies the MeNB that the UE successfully accesses, the MeNB After receiving the notification, the use of the alternate branching bearer to transmit data is stopped; or the MeNB sends the RRC connection reconfiguration message to the UE for a preset period of time T, and then stops using the alternate forked bearer transmission data, and the UE receives the RRC connection reconfiguration sent by the MeNB. After a preset period of time T, the message stops using the alternate fork carrier to transmit data.

Step 610: The MeNB sends a delete UE context to the S-SeNB.

FIG. 11 is a schematic flowchart of a second embodiment of implementing data transmission according to the present invention. In the second embodiment, a backup fork bearer is established for a forked bearer when the SeNB changes, as shown in FIG.

Step 1101: Establish a forked bearer.

A bifurcation bearer is established on the MeNB and the S-SeNB. FIG. 12(a) is a schematic diagram of a radio protocol architecture in which the SeNB changes the pre-downlink bifurcation bearer according to the second embodiment of the present invention. As shown in FIG. 12(a), the MeNB and the UE are configured. Two RBs are established: RB1 and RB2, where RB1 is an MCG bearer and RB2 is a split bearer.

Steps 1102 to 1103: The actual implementation is completely consistent with steps 601 to 602 in the first embodiment, and details are not described herein again.

Step 1104: The actual implementation is completely consistent with step 604 in the first embodiment, and details are not described herein again.

Step 1105: The MeNB sends an RRC connection reconfiguration to the UE. In the second embodiment, the RRC connection reconfiguration message is used to notify the UE to change the split bearer of the RB2 on the S-SeNB to the T-SeNB, and the other. Aspects are used to establish a forked bearer for a forked bearer on the MCG.

FIG. 12(b) is a schematic diagram of a radio protocol architecture of a downlink split bearer in a SeNB change process according to a second embodiment of the present invention. As shown in FIG. 12(b), in this step, the MeNB and the UE establish RB2 on the MeNB side. An alternate forked bearer, that is, the standby RLC 1220 established on the MeNB shown in FIG. 12(b) and the standby DTCH between the RLC 1220 and the MAC 1240 not shown in FIG. 12(b), the standby split bearer is used on the MeNB. MCG security configuration. Figure 12 (b) is a protocol architecture diagram of the base station side as an example. The protocol architecture diagram on the UE side is the same as that on the base station side. The only difference is that the base station side MeNB and the S-SeNB are located on different physical devices, and the MeNB and the S- The SeNBs are connected through the X2 interface, and on the UE side, the protocol architecture corresponding to the MeNB side and the protocol architecture corresponding to the S-SeNB side are located on the same physical device, and the internal hardware interface or software interface or software is used. Code connection.

In the SeNB change process, for example, in this step, according to the UE capability, the signal quality of the radio link between the UE and the S-SeNB, and the policy of the base station, the MeNB may notify the UE to directly delete the split bearer on the S-SeNB, that is, delete. The RLC 1230 and the DTCH between the RLC 1230 and the MAC 1250 may also continue to reserve the split bearer on the S-SeNB. For example, when the UE capability does not support simultaneous communication with the MeNB, the S-SeNB, and the T-SeNB, or when the quality of the radio link signal between the UE and the S-SeNB is not good enough, or when the base station policy needs to be deleted, the S is directly deleted. - split bearer on the SeNB; another example: when the UE capability supports simultaneous communication with the MeNB, the S-SeNB, and the T-SeNB, and the quality of the radio link signal between the UE and the S-SeNB is good enough, and the base station policy The split bearer on the S-SeNB can be kept as needed. For the case of reservation, in the SeNB change process, in addition to using the alternate bearer to transmit data, the data may continue to be transmitted on the split bearer of the S-SeNB. The first embodiment is equally applicable to such processing.

The above description is based on the alternate data transmission path as the standby forked bearer. When the standby data transmission path is the standby forked logical channel, the alternate forked logical channel established for the split RB2 on the MCG is connected to the MCG already in step 1101. The RLC entity and MAC entity established for split RB2.

Step 1106: Transfer data using the alternate fork bearer. For downlink transmission, the MeNB uses the alternate forked bearer to transmit data, and the transmitted data includes at least the RLC entity that the MeNB has distributed to the S-SeNB before the SeNB changes, as shown in the RLC 1230 in FIG. 12(b) but not completed at the S-SeNB. The data transferred. For uplink transmission, the UE uses the alternate fork bearer to transmit data, and the transmitted data includes at least data that the PDCP entity of the MCG has distributed to the RLC entity of the SCG before the SeNB changes but does not complete the transmission at the SCG.

The actual implementation of this step is consistent with step 603 in the first embodiment, and details are not described herein again.

Steps 1107 to 1111: The actual implementation is consistent with steps 606 to 610 in the first embodiment, and details are not described herein again.

In the second embodiment, after the UE successfully accesses the T-SeNB, the SeNB changes successfully. After the SeNB changes successfully, the protocol architecture is as shown in FIG. 12(c), the standby forked bearer is deleted, and the RB2 can be enabled on the T-SeNB. Split bearer. Deleting the alternate forked bearer may be: the UE notifies the MeNB after successfully accessing the T-SeNB, the UE deletes the local standby split bearer, and the MeNB deletes the local standby split bearer after receiving the notification; or the UE successfully accesses the T-SeNB After the local backup fork bearer is deleted, the T-SeNB informs the MeNB that the UE successfully accesses, and the MeNB deletes the local standby split bearer after receiving the notification; or, the MeNB sends the RRC connection reconfiguration message to the UE after a preset duration T. The local standby fork bearer is deleted, and the UE deletes the local standby fork bearer after receiving the RRC connection reconfiguration message sent by the MeNB for a preset duration T.

In the third embodiment and the fourth embodiment, it is assumed that the capacity of the X2 interface between the MeNB and the SeNB is not large enough. If all data transmitted on the SeNB needs to be sent by the MeNB to the SeNB through the X2 interface, then on the X2 interface. Can't carry such huge amounts of data, so it can't be in MeNB A forked bearer is established between the SeNB and the SeNB, and the MeNB and the SeNB have an independent S1-U interface with the core network. However, the capacity between the MeNB and the SeNB is sufficient to carry downlink data that the source SeNB sent by the source SeNB to the MeNB from the core network but does not complete the transmission at the source SeNB during the SeNB change process. The alternate data transmission path in the third embodiment and the fourth embodiment is a standby fork carrier.

FIG. 13 is a schematic flowchart of a third embodiment of implementing data transmission according to the present invention. In the third embodiment, it is assumed that a bearer is established on the SCG and a standby fork bearer is established for the bearer on the MCG. This includes the case where the bearer is directly established on the SCG, and the case where the bearer originally established on the MCG is reconstructed onto the SCG. As shown in Figure 13, the actual implementation includes:

Step 1301: Establish a bearer on the SCG, and establish a standby fork bearer for the bearer on the MCG.

The following row bearer is taken as an example. FIG. 14( a ) is a schematic diagram of a radio protocol architecture of a downlink split bearer and a standby fork bearer established by the base station side according to the third embodiment of the present invention, as shown in FIG. 14( a ). It is assumed that an RB3 is established for the UE on the S-SeNB, that is, the PDCP entity of the RB3, the RLC entity, and the DTCH between the RLC and the MAC are established on the S-SeNB. At the same time, when RB3 is established, a standby fork bearer is also established for the RB3 on the MeNB, such as the standby RLC 1420 established on the MeNB and the standby DTCH between the RLC 1420 and the MeNB MAC as shown in FIG. 14(a). The alternate fork bearer uses the security configuration of the SCG, such as using the user plane security key (K _UPenc ) of the SCG, and the RLC 1420 is connected to the PDCP 1410 of the RB3 on the SeNB. 14(b) is a diagram showing a wireless protocol architecture of an uplink split bearer and a standby fork bearer established by the UE side in the third embodiment of the present invention, and the protocol architecture thereof is consistent with the base station side shown in FIG. 14(a). The difference is only that the base station side MeNB and the S-SeNB are located on different physical devices, and the MeNB and the S-SeNB are connected through the X2 interface, and the UE side corresponds to the protocol architecture of the MeNB side and the protocol corresponding to the S-SeNB side. The architecture is on the same physical device, and the two are connected by internal hardware interfaces or software interfaces or software code.

As described in the step 600 of the first embodiment, two or more alternate fork carriers may be established for the RB3, and the actual implementation is not described herein again. In the third embodiment, only a case of establishing a standby fork bearing is taken as an example for detailed description.

Steps 1302 to 1303: Actual implementation and steps 601 to 602 in the first embodiment It is completely consistent and will not be repeated here.

Similarly, in this embodiment, the uplink uses the alternate split bearer to transmit data, that is, the case where the UE sends data to the base station by using the alternate split bearer transmission data, and is executed after the UE receives the notification message sent by the MeNB, and the notification message is an RRC layer message. For example, the RRC connection reconfiguration message of the subsequent step 605) or the MAC layer message.

Step 1304: The actual implementation is consistent with step 1004 in the first embodiment, and details are not described herein again.

Step 1305: The S-SeNB sends the PDCP PDU generated by the PDCP 1410 to the RLC 1420 of the MeNB, which is received by the S-SeNB from the downlink network but not transmitted by the S-SeNB.

In the third embodiment, in the SeNB change process, the RB3 remains in the PDCP 1410 of the S-SeNB until step 1311. Similarly, the PDCP entity of the RB3 on the UE side SCG remains used until step 1311. The RLC of the RB3 on the S-SCG and the DTCH between the MAC and the MAC are determined according to the UE capability, the signal quality of the radio link between the UE and the S-SeNB, and the policy of the base station, whether to continue to use, that is, whether The data is transmitted on the source SCG during the change of the SeNB. The method for determining is as described in step 1105 in the second embodiment, and details are not described herein again.

Step 1306: Transfer data using the alternate fork bearer.

The MeNB sends the PDCP PDU sent by the S-SeNB to the MeNB in the step 1305, and the UE uses the alternate forked bearer to receive the data. The received data is processed by the MCG backup fork carrier RLC 1430 and then sent to the PDCP 1440 of the source SCG. It is decrypted by the security configuration of the source SCG and sent to the protocol layer above the PDCP 1440, such as the application layer.

Steps 1307 to 1310: The actual implementation is completely consistent with steps 605 to 608 in the first embodiment, and details are not described herein again.

Step 1311: Stop using the alternate fork bearer to transmit data.

After the downlink data received by the S-SeNB from the core network but not completed by the S-SeNB is transmitted on the standby forked bearer, the use of the alternate split bearer to transmit data is stopped. Thereafter, the RLC entity of the RB3 on the standby forked bearer on the MCG is connected with the PDCP entity established by the RB3 on the target SCG (T-SCG), using the security configuration of the T-SCG.

Step 1312: The actual implementation is completely consistent with step 610 in the first embodiment, and details are not described herein again.

FIG. 15 is a schematic flowchart of a fourth embodiment of the present invention. In the fourth embodiment, it is assumed that a standby forked bearer is established for a bearer of a source SCG when the SeNB changes. As shown in FIG. 15, the actual implementation includes:

Step 1501: Establish a bearer RB3, that is, an SCG bearer, on the SCG (here, the SCG of the S-SeNB). In this embodiment, the RB3 uses only the resources of the S-SeNB, and all the protocol entities are established on the SCG, as shown in FIG. 16(a). FIG. 16(a) shows the SeNB changes the pre-downlink SCG bearer in the fourth embodiment of the present invention. Schematic diagram of the wireless protocol architecture.

Steps 1502 to 1504: The actual implementation is completely consistent with steps 1302 to 1304, and details are not described herein again.

Step 1505: The S-SeNB sends the PDCP PDU generated by the S-SeNB from the core network but not transmitted by the S-SeNB to the MeNB after the PDCP processing of the S-SeNB.

In the fourth embodiment, in the SeNB change process, the PDCP entity of the RB3 in the S-SeNB remains reserved until step 1511. Similarly, the PDCP entity of the RB3 on the SCG of the UE side remains used until step 1511. The RLC of the RB3 on the S-SCG and the DTCH between the MAC and the MAC are determined according to the UE capability, the signal quality of the radio link between the UE and the S-SeNB, and the policy of the base station, whether to continue to use, that is, whether The data is transmitted on the source SCG during the change of the SeNB. The method for determining is as described in step 1105 in the second embodiment, and details are not described herein again.

Step 1506: The MeNB sends an RRC connection reconfiguration to the UE. In the fourth embodiment, the RRC connection reconfiguration message is used to notify the UE to change the RB3 from the S-SeNB to the T-SeNB, and Establish an alternate fork bearer for RB3 on the MCG.

16(b) is a schematic diagram of a radio protocol architecture of a downlink SCG bearer in a process of changing a SeNB according to a fourth embodiment of the present invention. As shown in FIG. 16(b), in this step, the MeNB and the UE are established for the RB3 on the MeNB side. An alternate fork bearer, that is, the standby RLC 1620 established on the MeNB shown in FIG. 16(b) and the standby DTCH between the RLC 1620 and the MAC 1630 not shown in FIG. 16(b), the standby fork bearer being used on the S-SeNB For the security configuration of the SCG, the RLC1620 is connected to the PDCP1610 of the SCG.

Step 1507: Transfer data using the alternate fork bearer. The actual implementation is completely consistent with step 1306 in the third embodiment, and details are not described herein again.

Steps 1508 to 1510: The actual implementation is completely consistent with steps 1308 to 1310 in the third embodiment, and details are not described herein again.

Step 1511: After the downlink data received by the S-SeNB from the core network but not completed by the S-SeNB is transmitted on the standby forked bearer, the use of the alternate split bearer to transmit data is stopped. FIG. 16(b) is a schematic diagram of a radio protocol architecture of a downlink SCG bearer in a SeNB change process according to a fourth embodiment of the present invention. As shown in FIG. 16(c), the MeNB and the UE delete the standby fork bearer on the MCG, and the RB3 only The resources of the T-SeNB are used.

Step 1512: The actual implementation is completely consistent with step 1312 in the third embodiment, and details are not described herein again.

Corresponding to the method for implementing data transmission according to the embodiment of the present invention, an apparatus for implementing data transmission is also provided. The apparatus of the embodiment of the present invention may be used as an independent entity, or may be set in a base station, for example, set on the MeNB, or set in the In the UE, that is, the device configured on the base station side and the UE side is functionally corresponding. When one side is used as the transmitting end and the other side is used as the receiving end, for example, the base station transmits the downlink data, which is the transmitting end, and the base station receives the uplink. The data is the receiving end. Correspondingly, the UE receives the downlink data as the receiving end, and the UE sends the uplink data as the transmitting end.

FIG. 17 is a schematic structural diagram of a device for implementing data transmission according to an embodiment of the present invention. As shown in FIG. 17, at least an establishing module 171, a data transmission module 172, where:

The establishing module 171 is configured to: establish an alternate data transmission path on the MCG for the RB that needs to use the SeNB resource; and include establishing at least one standby RLC entity and at least one standby DTCH for the RB that needs to use the SeNB resource.

The data transmission module 172 is configured to: during the SeNB change process, transmit data using an alternate data transmission path, where the transmitted data includes at least an RLC entity that has been distributed to the source SCG before the SeNB changes but does not complete the transmission at the source SCG. data.

The alternate data transmission path is: a standby forked bearer of an RB that needs to use the SeNB resource, or a standby forked logical channel of the RB that needs to use the SeNB resource.

Optionally, the establishing module 171 is configured to: when establishing an RB that needs to use the SeNB resource, establish an alternate data transmission path for the RB; or, when the SeNB changes, establish standby data for the RB that needs to be used to use the SeNB resource. Transmission path.

Wherein, when the standby data transmission path is a standby fork bearing, the standby established on the MCG For the forked bearer, using the security configuration of the MCG, the standby RLC entity is connected to the PDCP entity established on the MCG by the RB that needs to use the SeNB resource;

Alternatively, the alternate fork bearer on the MCG uses the security configuration of the SCG, and the standby RLC entity is connected to the PDCP entity established on the SCG by the RB that needs to use the SeNB resource.

Wherein, when the alternate data transmission path is a standby forked logical channel,

When the apparatus of the embodiment of the present invention is separately disposed in the network side or the MeNB, the data transmission module 172 is configured to: after the MeNB to which the MCG belongs, request the target SeNB to allocate resources after receiving the SeNB change, and receive a positive reply from the target SeNB response, use the backup. The data transmission path transmits data; or, the MeNB receives data from the source SeNB that has been distributed to the RLC entity of the source SeNB before the SeNB changes but does not complete the transmission at the source SeNB, and uses the alternate data transmission path to transmit data.

When the apparatus of the embodiment of the present invention is separately set in the user side or the UE, the data transmission module 172 is configured to: after receiving the notification message sent by the MeNB, the UE uses the alternate data transmission path to transmit data.

Optionally, when the alternate data transmission path is a standby forked bearer, the data transmission module 172 is configured to: use at least one standby RLC entity established by the RB of the SeNB resource and one of the at least one standby DTCH and one standby DTCH transmits data;

When the alternate data transmission path is a standby forked logical channel, the data transmission module 172 is configured to transmit data using one of the at least one standby DTCH and the RLC entity that has been established for the RB that needs to use the SeNB resource.

among them,

When the alternate data transmission path is a standby forked bearer, the data transmission module 172 during the SeNB change process, the data transmitted using the alternate forked bearer includes at least the RLC entity that has been distributed to the source SCG before the SeNB changes but is not at the source SCG. Complete the transferred data, including:

For the standby forked bearer established by the establishing module 171 on the MCG, the security configuration of the MCG is used, and the PDCP of the standby RLC entity and the RB that needs to use the SeNB resource is established on the MCG. In the case of a body connection, the data transmitted by the data transmission module 172 includes: a PDCP PDU distributed by the PDCP entity of the MCG to the RLC entity of the source SCG but not completed at the source SCG; optionally, the data transmitted by the data transmission module 172 can also be And including: PDCP PDUs issued by the PDCP entity of the MCG except the PDCP PDUs distributed by the PDG entity of the MCG to the RLC entity of the source SCG but not completed by the source SCG. or,

For the standby forked bearer established by the establishing module 171 on the MCG to use the security configuration of the SCG, and the standby RLC entity is connected to the PDCP entity established on the SCG by the RB that needs to use the SeNB resource, the data transmitted by the data transmission module 172 includes: the source The downlink data received by the SeNB from the core network but not completed by the source SeNB is processed by the PDCP entity established on the source SeNB by the RB that needs to use the SeNB resource to process the generated PDCP PDU.

When the alternate data transmission path is the alternate forked logical channel, the data transmitted by the data transmission module 172 includes: a PDCP PDU distributed by the PDCP entity of the MCG to the RLC entity of the source SCG but not completed at the source SCG. Optionally,

The data transmitted by the data transmission module 172 further includes: PDCP PDUs issued by the PDCP entity of the MCG, except for the PDCP PDUs distributed by the PDCP entity of the MCG to the RLC entity of the source SCG but not completed by the source SCG.

For the standby fork bearer established by the establishing module 171 on the MCG, the security configuration of the MCG is used, the established standby RLC entity is connected with the PDCP entity established on the MCG by the RB that needs to use the SeNB resource, or the standby data transmission path is the standby branch. For the case of a forked logical channel,

When the apparatus of the embodiment of the present invention is separately configured in the user side or the UE, the data transmission module 172 is further configured to: after the UE successfully accesses the target SeNB, or after receiving the SeNB change notification sent by the MeNB for a preset duration T, the UE stops. Transfer data using an alternate data transmission path;

The data transmission module 172 is further configured to: when the MeNB receives the notification that the UE from the UE or the target SeNB successfully accesses the target SeNB, stops using the backup data transmission when the apparatus of the embodiment of the present invention is separately set in the network side or the MeNB. The channel transmits data.

For the standby forked bearer established by the establishing module 171 on the MCG, the security configuration of the SCG is used, and the established standby RLC entity is connected with the PDCP entity established on the SCG by the RB that needs to use the SeNB resource,

When the apparatus of the embodiment of the present invention is separately disposed on the network side or the MeNB, the data transmission module 172 is configured to stop using the backup data transmission after the transmission completes the downlink data received by the source SeNB but not completed by the source SeNB. The channel transmits data.

An embodiment of the present invention further provides a base station, including the apparatus of any of the foregoing.

An embodiment of the present invention further provides a UE, including the apparatus of any of the foregoing.

One of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described embodiments can be implemented using a computer program flow, which can be stored in a computer readable storage medium, such as on a corresponding hardware platform (eg, The system, device, device, device, etc. are executed, and when executed, include one or a combination of the steps of the method embodiments.

Alternatively, all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.

The devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.

When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

The above is only an alternative example of the present invention and is not intended to limit the scope of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application are intended to be included within the scope of the present application.

Industrial applicability

The technical solution provided by the embodiment of the present invention uses the alternate data transmission path to transmit data during the change process of the SeNB, ensures the continuity of data transmission during the SeNB change process, and realizes smooth transmission of data and improves the data transmission path. The user data transfer rate enhances the user experience.

Claims

A data transmission method includes:

Establishing an alternate data transmission path on the primary serving serving cell group MCG for the radio bearer RB that needs to use the secondary base station SeNB resource;

In the SeNB change process, the data is transmitted using the alternate data transmission path, wherein the transmitted data includes the radio link control RLC entity that has been distributed to the source secondary serving cell group S-SCG before the SeNB change but is not completed at the S-SCG. The data transferred.
The data transmission method according to claim 1, further comprising: establishing the RB that needs to use the SeNB resource;

The establishing an alternate data transmission path includes:

When the RB that needs to use the SeNB resource is established, the standby data transmission path is established for the RB; or

When the SeNB changes, the standby data transmission path is established for the RB that needs to use the SeNB resource that has been established.
The data transmission method according to claim 1 or 2, wherein the alternate data transmission path is a standby forked bearer of an RB that needs to use the SeNB resource, or a standby forked logical channel of the RB that needs to use the SeNB resource.
The data transmission method according to claim 1 or 2, wherein the standby data transmission path is a standby fork bearing;

The alternate fork bearer includes at least one alternate RLC entity and at least one alternate logical dedicated traffic channel DTCH.
The data transmission method according to claim 1, wherein the standby data transmission path is a standby fork bearing;

The standby fork bearer uses a security configuration of the MCG, and the standby forked bearer includes a standby RLC entity connected to a packet data control protocol PDCP entity established on the MCG by an RB that needs to use the SeNB resource; or

The alternate fork bearer uses a security configuration of the S-SCG, and the standby forked bearer includes a standby RLC entity and a PDCP established on the S-SCG by an RB that needs to use the SeNB resource. Entity connection.
The data transmission method according to claim 1 or 2, wherein the standby data transmission path is a standby forked logical channel;

The alternate forked logical channel includes: at least one standby DTCH established for the RB using the SeNB resource; wherein the standby DTCH connection is between the RLC entity established on the MCG for the RB requiring the use of the SeNB resource and the medium access control MAC entity on the MCG .
The data transmission method according to claim 1, wherein the SeNB change process comprises: after the MeNB to which the MCG belongs requests the target SeNB after the SeNB changes to allocate resources and receive a positive reply from the target SeNB response ;

Or, after the MeNB to which the MCG belongs receives the RLC entity from the source SeNB that has been distributed to the source SeNB before the SeNB changes but does not complete the transmission of the data at the source SeNB;

Or after the user terminal UE receives the notification message sent by the MeNB to which the MCG belongs.
The data transmission method according to claim 3, wherein said transmitting data using said alternate data transmission path comprises:

When the alternate data transmission path is a standby forked bearer, using at least one standby RLC entity and one of the at least one standby DTCH and one standby DTCH to transmit data;

When the alternate data transmission path is a standby forked logical channel, data is transmitted using one of the at least one standby DTCH and an RLC entity that has been established for the RB that needs to use the SeNB resource.
The data transmission method according to claim 5, wherein when the standby fork carrier uses a security configuration of the MCG, the standby RLC entity is connected to a PDCP entity established on the MCG by an RB that needs to use a SeNB resource. The transmitted data includes:

A PDCP packet data packet PDU that is distributed by the PDCP entity of the MCG to the RLC entity of the S-SCG but not completed at the S-SCG.
The data transmission method according to claim 9, wherein the transmitted data further comprises:

Distributed by the PDCP entity of the MCG to the PDCP entity of the MCG The RLC entity of the S-SCG but not other PDCP PDUs that complete the transmission of the PDCP PDU at the S-SCG.
The data transmission method according to claim 5, wherein when the standby fork bearer uses a security configuration of the S-SCG, the standby RLC entity establishes with the RB that needs to use the SeNB resource on the S-SCG When the PDCP entity is connected, the transmitted data includes:

The downlink data received by the source SeNB from the core network but not completed by the source SeNB is processed by the PDCP entity established by the RB that needs to use the SeNB resource on the source SeNB to process the generated PDCP PDU.
The data transmission method according to claim 6, wherein the transmitted data comprises a PDCP PDU distributed by a PDCP entity of the MCG to an RLC entity of a source SCG but not completed at a source SCG.
The data transmission method according to claim 12, wherein the transmitted data further comprises: an RLC entity delivered by the PDCP entity of the MCG but distributed by the PDCP entity of the MCG to the source SCG but not at the source The SCG completes other PDCP PDUs other than the transmitted PDCP PDU.
The data transmission method according to claim 1, further comprising: stopping transmission of data using said alternate data transmission path.
The data transmission method according to claim 14, wherein when the standby data transmission path is a standby forked bearer and a standby forked bearer on the MCG uses a security configuration of the MCG, the standby RLC entity needs to use the SeNB When the RB of the resource is connected to the PDCP entity established on the MCG, or when the alternate data transmission path is the alternate forked logical channel,

The stopping the use of the alternate fork carrier to transmit data includes:

After the UE successfully accesses the target SeNB after the SeNB changes, the UE notifies the MeNB to which the MCG belongs, and the UE stops using the alternate data transmission path to transmit data, and the MeNB to which the MCG belongs receives the notification and stops using the alternate data transmission path to transmit data; or,

After the UE successfully accesses the target SeNB after the change of the SeNB, the target SeNB stops transmitting data using the alternate data transmission path, and the target SeNB sends a notification that the UE has successfully accessed the MeNB to which the MCG belongs, and the MeNB to which the MCG belongs receives the notification. Stop using the alternate data transfer path to transfer data; or,

The MeNB to which the MCG belongs sends a SeNB change notification to the UE for a predetermined period of time T, and then stops using the alternate data transmission path to transmit data, and the UE stops using after receiving the SeNB change notification sent by the MeNB to which the MCG belongs for a preset duration T. The alternate data transmission path transmits data.
The data transmission method according to claim 14, wherein when the backup data transmission path is a backup fork carrier and a security configuration of the S-SCG, the standby RLC entity and the RB that needs to use the SeNB resource are in the When the PDCP entity established on the S-SCG is connected, the stopping the use of the alternate fork bearer to transmit data includes:

When the downlink data received by the source SeNB from the core network but not completed by the source SeNB is transmitted on the backup data transmission path, the use of the alternate data transmission path to stop data transmission is stopped.
The data transmission method according to claim 16, further comprising: connecting, by the standby RLC entity, a PDCP entity established on the target SCGT-SCG after the SeNB change with an RB that needs to use the SeNB resource, using the T-SCG Security configuration.
A data transmission device comprising:

Establishing a module, configured to: establish an alternate data transmission path on the MCG for the RB that needs to use the SeNB resource;

The data transmission module is configured to: during the SeNB change process, transmit data using an alternate data transmission path, where the transmitted data includes an RLC entity that has been distributed to the S-SCG before the SeNB changes but does not complete the transmission at the S-SCG. data.
The data transmission device according to claim 18, wherein the establishing module is configured to: establish an alternate data transmission path for the RB when establishing the RB that needs to use the SeNB resource; or, when the SeNB changes, An alternate data transmission path is established for an already established RB that needs to use SeNB resources.
The data transmission device according to claim 18 or 19, wherein the alternate data transmission path is a standby forked bearer of an RB that needs to use the SeNB resource, or a standby forked logical channel of the RB that needs to use the SeNB resource.
The data transmission device according to claim 18 or 19, wherein said alternate data transmission path is a standby fork bearing;

The alternate fork bearer includes at least one standby RLC entity and at least one standby DTCH.
The data transmission device according to claim 18, wherein said alternate data transmission path is a backup fork carrier;

The standby forked bearer uses a security configuration of the MCG, and the standby split-branch bearer includes a backup RLC entity that is connected to a PDCP entity established on the MCG by an RB that needs to use the SeNB resource; or

The standby fork bearer uses a security configuration of the S-SCG, and the standby forked bearer includes a backup RLC entity connected to a PDCP entity established on the S-SCG by an RB that needs to use the SeNB resource.
The data transmission method according to claim 18 or 19, wherein said standby data transmission path is a standby forked logical channel;

The alternate forked logical channel includes at least one standby DTCH established for the RB using the SeNB resource; wherein the alternate DTCH connection is between the RLC entity established on the MCG for the RB that needs to use the SeNB resource and the MAC entity on the MCG.
The data transmission device according to claim 18, wherein when the device is separately disposed on the network side or the MeNB, the data transmission module is configured to:

After the MeNB to which the MCG belongs requests the target SeNB after the SeNB changes to allocate resources and receives a positive reply from the target SeNB, and uses the alternate data transmission path to transmit data;

Alternatively, the MeNB to which the MCG belongs receives the data from the source SeNB that has been distributed to the RLC entity of the source SeNB before the SeNB changes but does not complete the transmission after the source SeNB completes the transmission, and uses the alternate data transmission path to transmit data.
The data transmission device according to claim 18, wherein the data transmission module is configured to: after the UE receives the notification message sent by the MeNB to which the MCG belongs, use the standby The data transmission path transmits data.
The data transmission apparatus according to claim 20, wherein, when said alternate data transmission path is a standby forked bearer, said data transmission module is configured to: use at least one standby RLC entity established for an RB requiring use of SeNB resources And transmitting data to one of the at least one standby DTCH and one of the standby DTCHs;

When the alternate data transmission path is a standby forked logical channel, the data transmission module is configured to: use one of the at least one standby DTCH and have already made The RLC entity established by the RB of the SeNB resource transmits data.
The data transmission apparatus according to claim 22, wherein the standby forked bearer established by the establishing module on the MCG uses a security configuration of the MCG, and the standby RLC entity and the PDCP established on the MCG by the RB that needs to use the SeNB resource When the entity is connected,

The data transmitted by the data transmission module includes: a PDCP PDU distributed by the PDCP entity of the MCG to the RLC entity of the S-SCG but not completed at the S-SCG.
The data transmission device according to claim 27, wherein the data transmitted by the data transmission module further comprises: a PDCP entity delivered by the MCG, which is distributed to the S-SCG by a PDCP entity of the MCG. A PDCP PDU other than the PDCP PDU that the RLC entity does not complete transmission at the S-SCG.
The data transmission apparatus according to claim 22, wherein the standby forked bearer established by the establishing module on the MCG uses a security configuration of the SCG, and the standby RLC entity and the PDCP established on the SCG by the RB that needs to use the SeNB resource When the entity is connected,

The data transmitted by the data transmission module includes: downlink data received by the source SeNB from the core network but not completed by the source SeNB, and PDCP generated by the PDCP entity established by the RB that needs to use the SeNB resource on the source SeNB. PDU.
The data transmission device according to claim 23, wherein the data transmitted by the data transmission module comprises: a PDCP PDU distributed by the PDCP entity of the MCG to an RLC entity of the source SCG but not completed at the source SCG.
The data transmission method according to claim 30, wherein the data transmitted by the data transmission module further comprises: an RLC entity delivered by the PDCP entity of the MCG but distributed by the PDCP entity of the MCG to the source SCG but Other PDCP PDUs that are not in the source SCG complete the transmitted PDCP PDU.
The data transmission device according to claim 20, wherein the standby forked bearer established by the establishing module on the MCG uses a security configuration of the MCG, and the established standby RLC entity and the RB that needs to use the SeNB resource are established on the MCG. When the PDCP entity is connected, or when the alternate data transmission path is a standby forked logical channel,

When the apparatus is separately disposed in the user side or the UE, the data transmission module is further configured to: after the UE successfully accesses the target SeNB after the SeNB change, or the UE receives the MCG After the SeNB change sent by the associated MeNB is notified for a preset duration T, the use of the alternate data transmission path to stop data transmission is stopped;

When the device is separately disposed in the network side or the MeNB, the data transmission module is further configured to: after the MeNB to which the MCG belongs, receive the UE from the target SeNB after the UE or the SeNB changes, the UE successfully accesses the After the SeNB changes the notification of the target SeNB after the change, the use of the alternate data transmission path to stop data transmission is stopped.
The data transmission apparatus according to claim 22, wherein the standby forked bearer established by the establishing module on the MCG uses a security configuration of the SCG, and the standby RLC entity and the PDCP established on the SCG by the RB that needs to use the SeNB resource When the entity is connected,

When the device is separately disposed on the network side or the MeNB, the data transmission module is configured to stop using the downlink data received by the source SeNB from the core network but not completed by the source SeNB after the transmission is completed. The alternate data transmission path transmits data.
A base station comprising the apparatus of any one of the above 18 to 33.
A UE comprising the apparatus of any one of the above 18 to 33.
A computer readable storage medium storing computer executable instructions for performing the data transmission method according to any one of the above items 1 to 17.