Data transmission method and device and computer readable storage medium

Abstract

Provided in an embodiment of the present specification are a data transmission method, an electronic device and a computer readable storage medium, the method comprising: determining current estimated downlink transmission rates of a first carrier and a second carrier, the first carrier being a carrier mounted on a master node MN, and the second carrier being a carrier mounted on an auxiliary node SN; determining a sending path of a current to-be-sent data packet based on the current estimated downlink transmission rates of the first carrier and the second carrier; and sending the current to-be-sent data packet to a target radio link layer control protocol RLC entity, the target RLC entity sending the current to-be-sent data through the sending path. Therefore, the data reaching the PDCP layer can be reasonably allocated to each carrier, thereby improving the data transmission efficiency.

Description

Technical Field

[0001] This document relates to the field of mobile communication technology, and in particular to a data transmission method, device and computer-readable storage medium. Background Art

[0002] Starting from 5G, mobile communication systems support multiple radio access technologies and introduce dual connection technology. In this technology, a terminal device (User equipment, UE) configured with multiple Rx / Tx can use the radio resources scheduled by two base stations. The two base stations are connected through the Xn / X2 interface, where one base station acts as the master node (Master Node, MN) and the other as the secondary node (Secondary Node, SN).

[0003] Dual connection technology allows the UE to connect to multiple carriers at the same time, and allows the same bearer to be transmitted on multiple carriers at the same time, that is, split bearer. There are many forms of split bearers under dual connection, including MN-terminated split bearers and SN-terminated split bearers. In the MN-terminated split bearer, the Packet Data Convergence Protocol (PDCP) entity is located on the MN side, and multiple Radio Link Control Protocol (RLC) entities are distributed on different carriers and associated with corresponding carriers. In the SN-terminated split bearer, the PDCP layer is located on the SN side, and multiple RLC layer entities are distributed on different carriers and associated with corresponding carriers.

[0004] After the data stream to be split and carried reaches the PDCP layer, if too little data is allocated to a certain carrier, the resources of the carrier cannot be fully utilized, resulting in a slow traffic ramp-up; if too much data is allocated to a certain carrier, it will cause link congestion, increase the loop delay of the data packet, and affect the overall traffic. Therefore, how to reasonably allocate the data stream arriving at the PDCP layer to each carrier is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of this specification provide a data transmission method, device, and computer-readable storage medium to solve the problem of how to reasonably distribute data arriving at the PDCP layer to each carrier.

[0006] To solve the above technical problems, the embodiments of this specification are implemented as follows:

[0007] In a first aspect, a data transmission method is provided, comprising:

[0008] Determine a current estimated downlink transmission rate of a first carrier and a second carrier, wherein the first carrier is a carrier mounted on a master node MN, and the second carrier is a carrier mounted on a secondary node SN;

[0009] Determine a sending path of a data packet to be sent based on current estimated downlink transmission rates of the first carrier and the second carrier;

[0010] The current data packet to be sent is sent to a target radio link layer control protocol RLC entity, wherein the target RLC entity sends the current data packet to be sent through the sending path.

[0011] In a second aspect, a data transmission method is provided, comprising:

[0012] Determine the current estimated downlink transmission rate of the carrier based on preset parameters of the carrier mounted on the node where the radio link layer control protocol RLC entity is located, wherein the node includes a master node MN or a secondary node SN;

[0013] The current estimated downlink transmission rate of the carrier is reported to a Packet Data Convergence Protocol (PDCP) entity, wherein the current estimated downlink transmission rate of the carrier is used by the PDCP entity to determine a transmission path of a data packet to be currently sent at the PDCP entity.

[0014] In a third aspect, a data transmission device is provided, comprising:

[0015] A rate determination module, configured to determine a current estimated downlink transmission rate of a first carrier and a second carrier, wherein the first carrier is a carrier mounted on a master node MN, and the second carrier is a carrier mounted on a secondary node SN;

[0016] a path determination module, configured to determine a transmission path of a data packet to be sent based on current estimated downlink transmission rates of the first carrier and the second carrier;

[0017] A data sending module is used to send the current data packet to be sent to a target radio link layer control protocol RLC entity, wherein the target RLC entity sends the current data packet to be sent through the sending path.

[0018] In a fourth aspect, a data transmission device is provided, comprising:

[0019] A rate sensing module, configured to determine a current estimated downlink transmission rate of a carrier mounted on a node where a radio link layer control protocol RLC entity is located based on preset parameters of the carrier, wherein the node includes a master node MN or a slave node SN;

[0020] The rate reporting module is used to report the current estimated downlink transmission rate of the carrier to the Packet Data Convergence Protocol PDCP entity, wherein the current estimated downlink transmission rate of the carrier is used by the PDCP entity to determine the sending path of the current data packet to be sent at the PDCP entity.

[0021] In a fifth aspect, an electronic device is provided, including:

[0022] processor;

[0023] a memory for storing instructions executable by the processor;

[0024] The processor is configured to execute the instructions to implement the method as described in the first aspect.

[0025] In a sixth aspect, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method described in the first aspect.

[0026] In an embodiment of the present specification, for the first carrier mounted on the main node MN and the second carrier mounted on the auxiliary node SN, the sending path of the current data packet to be sent is determined based on the current estimated downlink transmission rates of the two, that is, the perceived rate of the first carrier and the second carrier - the current estimated downlink transmission rate, is used as a reference basis for downlink split bearer. In this way, the capacity of each carrier can be fully utilized, the waste of scheduling resources due to unclear air interface capabilities of different carriers or the decrease in user traffic caused by congestion can be reduced, and the data reaching the PDCP layer can be reasonably distributed to each carrier, thereby improving data transmission efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0028] Figure 1 This is a schematic diagram of a dual connection network provided by an embodiment of this specification.

[0029] Figure 2 It is a schematic diagram of split bearer termination of a DC MN connected to an EPC provided by an embodiment of this specification.

[0030] Figure 3 This is a schematic diagram of split bearer termination of a DC SN connected to an EPC provided by an embodiment of this specification.

[0031] Figure 4 This is a split bearer diagram of a DC MN termination connected to a 5GC provided by an embodiment of this specification.

[0032] Figure 5 This is a schematic diagram of split bearer termination of DC SN connected to 5GC provided by an embodiment of this specification.

[0033] Figure 6 It is a flowchart of a data transmission method provided by an embodiment of this specification.

[0034] Figure 7 It is a flowchart of a data transmission method provided by another embodiment of the present specification.

[0035] Figure 8 It is a schematic diagram of an implementation architecture of a data transmission method provided by an embodiment of this specification.

