WO2018166442A1 - 一种数据传输方法及装置、计算机存储介质 - Google Patents

一种数据传输方法及装置、计算机存储介质 Download PDF

Info

Publication number
WO2018166442A1
WO2018166442A1 PCT/CN2018/078826 CN2018078826W WO2018166442A1 WO 2018166442 A1 WO2018166442 A1 WO 2018166442A1 CN 2018078826 W CN2018078826 W CN 2018078826W WO 2018166442 A1 WO2018166442 A1 WO 2018166442A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
data
target
pdu data
successfully received
Prior art date
Application number
PCT/CN2018/078826
Other languages
English (en)
French (fr)
Inventor
刘壮
高音
黄河
刘旸
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to DK18766862.9T priority Critical patent/DK3598797T3/da
Priority to EP18766862.9A priority patent/EP3598797B1/en
Priority to FIEP18766862.9T priority patent/FI3598797T3/fi
Priority to US16/493,731 priority patent/US11533775B2/en
Publication of WO2018166442A1 publication Critical patent/WO2018166442A1/zh
Priority to US17/987,762 priority patent/US11864275B2/en

Links

Images

Classifications

    • 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
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points

Definitions

  • the present application relates to the field of wireless communications, and in particular, to a data transmission method and apparatus, and a computer storage medium.
  • the fifth-generation (5G, 5th Generation) network architecture is innovative and flexible.
  • the BBU Building Base Band Unit
  • CU Centralized Unit
  • DU Distributed Processing Unit
  • the delay-insensitive network function is placed in the CU
  • the delay-sensitive network function is placed in the DU.
  • the CU and the DU are transmitted through the ideal/or non-ideal frontal (fronthaul). And connectivity for multi-point collaboration and support for flexible networking of separate or integrated sites.
  • the switching between the DUs in the same CU during the data transmission in the acknowledgment mode is easy to cause the downlink RLC PDU data to be lost. This is an urgent problem to be solved.
  • the embodiment of the present application provides a data transmission method and device.
  • a data transmission method includes:
  • the source DU reports a PDCP transmission status report to the CU, where the PDCP transmission status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE, and retransmits the PDCP PDU that is not successfully received by the UE to the UE through the target DU. data.
  • a data transmission device comprising:
  • a triggering unit configured to report a PDCP transmission status report to the CU, where the PDCP transmission status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE, and retransmit the UE to the UE by the target DU.
  • PDCP PDU data
  • a data transmission apparatus comprising: a processor and a memory, the memory storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the following method:
  • the PDCP transmission status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE, and retransmit the PDCP PDU data that is not successfully received by the UE to the UE through the target DU.
  • a data transmission method includes:
  • the target DU acquires PDCP PDU data that is not successfully received by the UE and retransmits to the UE.
  • a data transmission device comprising:
  • a first receiving unit configured to acquire PDCP PDU data that is not successfully received by the UE
  • the first sending unit is configured to retransmit the PDCP PDU data that is not successfully received by the UE to the UE.
  • a data transmission apparatus comprising: a processor and a memory, the memory storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the following method:
  • the PDCP PDU data that is not successfully received by the UE is obtained and retransmitted to the UE.
  • a data transmission method includes:
  • the CU receives a PDCP transmission status report, where the PDCP status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE;
  • the CU acquires PDCP PDU data that is not successfully received by the UE according to the PDCP transmission status report and resends the data to the target DU.
  • a data transmission device comprising:
  • a second receiving unit configured to receive a PDCP transmission status report, where the PDCP status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE;
  • the second sending unit is configured to acquire, according to the PDCP transmission status report, PDCP PDU data that is not successfully received by the UE and resend to the target DU.
  • a data transmission apparatus comprising: a processor and a memory, wherein the memory stores computer executable instructions, and when the computer executable instructions are executed by the processor, the following method is implemented:
  • the PDCP status report being used by the CU to determine which PDCP protocol data unit PDU data is not successfully received by the UE;
  • PDCP PDU data that is not successfully received by the UE is acquired and retransmitted to the target DU.
  • the embodiment of the present application further provides a computer storage medium storing computer executable instructions, and the computer executable instructions are implemented to implement the data transmission method applied to the UE.
  • the embodiment of the present application further provides a computer storage medium storing computer executable instructions, and the computer executable instructions are implemented to implement the data transmission method applied to the CU.
  • the embodiment of the present application further provides a computer storage medium storing computer executable instructions, and the computer executable instructions are implemented to implement the data transmission method applied to the DU.
  • the PDCP report is actively triggered by the UE and sent to the target DU.
  • the target DU can obtain PDCP PDU data that is not successfully received by the UE according to the PDCP report, and retransmit the data to the UE, and resolve the DU between the same CU. Switching easily leads to the loss of downlink PDCP PDU data, which satisfies the seamless handover requirements of users.
  • the UE actively triggers the RLC report and sends the report to the target DU.
  • the target DU can obtain the RLC PDU data that is not successfully received by the UE according to the RLC report and retransmit the data to the UE, and resolve the DU between the same CU. Switching easily leads to the loss of downlink RLC PDU data, which satisfies the seamless handover requirements of users.
  • FIG. 1 is a schematic diagram of CU-DU separation of a scheme option 2 in the related art
  • FIG. 2 is a schematic diagram of CU-DU separation of scheme option 3 in the related art
  • FIG. 3 is a schematic diagram of DU switching under the control of the same CU in the related art
  • FIG. 4 is a schematic flowchart of a data transmission method applied to a UE according to Embodiment 1 of the present application;
  • FIG. 5 is a schematic structural diagram of a structure of a data transmission apparatus applied to a UE according to Embodiment 1 of the present application;
  • FIG. 6 is a schematic flowchart of a data transmission method applied to a DU according to Embodiment 1 of the present application;
  • FIG. 7 is a schematic structural diagram of a data transmission apparatus applied to a DU according to Embodiment 1 of the present application.
  • FIG. 8 is a schematic flowchart of a data transmission method applied to a CU according to Embodiment 1 of the present application.
  • FIG. 9 is a schematic structural diagram of a structure of a data transmission apparatus applied to a CU according to Embodiment 1 of the present application.
  • FIG. 10 is a schematic flowchart of a data transmission method applied to a UE according to Embodiment 2 of the present application;
  • FIG. 11 is a schematic structural diagram of a structure of a data transmission apparatus applied to a UE according to Embodiment 2 of the present application;
  • FIG. 12 is a schematic flowchart of a data transmission method applied to a DU according to Embodiment 2 of the present application;
  • FIG. 13 is a schematic structural diagram of a structure of a data transmission apparatus applied to a DU according to Embodiment 2 of the present application;
  • FIG. 14 is a schematic flowchart of a data transmission method applied to a CU according to Embodiment 2 of the present application;
  • FIG. 15 is a schematic structural diagram of a structure of a data transmission apparatus applied to a CU according to Embodiment 2 of the present application;
  • 16 is a schematic diagram of a DU inter-mode confirmation mode switching process and a data transmission process according to Example 1 of the present application;
  • 17 is a schematic diagram of a DU inter-mode confirmation mode switching process and a data transmission process according to Example 2 of the present application;
  • FIG. 18 is a schematic diagram of a DU inter-mode confirmation mode switching process and a data transmission process according to Example 3 of the present application;
  • FIG. 19 is a schematic diagram of a DU inter-mode confirmation mode switching process and a data transmission process according to Example 4 of the present application;
  • FIG. 20 is a schematic diagram of a DU inter-mode confirmation mode switching process and a data transmission process according to Example 5 of the present application;
  • FIG. 21 is a schematic diagram of a DU inter-mode confirmation mode switching process and a data transmission process according to Example 6 of the present application.
  • option 2 there are two options of option 2 and option 3 in the architecture separated by the CU-DU high-level protocol.
  • option 2 is divided between Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLC), that is, PDCP and its PDCP are placed in CU, RLC and its The entities below the RLC are placed in the DU.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • option 3 is divided within the RLC, that is, a part of the RLC function, the PDCP and its PDCP are placed in the CU, and some entities of the RLC function and below are placed in the DU.
  • a partial RLC in the CU is defined herein as RLC-H
  • a partial RLC in the DU is defined as RLC-L.
  • the RLC-H function is a non-delay sensitive function, including an automatic repeat request (ARQ), a non-scheduled related segment, and/or a cascade.
  • the RLC-L function is a delay sensitive function (such as a real-time segmentation function), and processes protocol data unit (PDU) packets from the CU in real time according to the MAC scheduling indication.
  • the CU of one serving cell connects multiple DUs, and moves from the service range of one DU controlled by the current CU of the user to the service range of another DU controlled by the CU, and the user also Need to switch from the current DU to the target DU.
  • the DU switching under the control of the internal CU (intra-CU) will be more frequent due to the dense deployment of the DU.
  • the data of the RLC transmission buffer on the source DU is cleared.
  • the RLC PDU data that was not successfully transmitted on the original DU will be lost.
  • the target DU of the handover does not know which RLC PDU data is on the source DU and the transmission is not successful.
  • the present application provides a data transmission scheme, which is applicable to a process in which a user switches between DUs in a CU-DU networking architecture, and can solve data in a confirmation mode of a user in a 5G CU-DU architecture. Switching between DUs in the same CU during transmission is likely to cause loss of downlink RLC PDU data.
  • This embodiment can be applied to the CU-DU networking architecture shown in FIG. 1.
  • a data transmission method is applied to a source DU, as shown in FIG. 4, including:
  • Step 401 The source DU reports a PDCP transmission status report to the CU, where the PDCP transmission status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE.
  • Step 402 The CU retransmits the PDCP PDU data that is not successfully received by the UE to the UE by using the target DU.
  • the CU sends the PDCP PDU data that is not successfully received by the UE to the target DU, and sends the PDCP PDU data that is not successfully received by the UE to the UE by using the target DU.
  • a data transmission device is applied to a source DU, as shown in FIG. 5, and includes:
  • the triggering unit 51 is configured to report a PDCP transmission status report to the CU, where the PDCP transmission status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE, and retransmit the UE to the UE by the target DU. Received PDCP PDU data.
  • a data transmission apparatus comprising: a processor and a memory, the data transmission apparatus being applied to a UE, the memory storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the following method:
  • the PDCP transmission status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE, and retransmit the PDCP PDU data that is not successfully received by the UE to the UE through the target DU.
  • a data transmission method, applied to a target DU, as shown in FIG. 6, may include:
  • Step 601 The target DU acquires PDCP PDU data that is not successfully received by the UE and retransmits the data to the UE.
  • the target DU acquires PDCP PDU data that is not successfully received by the UE and retransmits the data to the UE, including:
  • the target DU receives PDCP PDU data from the CU and caches it;
  • the target DU resends the PDCP PDU data of the buffered PDCP PDU data that is not successfully received by the UE to the UE.
  • the target DU acquires PDCP PDU data that is not successfully received by the UE and retransmits the data to the UE, including:
  • the target DU receives the PDCP PDU data sent by the CU that is not successfully received by the UE and is buffered;
  • the target DU resends the buffered PDCP PDU data to the UE.
  • a data transmission device, applied to a target DU, as shown in FIG. 7, may include:
  • the first receiving unit 71 is configured to acquire PDCP PDU data that is not successfully received by the UE;
  • the first sending unit 72 is configured to retransmit the PDCP PDU data that is not successfully received by the UE to the UE.
  • the first receiving unit 71 is configured to receive PDCP PDU data from the CU and cache the data.
  • the first sending unit 72 is configured to resend PDCP PDU data that is not successfully received by the UE in the buffered PDCP PDU data to the UE.
  • the first receiving unit 71 is configured to receive, by the CU, PDCP PDU data that is not successfully received by the UE, and cache the data.
  • the first sending unit 72 is configured to resend the buffered PDCP PDU data to the UE.
  • a data transmission apparatus comprising: a processor and a memory, the data transmission apparatus being applied to a DU, the memory storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the following method:
  • the PDCP PDU data that is not successfully received by the UE is obtained and retransmitted to the UE.
  • a data transmission method, applied to a CU, as shown in FIG. 8, may include:
  • Step 801 The CU receives a PDCP transmission status report, where the PDCP status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE.
  • Step 802 The CU obtains PDCP PDU data that is not successfully received by the UE according to the PDCP transmission status report, and retransmits the data to the target DU, and retransmits the PDCP that is not successfully received by the UE to the UE by using the target DU. PDU data.
  • the CU obtains PDCP PDU data that is not successfully received by the UE and resends the data to the target DU according to the PDCP transmission status report, including:
  • the CU buffers PDCP PDU data
  • the CU resends the PDCP PDU data that is not successfully received by the UE in the buffered PDCP PDU data to the target DU according to the PDCP status report.
  • a data transmission device applied to a CU, as shown in FIG. 9, may include:
  • the second receiving unit 91 is configured to receive a PDCP transmission status report, where the PDCP status report is used by the CU to determine which PDCP PDU data is not successfully received by the UE;
  • the second sending unit 92 is configured to acquire, according to the PDCP transmission status report, PDCP PDU data that is not successfully received by the UE and resend to the target DU.
  • the method further includes:
  • the buffer unit 93 is configured to buffer PDCP PDU data that is not successfully received by the UE;
  • the second sending unit 92 is configured to resend the PDCP PDU data that is not successfully received by the UE in the buffered PDCP PDU data to the target DU according to the PDCP status report.
  • a data transmission apparatus comprising: a processor and a memory, the data transmission apparatus being applied to a CU, the memory storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the following method:
  • the PDCP status report being used by the CU to determine which PDCP protocol data unit PDU data is not successfully received by the UE;
  • PDCP PDU data that is not successfully received by the UE is acquired and retransmitted to the target DU.
  • the intra CU can transmit data to the target DU in advance when switching between the DUs, so that the target DU can retransmit the corresponding data to the UE.
  • the CU may send the PDCP PDU data sent to the source DU to the target DU at the same time one time in advance. Copy (with the same sequence (SN) number and content).
  • the target DU can directly learn the PDCP status that the UE fails to receive according to the PDCP status report, and retransmit the corresponding PDCP PDU data that the CU caches in the target DU in advance to the PDCP status report. UE, thereby reducing the retransmission delay.
  • the CU may also send a PDCP poll to the UE, and request the UE to report the PDCP status report. Specifically, the CU may send a PDCP polling packet to the UE before the network side determines that the inter-DU of the intra-CU needs to be switched. After receiving the PDCP polling packet, the UE may report the PDCP status report to the network.
  • the CU may send the newly transmitted data and the PDCP PDU data that the UE fails to receive to the source DU and the target DU at the same time, so that the redundancy of buffering data to the target DU in advance can be reduced.
  • the source DU may also know which PDCP PDU data is successfully transmitted according to the RLC status report fed back by the UE, and based on this, the source DU may construct a PDCP state. Reporting and sending to the CU, after receiving the PDCP status report, the CU may simultaneously send the newly transmitted data and the PDCP PDU data that the UE fails to receive to the source DU and the target DU, so that the target DU sends the corresponding PDCP PDU data. Go to the UE to avoid packet loss.
  • the UE actively triggers the PDCP report and sends the PDCP report to the target DU.
  • the target DU can obtain the PDCP PDU data that is not successfully received by the UE according to the PDCP report and retransmit the data to the UE, and the same CU is solved.
  • the switching between DUs is likely to cause the loss of downlink PDCP PDU data, which satisfies the seamless handover requirements of users.
  • the PDCP PDU data that is not successfully received by the UE is sent to the target DU by the CU in advance and cached.
  • the target DU may directly obtain the corresponding PDCP PDU data from the cache according to the PDCP status report and retransmit the data. Up to the UE, thereby solving the problem that the downlink data retransmission delay is large.
  • This embodiment can be applied to the CU-DU networking architecture shown in FIG. 2.
  • a data transmission method is applied to a UE, as shown in FIG. 10, including:
  • Step 1001 Before, during, or after the switching from the source DU to the target DU, the RLC status report is actively triggered and reported to the network side, where the RLC status report is used to indicate which RLC PDU data is not successfully received by the UE.
  • Step 1002 Receive RLC PDU data that is retransmitted by the network side and is not successfully received by the UE.
  • a data transmission device is applied to a UE, as shown in FIG. 11, and includes:
  • the fourth triggering unit 111 is configured to actively trigger and report an RLC status report to the network side before, during, or after the switching from the source DU to the target DU, where the RLC status report is used to indicate which RLC PDU data is not used by the UE. Successfully received;
  • the fourth receiving unit 112 is configured to receive RLC PDU data that is retransmitted by the network side and is not successfully received by the UE.
  • a data transmission apparatus comprising: a processor and a memory, the data transmission apparatus being applied to a UE, the memory storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the following method:
  • the RLC status report Before, during, or after the switching from the source DU to the target DU, the RLC status report is actively triggered and reported to the network side, where the RLC status report is used to indicate which RLC PDU data is not successfully received by the UE;
  • Step 1201 Receive an RLC status report from a UE, where the RLC status report is used to indicate which RLC PDU data is not successfully received by the UE.
  • Step 1202 Acquire, according to the RLC status report, RLC PDU data that is not successfully received by the UE from the CU and retransmit the data to the UE.
  • step 1202 acquiring RLC PDU data that is not successfully received by the UE from the CU and retransmitting to the UE may include: transparently transmitting the RLC status report to the CU; Receiving RLC PDU data from the CU that is not successfully received by the UE; retransmitting the RLC PDU data that is not successfully received by the UE to the UE.
  • the obtaining, by the CU according to the RLC status report, the RLC PDU data that is not successfully received by the UE and retransmitting to the UE may include: transparently transmitting the RLC status report to the CU.
  • a data transmission device, applied to a DU, as shown in FIG. 13, may include:
  • the fifth receiving unit 131 is configured to receive an RLC status report from the user equipment UE, where the RLC status report is used to indicate which RLC PDU data is not successfully received by the UE;
  • the fifth retransmission unit 132 is configured to acquire RLC PDU data that is not successfully received by the UE from the CU according to the RLC status report, and retransmit the data to the UE.
  • the fifth retransmission unit 132 is specifically configured to transparently transmit the RLC status report to the CU, and receive RLC PDU data that is not successfully received by the UE from the CU, and the The RLC PDU data successfully received by the UE is retransmitted to the UE.
  • the data transmission apparatus may further include: a fifth buffer unit 133, configured to receive, by the CU, the RLC PDU data that is not successfully received by the UE, and cache the fifth heavy leaflet;
  • the element 132 is specifically configured to transparently transmit the RLC status report to the CU, and retransmit the RLC PDU data buffered in the fifth buffer unit to the UE after the UE completes the handover of the target DU.
  • a data transmission apparatus comprising: a processor and a memory, the data transmission apparatus being applied to a DU, the memory storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the following method:
  • the RLC status report is used to indicate which RLC PDU data is not successfully received by the UE;
  • RLC PDU data that is not successfully received by the UE is acquired from the CU and retransmitted to the UE.
  • a data transmission method, applied to a CU, as shown in FIG. 14, may include:
  • Step 1401 Receive an RLC status report from a target DU, where the RLC status report is used to indicate which RLC PDU data is not successfully received by the UE.
  • Step 1402 Send, by the RLC status report, RLC PDU data that is not successfully received by the UE to the target DU.
  • a data transmission device applied to a CU, as shown in FIG. 15, may include:
  • the sixth receiving unit 151 is configured to receive an RLC status report from the target DU, where the RLC status report is used to indicate which RLC PDU data is not successfully received by the UE;
  • the sixth sending unit 152 is configured to send, by using the RLC status report, RLC PDU data that is not successfully received by the UE to the target DU.
  • a data transmission apparatus comprising: a processor and a memory, the data transmission apparatus being applicable to a CU, the memory storing computer executable instructions, the computer executable instructions being implemented by the processor to implement the following method:
  • the RLC status report is used to indicate which RLC PDU data is not successfully received by the UE;
  • the RLC status report is instructed to send RLC PDU data that is not successfully received by the UE to the target DU.
  • the UE may actively trigger an RLC status report to report to the network side before the UE completes the handover from the source DU to the target DU, or the handover may be performed on the CU-DU architecture shown in FIG.
  • the side CU can know which downlink RLC data packets are not successfully transmitted according to the RLC status report reported by the UE, and is used for selective RLC retransmission.
  • the target DU may directly parse the RLC status report and selectively read from the cache.
  • the RLC PDU data successfully received by the UE is retransmitted to the UE; if the target DU does not pre-cache the RLC PDU data, or the DU does not have the capability to resolve the RLC status report, the target DU may transparently transmit the RLC status report to the CU, and the CU may parse the RLC status. Reporting, and selectively retransmitting the RLC PDU data that the UE fails to receive to the UE through the target DU.
  • the CU may determine, according to the RLC status report, which downlink RLC PDU data is not successfully received by the UE, and the CU may The RLC PDU data that is not successfully received by the UE (that is, failed to be successfully transmitted on the source DU) is selectively retransmitted to the UE through the target DU.
  • the CU may send the RLC PDU data to the target DU in advance when the inter-DU handover, so that the target DU retransmits the corresponding RLC PDU data to the UE.
  • the CU may send the RLC PDU data indicating the retransmission in the RLC status report to the target DU in advance, and the target DU may be pre-cached. The data is such that after the user completes the handover to the target DU, the target DU can quickly retransmit the RLC PDU data to the UE, thereby reducing the transmission delay.
  • the UE actively triggers the RLC report and sends the report to the target DU.
  • the target DU can obtain the RLC PDU data that is not successfully received by the UE according to the RLC report and retransmit the data to the UE, and the same CU is solved.
  • the switching between the DUs is likely to cause the loss of downlink RLC PDU data, which satisfies the seamless handover requirements of users.
  • the RCU PDU data that is not successfully received by the UE is sent to the target DU by the CU in advance and cached.
  • the target DU may directly obtain the corresponding RLC PDU data from the cache according to the RLC status report and retransmit the data. Up to the UE, thereby solving the problem that the downlink data retransmission delay is large.
  • This example provides an inter-DU acknowledge mode switching procedure and a data transmission procedure. This example is applicable to the architecture shown in FIG. 1.
  • the CU supports initiating PDCP polling to the UE and pre-caching data to the target DU.
  • the CU may initiate PDCP polling to the UE, and pre-cache data according to the polling result to the target DU.
  • the PDCP PDU data that has been successfully transmitted may be relatively avoided in the target.
  • Pre-cache of the DU As shown in Figure 16, the steps of this example are as follows:
  • step 1601 the network side prepares to perform switching between the DUs according to the measurement result of the inter-DU handover.
  • step 1602 the CU sends a PDCP status report Polling packet to the UE through the source DU.
  • Step 1603 After receiving the PDCP polling packet, the UE responds to the network with a PDCP status report, where the PDCP status report is used to report the data reception status of the UE at the PDCP layer.
  • step 1604 to step 1605 the CU receives the PDCP status report reported by the UE, and simultaneously transmits the PDCP data packet that is not successfully received by the UE, which is indicated by the PDCP status report in the PDCP PDU data of the source DU, to the target DU.
  • the New PDUS SN (Xn..Xm) marked in FIG. 16 is the PDCP PDU data newly transmitted by the CU to the source DU, and the Unacknowledged PDCP PDU data S SN (Yn..Ym) marked in FIG. 16 is the PDCP that the UE has not successfully received. PDU data.
  • Step 1606 The target DU receives and buffers data sent by the CU in advance.
  • step 1607 after the network side completes the data pre-buffering of the target DU and completes the handover preparation work of the target DU, the RRC reconfiguration message is sent to the UE by the source DU, and the UE is notified to perform the switching of the DU.
  • the method further includes: Step 1608 (not shown in the figure), the UE performs a handover from the source DU to the target DU.
  • Step 1609 After the handover of the UE to the target DU is completed, the UE sends an RRC reconfiguration complete message to the target DU.
  • Step 1610 After the UE-to-target DU handover is completed, the UE actively triggers a PDCP status report and sends the report to the target DU.
  • the PDCP status report is used to notify the network side of which PDCP PDU data is not successfully received.
  • Step 1611 to step 1612 the target DU receives the PDCP status report, directly parses the PDCP status report, and resends the PDCP PDU data indicated by the PDCP status report in the cached data from the CU to the UE that is not successfully received. UE.
  • Step 1613 After the UE completes the target DU handover, the CU sends new PDCP PDU data to the UE through the target DU.
  • This example provides an inter-DU acknowledge mode switching process and a data transmission process.
  • This example is applicable to the architecture shown in FIG. 1, where the CU supports the target DU pre-cached data.
  • the difference between this example and the example 1 is that the CU may not initiate the PDCP status polling process to the user in the present example, but the data is directly cached to the target DU in advance during the handover preparation process, as shown in FIG. 17, the steps of this example. as follows:
  • Step 1701 The network side prepares to perform switching between the DUs according to the measurement result of the inter-DU handover.
  • Steps 1702 to 1703 the CU advances the PDCP PDU data sent to the source DU directly to the target DU, and the SN (Xn..Xm) as indicated in FIG. 17 indicates the data.
  • Step 1704 The target DU receives the PDCP PDU data sent by the CU in advance and caches.
  • step 1705 after the network side completes the data pre-buffering of the target DU and completes the handover preparation work of the target DU, the RRC reconfiguration message is sent to the UE by the source DU, and the UE is notified to perform the DU handover.
  • the method further includes: Step 1706 (not shown in the figure), the UE performs handover from the source DU to the target DU.
  • Step 1707 After the handover of the UE to the target DU is completed, the UE sends an RRC reconfiguration complete message to the target DU.
  • Step 1708 After the UE-to-target DU handover is completed, the UE actively triggers a PDCP status report to be sent to the target DU, where the PDCP status report is used to notify the network side which PDCP PDU data is not successfully received.
  • the target DU receives the PDCP status report, and directly parses the PDCP status report, and retransmits the PDCP PDU data that is not successfully received by the UE indicated by the PDCP status report status in the pre-cached PDCP PDU data to the UE.
  • Step 1711 After the UE completes the target DU handover, the CU sends new PDCP PDU data to the UE through the target DU.
  • This example provides an inter-DU acknowledge mode switching process and a data transmission process.
  • This example is applicable to the architecture shown in FIG.
  • the difference between this example and the example 1 and the example 2 is that the CU can initiate the PDCP status polling process to the user without invoking the data to the target DU in advance, and complete the no data loss switching between the DUs.
  • the steps of this example are as follows:
  • Step 1801 The network side prepares to perform switching between the DUs according to the measurement result of the inter-DU handover.
  • step 1802 the network side sends an RRC reconfiguration message to the UE through the source DU, and notifies the UE to perform the switching of the DU.
  • step 1803 the UE performs handover from the source DU to the target DU.
  • Step 1804 After the handover of the UE to the target DU is completed, the UE sends an RRC reconfiguration complete message to the target DU.
  • Step 1805 After the handover of the UE to the target DU is completed, the UE actively triggers a PDCP status report to be sent to the target DU, where the PDCP status report is used to notify the network side of which PDCP PDU data is not successfully received.
  • the target DU After the target DU receives the PDCP status report, the target DU transparently transmits the PDCP status report to the CU.
  • Step 1806 The CU retransmits the PDCP PDU data that is not successfully received by the UE indicated by the PDCP status report to the UE by using the target DU according to the received PDCP status report.
  • Step 1807 After the UE completes the target DU handover, the CU sends new PDCP PDU data to the UE through the target DU.
  • This example provides an inter-DU acknowledge mode switching process and a data transmission process.
  • This example is applicable to the architecture shown in FIG.
  • the difference between this example and the previous example is that in this example, the DU supports the transmission of the downlink PDCP PDU data and the RLC status report feedback, and can know which PDCP PDU data of the present DU is not successfully received by the UE, and can construct a PDCP status report.
  • the current PDCP transmission status is fed back to the CU.
  • the steps of this example are as follows:
  • step 1901 the network side prepares to perform switching between the DUs according to the measurement result of the inter-DU handover.
  • Step 1902 the source DU may know, according to its own transmission status of the downlink PDCP PDU data, and the RLC status report fed back by the UE, which PDCP PDU data of the present DU is not successfully received by the UE, and construct a PDCP status report.
  • the CU is sent to the CU to feed back the transmission status of the current PDCP.
  • Step 1903 The CU sends, according to the PDCP status report reported by the source DU, PDCP PDU data that has not been sent by the source DU, and PDCP PDU data that has been sent but not successfully received by the UE to the target DU.
  • Step 1904 the target DU receives and buffers data sent by the CU in advance.
  • Step 1905 The network side sends an RRC reconfiguration command to the UE through the source DU, and notifies the UE to perform the switching of the DU.
  • Step 1906 the UE performs a handover from the source DU to the target DU.
  • Step 1907 After the handover of the UE to the target DU is completed, the UE sends an RRC reconfiguration complete message to the target DU.
  • Step 1908 After the UE-to-target DU handover is completed, the UE actively triggers a PDCP status report and sends the report to the target DU.
  • the PDCP status report is used to notify the network side of which PDCP PDU data is not successfully received.
  • Step 1909 after the target DU receives the PDCP status report, the DU can directly parse the PDCP status report.
  • Step 1910 The DU retransmits the PDCP PDU data that is not successfully received by the UE in the pre-cached data to the UE according to the parsed PDCP status report content.
  • Step 1911 After the UE completes the target DU handover, the CU sends new PDCP PDU data to the UE through the target DU.
  • This example provides an inter-DU acknowledgment mode switching process and a data transmission process.
  • This example is applicable to the architecture shown in FIG. 2, where the UE side actively triggers the RLC status report to the network side after the handover is completed, as shown in FIG.
  • the steps of the example are as follows:
  • step 2001 the network side prepares to switch between the DUs according to the measurement result of the inter-DU handover.
  • step 2002 the network side sends an RRC reconfiguration message to the UE through the source DU, and notifies the UE to perform the switching of the DU.
  • step 2003 the UE performs handover from the source DU to the target DU.
  • Step 2004 After the handover of the UE to the target DU is completed, the UE sends an RRC reconfiguration complete message to the target DU.
  • step 2005 after the UE-to-target DU handover is completed, the RLC layer of the UE actively triggers an RLC status report and sends it to the target DU, which is used to notify the network side of which RLC PDU data is not successfully received by the UE, and the target DU receives the RLC. After the status report, it is directly transmitted to the CU;
  • step 2006 the CU receives the RLC status report forwarded by the target DU, and re-sends the RLC PDU data that the UE does not successfully receive by the RLC status report to the UE by using the target DU.
  • Step 2007 After the UE completes the target DU handover, the CU sends new RLC PDU data to the UE through the target DU.
  • This example provides an inter-DU acknowledgment mode switching process and a data transmission process.
  • This example is applicable to the architecture shown in FIG. 2, where the UE side actively triggers the RLC status report to the network side before the handover is completed, as shown in FIG.
  • the steps of the example are as follows:
  • step 2101 the network side prepares to switch between the DUs according to the measurement result of the inter-DU handover.
  • Step 2102 The network side sends an RRC reconfiguration command to the UE through the source DU, and notifies the UE to perform the switching of the DU.
  • Step 2103 After receiving the RRC reconfiguration message (DU switch) sent by the network side, the UE actively triggers an RLC status report and sends the report to the network side.
  • the RRC reconfiguration message DU switch
  • Step 2104 The CU receives the RLC status report reported by the UE, and sends the RLC PDU data that is not successfully received by the UE in the RLC status report to the target DU in advance.
  • Step 2105 The target DU receives the RLC PDU data sent by the CU in advance and caches.
  • Step 2106 the UE performs handover from the source DU to the target DU.
  • Step 2107 After the handover of the UE to the target DU is completed, the UE sends an RRC reconfiguration complete message to the target DU.
  • Step 2108 After the handover of the UE to the target DU is completed, the UE actively triggers an RLC status report to the target DU.
  • Step 2109 After the UE-to-target DU handover is completed, the target DU retransmits the RLC PDU data that the UE fails to receive in the RLC PDU data that is buffered in advance to the UE according to the latest RLC status report reported by the UE.
  • Step 2110 After the UE completes the target DU handover, the CU sends new RLC PDU data to the UE through the target DU.
  • the embodiment of the present application further provides a computer storage medium storing computer executable instructions, and the computer executable instructions are implemented to implement the data transmission method applied to the UE.
  • the embodiment of the present application further provides a computer storage medium storing computer executable instructions, and the computer executable instructions are implemented to implement the data transmission method applied to the CU.
  • the embodiment of the present application further provides a computer storage medium storing computer executable instructions, and the computer executable instructions are implemented to implement the data transmission method applied to the DU.
  • the foregoing storage medium may include, but not limited to, a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • mobile hard disk a magnetic disk
  • magnetic disk a magnetic disk
  • optical disk a variety of media that can store program code.
  • the processor executes the method steps of the above embodiments in accordance with program code already stored in the storage medium.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function.
  • This application is not limited to any specific combination of hardware and software.
  • the RLC report is actively triggered by the UE and sent to the target DU.
  • the target DU may obtain the RLC PDU data that is not successfully received by the UE according to the RLC report, and retransmit the data to the UE, and resolve the inter-DU handover under the same CU. It is easy to cause the loss of downlink RLC PDU data, which satisfies the seamless handover requirements of users.
  • the problem that the switching between DUs in the same CU is easy to cause downlink data loss is effectively solved, and the problem that the downlink data retransmission delay is large is also solved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)
  • Communication Control (AREA)
  • Signal Processing For Digital Recording And Reproducing (AREA)

