CN113472683A

CN113472683A - Data discarding method and device, terminal and storage medium

Info

Publication number: CN113472683A
Application number: CN202110839105.6A
Authority: CN
Inventors: 白伟华
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-07-23
Filing date: 2021-07-23
Publication date: 2021-10-01
Also published as: WO2023000827A1

Abstract

The embodiment of the application discloses a data discarding method, a data discarding device, a terminal and a storage medium, and belongs to the technical field of communication. The method comprises the following steps: setting a timeout timestamp for the PDCP SDU; reading the description information of the PDCP SDU in the DRB queue in response to the condition of overtime detection being met, wherein the description information comprises an overtime time stamp corresponding to the PDCP SDU; discarding the PDCP SDUs in response to the time-out timestamp indicating a time-out of the PDCP SDUs. By adopting the scheme provided by the embodiment of the application, a discarding timer is not required to be set for the PDCP SDU, so that a large number of discarding timers are prevented from occupying a large number of processing resources, the overtime discarding process of the PDCP SDU is simplified, and the complexity of problem detection and maintenance of a communication system is facilitated to be reduced.

Description

Data discarding method and device, terminal and storage medium

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a data discarding method, a data discarding device, a terminal and a storage medium.

Background

A Packet Data Convergence Protocol (PDCP) entity is located in a second layer of the Radio interface Protocol stack, and is configured to process a Radio Resource Control (RRC) message on a Control plane and an Internet Protocol (IP) Data Packet of a user plane.

On the user plane, after receiving a PDCP Service Data Unit (SDU) from an upper layer, the PDCP entity needs to configure an associated discard timer (discard) for each PDCP SDU. When the discard timer expires, the PDCP entity discards the PDCP SDU. If a PDCP Protocol Data Unit (PDU) corresponding to the PDCP SDU is sent to the bottom layer, the PDCP entity further needs to notify the bottom layer to discard the PDCP PDU.

Disclosure of Invention

The embodiment of the application provides a data discarding method, a data discarding device, a terminal and a storage medium. The technical scheme is as follows:

in one aspect, an embodiment of the present application provides a data discarding method, where the method includes:

setting a timeout timestamp for the PDCP SDU;

reading description information of the PDCP SDU in a Data Radio Bearer (DRB) queue in response to the condition of timeout detection being met, wherein the description information comprises the timeout timestamp corresponding to the PDCP SDU;

discarding the PDCP SDUs in response to the timeout timestamp indicating that the PDCP SDUs are timed out.

In another aspect, an embodiment of the present application provides a data discarding apparatus, where the apparatus includes:

the setting module is used for setting a timeout timestamp for the PDCP SDU;

a reading module, configured to read description information of the PDCP SDU in a DRB queue in response to a timeout detection condition being met, where the description information includes the timeout timestamp corresponding to the PDCP SDU;

a discarding module, configured to discard the PDCP SDU in response to the timeout timestamp indicating that the PDCP SDU is out of time.

In another aspect, an embodiment of the present application provides a terminal, where the terminal includes a processor and a memory, where the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the data discarding method according to the above aspect.

In another aspect, an embodiment of the present application provides a computer-readable storage medium, in which at least one program code is stored, and the program code is loaded and executed by a processor to implement the data discarding method according to the above aspect.

In another aspect, embodiments of the present application provide a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the data discarding method provided in the various alternative implementations of the above aspects.

The technical scheme provided by the embodiment of the application can bring the following beneficial effects:

in the embodiment of the application, the overtime time stamp is set for the PDCP SDU, and when the overtime detection condition is met, the description information of the PDCP SDU is obtained from the DRB queue, so that whether the PDCP SDU is overtime or not is determined based on the overtime time stamp in the description information, and the overtime PDCP SDU is discarded; by adopting the scheme provided by the embodiment of the application, a discarding timer is not required to be set for the PDCP SDU, so that a large number of discarding timers are prevented from occupying a large number of processing resources, the overtime discarding process of the PDCP SDU is simplified, and the complexity of problem detection and maintenance of a communication system is facilitated to be reduced.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a system architecture diagram of a communication system provided by an exemplary embodiment of the present application;

fig. 2 is a schematic diagram of a protocol architecture of a user plane and a control plane;

FIG. 3 illustrates a flow chart of a data discard method provided by an exemplary embodiment of the present application;

FIG. 4 illustrates a flow chart of a data discard method provided by another exemplary embodiment of the present application;

FIG. 5 is a schematic diagram of an implementation of the data discarding method shown in FIG. 4;

fig. 6 is a diagram illustrating an interaction procedure between an upper layer, a PDCP entity, and a MAC layer according to an exemplary embodiment;