[0036] Fig. 9 It is a schematic diagram of a split bearing architecture of a data transmission method provided by an embodiment of this specification.

[0037] Fig.10 It is a structural diagram of a data transmission device provided by an embodiment of this specification.

[0038] Fig.11 It is a structural schematic diagram of a data transmission device provided by another embodiment of the present specification. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0040] The terms "first", "second", etc. in this specification and claims are used to distinguish similar objects, and are not used to describe a particular order or precedence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of this specification can be implemented in an order other than those illustrated or described herein. In addition, "and / or" in this specification and claims means at least one of the connected objects, and the character " / " generally means that the objects associated with each other are in an "or" relationship.

[0041] In order to solve the problem of how to reasonably distribute the data arriving at the PDCP entity to each carrier mounted by the RLC entity, an embodiment of this specification proposes a data transmission method. The data transmission method can be applied to split bearer data diversion in a dual connectivity (DC) scenario in a wireless mobile communication network. These dual connectivity scenarios may include but are not limited to dual connectivity between 4G base stations and 4G base stations, dual connectivity between 4G base stations and 5G base stations, dual connectivity between 5G base stations and 5G base stations, and multiple connectivity.

[0042] There are many forms of split bearer under dual connectivity, including MN-terminated split bearer and SN-terminated split bearer. In MN-terminated split bearer, the Packet Data Convergence Protocol (PDCP) entity is located on the MN side, and multiple Radio Link Control (RLC) entities are distributed on different carriers and associated with the corresponding carriers. In SN-terminated split bearer, the PDCP layer is located on the SN side, and multiple RLC layer entities are distributed on different carriers and associated with the corresponding carriers.

[0043] The following is a brief description of a dual connection networking structure and split bearer conditions in different dual connection scenarios.

[0044] Figure 1 This is a schematic diagram of dual-connection networking of a 5G core network (Fifth Generation Core, 5GC) and an evolved packet core network (Evolved Packet Core, EPC) provided by an embodiment of this specification. Figure 1 In the figure on the left, the control plane of 5GC / EPC is connected to the master node (MN) through NG-C / S1-C, the user plane is connected to MN through NG-U / S1-U, MN and secondary node (SN) are connected through Xn / X2 ports, and UE is connected to MN and SN through air interfaces at the same time; the right figure is a schematic diagram of the network in which the control plane of 5GC / EPC is connected to MN through NG-C / S1-C, the user plane is connected to SN through NG-U / S1-U, MN and SN are connected through Xn / X2 ports, and UE is connected to MN and SN through air interfaces at the same time. Among them, 5GC is a 5G core network node, and EPC is a 4G core network node; the control plane is used to transmit control information, and the user plane is used to transmit service data.

[0045] Figure 2FIG. 1 is a schematic diagram of split bearer termination by a dual connectivity master node (DC MN) connected to an EPC, provided by an embodiment of the present specification. Figure 2 As shown in the figure, the data flows carried are aggregated in the NR PDCP of the MN, and the NR PDCP is connected to the RLC of the MN and the SN respectively. Figure 2 In this specification, NR stands for New Radio, PDCP stands for Packet Data Convergence Protocol, RLC stands for Radio Link Control, MAC stands for Media Access Control, and E-UTRA stands for Evolved Universal Terrestrial Radio Access, the same below.

[0046] Figure 3 FIG. 1 is a schematic diagram of a split bearer terminated by a dual connectivity secondary node (DC SN) connected to an EPC, provided by an embodiment of the present specification. Figure 3 As shown, the carried data flows are aggregated at the NR PDCP of the SN, and the NR PDCP is connected to the RLC of the MN and the SN respectively.

[0047] Figure 4 FIG. 1 is a schematic diagram of split bearer terminated by a DC MN connected to a 5GC provided by an embodiment of this specification. Figure 4 As shown, the bearer data flow converges in the NR PDCP of the MN, and the NR PDCP connects the RLC of the MN and the SN respectively. Among them, SDAP (Service Data Adaptation Protocol) is a new protocol layer introduced by the 5G protocol, which is used for mapping the wireless side data flow to the bearer, the same below.

[0048] Figure 5 FIG. 1 is a schematic diagram of split bearer terminated by a DC SN connected to a 5GC provided by an embodiment of this specification. Figure 5 As shown, the carried data flows are aggregated at the NR PDCP of the SN, and the NR PDCP is connected to the RLC of the MN and the SN respectively.

[0049] The data transmission method provided in the embodiments of this specification can be applied to but not limited to Figure 1 The dual-connection networking scenario shown, and Figure 2 , Figure 3 , Figure 4or Figure 5 Any split bearer scenario shown.

[0050] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0051] Figure 6 is a flowchart of a data transmission method provided by an embodiment of this specification. The method can be applied to Figure 2 , Figure 3 , Figure 4 or Figure 5 PDCP entities in the equally split bearer scenario, such as Figure 6 As shown, the method may include:

[0052] Step 601, determining currently estimated downlink transmission rates of a first carrier and a second carrier, wherein the first carrier is a carrier mounted on a master node MN, and the second carrier is a carrier mounted on a slave node SN.

[0053] There are two implementation methods for determining the current estimated downlink transmission rates of the first carrier and the second carrier.

[0054] Implementation method 1: determining and reporting by the RLC entity.

[0055] Specifically, determining the current estimated downlink transmission rates of the first carrier and the second carrier may include:

[0056] receiving a current estimated downlink transmission rate for a first carrier estimated and reported by a first RLC entity, wherein the first RLC entity is located in the MN, and the current estimated downlink transmission rate of the first carrier is estimated by the first RLC entity according to a preset parameter of the first carrier;

[0057] Receive a current estimated downlink transmission rate for a second carrier estimated and reported by a second RLC entity, wherein the second RLC entity is located at the SN, and the current estimated downlink transmission rate of the second carrier is estimated by the second RLC entity based on preset parameters of the second carrier.

[0058] Implementation method 2: determined by the PDCP entity.

[0059] Specifically, determining the current estimated downlink transmission rates of the first carrier and the second carrier may include:

[0060] estimating a current estimated downlink transmission rate of the first carrier according to a preset parameter of the first carrier;

[0061] According to the preset parameters of the second carrier, a current estimated downlink transmission rate of the second carrier is estimated.

[0062] The preset parameters may include but are not limited to at least one of the following: downlink channel quality, downlink physical resource block PRB load, wireless frame structure, number of users and service priority.

