CN112953849A - Data volume processing method, device and medium - Google Patents

Data volume processing method, device and medium Download PDF

Info

Publication number
CN112953849A
CN112953849A CN201911260559.7A CN201911260559A CN112953849A CN 112953849 A CN112953849 A CN 112953849A CN 201911260559 A CN201911260559 A CN 201911260559A CN 112953849 A CN112953849 A CN 112953849A
Authority
CN
China
Prior art keywords
data
rlc
application
sending
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.)
Granted
Application number
CN201911260559.7A
Other languages
Chinese (zh)
Other versions
CN112953849B (en
Inventor
孙军帅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN201911260559.7A priority Critical patent/CN112953849B/en
Publication of CN112953849A publication Critical patent/CN112953849A/en
Application granted granted Critical
Publication of CN112953849B publication Critical patent/CN112953849B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/26Flow control; Congestion control using explicit feedback to the source, e.g. choke packets
    • H04L47/263Rate modification at the source after receiving feedback

Landscapes

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

Abstract

The invention discloses a data volume processing method, equipment and a medium, comprising the following steps: a packet data convergence protocol receives a data volume application sent by wireless link control; and sending data according to the data volume application. The wireless link control determines the required data volume and applies for the data volume to the packet data convergence protocol; and the radio link control receives data sent by the packet data convergence protocol according to the application. By adopting the invention, the grouped data convergence protocol has the function of controlling the data volume, thereby realizing the requirement of simultaneously mapping one grouped data convergence protocol entity to a plurality of low-level link entities; the control of the data volume of the packet data convergence protocol can be realized according to the actual transmission of a wireless link control layer; the compatibility is good, and the 3G/4G/5G network can be compatible.

Description

Data volume processing method, device and medium
Technical Field
The present invention relates to the field of wireless communications technologies, and in particular, to a data amount processing method, device, and medium.
Background
In order to increase the robustness of Data transmission, multiplexing is implemented by DC/MC (DC: Dual Connectivity; MC: Multiple Connectivity) of PDCP (Packet Data Convergence Protocol) plus MAC CA (MAC: medium Access Control; CA: Carrier Aggregation), which is a standard choice, and this means that one PDCP entity needs to be mapped to Multiple lower link entities at the same time, that is, an RB (Radio Bearer) of one PDCP layer may be mapped to Multiple lower logical channels at the same time.
Disclosure of Invention
The invention provides a data volume processing method, equipment and a medium, which are used for solving the problem that the traditional PDCP does not have the data volume control function.
The embodiment of the invention provides a data volume processing method, which is applied to a Packet Data Convergence Protocol (PDCP) and comprises the following steps:
receiving an application, wherein the application is a data volume application sent by Radio Link Control (RLC);
and sending data according to the data volume application.
In implementation, the data volume request is sent by the RLC via a data request packet of the control packet type CPT.
In the implementation, the sending data according to the data volume application comprises:
after receiving a data request packet of a control packet type CPT on an RB, the PDCP distributes data to the RB and sends the data on the RB; or the like, or, alternatively,
after receiving the data request packet of the control packet type CPT, the PDCP allocates data to each user in each RB according to the content requested in the data request packet of the control packet type CPT, and transmits the data to each user in each RB.
In the implementation, when the data request packet of the control packet type CPT includes a time requirement for transmitting data, the method may further include:
when data is distributed, the PDCP changes the distributed data according to the data quantity caused by time delay brought by the time requirement of sending the data, and sends the data according to the time requirement of sending the data.
The embodiment of the invention provides a data volume processing method which is applied to RLC and comprises the following steps:
determining the required data volume and applying for the data volume from the PDCP;
receiving data, wherein the data is sent by the PDCP according to the application.
In implementation, the application is applied by a data request packet of a control packet type CPT.
In practice, the application comprises:
after the RLC determines the required data volume on the RB, a data request packet of a control packet type CPT is applied to the PDCP on the RB; or the like, or, alternatively,
after determining the data volume required by each user on each RB, the RLC applies for sending a data request packet of a control packet type CPT to the PDCP.
In the implementation, the method further comprises the following steps:
the RLC includes a time requirement for transmitting data in a data request packet of the control packet type CPT.
In implementation, the RLC determines the required amount of data including: the required data amount is determined according to the receiving and transmitting conditions of ARQ and/or HARQ data.
In implementation, the RLC determines the required data amount according to the transceiving condition of ARQ and/or HARQ data, and calculates the required data amount according to the data transmitted by ARQ and/or HARQ according to one or a combination of the following parameters:
the feedback time delay from sending data packet to receiving ACK/NACK, the total data amount, the number of data packets, the error ratio, BLER, the ratio of ACK and NACK, the number of data packets which reach the maximum sending times and still are not sent successfully, the data amount or the ratio of the data packets which occupy the total sending data packets, the ratio of one-time successful sending and the ratio of multiple successful sending.
In practice, when calculating according to one or a combination of the following parameters, the following formula is used for calculation:
Figure BDA0002311495500000031
Figure BDA0002311495500000032
wherein ,
Figure BDA0002311495500000033
the average sending rate of effective data RLC SDU on ARQ and/or HARQ in a period time is shown, Total _ data _ Length is the data length of RLC SDU in the period time, length _ RLC _ PDU _ header is the data length of RLC PDU head formed by RLC SDU, packet _ hum is the Total number of data packets, TunitThe BLER is a block error rate which is a period time length used in statistics;
RLC _ SDU _ Num is the number of RLC SDUs whose size on the RB is averaged, and RLC _ SDU _ size is the size of RLC SDU.
In the implementation, one or a combination of the following modes can be further included:
when the effective data amount of RLC of RB is lower than ThresholdLowWhen the data request packet is received, the RLC triggers and sends a data request packet of a control packet type CPT;
when the effective data amount of RLC of RB is higher than ThresholdHighWhen the control packet is received, the RLC triggers to send a data request packet of a control packet type CPT, and the data length in the control packet is set to be 0;
the data volume allocated by each application is as follows:
Figure BDA0002311495500000036
Figure BDA0002311495500000037
freely adjusting and increasing the algorithm;
wherein :
Figure BDA0002311495500000034
Figure BDA0002311495500000035
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)A rate of lower layer transmission;
Figure BDA0002311495500000041
Figure BDA0002311495500000042
Figure BDA0002311495500000043
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)For lower layer transmission rate, Taverage_lowerlayerAverage duration, T, of data packets sent over the RB for ARQ or HARQPDCP_RLC_DelayThe average time length for data transceiving between the RLC and the PDCP is detected.
An embodiment of the present invention provides a PDCP entity, including:
the processor is used for reading the program in the memory and processing data according to the requirement of the transceiver;
a transceiver for receiving and transmitting data under the control of the processor, performing the following processes:
receiving an application, wherein the application is a data volume application sent by Radio Link Control (RLC);
and sending the data to the RLC according to the data volume application.
In implementation, the data volume request is sent by the RLC via a data request packet of the control packet type CPT.
In the implementation, the sending data according to the data volume application comprises:
after receiving a data request packet of a control packet type CPT on an RB, distributing data to the RB and sending the data on the RB; or the like, or, alternatively,
after receiving the data request packet of the control packet type CPT, data is allocated to each user in each RB according to the content requested in the data request packet of the control packet type CPT, and data is transmitted to each user in each RB.
In the implementation, when the data request packet of the control packet type CPT includes a time requirement for transmitting data, the method may further include:
and when data is distributed, changing the distributed data according to the data quantity caused by time delay brought by the time requirement of sending the data, and sending the data according to the time requirement of sending the data.
An embodiment of the present invention provides a PDCP entity, including:
an application receiving module, configured to receive an application, where the application is a data volume application sent by a radio link control RLC;
and the sending module is used for sending data according to the data volume application.
In implementation, the application receiving module may be further configured to receive the application through a data request packet of the control packet type CPT.
In implementation, the allocation module may be further configured to, when sending data according to the data volume application:
after receiving a data request packet of a control packet type CPT on an RB, distributing data to the RB and sending the data on the RB; or the like, or, alternatively,
after receiving the data request packet of the control packet type CPT, data is allocated to each user in each RB according to the content requested in the data request packet of the control packet type CPT, and data is transmitted to each user in each RB.
In an implementation, the sending module may be further configured to, when the data request packet of the control packet type CPT includes a time requirement for sending data:
and when data is distributed, changing the distributed data according to the data quantity caused by time delay brought by the time requirement of sending the data, and sending the data according to the time requirement of sending the data.
An embodiment of the present invention provides an RLC entity, including:
a processor for reading the program in the memory, performing the following processes:
determining the required data volume;
a transceiver for receiving and transmitting data under the control of the processor, performing the following processes:
applying for the data volume to PDCP;
receiving data, wherein the data is sent by the PDCP according to the application.
In implementation, the application is applied by a data request packet of a control packet type CPT.
In practice, the application comprises:
after determining the required data volume on the RB, applying for sending a data request packet of a control packet type CPT to the PDCP on the RB; or the like, or, alternatively,
and after determining the data volume required by each user on each RB, applying for sending a data request packet of a control packet type CPT to the PDCP.
In the implementation, the method further comprises the following steps:
the data request packet of the control packet type CPT includes a time requirement for transmitting data.
In an implementation, determining the required amount of data includes: the required data amount is determined according to the receiving and transmitting conditions of ARQ and/or HARQ data.
In the implementation, the required data amount is determined according to the transmitting and receiving conditions of the ARQ and/or HARQ data, and the required data amount is determined according to the data transmitted by the ARQ and/or HARQ according to one or a combination of the following parameters:
the feedback time delay from sending data packet to receiving ACK/NACK, the total data amount, the number of data packets, the error ratio, BLER, the ratio of ACK and NACK, the number of data packets which reach the maximum sending times and still are not sent successfully, the data amount or the ratio of the data packets which occupy the total sending data packets, the ratio of one-time successful sending and the ratio of multiple successful sending.
In practice, when calculating according to one or a combination of the following parameters, the following formula is used for calculation:
Figure BDA0002311495500000061
Figure BDA0002311495500000062
wherein ,
Figure BDA0002311495500000063
efficient on ARQ and/or HARQ for one cycle timeThe average sending rate of data RLC SDU, Total _ data _ Length is the data length of RLC SDU in a period of time, Length _ RLC _ PDU _ header is the data length of RLC PDU head formed by RLC SDU, packet _ num is the Total number of data packets, TunitThe BLER is a block error rate which is a period time length used in statistics;
RLC _ SDU _ Num is the number of RLC SDUs whose size on the RB is averaged, and RLC _ SDU _ size is the size of RLC SDU.
In the implementation, one or a combination of the following modes can be further included:
when the effective data amount of RLC of RB is lower than ThresholdLowWhen the data request packet is received, the RLC triggers and sends a data request packet of a control packet type CPT;
when the effective data amount of RLC of RB is higher than ThresholdHighWhen the control packet is received, the RLC triggers to send a data request packet of a control packet type CPT, and the data length in the control packet is set to be 0;
the data volume allocated by each application is as follows:
Figure BDA0002311495500000076
Figure BDA0002311495500000077
freely adjusting and increasing the algorithm;
wherein :
Figure BDA0002311495500000071
Figure BDA0002311495500000072
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)A rate of lower layer transmission;
Figure BDA0002311495500000073
Figure BDA0002311495500000074
Figure BDA0002311495500000075
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)For lower layer transmission rate, Taverage_lowerlayerAverage duration, T, of data packets sent over the RB for ARQ or HARQPDCP_RLC_DelayThe average time length for data transceiving between the RLC and the PDCP is detected.
An embodiment of the present invention provides an RLC entity, including:
a determining module for determining a required data amount;
an application sending module, configured to apply for the data volume to a PDCP;
a receiving module, configured to receive data, where the data is sent by the PDCP according to the application.
In implementation, the application sending module may be further configured to send the application through a data request packet of the control packet type CPT.
In implementation, the application sending module may be further configured to, when applying:
after determining the required data volume on the RB, applying for sending a data request packet of a control packet type CPT to the PDCP on the RB; or the like, or, alternatively,
and after determining the data volume required by each user on each RB, applying for sending a data request packet of a control packet type CPT to the PDCP.
In an implementation, the application sending module may be further configured to enable the RLC to include a time requirement for sending data in the data request packet of the control packet type CPT.
In an implementation, the determining module may be further configured to determine the required amount of data including: the required data amount is determined according to the receiving and transmitting conditions of ARQ and/or HARQ data.
In an implementation, the determining module may be further configured to, when determining the required data amount according to the transceiving situation of the ARQ and/or HARQ data, calculate the required data amount according to the data transmitted according to the ARQ and/or HARQ according to one or a combination of the following parameters:
the feedback time delay from sending data packet to receiving ACK/NACK, the total data amount, the number of data packets, the error ratio, BLER, the ratio of ACK and NACK, the number of data packets which reach the maximum sending times and still are not sent successfully, the data amount or the ratio of the data packets which occupy the total sending data packets, the ratio of one-time successful sending and the ratio of multiple successful sending.
In an implementation, the determining module may be further configured to calculate according to the following formula when calculating according to one or a combination of the following parameters:
Figure BDA0002311495500000081
Figure BDA0002311495500000082
wherein ,
Figure BDA0002311495500000083
the average sending rate of effective data RLC SDU on ARQ and/or HARQ in a period time is shown, Total _ data _ Length is the data length of RLC SDU in the period time, length _ RLC _ PDU _ header is the data length of RLC PDU head formed by RLC SDU, packet _ num is the Total number of data packets, TunitThe BLER is a block error rate which is a period time length used in statistics;
RLC _ SDU _ Num is the number of RLC SDUs whose size on the RB is averaged, and RLC _ SDU _ size is the size of RLC SDU.
In an implementation, the application sending module may be further configured to perform one or a combination of the following modes:
when the effective data amount of RLC of RB is lower than ThresholdLowWhen the data request packet is received, the RLC triggers and sends a data request packet of a control packet type CPT;
when the effective data amount of RLC of RB is higher than ThresholdHighWhen the control packet is received, the RLC triggers to send a data request packet of a control packet type CPT, and the data length in the control packet is set to be 0;
the data volume allocated by each application is as follows:
Figure BDA0002311495500000096
Figure BDA0002311495500000097
freely adjusting and increasing the algorithm;
wherein :
Figure BDA0002311495500000091
Figure BDA0002311495500000092
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)A rate of lower layer transmission;
Figure BDA0002311495500000093
Figure BDA0002311495500000094
Figure BDA0002311495500000095
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)For lower layer transmission rate, Taverage_lowerlayerAverage duration, T, of data packets sent over the RB for ARQ or HARQPDCP_RLCDelayThe average time length for data transceiving between the RLC and the PDCP is detected.
An embodiment of the present invention provides a computer-readable storage medium storing a computer program for executing the data amount processing method.
The invention has the following beneficial effects:
in the technical solution provided in the embodiment of the present invention, the RLC sends a data volume application to the PDCP according to the required data volume, and the PDCP performs data allocation control based on the data volume application of the RLC, so that the PDCP has a data volume control function, and thus can implement a requirement of mapping one PDCP entity to a plurality of lower link entities at the same time.
In the scheme, optionally, because interlayer interaction is opened, the control of the PDCP data volume can be realized according to the actual transmission of the RLC layer;
optionally, because of the interaction between the PDCP layer and the RLC layer, the compatibility is good, and the 3G/4G/5G network can be compatible.
Optionally, the ACK/NACK state sent by the data packet feedback air interface of the UM RLC is fed back by the HARQ of the MAC, and the RLC/MAC layer is enabled to confirm and monitor the sending of the UM RLC.
Drawings
The accompanying drawings, which are included to provide an understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention.
In the drawings:
FIG. 1 is a schematic diagram illustrating an implementation flow of a data volume processing method at a PDCP side in an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating an implementation flow of a method for processing the data size of the RLC side according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a data allocation request control packet sent by RLC in an embodiment of the present invention 1;
fig. 4 is a schematic diagram of a data allocation request control packet sent by RLC in an embodiment of the present invention 2;
FIG. 5 is a diagram illustrating a PDCP entity structure in an embodiment of the present invention;
fig. 6 is a diagram illustrating an RLC entity structure according to an embodiment of the present invention.
Detailed Description
The inventor notices in the process of invention that:
when NR-PDCP duplication enhancement is involved, there are specific goals as follows:
specific PDCP duplication with up to 4 RLC entities configured by RRC in architectural combining CA only and NR-DC in combining with CA
Specific mechanisms relating to dynamic control of how configured RLC entities or branches are used for PDCP replication
Specific enhancements for more efficient DL PDCP replication with out multiplexing the UE, provided that the gains can be confirmed with reasonable complexity
Specific enhancements to address potential effects of high-level multi-connectivity based on SA2progress and request (specifying enhancement functions to address potential effects of high-level multi-connectivity based on SA2progress and request)
According to this goal, the duplicate transmission of PDCP studies the scheme of 4 transmission channels and requires no impact on the UE (User Equipment).
In the above scheme, PDCP is required to reasonably distribute datagrams to different one or more lower layer links (i.e., RLC Entities).
When the mode of the MAC layer is related to the outgoing mode, the following scheme is adopted:
a MAC PDU constraints system of a MAC SDU whose size is aligned to a TB; this MAC PDU is used for transmissions on PCH, BCH, and DL-SCH including BCCH (a MAC PDU consisting of only MAC SDUs, the size of which is aligned with TB; this MAC PDU is used for transmission on PCH, BCH, and DL-SCH including BCCH.)
Wherein, PDU: a Protocol Data Unit, Protocol Data Unit; SDU: a Service Data Unit, a Service Data Unit; TB: a Transport Block, Transport Block Set; PCH: paging Channel, Paging Channel; BCH: broadcast Channel, Broadcast Channel; DL-SCH: a Downlink Shared Channel (dl Shared Channel); BCCH: broadcast Control Channel, Broadcast Control Channel.
According to the current scheme, in order to increase the robustness of data transmission, multiplexing is implemented by DC/MC plus MAC CA of PDCP, which becomes a standard choice, and this means that one PDCP entity needs to be mapped to multiple lower link entities at the same time, i.e. the RB of one PDCP layer may be mapped to multiple lower logical channels at the same time.
This scheme requires the PDCP to have a data amount control function, however, there is no technical scheme for providing data amount control for the PDCP in the prior art.
Based on this, in the scheme, the RLC generates a data packet sending Request to the PDCP according to data receiving and sending conditions of ARQ (Automatic Repeat Request) and HARQ (Hybrid Automatic Repeat Request), and the PDCP sends data to each RLC entity according to the data distribution Request of the RLC, thereby realizing data control. The following describes embodiments of the present invention with reference to the drawings.
In the description, the implementation of the PDCP side and the RLC side will be described separately, and the description of the implementation of the PDCP side and the RLC side will be given in the example to better understand the implementation of the scheme provided in the embodiment of the present invention. Such an illustration does not mean that the two must be implemented together or separately, and actually, when the PDCP and the RLC are implemented separately, the PDCP side and the RLC side are solved separately, and when the two are used in combination, the better technical effect is obtained.
Fig. 1 is a schematic flow chart of an implementation of a data volume processing method at a PDCP side, as shown in the figure, the implementation may include:
step 101, receiving an application, wherein the application is a data volume application sent by a Radio Link Control (RLC);
and 102, sending data according to the data volume application.
In specific implementation, the application of PDCP receiving will be mainly described by taking data volume application information as an example, but other information or other forms may be selected according to needs; at this time, the PDCP then performs data allocation according to the data volume application information; and then transmits the data to the RLC.
Fig. 2 is a schematic flow chart of an implementation of a data volume processing method on the RLC side, as shown in the figure, the implementation may include:
step 201, determining a required data volume, and applying for the data volume to PDCP;
step 202, receiving data, wherein the data is sent by the PDCP according to the application.
In specific implementation, when the data volume application information is adopted to carry the application, the RLC sends the data volume application information to the PDCP after determining the required data volume; and then the RLC receives the data sent by the PDCP to the RLC according to the data volume application information.
Specifically, in the scheme, based on the RLC data volume application, the PDCP performs data distribution control, the RLC sends a request to the PDCP, and the PDCP sends data to each RLC entity according to the RLC data distribution request, thereby controlling data volume.
The implementation of the RLC to PDCP transmission request is explained below.
In a specific implementation, an inter-layer interaction mode or primitive for data volume application and allocation can be defined between the RLC and the PDCP.
The data volume application information transmitted by the RLC to the PDCP may include the following information:
the data length of the application may be a byte length, a bit length, the number of RLC SDUs, or the like;
RB ID (IDentifier) to which the data of the present application belongs;
the UE ID of the RB;
the number of RBs of the same UE;
the number of UEs in the application;
the corresponding time point of the application can be a system frame number, a subframe number, a half frame number, or a time timing mode newly introduced between the PDCP/RLC.
In the implementation, the data volume application information transmitted by the RLC is transmitted through a data request packet of the control packet type CPT.
Specifically, the PDCP allocates data according to the received RLC data request information, and sends the data packet to the RLC. The packet structure may be implemented as defined below:
introduce a new CPT (Control PDU Type) Type definition: and applying for a control packet for the data volume. In the current protocol, the CPT is defined as follows, and is defined as a data volume application control packet type CPT in terms of an idle CPT value.
6.2.3.9 Control PDU Type(CPT)field
Length: 3 bits (length: 3bit)
The CPT field indications of The type of The RLC control PDU, The interpretation of The CPT field is provided in Table 6.2.3.9-1 (The CPT field indicates The type of RLC control PDU. The interpretation of The CPT field is provided in Table 6.2.3.9-1)
Table 6.2.3.9-1: CPT field interpretation (Table 6.2.3.9-1: CPT field interpretation)
Figure BDA0002311495500000141
The D/C (Data/Control) field of the RLC is defined by the current RLC protocol (e.g., section 6.2.3.6), and the Data request packet sent by the RLC is the Control packet type CPT.
6.2.3.6 Data/Control(D/C)field
Length: 1bit (length: 1bit)
The D/C field indicators of The RLC PDU is an RLC data PDU or an RLC control PDU, The interpretation of The D/C field is provided in Table 6.2.3.6-1 (The D/C field indicates whether The RLC PDU is an RLC data PDU or an RLC control PDU. The interpretation of The D/C field is shown in Table 6.2.3.6-1)
Table 6.2.3.6-1: D/C field interpretation (Table 6.2.3.6-1: D/C field interpretation)
Value Description
0 Control PDU (Control PDU)
1 Data PDU (Data PDU)
Fig. 3 is a schematic diagram of a data allocation request control packet sent by RLC, and as shown in fig. 3, a request control packet format only containing the requested data length is shown.
In implementation, at the PDCP side, sending data according to the data volume application includes:
after receiving a data request packet of a control packet type CPT on an RB, the PDCP distributes data to the RB and sends the data on the RB; or the like, or, alternatively,
after receiving the data request packet of the control packet type CPT, the PDCP allocates data to each user in each RB according to the content requested in the data request packet of the control packet type CPT, and transmits the data to each user in each RB.
Correspondingly, on the RLC side, the application includes:
after the RLC determines the required data volume on the RB, a data request packet of a control packet type CPT is applied to the PDCP on the RB; or the like, or, alternatively,
after determining the data volume required by each user on each RB, the RLC applies for sending a data request packet of a control packet type CPT to the PDCP.
In a specific implementation, when the RLC sends the data allocation control packet shown in fig. 3, the RLC may send the data allocation control packet to the RB that needs to apply for data, and after receiving the data allocation request control packet in the corresponding RB, the PDCP allocates data to the RB that receives the control packet, and sends the data to the RB. That is, after the RLC determines the required data amount on the RB, it sends a data request packet of the control packet type CPT to the PDCP on the RB; the PDCP, after receiving the data request packet of the control packet type CPT on the RB, allocates data to the RB and transmits the data on the RB.
Fig. 4 is a schematic diagram of a data allocation request control packet sent by an RLC, and as shown in fig. 4, a format of the data allocation request control packet sent by the RLC carrying all information is shown. The packet includes a plurality of RBs simultaneously applying for data volume to a plurality of users.
In this way, the RLC may send the control packet over any available RB, or may send the control packet based on an inter-layer primitive of the PDCP/RLC. That is, after determining the data amount required by each user on each RB, the RLC sends a data request packet of a control packet type CPT to the PDCP; after receiving the data request packet of the control packet type CPT, the PDCP allocates data to each user in each RB according to the content requested in the data request packet of the control packet type CPT, and transmits the data to each user in each RB.
The control packet in the format of fig. 4 may reduce the number of transmission control packets relative to the control packet in the format of fig. 3.
In the implementation, when the data request packet of the control packet type CPT includes a time requirement for transmitting data, the method may further include:
when data is distributed, the PDCP changes the distributed data according to the data quantity caused by time delay brought by the time requirement of sending the data, and sends the data according to the time requirement of sending the data.
Correspondingly, on the RLC side, the method may also include:
the RLC includes a time requirement for transmitting data in a data request packet of the control packet type CPT.
In specific implementation, if the control packet carries the transmission time, the PDCP may be configured to estimate a delay of PCPC/RLC direct packet transmission, so that a data amount requirement caused by the delay may be considered when performing data amount control.
For PDCP, after receiving the data distribution request control packet, data transmission is performed according to the data amount applied in the control packet.
The following describes an embodiment in which the RLC side RLC determines a required data amount.
An application mechanism of data volume is introduced between PDCP/RLC. The RLC mainly applies for and generates data volume data from two aspects:
1. judging the receiving and transmitting state of data at an air interface based on the receiving and transmitting conditions of ARQ (Automatic Repeat reQuest) and/or HARQ (Hybrid Automatic Repeat reQuest) data; that is, the RLC determines the required data amount according to the transmission/reception situation of ARQ and/or HARQ data.
2. And according to the time length of receiving the first data packet after the data request packet is sent and the condition of whether the sending buffer is empty or not, self-learning the sum of the time delay of the data packet established by the PDCP and the time delay of data sending between the PDCP and the RLC, and dynamically considering the compensation data amount in the generated data request packet. Specifically, the RLC records the time delay from sending a data request to receiving the first data packet corresponding to the request packet, and forms self-learning of the time delay through multiple recording and gradual accumulation.
In a specific implementation, the RLC determines the required data amount according to the transmission and reception conditions of ARQ and/or HARQ data, and calculates the required data amount according to the data transmitted by ARQ and/or HARQ according to one or a combination of the following parameters:
the feedback time delay from sending data packet to receiving ACK/NACK, the total data amount, the number of data packets, the error ratio, BLER, the ratio of ACK and NACK, the number of data packets which reach the maximum sending times and still are not sent successfully, the data amount or the ratio of the data packets which occupy the total sending data packets, the ratio of one-time successful sending and the ratio of multiple successful sending.
The manner of obtaining these parameters is explained below.
And the RLC protocol entity calculates the data volume according to different RLC modes.
1. UM (Unacknowledged Mode) Mode:
if the RB (Radio Bearer) is in UM RLC mode in the RLC layer, the following process is performed:
if the data of the RB is transmitted and received in the MAC layer by using the HARQ mode, counting according to the transmitting and receiving conditions of the HARQ;
if the data of the RB is transmitted by using a Transparent transmission (MAC) mode at an MAC layer, namely, the MAC Transparent transmission mode is still used, and if the data packet is broadcast data, the transmitting and receiving conditions of the data packet cannot be counted because no feedback exists, and when the data packet is transmitted by the PDCP layer, the data packet is distributed according to the data transmitting and receiving quality obtained by historical statistics of other RBs in a lower-layer link;
if the RB data is transmitted by using a Transparent MAC mode in the MAC layer, but the data packet has feedback, feedback information corresponding to the data packet is obtained according to the feedback time sequence relation.
2. AM (Acknowledged Mode) Mode:
if the RB is in the AM RLC mode in the RLC layer, the following process is performed:
obtaining statistical information sent by the data packet according to the ARQ feedback of the data packet;
the feedback of HARQ for this packet is taken as secondary statistics.
The transmission and reception statistics for data for ARQ and HARQ are implemented as follows:
1、ARQ:
and counting the total number of the transmitted data packets in unit time on each RB.
The NACK number of each packet is counted (one packet may be retransmitted multiple times), and the NACK number of all packets on the RB in a unit period is calculated.
And counting the ACK times of all the data packets on the RB in the unit time.
And counting the average time delay of the data packet transmission in unit time.
Based on the statistical data, an average data transmission rate to the RB is calculated.
2、HARQ:
And counting the transmitting and receiving conditions of each data packet by taking RB as a unit. Since the MAC PDU may contain data packets on one or more RBs at the same time, the MAC layer needs to count the MAC SDUs (RLC PDUs) transmitted each time.
And counting the HARQ transmission times of each MAC SDU, and counting the total transmission times and the average transmission times of the data on the corresponding RB in unit time.
The number of MAC SDUs successfully transmitted (ACK) and the total number of transmitted MAC SDUs are counted, and the ratio of data transmission success (ACK) over the corresponding RB per unit time is counted.
In practice, when calculating according to one or a combination of the following parameters, the following formula can be used for calculation:
Figure BDA0002311495500000181
Figure BDA0002311495500000182
wherein ,
Figure BDA0002311495500000183
the average sending rate of effective data RLC SDU on ARQ and/or HARQ in a period time is shown, Total _ data _ Length is the data length of RLC SDU in the period time, length _ RLC _ PDU _ header is the data length of RLC PDU head formed by RLC SDU, packet _ num is the Total number of data packets, TunitThe BLER is a block error rate which is a period time length used in statistics;
RLC _ SDU _ Num is the number of RLC SDUs whose size on the RB is averaged, and RLC _ SDU _ size is the size of RLC SDU.
Specifically, the following calculation is performed according to the transmission delay, the total data amount, the number of data packets, the error ratio, and the like counted in the ARQ and/or HARQ:
Figure BDA0002311495500000184
Figure BDA0002311495500000191
obtaining the average sending rate of the effective data RLC SDU on ARQ and/or HARQ through a formula (1); the number of RLC SDUs transmitted on average is obtained based on the size of RLC SDUs on the RB by formula (2).
In the implementation, one or a combination of the following modes can be further included:
when the effective data amount of RLC of RB is lower than ThresholdLowWhen the data request packet is received, the RLC triggers and sends a data request packet of a control packet type CPT;
when the effective data amount of RLC of RB is higher than ThresholdHighWhen the control packet is received, the RLC triggers to send a data request packet of a control packet type CPT, and the data length in the control packet is set to be 0;
the data volume allocated by each application is as follows:
Figure BDA0002311495500000197
Figure BDA0002311495500000198
freely adjusting and increasing the algorithm;
wherein :
Figure BDA0002311495500000192
Figure BDA0002311495500000193
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)Rate for lower layer transmission:
Figure BDA0002311495500000194
Figure BDA0002311495500000195
Figure BDA0002311495500000196
is an algorithm ofIncreased by the adjustment, Initial _ Value is taken as the Initial Value, RLC _ SDU _ Numformula(2)For lower layer transmission rate, Taverage_lowerlayerAverage duration, T, of data packets sent over the RB for ARQ or HARQPDCP_RLC_DelayThe average time length for data transceiving between the RLC and the PDCP is detected.
Specifically, two thresholds may be set for the number of valid data that can be transmitted per RB of the AM/UM RLC mode (the definition of valid data may refer to at least the effective data of PDCP and the effective number of RLC that are specifically defined in the PDCP/RLC protocol in implementation).
Two thresholds are set for the data amount of valid data that can be transmitted by the RLC of this RB: high Threshold (Threshold)High) Threshold (Threshold) of the ThresholdLow)。
Figure BDA0002311495500000201
In the Value of the low threshold, when there is no measurement information, an Initial Value is taken; otherwise, the dynamic adjustment is carried out according to the rate of the low-layer transmission.
Figure BDA0002311495500000202
And (4) adding for algorithm free adjustment.
Figure BDA0002311495500000203
In the Value of the high threshold, when no measurement information exists, an Initial Value (Initial _ Value) is taken; otherwise, the dynamic adjustment is carried out according to the rate of the low-layer transmission. Two time counts in the high threshold:
Taverage_lowerlayerthe unit may be ms for the average duration of the ARQ or HARQ transmission of the packet on the RB.
IPDCP_RLC_DelayThe RLC may detect an average duration of data transceiving with the PDCP unit in ms. Dynamic self-learning adjustments based on actual data transceiver monitoring delays, e.g.And recording the time delay from the data distribution control packet to the first data packet after each data distribution control packet is sent, and performing smooth calculation.
Data volume of generated application:
when the effective data amount of RLC of RB is lower than ThresholdLowWhen the data is received, the RLC triggers the sending of a data distribution packet;
when the effective data amount of RLC of RB is higher than ThresholdHighWhen the data length in the control packet is set to 0, the RLC triggers transmission of a stop transmission data allocation packet.
Data volume allocated per application:
Figure BDA0002311495500000204
Figure BDA0002311495500000205
and (4) adding for algorithm free adjustment.
Based on the same inventive concept, embodiments of the present invention further provide a PDCP entity, an RLC entity, and a computer readable storage medium, and since the principle of solving the problem of these devices is similar to the data amount processing method, the implementation of these devices may refer to the implementation of the method, and repeated details are not repeated.
When the technical scheme provided by the embodiment of the invention is implemented, the implementation can be carried out as follows.
Fig. 5 is a schematic structural diagram of a PDCP entity, which includes:
a processor 500 for reading the program stored in the memory 520 and processing data according to the requirement of the transceiver;
a transceiver 510 for receiving and transmitting data under the control of the processor 500, performing the following processes:
receiving an application, wherein the application is a data volume application sent by Radio Link Control (RLC);
and sending the data to the RLC according to the data volume application.
In implementation, the data volume request is sent by the RLC via a data request packet of the control packet type CPT.
In the implementation, the sending data according to the data volume application comprises:
after receiving a data request packet of a control packet type CPT on an RB, distributing data to the RB and sending the data on the RB; or the like, or, alternatively,
after receiving the data request packet of the control packet type CPT, data is allocated to each user in each RB according to the content requested in the data request packet of the control packet type CPT, and data is transmitted to each user in each RB.
In the implementation, when the data request packet of the control packet type CPT includes a time requirement for transmitting data, the method may further include:
and when data is distributed, changing the distributed data according to the data quantity caused by time delay brought by the time requirement of sending the data, and sending the data according to the time requirement of sending the data.
Wherein in fig. 5, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 500, and various circuits, represented by memory 520, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.
An embodiment of the present invention provides a PDCP entity, including:
an application receiving module, configured to receive an application, where the application is a data volume application sent by a radio link control RLC;
and the sending module is used for sending data according to the data volume application.
In implementation, the application receiving module may be further configured to receive the application through a data request packet of the control packet type CPT.
In implementation, the allocation module may be further configured to, when sending data according to the data volume application:
after receiving a data request packet of a control packet type CPT on an RB, distributing data to the RB and sending the data on the RB; or the like, or, alternatively,
after receiving the data request packet of the control packet type CPT, data is allocated to each user in each RB according to the content requested in the data request packet of the control packet type CPT, and data is transmitted to each user in each RB.
In an implementation, the sending module may be further configured to, when the data request packet of the control packet type CPT includes a time requirement for sending data:
and when data is distributed, changing the distributed data according to the data quantity caused by time delay brought by the time requirement of sending the data, and sending the data according to the time requirement of sending the data.
For convenience of description, each part of the above-described apparatus is separately described as being functionally divided into various modules or units. Of course, the functionality of the various modules or units may be implemented in the same one or more pieces of software or hardware in practicing the invention.
Fig. 6 is a schematic diagram of an RLC entity structure, as shown, including:
the processor 600, which is used to read the program in the memory 620, executes the following processes:
determining the required data volume;
a transceiver 610 for receiving and transmitting data under the control of the processor 600, performing the following processes:
applying for the data volume to PDCP;
receiving data, wherein the data is sent by the PDCP according to the application.
In implementation, the application is applied by a data request packet of a control packet type CPT.
In practice, the application comprises:
after determining the required data volume on the RB, applying for sending a data request packet of a control packet type CPT to the PDCP on the RB; or the like, or, alternatively,
and after determining the data volume required by each user on each RB, applying for sending a data request packet of a control packet type CPT to the PDCP.
In the implementation, the method further comprises the following steps:
the data request packet of the control packet type CPT includes a time requirement for transmitting data.
In an implementation, determining the required amount of data includes: the required data amount is determined according to the receiving and transmitting conditions of ARQ and/or HARQ data.
In the implementation, the required data amount is determined according to the transmitting and receiving conditions of the ARQ and/or HARQ data, and the required data amount is determined according to the data transmitted by the ARQ and/or HARQ according to one or a combination of the following parameters:
the feedback time delay from sending data packet to receiving ACK/NACK, the total data amount, the number of data packets, the error ratio, BLER, the ratio of ACK and NACK, the number of data packets which reach the maximum sending times and still are not sent successfully, the data amount or the ratio of the data packets which occupy the total sending data packets, the ratio of one-time successful sending and the ratio of multiple successful sending.
In practice, when calculating according to one or a combination of the following parameters, the following formula is used for calculation:
Figure BDA0002311495500000231
Figure BDA0002311495500000232
wherein ,
Figure BDA0002311495500000233
the average sending rate of effective data RLC SDU on ARQ and/or HARQ in a period time is shown, Total _ data _ Length is the data length of RLC SDU in the period time, length _ RLC _ PDU _ header is the data length of RLC PDU head formed by RLC SDU, packet _ num is the Total number of data packets, TunitFor a statistical period of time, BLER is the block error rate;
RLC _ SDU _ Num is the number of RLC SDUs whose size on the RB is averaged, and RLC _ SDU _ size is the size of RLC SDU.
In the implementation, one or a combination of the following modes can be further included:
when the effective data amount of RLC of RB is lower than ThresholdLowWhen the data request packet is received, the RLC triggers and sends a data request packet of a control packet type CPT;
when the effective data amount of RLC of RB is higher than ThresholdHighWhen the control packet is received, the RLC triggers to send a data request packet of a control packet type CPT, and the data length in the control packet is set to be 0;
the data volume allocated by each application is as follows:
Figure BDA0002311495500000246
Figure BDA0002311495500000247
freely adjusting and increasing the algorithm;
wherein :
Figure BDA0002311495500000241
Figure BDA0002311495500000242
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)A rate of lower layer transmission;
Figure BDA0002311495500000243
Figure BDA0002311495500000244
Figure BDA0002311495500000245
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)For lower layer transmissionRate, Taverage_lowerlayerAverage duration, T, of data packets sent over the RB for ARQ or HARQPDCP_RLC_DelayThe average time length for data transceiving between the RLC and the PDCP is detected.
Where in fig. 6, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described further herein. The bus interface provides an interface. The transceiver 610 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 in performing operations.
An embodiment of the present invention provides an RLC entity, including:
a determining module for determining a required data amount;
an application sending module, configured to apply for the data volume to a PDCP;
a receiving module, configured to receive data, where the data is sent by the PDCP according to the application.
In implementation, the application sending module may be further configured to send the application through a data request packet of the control packet type CPT.
In implementation, the application sending module may be further configured to, when applying:
after determining the required data volume on the RB, applying for sending a data request packet of a control packet type CPT to the PDCP on the RB; or the like, or, alternatively,
and after determining the data volume required by each user on each RB, applying for sending a data request packet of a control packet type CPT to the PDCP.
In an implementation, the application sending module may be further configured to enable the RLC to include a time requirement for sending data in the data request packet of the control packet type.
In an implementation, the determining module may be further configured to determine the required amount of data including: the required data amount is determined according to the receiving and transmitting conditions of ARQ and/or HARQ data.
In an implementation, the determining module may be further configured to, when determining the required data amount according to the transceiving situation of the ARQ and/or HARQ data, calculate the required data amount according to the data transmitted according to the ARQ and/or HARQ according to one or a combination of the following parameters:
the feedback time delay from sending data packet to receiving ACK/NACK, the total data amount, the number of data packets, the error ratio, BLER, the ratio of ACK and NACK, the number of data packets which reach the maximum sending times and still are not sent successfully, the data amount or the ratio of the data packets which occupy the total sending data packets, the ratio of one-time successful sending and the ratio of multiple successful sending.
In an implementation, the determining module may be further configured to calculate according to the following formula when calculating according to one or a combination of the following parameters:
Figure BDA0002311495500000261
Figure BDA0002311495500000262
wherein ,
Figure BDA0002311495500000263
the average sending rate of effective data RLC SDU on ARQ and/or HARQ in a period time is shown, Total _ data _ Length is the data length of RLC SDU in the period time, length _ RLC _ PDU _ header is the data length of RLC PDU head formed by RLC SDU, packet _ num is the Total number of data packets, TunitThe BLER is a block error rate which is a period time length used in statistics;
RLC _ SDU _ Num is the number of RLC SDUs whose size on the RB is averaged, and RLC _ SDU _ size is the size of RLC SDU.
In an implementation, the application sending module may be further configured to perform one or a combination of the following modes:
when the effective data amount of RLC of RB is lower than ThresholdLowWhen the data request packet is received, the RLC triggers the data request packet of the type of the control packet to be sent;
when the effective data amount of RLC of RB is higher than ThresholdHighWhen the control packet is received, the RLC triggers to send a data request packet of a control packet type CPT, and the data length in the control packet is set to be 0;
the data volume allocated by each application is as follows:
Figure BDA0002311495500000264
Figure BDA0002311495500000265
freely adjusting and increasing the algorithm;
wherein :
Figure BDA0002311495500000266
Figure BDA0002311495500000267
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)A rate of lower layer transmission;
Figure BDA0002311495500000268
Figure BDA0002311495500000271
Figure BDA0002311495500000272
Figure BDA0002311495500000273
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)For lower layer transmission rate, Taverage_lowerlayerAverage duration, T, of data packets sent over the RB for ARQ or HARQPDCP_RLC_DelayIs RLC detects the average time length of data transceiving between the PDCP and the PDCP.
For convenience of description, each part of the above-described apparatus is separately described as being functionally divided into various modules or units. Of course, the functionality of the various modules or units may be implemented in the same one or more pieces of software or hardware in practicing the invention.
An embodiment of the present invention provides a computer-readable storage medium, which stores a computer program for executing the above-mentioned PDCP-side and/or RLC-side data volume processing method.
The specific implementation can be seen in the implementation of the data volume processing method of the PDCP side and/or the RLC side.
In summary, in the technical solution provided in the embodiment of the present invention, the PDCP entity performs data allocation control based on the RLC data volume application.
In the scheme, the control of the PDCP data volume is realized according to the actual sending of the RLC layer by opening the interaction between the layers;
and opening up the transmission confirmation and monitoring of the UM RLC by the RLC/MAC layer.
The compatibility is good, and the 3G/4G/5G network can be compatible.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (17)

