CN112996052A - Data transmission control method and device, terminal, base station and medium - Google Patents
Data transmission control method and device, terminal, base station and medium Download PDFInfo
- Publication number
- CN112996052A CN112996052A CN202110183614.8A CN202110183614A CN112996052A CN 112996052 A CN112996052 A CN 112996052A CN 202110183614 A CN202110183614 A CN 202110183614A CN 112996052 A CN112996052 A CN 112996052A
- Authority
- CN
- China
- Prior art keywords
- pdcp
- status report
- report information
- sending
- sent
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/04—Error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention provides a data transmission control method and device, a terminal, a base station and a medium, wherein the method comprises the steps that a PDCP sending end acquires PDCP status report information sent by a PDCP receiving end; and if the parameter in the PDCP status report information is unsuccessfully matched with the current sending status of the PDCP sending terminal, correcting the encryption parameter of a PDCP PDU data packet to be sent or to be retransmitted by the sending terminal according to the parameter in the PDCP status report information so as to obtain the corrected encryption parameter. By the scheme, the encryption parameters of the PDCP PDU data packet to be sent or retransmitted subsequently by the sending terminal are corrected according to the parameters in the PDCP status report information, so that data recovery is realized.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a data transmission control method and apparatus, a terminal, a base station, and a medium.
Background
In a communication system, in order to protect the security of a user from being tampered or monitored, user data is generally encrypted and transmitted, and then a receiving end decrypts the user data according to a protocol specification after receiving the user data. Fig. 1 is a schematic diagram illustrating an encryption and decryption method of a PDCP layer packet in the prior art, and as shown in fig. 1, data interaction can be normally performed only when KEY, COUNT, BEARER, DIRECTION, LENGTH, NEA/EEA of a transmitting end and a receiving end are the same, otherwise, an erroneous packet is decrypted. In a real network, KEY, BEARER, DIRECTION, LENGTH, EEA/NEA are semi-static data and are not easy to make errors, and COUNT is easy to make errors due to the fact that the COUNT is dynamically updated every time a PDCP PDU data packet is received, and therefore the decrypted data is abnormal. One of the conditions that is likely to occur during communication is that the encryption parameters used by the transmitting end are different from the receiving parameters used by the receiving end, and data decryption fails, thereby causing a failure in normal use of the service.
Disclosure of Invention
Embodiments of the present invention provide a data transmission control method and apparatus, a terminal, a base station, and a medium, where the data transmission control method can determine that a parameter carried in STATUS REPORT information and a current transmission STATUS on a PDCP sending entity of corresponding data corresponding to a data sending end have deviated when a data sending end receives PDCP STATUS REPORT information (PDCP STATUS REPORT) sent by a data receiving end, so as to correct according to the parameter in the PDCP STATUS REPORT information, thereby implementing data recovery.
In a first aspect, an embodiment of the present application provides a data transmission control method, including:
the PDCP sending end acquires PDCP status report information sent by the PDCP receiving end; and
and if the parameters in the PDCP status report information are determined to be unsuccessfully matched with the current sending status of the PDCP sending terminal, correcting the encryption parameters of the PDCP PDU data packet to be sent or retransmitted by the sending terminal according to the parameters in the PDCP status report information so as to obtain the corrected encryption parameters.
Further, before the determining that the parameter in the PDCP status report information fails to match the current transmission status of the PDCP transmitting end, the method further includes:
determining whether the parameters in the PDCP status report information are successfully matched with the current sending status of the PDCP sending end;
and if the matching is successful, determining that the PDCP sending end and the PDCP receiving end communicate normally according to the matching result.
Further, the parameters in the PDCP status report information include a count value of a first non-received PDCP PDU data packet of the PDCP receiving end and information of a receiving condition of a subsequent PDCP PDU data packet of the first non-received PDCP PDU data packet, and the current sending status of the PDCP sending end includes a count value of a next to-be-sent PDCP PDU data packet of the PDCP sending end and information of a current PDCP PDU data packet waiting for radio link control acknowledgement. Wherein, the receiving condition information of the subsequent PDCP PDU data packet can be determined according to the bitmap indication in the PDCP status report information.
Further, the determining whether the parameter in the PDCP status report information matches the current transmission status of the PDCP transmitting end successfully includes:
determining whether one or more indicated count values of the PDCP PDU data packets in the PDCP status report information fall into a set count value range, wherein the set count value range is an interval range which is not less than a count value corresponding to a first PDCP PDU data packet which is not confirmed by radio link control and is not more than a count value corresponding to a last sent PDCP PDU data packet;
and if the number of the matched objects falls into the range of the set counting value, the matching is successful, and if the number of the matched objects does not fall into the range of the set counting value, the matching is failed.
Further, the modifying the ciphering parameters of the PDCP PDU data packet to be sent or to be retransmitted by the sending end according to the parameters in the PDCP status report information includes:
and updating the count value of the PDCP PDU data packet to be transmitted or retransmitted subsequently by the PDCP transmitting end to the count value of the PDCP PDU data packet which is failed to be transmitted firstly by the transmitting end or the count value of the PDCP PDU data packet corresponding to any Bitmap in the PDCP status report information. Wherein, the COUNT (COUNT) value of the PDCP PDU packet that the first sending of the sending end fails can be determined according to the COUNT value of the PDCP PDU packet corresponding to any Bitmap in the FMC or PDCP status report information in the status report; wherein, the count value of the current PDCP PDU data packet to be sent or retransmitted is sequentially accumulated by 1 according to the count value of the previous PDCP PDU data packet.
Further, after determining that the parameter in the PDCP status report information fails to match the current transmission status of the PDCP sending end, the method further includes:
determining a PDCP SDU which fails to be sent by the PDCP sending end according to the current sending state of the PDCP sending end;
reconstructing the PDCP SDU which fails to be sent into a new PDCU PDU according to the corrected encryption parameters;
and recombining a new PDCU PDU to be sent to the PDCP receiving end according to the corrected encryption parameter.
Further, the determining, according to the current transmission state of the PDCP transmitting end, that the PDCP transmitting end fails to transmit the PDCP SDU includes:
and after determining that the parameters in the PDCP status report information are matched with the current sending status of the PDCP sending end and fail, judging that the data packets of the PDCP PDUs waiting for the radio link control confirmation are all sent unsuccessfully, and judging that the PDCP SDUs corresponding to the data packets of the PDCP PDUs waiting for the radio link control confirmation are all sent unsuccessfully.
In an implementation manner, if it is determined that the parameters in the PDCP status report information are unsuccessfully matched with the current transmission status of the PDCP transmitting end, it may be determined that all PDCP PDU packets that are not acknowledged by the radio link control have failed to be transmitted, and the PDCP SDUs corresponding to the PDCP PDU packets that are not acknowledged by the radio link control need to be retransmitted. Specifically, the TX _ NEXT may be updated to the COUNT corresponding to a bit in the FMC or STATUS PDU, and then the PDCP SDUs that need to be retransmitted are assembled into a new PDCP PDU according to the TX _ NEXT, and then the new PDCP PDU is sent to the PDCP receiving end.
In a second aspect, an embodiment of the present application further provides a data transmission control apparatus, including: a processor and a memory, the memory being configured to store at least one instruction, which is loaded and executed by the processor to implement the data transmission control method provided by the first aspect. In one implementation, the data transmission control device may be a chip.
In a third aspect, an embodiment of the present application further provides a terminal, where the terminal includes a terminal body and the data transmission control device provided in the second aspect.
In a fourth aspect, an embodiment of the present application further provides a base station, where the base station includes a base station body and the data transmission control device provided in the second aspect.
In a fifth aspect, an embodiment of the present application further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the data transmission control method provided in the first aspect.
Through the technical scheme, the data sending end receives the PDCP status report information sent by the data receiving end to determine the data receiving condition of the data receiving end, and can correct the encryption parameters of the PDCP PDU data packet to be sent or retransmitted subsequently according to the parameters in the PDCP status report information after determining that the parameters in the PDCP status report information are unsuccessfully matched with the current sending state of the PDCP sending end, thereby realizing data recovery.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a diagram illustrating a conventional encryption and decryption method for PDCP layer packets;
FIG. 2 is a diagram illustrating a structure of a count value of a PDCP PDU packet;
fig. 3 is a flowchart illustrating an uplink transmission procedure of a DRB when the RLC mode is AM in the prior art;
fig. 4 is a schematic flowchart of a data transmission control method according to an embodiment of the present application;
fig. 5 is a schematic diagram of a setting range of the COUNT value according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of PDCP status report information according to an embodiment of the present application;
fig. 7 is a flowchart of uplink transmission of a DRB when the RLC mode is AM according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a data transmission control device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In a wireless communication system, in order to ensure that Data transmitted over an air interface can be sequentially transmitted to an application layer at a receiving end, a transmitting end allocates sequence numbers to Data packets, and specifically, a Packet Data Convergence Protocol (PDCP) layer configures corresponding COUNT values (COUNTs) for the Data packets according to the sequence of Packet Data units (PDCP PDU) Data packets.
Fig. 2 is a schematic diagram of a COUNT value structure of a PDCP PDU packet, and as shown in fig. 2, the COUNT is 32-bit data composed of a Hyper Frame Number (HFN) of a high bit and a Sequence Number (SN) of a low bit. Wherein, the SN is the sequence number of the PDCP PDU data packet and is carried in the PDCP PDU data packet. The value range of the SN is 0 ^ (SN bit size) -1, wherein the SN bit size represents the bit number occupied by the sequence number in the PDCP PDU.
In order to protect the user data from being tampered or monitored, the user data is generally encrypted and transmitted, and the receiving end decrypts the data according to the protocol after receiving the data. During the process of encrypting and decrypting the data packet of the PDCP layer, the data packet is encrypted by COUNT and KEY (KEY, which are maintained by the sending end and the receiving end of the PDCP layer and are the same) stored locally at the sending end, BEARER (BEARER Number for carrying user data), direct (data DIRECTION, uplink value is 0, downlink value is 1), LENGTH (data LENGTH), EEA (EUTRAN encryption algorithm)/NEA (NR encryption algorithm), and the packet header carries a Sequence Number (PDCP SN) (Sequence Number) corresponding to the data packet and sends the Sequence Number to the receiving end through an air interface. At the transmitting end, the unencrypted data (such as the plain text block) and the key stream are subjected to and-or operation to obtain encrypted data, and at the receiving end, the encrypted data and the key stream are subjected to and-or operation to obtain data before encryption.
In the data transmission process, a sending end and a receiving end respectively maintain one HFN, and after receiving a PDCP PDU data packet sent by the sending end, the receiving end forms a COUNT for decryption according to SN carried in the PDCP PDU data packet and the HFN locally stored by the receiving end.
In the current NR terminal, during continuous handover or RRC connection reestablishment, the COUNT (the COUNT TX COUNT in the transmission direction and the COUNT RX COUNT in the reception direction) at both sides of the terminal and the base station are not matched. For convenience of description, the process of fig. 3 is illustrated by taking uplink transmission of a DRB with an RLC mode being AM (acknowledged mode) as an example, where the uplink transmission process of the DRB is performed when the RLC mode is AM in the prior art, as shown in fig. 3, the process includes the following stages:
stage 1: the NR radio link is normal.
And (2) stage: some procedures, such as a handover procedure or a Radio Resource Control (RRC) connection reestablishment procedure, are triggered between the base station and the terminal.
and (5) stage: after receiving a PDCP STATUS REPORT sent by a base station, a terminal discards a PDCP SDU already received by a receiving end, and then starts retransmission from a first data packet not acknowledged by RLC (Radio Link Control), and for a sending end, if a received FMC is greater than TX _ NEXT (COUNT used when the sending end assembles a NEXT PDCP PDU to be sent), all PDCP SDUs that have been sent but not acknowledged by RLC are discarded, and a PDCP PDU data packet between TX _ NEXT and FMC-1 with a COUNT value is sent, decryption failure occurs at the receiving end, or is directly discarded; if the FMC is much smaller than the COUNT corresponding to the first RLC unacknowledged PDU from the transmitting end, for example, smaller than the size of a transmission window, then none of the packets need to be discarded, but the subsequently transmitted PDUs may fail to be decrypted at the receiving end.
And 6: after receiving the PDU, the receiving end of the DRB may have two scenarios due to the abnormal variable maintenance of the receiving end:
scene 1: the received PDUs are discarded as deemed not to be within the window based on the SN determination.
Scene 2: the receiving end receives the packet according to RX _ DELIV and SN in PDU, and the COUNT used by the packet for decryption is different from the COUNT used by the transmitting end for performing encryption, thus the decryption failure occurs.
In order to avoid the foregoing scenario 1 and scenario 2, an embodiment of the present application provides a data transmission control method, and fig. 4 is a data transmission control method provided in an embodiment of the present application, as shown in fig. 4, the data transmission control method includes the following steps:
step 401: the PDCP sending end acquires PDCP status report information sent by the PDCP receiving end.
After the PDCP sending end and the PDCP receiving end execute the corresponding procedure, the PDCP receiving end is triggered to report (uplink or downlink) the receiving status.
Step 402: and determining whether the parameters in the PDCP status report information are successfully matched with the current transmission status of the PDCP transmitting end, if so, executing step 403, and if not, executing step 404.
Step 403: and determining that the PDCP receiving end and the PDCP sending end normally communicate, wherein the sending end executes according to the existing standard.
Step 404: and determining that the PDCP receiving end and the PDCP transmitting end are abnormal in communication, and correcting the COUNT used for encrypting the subsequent data packet to be retransmitted or to be transmitted by the PDCP transmitting end according to the parameters in the PDCP status report information.
Fig. 5 is a schematic diagram of a setting range of COUNT values provided in an embodiment of the present application, and as shown in fig. 5, it is specifically determined whether a parameter in the PDCP status report information is successfully matched with a current transmission status of a PDCP sending end by determining whether a COUNT of a data packet indicated in a status report is within a reasonable range of the sending end (for example, the COUNT of any data packet indicated in the status report is not less than a COUNT corresponding to a first data packet that is not acknowledged by an RLC and not greater than a COUNT corresponding to a last PDCP PDU data packet).
In order to overcome the above problem of communication abnormality, the PDCP transmitting end may update the TX _ NEXT to the FMC in the PDCP status report information or the count value of the PDCP PDU packet corresponding to any Bitmap in the PDCP status report information.
After determining that the variable TX _ NEXT of the sending end is not matched with the FMC state, the PDCP sending end can also resend the data which is failed to be sent by the PDCP sending end to the PDCP receiving end according to the protocol. Specifically, the PDCP transmitting end performs transmission from the first PDCP SDU which is not acknowledged by the RLC, and all the to-be-transmitted PDCP SDUs are considered as new PDCP SDUs received from the upper layer according to the standard, and ciphering is performed according to TX _ NEXT. Fig. 6 is a schematic diagram of a PDCP status report information structure according to an embodiment of the present application, and as shown in fig. 6, an FMC of the PDCP status report information indicates a COUNT value of a PDCP PDU packet that is not received by a receiving end of the DRB. Wherein Bitmap: indicating which of the PDCP PDU packets whose COUNT is greater than FMC are lost.
For convenience of describing the technical solution, the process is illustrated by taking a DRB uplink transmission flow with an RLC mode as AM as an example, and fig. 7 is an uplink transmission flow diagram of a DRB when the RLC mode is AM according to an embodiment of the present application, where the flow includes the following stages:
stage 1: the NR radio link is normal.
And (2) stage: triggering a PDCP sending status report between the base station and the terminal, such as a handover procedure or an RRC connection reestablishment procedure.
and (5) stage: after receiving the PDCP STATUS REPORT sent by the base station, the terminal determines whether a STATUS mismatch between the sending end and the receiving end occurs according to a comparison between a variable of the sending end and the FMC, where the checking manner includes, but is not limited to, that a HFN difference between HFN of the FMC and TX _ NEXT is greater than 1, or that a packet COUNT indicated in the STATUS REPORT does not conform to a current STATUS of the PDCP sending entity; at this time, the sending end of the DRB updates TX _ NEXT to the count value of the PDCP PDU packet corresponding to either FMC (the count value of the first PDCP PDU packet that failed to be sent) or Bitmap in the PDCP status report information, and then uses the PDCP SDU that has not been confirmed by the bottom layer from the first as the newly received data from the upper layer, repackages, header compresses, integrity protects, encrypts, and then delivers to the bottom layer. Specifically, the TX _ NEXT of the PDCP transmitting end is updated according to the status report, where the updating includes setting the TX _ NEXT to the COUNT of any received or not received packet indicated in the FMC or the status report. Then the related PDCP transmitting end discards all PDCP PDU data packets, and then the PDCP SDU which is not confirmed by the RLC is regarded as a new data packet obtained from an upper layer, and the new data packet is transmitted according to the protocol.
And 6: since the PDCP sending end adjusts TX _ NEXT in an abnormal situation, there is no PDU drop outside the window or no deciphering failure due to the difference in COUNT used for ciphering and deciphering at the receiving end.
It should be noted that the data transmission control method provided in the present application is not limited to the embodiment described in fig. 7, and the downlink processing and the uplink processing are similar to the above-described flow, except that the transmitting entity is in the base station, and the receiving entity is in the terminal UE.
Fig. 8 is a data transmission control apparatus provided in an embodiment of the present application, and as shown in fig. 8, the apparatus includes a processor 701 and a memory 702, where the memory 702 is configured to store at least one instruction, and the instruction is loaded and executed by the processor 701 to implement the data transmission control method provided in the foregoing embodiment.
In one implementation, the data transmission control apparatus may be a chip, that is, the chip may include a processor 701 and a memory 702, where the memory 702 is configured to store at least one instruction, and the instruction is loaded and executed by the processor 701 to implement the data transmission control method provided by the foregoing embodiment.
The embodiment of the present application further provides a terminal, where the terminal may be, but is not limited to, an NR terminal, and the terminal includes a terminal body and the data transmission control device provided in the embodiment shown in fig. 8. The NR terminal may be a PDCP transmitting end, or a PDCP receiving end, where when the NR terminal is the PDCP transmitting end, a base station communicatively connected to the NR terminal is used as the PDCP receiving end, and otherwise, when the NR terminal is the PDCP receiving end, a base station communicatively connected to the NR terminal is used as the PDCP transmitting end.
In an implementation manner, the NR terminal may have a chip provided in the embodiment shown in fig. 8 built therein, and then the NR terminal having the chip built therein may correct the encryption parameter of the data packet to be retransmitted or to be transmitted subsequently by the transmitting end according to the parameter in the PDCP status report information after determining that the parameter in the PDCP status report information fails to match the current transmission status of the PDCP transmitting end, and implement data recovery after the PDCP transmitting end retransmits the data that has failed to be transmitted to the PDCP receiving end, that is, successfully complete decryption when the COUNT maintained at both ends of the PDCP transmitting end and the PDCP receiving end is consistent, so as to ensure successful data transmission.
The embodiment of the present application further provides a base station, where the base station includes a base station body and the data transmission control device provided in the embodiment shown in fig. 8. When the NR terminal is a PDCP transmitting end, a base station communicatively connected to the NR terminal serves as a PDCP receiving end, and when the NR terminal is a PDCP receiving end, a base station communicatively connected to the NR terminal serves as a PDCP transmitting end.
In an implementation manner, the base station may include the chip provided in the embodiment shown in fig. 8, and then the NR terminal with the chip built therein may correct the ciphering parameter of the data packet to be retransmitted or transmitted subsequently by the transmitting end according to the parameter in the PDCP status report information after determining that the parameter in the PDCP status report information fails to match the current transmission status of the PDCP transmitting end, and implement data recovery after the PDCP transmitting end retransmits the data that has failed to be transmitted to the PDCP receiving end, that is, successfully complete decryption when the COUNT maintained at both ends of the PDCP transmitting end and the PDCP receiving end is consistent, so as to ensure successful data transmission.
The embodiment of the present application further provides a computer storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the data transmission control method provided by the above embodiment.
It should be understood that the application may be an application program (native app) installed on the terminal, or may also be a web page program (webApp) of a browser on the terminal, which is not limited in this embodiment of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions in actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a Processor (Processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (11)
1. A data transmission control method, characterized in that the method comprises:
the PDCP sending end acquires PDCP status report information sent by the PDCP receiving end; and
and if the parameters in the PDCP status report information are determined to be unsuccessfully matched with the current sending status of the PDCP sending terminal, correcting the encryption parameters of the PDCP PDU data packet to be sent or retransmitted by the sending terminal according to the parameters in the PDCP status report information so as to obtain the corrected encryption parameters.
2. The method as claimed in claim 1, wherein before the failure of the determining that the parameter in the PDCP status report information matches the current transmission status of the PDCP transmitting end, further comprising:
determining whether the parameters in the PDCP status report information are successfully matched with the current sending status of the PDCP sending end;
and if the matching is successful, determining that the PDCP sending end and the PDCP receiving end communicate normally according to the matching result.
3. The method according to claim 1 or 2, wherein the parameters in the PDCP status report information include a count value of a first non-received PDCP PDU packet at the PDCP receiving end and reception information of a subsequent PDU of the first non-received PDCP PDU packet;
the current sending state of the PDCP sending end comprises the count value of the next PDCP PDU data packet to be sent of the PDCP sending end and the information of the PDCP PDU data packet waiting for the control confirmation of the wireless link at present.
4. The method as claimed in claim 2, wherein the determining whether the parameter in the PDCP status report information matches the current transmission status of the PDCP transmitting end successfully comprises:
determining whether one or more indicated count values of the PDCP PDU data packets in the PDCP status report information fall into a set count value range, wherein the set count value range is an interval range which is not less than a count value corresponding to a first PDCP PDU data packet which is not confirmed by radio link control and is not more than a count value corresponding to a last sent PDCP PDU data packet;
and if the number of the matched objects falls into the range of the set counting value, the matching is successful, and if the number of the matched objects does not fall into the range of the set counting value, the matching is failed.
5. The method as claimed in claim 3, wherein the modifying the ciphering parameter of the PDCP PDU packet to be sent or retransmitted by the sending end according to the parameter in the PDCP status report message comprises:
updating the count value of the first PDCP PDU data packet to be transmitted or retransmitted subsequently by the PDCP transmitting end to the count value of the first PDCP PDU data packet which is failed to be transmitted or retransmitted by the transmitting end or the count value of the PDCP PDU data packet corresponding to any Bitmap in the PDCP status report information; wherein, the count value of the current PDCP PDU data packet to be sent or retransmitted is sequentially accumulated by 1 according to the count value of the previous PDCP PDU data packet.
6. The method as claimed in claim 3, wherein after the determining that the parameter in the PDCP status report information fails to match the current transmission status of the PDCP transmitting end, the method further comprises:
determining a PDCP SDU which fails to be sent by the PDCP sending end according to the current sending state of the PDCP sending end;
reconstructing the PDCP SDU which fails to be sent into a new PDCU PDU according to the corrected encryption parameters;
and recombining a new PDCU PDU to be sent to the PDCP receiving end according to the corrected encryption parameter.
7. The method as claimed in claim 6, wherein the determining that the PDCP transmitting end has failed to transmit the PDCP SDU according to the current transmission status of the PDCP transmitting end comprises:
and after determining that the parameters in the PDCP status report information are matched with the current sending status of the PDCP sending end and fail, judging that the data packets of the PDCP PDUs waiting for the radio link control confirmation are all sent unsuccessfully, and judging that the PDCP SDUs corresponding to the data packets of the PDCP PDUs waiting for the radio link control confirmation are all sent unsuccessfully.
8. A data transmission control apparatus, characterized in that the apparatus comprises:
a processor and a memory for storing at least one instruction which is loaded and executed by the processor to implement the data transmission control method of any one of claims 1 to 7.
9. A terminal, characterized in that the terminal comprises: the data transmission control apparatus of claim 8.
10. A base station, characterized in that the base station comprises: the data transmission control apparatus of claim 8.
11. A computer storage medium on which a computer program is stored, which computer program, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110183614.8A CN112996052B (en) | 2021-02-08 | 2021-02-08 | Data transmission control method and device, terminal, base station and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110183614.8A CN112996052B (en) | 2021-02-08 | 2021-02-08 | Data transmission control method and device, terminal, base station and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112996052A true CN112996052A (en) | 2021-06-18 |
| CN112996052B CN112996052B (en) | 2023-01-31 |
Family
ID=76392984
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110183614.8A Active CN112996052B (en) | 2021-02-08 | 2021-02-08 | Data transmission control method and device, terminal, base station and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112996052B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023000876A1 (en) * | 2021-07-19 | 2023-01-26 | 大唐移动通信设备有限公司 | Data transmission method and apparatus, base station, and terminal |
| WO2024032742A1 (en) * | 2022-08-11 | 2024-02-15 | 展讯通信（上海）有限公司 | Service processing method and apparatus, device, storage medium, and program product |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101132261A (en) * | 2006-08-21 | 2008-02-27 | 华为技术有限公司 | Data package retransmission method and system thereof |
| CN102833050A (en) * | 2007-09-11 | 2012-12-19 | Lg电子株式会社 | Method for transmitting status report of PDCP layer and receiver |
| WO2015192322A1 (en) * | 2014-06-17 | 2015-12-23 | 华为技术有限公司 | Radio resource scheduling method and apparatus |
| CN111262660A (en) * | 2018-11-30 | 2020-06-09 | 华为技术有限公司 | Data transmission method, equipment and system |
-
2021
- 2021-02-08 CN CN202110183614.8A patent/CN112996052B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101132261A (en) * | 2006-08-21 | 2008-02-27 | 华为技术有限公司 | Data package retransmission method and system thereof |
| CN102833050A (en) * | 2007-09-11 | 2012-12-19 | Lg电子株式会社 | Method for transmitting status report of PDCP layer and receiver |
| WO2015192322A1 (en) * | 2014-06-17 | 2015-12-23 | 华为技术有限公司 | Radio resource scheduling method and apparatus |
| US20170099128A1 (en) * | 2014-06-17 | 2017-04-06 | Huawei Technologies Co., Ltd. | Radio resource scheduling method and apparatus |
| CN111262660A (en) * | 2018-11-30 | 2020-06-09 | 华为技术有限公司 | Data transmission method, equipment and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023000876A1 (en) * | 2021-07-19 | 2023-01-26 | 大唐移动通信设备有限公司 | Data transmission method and apparatus, base station, and terminal |
| WO2024032742A1 (en) * | 2022-08-11 | 2024-02-15 | 展讯通信（上海）有限公司 | Service processing method and apparatus, device, storage medium, and program product |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112996052B (en) | 2023-01-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7116667B2 (en) | Determination of acceptable sequence number ranges in a communications protocol | |
| KR101392697B1 (en) | Method for detecting security error in mobile telecommunications system and device of mobile telecommunications | |
| KR100673515B1 (en) | Method for on-line recovery of parameter synchronization for ciphering applications | |
| US7388883B2 (en) | Abnormal case handling for acknowledged mode transmission and unacknowledged mode transmission | |
| JP5279732B2 (en) | PDCP layer status report transmission method and receiver in mobile communication system | |
| EP2136501B1 (en) | Method of delivering a PDCP data unit to an upper layer | |
| US7940770B2 (en) | Reception device, transmission device, communication system and associated methodology for data transmission re-establishment through a lower layer of a transmission protocol | |
| EP1928130A2 (en) | Apparatuses and methods for performing initialization of the Packet Data Convergence Protocol PDCP in a mobile communication system | |
| US20140112157A1 (en) | Method and apparatus for sending packet, updating and maintaining hyper frame number, and processing data | |
| EP3443697B1 (en) | Apparatuses and methods for using arq processes in a relay device | |
| CN106797376B (en) | Method and apparatus for handling packet loss in mobile communication network | |
| KR20050071672A (en) | Transmission of data packets in containers | |
| JP2006506000A (en) | Data packet transmission in a single container | |
| CN112996052B (en) | Data transmission control method and device, terminal, base station and medium | |
| CN111865820A (en) | Data transmission method, data transmission device, receiving end, communication system, device and medium | |
| US20080101608A1 (en) | Method and apparatus for handling protocol error in a wireless communications system | |
| WO2024032742A1 (en) | Service processing method and apparatus, device, storage medium, and program product | |
| US20080137574A1 (en) | Method and apparatus for handling data delivery in a wireless communications system | |
| US20080148111A1 (en) | Method and apparatus for recovering protocol error in a wireless communications system | |
| CN111769914B (en) | Data communication method and storage medium | |
| EP1510017B1 (en) | Synchronizing method and apparatus using error detection of sequence numbers to avoid synchronizing failure | |
| CN112333850B (en) | Method for preventing downlink desynchronization, communication device and readable storage medium | |
| US20080137687A1 (en) | Method and apparatus for handling reordering in a wireless communications system | |
| KR100856244B1 (en) | apparatus and method transmitting/receiving ARQ packet in mobile telecommunication system | |
| KR20080044148A (en) | Apparatus and method for pdcp reset in mobile telecommunication system |
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 |