FIG. 7 illustrates a flow chart of a data discard method provided by another exemplary embodiment of the present application;

FIG. 8 is a schematic diagram of an implementation of the data discard method of FIG. 7;

fig. 9 is a block diagram illustrating a structure of a data discarding apparatus according to an embodiment of the present application;

fig. 10 shows a schematic structural diagram of a terminal according to an exemplary embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Referring to fig. 1, a schematic diagram of a communication system according to an embodiment of the present application is shown. The communication system may include: access network 12 and terminal 14.

Several network devices 120 are included in access network 12. Network device 120 may be a base station, which is a device deployed in an access network to provide wireless communication functionality for terminals. The base stations may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different radio access technologies, the names of devices with base station functionality may differ, for example in LTE systems, called eNodeB or eNB; in a 5G NR-U system, it is called gNodeB or gNB. The description of "base station" may change as communication technology evolves. For convenience of this embodiment, the above-mentioned devices providing wireless communication function for the terminal 14 are collectively referred to as network devices.

The terminal 14 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication capability, as well as various forms of user equipment, Mobile Stations (MSs), terminals (terminal devices), and so forth. For convenience of description, the above-mentioned devices are collectively referred to as a terminal. The network device 120 and the terminal 14 communicate with each other via some air interface technology, such as a Uu interface.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile Communication (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, a LTE Frequency Division Duplex (FDD) System, a LTE Time Division Duplex (TDD) System, an Advanced Long Term Evolution (LTE-A) System, a New wireless (New Radio, NR) System, an Evolution System of an NR System, an LTE-based Access (LTE-to-non-licensed) System, a UMTS-based Access (UMTS-to-non-licensed) System, a UMTS-based Universal Mobile Communication (UMTS-to-Universal Mobile Access, UMTS) System, WiMAX) communication system, Wireless Local Area Network (WLAN), Wireless Fidelity (WiFi), next generation communication system, or other communication system.

Generally, the conventional Communication system supports a limited number of connections and is easy to implement, however, with the development of Communication technology, the mobile Communication system will support not only conventional Communication but also, for example, Device-to-Device (D2D) Communication, Machine-to-Machine (M2M) Communication, Machine Type Communication (MTC), Vehicle-to-Vehicle (V2V) Communication, and Vehicle networking (V2X) system, etc. The embodiments of the present application can also be applied to these communication systems.

Taking LTE system as an example, the protocol architecture of the user plane and the control plane is shown in fig. 2.

Radio Resource Control (RRC): the method is used for managing, controlling and scheduling the wireless resources, fully utilizes the limited wireless network resources as far as possible under the condition of meeting the requirement of service quality, and enlarges the capacity of a communication system.

PDCP: for IP header compression to reduce the number of bits transmitted over the radio interface. The header compression mechanism is based on a robust header compression (ROHC) algorithm, which is also applicable to standardized header compression for other mobile communication technologies. PDCP is also responsible for ciphering of the control plane, integrity protection of the transmitted data, and in-sequence sending and deduplication for handover. At the receiving end, the PDCP protocol performs the corresponding decryption and decompression operations. Each Radio Bearer (RB) of the terminal configures one PDCP entity.

Radio Link Control (RLC): responsible for segmentation/concatenation, retransmission control, duplicate detection and sequence delivery to higher layers. The RLC serves the PDCP. One RLC entity is configured for each radio bearer of the terminal.

Media Access Control (MAC): for controlling multiplexing of logical channels, hybrid Automatic Repeat-reQuest (ARQ) retransmissions, scheduling of uplink and downlink. For the uplink and downlink, the scheduling function is located at the base station. The hybrid ARQ protocol portion is located at the end of the transmission and reception of the MAC protocol. The MAC provides services for the RLC in the form of logical channels.

Physical layer (PHY): for managing coding/decoding, modulation/demodulation, mapping of multiple antennas, and other types of physical layer functions. The physical layer provides services to the MAC layer in the form of transport channels.

In the related art, when the PDCP entity receives PDCP SDUs from the upper layer and configures a timeout mechanism, it needs to configure an associated discard timer for the PDCP PDU and start the discard timer. Upon expiration of the discard timer, the PDCP entity discards the PDCP SDU associated with the discard timer. If the PDCP PDU (obtained after adding the PDCP header to the header of the PDCP SDU) corresponding to the PDCP SDU is delivered to the bottom layer, the PDCP entity needs to notify the bottom layer to discard the PDCP PDU.