1. A data volume processing method is applied to a Packet Data Convergence Protocol (PDCP), and is characterized by comprising the following steps:
receiving an application, wherein the application is a data volume application sent by Radio Link Control (RLC);
and sending data according to the data volume application.
2. The method of claim 1, wherein the data volume application is transmitted by the RLC via a data request packet of a control packet type CPT.
3. The method of claim 2, wherein transmitting data in accordance with the data volume application comprises:
after receiving a data request packet of a control packet type CPT on a data Radio Bearer (RB), sending data on the RB; or the like, or, alternatively,
after receiving the data request packet of the control packet type CPT, data is allocated to each user in each RB according to the content requested in the data request packet of the control packet type CPT, and data is transmitted to each user in each RB.
4. The method as claimed in claim 3, wherein when the data request packet of the control packet type CPT includes a time requirement for transmitting data, it comprises:
and when data is distributed, changing the distributed data according to the data quantity caused by time delay brought by the time requirement of sending the data, and sending the data according to the time requirement of sending the data.
5. A data volume processing method is applied to RLC, and is characterized by comprising the following steps:
determining the required data volume and applying for the data volume from the PDCP;
receiving data, wherein the data is sent by the PDCP according to the application.
6. The method of claim 5, wherein the application is applied through a data request packet of a control packet type CPT.
7. The method of claim 6, wherein said applying comprises:
after determining the required data volume on the RB, applying a data request packet of a control packet type CPT to the PDCP on the RB; or the like, or, alternatively,
and after determining the data volume required by each user on each RB, applying a data request packet of a control packet type CPT to the PDCP.
8. The method of claim 7, comprising:
the data request packet of the control packet type CPT includes a time requirement for transmitting data.
9. The method of any of claims 5 to 8, wherein determining the required amount of data comprises: and determining the required data quantity according to the receiving and sending conditions of the automatic repeat request ARQ and/or hybrid automatic repeat request HARQ data.
10. The method of claim 9, wherein the determining the required amount of data according to the transceiving conditions of the ARQ and/or HARQ data is based on calculating the required amount of data determined according to the data transmitted in the ARQ and/or HARQ according to one or a combination of the following parameters:
the feedback time delay from sending data packet to receiving ACK/NACK, the total data amount, the number of data packets, the error ratio, BLER, the ratio of ACK and NACK, the number of data packets which reach the maximum sending times and still are not sent successfully, the data amount or the ratio of the data packets which occupy the total sending data packets, the ratio of one-time successful sending and the ratio of multiple successful sending.
11. The method of claim 10, wherein when calculating according to one or a combination of the following parameters, the following formula is used:
Figure FDA0002311495490000021
Figure FDA0002311495490000022
wherein ,
Figure FDA0002311495490000023
for ARQ and/or HA within one cycle timeThe average sending rate of effective data RLC service data unit SDU on RQ, Total _ data _ Length is the data length of RLC SDU in a period of time, length _ RLC _ PDU _ header is the data length of RLC protocol data unit PDU head formed by RLC SDU, packet _ num is the Total number of data packets, TunitThe BLER is a block error rate which is a period time length used in statistics;
RLC _ SDU _ Num is the number of RLC SDUs whose size on the RB is averaged, and RLC _ SDU _ size is the size of RLC SDU.
12. The method of claim 9, comprising one or a combination of the following:
when the effective data amount of RLC of RB is lower than ThresholdLowWhen the data request packet is received, the RLC triggers and sends a data request packet of a control packet type CPT;
when the effective data amount of RLC of RB is higher than ThresholdHighWhen the control packet is received, the RLC triggers to send a data request packet of a control packet type CPT, and the data length in the control packet is set to be 0;
the data volume allocated by each application is as follows:
Figure FDA0002311495490000031
Figure FDA0002311495490000032
freely adjusting and increasing the algorithm;
wherein :
Figure FDA0002311495490000033
Figure FDA0002311495490000034
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)A rate of lower layer transmission;
Figure FDA0002311495490000035
Figure FDA0002311495490000036
Figure FDA0002311495490000037
for the algorithm to be adjusted and increased freely, Initial _ Value is used as the Initial Value, RLC _ SDU _ Numformula(2)For lower layer transmission rate, Taverage_lowerlayerAverage duration, T, of data packets sent over the RB for ARQ or HARQPDCP_RLC_DelayThe average time length for data transceiving between the RLC and the PDCP is detected.
13. A PDCP entity, comprising:
the processor is used for reading the program in the memory and processing data according to the requirement of the transceiver;
a transceiver for receiving and transmitting data under the control of the processor, performing the following processes:
receiving an application, wherein the application is a data volume application sent by Radio Link Control (RLC);
and sending the data to the RLC according to the data volume application.
14. A PDCP entity, comprising:
an application receiving module, configured to receive an application, where the application is a data volume application sent by a radio link control RLC;
and the sending module is used for sending data according to the data volume application.
15. An RLC entity, comprising:
a processor for reading the program in the memory, performing the following processes:
determining the required data volume;
a transceiver for receiving and transmitting data under the control of the processor, performing the following processes:
applying for the data volume to PDCP;
receiving data, wherein the data is sent by the PDCP according to the application.
16. An RLC entity, comprising:
a determining module for determining a required data amount;
an application sending module, configured to apply for the data volume to a PDCP;
a receiving module, configured to receive data, where the data is sent by the PDCP according to the application.
17. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1 to 12.
CN201911260559.7A 2019-12-10 2019-12-10 Data volume processing method, device and medium Active CN112953849B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911260559.7A CN112953849B (en) 2019-12-10 2019-12-10 Data volume processing method, device and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911260559.7A CN112953849B (en) 2019-12-10 2019-12-10 Data volume processing method, device and medium

