CN109475007B - Data distribution method, user terminal, and computer-readable storage medium - Google Patents
Data distribution method, user terminal, and computer-readable storage medium Download PDFInfo
- Publication number
- CN109475007B CN109475007B CN201710800474.8A CN201710800474A CN109475007B CN 109475007 B CN109475007 B CN 109475007B CN 201710800474 A CN201710800474 A CN 201710800474A CN 109475007 B CN109475007 B CN 109475007B
- Authority
- CN
- China
- Prior art keywords
- rlc entity
- data
- cell group
- data transmission
- pdcp
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1221—Wireless traffic scheduling based on age of data to be sent
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
- H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A data distribution method, a user terminal, and a computer-readable storage medium, the method comprising: when detecting that PDCP data needs to be distributed, acquiring the data transmission capability and the data transmission queue depth n1 of a first RLC entity and the data transmission capability and the data transmission queue depth n2 of a second RLC entity; selecting a corresponding RLC entity according to the relation between the data transmission capacity and the data transmission queue depth n1 of the first RLC entity, the data transmission capacity and the data transmission queue depth n2 of the second RLC entity and preset data distribution conditions; distributing the PDCP data to a transmission queue of the selected RLC entity; applying for authorization to a corresponding base station by adopting an MAC entity corresponding to the selected RLC entity according to the data transmission queue depth of the selected RLC entity; and sending the PDCP data to the corresponding base station by adopting the selected RLC entity according to the received authorization information of the corresponding base station. The scheme can improve the success rate of data transmission and the utilization rate of air interface resources.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a data distribution method, a user terminal and a computer readable storage medium.
Background
In a Long Term Evolution (LTE) Protocol, when uplink bearer separation is configured in a User Equipment (UE), Buffer Status Reports (BSRs) reported by a Master Cell Group (MCG) and a Secondary Cell Group (SCG) are both Data transmittable in a Packet Data Convergence Protocol (PDCP).
When the MAC entity in the UE needs to report the BSR and calculate the Buffer Size (Buffer Size), if an uplink data separation Threshold (ul-Date Split Threshold) is configured, data distribution is performed according to the relationship between the queue depth of the PDCP and the ul-Date Split Threshold.
When the queue depth of the PDCP is greater than or equal to ul-Date Split Threshold, the UE needs to report the queue depth of the PDCP to the primary base station at the MAC entity of the MCG, and report the queue depth of the PDCP to the secondary base station at the MAC entity of the SCG. And the main base station and the auxiliary base station respectively carry out uplink authorization (Grant) according to the BSR. And the UE distributes data according to the authorization information sent by the main base station and the auxiliary base station.
When the queue depth of the PDCP is less than ul-Date Split Threshold, the UE selects an MAC entity using the MCG or an MAC entity using the SCG to report the queue depth according to an ul-Date Split drb-viascag (ul-data Split drb-viascag) configured by a radio link layer (radio link Control, RLC) according to the MAC.
However, when the queue depth of the PDCP is greater than or equal to ul-Date Split Threshold, data distribution is performed according to the authorization information sent by the base station, which easily causes waste of air interface resources. When the queue depth of the PDCP is less than ul-DateSplith Threshold, a unilateral mode is adopted for data transmission, and the success rate of data transmission is low.
Disclosure of Invention
The technical problem solved by the embodiment of the invention is how to improve the success rate of data transmission and the utilization rate of air interface resources.
To solve the foregoing technical problem, an embodiment of the present invention provides a data distribution method, including: when detecting that PDCP data needs to be distributed, acquiring the data transmission capability and the data transmission queue depth n1 of a first RLC entity and the data transmission capability and the data transmission queue depth n2 of a second RLC entity, wherein the service cell group corresponding to the first RLC entity and the service cell group corresponding to the second RLC entity are in a main-auxiliary relationship; selecting a corresponding RLC entity according to the relation between the data transmission capacity and the data transmission queue depth n1 of the first RLC entity, the data transmission capacity and the data transmission queue depth n2 of the second RLC entity and preset data distribution conditions; distributing the PDCP data to a transmission queue of the selected RLC entity; applying for authorization to a corresponding base station by adopting an MAC entity corresponding to the selected RLC entity according to the data transmission queue depth of the selected RLC entity; and sending the PDCP data to the corresponding base station by adopting the selected RLC entity according to the received authorization information of the corresponding base station.
Optionally, the data transmission capability of the first RLC entity is characterized by using the number m1 of correctly transmitted bytes of the first RLC entity; and characterizing the data transmission capability of the second RLC entity by adopting the correct transmission byte number m2 of the second RLC entity.
Optionally, the selecting a corresponding RLC entity according to a relationship between the data transmission capability and the data transmission queue depth n1 of the first RLC entity, the data transmission capability and the data transmission queue depth n2 of the second RLC entity, and a preset data distribution condition includes any one of: selecting a first RLC entity when m1/m2 > n1/n 2; selecting a second RLC entity when m1/m2 < n1/n 2; and when m1/m2 is n1/n2, selecting the corresponding RLC entity according to the uplink data separation bearer threshold of the secondary cell group configured by RRC.
Optionally, the preset value of m1 is 1, the preset value of m2 is 1, the preset value of n1 is 0, and the preset value of n2 is 0.
Optionally, when PDCP data is first distributed, the corresponding RLC entity is selected according to the uplink data separation bearer threshold of the secondary cell group configured by the RRC.
Optionally, after the selected RLC entity is adopted to transmit the PDCP data to the corresponding base station, the method further includes: receiving a status packet returned by a base station, wherein the status packet is suitable for identifying whether the selected RLC entity successfully sends the PDCP data or not; and when the received status packet identifies that the selected RLC entity successfully sends the PDCP data, accumulating the number of bytes of the correctly sent data of the selected RLC entity with the number of bytes corresponding to the PDCP data.
Optionally, the serving cell group corresponding to the first RLC entity and the serving cell group corresponding to the second RLC entity are in a primary-secondary relationship, including: the service cell group corresponding to the first RLC entity is a master cell group, and the service cell group corresponding to the second RLC entity is a secondary cell group; or, the serving cell group corresponding to the first RLC entity is a secondary cell group, and the serving cell group corresponding to the second RLC entity is a master cell group.
An embodiment of the present invention further provides a user terminal, including: the device comprises an acquisition unit, a selection unit, a distribution unit, an authorization application unit, a first receiving unit and a sending unit, wherein: the acquiring unit is suitable for acquiring the data sending capability and the data sending queue depth n1 of a first RLC entity and the data sending capability and the data sending queue depth n2 of a second RLC entity when PDCP data are detected to be distributed, wherein the service cell group corresponding to the first RLC entity and the service cell group corresponding to the second RLC entity are in a main-auxiliary relationship; the selection unit is suitable for selecting the corresponding RLC entity according to the relation between the data transmission capability and the data transmission queue depth n1 of the first RLC entity and the data transmission capability and the data transmission queue depth n2 of the second RLC entity and preset data distribution conditions; the distribution unit is suitable for distributing the PDCP data to a transmission queue of the selected RLC entity; the authorization application unit is suitable for applying authorization to a corresponding base station by adopting the MAC entity corresponding to the selected RLC entity according to the data transmission queue depth of the selected RLC entity; the first receiving unit is suitable for receiving the authorization information sent by the corresponding base station; and the sending unit is suitable for sending the PDCP data to the corresponding base station by adopting the selected RLC entity according to the received authorization information of the corresponding base station.
Optionally, the first RLC entity correctly sends byte number m1 to characterize the data sending capability of the first RLC entity; the number m2 of correctly sent bytes of the second RLC entity represents the data sending capability of the second RLC entity.
Optionally, the selecting unit is adapted to select the first RLC entity when m1/m2 > n1/n 2; adapted to select the second RLC entity when m1/m2 < n1/n 2; and when m1/m2 is n1/n2, selecting the corresponding RLC entity according to the RRC configured uplink data separation bearer threshold of the secondary cell group.
Optionally, the preset value of m1 is 1, the preset value of m2 is 1, the preset value of n1 is 0, and the preset value of n2 is 0.
Optionally, the selecting unit is adapted to select the corresponding RLC entity according to an uplink data separation bearer threshold of the secondary cell group configured by the RRC when the PDCP data is first distributed.
Optionally, the user terminal further includes: a second receiving unit and an updating unit, wherein: the second receiving unit is adapted to receive a status packet returned by the base station after the selected RLC entity is adopted to send the PDCP data to the corresponding base station, where the status packet is adapted to identify whether the selected RLC entity successfully sends the PDCP data; and the updating unit is suitable for accumulating the number of bytes of correctly transmitted data of the selected RLC entity by the number of bytes corresponding to the PDCP data when the received status packet identifies that the selected RLC entity successfully transmits the PDCP data.
Optionally, the serving cell group corresponding to the first RLC entity and the serving cell group corresponding to the second RLC entity are in a primary-secondary relationship, including: the service cell group corresponding to the first RLC entity is a master cell group, and the service cell group corresponding to the second RLC entity is a secondary cell group; or, the serving cell group corresponding to the first RLC entity is a secondary cell group, and the serving cell group corresponding to the second RLC entity is a master cell group.
The embodiment of the present invention further provides a computer-readable storage medium, on which computer instructions are stored, and when the computer instructions are executed, the method performs any of the steps of the data distribution method.
The embodiment of the present invention further provides a user terminal, which includes a memory and a processor, where the memory stores a computer instruction capable of running on the processor, and the processor executes any of the steps of the data distribution method when running the computer instruction.
Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:
when detecting that PDCP data needs to be distributed, selecting and distributing the PDCP data to a transmission queue of a corresponding RLC entity according to the relation between the data transmission capacity and the data transmission queue depth n1 of a first RLC entity, the data transmission capacity and the data transmission queue depth n2 of a second RLC entity and a preset data distribution condition, and applying for authorization to a base station by the MAC entity corresponding to the determined RLC entity according to the data transmission queue depth of the RLC entity. When the PDCP data is distributed, the data sending capability and the data sending queue depth corresponding to each RLC entity are considered, and each RLC entity applies for authorization to the base station according to the data sending queue depth of the RLC entity, so that the data sending success rate and the air interface resource utilization rate can be improved.
Drawings
FIG. 1 is a flow chart of a method of data distribution in an embodiment of the invention;
FIG. 2 is a process diagram of data distribution according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a user terminal according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of another ue in the embodiment of the present invention.
Detailed Description
As can be seen from the above, when the queue depth of the PDCP is greater than or equal to ul-Date Split Threshold, the MAC entity of the MCG and the MAC entity of the SCG need to report the same queue depth, and the base stations on both sides will distribute authorization according to the reported BSR, and only one copy of data is available, which is easy to cause waste of air interface resources. When the queue depth of the PDCP is less than ul-Date Split Threshold, the UE selects the RLC entity of the MCG or the RLC entity of the SCG for transmission according to the ul-Date Split drb-viasccg parameter configured by the RLC, that is, single-side transmission, and if uplink transmission of the selected RLC entity has a problem, such as a cell edge of a mobile phone, the probability of data transmission failure may be increased.
In the embodiment of the invention, when detecting that PDCP data needs to be distributed, the PDCP data is selected and distributed to the transmission queue of the corresponding RLC entity according to the relation between the data transmission capacity and the data transmission queue depth n1 of the first RLC entity, the data transmission capacity and the data transmission queue depth n2 of the second RLC entity and the preset data distribution condition, and the determined MAC entity corresponding to the RLC entity applies for authorization to the base station according to the data transmission queue depth of the RLC entity. When the PDCP data is distributed, the data sending capability and the data sending queue depth corresponding to each RLC entity are considered, and each RLC entity applies for authorization to the base station according to the data sending queue depth of the RLC entity, so that the data sending success rate and the air interface resource utilization rate can be improved.
In order to make the aforementioned objects, features and advantages of the embodiments of the present invention more comprehensible, specific embodiments accompanied with figures are described in detail below.
Referring to fig. 1, a flowchart of a data distribution method according to an embodiment of the present invention is shown, and details are described below with reference to specific steps.
And step 11, when detecting that there is PDCP data to be distributed, acquiring the data transmission capability and the data transmission queue depth n1 of the first RLC entity and the data transmission capability and the data transmission queue depth n2 of the second RLC entity.
In a specific implementation, after the UE establishes uplink data bearer separation, when it is detected that there is PDCP data to be distributed, that is, when there is new data in the PDCP layer, the data transmission capability of the first RLC entity, the data transmission queue depth n1 of the first RLC entity, the data transmission capability of the second RLC entity, and the data transmission queue depth n2 of the second RLC entity may be obtained through a data distribution counter.
In a specific implementation, the serving cell group corresponding to the first RLC entity and the serving cell group corresponding to the second RLC entity are in a primary-secondary relationship. And when the service cell group corresponding to the first RLC entity is MCG, the service cell group corresponding to the second RLC entity is SCG. And when the service cell group corresponding to the first RLC entity is SCG, the service cell group corresponding to the second RLC entity is MCG.
And step 12, selecting the corresponding RLC entity according to the relationship between the data transmission capability and the data transmission queue depth n1 of the first RLC entity, the data transmission capability and the data transmission queue depth n2 of the second RLC entity and the preset data distribution condition.
In a specific implementation, the data transmission capability of the first RLC entity may be characterized by the correct number m1 of transmission bytes of the first RLC entity, and the data transmission capability of the second RLC entity may be characterized by the correct number m1 of transmission bytes of the second RLC entity.
In an embodiment of the present invention, a corresponding RLC entity may be selected according to the data transmission capability m1 of the first RLC entity, the data transmission queue depth n1 of the first RLC entity, the data transmission capability m2 of the second RLC entity, and the data transmission queue depth n2 of the second RLC entity, which is specifically as follows:
when m1/m2 > n1/n2, the first RLC entity may be selected.
The second RLC entity may be selected when m1/m2 < n1/n 2.
When m1/m2 is n1/n2, the corresponding RLC entity may be selected according to the RRC configured uplink data separation bearer threshold of the secondary cell group. Specifically, when the RRC sets the uplink data separation bearer threshold of the secondary cell group to be true, the RLC layer corresponding to the secondary cell group is selected, and when the RRC sets the uplink data separation bearer threshold of the secondary cell group to be other, the RLC layer corresponding to the primary cell group is selected.
In a specific implementation, after the UE establishes uplink data bearer separation, each RLC entity in the UE may set its uplink data sending capability. For example, the preset value of the data transmission capability m1 of the first RLC entity may be 1, the preset value of the data transmission capability m2 of the second RLC entity may be 1, the preset value initially set by the data transmission queue n1 of the first RLC entity is 0, and the preset value initially set by the data transmission queue n2 of the second RLC entity is 0.
It should be understood that, in the implementation, when the values of m1, m2, n1 and n2 are initially set, other values may be set, and only m1 — m2 and n1 — n2 need to be satisfied.
In specific implementation, when PDCP data is first distributed, a corresponding RLC entity may be selected according to an uplink data separation bearer threshold of a secondary cell group configured by an RRC.
And step 13, distributing the PDCP data to a transmission queue of the selected RLC entity.
In a specific implementation, after the corresponding RLC entity is selected, the PDCP data may be distributed to a transmission queue of the selected RLC entity.
For example, the selected RLC entity is a first RLC entity, and the PDCP data is distributed to a transmission queue of the first RLC entity.
In another example, the selected RLC entity is a second RLC entity, and the PDCP data is distributed to a transmission queue of the second RLC entity.
And step 14, applying for authorization to a corresponding base station by using the MAC entity corresponding to the selected RLC entity according to the data transmission queue depth of the selected RLC entity.
In a specific implementation, after the PDCP data is distributed to the selected RLC transmission queue, the MAC entity corresponding to the selected RLC entity may apply for authorization to the corresponding base station according to the data transmission queue depth of the selected RLC entity.
For example, the selected first RLC entity is an RLC entity of the MCG, and the MAC entity of the MCG applies for authorization to a master base station (MeNB) according to a data transmission queue depth of the RLC entity of the MCG. The MeNB may feed back the authorization information to the UE according to the data transmission queue depth of the RLC entity of the MCG reported by the MAC entity of the MCG.
And step 15, sending the PDCP data to the corresponding base station by adopting the selected RLC entity according to the received authorization information of the corresponding base station.
In a specific implementation, after receiving the authorization information sent by the corresponding base station, the UE may send the PDCP data to the corresponding base station by using the selected RLC entity.
By adopting the scheme, when the PDCP data are detected to be distributed, the PDCP data are selected and distributed to the transmission queue of the corresponding RLC entity according to the relation between the data transmission capacity and the data transmission queue depth n1 of the first RLC entity, the data transmission capacity and the data transmission queue depth n2 of the second RLC entity and the preset data distribution condition, and the determined MAC entity corresponding to the RLC entity applies for authorization to the base station according to the data transmission queue depth of the RLC entity. When the PDCP data is distributed, the data sending capability and the data sending queue depth corresponding to each RLC entity are considered, and each RLC entity applies for authorization to the base station according to the data sending queue depth of the RLC entity, so that the data sending success rate and the air interface resource utilization rate can be improved.
In addition, the data rate in the 5G system is hundreds of times of the data rate of a Long Term Evolution (LTE) system, and if the allocation and transmission of data and the like still continue to use the LTE system, after the MAC entity receives the authorization of the corresponding base station, data distribution is triggered, the requirement on the processing capability of the UE is high.
In a specific implementation, after the selected RLC entity is adopted to send the PDCP data to the corresponding base station, a status packet returned by the base station may be further received. The status packet is suitable for identifying whether the selected RLC entity successfully sends the PDCP data, and when the received status packet identifies that the selected RLC entity successfully sends the PDCP data, the number of bytes of correctly sent data of the selected RLC entity is accumulated by the number of bytes corresponding to the PDCP data.
For example, the number of correctly transmitted bytes of the selected RLC entity is p, the received status packet identifier correctly transmits the PDCP data, the number of correctly transmitted bytes of the PDCP data is q, and the number of correctly transmitted bytes of the selected RLC entity is updated, that is, the number of correctly transmitted bytes of the PDCP data q is accumulated on the basis of the number of correctly transmitted bytes p of the selected RLC entity.
According to the received status packet, the correct sending byte number of each RLC entity can be dynamically adjusted to correct the data sending capability of each RLC entity in real time, so that when PDCP data distribution is carried out, the corresponding RLC entity can be selected according to the latest data sending capability and sending queue depth of each RLC entity, PDCP data distribution is carried out, and the correct rate of data sending and the utilization rate of air interface resources are further improved.
Referring to fig. 2, a schematic diagram of a data distribution process in an embodiment of the present invention is given, and a data distribution process is described below with reference to a specific embodiment.
In an embodiment of the present invention, the first RLC entity is an MCG RLC entity, and the second RLC entity is an SCG RLC entity. The MCG RLC layer 22 and the SCG RLE layer 23 both belong to the RLC layer of the UE and are located between the PDCP layer 21 and the MAC layer (not shown).
In step 201, when the PDCP data processing module in the PDCP layer 21 receives new PDCP data.
When m1/m2 > n1/n2, step 203 is performed to distribute PDCP data to a transmission queue of the MCG RLC entity. When m1/m2 < n1/n2, step 207 is performed to distribute the PDCP data to the transmission queue of the SCG RLC entity. When m1/m2 is n1/n2, step 203 or step 207 is determined to be performed according to the ul-DateSplitDRB-ViaSCG configured by RRC. Specifically, when the RRC sets the uplink data separation bearer threshold of the secondary cell group to true, step 207 is executed; and when the RRC sets the secondary cell group uplink data separation bearer threshold as other, executing step 203.
In step 204, the MCG RLC entity transmits data.
In specific implementation, after the PDCP data is distributed to a sending queue of the MCG RLC entity, the MCG MAC entity applies for authorization to the MeNB and receives authorization information returned by the MeNB. And when receiving the authorization information, the MCG RLC entity sends the data in the queue to the MeNB.
In step 205, the received RLC status packet is parsed.
And step 206, updating the MCG RLC entity to correctly send the byte number according to the analysis result of the RLC status packet.
In step 208, the SCG RLC entity transmits data.
In specific implementation, after the PDCP data is distributed to a sending queue of the SCG RLC entity, the SCG MAC entity applies for authorization to a secondary base station (SeNB), and receives authorization information returned by the SeNB. And after receiving the authorization information, the SCG RLC entity sends the data in the queue to the SeNB.
In the specific implementation, step 201 and step 202 may be completed in the PDCP layer 21, step 203 to step 206 may be completed in the MCG RLC layer 22, and step 207 to step 210 may be completed in the SCG RLC layer 23. There may be no sequence between step 203 to step 206 and step 207 to step 210, and the steps are executed according to actual needs in the data distribution process.
In order to facilitate better understanding and implementation of the embodiments of the present invention for those skilled in the art, the embodiments of the present invention also provide a user terminal.
Referring to fig. 3, a schematic structural diagram of a user terminal in the embodiment of the present invention is shown. The user terminal 30 may include: an obtaining unit 31, a selecting unit 32, a distributing unit 33, an authorization applying unit 34, a first receiving unit 35 and a sending unit 36, wherein:
the obtaining unit 31 is adapted to obtain, when it is detected that there is PDCP data that needs to be distributed, a data sending capability and a data sending queue depth n1 of a first RLC entity, and a data sending capability and a data sending queue depth n2 of a second RLC entity, where a serving cell group corresponding to the first RLC entity and a serving cell group corresponding to the second RLC entity are in a primary-secondary relationship;
the selecting unit 32 is adapted to select a corresponding RLC entity according to a relationship between the data transmission capability and the data transmission queue depth n1 of the first RLC entity, and the data transmission capability and the data transmission queue depth n2 of the second RLC entity, and a preset data distribution condition;
the distribution unit 33 is adapted to distribute the PDCP data to a transmission queue of the selected RLC entity;
the authorization applying unit 34 is adapted to apply authorization to a corresponding base station according to the data transmission queue depth of the selected RLC entity by using the MAC entity corresponding to the selected RLC entity;
the first receiving unit 35 is adapted to receive authorization information sent by a corresponding base station;
the sending unit 36 is adapted to send the PDCP data to the corresponding base station by using the selected RLC entity according to the received authorization information of the corresponding base station.
According to the scheme, when PDCP data are detected to be distributed, the PDCP data are selected and distributed to the transmission queue of the corresponding RLC entity according to the relation between the data transmission capacity and the data transmission queue depth n1 of the first RLC entity, the data transmission capacity and the data transmission queue depth n2 of the second RLC entity and the preset data distribution condition, and the determined MAC entity corresponding to the RLC entity applies for authorization to the base station according to the data transmission queue depth of the RLC entity. When the PDCP data is distributed, the data sending capability and the data sending queue depth corresponding to each RLC entity are considered, and each RLC entity applies for authorization to the base station according to the data sending queue depth of the RLC entity, so that the data sending success rate and the air interface resource utilization rate can be improved.
In a specific implementation, the number m1 of correctly sent bytes of the first RLC entity may characterize the data sending capability of the first RLC entity; the number m2 of correctly transmitted bytes of the second RLC entity can characterize the data transmission capability of the second RLC entity.
In a specific implementation, the selecting unit 32 is adapted to select the first RLC entity when m1/m2 > n1/n 2; adapted to select the second RLC entity when m1/m2 < n1/n 2; and when m1/m2 is n1/n2, selecting the corresponding RLC entity according to the RRC configured uplink data separation bearer threshold of the secondary cell group.
In a specific implementation, the preset value of m1 is 1, the preset value of m2 is 1, the preset value of n1 is 0, and the preset value of n2 is 0.
In a specific implementation, the selecting unit 32 is adapted to select a corresponding RLC entity according to an uplink data separation bearer threshold of a secondary cell group configured by an RRC when PDCP data is first distributed.
In a specific implementation, the user terminal 30 may further include: a second receiving unit and an updating unit (not shown in fig. 3), wherein:
the second receiving unit is adapted to receive a status packet returned by the base station after the selected RLC entity is adopted to send the PDCP data to the corresponding base station, where the status packet is adapted to identify whether the selected RLC entity successfully sends the PDCP data;
and the updating unit is suitable for accumulating the number of bytes of correctly transmitted data of the selected RLC entity by the number of bytes corresponding to the PDCP data when the received status packet identifies that the selected RLC entity successfully transmits the PDCP data.
In a specific implementation, the serving cell group corresponding to the first RLC entity and the serving cell group corresponding to the second RLC entity are in a primary-secondary relationship. The service cell group corresponding to the first RLC entity is a master cell group, and the service cell group corresponding to the second RLC entity is a secondary cell group; or, the serving cell group corresponding to the first RLC entity is a secondary cell group, and the serving cell group corresponding to the second RLC entity is a master cell group.
Referring to fig. 4, a schematic structural diagram of another ue in the embodiment of the present invention is shown. The user terminal 30 may be provided with a PDCP layer 41, an MCG RLC layer 42, an SCG RLC layer 43, an MCG MAC layer 44, and an SCG MAC layer 45. The user terminal 30 may include: the device comprises an acquisition unit 31, a selection unit 32, a distribution unit 33, an authorization application unit 34, a first receiving unit 35 and a sending unit 36. The PDCP layer 41 may be provided with the acquiring unit 31, the selecting unit 32, and the distributing unit 33. The MCG MAC layer 44 and the SCG MAC layer 45 may be provided with the authorization application unit 34 and the first receiving unit 35. The MCG RLC layer 42 and the SCG MAC layer may be provided with a transmitting unit 36.
In a specific implementation, the working principle and the working flow of the user terminal 30 may refer to the description in the data distribution method provided in the foregoing embodiment, and are not described herein again.
The embodiment of the present invention further provides a computer-readable storage medium, on which computer instructions are stored, and when the computer instructions are executed, the steps of the data distribution method provided in any of the above embodiments are executed.
The embodiment of the present invention further provides a user terminal, which includes a memory and a processor, where the memory stores a computer instruction capable of running on the processor, and the processor executes the steps of the data distribution method provided in any of the above embodiments when running the computer instruction.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: ROM, RAM, magnetic or optical disks, and the like.
Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (12)
1. A method for data distribution, comprising:
when detecting that PDCP data needs to be distributed, acquiring the data transmission capability and the data transmission queue depth n1 of a first RLC entity and the data transmission capability and the data transmission queue depth n2 of a second RLC entity, wherein the service cell group corresponding to the first RLC entity and the service cell group corresponding to the second RLC entity are in a main-auxiliary relationship;
selecting a corresponding RLC entity according to the relationship between the data transmission capability and the data transmission queue depth n1 of the first RLC entity, the data transmission capability and the data transmission queue depth n2 of the second RLC entity and preset data distribution conditions, wherein the method comprises the following steps: the data sending capability of the first RLC entity is represented by the correct sending byte number m1 of the first RLC entity; the data transmission capability of the second RLC entity is characterized by adopting the correct transmission byte number m2 of the second RLC entity, and when m1/m2 is greater than n1/n2, the first RLC entity is selected; selecting a second RLC entity when m1/m2 < n1/n 2; when m1/m2 is n1/n2, selecting a corresponding RLC entity according to an auxiliary cell group uplink data separation bearing threshold configured by RRC, when the RRC sets the auxiliary cell group uplink data separation bearing threshold to be true, selecting an RLC layer corresponding to the auxiliary cell group, and when the RRC sets the auxiliary cell group uplink data separation bearing threshold to be other, selecting an RLC corresponding to a main cell group;
distributing the PDCP data to a transmission queue of the selected RLC entity;
applying for authorization to a corresponding base station by adopting an MAC entity corresponding to the selected RLC entity according to the data transmission queue depth of the selected RLC entity;
and sending the PDCP data to the corresponding base station by adopting the selected RLC entity according to the received authorization information of the corresponding base station.
2. The data distribution method of claim 1, wherein the preset value of m1 is 1, the preset value of m2 is 1, the preset value of n1 is 0, and the preset value of n2 is 0.
3. The data distribution method of claim 2, wherein when PDCP data distribution is performed for the first time, the corresponding RLC entity is selected according to the RRC configured uplink data separation bearer threshold of the secondary cell group.
4. The data distribution method according to claim 1, wherein after the selected RLC entity is adopted to transmit the PDCP data to the corresponding base station, the method further comprises:
receiving a status packet returned by a base station, wherein the status packet is suitable for identifying whether the selected RLC entity successfully sends the PDCP data or not;
and when the received status packet identifies that the selected RLC entity successfully sends the PDCP data, accumulating the number of bytes of the correctly sent data of the selected RLC entity with the number of bytes corresponding to the PDCP data.
5. The data distribution method of claim 1, wherein the serving cell group corresponding to the first RLC entity and the serving cell group corresponding to the second RLC entity are in a primary-secondary relationship, comprising:
the service cell group corresponding to the first RLC entity is a master cell group, and the service cell group corresponding to the second RLC entity is a secondary cell group; alternatively, the first and second electrodes may be,
the service cell group corresponding to the first RLC entity is a secondary cell group, and the service cell group corresponding to the second RLC entity is a master cell group.
6. A user terminal, comprising: the device comprises an acquisition unit, a selection unit, a distribution unit, an authorization application unit, a first receiving unit and a sending unit, wherein:
the acquiring unit is suitable for acquiring the data sending capability and the data sending queue depth n1 of a first RLC entity and the data sending capability and the data sending queue depth n2 of a second RLC entity when PDCP data are detected to be distributed, wherein the service cell group corresponding to the first RLC entity and the service cell group corresponding to the second RLC entity are in a main-auxiliary relationship;
the selection unit is suitable for selecting a corresponding RLC entity according to the relation between the data transmission capacity and the data transmission queue depth n1 of a first RLC entity, the data transmission capacity and the data transmission queue depth n2 of a second RLC entity and preset data distribution conditions, and the data transmission capacity of the first RLC entity is represented by adopting the number m1 of correct transmission bytes of the first RLC entity; the data transmission capability of the second RLC entity is characterized by adopting the correct transmission byte number m2 of the second RLC entity, and when m1/m2 is greater than n1/n2, the first RLC entity is selected; selecting a second RLC entity when m1/m2 < n1/n 2; when m1/m2 is n1/n2, selecting a corresponding RLC entity according to an auxiliary cell group uplink data separation bearing threshold configured by RRC, when the RRC sets the auxiliary cell group uplink data separation bearing threshold to be true, selecting an RLC layer corresponding to the auxiliary cell group, and when the RRC sets the auxiliary cell group uplink data separation bearing threshold to be other, selecting an RLC corresponding to a main cell group;
the distribution unit is suitable for distributing the PDCP data to a transmission queue of the selected RLC entity;
the authorization application unit is suitable for applying authorization to a corresponding base station by adopting the MAC entity corresponding to the selected RLC entity according to the data transmission queue depth of the selected RLC entity;
the first receiving unit is suitable for receiving the authorization information sent by the corresponding base station;
and the sending unit is suitable for sending the PDCP data to the corresponding base station by adopting the selected RLC entity according to the received authorization information of the corresponding base station.
7. The UE of claim 6, wherein the preset value of m1 is 1, the preset value of m2 is 1, the preset value of n1 is 0, and the preset value of n2 is 0.
8. The user terminal according to claim 7, wherein the selecting unit is adapted to select the corresponding RLC entity according to an uplink data separation bearer threshold of the secondary cell group configured by the RRC when the PDCP data is first distributed.
9. The user terminal according to claim 6, further comprising: a second receiving unit and an updating unit, wherein:
the second receiving unit is adapted to receive a status packet returned by the base station after the selected RLC entity is adopted to send the PDCP data to the corresponding base station, where the status packet is adapted to identify whether the selected RLC entity successfully sends the PDCP data;
and the updating unit is suitable for accumulating the number of bytes of correctly transmitted data of the selected RLC entity by the number of bytes corresponding to the PDCP data when the received status packet identifies that the selected RLC entity successfully transmits the PDCP data.
10. The ue of claim 6, wherein the serving cell group corresponding to the first RLC entity and the serving cell group corresponding to the second RLC entity are in a primary-secondary relationship, comprising:
the service cell group corresponding to the first RLC entity is a master cell group, and the service cell group corresponding to the second RLC entity is a secondary cell group; alternatively, the first and second electrodes may be,
the service cell group corresponding to the first RLC entity is a secondary cell group, and the service cell group corresponding to the second RLC entity is a master cell group.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the data distribution method according to any one of claims 1 to 5.
12. A user terminal comprising a memory and a processor, the memory having stored thereon a computer program operable on the processor, characterized in that the processor, when executing the computer program, performs the steps of the data distribution method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710800474.8A CN109475007B (en) | 2017-09-07 | 2017-09-07 | Data distribution method, user terminal, and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710800474.8A CN109475007B (en) | 2017-09-07 | 2017-09-07 | Data distribution method, user terminal, and computer-readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109475007A CN109475007A (en) | 2019-03-15 |
| CN109475007B true CN109475007B (en) | 2020-08-14 |
Family
ID=65657571
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710800474.8A Active CN109475007B (en) | 2017-09-07 | 2017-09-07 | Data distribution method, user terminal, and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109475007B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113507726B (en) * | 2021-07-14 | 2024-05-14 | Oppo广东移动通信有限公司 | Data transmission method and device in separated bearing mode and terminal equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102857871A (en) * | 2011-06-30 | 2013-01-02 | 中兴通讯股份有限公司 | cluster data transmission method and network-side equipment |
| CN103858455A (en) * | 2011-10-07 | 2014-06-11 | 华为技术有限公司 | System and method for multiple point transmission in a communications system |
-
2017
- 2017-09-07 CN CN201710800474.8A patent/CN109475007B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102857871A (en) * | 2011-06-30 | 2013-01-02 | 中兴通讯股份有限公司 | cluster data transmission method and network-side equipment |
| CN103858455A (en) * | 2011-10-07 | 2014-06-11 | 华为技术有限公司 | System and method for multiple point transmission in a communications system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109475007A (en) | 2019-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108112087B (en) | V2X network resource information indication method and base station | |
| US10701725B2 (en) | Scheduling resource configuration method and apparatus, user equipment, and base station | |
| US10575320B2 (en) | Data transmission method and device | |
| CN106488544B (en) | Uplink power control method, network node and system | |
| CN107155218B (en) | Method and equipment for configuring uplink semi-persistent scheduling | |
| US20190335448A1 (en) | Data transmission method and apparatus | |
| US20200228253A1 (en) | Data transmission method and apparatus | |
| EP3198919B1 (en) | Methods and apparatus for minimization of drive testing | |
| US10897767B2 (en) | Resource scheduling method, apparatus, and system | |
| US10798563B2 (en) | User terminal, radio base station and radio communication method | |
| CN108847919B (en) | Data transmission method, base station and wireless communication equipment | |
| US20180192427A1 (en) | Dynamic delay scheduling method and base station for voice data | |
| CN102833734A (en) | Method for transmitting paging message | |
| CN108322939B (en) | Method and apparatus for wireless communication system supporting multiple physical layer methods | |
| US20210227507A1 (en) | Communications method and apparatus | |
| CN107743313B (en) | Method, base station and system for realizing time division duplex configuration of auxiliary cell | |
| CN112740813A (en) | Communication method and device | |
| CN109475007B (en) | Data distribution method, user terminal, and computer-readable storage medium | |
| JP2017038335A (en) | User device and communication method | |
| EP3099091A1 (en) | Uplink resource allocation method, access terminal, and access point | |
| EP3188379B1 (en) | Random access method, network device and user equipment | |
| CN107820216B (en) | Scheduling method and device based on SC-MTCH | |
| CN107566093B (en) | RLC ARQ method of cross-base-station carrier aggregation system and base station | |
| CN112153692B (en) | Cache reporting method and device for radio bearer | |
| EP3606212A1 (en) | Terminal mode acquisition method, apparatus and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |