WO2018171775A1 - 一种多连接下实现多链路重传的方法及基站、存储介质 - Google Patents

一种多连接下实现多链路重传的方法及基站、存储介质 Download PDF

Info

Publication number
WO2018171775A1
WO2018171775A1 PCT/CN2018/080365 CN2018080365W WO2018171775A1 WO 2018171775 A1 WO2018171775 A1 WO 2018171775A1 CN 2018080365 W CN2018080365 W CN 2018080365W WO 2018171775 A1 WO2018171775 A1 WO 2018171775A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
network element
links
data packet
retransmission
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/080365
Other languages
English (en)
French (fr)
Inventor
李刚
刘亮
陈亚迷
金巴
孙军帅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
Research Institute of China Mobile Communication Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
Research Institute of China Mobile Communication Co Ltd
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 China Mobile Communications Group Co Ltd, Research Institute of China Mobile Communication Co Ltd filed Critical China Mobile Communications Group Co Ltd
Priority to US16/497,227 priority Critical patent/US20200382243A1/en
Priority to EP18771616.2A priority patent/EP3595219B1/en
Publication of WO2018171775A1 publication Critical patent/WO2018171775A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/1607—Details of the supervisory signal
    • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1858—Transmission or retransmission of more than one copy of acknowledgement message
    • 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/1896—ARQ related signaling
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link 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/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
    • 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
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint
    • 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
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0097—Relays