As can be seen, the related art implements timeout management by setting a discard timer. However, since it takes a certain processing resource to start the discard timer and the management timer, when there are a large number of PDCP SDUs, it needs to take a large amount of processing resource to implement timeout management. Moreover, for the overtime PDCP PDU sent to the bottom layer, the procedure of overtime discarding by the bottom layer is tedious, which results in higher complexity of problem detection and maintenance of the communication system.

In order to simplify the data discarding process, in the embodiment of the present application, the PDCP entity does not need to configure a relevant discarding timer for the PDCP SDU, but adds a timeout timestamp in the description information of the PDCP SDU, and when timeout detection is needed, reads the description information of the PDCP SDU in the DRB queue, and performs timeout detection based on the timeout timestamp in the description information, so that when the PDCP SDU is detected to be timeout, the PDCP SDU is discarded. In the whole data discarding process, a discarding timer is not required to be configured for the PDCP SDU, so that the starting and management of the timer are avoided from occupying processing resources, the data discarding process is simplified, and the complexity of problem detection and maintenance of a communication system is favorably reduced.

Referring to fig. 3, a flowchart of a data discarding method according to an exemplary embodiment of the present application is shown, where the present embodiment takes the method as an example for being used in a terminal in the communication system shown in fig. 1, and the method includes:

step 301, setting a time-out time stamp for the PDCP SDU.

In a possible implementation manner, when the PDCP entity receives a PDCP SDU sent by an upper layer and the PDCP entity is provided with a timeout mechanism, a corresponding timeout timestamp (expirytts) is set for the PDCP SDU, where the timeout timestamp is used to indicate a timeout point of the PDCP SDU.

Step 302, in response to the condition of timeout detection being satisfied, reading the description information of the PDCP SDU in the DRB queue, where the description information includes a timeout timestamp corresponding to the PDCP SDU.

The timeout detection condition is a condition that needs to be satisfied when the timeout detection is triggered. Alternatively, the timeout detection condition may be triggered by an external device (such as an access network device), or by the terminal itself.

In a possible implementation manner, when the access network equipment indicates that uplink data can be sent, the terminal determines that a timeout detection condition is met; or, when the timeout detection period is reached, the terminal determines that the timeout detection condition is satisfied.

In the embodiment of the application, the timeout timestamp is added to the description information of the PDCP SDU, and the description information of the PDCP SDU is stored in a DRB Queue (DRB Queue) in sequence (according to the sequence of receiving the PDCP SDU). Optionally, after the terminal sets the timeout timestamp for the PDCP SDU, the description information including the timeout timestamp is added to the DRB queue, and the description information enqueuing operation is completed.

The terminal is provided with at least one DRB queue, and different DRB queues are used for storing the description information of PDCP SDUs corresponding to different PDCP entities.

Optionally, the description information may further include a data length and a data address of the PDCP SDU, in addition to the timeout timestamp. Of course, the description information may also include other information besides the above information, and the specific content included in the description information is not limited in this embodiment.

In some embodiments, each DRB queue is provided with a write index (write index) and a read index (readindex), the write index is used to indicate a write position of the description information, and after the description information is written into the DRB queue, the position of the write index changes; the read index is used for indicating the reading position of the description information, and the position of the read index changes after the description information is read from the DRB queue.

In a possible implementation manner, when a timeout detection condition is met, the terminal reads the description information of the PDCP SDU according to the position of the read index in the DRB queue; after setting the time-out time stamp for the PDCP SDU, the terminal writes the description information into the DRB queue according to the position of the written index in the DRB queue.

Step 303, in response to the time-out timestamp indicating that the PDCP SDU is time-out, discards the PDCP SDU.

After reading the overtime time stamp of the PDCP SDU, the terminal detects whether the PDCP SDU is overtime or not based on the overtime time stamp, if so, the PDCP SDU is discarded, wherein the discarded PDCP SDU cannot be sent to a bottom layer.

In a possible implementation manner, the terminal acquires the current time, detects whether the timeout timestamp is less than the current time, and determines that the PDCP SDU is out of time if the timeout timestamp is less than the current time; if so, determining that the PDCP SDU is not overtime. For example, when the timeout timestamp is 16254747887060 (in ms) and the current time is 1625474788759, the terminal determines that the PDCP SDU times out.

Optionally, if the timeout timestamp indicates that the PDCP SDU is not timeout, the terminal sends uplink data based on the PDCP SDU, or continues to store the PDCP SDU.