[0063] Among them, determining the current estimated downlink transmission rate of the carrier according to the preset parameters of the carrier may include: determining the current estimated downlink transmission rate of the carrier based on a predetermined rate estimation model and the preset parameters of the carrier, wherein the rate estimation model is a function of the preset parameters.

[0064] The rate estimation model can be expressed as:

[0065] v(i)=f(downlink channel quality, downlink physical resource block PRB load, wireless frame structure, number of users, service priority, ...), where i represents different carrier numbers.

[0066] In the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated or negatively correlated with a preset parameter of the carrier.

[0067] Specific:

[0068] 1) If the preset parameters of the carrier include downlink channel quality, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the downlink channel quality of the carrier. The better the downlink channel quality, the greater the current estimated downlink transmission rate.

[0069] 2) If the preset parameters of the carrier include the load of the downlink physical resource block PRB, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is negatively correlated with the load of the downlink PRB of the carrier. The smaller the load of the downlink PRB, the greater the current estimated downlink transmission rate.

[0070] 3) If the preset parameters of the carrier include a wireless frame structure, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the proportion of downlink subframes in the wireless frame structure of the carrier. The greater the proportion of downlink subframes in the wireless frame structure of the carrier, the greater the current estimated downlink transmission rate.

[0071] 4) If the preset parameters of the carrier include the number of users, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is negatively correlated with the number of users of the carrier. The fewer the number of users of the carrier, the greater the current estimated downlink transmission rate.

[0072] 5) If the preset parameters of the carrier include service priority, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the service priority, and the higher the service priority, the greater the current estimated downlink transmission rate.

[0073] Step 602: Determine a sending path for a data packet to be sent based on currently estimated downlink transmission rates of the first carrier and the second carrier.

[0074] It should be noted that the current data packet to be sent mentioned in step 602 refers to the current data packet to be sent that needs to be split and carried at the PDCP entity.

[0075] The PDCP entity may be located in the MN or the SN. For a split bearer terminated by the MN, the PDCP is located in the MN, and for a split bearer terminated by the SN, the PDCP is located in the SN.

[0076] As an example, step 602 may include: comparing the currently estimated downlink transmission rates of the first carrier and the second carrier, determining the carrier with the highest currently estimated downlink transmission rate between the first carrier and the second carrier; determining the carrier with the highest currently estimated downlink transmission rate as the downlink main path carrying the data to be sent; and determining the downlink main path as the sending path of the data packet to be sent. That is, the carrier with the highest currently estimated downlink transmission rate between the first carrier and the second carrier is directly used as the sending path of the data packet to be sent.

[0077] As another example, the estimated time required to send the currently remaining historical data packets to be sent on the first carrier and the second carrier may be determined respectively, and then the sending path of the current data packet to be sent may be determined according to the estimated time corresponding to each of the first carrier and the second carrier and the current estimated downlink transmission rate. That is, step 602 may include: determining the sending path of the current data packet to be sent based on the current estimated downlink transmission rate of the first carrier, the current estimated downlink transmission rate of the second carrier, the estimated time corresponding to the first carrier, and the estimated time corresponding to the second carrier.

[0078] It can be understood that the estimated time required to send the currently remaining historical data packets to be sent on the first carrier and the second carrier (i.e., the currently remaining historical data packets to be sent at the RLC entity) is also used as a reference for determining the sending path of the current data packets to be sent at the PDCP entity. This can make the sending path determined for the current data packets to be sent at the PDCP entity more reasonable and will not cause traffic congestion on the first carrier or the second carrier.

[0079] The determining of the estimated time required to send the currently remaining historical data packets to be sent on the first carrier and the second carrier respectively may include:

[0080] receiving an amount of first data reported by a first RLC entity, wherein the first RLC entity is located in the MN, and the first data includes historical data packets to be sent currently remaining on the first carrier;

[0081] receiving an amount of second data reported by a second RLC entity, wherein the second RLC entity is located at the SN, and the second data includes historical data packets to be sent currently remaining on the second carrier;

[0082] Determine, based on the amount of the first data and the current estimated downlink transmission rate of the first carrier, an estimated time required to send the historical data packets to be sent currently remaining on the first carrier;

[0083] Based on the amount of the second data and the current estimated downlink transmission rate of the second carrier, an estimated time required to send the historical data packets to be sent currently remaining on the second carrier.

[0084] It can be understood that the estimated time required for the remaining historical data packets to be sent on a carrier is generally: the amount of the remaining historical data packets to be sent on the carrier divided by the current estimated downlink transmission rate of the carrier. That is, t(i) = the remaining historical data packets to be sent on the carrier / v(i), where t(i) represents the estimated time, and v(i) represents the current estimated downlink transmission rate.

[0085] Wherein, determining the sending path of the current data packet to be sent based on the current estimated downlink transmission rate of the first carrier, the current estimated downlink transmission rate of the second carrier, the estimated time consumption corresponding to the first carrier, and the estimated time consumption corresponding to the second carrier may include:

[0086] Comparing currently estimated downlink transmission rates of the first carrier and the second carrier, and determining a carrier having a maximum currently estimated downlink transmission rate between the first carrier and the second carrier;

[0087] Determine a carrier with the maximum currently estimated downlink transmission rate as a downlink main path for carrying the currently to-be-sent data;

[0088] Based on the estimated time consumption corresponding to the downlink main path and the estimated time consumption corresponding to the remaining carriers in the first carrier and the second carrier, a sending path for the current data packet to be sent is determined.

[0089] Furthermore, the determining, based on the estimated time consumption corresponding to the downlink main path and the estimated time consumption corresponding to the remaining carriers in the first carrier and the second carrier, a sending path of the current data packet to be sent includes:

[0090] 1) when the estimated time consumption corresponding to the downlink main path meets the first preset condition, determining the downlink main path as the sending path of the current data packet to be sent;

[0091] 2) when the estimated time consumption corresponding to the downlink main path meets the second preset condition, determining the carrier with the smallest estimated time consumption between the first carrier and the second carrier as the sending path of the current data packet to be sent;

[0092] 3) When the estimated time consumption corresponding to the first carrier or the second carrier satisfies a third preset condition, the carrier is not used as a sending path for the data packet to be sent.

[0093] The first preset condition includes: the estimated time is less than the first threshold; the second preset condition includes: the estimated time is greater than or equal to the first threshold and less than the second threshold; the third preset condition includes: the estimated time is greater than the second threshold. The first threshold is the preset minimum buffer delay of the data to be sent in the RLC entity; the second threshold is the preset maximum buffer delay of the data to be sent in the RLC entity.

[0094] Specifically, assuming that the first threshold is Tmin, the second threshold is Tmax, t(i) represents the estimated time consumption, and v(i) represents the current estimated downlink transmission rate, then the above rule (diversion rule) for determining the sending path of the current data packet to be sent at the PDCP entity can be specifically expressed as:

[0095] 1) When t(i) corresponding to the downlink main path is less than Tmin, the downlink main path is determined as the sending path of the current data packet to be sent;

[0096] 2) When t(i) corresponding to the downlink main path is greater than or equal to Tmin, the carrier with the smallest t(i) between the first carrier and the second carrier is determined as the sending path of the current data packet to be sent.

[0097] 3) When t(i) corresponding to any one of the first carrier and the second carrier is greater than Tmax, data is not sent on the carrier.

[0098] It should be noted that in the embodiment of this specification, the first carrier or the second carrier may be a single carrier or an aggregated carrier, and accordingly, the sending path of the current data packet to be sent at the PDCP entity may also be a single carrier or an aggregated carrier, which is specifically divided into the following cases:

[0099] 1) If both the first carrier and the second carrier are single carriers, the current estimated downlink transmission rate of the first carrier is its own current estimated downlink transmission rate, the current estimated downlink transmission rate of the second carrier is its own current estimated downlink transmission rate, and the transmission path is a single carrier among the first carrier and the second carrier.

[0100] In layman's terms, when the RLC entity carries a single carrier (the first carrier or the second carrier is a single carrier), traffic is split in carrier units, that is, traffic is split in RLC units.

[0101] 2) If the first carrier is a first aggregated carrier including multiple first component carriers, and the second carrier is a second aggregated carrier including multiple second component carriers, the current estimated downlink transmission rate of the first carrier is the sum of the current estimated downlink transmission rates of the multiple first component carriers, the current estimated downlink transmission rate of the second carrier is the sum of the current estimated downlink transmission rates of the multiple second component carriers, and the sending path is the first aggregated carrier or the second aggregated carrier.

[0102] In layman's terms, when the RLC entity carries multiple carriers (the first carrier or the second carrier is an aggregated carrier), the current estimated downlink transmission rates of the component carriers are aggregated and reported (added), and traffic is split in units of aggregated carriers, that is, in units of RLC.

[0103] 3) If the first carrier includes a plurality of first component carriers, and the second carrier includes a plurality of second component carriers, the current estimated downlink transmission rate of the first carrier includes a current estimated downlink transmission rate of each of the plurality of first component carriers, the current estimated downlink transmission rate of the second carrier includes a current estimated downlink transmission rate of each of the plurality of second component carriers, and the transmission path is a single carrier among the plurality of first component carriers and the plurality of second component carriers.

[0104] In layman's terms, when the RLC entity carries multiple carriers (the first carrier or the second carrier includes multiple component carriers), the current estimated downlink transmission rates of the component carriers are reported separately (without aggregation) and traffic is split in units of carriers.

[0105] It should be noted that, at the PDCP entity, the diversion of the current data packet to be sent is dynamic. Generally, for a data packet to be sent, t(i) corresponding to the first carrier and the second carrier is calculated once, and the current estimated downlink transmission rate of the first carrier and the second carrier is combined to determine which carrier to distribute the data packet to.

[0106] Step 603: Send the current data packet to be sent to a target radio link layer control protocol RLC entity, wherein the target RLC entity sends the current data packet to be sent through the sending path.

[0107] The target RLC entity is the first RLC entity or the second RLC entity.

[0108] Through step 603, the current data packet to be sent at the PDCP entity can be sent to the target RLC entity corresponding to the sending path, so that the target RLC entity sends the current data packet to be sent through the sending path.

[0109] A data transmission method provided in an embodiment of the present specification determines, for a first carrier mounted on a main node MN and a second carrier mounted on a secondary node SN, a sending path of a current data packet to be sent based on the current estimated downlink transmission rates of the two, that is, the perceived rate of the first carrier and the second carrier - the current estimated downlink transmission rate, is used as a reference basis for downlink splitting of the bearer. In this way, the capacity of each carrier can be fully utilized, the waste of scheduling resources due to unclear air interface capabilities of different carriers or the decrease in user traffic caused by congestion can be reduced, and the data arriving at the PDCP layer can be reasonably distributed to each carrier, thereby improving data transmission efficiency.

[0110] Figure 7 is a flowchart of a data transmission method provided by another embodiment of this specification. The method can be applied to Figure 2 , Figure 3 , Figure 4 or Figure 5 In the equally split bearer scenario, the RLC entity can be located in either the MN or the SN. Figure 7 As shown, the method may include:

[0111] Step 701, based on preset parameters of a carrier mounted on a node where a radio link layer control protocol RLC entity is located, determine a current estimated downlink transmission rate of the carrier, wherein the node includes a master node MN or a slave node SN.

[0112] As an example, step 701 may include: determining the current estimated downlink transmission rate of the carrier based on a predetermined rate estimation model and preset parameters of the carrier mounted on the node where the RLC entity is located, wherein the rate estimation model is a function of the preset parameters.

[0113] The preset parameters include at least one of downlink channel quality, downlink physical resource block PRB load, wireless frame structure, number of users and service priority.

[0114] The rate estimation model can be expressed as:

[0115] v(i)=f(downlink channel quality, downlink physical resource block PRB load, wireless frame structure, number of users, service priority, ...), where i represents different carrier numbers.

[0116] In the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated or negatively correlated with a preset parameter of the carrier.

[0117] Specific:

[0118] 1) If the preset parameters of the carrier include downlink channel quality, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the downlink channel quality of the carrier. The better the downlink channel quality, the greater the current estimated downlink transmission rate.

[0119] 2) If the preset parameters of the carrier include the load of the downlink physical resource block PRB, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is negatively correlated with the load of the downlink PRB of the carrier. The smaller the load of the downlink PRB, the greater the current estimated downlink transmission rate.

[0120] 3) If the preset parameters of the carrier include a wireless frame structure, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the proportion of downlink subframes in the wireless frame structure of the carrier. The greater the proportion of downlink subframes in the wireless frame structure of the carrier, the greater the current estimated downlink transmission rate.

[0121] 4) If the preset parameters of the carrier include the number of users, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is negatively correlated with the number of users of the carrier. The fewer the number of users of the carrier, the greater the current estimated downlink transmission rate.

[0122] 5) If the preset parameters of the carrier include service priority, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the service priority, and the higher the service priority, the greater the current estimated downlink transmission rate.

[0123] Step 702: reporting the current estimated downlink transmission rate of the carrier to a Packet Data Convergence Protocol (PDCP) entity, wherein the current estimated downlink transmission rate of the carrier is used by the PDCP entity to determine a transmission path for a data packet to be currently sent at the PDCP entity.