Definitions

  • the present invention relates to a retransmission technology, and in particular, to a method, a base station, and a storage medium for implementing multi-link retransmission under multiple connections.
  • the access network logical nodes are composed of a base station (NB, Node B) and a radio network controller (RNC), and a 4G logical architecture.
  • the design is flatter and includes only enhanced base station (eNB) nodes.
  • eNB enhanced base station
  • the access network supports the logical functions of the distributed remote unit (RU) and the central unit (CU). Divided, and supports the protocol stack function to migrate between the CU and the distributed unit (DU, Distributed Unit).
  • the CU-DU two-level architecture of the access network has the advantages of achieving inter-cell cooperation gain and centralized load management; efficiently implementing centralized control under dense networking, such as multiple connections and dense switching; Gaining, enabling Network Function Virtualization (NFV, Network-Function Virtualization)/Software-defined networking (SDN) to meet the deployment requirements of certain 5G scenarios of operators.
  • NFV Network Function Virtualization
  • SDN Software-defined networking
  • the CU In the CU-DU two-level architecture, in the two network elements (CU and DU) located on the base station side, the CU is a centralized node, which can control and coordinate multiple cells, including protocol stack high-level control and data functions, and possibly Includes a portion of baseband processing.
  • the DU is a distributed unit that implements a radio frequency front end (RRH) function and other baseband processing functions.
  • the CU and the DU are connected through a preamble interface. Since only the Packet Data Convergence Protocol (PDCP) protocol stack is available on the CU, and the PDCP layer does not have the retransmission function, in a scenario where retransmission is required, if the terminal accesses multiple DUs, The terminal fails to transmit on one link. How to implement fast retransmission on another link is a problem that the access network CU-DU architecture needs to solve.
  • PDCP Packet Data Convergence Protocol
  • the embodiments of the present application are intended to provide a method for implementing multi-link retransmission under multiple connections, a base station, and a storage medium, which solve at least the problems existing in the prior art.
  • a method for implementing multi-link retransmission under multiple connections in the embodiment of the present application includes:
  • the second network element reports the status report
  • the other network element selects another link for data retransmission.
  • the method further includes:
  • the method further includes:
  • the second network element fragments the plurality of data packets
  • the plurality of fragmented data packets are provided to the terminal for transmission.
  • the other network link is selected to perform data retransmission, including:
  • the other network link is selected to perform data retransmission.
  • the method further includes:
  • the first network element selects, from the at least two links, a link transmission quality that is better than i links of the first link, where x is a positive integer greater than or equal to 1;
  • a base station where the base station includes a first network element and a second network element, where
  • the first network element is configured to access at least two links in the terminal, and receive a status report reported by the second network element when the terminal fails to transmit the data packet on one link; and parse the status report as the first When the link packet transmission fails, select another link for data retransmission;
  • the second network element is configured to report the status report, and interact with the first network element to implement data packet retransmission processing under multiple connection of the terminal.
  • the first network element is further configured to allocate a plurality of data packets after the splitting to the at least two links.
  • the second network element is further configured to: after the plurality of data packets are fragmented, provide a plurality of fragmented data packets to the terminal for transmission.
  • the first network element is further configured to:
  • the first network element is further configured to:
  • the first network element is further configured to:
  • a method for implementing multi-link retransmission under multiple connections in the embodiment of the present application includes:
  • the first network element receives the status report reported by the second network element
  • the other network element selects another link for data retransmission.
  • the method further includes:
  • a base station of an embodiment of the present application includes: a processor and a memory for storing a computer program executable on the processor;
  • the processor is configured to implement the steps of any one of the foregoing aspects when the computer program is executed.
  • a storage medium of the embodiment of the present application wherein a computer program is stored thereon, wherein the computer program is executed by the processor to implement the steps of the method according to any one of the above aspects.
  • the solution for implementing multi-link retransmission under multiple connections in the embodiment of the present application includes: when the terminal accesses at least two links, allocating a plurality of data packets after the splitting for the at least two links; When the data packet transmission fails on the link, the first network element interacts with the second network element according to the preset policy, so as to implement data packet retransmission processing under the terminal multiple connection.
  • the terminal accesses at least two links; when the terminal fails to transmit the data packet on one link, the second network element reports a status report; the first network element parses the status report as When the first link packet transmission fails, another link is selected for data retransmission. Therefore, when one link data packet transmission fails in the multiple links of the terminal, the fast retransmission of the transmission failure data packet can be implemented on the other link, thereby realizing the data packet retransmission processing under the terminal multiple connection. It is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is the CU and the second network element is the DU, and is not limited to the scenario of the CU-DU architecture.
  • FIG. 1 is a flowchart of implementing a method according to Embodiment 1 of the present application
  • FIG. 2 is a schematic diagram of a CU-DU architecture according to an embodiment of the present application.
  • FIG. 3 is a flowchart of an implementation scenario of an application scenario according to an embodiment of the present application.
  • FIG. 4 is a flowchart of an implementation scenario of an application scenario according to an embodiment of the present application.
  • FIG. 5 is a flowchart of an implementation scenario of an application scenario according to an embodiment of the present application.
  • FIG. 6 is a flowchart of an implementation scenario of an application scenario according to Embodiment 1 of the present application.
  • FIG. 7 is a flowchart of an implementation scenario of an application scenario according to an embodiment of the present application.
  • FIG. 8 is a flowchart of an implementation scenario of an application scenario according to an embodiment of the present application.
  • FIG. 9 is a flowchart of an implementation scenario of an application scenario according to an embodiment of the present application.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • a method for implementing multi-link retransmission under multiple connections in the embodiment of the present application includes:
  • Step 101 Access at least two links in the terminal
  • Step 102 When the terminal fails to transmit the data packet on one link, the second network element reports the status report.
  • Step 103 When the first network element parses the status report to fail to transmit the first link data packet, select another link to perform data retransmission.
  • the first network element accesses at least two links in the terminal, the plurality of data packets after the splitting are allocated to the at least two links, and then, when the terminal transmits the data packet on one link
  • the first network element receives the status report reported by the second network element by using the interaction between the first network element and the second network element, and the first network element parses the status report as the first link data packet fails to be transmitted.
  • the other links are selected for data retransmission, and the data packet retransmission processing under the terminal multi-connection is realized.
  • the first network element is a CU on the base station side
  • the second network element is a DU on the base station side
  • a CU-DU architecture is shown in Figure 2.
  • the CU divides the data packet according to multiple links accessed by the terminal.
  • the data packet at this time refers to an IP data packet or a compressed IP data packet, which is different from the subsequent fragmented data packet obtained by the DU fragment processing (or
  • the fragmented data packet is called a "small packet”
  • the IP data packet or the compressed IP data packet can be called a "big packet”.
  • the "small package” and “big bag” mentioned in this article are all meant to simplify the description.
  • the DU performs fragmentation processing on the data packet, and obtains the fragmented data packet, and then provides the corresponding link in the multiple links for transmission. If the retransmission is required in the multi-connection scenario, that is, the terminal fails to transmit on one of the multiple links, the signaling interaction between the CU and the DU is performed according to the preset policy based on the architecture shown in FIG. On the other link of the multiple links of the terminal, the fast retransmission of the transmission failure data packet is implemented, so that the data packet retransmission process under the multi-connection of the terminal is implemented, and the embodiment of the present application is applicable to the first network element being the CU.
  • the second network element is a retransmission process of the CU-DU architecture of the access network of the DU, and is not limited to the scenario of the CU-DU architecture.
  • the CU is a centralized node that can control and coordinate multiple cells, including protocol stack high-level control and data functions, and may also include some baseband processing functions.
  • the unit included in the CU is PDCP, and the PDCP is used for processing such as compression, encryption, reassembly, and offloading.
  • the DU is a distributed unit that implements the RRH function and the remaining baseband processing functions.
  • the units included in the DU are: 1) Radio Link Control (RLC), RLC for fragmentation, retransmission, etc.; 2) Media Intervention Control (MAC), MAC for scheduling, cascading, multiplexing, retransmission, etc. 3) Physical layer (PHY), PHY for modulation, coding, etc.
  • the CU and the DU are connected through a preamble interface.
  • the function division between CU-DUs has multiple splitting schemes.
  • the applicable scenarios and performance gains of different splitting schemes are different.
  • the parameters such as bandwidth, transmission delay, and synchronization of the preamble interface are also very different.
  • PDCP-RLC is a high-level splitting scheme.
  • the PDCP-RLC scheme is the most feasible for the future 3GPP of the CU-DU architecture. Considering that there is only a PDCP protocol stack on the CU, and the PDCP layer does not have the retransmission function, If the terminal accesses multiple DUs, when the terminal fails to transmit on one link, fast retransmission needs to be implemented on the other link. In the embodiment of the present application, the fast retransmission in the multi-connection scenario is solved by the specific implementation of the interaction between the CU and the DU in the subsequent embodiments.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the multi-connection scenario is multiple-received, that is, the terminal currently accesses at least two links at the same time, and at least two links are processed in parallel, and no inter-link handover is required.
  • the retransmission is triggered by the first network element, such as the CU, and the retransmission is performed by the first network element, such as the CU. Specifically, when the first network element receives the status report reported by the terminal, the first network element triggers a retransmission process.
  • the first network element parses the status report as the first link data packet transmission fails, selecting one of the at least two links with the link transmission quality better than the first link, the first The data packets transmitted on the link are retransmitted on the i links, and i is a positive integer greater than or equal to 1.
  • the status report has two types of reporting, including: 1) a status report periodically reported by the terminal, which is an active report. 2) The status report reported by the terminal after receiving the query request of the first network element is passively reported.
  • the PDCP status report is based on the network configuration. For example, the base station actively queries the terminal for reporting (passive reporting) or the terminal periodically reports (active reporting).
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the multi-connection scenario is multiple-received, that is, the terminal currently accesses at least two links at the same time, and at least two links are processed in parallel, and no inter-link handover is required.
  • the retransmission is triggered by the second network element, such as the DU, and the retransmission is performed by the first network element, such as the CU.
  • the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, the second network element triggers a retransmission process.
  • the second network element reports a status report.
  • the first network element parses out that the status report is that the first link data packet fails to be transmitted, selecting one link from the at least two links that the link transmission quality is better than the first link, The data packet transmitted on the first link is retransmitted on the i links, and i is a positive integer greater than or equal to 1.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the multi-connection scenario is multiple-received, that is, the terminal currently accesses at least two links at the same time, and at least two links are processed in parallel, and no inter-link handover is required.
  • Retransmission is triggered by the second network element, such as the DU, and retransmission is performed by the first network element, such as the CU.
  • the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, the second network element triggers a retransmission process.
  • the second network element reports a status report.
  • the first network element parses the status report to fail to transmit the first link data packet, the first network element initiates a query request to the terminal to confirm the transmission status.
  • the transmission quality is better than the i links of the first link, and the data packets transmitted on the first link are retransmitted on the i links, where i is a positive integer greater than or equal to 1.
  • the first network element needs to go to the terminal to confirm the transmission status.
  • the SN of the text indicates the serial number and will not be described.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the multi-connection scenario is multiple-received, that is, the terminal currently accesses at least two links at the same time, and at least two links are processed in parallel, and no inter-link handover is required.
  • the retransmission is triggered by the first network element, such as the CU, and the retransmission is performed by the first network element, such as the CU.
  • the difference from the above embodiment is that the foregoing embodiment is a full retransmission, that is, a data packet, or a "big packet"; the embodiment of the present application is a partial retransmission, which is a fragmented data packet, or "small packet".
  • the first network element receives the status report reported by the terminal, the first network element triggers a retransmission process.
  • the first network element parses the status report to fail to transmit the first link data packet, the first network element initiates a query request to the second network element to confirm the transmission status.
  • the second network element (such as a DU) sends a status report to the first network element (such as a CU), and the status report includes a data packet start location that is not successfully transmitted, etc., and the first The information of the network element fragment data packet is backed up to the second network element, and carries the link identifier of the transmission failure data packet, so that the subsequent second network element performs the retransmission processing of the preferred link.
  • the unit “link 1-RLC" in the second network element may also return a PDCP PDU transmission status report (including the initial state of the RLC PDU that has not been successfully transmitted), the first network element ( After receiving the transmission report, the unit “PDCP” in the CU) generates an RLC PDU and carries the identity of the link 1 to select a better link 2 for transmission.
  • a PDCP PDU transmission status report including the initial state of the RLC PDU that has not been successfully transmitted
  • the first network element After receiving the transmission report, the unit “PDCP” in the CU) generates an RLC PDU and carries the identity of the link 1 to select a better link 2 for transmission.
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the multi-connection scenario is multiple-received, that is, the terminal currently accesses at least two links at the same time, and at least two links are processed in parallel, and no inter-link handover is required.
  • the retransmission is triggered by the second network element, such as the DU, and the retransmission is performed by the first network element, such as the CU.
  • the difference from the above embodiment is that the foregoing embodiment is a full retransmission, that is, a data packet, or a "big packet"; the embodiment of the present application is a partial retransmission, which is a fragmented data packet, or "small packet".
  • the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, the second network element triggers a retransmission process.
  • the second network element reports a status report.
  • the first network element parses the status report as the transmission of the xth fragment data packet in the first link data packet, the link transmission quality is better than the first link from the at least two links. i links, the x being a positive integer greater than or equal to 1.
  • the first network element Transmitting, by the first network element, the first link identifier obtained from the status report to the i links, and transmitting the xth fragment data transmitted on the first link according to the first link identifier
  • the packet is retransmitted on the i links to perform reassembly of the fragmented data packet at the terminal, where i is a positive integer greater than or equal to 1.
  • the second network element (such as a DU) sends a status report to the first network element (such as a CU), and the status report includes a data packet start location that is not successfully transmitted, etc., and the first The information of the network element fragment data packet is backed up to the second network element, and carries the link identifier of the transmission failure data packet, so that the subsequent second network element performs the retransmission processing of the preferred link.
  • the unit “link 1-RLC" in the second network element may also return a PDCP PDU transmission status report (including the initial state of the RLC PDU that has not been successfully transmitted), the first network element ( After receiving the transmission report, the unit “PDCP” in the CU) generates an RLC PDU and carries the identity of the link 1 to select a better link 2 for transmission.
  • a PDCP PDU transmission status report including the initial state of the RLC PDU that has not been successfully transmitted
  • the first network element After receiving the transmission report, the unit “PDCP” in the CU) generates an RLC PDU and carries the identity of the link 1 to select a better link 2 for transmission.
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the multi-connection scenario is multiple-received, that is, the terminal currently accesses at least two links at the same time, and at least two links are processed in parallel, and no inter-link handover is required.
  • Retransmission is triggered by the second network element, such as the DU, and retransmission is performed by the first network element, such as the CU.
  • the difference from the above embodiment is that the foregoing embodiment is a full retransmission, that is, a data packet, or a "big packet"; the embodiment of the present application is a partial retransmission, which is a fragmented data packet, or "small packet".
  • the fragmentation data packet needs to be reorganized. Specifically, when the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, the second network element triggers a retransmission process. The second network element reports a status report. When the first network element parses the status report as the transmission of the xth fragment data packet in the first link data packet, the first network element initiates a query request to the terminal to confirm the transmission status.
  • the link transmission quality is selected to be better than the i links of the first link, and the x is a positive integer greater than or equal to 1.
  • the first network element needs to confirm which fragment data packet transmission fails according to the transmission status fed back by the terminal.
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the multi-connection scenario is multiple-received, that is, the terminal currently accesses at least two links at the same time, and at least two links are processed in parallel, and no inter-link handover is required.
  • the retransmission is triggered by the second network element, such as the DU, and the retransmission is performed by the first network element, such as the CU.
  • the second network element When the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, the second network element triggers a retransmission process.
  • the second network element reports a status report.
  • the terminal also reports status reports.
  • the two status reports can be the same or different.
  • the first network element parses the two status reports to compare the actual transmission status (mainly based on the transmission status in the status report reported by the terminal). If the actual transmission state is that the first link data packet transmission fails, selecting one of the at least two links that has a better link transmission quality than the first link, and transmitting the first link
  • the data packet is retransmitted on the i links, and i is a positive integer greater than or equal to 1.
  • the first network And selecting, from the at least two links, the i-links whose link transmission quality is better than the first link, and forwarding the first link identifier obtained from the status report to the i links, And transmitting, according to the first link identifier, the xth fragment data packet transmitted on the first link on the i links, to perform reassembly of the fragmented data packet at the terminal, where i is greater than or equal to 1 Positive integer.
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the single-transmission and single-receiving in the multi-connection scenario is that the terminal currently accesses one of the at least two links, and at least two links need to be switched.
  • the retransmission is triggered by the first network element, such as the CU, and the retransmission is performed by the first network element, such as the CU.
  • the difference from the above embodiment is that the above embodiment is a case where multiple connections are received in a multi-connection scenario.
  • one way is: all the retransmission policies in the case of multiple transmission and over-receiving, that is, transmitting data packets, or “big packets”; another way is: if the above-mentioned multiple transmissions are overcharged
  • the partial retransmission strategy that is, the fragmented data packet, or "small packet”, that is, which "small packet” transmission fails, only the "small packet” is worn, and no retransmission is required.
  • the processing may be performed according to the query response fed back by the terminal, and the reassembly of the fragmented data packet is required after the transmission is successful.
  • the partial retransmission policy is taken as an example, after the first network element switches between at least two link transmission links accessed by the terminal, the status report reported by the terminal is received by the terminal, The first network element triggers a retransmission process. Determining, by the first network element, that the status report is that the first link data packet fails to be transmitted, and initiating a query request to the second network element to confirm that the transmission status is which fragment data packet in the first link data packet. The transfer failed.
  • the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by the interaction between the first network element and the second network element.
  • the embodiment of the invention is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is a CU and the second network element is a DU, and is not limited to the scenario of the CU-DU architecture.
  • the single-transmission and single-receiving in the multi-connection scenario is that the terminal currently accesses one of the at least two links, and at least two links need to be switched.
  • the retransmission is triggered by the second network element, such as the DU, and the retransmission is performed by the first network element, such as the CU.
  • the difference from the above embodiment is that the above embodiment is a case where multiple connections are received in a multi-connection scenario.
  • one way is: all the retransmission policies in the case of multiple transmission and over-receiving, that is, transmitting data packets, or “big packets”; another way is: if the above-mentioned multiple transmissions are overcharged
  • the partial retransmission strategy that is, the fragmented data packet, or "small packet”, that is, which "small packet” transmission fails, only the "small packet” is worn, and no retransmission is required.
  • the processing may be performed according to the query response fed back by the terminal, and the reassembly of the fragmented data packet is required after the transmission is successful.
  • the partial retransmission policy is taken as an example, after the second network element switches between the link transmission links of the at least two links accessed by the terminal, the first link data packet transmission failure is found and/ When the first link is abnormal, the second network element triggers a retransmission process.
  • the second network element reports a status report.
  • the first network element parses the status report as the transmission of the xth fragment data packet in the first link data packet, the link transmission quality is better than the first link from the at least two links.
  • i links, the x being a positive integer greater than or equal to 1.
  • the first network element Transmitting, by the first network element, the first link identifier obtained from the status report to the i links, and transmitting the xth fragment data transmitted on the first link according to the first link identifier
  • the packet is retransmitted on the i links to perform reassembly of the fragmented data packet at the terminal, where i is a positive integer greater than or equal to 1.
  • the base station includes a first network element and a second network element, where the first network element is configured to access at least two links in the terminal, and when the terminal is on a link
  • the packet transmission fails the status report reported by the second network element is received; when the status report is parsed, the first link data packet fails to be transmitted, and another link is selected for data retransmission; the second network element is configured as The status report is reported, and the fast retransmission processing of the data packet under the multi-connection of the terminal is implemented by interacting with the first network element.
  • the plurality of data packets after the splitting are allocated to the at least two links, and then, when the terminal is on the data of one link
  • the data packet retransmission processing under the multi-connection of the terminal is realized by the interaction between the first network element and the second network element.
  • the first network element is a CU on the base station side
  • the second network element is a DU on the base station side
  • a CU-DU architecture is shown in Figure 2.
  • the CU divides the data packet according to multiple links accessed by the terminal.
  • the data packet at this time refers to an IP data packet or a compressed IP data packet, which is different from the subsequent fragmented data packet obtained by the DU fragment processing (or
  • the fragmented data packet is called a "small packet”
  • the IP data packet or the compressed IP data packet can be called a "big packet”.
  • the "small package” and “big bag” mentioned in this article are all meant to simplify the description.
  • the DU performs fragmentation processing on the data packet, and obtains the fragmented data packet, and then provides the corresponding link in the multiple links for transmission. If the retransmission is required in the multi-connection scenario, that is, the terminal fails to transmit on one of the multiple links, the signaling interaction between the CU and the DU is performed according to the preset policy based on the architecture shown in FIG. On the other link of the multiple links of the terminal, the fast retransmission of the transmission failure data packet is implemented, so that the data packet retransmission process under the multi-connection of the terminal is implemented, and the embodiment of the present application is applicable to the first network element being the CU.
  • the second network element is a retransmission process of the CU-DU architecture of the access network of the DU, and is not limited to the scenario of the CU-DU architecture.
  • the CU is a centralized node that can control and coordinate multiple cells, including protocol stack high-level control and data functions, and may also include some baseband processing functions.
  • the unit included in the CU is PDCP, and the PDCP is used for processing such as compression, encryption, reassembly, and offloading.
  • the DU is a distributed unit that implements the RRH function and the remaining baseband processing functions.
  • the units included in the DU are: 1) RLC, RLC for fragmentation, retransmission, etc.; 2) MAC, MAC for scheduling, cascading, multiplexing, retransmission, etc.; 3) PHY, PHY for modulation, coding Wait.
  • the CU and the DU are connected through a preamble interface.
  • the function division between CU-DUs has multiple splitting schemes.
  • the applicable scenarios and performance gains of different splitting schemes are different.
  • the parameters such as bandwidth, transmission delay, and synchronization of the preamble interface are also very different.
  • PDCP-RLC is a high-level splitting scheme.
  • the PDCP-RLC scheme is the most feasible for the future 3GPP of the CU-DU architecture. Considering that there is only a PDCP protocol stack on the CU, and the PDCP layer does not have the retransmission function, If the terminal accesses multiple DUs, when the terminal fails to transmit on one link, fast retransmission needs to be implemented on the other link. With the embodiment of the present application, the fast re-switching in the multi-connection scenario is solved by the specific implementation of the interaction between the CU-DUs in the subsequent embodiments.
  • the first network element is further configured to: when the first network element receives the status report, trigger the retransmission process by the first network element; When the network element parses the status report as the first link data packet transmission fails, selecting one link from the at least two links that is better than the first link, and connecting the first link The transmitted data packet is retransmitted on the i links, and i is a positive integer greater than or equal to 1.
  • the reporting manner of the status report includes: 1) a status report periodically reported by the terminal; 2) a status report reported by the terminal after receiving the query request of the first network element.
  • the first network element is further configured to:
  • the first network element When the first network element receives the status report reported by the terminal, the first network element triggers a retransmission process; the first network element parses the status report as a first link data packet transmission. Upon failure, selecting one of the at least two links whose link transmission quality is better than the first link, and retransmitting the data packet transmitted on the first link on the i links , i is a positive integer greater than or equal to 1.
  • the status report includes:
  • the second network element is further configured to: when the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, The second network element triggers a retransmission process; the second network element reports a status report.
  • the first network element is further configured to: when the status report is parsed as the first link data packet transmission fails, select a link transmission quality that is better than the first link from the at least two links.
  • the link transmits the data packet transmitted on the first link on the i links, where i is a positive integer greater than or equal to 1.
  • the second network element is further configured to: when the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, The second network element triggers a retransmission process; the second network element reports a status report.
  • the first network element is further configured to: when the status report is parsed as a first link data packet transmission failure and/or a first link abnormality, initiate a query request to the terminal to confirm a transmission status; The first network element receives the query response fed back by the terminal, and parses out that the transmission state is that the first link data packet transmission fails, and selecting the link transmission quality from the at least two links is better than the first link.
  • the i-links retransmit the data packets transmitted on the first link on the i links, where i is a positive integer greater than or equal to 1.
  • the first network element is further configured to: when the first network element receives the status report reported by the terminal, the first network element triggers a retransmission process.
  • the first network element parses the status report to fail to transmit the first link data packet, initiates a query request to the second network element to confirm that the transmission status is which fragment in the first link data packet.
  • the data packet fails to be transmitted; the first network element receives the query response fed back by the second network element, and parses the transmission status as the transmission of the xth fragment data packet in the first link data packet, where the x is greater than or equal to 1 a positive integer; the first network element selects, from the at least two links, the link transmission quality is better than the i links of the first link, and the first link identifier obtained from the query response Forwarding to the i links, and retransmitting the xth fragment data packet transmitted on the first link on the i links according to the first link identifier, to perform fragmentation data in the terminal.
  • the reorganization of the packet, i is a positive integer greater than or equal to 1.
  • the second network element is further configured to: when the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, The second network element triggers a retransmission process; the second network element reports a status report.
  • the first network element is further configured to: when the status report is parsed as the transmission of the xth fragment data packet in the first link data packet, the link transmission quality is selected from the at least two links.
  • the x is a positive integer greater than or equal to 1; the first network element forwards the first link identifier obtained from the status report to the i links And re-transmitting the xth fragment data packet transmitted on the first link on the i links according to the first link identifier, to perform reassembly of the fragmented data packet at the terminal, where i is greater than or equal to A positive integer of 1.
  • the second network element is further configured to: when the second network element finds that the first link data packet transmission fails and/or the first link is abnormal, The second network element triggers a retransmission process; the second network element reports a status report.
  • the first network element is further configured to: when the status report is parsed as the transmission of the xth fragment data packet in the first link data packet, the query request is initiated to the terminal to confirm the transmission status; The first network element receives the query response fed back by the terminal, and parses out that the transmission state is that the xth fragment data packet in the first link data packet fails to be transmitted, and the link transmission quality is selected from the at least two links.
  • the x is a positive integer greater than or equal to 1; the first network element forwards the first link identifier obtained from the query response to the i links And re-transmitting the xth fragment data packet transmitted on the first link on the i links according to the first link identifier, to perform reassembly of the fragmented data packet at the terminal, where i is greater than or equal to A positive integer of 1.
  • the first network element is further configured to: after the first network element switches between at least two link transmission links accessed by the terminal, the first network element receives the a status report reported by the terminal, the first network element triggers a retransmission process; the first network element parses the status report to fail to transmit the first link data packet, and initiates a query request to the second network element The first network element receives the query response fed back by the second network element, and parses the transmission status as the transmission of the xth fragment data packet in the first link data packet, where the x is greater than or equal to a positive integer of 1; the first network element selects, from the at least two links, an i-link whose link transmission quality is better than the first link, and the first link obtained from the query response The identifier is forwarded to the i links, and the xth fragment data packet transmitted on the first link is retransmitted on the i links according to the first link identifier, to perform fragmentation in the terminal.
  • the second network element is further configured to: after the second network element switches between at least two link transmission links accessed by the terminal, discover the first chain.
  • the second network element triggers a retransmission process; the second network element reports a status report.
  • the first network element is further configured to: when the status report is parsed as the transmission of the xth fragment data packet in the first link data packet, the link transmission quality is selected from the at least two links.
  • the x is a positive integer greater than or equal to 1; the first network element forwards the first link identifier obtained from the status report to the i links And re-transmitting the xth fragment data packet transmitted on the first link on the i links according to the first link identifier, to perform reassembly of the fragmented data packet at the terminal, where i is greater than or equal to A positive integer of 1.
  • a base station includes: a processor and a memory for storing a computer program executable on the processor;
  • the processor is configured to implement the steps of any one of the foregoing aspects when the computer program is executed.
  • the processor is configured to: when the computer program is executed:
  • the first network element accesses at least two links in the terminal
  • the second network element reports the status report
  • the other network element selects another link for data retransmission.
  • the processor is further configured to: when the computer program is executed:
  • the second network element fragments the plurality of data packets
  • the plurality of fragmented data packets are provided to the terminal for transmission.
  • the processor is further configured to: when the computer program is executed:
  • the processor is further configured to: when the computer program is executed:
  • the other network link is selected to perform data retransmission.
  • the processor is further configured to: when the computer program is executed:
  • the first network element selects, from the at least two links, a link transmission quality that is better than i links of the first link, where x is a positive integer greater than or equal to 1;
  • a storage medium according to an embodiment of the present invention, wherein a computer program is stored thereon, wherein the computer program is executed by a processor to implement the steps of the method according to any one of the above aspects.
  • the computer program is implemented by the processor:
  • the first network element accesses at least two links in the terminal
  • the second network element reports the status report
  • the other network element selects another link for data retransmission.
  • the computer program is also implemented when executed by the processor:
  • the second network element fragments the plurality of data packets
  • the plurality of fragmented data packets are provided to the terminal for transmission.
  • the computer program is also implemented when executed by the processor:
  • the computer program is also implemented when executed by the processor:
  • the other network link is selected to perform data retransmission.
  • the computer program is also implemented when executed by the processor:
  • the first network element selects, from the at least two links, a link transmission quality that is better than i links of the first link, where x is a positive integer greater than or equal to 1;
  • the embodiment of the present application is as follows:
  • Solution 1 The PDCP layer triggers to retransmit the PDCP packets between different link legs, as shown in Figure 3.
  • the flow of Figure 3 includes the following steps:
  • Step 201 Establish a connection with link 1.
  • Step 202 Establish a connection with link 2.
  • Step 203 Perform downlink traffic on the downlink data.
  • Step 206 Reporting a PDCP status report, that is, a PDCP status report
  • the method further includes: the PDCP status report is based on the network configuration, for example, the base station actively queries the terminal for reporting or periodically reports the terminal.
  • Solution 2 The RLC triggers and retransmits the PDCP packet between different legs, as shown in Figure 4-5.
  • the flow of Figure 4 includes the following steps:
  • Step 301 Establish a connection with the link 1.
  • Step 302 Establish a connection with link 2.
  • Step 303 offloading downlink data.
  • Step 306 PDCP n1 is fragmented into RLC fragments s1, s2, s3, or not fragmented;
  • the terminal since the terminal does not rely on the PDCP status report, the RLC feeds back to the PDCP layer, and the delay is shorter.
  • the PDCP data packet to be retransmitted may also be determined by the CU after initiating a query for the PDCP transmission status request to the terminal, as shown in FIG. 5.
  • the flow of Figure 5 includes the following steps:
  • Step 401 Establish a connection with the link 1.
  • Step 402 Establish a connection with the link 2;
  • Step 403 offloading downlink data.
  • Step 406 PDCP n1 is fragmented into RLC fragments s1, s2, s3, or not fragmented;
  • Step 408 transmitting a status report, such as a transmission failure
  • Step 409 Initiate a PDCP transmission status query.
  • Step 410 Reporting PDCP transmission status feedback.
  • Option 3 PDCP triggering, retransmitting the RLC packet between different legs, as shown in Figure 6.
  • the flow of Figure 6 includes the following steps:
  • Step 501 Establish a connection with link 1.
  • Step 502 Establish a connection with the link 2;
  • Step 503 offloading downlink data.
  • Step 506 PDCP n1 is fragmented into RLC fragments s1, s2, s3, or not fragmented;
  • Step 507 reporting a PDCP status report, that is, a PDCP status report
  • Step 508 The link transmission fails.
  • Step 510 The link transmission failure is found.
  • Step 511 Return an RLC packet that is not successfully transmitted (such as RLC fragment s2), and carry PDCP PDU SN information;
  • Step 512 selecting a better link 2, and retransmitting the RLC fragment s2 on the link 2, and carrying the identifier of the link 1 to forward to the link 2;
  • Step 513 retransmit the RLC fragment s2 on the link 2;
  • Step 514 After receiving the RLC PDU s2 packet, reassemble the RLC fragment on the terminal. Continue subsequent signaling interactions.
  • the PDCP PDU transmission status report (including the initial state of the untransmitted RLC PDU) may be returned through the link 1 - RLC.
  • the PDCP After receiving the transmission report, the PDCP generates an RLC PDU and carries the link. The identification of 1 selects the better link 2 for transmission.
  • Option 4 RLC triggering, transmitting RLC packets between different legs, as shown in Figure 7.
  • the flow of Figure 7 includes the following steps:
  • Step 601 Establish a connection with the link 1.
  • Step 602 establishing a connection with the link 2;
  • Step 603 offloading downlink data.
  • Step 606 PDCP n1 is fragmented into RLC fragments s1, s2, s3, or not fragmented;
  • Step 608 returning an untransmitted RLC packet (such as RLC fragment s2), and carrying PDCP PDU SN information;
  • Step 609 selecting a better link 2, and retransmitting the RLC fragment s2 on the link 2, and carrying the identifier of the link 1 to forward to the link 2;
  • Step 610 Retransmit the RLC fragment s2 on the link 2.
  • Step 611 After receiving the RLC PDU s2 packet, reassembling the RLC fragment on the terminal. Continue the subsequent signaling interaction.
  • the PDCP PDU transmission status report (including the initial state of the untransmitted RLC PDU) may be returned through the link 1 - RLC.
  • the PDCP After receiving the transmission report, the PDCP generates an RLC PDU and carries the link. The identification of 1 selects the better link 2 for transmission.
  • Solution 5 In addition to the DU handover scenario, the RLC fragmentation packet may also be retransmitted, as shown in FIG. 8-9.
  • the scheme 5 is different from the “double-issue and dual-receiving scenario” in the above multiple connection, and the scheme 5 is the “single-single-single-scenario scenario” in the multi-connection.
  • Figure 8 shows the process of PDCP triggering retransmission, including the following steps:
  • Step 701 Establish a connection with the link 1.
  • Step 703 PDCP n1 is fragmented into RLC fragments s1, s2, s3, or no fragment s;
  • Step 704 A handover from link 1 to link 2 occurs, and a connection is established with link 2;
  • Step 705 reporting a PDCP status report, that is, a PDCP status report
  • Step 706 The link transmission fails.
  • Step 709 returning an untransmitted RLC packet (such as RLC fragment s2), and carrying PDCP PDU SN information;
  • Step 710 select a better link 2, and retransmit the RLC fragment s2 on the link 2, and carry the information of the link 1 to the link 2;
  • Step 711 retransmit the RLC fragment s2 on the link 2;
  • Step 712 After receiving the RLC PDU s2 packet, reassemble the RLC fragment on the terminal. Continue the subsequent signaling interaction.
  • FIG. 9 shows the flow of RLC trigger retransmission, including the following steps:
  • Step 801 Establish a connection with the link 1.
  • Step 803 PDCP n1 is fragmented into RLC fragments s1, s2, s3, or no fragment s;
  • Step 804 A handover from link 1 to link 2 occurs, and a connection is established with link 2;
  • Step 806 returning an untransmitted RLC packet (such as RLC fragment s2), and carrying PDCP PDU SN information;
  • Step 807 select a better link 2, and retransmit the RLC fragment s2 on the link 2, and carry the information of the link 1 to the link 2;
  • Step 808 retransmit the RLC fragment s2 on the link 2;
  • Step 809 After receiving the RLC PDU s2 packet, reassembling the RLC fragment on the terminal. Continue subsequent signaling interactions.
  • the fast retransmission of the PDCP or the RLC packet under the multi-link is implemented by the interaction between the CU and the DU.
  • Fast retransmission can be implemented between multiple links, and retransmission of RLC PDUs between different links can be implemented to avoid retransmission of the entire PDCP PDU.
  • the integrated modules described in the embodiments of the present application may also be stored in a computer readable storage medium if they are implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solution of the embodiments of the present application may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • embodiments of the present application are not limited to any particular combination of hardware and software.
  • the embodiment of the present application further provides a computer storage medium, where a computer program is stored, and the computer program is used to implement a method for implementing multi-link retransmission under multiple connections in the embodiment of the present application.
  • the terminal accesses at least two links; when the terminal fails to transmit the data packet on one link, the second network element reports a status report; the first network element parses the status report as When the first link packet transmission fails, another link is selected for data retransmission. Therefore, when one link data packet transmission fails in the multiple links of the terminal, the fast retransmission of the transmission failure data packet can be implemented on the other link, thereby realizing the data packet retransmission processing under the terminal multiple connection. It is applicable to the retransmission process of the CU-DU architecture of the access network where the first network element is the CU and the second network element is the DU, and is not limited to the scenario of the CU-DU architecture.

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)