In summary, in the embodiment of the present application, by setting the timeout timestamp for the PDCP SDU and acquiring the description information of the PDCP SDU from the DRB queue when the timeout detection condition is satisfied, it is determined whether the PDCP SDU is timeout based on the timeout timestamp in the description information, and the timeout PDCP SDU is discarded; by adopting the scheme provided by the embodiment of the application, a discarding timer is not required to be set for the PDCP SDU, so that a large number of discarding timers are prevented from occupying a large number of processing resources, the overtime discarding process of the PDCP SDU is simplified, and the complexity of problem detection and maintenance of a communication system is facilitated to be reduced.

In a possible implementation manner, in order to avoid uplink data blocking caused by the PDCP SDU being overtime, when uplink data needs to be sent, the terminal determines that a timeout detection condition is satisfied, and performs timeout detection based on a timeout timestamp of the PDCP SDU. Referring to fig. 4, a flowchart of a data discarding method according to another exemplary embodiment of the present application is shown, where the present embodiment takes the method as an example for being used in the terminal in the communication system shown in fig. 1, and the method includes:

step 401, in response to the PDCP entity receiving the timestamp setting notification sent by the upper layer, obtaining the configured timeout duration, where the timestamp setting notification is sent when the upper layer receives the IP data packet.

In one possible implementation, after receiving the IP packet, the upper layer (upper layer) writes the IP packet into the buffer, and sends a timestamp setting notification to the PDCP entity, instructing the PDCP entity to set a timeout timestamp for the PDCP SDU (representation of the IP packet at the PDCP entity).

Since the terminal sets different PDCP entities for different radio bearers, the upper layer needs to determine the PDCP entity corresponding to the radio bearer to which the IP packet belongs, and thus sends a timestamp setting notification to the determined PDCP entity.

Optionally, when the upper layer notifies the PDCP entity to set the timeout timestamp, it needs to determine whether the PDCP entity configures a timeout mechanism, and when the PDCP entity configures the timeout mechanism, sends a timestamp setting notification to the PDCP entity. Correspondingly, after receiving the timestamp setting notification, the PDCP entity obtains the configured timeout duration.

Wherein, the configured timeout durations of different PDCP entities may be the same or different. For example, for radio bearer a, the configured timeout duration corresponding to the PDCP entity is 500ms, and for radio bearer B, the configured timeout duration corresponding to the PDCP entity is 400ms, which is not limited in this embodiment of the present application.

Illustratively, as shown in fig. 5, after receiving the IP packet, the upper layer 51 writes the IP packet into an L3buffer (in the form of PD), and sends a timestamp setting notification to the PDCP entity 52.

Step 402, setting a time-out time stamp for the PDCP SDU by the PDCP entity based on the current time and the time-out duration.

And after receiving the time stamp setting notice, the PDCP entity determines the time-out time point of the PDCP SDU according to the time-out duration and the current time configured by the PDCP entity, and further sets the time-out time stamp for the PDCP SDU. Wherein, the timeout timestamp is the current time + the timeout duration.

In an illustrative example, if the current time is 1625474788759 and the timeout timestamp is 500ms, the timeout timestamp of the PDCP SDU is 1625474789259.

In a possible implementation manner, after the PDCP entity sets a timeout timestamp for the PDCP SDU, the timeout timestamp is used as a part of description information of the PDCP SDU, and the description information is written into a DRB queue corresponding to the PDCP entity, so that the description information is queued. Wherein, each time the enqueue is completed, the PDCP entity needs to update the index position of the write index in the DRB queue.

Illustratively, as shown in fig. 5, after receiving the notification, the PDCP entity 52 reads the L3buffer, sets a timeout timestamp for the PDCP SDU, and writes the description information containing the timeout timestamp into the corresponding DRB queue. In fig. 5, n DRB queues are provided, and the PDCP entity 52 writes the description information into its corresponding DRB queue of the n DRB queues.

Step 403, in response to the MAC layer receiving the uplink authorization information, reading description information of the PDCP SDU in the DRB queue, where the description information includes a timeout timestamp corresponding to the PDCP SDU.

When the network side allows the terminal to transmit uplink data, uplink grant information (UL grant) is transmitted to the terminal, and accordingly, the terminal can transmit the uplink data based on the uplink grant information. In order to avoid the uplink data transmission of overtime data blocking, when the MAC layer receives the uplink authorization information and needs to perform PDCP SDU reading processing, firstly performing overtime detection on the PDCP SDU; if the PDCP SDU is overtime, discarding; and if the PDCP SDU is not overtime, carrying out uplink data transmission based on the PDCP SDU.

Because the terminal is simultaneously provided with a plurality of DRB queues (corresponding to different radio bearers), in order to ensure accuracy of timeout detection, after receiving the uplink authorization information, the terminal first needs to determine a target radio bearer and ensure that the subsequent description information of the PDCP SDU is accurately read from the DRB queue corresponding to the target radio bearer.