Abstract

本文公布了一种数据传输方法及装置、计算机存储介质，该方法可以包括：源DU上报PDCP传输状态报告至元CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。

Description

一种数据传输方法及装置、计算机存储介质
相关申请的交叉引用
本申请基于申请号为201710147146.2、申请日为2017年03月13日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及无线通信领域，具体涉及一种数据传输方法及装置、计算机存储介质。
背景技术
第五代(5G，5th Generation)网络架构具有革新性和组网的灵活性，在5G网络中无线接入网侧的基础处理单元(BBU，Building Base band Unit)被分离为集中式处理单元(CU，Centralized Unit)和分布式处理单元(DU，Distributed Unit)两个功能实体，通过集中式CU来控制多个DU，可以实现云架构的基带集中处理和针对用户的远端分布式提供服务。在CU-DU分离的网络架构中，时延不敏感的网络功能放在CU中，时延敏感的网络功能放在DU中，CU与DU之间通过理想/或非理想前传(fronthaul)进行传输和连接，实现多点协作化功能，并可以支持分离或一体化站点的灵活组网。
在5G的CU-DU架构下，用户在确认模式下数据传输过程中在同一CU下的DU间切换容易导致下行RLC PDU数据丢失，这是亟待解决的问题。
发明内容
为了解决上述技术问题，本申请实施例提供了一种数据传输方法及装 置。
本申请提供提供了如下方案：
一种数据传输方法，包括：
源DU上报PDCP传输状态报告至CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
一种数据传输装置，包括：
触发单元，配置为上报PDCP传输状态报告至CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
一种数据传输装置，包括：处理器和存储器，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
上报PDCP传输状态报告至CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
一种数据传输方法，包括：
目标DU获取未被UE成功接收的PDCP PDU数据并重传至所述UE。
一种数据传输装置，包括：
第一接收单元，配置为获取未被UE成功接收的PDCP PDU数据；
第一发送单元，配置为将所述未被UE成功接收的PDCP PDU数据重传至所述UE。
一种数据传输装置，包括：处理器和存储器，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
获取未被UE成功接收的PDCP PDU数据并重传至所述UE。
一种数据传输方法，包括：
CU接收PDCP传输状态报告，所述PDCP状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收；
所述CU根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至目标DU。
一种数据传输装置，包括：
第二接收单元，配置为接收PDCP传输状态报告，所述PDCP状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收；
第二发送单元，配置为根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至所述目标DU。
一种数据传输装置，包括：处理器和存储器，其特征在于，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
接收PDCP传输状态报告，所述PDCP状态报告用于CU确定哪些PDCP协议数据单元PDU数据未被UE成功接收；
根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至目标DU。
此外，本申请实施例还提供一种计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述应用于UE的数据传输方法。
此外，本申请实施例还提供一种计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述应用于CU的数据传输方法。
此外，本申请实施例还提供一种计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述应用于DU的数据传输方法。
本申请提供的方法包括如下效果：
本申请至少一个实施例中，由UE主动触发PDCP报告并送至目标DU，目标DU可以根据该PDCP报告获取未被UE成功接收的PDCP PDU数据并重传至UE，解决了同一CU下的DU间切换容易导致下行PDCP PDU数据丢失的问题，满足了用户的无缝切换需求。
本申请至少一个实施例中，由UE主动触发RLC报告并送至目标DU，目标DU可以根据该RLC报告获取未被UE成功接收的RLC PDU数据并重传至UE，解决了同一CU下的DU间切换容易导致下行RLC PDU数据丢失的问题，满足了用户的无缝切换需求。
本申请至少一个实施例中，不仅有效解决了同一CU下的DU间切换容易导致下行数据丢失的问题，而且还解决了下行数据重传时延较大的问题。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1为相关技术中方案option2的CU-DU分离示意图；
图2为相关技术中方案option3的CU-DU分离示意图；
图3为相关技术中同一CU控制下DU切换示意图；
图4为本申请实施例一应用于UE的数据传输方法的流程示意图；
图5为本申请实施例一应用于UE的数据传输装置的组成结构示意图；
图6为本申请实施例一应用于DU的数据传输方法的流程示意图；
图7为本申请实施例一应用于DU的数据传输装置的组成结构示意图；
图8为本申请实施例一应用于CU的数据传输方法的流程示意图；
图9为本申请实施例一应用于CU的数据传输装置的组成结构示意图；
图10为本申请实施例二应用于UE的数据传输方法的流程示意图；
图11为本申请实施例二应用于UE的数据传输装置的组成结构示意图；
图12为本申请实施例二应用于DU的数据传输方法的流程示意图；
图13为本申请实施例二应用于DU的数据传输装置的组成结构示意图；
图14为本申请实施例二应用于CU的数据传输方法的流程示意图；
图15为本申请实施例二应用于CU的数据传输装置的组成结构示意图；
图16为本申请实例1的DU间确认模式切换过程以及数据传输流程示意图；
图17为本申请实例2的DU间确认模式切换过程以及数据传输流程示意图；
图18为本申请实例3的DU间确认模式切换过程以及数据传输流程示意图；
图19为本申请实例4的DU间确认模式切换过程以及数据传输流程示意图；
图20为本申请实例5的DU间确认模式切换过程以及数据传输流程示意图；
图21为本申请实例6的DU间确认模式切换过程以及数据传输流程示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚明白，下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
相关技术中，在CU-DU高层协议分离的架构中有option2和option3两种方案。
如图1，option 2是在分组数据汇聚协议(PDCP，Packet Data Convergence Protocol)和无线链路控制(RLC，Radio Link Control)之间进行划分，即PDCP及其PDCP以上放在CU，RLC及其RLC以下的实体放在DU。
如图2所示，option 3是在RLC内部进行划分，即部分RLC功能、PDCP及其PDCP以上放在CU，部分RLC功能及其以下的实体放在DU。在本文中在CU中的部分RLC定义为RLC-H，对在DU中的部分RLC定义为RLC-L。其中，RLC-H功能为非时延敏感功能，包括自动重传请求(ARQ，Automatic Repeat Request)、非调度相关的分段和/或级联。RLC-L功能为时延敏感功能(比如实时分段功能)，根据MAC调度指示对来自CU的协议数据单元(Protocol Data Unit，PDU)数据包实时进行处理。
如图3所示，由于CU集中式部署，一个服务小区的CU会连接多个DU，从用户当前CU控制的一个DU的服务范围内移动到该CU控制的另一个DU的服务范围，用户也需要从当前DU切换到目标DU。并且这种内部CU(intra-CU)控制下的DU切换由于DU会密集部署，会比较频繁。
在option2的intra-CU DU切换过程中，由于RLC功能位于DU，那么当用户从源DU切换到目标DU以后，在下行数据传输过程中，源DU上的RLC发送缓冲区的数据会清除，这样原DU上没有发送成功的RLC PDU数据就会丢失。切换的目标DU并不清楚源DU上有哪些RLC PDU数据并没有传输成功。
在option3的intra-CU DU切换过程中，由于RLC功能一部分位于DU，另一部分包含RLC ARQ的那部分位于CU，那么当用户从源DU切换到目标DU之后，由于为了节省状态报告发送资源，现有RLC的状态报告并非实时的，而是受到RLC轮询、状态报告发送机制和状态禁止定时器控制，通常状态报告发送之间存在较长的时间间隔(gap)。那么在option3切换到目标DU以后，发送端CU可能并没有发起实时的轮询，或者用户RLC可能不能及时上报RLC状态报告给CU，或者最新的RLC状态报告在DU链路切换过程中已经丢失。这样使得CU无法及时发现需要重传的RLC PDU数据，导致用户传输时延加大，甚至丢包。
综上，在intra-CU的DU间切换的时候，在option 2和option3中都会存在下行RLC PDU数据的重传时延加大和丢失的风险。如果用户数据传输RLC是配置在AM模式下，那么这种RLC PDU数据在DU之间切换过程中的丢失，就会对用户服务质量带来严重的负面影响。以上下行RLC PDU数据在DU切换过程中的丢失，在单连接(UE连接到一个DU)、双连接或者多连接中都是类似的(UE同时连接到两个或者多个DU)。
所以相关技术中的CU-DU架构下，用户在同一CU下的DU间切换容易导致下行数据丢失，不满足无缝切换的要求。针对该问题，本申请提出一种数据传输方案，该数据传输方案适用于CU-DU组网架构下用户在DU之间切换的过程，能够解决5G的CU-DU架构下用户在确认模式下数据传输过程中在同一CU下的DU间切换容易导致下行RLC PDU数据丢失的问题。
实施例一
本实施例可适用于图1所示CU-DU组网架构。
一种数据传输方法，应用于源DU，如图4所示，包括：
步骤401，源DU上报PDCP传输状态报告至CU，所述PDCP传输状 态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收；
步骤402，所述CU通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
在一种实现方式中，所述CU将所述未被UE成功接收的PDCP PDU数据发送给目标DU，通过所述目标DU将所述未被UE成功接收的PDCP PDU数据发送给UE。。
一种数据传输装置，应用于源DU，如图5所示，包括：
触发单元51，配置为上报PDCP传输状态报告至CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
一种数据传输装置，包括：处理器和存储器，所述数据传输装置应用于UE，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
上报PDCP传输状态报告至CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
一种数据传输方法，应用于目标DU，如图6所示，可以包括：
步骤601，目标DU获取未被UE成功接收的PDCP PDU数据并重传至所述UE。
在一种实现方式中，所述目标DU获取未被UE成功接收的PDCP PDU数据并重传至所述UE，包括：
目标DU接收来自CU的PDCP PDU数据并缓存；
所述目标DU将所述缓存的PDCP PDU数据中未被UE成功接收的PDCP PDU数据重新发送给UE。
在另一种实现方式中，所述目标DU获取未被UE成功接收的PDCP  PDU数据并重传至所述UE，包括：
目标DU接收CU发送的未被UE成功接收的PDCP PDU数据并缓存；
所述目标DU将所述缓存的PDCP PDU数据重新发送给UE。
一种数据传输装置，应用于目标DU，如图7所示，可以包括：
第一接收单元71，配置为获取未被UE成功接收的PDCP PDU数据；
第一发送单元72，配置为将所述未被UE成功接收的PDCP PDU数据重传至所述UE。
在一实施方式中，所述第一接收单元71，配置为接收来自CU的PDCP PDU数据并缓存；
所述第一发送单元72，配置为将所述缓存的PDCP PDU数据中未被UE成功接收的PDCP PDU数据重新发送给UE。
在另一实施方式中，所述第一接收单元71，配置为接收CU发送的未被UE成功接收的PDCP PDU数据并缓存；
所述第一发送单元72，配置为将所述缓存的PDCP PDU数据重新发送给UE。
一种数据传输装置，包括：处理器和存储器，所述数据传输装置应用于DU，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
获取未被UE成功接收的PDCP PDU数据并重传至所述UE。
一种数据传输方法，应用于CU，如图8所示，可以包括：
步骤801，CU接收PDCP传输状态报告，所述PDCP状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收。
步骤802，所述CU根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至目标DU，并通过所述目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
在一实施方式中，所述CU根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至目标DU，包括：
所述CU缓存PDCP PDU数据；
所述CU根据所述PDCP状态报告，将所述缓存的PDCP PDU数据中未被UE成功接收的PDCP PDU数据重新发送给目标DU。
一种数据传输装置，应用于CU，如图9所示，可以包括：
第二接收单元91，配置为接收PDCP传输状态报告，所述PDCP状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收；
第二发送单元92，配置为根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至所述目标DU。
在一实施方式中，还包括：
缓存单元93，配置为缓存未被UE成功接收的PDCP PDU数据；
所述第二发送单元92，配置为根据所述PDCP状态报告，将所述缓存的PDCP PDU数据中未被UE成功接收的PDCP PDU数据重新发送给目标DU。
一种数据传输装置，包括：处理器和存储器，所述数据传输装置应用于CU，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
接收PDCP传输状态报告，所述PDCP状态报告用于CU确定哪些PDCP协议数据单元PDU数据未被UE成功接收；
根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至目标DU。
本实施例中，intra CU在DU间切换时可以提前向目标DU发送数据，以便目标DU能够将相应数据重传至UE。具体的，当网络侧判断DU间可能进行切换，或者网络侧在进行DU间切换的准备工作时，CU可以提前一 段时间将向源DU发送的PDCP PDU数据同时向目标DU发送一份完全相同的拷贝(具有相同的序列(SN)号和内容)。这样，目标DU在切换完成时，接收到PDCP状态报告后，可以直接根据所述PDCP状态报告获知UE未能成功接收的PDCP情况，将CU提前缓存在目标DU中的对应PDCP PDU数据重传到UE，从而缩小重传时延。
在一些实现方式中，如果UE不支持DU切换完成后主动触发PDCP状态报告的功能，CU也可以在切换时，向UE发送PDCP轮询，要求UE上报PDCP状态报告。具体的，在网络侧判断intra CU的DU间需要切换前，CU可以向UE发送一个PDCP轮询包，UE接收到所述PDCP轮询包后，可以向网络侧上报PDCP状态报告。CU接收到PDCP状态报告以后，可以将新传的数据和UE未能成功接收的PDCP PDU数据同时向源DU和目标DU发送，这样可以降低提前向目标DU缓冲数据的冗余性。
在一些实现方式中，为减少提前发送数据的冗余度，源DU也可以根据UE反馈的RLC状态报告，知道自己有哪些PDCP PDU数据未能成功传输，基于此，源DU可以构造一个PDCP状态报告并发送给CU，CU接收到该PDCP状态报告以后，可以将新传的数据和UE未能成功接收的PDCP PDU数据同时发送至源DU和目标DU，以便目标DU将相应的PDCP PDU数据发送至UE，从而避免丢包。
本实施例的上述数据传输方法及装置，由UE主动触发PDCP报告并送至目标DU，目标DU可以根据该PDCP报告获取未被UE成功接收的PDCP PDU数据并重传至UE，解决了同一CU下的DU间切换容易导致下行PDCP PDU数据丢失的问题，满足了用户的无缝切换需求。
此外，本实施例中由CU提前将未被UE成功接收的PDCP PDU数据送至目标DU并缓存，在DU切换完成之后目标DU可以直接根据PDCP状态报告从缓存中获取相应的PDCP PDU数据并重传至UE，从而解决了下 行数据重传时延较大的问题。
实施例二
本实施例可适用于图2所示CU-DU组网架构。
一种数据传输方法，应用于UE，如图10所示，包括：
步骤1001，从源DU切换至目标DU的之前、过程中或完成后，主动触发并上报RLC状态报告至网络侧，所述RLC状态报告用于指示哪些RLC PDU数据未被UE成功接收；
步骤1002，接收网络侧重新发送的未被UE成功接收的RLC PDU数据。
一种数据传输装置，应用于UE，如图11所示，包括：
第四触发单元111，用于从源DU切换至目标DU的之前、过程中或完成后，主动触发并上报RLC状态报告至网络侧，所述RLC状态报告用于指示哪些RLC PDU数据未被UE成功接收；
第四接收单元112，用于接收网络侧重新发送的未被UE成功接收的RLC PDU数据。
一种数据传输装置，包括：处理器和存储器，所述数据传输装置应用于UE，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
从源DU切换至目标DU的之前、过程中或完成后，主动触发并上报RLC状态报告至网络侧，所述RLC状态报告用于指示哪些RLC PDU数据未被UE成功接收；
接收网络侧重新发送的未被UE成功接收的RLC PDU数据。
一种数据传输方法，应用于DU，如图12所示，包括：
步骤1201，接收来自UE的RLC状态报告，所述RLC状态报告用于 指示哪些RLC PDU数据未被UE成功接收；
步骤1202，根据所述RLC状态报告，从CU获取未被UE成功接收的RLC PDU数据并重传至所述UE。
在一种实现方式中，步骤1202中根据所述RLC状态报告，从CU获取未被UE成功接收的RLC PDU数据并重传至所述UE，可以包括：将所述RLC状态报告透传至CU；接收来自所述CU的未被UE成功接收的RLC PDU数据；将所述未被UE成功接收的RLC PDU数据重传至所述UE。
在另一种实现方式中，步骤1202中根据所述RLC状态报告，从CU获取未被UE成功接收的RLC PDU数据并重传至所述UE，可以包括：将所述RLC状态报告透传至CU；接收来自所述CU的所述未被UE成功接收的RLC PDU数据并缓存；在UE到所述目标DU切换完成后，将所述缓存的RLC PDU数据重传至所述UE。
一种数据传输装置，应用于DU，如图13所示，可以包括：
第五接收单元131，用于接收来自用户设备UE的RLC状态报告，所述RLC状态报告用于指示哪些RLC PDU数据未被UE成功接收；
第五重传单元132，用于根据所述RLC状态报告，从CU获取未被UE成功接收的RLC PDU数据并重传至所述UE。
在一种实现方式中，所述第五重传单元132，具体可用于将所述RLC状态报告透传至CU，接收来自所述CU的未被UE成功接收的RLC PDU数据，将所述未被UE成功接收的RLC PDU数据重传至所述UE。
在另一种实现方式中，上述数据传输装置还可以包括：第五缓存单元133，用于接收来自所述CU的所述未被UE成功接收的RLC PDU数据并缓存；所述第五重传单元132，具体可用于将所述RLC状态报告透传至CU，并在UE到所述目标DU切换完成后，将所述第五缓存单元中缓存的RLC PDU数据重传至所述UE。
一种数据传输装置，包括：处理器和存储器，所述数据传输装置应用于DU，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
接收来自UE的RLC状态报告，所述RLC状态报告用于指示哪些RLC PDU数据未被UE成功接收；
根据所述RLC状态报告，从CU获取未被UE成功接收的RLC PDU数据并重传至所述UE。
一种数据传输方法，应用于CU，如图14所示，可以包括：
步骤1401，接收来自目标DU的RLC状态报告，所述RLC状态报告用于指示哪些RLC PDU数据未被UE成功接收；
步骤1402，将所述RLC状态报告指示未被UE成功接收的RLC PDU数据发送给所述目标DU。
一种数据传输装置，应用于CU，如图15所示，可以包括：
第六接收单元151，用于接收来自目标DU的RLC状态报告，所述RLC状态报告用于指示哪些RLC PDU数据未能被UE成功接收；
第六发送单元152，用于将所述RLC状态报告指示未被UE成功接收的RLC PDU数据发送给所述目标DU。
一种数据传输装置，包括：处理器和存储器，所述数据传输装置可以应用于CU，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
接收来自目标DU的RLC状态报告，所述RLC状态报告用于指示哪些RLC PDU数据未被UE成功接收；
将所述RLC状态报告指示未被UE成功接收的RLC PDU数据发送给所述目标DU。
本实施例中，当UE从源DU切换到目标DU完成前或者切换完成后， UE可以主动触发一个RLC状态报告上报给网络侧，这可以用于图2所示的CU-DU架构，使得网络侧CU可以根据UE上报的RLC状态报告，知道哪些下行RLC数据包没有传输成功，并用于选择性RLC重传。
本实施例中，目标DU接收到UE上报的RLC状态报告之后，如果目标DU预先缓存了CU提前发送的RLC PDU数据，目标DU可以直接解析RLC状态报告，并选择性从缓存中读取未被UE成功接收的RLC PDU数据并重传给UE；如果目标DU未预先缓存RLC PDU数据，或者DU不具备解析RLC状态报告的能力，目标DU可以将RLC状态报告透传到CU，CU可以解析RLC状态报告，并选择性将UE未能成功接收的RLC PDU数据通过目标DU重传给UE。
在一种实现方式中，UE从源DU切换到目标DU完成时，当CU接收到UE上报的RLC状态报告后，CU可以根据RLC状态报告确定哪些下行RLC PDU数据没有被UE成功接收，CU可以选择性的将这些没有被UE成功接收(也就是说，源DU上未能成功传输)的RLC PDU数据通过目标DU重传给UE。
在另一种实现方式中，DU间切换时CU可以提前向目标DU发送RLCPDU数据，以便目标DU将相应的RLC PDU数据重传至UE。具体的，在DU切换准备过程阶段，CU如果收到UE上报的RLC状态报告，CU可以提前将所述RLC状态报告中指示需要重传的RLC PDU数据都发送到目标DU，目标DU可以预先缓存这些数据，这样，当用户完成到目标DU的切换以后，目标DU可以快速向UE发送重传这些RLC PDU数据，从而降低发送时延。
本实施例中的上述数据传输方法及装置，由UE主动触发RLC报告并送至目标DU，目标DU可以根据该RLC报告获取未被UE成功接收的RLC PDU数据并重传至UE，解决了同一CU下的DU间切换容易导致下行RLC  PDU数据丢失的问题，满足了用户的无缝切换需求。
此外，本实施例中由CU提前将未被UE成功接收的RLC PDU数据送至目标DU并缓存，在DU切换完成之后目标DU可以直接根据RLC状态报告从缓存中获取相应的RLC PDU数据并重传至UE，从而解决了下行数据重传时延较大的问题。
下面以实例的形式详细说明本申请数据传输的多种具体实现方式。
实例1
本实例提供一种DU间确认模式切换过程以及数据传输流程，本实例适用于图1所示架构，CU支持向UE发起PDCP轮询和向目标DU预缓存数据。
本实例中，准备进行DU间切换时，CU可以向UE发起PDCP轮询，并根据轮询结果向目标DU预先缓存数据，通过PDCP轮询，可以相对避免那些已经传输成功的PDCP PDU数据在目标DU的预缓存。如图16所示，本实例的步骤如下：
步骤1601，网络侧根据DU间切换的测量结果，准备进行DU之间的切换。
步骤1602，CU通过源DU发出一个PDCP状态轮询PDU(PDCP status report Polling)数据包给UE。
步骤1603，UE接收到PDCP轮询包以后，向网络端回应一个PDCP状态报告(PDCP status report)，所述PDCP状态报告用于上报UE在PDCP层的数据接收情况。
步骤1604至步骤1605，CU接收UE上报的PDCP状态报告，将下发给源DU的PDCP PDU数据中所述PDCP状态报告指示的、UE未成功接收的PDCP数据包同时发送到目标DU。
图16中标注的New PDUS SN(Xn..Xm)为CU新传给源DU的PDCP  PDU数据，图16中标注的Unacknowledged PDCP PDU数据S SN(Yn..Ym)为UE尚未成功接收的PDCP PDU数据。
步骤1606，目标DU接收并缓存CU提前发送的数据。
步骤1607，网络侧完成目标DU的数据预缓存并完成目标DU的切换准备工作以后，通过源DU下发RRC重配置消息给UE，通知UE进行DU的切换。
可选地，还包括：步骤1608(图中未示出)，UE执行从源DU到目标DU的切换。
步骤1609，UE到目标DU的切换完成后，UE向目标DU发送RRC重配置完成消息。
步骤1610，UE到目标DU切换完成后，UE主动触发一个PDCP状态报告并发送到目标DU，所述PDCP状态报告用于通知网络侧有哪些PDCP PDU数据未能成功接收。
步骤1611至步骤1612，目标DU接收所述PDCP状态报告，直接解析所述PDCP状态报告，并将来自CU的缓存数据中所述PDCP状态报告指示的、UE未成功接收的PDCP PDU数据重新发送给UE。
步骤1613，UE完成到目标DU切换以后，CU通过目标DU向UE发送新的PDCP PDU数据。
实例2
本实例提供一种DU间确认模式切换过程以及数据传输流程，本实例适用于图1所示架构，其中，CU支持目标DU预缓存数据。本实例和实例1的区别在与本例子中CU可以不用向用户发起PDCP状态轮询过程，而是切换准备过程中提前一段时间向目标DU直接缓存数据，如图17所示，本实例的步骤如下：
步骤1701：网络侧根据DU间切换的测量结果，准备进行DU之间的 切换。
步骤1702至步骤1703，CU提前一段时间，直接将下发给源DU的PDCP PDU数据同时也发送一份给目标DU，如图17中标注的SN(Xn..Xm)表示该数据。
步骤1704，目标DU接收CU提前发送的PDCP PDU数据并缓存。
步骤1705，网络侧完成目标DU的数据预缓存并完成目标DU的切换准备工作以后，通过源DU下发RRC重配置消息给UE，通知UE进行DU的切换。
可选地，还包括：步骤1706(图中未示出)，UE执行从源DU到目标DU的切换。
步骤1707，UE到目标DU的切换完成后，UE向目标DU发送RRC重配置完成消息。
步骤1708，UE到目标DU切换完成后，UE主动触发一个PDCP状态报告发送到目标DU，所述PDCP状态报告用于通知网络侧哪些PDCP PDU数据未能成功接收。
步骤1709至步骤1710，目标DU接收PDCP状态报告，直接解析所述PDCP状态报告，将预缓存的PDCP PDU数据中所述PDCP状态报告状态指示的UE未成功接收的PDCP PDU数据重新发送给UE。
步骤1711，UE完成到目标DU切换以后，CU通过目标DU向UE发送新的PDCP PDU数据。
实例3
本实例提供一种DU间确认模式切换过程以及数据传输流程，本实例适用于图1所示架构。本实例和实例1、实例2的区别在于，本例子中CU可以不用向用户发起PDCP状态轮询过程，也不向目标DU提前缓存数据，完成DU之间的无数据丢失切换。如图18所示，本实例的步骤如下：
步骤1801：网络侧根据DU间切换的测量结果，准备进行DU之间的切换。
步骤1802，网络侧通过源DU下发RRC重配置消息给UE，通知UE进行DU的切换。
步骤1803，UE执行从源DU到目标DU的切换。
步骤1804，UE到目标DU的切换完成后，UE向目标DU发送RRC重配置完成消息。
步骤1805，UE到目标DU切换完成后，UE主动触发一个PDCP状态报告发送到目标DU，所述PDCP状态报告用于通知网络侧有哪些PDCP PDU数据未能成功接收。目标DU接收到PDCP状态报告以后，目标DU将PDCP状态报告透传给CU。
步骤1806，CU根据接收的PDCP状态报告，将所述PDCP状态报告指示的UE未成功接收的PDCP PDU数据通过目标DU重新发送给UE。
步骤1807，UE完成到目标DU切换以后，CU通过目标DU向UE发送新的PDCP PDU数据。
实例4
本实例提供一种DU间确认模式切换过程以及数据传输流程，本实例适用于图1所示架构。本实例和前面实例的区别在于，本实例中DU支持根据自己对下行PDCP PDU数据的发送情况，以及RLC状态报告反馈，可以知道本DU哪些PDCP PDU数据没有被UE成功接收，可以构造PDCP状态报告向CU反馈当前PDCP的传输状态。如图19所示，本实例的步骤如下：
步骤1901，网络侧根据DU间切换的测量结果，准备进行DU之间的切换。
步骤1902，在切换准备过程中，源DU可以根据自己对下行PDCP PDU 数据的发送情况、以及UE反馈的RLC状态报告，可以知道本DU哪些PDCP PDU数据没有被UE成功接收，构造PDCP状态报告并送至CU，以向CU反馈当前PDCP的传输状态。
步骤1903，CU根据源DU上报的PDCP状态报告，将源DU还未发送的PDCP PDU数据、以及已发送但未被UE成功接收的PDCP PDU数据发送到目标DU。
步骤1904，目标DU接收并缓存CU提前发送的数据。
步骤1905，网络侧通过源DU下发RRC重配置命令给UE，通知UE进行DU的切换。
步骤1906，UE执行从源DU到目标DU的切换。
步骤1907，UE到目标DU的切换完成后，UE向目标DU发送RRC重配置完成消息。
步骤1908，UE到目标DU切换完成后，UE主动触发一个PDCP状态报告并发送到目标DU，所述PDCP状态报告用于通知网络侧有哪些PDCP PDU数据未能成功接收。
步骤1909，目标DU接收到PDCP状态报告以后，DU可以直接解析PDCP状态报告。
步骤1910，DU根据解析得到的PDCP状态报告内容，将预缓存的数据中所述PDCP状态报告指示UE未成功接收的PDCP PDU数据重新发送给UE。
步骤1911，UE完成到目标DU切换以后，CU通过目标DU向UE发送新的PDCP PDU数据。
实例5
本实例提供一种DU间确认模式切换过程以及数据传输流程，本实例适用于图2所示架构，其中，UE侧在切换完成后主动触发RLC状态报告 到网络侧，如图20所示，本实例的步骤如下：
步骤2001，网络侧根据DU间切换的测量结果，准备进行DU之间的切换。
步骤2002，网络侧通过源DU下发RRC重配置消息给UE，通知UE进行DU的切换。
步骤2003，UE执行从源DU到目标DU的切换。
步骤2004，UE到目标DU的切换完成后，UE向目标DU发送RRC重配置完成消息。
步骤2005，UE到目标DU切换完成后，UE的RLC层主动触发一个RLC状态报告并发送到目标DU，用于通知网络侧有哪些RLC PDU数据未能被UE成功接收，目标DU接收到该RLC状态报告后直接透传给CU；
步骤2006，CU接收目标DU转发的RLC状态报告，将所述RLC状态报告指示UE未成功接收的RLC PDU数据通过所述目标DU重新发送给UE。
步骤2007，UE完成到目标DU切换以后，CU通过目标DU向UE发送新的RLC PDU数据。
实例6
本实例提供一种DU间确认模式切换过程以及数据传输流程，本实例适用于图2所示架构，其中，UE侧在切换完成前主动触发RLC状态报告到网络侧，如图21所示，本实例的步骤如下：
步骤2101，网络侧根据DU间切换的测量结果，准备进行DU之间的切换。
步骤2102，网络侧通过源DU下发RRC重配置命令给UE，通知UE进行DU的切换。
步骤2103，UE接收网络侧下发的RRC重配置消息(DU切换)后， 主动触发一个RLC状态报告并发送给网络侧。
步骤2104，CU接收UE上报的RLC状态报告，将RLC状态报告中指示UE未成功接收的RLC PDU数据提前发送给目标DU。
步骤2105，目标DU接收CU提前发送的RLC PDU数据并缓存。
步骤2106，UE执行从源DU到目标DU的切换。
步骤2107，UE到目标DU的切换完成后，UE向目标DU发送RRC重配置完成消息。
步骤2108，UE到目标DU的切换完成后，UE向目标DU主动触发一个RLC状态报告。
步骤2109，UE到目标DU切换完成后，目标DU根据UE最新上报的RLC状态报告，将提前缓存的RLC PDU数据中UE未能成功接收的RLC PDU数据重传至UE。
步骤2110，UE完成到目标DU切换以后，CU通过目标DU向UE发送新的RLC PDU数据。
此外，本申请实施例还提供一种计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述应用于UE的数据传输方法。
此外，本申请实施例还提供一种计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述应用于CU的数据传输方法。
此外，本申请实施例还提供一种计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述应用于DU的数据传输方法。
在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access  Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
在本实施例中，处理器根据存储介质中已存储的程序代码执行上述实施例的方法步骤。
本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机存储介质中，如只读存储器、磁盘或光盘等。上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本申请不限制于任何特定形式的硬件和软件的结合。
以上显示和描述了本申请的基本原理和主要特征和本申请的优点。本申请不受上述实施例的限制，上述实施例和说明书中描述的只是说明本申请的原理，在不脱离本申请精神和范围的前提下，本申请还会有各种变化和改进，这些变化和改进都落入要求保护的本申请范围内。
工业实用性
本申请的实施例中，由UE主动触发RLC报告并送至目标DU，目标DU可以根据该RLC报告获取未被UE成功接收的RLC PDU数据并重传至UE，解决了同一CU下的DU间切换容易导致下行RLC PDU数据丢失的问题，满足了用户的无缝切换需求。不仅有效解决了同一CU下的DU间切换容易导致下行数据丢失的问题，而且还解决了下行数据重传时延较大的问题。