Abstract

本申请公开了一种多连接下实现多链路重传的方法及基站、存储介质，其中，所述方法包括：在终端接入至少两条链路；当终端在一个链路上数据包传输失败时，第二网元上报状态报告；所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。

Description

一种多连接下实现多链路重传的方法及基站、存储介质
相关申请的交叉引用
本申请基于申请号为201710184917.5、申请日为2017年03月24日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及重传技术，尤其涉及一种多连接下实现多链路重传的方法及基站、存储介质。
背景技术
如何设计灵活鲁棒的接入网架构是移动通信系统的关键，3G系统中接入网逻辑节点由基站(NB，Node B)和无线网络控制器(RNC，Radio Network Controller)组成，4G逻辑架构设计更加扁平化，仅包含增强型基站(eNB)节点。考虑到对5G接入网架构的需求，区别于4G接入网的最为典型的需求是接入网支持分布式远端单元(RU，Remote Unit)和集中单元(CU，Central Unit)的逻辑功能划分，且支持协议栈功能在CU和分布单元(DU，Distributed Unit)之间迁移。相比4G扁平化架构，接入网CU-DU两级架构的好处在于能够获得小区间协作增益，实现集中负载管理；高效实现密集组网下的集中控制，比如多连接，密集切换；获得池化增益，使能网络功能虚拟化(NFV，NetworkFunctionVirtualization)/软件定义型网络(SDN，Software-defined networking)，满足运营商某些5G场景的部署需求。
在CU-DU两级架构中，位于基站侧的两个网元(CU和DU)中，CU是一个集中式节点，能够控制和协调多个小区，包含协议栈高层控制和数 据功能，也可能包含一部分基带处理功能。DU是分布式单元实现射频前端(RRH)功能和其余基带处理功能，CU和DU之间通过前传接口连接。由于CU上仅有分组数据汇聚协议(PDCP，Packet Data Convergence Protocol)协议栈，而PDCP层不具备重传功能，因此，在需要重传的一种场景中，如果终端接入多个DU时，终端在一个链路上传输失败，如何是在另一个链路上实现快速重传是该接入网CU-DU架构需要解决的问题。
发明内容
有鉴于此，本申请实施例希望提供一种多连接下实现多链路重传的方法及基站、存储介质，至少解决了现有技术存在的问题。
本申请实施例的技术方案是这样实现的：
本申请实施例的一种多连接下实现多链路重传的方法，所述方法包括：
在终端接入至少两条链路；
当终端在一个链路上数据包传输失败时，第二网元上报状态报告；
所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。
上述方案中，所述方法还包括：
由所述第一网元为所述至少两条链路分配分流后的多个数据包。
上述方案中，所述方法还包括：
所述第二网元对所述多个数据包分片后，将多个分片数据包提供给终端进行传输。
上述方案中，所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传，包括：
从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
上述方案中，所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传；
所述第一网元解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，选择其他的链路进行数据重传。
上述方案中，所述方法还包括：
所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；
所述第一网元将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，i为大于等于1的正整数。
本申请实施例的一种基站，所述基站包括第一网元和第二网元；其中，
所述第一网元，配置为在终端接入至少两条链路，当终端在一个链路上数据包传输失败时接收第二网元上报的状态报告；解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传；
所述第二网元，配置为上报所述状态报告，与第一网元进行交互，以实现终端多连接下的数据包重传处理。
上述方案中，上述方案中，所述第一网元，进一步配置为：为所述至少两条链路分配分流后的多个数据包。
上述方案中，所述第二网元，进一步配置为对所述多个数据包分片后，将多个分片数据包提供给终端进行传输。
上述方案中，所述第一网元，进一步配置为：
从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
上述方案中，所述第一网元，进一步配置为：
解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，选择其他的链路进行数据重传。
上述方案中，所述第一网元，进一步配置为：
从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；
将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，i为大于等于1的正整数。
本申请实施例的一种多连接下实现多链路重传的方法，所述方法包括：
在终端接入至少两条链路；
当终端在一个链路上数据包传输失败时，第一网元接收第二网元上报的状态报告；
所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。
上述方案中，所述方法还包括：
由所述第一网元为所述至少两条链路分配分流后的多个数据包。
本申请实施例的一种基站，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器；
其中，所述处理器用于运行所述计算机程序时实现上述方案任一项所述方法的步骤。
本申请实施例的一种存储介质，其上存储有计算机程序，其中，该计算机程序被处理器执行时实现上述方案任一项所述方法的步骤。
本申请实施例的多连接下实现多链路重传的方案包括：在终端接入至少两条链路时，为所述至少两条链路分配分流后的多个数据包；当终端在一个链路上数据包传输失败时，第一网元根据预设策略与第二网元进行交 互，以实现终端多连接下的数据包重传处理。
采用本申请实施例，在终端接入至少两条链路；当终端在一个链路上数据包传输失败时，第二网元上报状态报告；所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。由于，在终端多个链路中的一个链路数据包传输失败时，可以在另一个链路上实现传输失败数据包的快速重传，从而实现了终端多连接下的数据包重传处理，适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
附图说明
图1为本申请实施例一方法实现流程图；
图2为本申请实施例一CU-DU架构的示意图；
图3为本申请实施例一应用场景的实现流程图；
图4为本申请实施例一应用场景的实现流程图；
图5为本申请实施例一应用场景的实现流程图；
图6为本申请实施例一应用场景的实现流程图；
图7为本申请实施例一应用场景的实现流程图；
图8为本申请实施例一应用场景的实现流程图；
图9为本申请实施例一应用场景的实现流程图。
具体实施方式
下面结合附图对技术方案的实施作进一步的详细描述。
实施例一：
本申请实施例的一种多连接下实现多链路重传的方法，如图1所示，所述方法包括：
步骤101、在终端接入至少两条链路；
步骤102、当终端在一个链路上数据包传输失败时，第二网元上报状态报告；
步骤103、第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。
在实际应用中，当第一网元在终端接入至少两条链路时，为所述至少两条链路分配分流后的多个数据包，之后，当终端在一个链路上数据包传输失败时，通过第一网元与第二网元的交互，第一网元接收第二网元上报的状态报告，第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传，实现了终端多连接下的数据包重传处理。
在实际应用中，以第一网元为基站侧的CU，第二网元为基站侧的DU为例。一个CU-DU架构如图2所示。CU按照终端接入的多个链路对数据包进行分流，此时的数据包是指IP数据包或者压缩后的IP数据包，区别于后续经DU分片处理得到的分片数据包(或称分片数据包)称之为“小包”，可以将该IP数据包或者压缩后的IP数据包称之为“大包”。本文中所提及的“小包”和“大包”均是这个含义，只是为了简化描述。DU对数据包进行分片处理，得到分片数据包后再提供给多个链路中对应的链路进行传输。如果在该多连接场景下需要重传，即终端在多个链路中的一个链路上传输失败，则基于图2所示的架构根据预设策略在CU与DU间进行信令交互，在终端多个链路中的另一个链路上实现传输失败数据包的快速重传，从而实现了终端多连接下的数据包重传处理，本申请实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
如图2所示，CU是一个集中式节点，能够控制和协调多个小区，包含协议栈高层控制和数据功能，也可能包含一部分基带处理功能。CU中包含的单元为PDCP，PDCP用于压缩、加密、重组、分流等处理。DU是分布 式单元实现RRH功能和其余基带处理功能。DU中包含的单元为：1)无线链路控制(RLC)，RLC用于分片、重传等；2)媒体介入控制(MAC)，MAC用于调度、级联、复用、重传等；3)物理层(PHY)，PHY用于调制、编码等。CU和DU之间通过前传接口连接。
CU-DU之间的功能划分具有多种切分方案，不同切分方案的适用场景和性能增益均不同，同时对前传接口的带宽、传输时延、同步等参数要求也有很大差异。PDCP-RLC是一种高层的切分方案，针对CU-DU架构未来3GPP最有可行性的该PDCP-RLC方案，考虑到CU上仅有PDCP协议栈，而PDCP层不具备重传功能，因此如果终端接入多个DU时，当终端在一个链路上传输失败，需要在另一个链路上实现快速重传。采用本申请实施例，通过后续各个实施例中CU-DU间进行交互的具体实现来解决多连接场景下的快速重换。
实施例二：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中多发多收的情况，即：终端当前同时接入至少两条链路，至少两条链路并行处理，不需要链路间切换。由第一网元如CU触发重传，由第一网元如CU执行重传。具体的，当所述第一网元收到所述终端上报的状态报告时，由所述第一网元触发重传处理。第一网元解析出所述状态报告为第一链路数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
在本申请实施例一实施方式中，所述状态报告，存在两种上报方式， 包括：1)由所述终端周期性上报的状态报告，是主动上报。2)由所述终端收到所述第一网元的查询请求后上报的状态报告，是被动上报。实际应用中，PDCP状态报告基于网络配置，比如基站主动查询终端上报(被动上报)或者终端周期性上报(主动上报)。
实施例三：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中多发多收的情况，即：终端当前同时接入至少两条链路，至少两条链路并行处理，不需要链路间切换。由第二网元如DU触发重传，由第一网元如CU执行重传。具体的，当第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理。所述第二网元上报状态报告。所述第一网元解析出所述状态报告为第一链路数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
实施例四：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中多发多收的情况，即：终端当前同时接入至少两条链路，至少两条链路并行处理，不需要链路间切换。由第 二网元如DU触发重传，由第一网元如CU执行重传。具体的，当第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理。所述第二网元上报状态报告。所述第一网元解析出所述状态报告为第一链路数据包传输失败时，向所述终端发起查询请求，以确认传输状态。所述第一网元收到终端反馈的查询响应，从所述查询响应中解析出所述传输状态为所述第一链路数据包传输失败，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
区别于上述实施例三，第一网元需要去终端确认传输状态。在实际应用中，考虑到终端可能已经收到了CU中PDCP SN＝n2的包，但可能出现收到了反馈(ACK)在空口链路传输失败，因此，可以由CU向终端发起查询PDCP传输状态请求后，来决定要重传的PDCP数据包。文字的SN表示序列号，不做赘述。
实施例五：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中多发多收的情况，即：终端当前同时接入至少两条链路，至少两条链路并行处理，不需要链路间切换。由第一网元如CU触发重传，由第一网元如CU执行重传。与上述实施例的区别在于：上述实施例是全部重传，即传数据包，或称“大包”；本申请实施例是部分重传，传的是分片数据包，或称“小包”，即：哪个“小包”传输失败，只穿该“小包”，而无需全部重传，传输成功后需要进行分片数据包的重组。具体的，当第一网元收到所述终端上报的状态报告时，由所述第一 网元触发重传处理。所述第一网元解析出所述状态报告为第一链路数据包传输失败时，向所述第二网元发起查询请求，以确认传输状态。所述第一网元收到第二网元反馈的查询响应，从所述查询响应中解析出传输状态为第一链路数据包中第x分片数据包传输失败，所述x为大于等于1的正整数。所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将从所述查询响应中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
在本申请实施例一实施方式中，第二网元(如DU)发送状态报告给第一网元(如CU)，状态报告中包含未传输成功的数据包起始位置等，既将第一网元分片数据包的信息备份到第二网元，且携带传输失败数据包的链路标识，以便后续第二网元进行优选链路的重传处理。在实际应用中，第二网元(如DU)中的单元“链路1-RLC”也可以返回PDCP PDU传输状态报告(包含未传输成功的RLC PDU的起始状态)，第一网元(如CU)中的单元“PDCP”收到此传输报告后，生成RLC PDU,并携带链路1的标识，选择更优的链路2进行传输。
实施例六：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中多发多收的情况，即：终端当前同时接入至少两条链路，至少两条链路并行处理，不需要链路间切换。由第二网元如DU触发重传，由第一网元如CU执行重传。与上述实施例的区别在于：上述实施例是全部重传，即传数据包，或称“大包”；本申请实施例 是部分重传，传的是分片数据包，或称“小包”，即：哪个“小包”传输失败，只穿该“小包”，而无需全部重传，传输成功后需要进行分片数据包的重组。具体的，当所述第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理。所述第二网元上报状态报告。所述第一网元解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数。所述第一网元将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
在本申请实施例一实施方式中，第二网元(如DU)发送状态报告给第一网元(如CU)，状态报告中包含未传输成功的数据包起始位置等，既将第一网元分片数据包的信息备份到第二网元，且携带传输失败数据包的链路标识，以便后续第二网元进行优选链路的重传处理。在实际应用中，第二网元(如DU)中的单元“链路1-RLC”也可以返回PDCP PDU传输状态报告(包含未传输成功的RLC PDU的起始状态)，第一网元(如CU)中的单元“PDCP”收到此传输报告后，生成RLC PDU,并携带链路1的标识，选择更优的链路2进行传输。
实施例七：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中多发多收的情况，即：终端当前同时接入至少两条链路，至少两条链路并行处理，不需要链路间切换。由第 二网元如DU触发重传，由第一网元如CU执行重传。与上述实施例的区别在于：上述实施例是全部重传，即传数据包，或称“大包”；本申请实施例是部分重传，传的是分片数据包，或称“小包”，即：哪个“小包”传输失败，只穿该“小包”，而无需全部重传，且需要根据终端反馈的查询响应进行处理，传输成功后需要进行分片数据包的重组。具体的，当第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理。所述第二网元上报状态报告。所述第一网元解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，向所述终端发起查询请求，以确认传输状态。所述第一网元收到终端反馈的查询响应，从所述查询响应中解析出所述传输状态为所述第一链路数据包中第x分片数据包传输失败，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数。所述第一网元将从所述查询响应中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
本申请实施例中，第一网元需要根据终端反馈的传输状态来确认哪个分片数据包传输失败。在实际应用中，考虑到终端可能已经收到了CU中PDCP SN＝n2的包，但可能出现收到了ACK在空口链路传输失败，因此，可以由CU向终端发起查询PDCP传输状态请求后，来决定要重传的PDCP数据包。
实施例八：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中多发多收的情况，即：终端当前同时接入至少两条链路，至少两条链路并行处理，不需要链路间切换。由第二网元如DU触发重传，由第一网元如CU执行重传。
当第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理。所述第二网元上报状态报告。同时，终端也上报状态报告。两个状态报告可以相同，也可以不同。所述第一网元对这两个状态报告进行解析，以比对出实际的传输状态(主要以终端上报状态报告中的传输状态为准)。如果实际的传输状态为第一链路数据包传输失败，则从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。如果实际的传输状态为第一链路数据包传输失败，且为第一链路数据包中第x分片数据包传输失败，所述x为大于等于1的正整数，则所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
实施例九：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中单发单收的情况，即：终端当前接入至少两条链路中的一条链路，至少两条链路间需要切换。由第一网元如CU触发重传，由第一网元如CU执行重传。与上述实施例的区别在于：上述实施例是多连接场景中多发多收的情况。在本实施例中，一种方式是： 如上述多发多收的情况中的全部重传策略，即传数据包，或称“大包”；另一种方式是：如上述多发多收的情况中的部分重传策略，即传的是分片数据包，或称“小包”，即：哪个“小包”传输失败，只穿该“小包”，而无需全部重传。进一步，还可以根据终端反馈的查询响应进行处理，传输成功后需要进行分片数据包的重组。本申请实施例中，以部分重传策略为例，所述第一网元在所述终端接入的至少两条链路发送链路间切换后，收到所述终端上报的状态报告，由所述第一网元触发重传处理。所述第一网元解析出所述状态报告为第一链路数据包传输失败，向所述第二网元发起查询请求，以确认传输状态为第一链路数据包中哪个分片数据包传输失败。所述第一网元收到第二网元反馈的查询响应，从所述查询响应中解析出传输状态为第一链路数据包中第x分片数据包传输失败，所述x为大于等于1的正整数。所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将从所述查询响应中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
实施例十：
基于上述实施例，本申请实施例中，通过第一网元与第二网元的交互，实现了终端多连接下的数据包快速重传处理。发明实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
本申请实施例中，是多连接场景中单发单收的情况，即：终端当前接入至少两条链路中的一条链路，至少两条链路间需要切换。由第二网元如DU触发重传，由第一网元如CU执行重传。与上述实施例的区别在于：上述实施例是多连接场景中多发多收的情况。在本实施例中，一种方式是： 如上述多发多收的情况中的全部重传策略，即传数据包，或称“大包”；另一种方式是：如上述多发多收的情况中的部分重传策略，即传的是分片数据包，或称“小包”，即：哪个“小包”传输失败，只穿该“小包”，而无需全部重传。进一步，还可以根据终端反馈的查询响应进行处理，传输成功后需要进行分片数据包的重组。本申请实施例中，以部分重传策略为例，所述第二网元在所述终端接入的至少两条链路发送链路间切换后，发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理。所述第二网元上报状态报告。所述第一网元解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数。所述第一网元将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
实施例十一：
本申请实施例的基站，所述基站包括第一网元和第二网元；其中，所述第一网元，配置为在终端接入至少两条链路，当终端在一个链路上数据包传输失败时接收第二网元上报的状态报告；解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传；所述第二网元，配置为上报所述状态报告，通过与第一网元的交互，实现了终端多连接下的数据包快速重传处理。
本申请实施例中，当位于第一网元在终端接入至少两条链路时，为所述至少两条链路分配分流后的多个数据包，之后，当终端在一个链路上数据包传输失败时，通过第一网元与第二网元的交互，实现了终端多连接下的数据包重传处理。
在实际应用中，以第一网元为基站侧的CU，第二网元为基站侧的DU 为例。一个CU-DU架构如图2所示。CU按照终端接入的多个链路对数据包进行分流，此时的数据包是指IP数据包或者压缩后的IP数据包，区别于后续经DU分片处理得到的分片数据包(或称分片数据包)称之为“小包”，可以将该IP数据包或者压缩后的IP数据包称之为“大包”。本文中所提及的“小包”和“大包”均是这个含义，只是为了简化描述。DU对数据包进行分片处理，得到分片数据包后再提供给多个链路中对应的链路进行传输。如果在该多连接场景下需要重传，即终端在多个链路中的一个链路上传输失败，则基于图2所示的架构根据预设策略在CU与DU间进行信令交互，在终端多个链路中的另一个链路上实现传输失败数据包的快速重传，从而实现了终端多连接下的数据包重传处理，本申请实施例适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。
如图2所示，CU是一个集中式节点，能够控制和协调多个小区，包含协议栈高层控制和数据功能，也可能包含一部分基带处理功能。CU中包含的单元为PDCP，PDCP用于压缩、加密、重组、分流等处理。DU是分布式单元实现RRH功能和其余基带处理功能。DU中包含的单元为：1)RLC，RLC用于分片、重传等；2)MAC，MAC用于调度、级联、复用、重传等；3)PHY，PHY用于调制、编码等。CU和DU之间通过前传接口连接。
CU-DU之间的功能划分具有多种切分方案，不同切分方案的适用场景和性能增益均不同，同时对前传接口的带宽、传输时延、同步等参数要求也有很大差异。PDCP-RLC是一种高层的切分方案，针对CU-DU架构未来3GPP最有可行性的该PDCP-RLC方案，考虑到CU上仅有PDCP协议栈，而PDCP层不具备重传功能，因此如果终端接入多个DU时，当终端在一个链路上传输失败，需要在另一个链路上实现快速重传。采用本申请实施例，通过后续各个实施例中CU-DU间进行交互的具体实现来解决多连接场 景下的快速重换。
在本申请实施例一实施方式中，所述第一网元，进一步配置为：当所述第一网元收到状态报告时，由所述第一网元触发重传处理；所述第一网元解析出所述状态报告为第一链路数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。其中，所述状态报告的上报方式，包括：1)由所述终端周期性上报的状态报告；2)由所述终端收到所述第一网元的查询请求后上报的状态报告。
在本申请实施例一实施方式中，所述第一网元，进一步配置为：
当所述第一网元收到所述终端上报的状态报告时，由所述第一网元触发重传处理；所述第一网元解析出所述状态报告为第一链路数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
在本申请实施例一实施方式中，所述状态报告，包括：
由所述终端周期性上报的状态报告；或者，
由所述终端收到所述第一网元的查询请求后上报的状态报告。
在本申请实施例一实施方式中，所述第二网元，进一步配置为：当所述第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理；所述第二网元上报状态报告。
所述第一网元，进一步配置为：解析出所述状态报告为第一链路数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
在本申请实施例一实施方式中，所述第二网元，进一步配置为：当所 述第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理；所述第二网元上报状态报告。
所述第一网元，进一步配置为：解析出所述状态报告为第一链路数据包传输失败和/或第一链路异常时，向所述终端发起查询请求，以确认传输状态；所述第一网元收到终端反馈的查询响应，解析出所述传输状态为第一链路数据包传输失败，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
在本申请实施例一实施方式中，所述第一网元，进一步配置为：当所述第一网元收到所述终端上报的状态报告时，由所述第一网元触发重传处理；所述第一网元解析出所述状态报告为第一链路数据包传输失败时，向所述第二网元发起查询请求，以确认传输状态为第一链路数据包中哪个分片数据包传输失败；所述第一网元收到第二网元反馈的查询响应，解析出传输状态为第一链路数据包中第x分片数据包传输失败，所述x为大于等于1的正整数；所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将从所述查询响应中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
在本申请实施例一实施方式中，所述第二网元，进一步配置为：当所述第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理；所述第二网元上报状态报告。
所述第一网元，进一步配置为：解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；所述第一网元 将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
在本申请实施例一实施方式中，所述第二网元，进一步配置为：当所述第二网元发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理；所述第二网元上报状态报告。
所述第一网元，进一步配置为：解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，向所述终端发起查询请求，以确认传输状态；所述第一网元收到终端反馈的查询响应，解析出所述传输状态为第一链路数据包中第x分片数据包传输失败，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；所述第一网元将从所述查询响应中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
在本申请实施例一实施方式中，所述第一网元，进一步配置为：所述第一网元在所述终端接入的至少两条链路发送链路间切换后，收到所述终端上报的状态报告，由所述第一网元触发重传处理；所述第一网元解析出所述状态报告为第一链路数据包传输失败，向所述第二网元发起查询请求，以确认传输状态；所述第一网元收到第二网元反馈的查询响应，解析出传输状态为第一链路数据包中第x分片数据包传输失败，所述x为大于等于1的正整数；所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将从所述查询响应中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
在本申请实施例一实施方式中，所述第二网元，进一步配置为：所述第二网元在所述终端接入的至少两条链路发送链路间切换后，发现第一链路数据包传输失败和/或第一链路异常时，由所述第二网元触发重传处理；所述第二网元上报状态报告。
所述第一网元，进一步配置为：解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；所述第一网元将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，以在终端进行分片数据包的重组，i为大于等于1的正整数。
本发明实施例的一种基站，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器；
其中，所述处理器用于运行所述计算机程序时实现上述方案任一项所述方法的步骤。
具体的，所述处理器，用于运行所述计算机程序时实现：
第一网元在终端接入至少两条链路；
当终端在一个链路上数据包传输失败时，第二网元上报状态报告；
所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。
所述处理器，还用于运行所述计算机程序时实现：
所述第二网元对所述多个数据包分片后，将多个分片数据包提供给终端进行传输。
所述处理器，还用于运行所述计算机程序时实现：
从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正 整数。
所述处理器，还用于运行所述计算机程序时实现：
所述第一网元解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，选择其他的链路进行数据重传。
所述处理器，还用于运行所述计算机程序时实现：
所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；
所述第一网元将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，i为大于等于1的正整数。
本发明实施例的一种存储介质，其上存储有计算机程序，其中，该计算机程序被处理器执行时实现上述方案任一项所述方法的步骤。
具体的，该计算机程序被处理器执行时实现：
第一网元在终端接入至少两条链路；
当终端在一个链路上数据包传输失败时，第二网元上报状态报告；
所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。
该计算机程序被处理器执行时还实现：
所述第二网元对所述多个数据包分片后，将多个分片数据包提供给终端进行传输。
该计算机程序被处理器执行时还实现：
从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
该计算机程序被处理器执行时还实现：
所述第一网元解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，选择其他的链路进行数据重传。
该计算机程序被处理器执行时还实现：
所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；
所述第一网元将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，i为大于等于1的正整数。
以一个现实应用场景为例对本申请实施例阐述如下：
采用本申请实施例，其应用场景有如下几个具体方案，分别阐述如下：
方案1：PDCP层触发，在不同链路分支(leg)间重传PDCP包，如图3所示。
图3的流程包括如下步骤：
步骤201、与链路1建立连接；
步骤202、与链路2建立连接；
步骤203、将下行数据进行分流；
步骤204、传输数据包，数据包为PDCP PDU(SN＝m1,m2...)；
步骤205、传输数据包，数据包为PDCP PDU(SN＝n1,n2...)；
步骤206、上报PDCP状态报告，即PDCP status report；
步骤207、发现链路传输失败，如链路1：PDCP PDU(SN＝n2)没有重传成功；
步骤208、选择更优链路2，并在链路2重传PDCP PDU(SN＝n2)。继续后续的信令交互。
本申请实施例中，还可以包括：PDCP状态报告基于网络配置，比如基站主动查询终端上报或者终端周期性上报。
方案2：RLC触发，在不同legs间重传PDCP包，如图4-图5所示。
图4的流程包括如下步骤：
步骤301、与链路1建立连接；
步骤302、与链路2建立连接；
步骤303、将下行数据进行分流；
步骤304、传输数据包，数据包为PDCP PDU(SN＝m1,m2...)；
步骤305、传输数据包，数据包为PDCP PDU(SN＝n1,n2...)；
步骤306、PDCP n1被分片为RLC分片s1、s2、s3，或者不分片；
步骤307、链路传输失败，如链路1：对分段数据包，PDCP PDU(SN＝n1)中RLC PDU s2重传失败；对不分片数据包，PDCP PDU(SN＝n1)重传失败；
步骤308、上报传输状态报告，如PDCP PDU(SN＝n1)传输失败；
步骤309、选择更优链路2，并在链路2重传PDCP PDU(SN＝n1)。继续后续的信令交互。
图4中，由于不依赖终端反馈PDCP status report，RLC向PDCP层反馈，时延更短。另外，考虑到终端可能已经收到了PDCP SN＝n2的包，但可能出现ACK在空口链路传输失败。也可以由CU向终端发起查询PDCP传输状态请求后，来决定要重传的PDCP数据包，如图5所示。
图5的流程包括如下步骤：
步骤401、与链路1建立连接；
步骤402、与链路2建立连接；
步骤403、将下行数据进行分流；
步骤404、传输数据包，数据包为PDCP PDU(SN＝m1,m2...)；
步骤405、传输数据包，数据包为PDCP PDU(SN＝n1,n2...)；
步骤406、PDCP n1被分片为RLC分片s1、s2、s3，或者不分片；
步骤407、链路传输失败，如链路1：对分段数据包，PDCP PDU(SN＝n1)中RLC PDU s2重传失败；对不分片数据包，PDCP PDU(SN＝n1)重传失败；
步骤408、传输状态报告，如传输失败；
步骤409、发起PDCP传输状态查询；
步骤410、上报PDCP传输状态反馈；
步骤411、选择更优链路2，并在链路2重传PDCP PDU(SN＝n1)。继续后续的信令交互。
方案3：PDCP触发，在不同的legs间重传RLC包，如图6所示。
图6的流程包括如下步骤：
步骤501、与链路1建立连接；
步骤502、与链路2建立连接；
步骤503、将下行数据进行分流；
步骤504、传输数据包，数据包为PDCP PDU(SN＝m1,m2...)；
步骤505、传输数据包，数据包为PDCP PDU(SN＝n1,n2...)；
步骤506、PDCP n1被分片为RLC分片s1、s2、s3，或者不分片；
步骤507、上报PDCP状态报告，即PDCP status report；
步骤508、链路传输失败，如链路1:PDCP PDU(SN＝n1)没有重传成功；
步骤509、请求PDCP PDU(SN＝n2)传输状态；
步骤510、发现链路传失败，如链路1：对分段数据包，PDCP PDU(SN＝n1)中RLC PDU s2重传失败；对不分片数据包，PDCP PDU(SN＝n1)重传失败；
步骤511、返回未传输成功的RLC包(如RLC分片s2)，并携带PDCP PDU SN信息；
步骤512、选择更优链路2，并在链路2重传RLC分片s2，并携带链路1的标识转发给链路2；
步骤513、在链路2重传RLC分片s2；
步骤514、收到RLC PDU s2包后，在终端上重组RLC分片。继续后续的信令交互。
本申请实施例中，还可以通过链路1-RLC返回PDCP PDU传输状态报告(包含未传输成功的RLC PDU的起始状态)，PDCP收到此传输报告后，生成RLC PDU,并携带链路1的标识，选择更优的链路2进行传输。
方案4：RLC触发，在不同的legs间传输RLC包，如图7所示。
图7的流程包括如下步骤：
步骤601、与链路1建立连接；
步骤602、与链路2建立连接；
步骤603、将下行数据进行分流；
步骤604、传输数据包，数据包为PDCP PDU(SN＝m1,m2...)；
步骤605、传输数据包，数据包为PDCP PDU(SN＝n1,n2...)；
步骤606、PDCP n1被分片为RLC分片s1、s2、s3，或者不分片；
步骤607、链路传输失败，如链路1：对分段数据包，PDCP PDU(SN＝n1)中RLC PDU s2重传失败；对不分片数据包，PDCP PDU(SN＝n1)重传失败；
步骤608、返回未传输成功的RLC包(如RLC分片s2)，并携带PDCP PDU SN信息；
步骤609、选择更优链路2，并在链路2重传RLC分片s2，并携带链路1的标识转发给链路2；
步骤610、在链路2重传RLC分片s2；
步骤611、收到RLC PDU s2包后，在终端上重组RLC分片。继续后 续的信令交互。
本申请实施例中，还可以通过链路1-RLC返回PDCP PDU传输状态报告(包含未传输成功的RLC PDU的起始状态)，PDCP收到此传输报告后，生成RLC PDU，并携带链路1的标识，选择更优的链路2进行传输。
方案5：另外针对DU切换场景，也可以重传RLC分片包，如图8-图9所示。方案5区别于上述多连接中“双发双收的场景”，方案5是多连接中“单发单收的场景”
图8为PDCP触发重传的流程，包括如下步骤：
步骤701、与链路1建立连接；
步骤702、传输下行数据包PDCP PDU(SN＝n1,n2...)；
步骤703、PDCP n1被分片为RLC分片s1、s2、s3，或者不分片s；
步骤704、发生从链路1到链路2的切换，同时与链路2建立连接；
步骤705、上报PDCP状态报告，即PDCP status report；
步骤706、链路传输失败，如链路1:PDCP PDU(SN＝n1)没有重传成功；
步骤707、请求PDCP PDU(SN＝n2)传输状态；
步骤708、链路传输失败，如链路1：对分段数据包，PDCP PDU(SN＝n1)中RLC PDU s2重传失败；对不分片数据包，PDCP PDU(SN＝n1)重传失败；
步骤709、返回未传输成功的RLC包(如RLC分片s2)，并携带PDCP PDU SN信息；
步骤710、选择更优链路2，并在链路2重传RLC分片s2，并携带链路1的信息转发给链路2；
步骤711、在链路2重传RLC分片s2；
步骤712、收到RLC PDU s2包后，在终端上重组RLC分片。继续后 续的信令交互。
图9为RLC触发重传的流程，包括如下步骤：
步骤801、与链路1建立连接；
步骤802、传输数据包PDCP PDU(SN＝n1,n2...)；
步骤803、PDCP n1被分片为RLC分片s1、s2、s3，或者不分片s；
步骤804、发生从链路1到链路2的切换，同时与链路2建立连接；
步骤805、链路传输失败，如链路1：对分段数据包，PDCP PDU(SN＝n1)中RLC PDU s2重传失败；对不分片数据包，PDCP PDU(SN＝n1)s重传失败；
步骤806、返回未传输成功的RLC包(如RLC分片s2)，并携带PDCP PDU SN信息；
步骤807、选择更优链路2，并在链路2重传RLC分片s2，并携带链路1的信息转发给链路2；
步骤808、在链路2重传RLC分片s2；
步骤809、收到RLC PDU s2包后，在终端上重组RLC分片。继续后续的信令交互。
采用上述方案1-5，通过CU和DU之间的交互来实现多链路下的PDCP或者RLC包的快速重传。可以在多链路间实现快速的重传，并可以实现RLC PDU在不同链路间的重传，避免重传整个PDCP PDU。
本申请实施例所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本申请各个实施例所述方法的全部或 部分。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。这样，本申请实施例不限制于任何特定的硬件和软件结合。
相应的，本申请实施例还提供一种计算机存储介质，其中存储有计算机程序，该计算机程序用于执行本申请实施例的多连接下实现多链路重传的方法。
以上所述，仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围。
工业实用性
采用本申请实施例，在终端接入至少两条链路；当终端在一个链路上数据包传输失败时，第二网元上报状态报告；所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。由于，在终端多个链路中的一个链路数据包传输失败时，可以在另一个链路上实现传输失败数据包的快速重传，从而实现了终端多连接下的数据包重传处理，适用于第一网元为CU，第二网元为DU的接入网CU-DU架构的重传处理，且不限于CU-DU架构的场景。