In a possible implementation manner, in response to receiving the uplink grant information by the MAC layer, the terminal determines a target DRB queue corresponding to a target logical channel (logical channel) from the at least one DRB queue, where the target logical channel is a logical channel for receiving the uplink grant information, and further reads description information of PDCP SDUs in the target DRB queue.

Optionally, a read index is set in the target DRB queue, and the terminal reads the description information from the target DRB queue based on the read index.

Illustratively, as shown in fig. 5, after receiving the uplink grant information, the MAC layer 53 determines that the target DRB queue is a DRB queue n, and then reads the description information from the DRB queue n in sequence (i.e., the description information is dequeued).

It should be noted that, because different logical channels have different priorities, when receiving uplink grant information through multiple logical channels, the terminal preferentially performs timeout detection on the DRB queue corresponding to the high-priority logical channel. In some embodiments, both the PDCP entity and the MAC layer have a read-write permission of the DRB queue, and after receiving the uplink authorization information, an LCP (Logical channel priority) module of the MAC layer reads the description information based on the Logical channel priority and performs timeout detection.

The terminal detects whether the time is overtime based on the time stamp of the PDCP SDU, if so, the step 404 is executed, and if not, the step 405 is executed.

Step 404, in response to the time-out timestamp indicating that the PDCP SDU is time-out, discarding the PDCP SDU.

In one possible embodiment, the description information includes a data address and a data length of the PDCP SDU in addition to the timeout timestamp, and the discarding of the PDCP SDU by the terminal may include the following steps.

Firstly, acquiring the data address and the data length of the PDCP SDU from the description information.

When determining that the PDCP SDU is overtime, the terminal further acquires a data address and a data length from the description information of the PDCP SDU so as to release the storage space in the following process. In some embodiments, the data address is a start address of the PDCP SDU in the buffer, and based on the data address and the data length, an end address of the PDCP SDU in the buffer can be determined.

And secondly, based on the data address and the data length, releasing the storage space occupied by the PDCP SDU.

And the terminal deletes the PDCP SDU from the buffer memory based on the data address and the data length, thereby releasing the storage space for writing new PDCP SDU in a subsequent process.

And thirdly, removing the description information of the PDCP SDU from the DRB queue.

Meanwhile, the terminal removes the description information of the expired PDCP SDU from the DRB queue so as to write the description information of the newly received PDCP SDU in the following.

Because the description information in the DRB queue is arranged in sequence, after detecting that the current PDCP SDU is overtime, the terminal continues to read the next description information from the DRB queue and repeatedly executes the overtime detection procedure.

In some embodiments, when the DRB queue is provided with the read index, the terminal needs to update the position of the read index, and the subsequent timeout detection starts from the updated position of the read index.

Step 405, responding to the time-out timestamp indicating that the PDCP SDU is not time-out, performing data processing on the PDCP SDU, and sending the processed data.

And when the PDCP SDU is not overtime, the terminal further performs data processing before sending the PDCP SDU and further sends the processed data. The data processing before transmission includes adding a PDCP header (performed by the PDCP entity), adding an RLC header (performed by the RLC entity), adding a MAC header (performed by the MAC layer), and the like, which is not limited in this embodiment.

Illustratively, as shown in fig. 5, when the PDCP SDU is not timed out, the terminal performs data processing such as ciphering on the PDCP SDU, so as to send the processed data to a transmitter buffer (TXbuffer) for subsequent data transmission.

Because the description information in the DRB queue is arranged in sequence, after detecting that the current PDCP SDU is not overtime, the terminal does not need to execute the above overtime detection procedure, and directly transmits data based on the PDCP SDU (still needing to read the description information, and read the PDCP SDU based on the data address and data length in the description information).

In an illustrative example, when the above-described data discarding method is implemented, the interaction procedure between the upper layer, the PDCP entity, and the MAC layer in the terminal is as shown in fig. 6.

Step 601, the upper layer writes the IP data packet into L3 buffer.

In step 602, the upper layer notifies the PDCP entity to perform timestamp setting.

In step 603, the PDCP entity reads the L3buffer, and calculates a time-out timestamp of the PDCP SDU based on the configured time-out duration and the current time.

In step 604, the PDCP entity writes the description information containing the timeout timestamp into the target DRB queue and updates the write index of the DRB queue.

In step 605, the MAC layer receives the UL grant.

Step 606, the MAC layer reads the target DRB queue and detects whether the PDCP SDU is overtime based on the timeout timestamp in the description information. If the time is out, step 607 is executed, and if the time is not out, step 608 is executed.

In step 607, the MAC layer discards the PDCP SDU, releases the L3buffer occupied by the PDCP SDU, and updates the read index.

Step 608, the MAC layer reads the non-overtime PDCP SDU and sends it to the bottom layer for uplink data transmission.

In this embodiment, when receiving the uplink authorization information and preparing to send uplink data, the description information in the DRB queue is read, and whether the PDCP SDU is overtime is detected based on the timeout timestamp in the description information, so that automatic discarding of the overtime PDCP SDU and normal uplink transmission of the non-overtime PDCP SDU are achieved, a discard timer is not required, and processing resources are saved.

In a possible scenario, when the terminal does not receive the uplink authorization information for a long time due to poor link quality or bottom layer error, the scheme for performing timeout detection based on the uplink authorization information cannot be executed, so that a large number of timeout PDCP SDUs cannot be discarded in time. In order to avoid the occurrence of data backlog due to timeout in such a scenario, in a possible implementation, the terminal may set a common check timer for each DRB queue, so as to trigger timing timeout detection by using the detection timer. The following description will be made using exemplary embodiments.

Referring to fig. 7, a flowchart of a data discarding method according to another exemplary embodiment of the present application is shown, where the present embodiment takes the method as an example for being used in the terminal in the communication system shown in fig. 1, and the method includes:

step 701, in response to the PDCP entity receiving the timestamp setting notification sent by the upper layer, obtaining the configured timeout duration, where the timestamp setting notification is sent when the upper layer receives the IP data packet.

Step 702, setting a time-out time stamp for the PDCP SDU by the PDCP entity based on the current time and the time-out duration.

The implementation of steps 701 to 702 can refer to steps 401 to 402, and this embodiment is not described herein again.

Illustratively, as shown in fig. 8, after receiving the IP packet, the upper layer 81 writes the IP packet into the L3buffer, and sends a timestamp setting notification to the PDCP entity 82. After receiving the notification, the PDCP entity 82 reads the L3buffer, sets a timeout timestamp for the PDCP SDU, and writes the description information containing the timeout timestamp into the corresponding DRB queue.

And step 703, reading the description information of the PDCP SDU in the DRB queue in response to the check timer reaching the time length of the timer, where the description information includes an timeout timestamp corresponding to the PDCP SDU, and the time length of the timer is less than the time length configured by the PDCP entity.

In this embodiment, the PDCP entities configured with the timeout mechanism share a common check timer, where the check timer is used to trigger periodic detection of whether timeout data exists in a DRB queue corresponding to the PDCP entity, and discard the timeout data.

In a possible embodiment, the timer duration of the check timer is less than the timeout duration configured by any PDCP entity, and the timer duration needs to be set to be too small to avoid timing detection too frequently. For example, the duration of the timer is not less than one tenth of the timeout duration.

Different from the time-out detection triggered by the uplink authorization information aiming at a specific DRB, the time-out detection triggered by the check timer aims at all DRBs needing time-out detection. Therefore, in a possible implementation manner, in response to that the check timer reaches the time length of the timer, the terminal determines a target DRB queue corresponding to a target PDCP entity, where the target PDCP entity is a PDCP entity configured with a timeout mechanism, and further reads description information of PDCP SDUs in each target DRB queue.

Optionally, the terminal may read the description information in each target DRB queue in order based on the priority of the logical channel, which is not limited in this embodiment.

Illustratively, as shown in fig. 8, when n DRB queues are set in the terminal and the PDCP entity corresponding to each DRB queue is provided with an timeout mechanism, when the check timer reaches the duration of the timer, the MAC layer 83 (or other modules in the terminal) reads the description information in the n DRB queues and performs timeout detection.

Step 704, in response to the time-out timestamp indicating that the PDCP SDU is time-out, discarding the PDCP SDU.

Similar to the step 404, when the PDCP SDU times out, the terminal discards the PDCP SDU (refer to the step 404). In a possible implementation manner, if the current PDCP SDU is overtime, the terminal continues to read the next piece of description information in the DRB queue and updates the read index of the DRB queue until the time-out detection is stopped when the current PDCP SDU is not overtime.

Illustratively, as shown in fig. 8, the MAC layer 83 discards the timed-out PDCP SDUs, and the non-timed-out PDCP SDUs are continuously stored in the DRB queue, and uplink transmission is performed while waiting for the UL grant.

Step 705, restart the check timer.

In one possible implementation, after each DRB queue completes the timeout detection, the terminal restarts the check timer for the next round of timing detection.

In some embodiments, the timer duration of the check timer is a fixed value, and the terminal starts the check timer according to the fixed timer duration each time. For example, the timer duration is 50 ms.