Publications (2)

Publication Number Publication Date
CN112953849A true CN112953849A (en) 2021-06-11
CN112953849B CN112953849B (en) 2023-05-09

Family

ID=76226163

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911260559.7A Active CN112953849B (en) 2019-12-10 2019-12-10 Data volume processing method, device and medium

Country Status (1)

Country Link
CN (1) CN112953849B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100278121A1 (en) * 2007-01-09 2010-11-04 Sung Duck Chun Method of supporting data retransmission in a wireless communication system
CN102395156A (en) * 2011-09-28 2012-03-28 电信科学技术研究院 Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity
CN107404734A (en) * 2016-05-18 2017-11-28 中兴通讯股份有限公司 Data transmission method for uplink, apparatus and system
CN109314884A (en) * 2016-06-15 2019-02-05 华为技术有限公司 Business datum shunt method and device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100278121A1 (en) * 2007-01-09 2010-11-04 Sung Duck Chun Method of supporting data retransmission in a wireless communication system
CN102395156A (en) * 2011-09-28 2012-03-28 电信科学技术研究院 Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity
CN107404734A (en) * 2016-05-18 2017-11-28 中兴通讯股份有限公司 Data transmission method for uplink, apparatus and system
CN109314884A (en) * 2016-06-15 2019-02-05 华为技术有限公司 Business datum shunt method and device