Claims (16)

  1. 一种多连接下实现多链路重传的方法，所述方法包括：
    终端接入至少两条链路；
    当终端在一个链路上数据包传输失败时，第二网元上报状态报告；
    所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    由所述第一网元为所述至少两条链路分配分流后的多个数据包。
  3. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述第二网元对所述多个数据包分片后，将多个分片数据包提供给终端进行传输。
  4. 根据权利要求1至3任一项所述的方法，其中，所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传，包括：
    从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
  5. 根据权利要求1至3任一项所述的方法，所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传；
    所述第一网元解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，选择其他的链路进行数据重传。
  6. 根据权利要求5所述的方法，其中，所述方法还包括：
    所述第一网元从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；
    所述第一网元将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，i为大于等于1的正整数。
  7. 一种基站，所述基站包括第一网元和第二网元；其中，
    所述第一网元，配置为在终端接入至少两条链路，当终端在一个链路上数据包传输失败时接收第二网元上报的状态报告；解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传；
    所述第二网元，配置为上报所述状态报告。
  8. 根据权利要求7所述的基站，其中，所述第一网元，进一步配置为为所述至少两条链路分配分流后的多个数据包。
  9. 根据权利要求7所述的基站，其中，所述第二网元，进一步配置为对所述多个数据包分片后，将多个分片数据包提供给终端进行传输。
  10. 根据权利要求7至9任一项所述的基站，其中，所述第一网元，进一步配置为：
    从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，将第一链路上传输的数据包在所述i个链路上进行重传，i为大于等于1的正整数。
  11. 根据权利要求7至9任一项所述的基站，其中，所述第一网元，进一步配置为：
    解析出所述状态报告为第一链路数据包中第x分片数据包传输失败时，选择其他的链路进行数据重传。
  12. 根据权利要求11所述的基站，其中，所述第一网元，进一步配置为：
    从所述至少两条链路中选择链路传输质量优于第一链路的i个链路，所述x为大于等于1的正整数；
    将从所述状态报告中得到的第一链路标识转发给所述i个链路，根据所述第一链路标识将第一链路上传输的第x分片数据包在所述i个链路上进行重传，i为大于等于1的正整数。
  13. 一种多连接下实现多链路重传的方法，所述方法包括：
    在终端接入至少两条链路；
    当终端在一个链路上数据包传输失败时，第一网元接收第二网元上报的状态报告；
    所述第一网元解析出所述状态报告为第一链路数据包传输失败时，选择其他的链路进行数据重传。
  14. 根据权利要求13所述的方法，其中，所述方法还包括：
    由所述第一网元为所述至少两条链路分配分流后的多个数据包。
  15. 一种基站，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器；
    其中，所述处理器用于运行所述计算机程序时实现权利要求1-6、权利要求13-14任一项所述方法的步骤。
  16. 一种存储介质，其上存储有计算机程序，其中，该计算机程序被处理器执行时实现权利要求1-6、权利要求13-14任一项所述方法的步骤。
