WO2017118186A1 - Procédé et appareil de transmission de données ainsi que station de base et équipement utilisateur - Google Patents

Procédé et appareil de transmission de données ainsi que station de base et équipement utilisateur Download PDF

Info

Publication number
WO2017118186A1
WO2017118186A1 PCT/CN2016/103935 CN2016103935W WO2017118186A1 WO 2017118186 A1 WO2017118186 A1 WO 2017118186A1 CN 2016103935 W CN2016103935 W CN 2016103935W WO 2017118186 A1 WO2017118186 A1 WO 2017118186A1
Authority
WO
WIPO (PCT)
Prior art keywords
senb
data transmission
standby
mcg
data
Prior art date
Application number
PCT/CN2016/103935
Other languages
English (en)
Chinese (zh)
Inventor
施小娟
黄河
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017118186A1 publication Critical patent/WO2017118186A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • 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).
  • a base station and a UE (User Equipment, User Equipment/User Terminal).
  • FIG. 1 is a schematic diagram of the network topology of the traditional cellular wireless access network.
  • 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.
  • LPN Low Power Node
  • 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.
  • e Femto/Home
  • Relay Radio Relay Access Device
  • UDN Ultra Dense Network
  • 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.
  • the user equipment/user terminal 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.
  • 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.
  • 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;
  • 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 method further includes: establishing the RB that needs to use the SeNB resource;
  • the establishing an alternate data transmission path includes:
  • the standby data transmission path is established for the RB.
  • the standby data transmission path is established for the RB that needs to use the SeNB resource that has been established.
  • 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 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 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.
  • 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 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;
  • 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;
  • the user terminal UE receives the notification message sent by the MeNB to which the MCG belongs.
  • the transmitting data by using the alternate data transmission path includes:
  • 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;
  • 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 standby forked bearer uses the security configuration of the MCG
  • 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:
  • 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.
  • 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.
  • 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.
  • the transmitted data further includes: a split by the PDCP entity of the MCG.
  • the method further includes: stopping the use of the alternate data transmission path to transmit data.
  • 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.
  • 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:
  • 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,
  • the target SeNB 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 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:
  • 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.
  • 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.
  • 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 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.
  • 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 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 module is configured to:
  • 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;
  • 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.
  • 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.
  • 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;
  • 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. .
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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,
  • 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;
  • 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 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 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.
  • 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.
  • FIG. 1 is a schematic diagram of a network topology of a related art cellular radio access network
  • FIG. 2 is a schematic diagram of deploying a UDN in a specific area of a conventional cellular radio access network
  • FIG. 3 is a schematic diagram of a DC 3C 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.
  • 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
  • FIG. 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. 10 is a schematic flowchart diagram of another embodiment of implementing data transmission according to the present invention.
  • 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.
  • 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.
  • 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.
  • LTE Long Term Evaluation
  • 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.
  • 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.
  • 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.
  • 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.
  • TCP Transmission Control Protocol
  • 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.
  • 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.
  • 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.
  • 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).
  • S1-MME S1-Mobile Management Entity
  • 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)
  • MCG master cell group
  • 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.
  • 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.
  • the The serving cell is the PScell.
  • 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.
  • FIG. 3 is a schematic diagram of a DC 3C protocol architecture in the related art.
  • 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).
  • S1-U User plane
  • the S1 interface is a user plane interface between the base station and the core network.
  • RBs radio bearers
  • 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.
  • RLC Radio Link Control
  • MAC Media Access Control
  • the PDCP of the MeNB 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.
  • FIG. 4 is a schematic diagram of a DC 1A protocol architecture in the related art.
  • the UE is simultaneously connected to the MeNB and the SeNB.
  • the MeNB and the SeNB and the core network respectively have independent S1-U interfaces.
  • 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).
  • 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.
  • 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.
  • frequent changes of the SeNB do not occur.
  • the above problem does not have a significant impact on the user service experience.
  • dense deployment of small cells may cause even if the UE moves at a walking speed.
  • the SeNB is also frequently changed.
  • 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.
  • At least one standby RLC entity and at least one alternate logical dedicated traffic channel 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.
  • 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.
  • 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.
  • 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.
  • the data may be used by using different memory pointers for data transmitted through different DTCHs, for example, by using data.
  • 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
  • the MAC entity accesses the pointer 1 according to the received pointer 1 Data
  • 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 is to be used to the standby DTCH1 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
  • the MAC entity accesses the pointer 1 according to the received pointer 1 Data
  • the data is sent
  • 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.
  • S-SCG source SCG
  • At least one alternate logical dedicated traffic channel 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.
  • the standby bifurcation data transmission path may be established for the RB;
  • the MCG is located on the MeNB, and the physical characteristics of the MeNB may be a macro eNB or an LPN.
  • the MeNB is a macro eNB
  • each cell in the MCG is a macro cell.
  • 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;
  • 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 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.
  • the alternate data transmission path is a standby forked logical channel
  • 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:
  • 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
  • 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.
  • 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:
  • 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.
  • 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.
  • Step 502 Stop using the alternate data transmission path to transmit data.
  • 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
  • this step may include:
  • the UE 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
  • the target SeNB 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
  • the MeNB 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.
  • the step may include:
  • 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.
  • 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 MeNB 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.
  • 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.
  • a forked bearer is established for the split bearer while establishing a split bearer, where the concept of a forked bearer is established.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • RB1 establishes the MCG bearer
  • RB2 establishes the split bearer.
  • 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.
  • 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).
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • SeNB Addition Request SeNB Addition Request
  • 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.
  • 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.
  • 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.
  • FIG. 10 is a schematic flowchart of another embodiment of implementing data transmission according to the present invention, then, as shown in FIG. 10
  • the MeNB 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.
  • 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.
  • 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.
  • 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.
  • 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 notification message is an RRC layer message (such as subsequent The RRC connection reconfiguration message of step 605) or the MAC layer message.
  • 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.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • 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.
  • 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
  • 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.
  • a backup fork bearer is established for a forked bearer when the SeNB changes, as shown in FIG.
  • Step 1101 Establish a forked bearer.
  • 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.
  • 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.
  • 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.
  • 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 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 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.
  • 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.
  • the - 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.
  • 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.
  • 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.
  • Step 1106 Transfer data using the alternate fork bearer.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the actual implementation includes:
  • Step 1301 Establish a bearer on the SCG, and establish a standby fork bearer for the bearer on the MCG.
  • 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.
  • 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.
  • two or more alternate fork carriers may be established for the RB3, and the actual implementation is not described herein again.
  • 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.
  • 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.
  • the notification message is an RRC 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.
  • the RB3 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.
  • 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.
  • the fourth embodiment it is assumed that a standby forked bearer is established for a bearer of a source SCG when the SeNB changes.
  • 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).
  • 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.
  • the PDCP entity of the RB3 in the S-SeNB remains reserved until step 1511.
  • 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.
  • 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.
  • FIG. 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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 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.
  • 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.
  • 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;
  • 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.
  • 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:
  • 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.
  • 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,
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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,
  • 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.
  • 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.
  • the device/function module/functional unit in the above embodiment 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 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.