Claims (16)

  1. 一种数据传输方法，包括：
    源分布式处理单元DU上报分组数据汇聚协议PDCP传输状态报告至集中式处理单元CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP协议数据单元PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
  2. 一种数据传输装置，包括：
    触发单元，配置为上报PDCP传输状态报告至CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
  3. 一种数据传输装置，包括：处理器和存储器，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
    上报PDCP传输状态报告至CU，所述PDCP传输状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收，并通过目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
  4. 一种数据传输方法，包括：
    目标DU获取未被UE成功接收的PDCP PDU数据并重传至所述UE。
  5. 根据权利要求4所述的数据传输方法，其中，所述目标DU获取未被UE成功接收的PDCP PDU数据并重传至所述UE，包括：
    目标DU接收来自CU的PDCP PDU数据并缓存；
    所述目标DU将所述缓存的PDCP PDU数据中未被UE成功接收的PDCP PDU数据重新发送给UE。
  6. 根据权利要求4所述的数据传输方法，其中，所述目标DU获取未被UE成功接收的PDCP PDU数据并重传至所述UE，包括：
    目标DU接收CU发送的未被UE成功接收的PDCP PDU数据并缓存；
    所述目标DU将所述缓存的PDCP PDU数据重新发送给UE。
  7. 一种数据传输装置，包括：
    第一接收单元，配置为获取未被UE成功接收的PDCP PDU数据；
    第一发送单元，配置为将所述未被UE成功接收的PDCP PDU数据重传至所述UE。
  8. 根据权利要求7所述的装置，其中，
    所述第一接收单元，配置为接收来自CU的PDCP PDU数据并缓存；
    所述第一发送单元，配置为将所述缓存的PDCP PDU数据中未被UE成功接收的PDCP PDU数据重新发送给UE。
  9. 根据权利要求7所述的装置，其中，
    所述第一接收单元，配置为接收CU发送的未被UE成功接收的PDCP PDU数据并缓存；
    所述第一发送单元，配置为将所述缓存的PDCP PDU数据重新发送给UE。
  10. 一种数据传输装置，包括：处理器和存储器，其特征在于，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
    获取未被UE成功接收的PDCP PDU数据并重传至所述UE。
  11. 一种数据传输方法，包括：
    CU接收PDCP传输状态报告，所述PDCP状态报告用于所述CU确定哪些PDCP PDU数据未被UE成功接收；
    所述CU根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至目标DU。
  12. 根据权利要求11所述的方法，其中，所述CU根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至目标DU，包括：
    所述CU缓存PDCP PDU数据；
    所述CU根据所述PDCP状态报告，将所述缓存的PDCP PDU数据中未被UE成功接收的PDCP PDU数据重新发送给目标DU，并通过所述目标DU向UE重传所述未被UE成功接收的PDCP PDU数据。
  13. 一种数据传输装置，包括：
    第二接收单元，配置为接收PDCP传输状态报告，所述PDCP状态报 告用于所述CU确定哪些PDCP PDU数据未被UE成功接收；
    第二发送单元，配置为根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至所述目标DU。
  14. 根据权利要求13所述的数据传输装置，其中，还包括：
    缓存单元，配置为缓存未被UE成功接收的PDCP PDU数据；
    所述第二发送单元，配置为根据所述PDCP状态报告，将所述缓存的PDCP PDU数据中未被UE成功接收的PDCP PDU数据重新发送给目标DU。
  15. 一种数据传输装置，包括：处理器和存储器，其特征在于，所述存储器存储有计算机可执行指令，所述计算机可执行指令被所述处理器执行时实现如下方法：
    接收PDCP传输状态报告，所述PDCP状态报告用于CU确定哪些PDCP协议数据单元PDU数据未被UE成功接收；
    根据所述PDCP传输状态报告，获取未被UE成功接收的PDCP PDU数据并重新发送至目标DU。
  16. 一种计算机存储介质，其上存储有计算机可执行指令，该计算机可执行指令被处理器执行时实现权利要求1所述的方法步骤，或者权利要求4至6任一项所述的方法步骤，或者权利要求11至12任一项所述的方法步骤。