[0124] It should be noted that, in the embodiment of the present specification, the carrier mounted by the RLC entity may be a single carrier or an aggregated carrier. Accordingly, step 702 may include:

[0125] If the carrier is a single carrier, reporting the current estimated downlink transmission rate of the carrier separately to the PDCP entity;

[0126] If the carrier is a component carrier in an aggregated carrier, the current estimated downlink transmission rate of the carrier and the current estimated downlink transmission rates of other component carriers are added together and reported to the PDCP entity.

[0127] More specifically, it can be divided into the following three situations:

[0128] 1) If the carrier mounted by the node where the RLC entity is located is a single carrier, reporting the current estimated downlink transmission rate of the carrier to the PDCP entity includes: reporting the current estimated downlink transmission rate of the single carrier to the PDCP entity;

[0129] 2) If the carrier mounted on the node where the RLC entity is located is an aggregated carrier including multiple component carriers, reporting the current estimated downlink transmission rate of the carrier to the PDCP entity includes: adding the current estimated downlink transmission rates of the multiple component carriers and reporting the sum to the PDCP entity;

[0130] 3) If the carrier mounted on the node where the RLC entity is located includes multiple component carriers, then reporting the current estimated downlink transmission rate of the carrier to the PDCP entity includes: reporting the current estimated downlink transmission rates of the multiple component carriers to the PDCP entity respectively.

[0131] A data transmission method provided in an embodiment of the present specification comprises the following steps: an RLC entity determines the current estimated downlink transmission rate of the carrier mounted on itself and reports it to the PDCP entity, so that the PDCP entity determines the sending path of the current data packet to be sent according to the current estimated downlink transmission rate of each carrier, that is, the perceived rate of the carrier - the current estimated downlink transmission rate, is used as a reference basis for downlink splitting of the bearer. In this way, the capacity of each carrier can be fully utilized, the waste of scheduling resources due to unclear air interface capabilities of different carriers or the decrease in user traffic caused by congestion can be reduced, and the data reaching the PDCP layer can be reasonably distributed to each carrier, thereby improving data transmission efficiency.

[0132] Optional, Figure 7 The method shown may also include: reporting to the PDCP entity the amount of data of the historical data packets currently remaining on the carrier to be sent, wherein the data amount is used to determine the estimated time required to send the historical data packets currently remaining on the carrier to be sent, and the estimated time is used by the PDCP entity to determine the sending path of the current data packets to be sent at the PDCP entity.

[0133] It can be understood that the estimated time required to send the currently remaining historical data packets to be sent on the corresponding carrier (i.e., the currently remaining historical data packets to be sent at the RLC entity) can also be used as a reference for determining the sending path of the current data packets to be sent at the PDCP entity. This can make the sending path determined for the current data packets to be sent at the PDCP entity more reasonable and will not cause traffic congestion on the corresponding carrier.

[0134] Figure 8 FIG. 1 is a schematic diagram of an implementation architecture of a data transmission method provided by an embodiment of this specification. Figure 8 In the 5G base station, CU refers to the central unit and DU refers to the distributed unit. The 5G base station divides the baseband unit (BBU) into CU and DU, and connects it to the active antenna unit (AAU) through optical fiber. Among them, the CU is responsible for hosting the radio resource control layer (RRC), service data adaptation protocol (SDAP) and PDCP sublayer of the 5G base station, which centrally controls one or more DU units.

[0135] exist Figure 8 In the PDCP entity, a diversion decision module is provided, and a perception estimation module and an information reporting module are provided in the RLC entity.

[0136] The perception and estimation module is used to obtain preset parameters of a carrier attached to the RLC entity, and determine a current estimated downlink transmission rate of the carrier according to the estimated parameters of the carrier.

[0137] The information reporting module is used to report the current estimated downlink transmission rate of the carrier to the diversion decision module in the PDCP entity. Optionally, the amount of historical data packets remaining to be sent on the carrier can also be reported to the diversion decision module in the PDCP entity.

[0138] The traffic diversion decision module is used to receive the current estimated downlink transmission rate of each carrier reported by the RLC entity, and determine the transmission path of the current data packet to be sent at the PDCP entity based on the current estimated downlink transmission rate of each carrier.

[0139] For the detailed functions that can be achieved by the perception estimation module, the information reporting module and the diversion decision module, please refer to the data transmission method described above, which will not be repeated here.

[0140] It should be noted that Figure 8This is just a possible architecture for implementing a data transmission method provided in this specification, and does not mean that a data transmission method provided in this specification can only be implemented through Figure 8 The architecture shown is implemented.

[0141] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0142] Fig. 9 This is a schematic diagram of the structure of an electronic device according to an embodiment of this specification. Fig. 9 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0143] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0144] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0145] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a data transmission device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0146] Determine a current estimated downlink transmission rate of a first carrier and a second carrier, wherein the first carrier is a carrier mounted on a master node MN, and the second carrier is a carrier mounted on a secondary node SN;

[0147] Determine a sending path of a data packet to be sent based on current estimated downlink transmission rates of the first carrier and the second carrier;

[0148] The current data packet to be sent is sent to a target radio link layer control protocol RLC entity, wherein the target RLC entity sends the current data packet to be sent through the sending path.

[0149] Alternatively, the processor executes the program stored in the memory and is specifically configured to perform the following operations:

[0150] Determine the current estimated downlink transmission rate of the carrier based on preset parameters of the carrier mounted on the node where the radio link layer control protocol RLC entity is located, wherein the node includes a master node MN or a secondary node SN;

[0151] The current estimated downlink transmission rate of the carrier is reported to a Packet Data Convergence Protocol (PDCP) entity, wherein the current estimated downlink transmission rate of the carrier is used by the PDCP entity to determine a transmission path of a data packet to be currently sent at the PDCP entity.

[0152] The above is as in this manual Fig. 9The method performed by the data transmission device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of this specification can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of this specification can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0153] The electronic device may also perform Figure 6 or Figure 7 The method shown in the figure realizes the data transmission device in Figure 6 or Figure 7 The functions in the illustrated embodiments will not be described in detail in this specification.

[0154] Of course, in addition to software implementation, the electronic device of this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0155] The embodiment of the present specification also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to execute Figure 6 or Figure 7 The method of the embodiment shown is specifically used to perform the following operations:

[0156] Determine a current estimated downlink transmission rate of a first carrier and a second carrier, wherein the first carrier is a carrier mounted on a master node MN, and the second carrier is a carrier mounted on a secondary node SN;

[0157] Determine a sending path of a data packet to be sent based on current estimated downlink transmission rates of the first carrier and the second carrier;

[0158] The current data packet to be sent is sent to a target radio link layer control protocol RLC entity, wherein the target RLC entity sends the current data packet to be sent through the sending path.

[0159] Or, specifically, to do the following:

[0160] Determine the current estimated downlink transmission rate of the carrier based on preset parameters of the carrier mounted on the node where the radio link layer control protocol RLC entity is located, wherein the node includes a master node MN or a secondary node SN;

[0161] The current estimated downlink transmission rate of the carrier is reported to a Packet Data Convergence Protocol (PDCP) entity, wherein the current estimated downlink transmission rate of the carrier is used by the PDCP entity to determine a transmission path of a data packet to be currently sent at the PDCP entity.

[0162] Fig.10 FIG. 1 is a schematic diagram of a data transmission device 1000 provided in an embodiment of the present specification. The device 1000 can be applied to Figure 2 , Figure 3 , Figure 4 or Figure 5 PDCP entity in the equally split bearer scenario. Please refer to Fig.10 In a software implementation, the data transmission device 1000 may include: a rate determination module 1001, a path determination module 1002 and a data sending module 1003, wherein:

[0163] The rate determination module 1001 is used to determine the current estimated downlink transmission rates of the first carrier and the second carrier, wherein the first carrier is a carrier mounted on the master node MN, and the second carrier is a carrier mounted on the slave node SN.

[0164] There are two implementation methods for determining the current estimated downlink transmission rates of the first carrier and the second carrier.

[0165] Implementation method 1: determining and reporting by the RLC entity.

[0166] Specifically, the rate determination module 1001 may be used to:

[0167] receiving a current estimated downlink transmission rate for a first carrier estimated and reported by a first RLC entity, wherein the first RLC entity is located in the MN, and the current estimated downlink transmission rate of the first carrier is estimated by the first RLC entity according to a preset parameter of the first carrier;

[0168] Receive a current estimated downlink transmission rate for a second carrier estimated and reported by a second RLC entity, wherein the second RLC entity is located at the SN, and the current estimated downlink transmission rate of the second carrier is estimated by the second RLC entity based on preset parameters of the second carrier.

[0169] Implementation method 2: determined by the PDCP entity.

[0170] Specifically, the rate determination module 1001 may be used to:

[0171] estimating a current estimated downlink transmission rate of the first carrier according to a preset parameter of the first carrier;

[0172] According to the preset parameters of the second carrier, a current estimated downlink transmission rate of the second carrier is estimated.

[0173] The preset parameters may include but are not limited to at least one of the following: downlink channel quality, downlink physical resource block PRB load, wireless frame structure, number of users and service priority.

[0174] Among them, determining the current estimated downlink transmission rate of the carrier according to the preset parameters of the carrier may include: determining the current estimated downlink transmission rate of the carrier based on a predetermined rate estimation model and the preset parameters of the carrier, wherein the rate estimation model is a function of the preset parameters.

[0175] The rate estimation model can be expressed as:

[0176] v(i)=f(downlink channel quality, downlink physical resource block PRB load, wireless frame structure, number of users, service priority, ...), where i represents different carrier numbers.

[0177] In the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated or negatively correlated with a preset parameter of the carrier.

[0178] Specific:

[0179] 1) If the preset parameters of the carrier include downlink channel quality, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the downlink channel quality of the carrier. The better the downlink channel quality, the greater the current estimated downlink transmission rate.

[0180] 2) If the preset parameters of the carrier include the load of the downlink physical resource block PRB, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is negatively correlated with the load of the downlink PRB of the carrier. The smaller the load of the downlink PRB, the greater the current estimated downlink transmission rate.

[0181] 3) If the preset parameters of the carrier include a wireless frame structure, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the proportion of downlink subframes in the wireless frame structure of the carrier. The greater the proportion of downlink subframes in the wireless frame structure of the carrier, the greater the current estimated downlink transmission rate.

[0182] 4) If the preset parameters of the carrier include the number of users, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is negatively correlated with the number of users of the carrier. The fewer the number of users of the carrier, the greater the current estimated downlink transmission rate.

[0183] 5) If the preset parameters of the carrier include service priority, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the service priority, and the higher the service priority, the greater the current estimated downlink transmission rate.

[0184] The path determination module 1002 is used to determine a sending path of a data packet to be sent based on the current estimated downlink transmission rates of the first carrier and the second carrier.

[0185] As an example, the path determination module 1002 may be used to: compare the currently estimated downlink transmission rates of the first carrier and the second carrier, determine the carrier with the highest currently estimated downlink transmission rate between the first carrier and the second carrier; determine the carrier with the highest currently estimated downlink transmission rate as the downlink main path carrying the data to be sent; determine the downlink main path as the sending path of the data packet to be sent. That is, the carrier with the highest currently estimated downlink transmission rate between the first carrier and the second carrier is directly used as the sending path of the data packet to be sent.

[0186] As another example, the estimated time required to send the currently remaining historical data packets to be sent on the first carrier and the second carrier may be determined respectively, and then the sending path of the current data packet to be sent may be determined according to the estimated time corresponding to each of the first carrier and the second carrier and the current estimated downlink transmission rate. That is, the path determination module 1002 may be used to determine the sending path of the current data packet to be sent based on the current estimated downlink transmission rate of the first carrier, the current estimated downlink transmission rate of the second carrier, the estimated time corresponding to the first carrier, and the estimated time corresponding to the second carrier.

[0187] It can be understood that the estimated time required to send the currently remaining historical data packets to be sent on the first carrier and the second carrier (i.e., the currently remaining historical data packets to be sent at the RLC entity) is also used as a reference for determining the sending path of the current data packets to be sent at the PDCP entity. This can make the sending path determined for the current data packets to be sent at the PDCP entity more reasonable and will not cause traffic congestion on the first carrier or the second carrier.

[0188] The determining of the estimated time required to send the currently remaining historical data packets to be sent on the first carrier and the second carrier respectively may include:

[0189] receiving an amount of first data reported by a first RLC entity, wherein the first RLC entity is located in the MN, and the first data includes historical data packets to be sent currently remaining on the first carrier;

[0190] receiving an amount of second data reported by a second RLC entity, wherein the second RLC entity is located at the SN, and the second data includes historical data packets to be sent currently remaining on the second carrier;

[0191] Determine, based on the amount of the first data and the current estimated downlink transmission rate of the first carrier, an estimated time required to send the historical data packets to be sent currently remaining on the first carrier;