Landscapes

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

Abstract

La présente invention porte sur un procédé et sur un dispositif de transmission de données ainsi que sur une station de base et sur un équipement utilisateur (UE pour User Equipment). Le procédé consiste : à établir un canal de transmission de données en attente sur un MCG pour un RB ayant besoin d'utiliser une ressource SeNB ; et, pendant un processus de changement d'un SeNB, à utiliser le canal de transmission de données en attente pour transmettre des données, les données transmises comprenant des données qui ont été distribuées à une entité RLC d'un SCG source avant que le SeNB ne change mais qui ne sont pas complètement transmises dans le SCG source.
PCT/CN2016/103935 2016-01-04 2016-10-31 Procédé et appareil de transmission de données ainsi que station de base et équipement utilisateur WO2017118186A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610005639.8A CN106941700B (zh) 2016-01-04 2016-01-04 一种数据传输方法及装置和基站及ue
CN201610005639.8 2016-01-04

Publications (1)

Publication Number Publication Date
WO2017118186A1 true WO2017118186A1 (fr) 2017-07-13

Family

ID=59273213

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/103935 WO2017118186A1 (fr) 2016-01-04 2016-10-31 Procédé et appareil de transmission de données ainsi que station de base et équipement utilisateur

Country Status (2)

Country Link
CN (1) CN106941700B (fr)
WO (1) WO2017118186A1 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109661839B (zh) * 2017-09-26 2020-09-25 Oppo广东移动通信有限公司 用于数据处理的方法和终端设备
EP3687239B1 (fr) 2017-09-28 2021-09-08 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de commutation de trajet,support lisible par ordinateur et dispositif terminal
CN110167018B (zh) * 2018-02-11 2021-12-10 华为技术有限公司 一种安全保护的方法、装置及接入网设备
CN110366198B (zh) * 2018-03-26 2021-07-23 维沃移动通信有限公司 一种辅小区组变更结果的检测方法及终端
CN113068180A (zh) * 2018-08-10 2021-07-02 华为技术有限公司 双连接通信方法及其装置、系统
CN111586766B (zh) * 2019-02-15 2021-08-27 华为技术有限公司 一种通信方法、装置及系统
CN111726840B (zh) * 2019-03-21 2021-09-24 大唐移动通信设备有限公司 一种终端的双连接配置处理方法及装置
CN111757397B (zh) * 2019-03-28 2021-11-16 大唐移动通信设备有限公司 一种进行数据前转的方法及设备
CN114342465A (zh) * 2019-11-06 2022-04-12 Oppo广东移动通信有限公司 无线通信的方法和终端设备
CN113316153B (zh) * 2020-04-02 2024-03-26 阿里巴巴集团控股有限公司 一种短信息检验方法、装置和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104349387A (zh) * 2013-08-08 2015-02-11 上海贝尔股份有限公司 在支持双/多连接的系统中用于下行链路传输的方法和设备
WO2015065080A1 (fr) * 2013-11-01 2015-05-07 Samsung Electronics Co., Ltd. Procédé et appareil pour reconfigurer un support
US20150264621A1 (en) * 2014-03-14 2015-09-17 Intel Corporation Systems and methods for joint handover of user equipment and secondary cell group in 3gpp lte dual connectivity
CN104969592A (zh) * 2014-01-17 2015-10-07 三星电子株式会社 无线通信网络中用户设备的双连通操作模式

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102083126A (zh) * 2009-11-27 2011-06-01 诺基亚西门子通信公司 对不同中继链路使用不同收发机的中继节点切换
EP2400796A1 (fr) * 2010-06-28 2011-12-28 Alcatel Lucent Reconfiguration d'interface radio
US20150043492A1 (en) * 2013-08-12 2015-02-12 Electronics And Telecommunications Research Institute Method for providing dual connectivity in wireless communication system
US10039086B2 (en) * 2013-11-11 2018-07-31 Electronics And Telecommunications Research Institute Communication method and apparatus in network environment where terminal may have dual connectivity to multiple base stations
CN104768152B (zh) * 2014-01-02 2018-11-23 中国移动通信集团公司 一种双基站数据分流时的密钥产生方法、装置及系统
US10075381B2 (en) * 2014-01-28 2018-09-11 Mediatek Inc. Buffer status report and logical channel prioritization for dual connectivity
EP3101989A4 (fr) * 2014-01-29 2017-10-11 Samsung Electronics Co., Ltd. Procédé et appareil d'accès aléatoire de système de communication mobile
JP2015177548A (ja) * 2014-03-14 2015-10-05 宏達國際電子股▲ふん▼有限公司 ユーザ機器及び基地局に適用しうる接続変更方法
ES2774961T3 (es) * 2014-03-21 2020-07-23 Alcatel Lucent Red de conectividad dual
CN104955064B (zh) * 2014-03-28 2019-01-11 上海诺基亚贝尔股份有限公司 一种在双连接系统中处理用户设备端rlc/pdcp实体的方法与设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104349387A (zh) * 2013-08-08 2015-02-11 上海贝尔股份有限公司 在支持双/多连接的系统中用于下行链路传输的方法和设备
WO2015065080A1 (fr) * 2013-11-01 2015-05-07 Samsung Electronics Co., Ltd. Procédé et appareil pour reconfigurer un support
CN104969592A (zh) * 2014-01-17 2015-10-07 三星电子株式会社 无线通信网络中用户设备的双连通操作模式
US20150264621A1 (en) * 2014-03-14 2015-09-17 Intel Corporation Systems and methods for joint handover of user equipment and secondary cell group in 3gpp lte dual connectivity