PCT/CN2018/078826 2017-03-13 2018-03-13 一种数据传输方法及装置、计算机存储介质 WO2018166442A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
DK18766862.9T DK3598797T3 (da) 2017-03-13 2018-03-13 Fremgangsmåde og enhed til dataoverføring og computerlagringsmedium
EP18766862.9A EP3598797B1 (en) 2017-03-13 2018-03-13 Method and device for data transmission, and computer storage medium
FIEP18766862.9T FI3598797T3 (fi) 2017-03-13 2018-03-13 Menetelmä ja laite tiedonsiirtoon sekä tietokoneen tallennusväline
US16/493,731 US11533775B2 (en) 2017-03-13 2018-03-13 Method and device for data transmission, and computer storage medium
US17/987,762 US11864275B2 (en) 2017-03-13 2022-11-15 System for data transmission

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710147146.2A CN108574967B (zh) 2017-03-13 2017-03-13 一种数据传输方法及装置
CN201710147146.2 2017-03-13

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/493,731 A-371-Of-International US11533775B2 (en) 2017-03-13 2018-03-13 Method and device for data transmission, and computer storage medium
US17/987,762 Continuation US11864275B2 (en) 2017-03-13 2022-11-15 System for data transmission

Publications (1)

Publication Number Publication Date
WO2018166442A1 true WO2018166442A1 (zh) 2018-09-20