PCT/CN2018/080365 2017-03-24 2018-03-23 一种多连接下实现多链路重传的方法及基站、存储介质 Ceased WO2018171775A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/497,227 US20200382243A1 (en) 2017-03-24 2018-03-23 Method of multi-link retransmission under multiple connections, base station and storage medium
EP18771616.2A EP3595219B1 (en) 2017-03-24 2018-03-23 Method of multi-link retransmission under multiple connections, base station and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710184917.5 2017-03-24
CN201710184917.5A CN108631961A (zh) 2017-03-24 2017-03-24 一种多连接下实现多链路重传的方法及基站

Publications (1)

Publication Number Publication Date
WO2018171775A1 true WO2018171775A1 (zh) 2018-09-27

Family

ID=63584146

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/080365 Ceased WO2018171775A1 (zh) 2017-03-24 2018-03-23 一种多连接下实现多链路重传的方法及基站、存储介质

Country Status (4)

Country Link
US (1) US20200382243A1 (zh)
EP (1) EP3595219B1 (zh)
CN (1) CN108631961A (zh)
WO (1) WO2018171775A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3905567A4 (en) * 2018-12-24 2022-03-02 ZTE Corporation Data retransmission indication and processing method and device

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7020163B2 (ja) * 2018-02-15 2022-02-16 日本電信電話株式会社 データ転送方法、データ転送装置及びプログラム
WO2020186521A1 (zh) * 2019-03-21 2020-09-24 华为技术有限公司 一种数据传输方法及装置
EP3913832A4 (en) 2019-03-22 2022-01-12 Huawei Technologies Co., Ltd. COMMUNICATION METHOD, APPARATUS, DEVICE, SYSTEM, AND STORAGE MEDIA
CN111294146B (zh) 2019-04-12 2021-08-10 展讯通信（上海）有限公司 数据帧的重传方法及装置
CN111294859B (zh) * 2019-05-24 2021-09-07 展讯通信（上海）有限公司 数据分组的传输方法及装置、存储介质、终端
CN110662259B (zh) * 2019-12-02 2020-04-17 武汉慧联无限科技有限公司 一种报文处理方法、装置及计算机存储介质
CN113923798A (zh) * 2020-07-10 2022-01-11 华为技术有限公司 链路的错误恢复方法及装置
US11936566B2 (en) * 2020-12-18 2024-03-19 Dish Wireless L.L.C. Intelligent router bonding 5G telephony and digital subscriber line services
EP4482069A1 (en) * 2023-06-20 2024-12-25 Deutsche Telekom AG Methods, computer programs, and apparatuses for a data receiver, an intermediate node, and a data transmitter, user equipment, access node, and proxy entity
CN120512415A (zh) * 2024-02-07 2025-08-19 华为技术有限公司 数据重传方法、数据传输系统以及网络装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102377547A (zh) * 2010-08-10 2012-03-14 中兴通讯股份有限公司 一种多载波系统中数据重传方法及系统
CN103326831A (zh) * 2013-06-04 2013-09-25 华为终端有限公司 在多路传输控制协议中的链路处理方法和移动终端
CN104205706A (zh) * 2012-03-26 2014-12-10 瑞典爱立信有限公司 选择mimo秩的方法以及相关设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100471101C (zh) * 2005-08-29 2009-03-18 华为技术有限公司 基于错误反馈机制的数据重传方法及相应系统
CN102318217B (zh) * 2008-12-30 2014-09-03 意大利电信股份公司 安排信号交换的方法和设备以及分布式天线系统
CN101510816B (zh) * 2009-03-05 2012-06-20 北京交通大学 基于路径关联化的多路径并行传输方法
CN104080121B (zh) * 2013-03-26 2019-04-26 中兴通讯股份有限公司 一种传输数据的方法及系统
US20140369392A1 (en) * 2013-06-13 2014-12-18 Alcatel-Lucent Usa Inc. Multi-standard compatible communication system
KR101881969B1 (ko) * 2014-02-28 2018-07-25 후아웨이 테크놀러지 컴퍼니 리미티드 데이터 재전송 방법 및 장치
CN108574967B (zh) * 2017-03-13 2021-08-03 中兴通讯股份有限公司 一种数据传输方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102377547A (zh) * 2010-08-10 2012-03-14 中兴通讯股份有限公司 一种多载波系统中数据重传方法及系统
CN104205706A (zh) * 2012-03-26 2014-12-10 瑞典爱立信有限公司 选择mimo秩的方法以及相关设备
CN103326831A (zh) * 2013-06-04 2013-09-25 华为终端有限公司 在多路传输控制协议中的链路处理方法和移动终端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3595219A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3905567A4 (en) * 2018-12-24 2022-03-02 ZTE Corporation Data retransmission indication and processing method and device
US12021641B2 (en) 2018-12-24 2024-06-25 Zte Corporation Data retransmission indication and processing method and device

Also Published As

Publication number Publication date
EP3595219A1 (en) 2020-01-15
US20200382243A1 (en) 2020-12-03
EP3595219B1 (en) 2021-01-13
CN108631961A (zh) 2018-10-09
EP3595219A4 (en) 2020-03-11

Similar Documents

Publication Publication Date Title
WO2018171775A1 (zh) 一种多连接下实现多链路重传的方法及基站、存储介质
CN114731560B (zh) 下一代无线通信系统中在daps移交期间驱动pdcp实体的方法和装置
US20220264368A1 (en) Method and apparatus for processing a packet in a wireless communication system
US11570846B2 (en) Discard timer operation in wireless communication
JP6631961B2 (ja) スモールセル配備時の効率的な破棄メカニズム
US10555362B2 (en) Radio bearer reconfiguration method, radio bearer establishment method, user equipment, and base station
US10368266B2 (en) Efficient uplink scheduling mechanisms for dual connectivity
CN102939729B (zh) 移动通信系统和移动通信系统中的分组控制方法
KR102460350B1 (ko) 통신 시스템에서 데이터 송수신 방법 및 장치
EP2647175B1 (en) Facilitating device-to-device communication
US11206106B2 (en) Data packet synchronization
US10728801B2 (en) Data processing method and apparatus for LTE and WLAN aggregation and communications system
CN111294839B (zh) 一种pfcp会话处理方法及装置
CN111373837A (zh) 用于在无线通信系统中发送和接收数据的方法和装置
KR20260040338A (ko) L1/l2 트리거 이동성(ltm)에 관련된 방법 및 장치
US10064237B2 (en) Communication apparatus, and layer 2 state control method
WO2017133595A1 (zh) 数据处理的方法及装置
HK40018566B (zh) 一种多连接下实现多链路重传的方法及基站、存储介质
HK40018566A (zh) 一种多连接下实现多链路重传的方法及基站、存储介质
US10419167B2 (en) RLC data packet retransmission method and eNodeB
KR20250142156A (ko) 무선 통신 시스템에서 pdcp 계층의 일련번호 간격 보고를 위한 방법 및 장치
WO2019052174A1 (zh) 一种改变承载类型的方法及装置、计算机存储介质

Legal Events

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

Ref document number: 18771616

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

Country of ref document: EP

Effective date: 20191010