Also Published As

Publication number Publication date
CN106941700A (zh) 2017-07-11
CN106941700B (zh) 2020-12-29

Similar Documents

Publication Publication Date Title
WO2017118186A1 (fr) Procédé et appareil de transmission de données ainsi que station de base et équipement utilisateur
RU2713442C1 (ru) Система и способ переключения сот
US11690026B2 (en) Method and device for efficient communication in next generation mobile communication system
EP4027715A1 (fr) Appareil et procédé d'abonnement à un service par l'intermédiaire d'une interface e2 dans un système de communication de réseau d'accès radio
US9986462B2 (en) Double-connection implementation method and base station
CN103947252B (zh) 无线连接失败期间的掉话避免
EP2744260B1 (fr) Procédé et dispositif de transmission de données
EP3035735A1 (fr) Procédé de transfert, station de base maître et station de base esclave
US20180049091A1 (en) Method, apparatus, and system for transmitting data during handover procedure
US10045266B2 (en) Scheme for transmitting and receiving information in wireless communication system
US9615301B2 (en) Base station handover method and system for communications system
JP2017508364A (ja) セカンダリ基地局及びマスター基地局によって実行される通信方法、並びに対応する基地局
CN113709909B (zh) 多连接通信方法和设备
CN104640165B (zh) 一种数据传输方法、设备和系统
US9668244B2 (en) Radio resource management method, macro base station, and low-power node
US11877327B2 (en) Method and apparatus for transmitting and receiving connection information in wireless communication system
KR20200098178A (ko) 차세대 이동통신 시스템에서 전력 소모를 줄이기 위해 동적 스케쥴링을 적용하는 동작 방법 및 장치
WO2017177950A1 (fr) Procédé, appareil et système d'établissement de connexion
WO2015161575A1 (fr) Procédé, station de base, entité de gestion mobile, et système de notification d'emplacement de terminal utilisateur
JP2023546462A (ja) 通信方法および装置、可読記憶媒体、ならびにシステム
WO2020078220A1 (fr) Procédé et appareil de traitement de données et dispositif de réseau
US20220124583A1 (en) Method and device for multicast transmission
WO2021163894A1 (fr) Procédé et appareil de communication basés sur un relais
EP3878239A1 (fr) Procédé et système pour prise en charge de multiples tranches de réseau entièrement séparées
WO2014050805A1 (fr) Procédé de communication mobile

Legal Events

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

Ref document number: 16883314

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16883314

Country of ref document: EP

Kind code of ref document: A1