Family

ID=63521710

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/078826 WO2018166442A1 (zh) 2017-03-13 2018-03-13 一种数据传输方法及装置、计算机存储介质

Country Status (6)

Country Link
US (2) US11533775B2 (zh)
EP (1) EP3598797B1 (zh)
CN (1) CN108574967B (zh)
DK (1) DK3598797T3 (zh)
FI (1) FI3598797T3 (zh)
WO (1) WO2018166442A1 (zh)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018170377A1 (en) * 2017-03-17 2018-09-20 Intel Corporation Re-transmission of pdcp pdus by centralized nodes of a ran architecture
CN108631961A (zh) * 2017-03-24 2018-10-09 中国移动通信有限公司研究院 一种多连接下实现多链路重传的方法及基站
GB2574876A (en) * 2018-06-21 2019-12-25 Tcl Communication Ltd Transmission techniques in a cellular network
CN111132244A (zh) * 2018-10-31 2020-05-08 电信科学技术研究院有限公司 一种切换方法、装置及终端
CN109756942B (zh) * 2019-03-05 2021-06-22 维沃移动通信有限公司 一种切换方法、终端及网络设备
WO2020259256A1 (en) * 2019-06-28 2020-12-30 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for flow control
CN117440433A (zh) 2019-06-28 2024-01-23 瑞典爱立信有限公司 用于流控制的方法和装置
CN112423409A (zh) * 2019-08-22 2021-02-26 中兴通讯股份有限公司 一种分布式单元
US11546812B2 (en) * 2019-09-23 2023-01-03 Verizon Patent And Licensing Inc. Systems and methods for distributed unit handover
KR20220103627A (ko) * 2019-11-21 2022-07-22 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 Daps 핸드오버 방법, 사용자 기기, 컴퓨터 판독 가능한 매체
CN113840281A (zh) * 2020-06-23 2021-12-24 展讯通信（上海）有限公司 数据传输方法、设备、装置及存储介质
CN111935794B (zh) * 2020-07-02 2021-06-04 四川创智联恒科技有限公司 一种缩短切换时延的数据处理方法
CN113938962A (zh) * 2020-07-13 2022-01-14 夏普株式会社 切换信息报告方法及用户设备
US20220201786A1 (en) * 2020-12-18 2022-06-23 Mediatek Inc. Methods and apparatus to reduce packet latency in multi-leg transmission
CN117202402A (zh) * 2022-05-16 2023-12-08 大唐移动通信设备有限公司 交互方法和相关设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101779493A (zh) * 2007-08-08 2010-07-14 高通股份有限公司 在无线数据分组通信系统中的可避免用户数据丢失的切换
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090087779A (ko) * 2008-02-13 2009-08-18 삼성전자주식회사 이동 통신 시스템에서 우선 순위화 비트 레이트를 이용하여데이터를 전송하는 방법 및 장치
CN102056226B (zh) * 2009-11-10 2016-03-02 中兴通讯股份有限公司 Pdcp状态报告的获取方法和pdcp实体
KR101472100B1 (ko) * 2010-12-22 2014-12-11 주식회사 케이티 무선통신 시스템에서 기지국 장비 및 데이터 처리 방법
EP2835925B1 (en) 2013-08-09 2018-08-08 Panasonic Intellectual Property Corporation of America Efficient Status Reporting for UEs in dual connectivity during mobility
CN104066128B (zh) * 2014-06-27 2017-06-23 京信通信系统（中国）有限公司 一种数据发送方法及装置
US10178702B2 (en) * 2016-06-10 2019-01-08 Futurewei Technologies, Inc. System and method for cell switching
EP3494756B1 (en) * 2016-08-09 2024-10-02 Samsung Electronics Co., Ltd. Method and apparatus for managing user plane operation in wireless communication system
CN106538037B (zh) * 2016-09-26 2019-10-15 北京小米移动软件有限公司 无线承载的配置方法、装置及系统
CN110383888B (zh) * 2017-03-07 2021-08-27 Lg电子株式会社 用于在cu-du切分场景下发送数据的方法和装置
ES2841848T3 (es) * 2017-05-05 2021-07-09 Samsung Electronics Co Ltd Procedimiento para establecer una interfaz de enlace de recorrido frontal y estación base
US20180376380A1 (en) * 2017-06-23 2018-12-27 Huawei Technologies Co., Ltd. Exposure of capabilities of central units and distributed units in base station entities for admission control

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101779493A (zh) * 2007-08-08 2010-07-14 高通股份有限公司 在无线数据分组通信系统中的可避免用户数据丢失的切换
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ALTIOSTAR NETWORKS: "High-Layer Split Option", 3GPP TSG RAN WG3 MEETING #95 R3-170589, 17 February 2017 (2017-02-17), XP051237487 *
HUAWEI: "Reconsideration of higher layer split options", 3GPP TSG-RAN3 MEETING NR#1 R3-170173, 19 January 2017 (2017-01-19), XP051204427 *
See also references of EP3598797A4 *
ZTE: "Consideration on RRC message transmission", 3GPP TSG RAN WG3 NR ADHOC R3-170102, 19 January 2017 (2017-01-19), XP051204259 *