In other embodiments, the timer duration of the timer is checked to be a dynamic value, and the terminal may dynamically adjust the timer duration according to the real-time data transmission condition.

In a possible implementation manner, the terminal adjusts the duration of the timer based on a target parameter, where the target parameter includes at least one of an uplink grant frequency, an uplink transmission rate, and a data buffer size.

When the uplink frequency is higher or the uplink sending rate is faster, it indicates that the uplink data transmission channel state is better, and in order to avoid frequent periodic detection, a longer timer duration may be set, that is, the timer duration has a positive correlation with the uplink grant frequency and the uplink sending rate; on the contrary, when the data buffer of the terminal is larger, it indicates that the uplink speed of the data is slower, and uplink data blocking is easy to occur, so that a shorter timer duration can be set so as to clear the overtime data in time, that is, the timer duration and the data buffer size present a negative correlation.

Of course, the terminal may also dynamically adjust the duration of the timer based on other parameters besides the above parameters, which is not limited in this embodiment of the application.

In this embodiment, a common check timer is set for the PDCP entity, so that the timer is used to trigger periodic timeout check on the PDCP SDUs in each DRB queue, and discard timeout data, thereby avoiding a problem that a large number of timeout PDCP SDUs cannot be discarded in time when the terminal does not receive uplink authorization information for a long time due to poor link quality or bottom layer error, and further ensuring smooth transmission of uplink data.

In addition, in this embodiment, the terminal dynamically adjusts the duration of the timer based on the uplink grant frequency, the uplink sending rate, the data buffer size, and other factors, so that the uplink data is prevented from being blocked, and meanwhile, the waste of processing resources caused by the frequent start of the periodic detection is avoided.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Referring to fig. 9, a block diagram of a data discarding apparatus according to an embodiment of the present application is shown. The apparatus may include:

a setting module 901, configured to set a timeout timestamp for a service data unit PDCP SDU of a packet data convergence protocol;

a reading module 902, configured to, in response to that a timeout detection condition is met, read description information of the PDCP SDU in a DRB queue of a data radio bearer, where the description information includes the timeout timestamp corresponding to the PDCP SDU;

a discarding module 903, configured to discard the PDCP SDU in response to the timeout timestamp indicating that the PDCP SDU is timed out.

Optionally, the reading module 902 includes:

a first reading unit, configured to read the description information of the PDCP SDU in the DRB queue in response to receiving uplink grant information by a media access control MAC layer.

Optionally, the first reading unit is specifically configured to:

responding to the MAC layer receiving the uplink authorization information, and determining a target DRB queue corresponding to a target logical channel from at least one DRB queue, wherein the target logical channel is a logical channel for receiving the uplink authorization information;

and reading the description information of the PDCP SDU in the target DRB queue.

Optionally, the apparatus further comprises:

and the sending module is used for responding to the overtime time stamp to indicate that the PDCP SDU is not overtime, carrying out data processing on the PDCP SDU and sending the processed data.

Optionally, the reading module 902 includes:

a second reading unit, configured to read the description information of the PDCP SDU in the DRB queue in response to a check timer reaching a timer duration, where the timer duration is less than an timeout duration configured by a PDCP entity;

and the restarting unit is used for restarting the check timer.

Optionally, the second reading unit is configured to:

responding to the time length of the timer reached by the check timer, and determining a target DRB queue corresponding to a target PDCP entity, wherein the target PDCP entity is a PDCP entity configured with an overtime mechanism;

and reading the description information of the PDCP SDU in each target DRB queue.

Optionally, the apparatus further comprises:

an adjusting module, configured to adjust the duration of the timer based on a target parameter, where the target parameter includes at least one of an uplink grant frequency, an uplink sending rate, and a data buffer size;

the timer duration and the uplink authorization frequency and the uplink sending rate are in positive correlation, and the timer duration and the data buffer size are in negative correlation.

Optionally, the setting module 901 includes:

a first obtaining unit, configured to obtain a configured timeout duration in response to a timestamp setting notification received by a PDCP entity, where the timestamp setting notification is sent when an IP packet is received by an upper layer;

and the setting unit is used for setting the time-out time stamp for the PDCP SDU through the PDCP entity based on the current time and the time-out duration.

Optionally, the discarding module 903 is configured to:

and determining that the PDCP SDU is overtime and discarding the PDCP SDU in response to the overtime timestamp being less than the current time.

Optionally, the discarding module 903 includes:

a second obtaining unit, configured to obtain a data address and a data length of the PDCP SDU from the description information;

a release unit, configured to release a storage space occupied by the PDCP SDU based on the data address and the data length;

a removing unit, configured to remove the description information of the PDCP SDU from the DRB queue.