Also Published As

Publication number Publication date
CN112953849B (en) 2023-05-09

Similar Documents

Publication Publication Date Title
US9936423B2 (en) Method and apparatus for enhancing RLC for flexible RLC PDU size
EP1710963B1 (en) Method and apparatus for reporting a buffer status using node B-estimated buffer status information in a mobile communication system
CN102301633B (en) Signal transmission scheme for efficient management of common enhanced dedicated channel
TWI672969B (en) Method and mobile communication device to support data preprocessing
TWI731061B (en) Automatic retransmission scheduling method, terminal, network side equipment and storage medium
EP1710962A1 (en) Method and apparatus for scheduling uplink packet transmission in a mobile communication system
CN101621369B (en) Method of performing packet transmission and priority, and relevant apparatus thereof
JP2016500981A (en) Method for adjusting aggregation size based on acknowledgment (ACK) bitmap
JP4763343B2 (en) Method and apparatus for allocating resources in a network
CN104137507B (en) Feed back the message treatment method and device of packet loss
CN102088715B (en) Packet segmentation method and equipment
CN102595609A (en) Method and system for realizing uplink sub-frame dispatch in sub-frame binding
CN112953849B (en) Data volume processing method, device and medium
US10027443B2 (en) Method and device for frame acknowledgment
CN102665183B (en) Adaptive frame size computing method for transmitting M2M (machine to machine) service in wireless system
CN111601343B (en) Frame aggregation method, terminal device and computer storage medium
CN104661311A (en) Buffer status report (BSR) processing method, device and terminal under carrier aggregation
CN109150417A (en) The method and apparatus for sending and receiving uplink information
CN106341348A (en) TCP service oriented flow control method and access network element
EP2434679B1 (en) Method and device for managing hybrid automatic repeat request multi-process data
KR101012549B1 (en) A method and apparatus for packet aggregation according to traffic characteristics
CN112532354B (en) RLC layer AM mode transmission method and device
US20220417949A1 (en) Method performed by user equipment, and user equipment
CN101795469A (en) Data transmission method and device
CN111726865B (en) Medium access control service data unit processing and receiving method, equipment 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