Also Published As

Publication number Publication date
EP3598797A1 (en) 2020-01-22
CN108574967A (zh) 2018-09-25
EP3598797B1 (en) 2023-01-25
CN108574967B (zh) 2021-08-03
US11864275B2 (en) 2024-01-02
FI3598797T3 (fi) 2023-03-19
US11533775B2 (en) 2022-12-20
EP3598797A4 (en) 2020-11-18
DK3598797T3 (da) 2023-02-27
US20230208558A1 (en) 2023-06-29
US20200077466A1 (en) 2020-03-05

Similar Documents

Publication Publication Date Title
WO2018166442A1 (zh) 一种数据传输方法及装置、计算机存储介质
US11758612B2 (en) Communication method and related product
US10172048B2 (en) System for efficient recovery of node-B buffered data following MAC layer reset
KR101387475B1 (ko) 복수의 네트워크 엔터티를 포함하는 이동 통신시스템에서의 데이터 처리 방법
JP2010511320A (ja) 移動通信システムにおける状態報告送受信方法
WO2010127493A1 (zh) 切换处理方法、基站及中继节点
RU2781562C2 (ru) Способ связи и соответствующий продукт
AU2007203286A1 (en) System for efficient recovery of node-B buffered data following MAC layer reset

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018766862

Country of ref document: EP

Effective date: 20191014