[0192] Based on the amount of the second data and the current estimated downlink transmission rate of the second carrier, an estimated time required to send the historical data packets to be sent currently remaining on the second carrier.

[0193] It can be understood that the estimated time required for the remaining historical data packets to be sent on a carrier is generally: the amount of the remaining historical data packets to be sent on the carrier divided by the current estimated downlink transmission rate of the carrier. That is, t(i) = the remaining historical data packets to be sent on the carrier / v(i), where t(i) represents the estimated time, and v(i) represents the current estimated downlink transmission rate.

[0194] Wherein, determining the sending path of the current data packet to be sent based on the current estimated downlink transmission rate of the first carrier, the current estimated downlink transmission rate of the second carrier, the estimated time consumption corresponding to the first carrier, and the estimated time consumption corresponding to the second carrier may include:

[0195] Comparing currently estimated downlink transmission rates of the first carrier and the second carrier, and determining a carrier having a maximum currently estimated downlink transmission rate between the first carrier and the second carrier;

[0196] Determine a carrier with the maximum currently estimated downlink transmission rate as a downlink main path for carrying the currently to-be-sent data;

[0197] Based on the estimated time consumption corresponding to the downlink main path and the estimated time consumption corresponding to the remaining carriers in the first carrier and the second carrier, a sending path for the current data packet to be sent is determined.

[0198] Furthermore, the determining, based on the estimated time consumption corresponding to the downlink main path and the estimated time consumption corresponding to the remaining carriers in the first carrier and the second carrier, a sending path of the current data packet to be sent includes:

[0199] 1) when the estimated time consumption corresponding to the downlink main path meets the first preset condition, determining the downlink main path as the sending path of the current data packet to be sent;

[0200] 2) when the estimated time consumption corresponding to the downlink main path meets the second preset condition, determining the carrier with the smallest estimated time consumption between the first carrier and the second carrier as the sending path of the current data packet to be sent;

[0201] 3) When the estimated time consumption corresponding to the first carrier or the second carrier satisfies a third preset condition, the carrier is not used as a sending path for the data packet to be sent.

[0202] The first preset condition includes: the estimated time is less than the first threshold; the second preset condition includes: the estimated time is greater than or equal to the first threshold and less than the second threshold; the third preset condition includes: the estimated time is greater than the second threshold. The first threshold is the preset minimum buffer delay of the data to be sent in the RLC entity; the second threshold is the preset maximum buffer delay of the data to be sent in the RLC entity.

[0203] The data sending module 1003 is used to send the current data packet to be sent to a target radio link layer control protocol RLC entity, wherein the target RLC entity sends the current data packet to be sent through the sending path.

[0204] The target RLC entity is the first RLC entity or the second RLC entity.

[0205] The data packet currently to be sent at the PDCP entity may be sent to the target RLC entity corresponding to the sending path through the data sending module 1003, so that the target RLC entity sends the data packet currently to be sent through the sending path.

[0206] A data transmission device 1000 provided in an embodiment of the present specification determines, for a first carrier mounted on a main node MN and a second carrier mounted on a secondary node SN, a sending path of a data packet to be sent based on the current estimated downlink transmission rates of the two, that is, the perceived rates of the first carrier and the second carrier - the current estimated downlink transmission rate, are used as a reference basis for downlink splitting of the bearer. In this way, the capacity of each carrier can be fully utilized, the waste of scheduling resources due to unclear air interface capabilities of different carriers or the decrease in user traffic caused by congestion can be reduced, and the data arriving at the PDCP layer can be reasonably distributed to each carrier, thereby improving data transmission efficiency.

[0207] The data transmission device 1000 provided in the embodiment of this specification can also execute Figure 6 The method is implemented by the data transmission device 1000 Figure 6 The functions of the illustrated embodiments will not be described in detail in the embodiments of this specification.

[0208] Fig.11 This is a schematic diagram of a data transmission device 1100 provided by an embodiment of this specification. Fig.11 In a software implementation, the data transmission device 1100 may include: a rate sensing module 1101 and a rate reporting module 1102, wherein:

[0209] The rate sensing module 1101 is used to determine the current estimated downlink transmission rate of the carrier based on the preset parameters of the carrier mounted on the node where the radio link layer control protocol RLC entity is located, wherein the node includes the master node MN or the slave node SN.

[0210] The rate reporting module 1102 is used to report the current estimated downlink transmission rate of the carrier to the Packet Data Convergence Protocol PDCP entity, wherein the current estimated downlink transmission rate of the carrier is used by the PDCP entity to determine the sending path of the current data packet to be sent at the PDCP entity.

[0211] Optionally, the device 1100 may also include: a data volume reporting module, used to report the data volume of the historical data packets currently remaining to be sent on the carrier to the PDCP entity, wherein the data volume is used to determine the estimated time required to send the historical data packets currently remaining to be sent on the carrier, and the estimated time is used by the PDCP entity to determine the sending path of the current data packets to be sent at the PDCP entity.

[0212] The data transmission device 1100 provided in the embodiment of this specification can also execute Figure 7 The method can achieve the same technical effect, and the embodiments of this specification will not be repeated here.

[0213] In short, the above description is only a preferred embodiment of this specification and is not intended to limit the protection scope of this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in the protection scope of this specification.

[0214] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0215] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0216] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0217] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

Claims

1. A data transmission method, the method comprising: Determine a current estimated downlink transmission rate of a first carrier and a second carrier, wherein the first carrier is a carrier mounted on a master node MN, and the second carrier is a carrier mounted on a secondary node SN; Determine a sending path of a data packet to be sent based on current estimated downlink transmission rates of the first carrier and the second carrier; The current data packet to be sent is sent to a target radio link layer control protocol RLC entity, wherein the target RLC entity sends the current data packet to be sent through the sending path.

2. The method according to claim 1, wherein determining the current estimated downlink transmission rate of the first carrier and the second carrier comprises: receiving a current estimated downlink transmission rate for a first carrier estimated and reported by a first RLC entity, wherein the first RLC entity is located in the MN, and the current estimated downlink transmission rate of the first carrier is estimated by the first RLC entity according to a preset parameter of the first carrier; receiving a current estimated downlink transmission rate for a second carrier estimated and reported by a second RLC entity, wherein the second RLC entity is located at the SN, and the current estimated downlink transmission rate of the second carrier is estimated by the second RLC entity according to a preset parameter of the second carrier; The target RLC entity is the first RLC entity or the second RLC entity.