Fig. 10 is a schematic structural diagram of a terminal according to an exemplary embodiment of the present application, where the terminal includes: a processor 1001, a receiver 1002, a transmitter 1003, a memory 1004, and a bus 1005.

The processor 1001 includes one or more processing cores, and the processor 1001 executes various functional applications and information processing by running software programs and modules.

The receiver 1002 and the transmitter 1003 may be implemented as one communication component, which may be a piece of communication chip.

The memory 1004 is connected to the processor 1001 through a bus 1005.

The memory 1004 may be used to store at least one instruction that the processor 1001 uses to execute in order to implement the various steps in the above-described method embodiments.

Further, the memory 1004 may be implemented by any type or combination of volatile or non-volatile storage devices, including, but not limited to: magnetic or optical disks, Electrically Erasable Programmable Read Only Memories (EEPROMs), Erasable Programmable Read Only Memories (EPROMs), Static Random Access Memories (SRAMs), Read-Only memories (ROMs), magnetic memories, flash memories, Programmable Read Only Memories (PROMs).

The embodiment of the present application also provides a computer-readable storage medium, which stores at least one program code, and the program code is loaded and executed by a processor to implement the data discarding method according to the above embodiments.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the data discarding method provided in the various alternative implementations of the above aspects.

It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. In addition, the step numbers described herein only exemplarily show one possible execution sequence among the steps, and in some other embodiments, the steps may also be executed out of the numbering sequence, for example, two steps with different numbers are executed simultaneously, or two steps with different numbers are executed in a reverse order to the order shown in the figure, which is not limited by the embodiment of the present application.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method of data discard, the method comprising:

setting a timeout timestamp for a service data unit PDCP SDU of a packet data convergence protocol;

reading description information of the PDCP SDU in a Data Radio Bearer (DRB) queue in response to the condition of timeout detection being met, wherein the description information contains the timeout timestamp corresponding to the PDCP SDU;

2. The method of claim 1, wherein reading the description information of the PDCP SDU in the DRB queue in response to the timeout detection condition being met comprises:

and responding to the receiving of the uplink authorization information by the media access control MAC layer, and reading the description information of the PDCP SDU in the DRB queue.

3. The method of claim 2, wherein the reading the description information of the PDCP SDU in the DRB queue in response to the MAC layer receiving uplink grant information comprises:

4. The method as claimed in claim 2, wherein after reading the description information of the PDCP SDU in the DRB queue, the method further comprises:

and responding to the time-out time stamp indicating that the PDCP SDU is not time-out, performing data processing on the PDCP SDU, and sending the processed data.

5. The method of claim 1, wherein reading the description information of the PDCP SDU in the DRB queue in response to the timeout detection condition being met comprises:

reading the description information of the PDCP SDU in the DRB queue in response to a check timer reaching a timer duration, wherein the timer duration is less than an overtime duration configured by a PDCP entity;

restarting the check timer.

6. The method of claim 5, wherein the reading the description information of the PDCP SDU in the DRB queue in response to the checking timer reaching a timer duration comprises:

7. The method of claim 5, further comprising:

adjusting the time length of the timer based on target parameters, wherein the target parameters comprise at least one of uplink authorization frequency, uplink sending rate and data buffer size;

8. The method according to any of claims 1 to 7, wherein the setting the time-out timestamp for the PDCP SDU comprises:

responding to a time stamp setting notice sent by an upper layer received by a PDCP entity, and acquiring configured overtime duration, wherein the time stamp setting notice is sent when the upper layer receives an IP data packet;

and setting the time-out time stamp for the PDCP SDU through the PDCP entity based on the current time and the time-out duration.

9. The method according to any of claims 1 to 7, wherein said discarding the PDCP SDU in response to the time-out timestamp indicating that the PDCP SDU times out comprises:

10. The method according to any of claims 1 to 7, wherein the discarding the PDCP SDU comprises:

acquiring a data address and a data length of the PDCP SDU from the description information;

based on the data address and the data length, releasing the storage space occupied by the PDCP SDU;

removing the description information of the PDCP SDU from the DRB queue.

11. A data discarding apparatus, characterized in that the apparatus comprises:

the setting module is used for setting a timeout timestamp for a service data unit PDCP SDU of a packet data convergence protocol;

12. A terminal, characterized in that the terminal comprises a processor and a memory, the memory having stored therein at least one instruction, the at least one instruction being loaded and executed by the processor to implement the data discarding method according to any one of claims 1 to 10.

13. A computer-readable storage medium having at least one program code stored therein, the program code being loaded and executed by a processor to implement the data discarding method according to any one of claims 1 to 10.