3. The method according to claim 1, wherein determining the current estimated downlink transmission rates of the first carrier and the second carrier comprises: estimating a current estimated downlink transmission rate of the first carrier according to a preset parameter of the first carrier; According to the preset parameters of the second carrier, a current estimated downlink transmission rate of the second carrier is estimated.

4. The method according to claim 2 or 3, The preset parameters include at least one of downlink channel quality, downlink physical resource block PRB load, radio frame structure, number of users and service priority.

5. The method according to claim 1, before determining the sending path of the current data packet to be sent based on the current estimated downlink transmission rates of the first carrier and the second carrier, the method further comprises: The estimated time required to send the historical data packets to be sent currently remaining on the first carrier and the second carrier is determined respectively.

6. The method according to claim 5, wherein the determining the estimated time required to send the currently remaining historical data packets to be sent on the first carrier and the second carrier respectively comprises: receiving an amount of first data reported by a first RLC entity, wherein the first RLC entity is located in the MN, and the first data includes historical data packets to be sent currently remaining on the first carrier; receiving an amount of second data reported by a second RLC entity, wherein the second RLC entity is located at the SN, and the second data includes historical data packets to be sent currently remaining on the second carrier; Determine, based on the amount of the first data and the current estimated downlink transmission rate of the first carrier, an estimated time required to send the historical data packets to be sent currently remaining on the first carrier; Based on the amount of the second data and the current estimated downlink transmission rate of the second carrier, an estimated time required to send the historical data packets to be sent currently remaining on the second carrier.

7. The method according to claim 5, wherein determining a sending path of a current data packet to be sent based on current estimated downlink transmission rates of the first carrier and the second carrier comprises: Based on the current estimated downlink transmission rate of the first carrier, the current estimated downlink transmission rate of the second carrier, the estimated time consumption corresponding to the first carrier, and the estimated time consumption corresponding to the second carrier, a sending path of the current data packet to be sent is determined.

8. The method according to claim 7, wherein determining the sending path of the current data packet to be sent based on the current estimated downlink transmission rate of the first carrier, the current estimated downlink transmission rate of the second carrier, the estimated time consumption corresponding to the first carrier, and the estimated time consumption corresponding to the second carrier comprises: Comparing currently estimated downlink transmission rates of the first carrier and the second carrier, and determining a carrier having a maximum currently estimated downlink transmission rate between the first carrier and the second carrier; Determine a carrier with the maximum currently estimated downlink transmission rate as a downlink main path for carrying the currently to-be-sent data; Based on the estimated time consumption corresponding to the downlink main path and the estimated time consumption corresponding to the remaining carriers in the first carrier and the second carrier, a sending path for the current data packet to be sent is determined.

9. The method according to claim 8, wherein determining the sending path of the current data packet to be sent based on the estimated time consumption corresponding to the downlink main path and the estimated time consumption corresponding to the remaining carriers in the first carrier and the second carrier comprises: When the estimated time consumption corresponding to the downlink main path meets the first preset condition, the downlink main path is determined as the sending path of the current data packet to be sent; When the estimated time consumption corresponding to the downlink main path meets the second preset condition, determining the carrier with the smallest estimated time consumption between the first carrier and the second carrier as the sending path of the current data packet to be sent; When the estimated time consumption corresponding to the first carrier or the second carrier satisfies a third preset condition, the carrier is not used as a sending path for the current data packet to be sent.

10. The method according to claim 9, The first preset condition includes: The estimated time consumption is less than the first threshold; The second preset condition includes: the estimated time consumption is greater than or equal to the first threshold and less than the second threshold; The third preset condition includes: the estimated time consumption is greater than the second threshold.

11. The method according to claim 10, The first threshold is a preset minimum buffer delay of the data to be sent in the RLC entity; The second threshold is a preset maximum buffer delay of the data to be sent in the RLC entity.

12. The method according to any one of claims 1 to 3, 5 to 11, The transmission path is a single carrier or an aggregated carrier.

13. A data transmission method, the method comprising: Determine the current estimated downlink transmission rate of the carrier based on preset parameters of the carrier mounted on the node where the radio link layer control protocol RLC entity is located, wherein the node includes a master node MN or a secondary node SN; The current estimated downlink transmission rate of the carrier is reported to a Packet Data Convergence Protocol (PDCP) entity, wherein the current estimated downlink transmission rate of the carrier is used by the PDCP entity to determine a transmission path of a data packet to be currently sent at the PDCP entity.

14. The method according to claim 13, wherein determining the current estimated downlink transmission rate of the carrier based on preset parameters of the carrier mounted on the node where the RLC entity is located comprises: Based on a predetermined rate estimation model and preset parameters of a carrier mounted on a node where an RLC entity is located, a current estimated downlink transmission rate of the carrier is determined, wherein the rate estimation model is a function of the preset parameters.

15. According to the method of claim 14, the preset parameters include at least one of downlink channel quality, downlink physical resource block (PRB) load, wireless frame structure, number of users and service priority.

16. The method according to claim 15, In the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated or negatively correlated with a preset parameter of the carrier.

17. The method according to claim 16, If the preset parameters of the carrier include downlink channel quality, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the downlink channel quality of the carrier; If the preset parameters of the carrier include a load of a downlink physical resource block (PRB), then in the rate estimation model, the current estimated downlink transmission rate of the carrier is negatively correlated with the load of the downlink PRB of the carrier; If the preset parameters of the carrier include a radio frame structure, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the proportion of downlink subframes in the radio frame structure of the carrier; If the preset parameter of the carrier includes the number of users, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is negatively correlated with the number of users of the carrier; If the preset parameters of the carrier include service priority, then in the rate estimation model, the current estimated downlink transmission rate of the carrier is positively correlated with the service priority.

18. The method according to any one of claims 13 to 17, wherein reporting the current estimated downlink transmission rate of the carrier to the PDCP entity comprises: If the carrier is a single carrier, reporting the current estimated downlink transmission rate of the carrier separately to the PDCP entity; If the carrier is a component carrier in an aggregated carrier, the current estimated downlink transmission rate of the carrier and the current estimated downlink transmission rates of other component carriers are added together and reported to the PDCP entity.

19. The method according to any one of claims 13 to 17, further comprising: Report the amount of data of the historical data packets to be sent currently remaining on the carrier to the PDCP entity, wherein the amount of data is used to determine the estimated time required to send the historical data packets to be sent currently remaining on the carrier, and the estimated time is used by the PDCP entity to determine the sending path of the current data packets to be sent at the PDCP entity.

20. An electronic device, comprising: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method as claimed in any one of claims 1 to 19.

21. A computer-readable storage medium, when instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the method according to any one of claims 1 to 19.

Images