CN113472683B - Data discarding method, device, terminal and storage medium - Google Patents

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 description information of the PDCP SDU in the DRB queue in response to the condition of timeout detection, wherein the description information comprises a timeout time stamp corresponding to the PDCP SDU; and discarding the PDCP SDU in response to the timeout timestamp indicating that the PDCP SDU is overtime. By adopting the scheme provided by the embodiment of the application, the setting of a discarding timer for the PDCP SDU is not needed, a large amount of processing resources occupied by the setting of a large amount of discarding timers are avoided, the overtime discarding process of the PDCP SDU is simplified, and the complexity of detecting and maintaining the problems of a communication system is reduced.

Description

Data discarding method, device, terminal and storage medium

Technical Field

The embodiments of the present application relate to the field of communication technology, and in particular to a data discarding method, device, terminal and storage medium.

Background Art

The Packet Data Convergence Protocol (PDCP) entity is located at the second layer of the radio interface protocol stack and is used to process Radio Resource Control (RRC) messages on the control plane and Internet Protocol (IP) packets on the user plane.

On the user plane, after the PDCP entity receives the PDCP Service Data Unit (SDU) from the upper layer, it needs to configure the associated discard timer (discardTimer) for each PDCP SDU. When the discard timer times out, the PDCP entity discards the PDCP SDU. If the PDCP Protocol Data Unit (PDU) corresponding to the PDCP SDU is sent to the lower layer, the PDCP entity also needs to notify the lower layer to discard the PDCP PDU.

Summary of the invention

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

On the one hand, an embodiment of the present application provides a data discarding method, the method comprising:

Set a timeout timestamp for the PDCP SDU;

In response to satisfying a timeout detection condition, reading description information of the PDCP SDU in a data radio bearer (DRB) queue, the description information including the timeout timestamp corresponding to the PDCP SDU;

In response to the timeout timestamp indicating that the PDCP SDU is timed out, discarding the PDCP SDU.

On the other hand, an embodiment of the present application provides a data discarding device, the device comprising:

A setting module, used for setting a timeout timestamp for a PDCP SDU;

a reading module, configured to read, in response to satisfying a timeout detection condition, description information of the PDCP SDU in the DRB queue, the description information including the timeout timestamp corresponding to the PDCP SDU;

The discarding module is configured to discard the PDCP SDU in response to the timeout timestamp indicating that the PDCP SDU has timed out.

On the other hand, an embodiment of the present application provides a terminal, which includes a processor and a memory, wherein 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 as described in the above aspects.

On the other hand, 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 as described in the above aspects.

On the other hand, an embodiment of the present application provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the data discarding method provided in various optional implementations of the above aspects.

The technical solution provided in the embodiments of the present application can bring the following beneficial effects:

In an embodiment of the present application, a timeout timestamp is set for the PDCP SDU, and when the timeout detection condition is met, the description information of the PDCP SDU is obtained from the DRB queue, so as to determine whether the PDCP SDU has timed out based on the timeout timestamp in the description information, and then the timed out PDCP SDU is discarded; by adopting the solution provided in the embodiment of the present application, there is no need to set a discard timer for the PDCP SDU, thus avoiding setting a large number of discard timers to occupy a large amount of processing resources, simplifying the timeout discard process of the PDCP SDU, and helping to reduce the complexity of problem detection and maintenance of the communication system.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

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

FIG2 is a schematic diagram of the protocol architecture of the user plane and the control plane;

FIG3 shows a flow chart of a data discarding method provided by an exemplary embodiment of the present application;

FIG4 shows a flow chart of a data discarding method provided by another exemplary embodiment of the present application;

FIG5 is a schematic diagram of the implementation process of the data discarding method shown in FIG4;

FIG6 is a schematic diagram of an interaction process between an upper layer, a PDCP entity and a MAC layer, showing an exemplary embodiment;

FIG7 shows a flow chart of a data discarding method provided by another exemplary embodiment of the present application;

FIG8 is a schematic diagram of the implementation process of the data discarding method shown in FIG7;

FIG9 shows a structural block diagram of a data discarding device provided by an embodiment of the present application;

FIG. 10 shows a schematic diagram of the structure of a terminal provided by an exemplary embodiment of the present application.

DETAILED DESCRIPTION

In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

Please refer to FIG1 , which shows a schematic diagram of a communication system provided by an embodiment of the present application. The communication system may include: an access network 12 and a terminal 14 .

The access network 12 includes several network devices 120. The network device 120 may be a base station, which is a device deployed in the access network to provide wireless communication functions for the terminal. The base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different wireless access technologies, the names of devices with base station functions may be different. For example, in an LTE system, it is called eNodeB or eNB; in a 5G NR-U system, it is called gNodeB or gNB. With the evolution of communication technology, the description of "base station" may change. For the convenience of the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal 14 are collectively referred to as network devices.

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

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based access to Unlicensed spectrum, LTE-U) system, NR-U system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Wireless Local Area Network (WLAN) system. Networks, WLAN), Wireless Fidelity (WiFi), next generation communication systems or other communication systems, etc.

Generally speaking, the number of connections supported by traditional communication systems is limited and easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication and vehicle to everything (V2X) system, etc. The embodiments of the present application can also be applied to these communication systems.

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

Radio Resource Control (RRC): It is used to manage, control and schedule radio resources, making full use of limited radio network resources and expanding the capacity of the communication system while meeting the quality of service requirements.

PDCP: used to perform IP header compression to reduce the number of bits transmitted on the wireless interface. The header compression mechanism is based on the Robust Header Compression (ROHC) algorithm, which can also be applied to the standardized header compression of other mobile communication technologies. PDCP is also responsible for encryption of the control plane, integrity protection of transmitted data, and in-order transmission and duplicate deletion for switching. At the receiving end, the PDCP protocol performs the corresponding decryption and decompression operations. Among them, each radio bearer (RadioBearer, RB) of the terminal is configured with a PDCP entity.

Radio Link Control (RLC): Responsible for segmentation/concatenation, retransmission control, duplication detection, and sequence transmission to higher layers. RLC provides services for PDCP. Each radio bearer of the terminal is configured with an RLC entity.

Media Access Control (MAC): It is used to control the multiplexing of logical channels, hybrid automatic repeat-request (ARQ) retransmission, and scheduling of uplink and downlink. For uplink and downlink, the scheduling function is located in the base station. The hybrid ARQ protocol part is located at the transmit and receive end of the MAC protocol. MAC provides services to RLC in the form of logical channels.

Physical layer (PHY): used to manage encoding/decoding, modulation/demodulation, multi-antenna mapping 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 a PDCP SDU from the upper layer and is configured by a timeout mechanism, it is necessary to configure an associated discard timer for the PDCP PDU and start the discard timer. Once the discard timer times out, the PDCP entity discards the PDCP SDU associated with the discard timer. If the PDCP PDU corresponding to the PDCP SDU (obtained after adding a PDCP header to the head of the PDCP SDU) is sent down to the bottom layer, the PDCP entity needs to notify the bottom layer to discard the PDCP PDU.

It can be seen that the related art implements timeout management by setting a discard timer. However, since starting the discard timer and managing the timer requires a certain amount of processing resources, when there are a large number of PDCP SDUs, a large amount of processing resources are required to implement timeout management. In addition, for the timed-out PDCP PDU sent to the bottom layer, the bottom layer's timeout discard process is relatively cumbersome, resulting in high complexity in problem detection and maintenance of the communication system.

In order to simplify the data discard process, in the embodiment of the present application, the PDCP entity does not need to configure an associated discard timer for the PDCP SDU, but adds a timeout timestamp to the description information of the PDCP SDU. When a timeout detection is required, the description information of the PDCP SDU in the DRB queue is read, and a timeout detection is performed based on the timeout timestamp in the description information, so that when the PDCP SDU timeout is detected, the PDCP SDU is discarded. In the entire data discard process, there is no need to configure a discard timer for the PDCP SDU, so as to avoid starting and managing timers to occupy processing resources, simplify the data discard process, and help reduce the complexity of problem detection and maintenance of the communication system.

Please refer to FIG. 3, which shows a flow chart of a data discarding method provided by an exemplary embodiment of the present application. This embodiment is described by taking the method used in a terminal in the communication system shown in FIG. 1 as an example. The method includes:

Step 301, setting a timeout timestamp for a PDCP SDU.

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

Step 302: In response to satisfying the timeout detection condition, read 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 triggering the timeout detection. Optionally, the timeout detection condition can be triggered by an external device (such as an access network device), or by the terminal itself.

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

In the embodiment of the present 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 the DRB queue in sequence (according to the order in which the PDCP SDU is received). 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 to complete the description information queuing operation.

Among them, at least one DRB queue is set in the terminal, and different DRB queues are used to store description information of PDCP SDU corresponding to different PDCP entities.

Optionally, the description information may include the data length and data address of the PDCP SDU in addition to the timeout timestamp. Of course, the description information may also include other information in addition to the above information, and this embodiment does not limit the specific content of the description information.

In some embodiments, each DRB queue is provided with a write index and a read index. The write index is used to indicate the 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 to indicate the read position of the description information, and after the description information is read from the DRB queue, the position of the read index changes.

In one possible implementation, when the 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 timeout timestamp for the PDCP SDU, the terminal writes the description information to the DRB queue according to the position of the write index in the DRB queue.

Step 303: In response to the timeout timestamp indicating that the PDCP SDU is timed out, discard the PDCP SDU.

After reading the timeout timestamp of the PDCP SDU, the terminal detects whether the PDCP SDU has timed out based on the timeout timestamp, and if so, discards the PDCP SDU, wherein the discarded PDCP SDU will not be sent to the bottom layer.

In a possible implementation, the terminal obtains the current time and detects whether the timeout timestamp is less than the current time. If so, it is determined that the PDCP SDU has timed out; if so, it is determined that the PDCP SDU has not timed out. For example, when the timeout timestamp is 16254747887060 (in ms) and the current time is 1625474788759, the terminal determines that the PDCP SDU has timed out.

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

To summarize, in the embodiments of the present application, a timeout timestamp is set for the PDCP SDU, and when the timeout detection condition is met, the description information of the PDCP SDU is obtained from the DRB queue, thereby determining whether the PDCP SDU has timed out based on the timeout timestamp in the description information, and then discarding the timed out PDCP SDU; by adopting the solution provided in the embodiments of the present application, there is no need to set a discard timer for the PDCP SDU, thus avoiding setting a large number of discard timers to occupy a large amount of processing resources, simplifying the timeout discard process of the PDCP SDU, and helping to reduce the complexity of problem detection and maintenance of the communication system.

In a possible implementation, in order to avoid uplink data blocking caused by a timed-out PDCP SDU, when uplink data needs to be sent, the terminal determines that a timeout detection condition is met, and performs a timeout detection based on the timeout timestamp of the PDCP SDU. Please refer to FIG4, which shows a flow chart of a data discarding method provided by another exemplary embodiment of the present application. This embodiment takes the method used in the terminal in the communication system shown in FIG1 as an example for explanation, and the method includes:

Step 401, in response to the PDCP entity receiving a timestamp setting notification sent by an upper layer, obtaining a configured timeout duration, wherein the timestamp setting notification is sent by the upper layer when receiving an IP data packet.

In one possible implementation, after receiving the IP data packet, the upper layer writes the IP data packet into a cache and sends a timestamp setting notification to the PDCP entity, instructing the PDCP entity to set a timeout timestamp for the PDCP SDU (the representation of the IP data 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 data packet belongs, and then send 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 is configured with a timeout mechanism, and when the PDCP entity configures the timeout mechanism, it sends a timestamp setting notification to the PDCP entity. Accordingly, after the PDCP entity receives the timestamp setting notification, it obtains the timeout duration configured by itself.

The timeout durations configured by different PDCP entities may be the same or different. For example, for wireless bearer A, the timeout duration configured by the corresponding PDCP entity is 500ms, and for wireless bearer B, the timeout duration configured by the corresponding PDCP entity is 400ms. The timeout duration configured by the PDCP entity is not limited in the embodiments of the present application.

Schematically, as shown in FIG. 5 , after receiving the IP data packet, the upper layer 51 writes the IP data packet into the L3 buffer (in PD form) and sends a timestamp setting notification to the PDCP entity 52 .

Step 402: Based on the current time and the timeout duration, a timeout timestamp is set for the PDCP SDU via the PDCP entity.

After receiving the timestamp setting notification, the PDCP entity determines the timeout time point of the PDCP SDU according to the timeout duration configured by itself and the current time, and then sets a timeout timestamp for the PDCP SDU. The timeout timestamp = current time + timeout duration.

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

In a possible implementation, after the PDCP entity sets a timeout timestamp for the PDCP SDU, the timeout timestamp is used as part of the description information of the PDCP SDU, and the description information is written into the DRB queue corresponding to the PDCP entity to complete the enqueuing of the description information. Each time the enqueuing is completed, the PDCP entity needs to update the index position of the write index in the DRB queue.

Schematically, as shown in FIG5, after receiving the notification, the PDCP entity 52 reads the L3 buffer, sets a timeout timestamp for the PDCP SDU, and writes the description information including the timeout timestamp into the corresponding DRB queue. In FIG5, n DRB queues are set, and the PDCP entity 52 is about to write the description information into the DRB queue corresponding to itself among the n DRB queues.

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

When the network side allows the terminal to send uplink data, it will send uplink grant information (UL grant) to the terminal. Accordingly, the terminal can send uplink data based on the uplink grant information. In order to avoid timeout data blocking uplink data transmission, when the MAC layer receives the uplink grant information and needs to read the PDCP SDU, it first performs a timeout check on the PDCP SDU; if the PDCP SDU times out, it is discarded; if the PDCP SDU does not time out, uplink data is sent based on the PDCP SDU.

Since multiple DRB queues (corresponding to different wireless bearers) are set up in the terminal at the same time, in order to ensure the accuracy of timeout detection, after receiving the uplink authorization information, the terminal first needs to determine the target wireless bearer to ensure that the PDCP SDU description information is accurately read from the DRB queue corresponding to the target wireless bearer.

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

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

Illustratively, as shown in FIG. 5 , after receiving the uplink authorization information, the MAC layer 53 determines that the target DRB queue is the DRB queue n, and then reads the description information in sequence from the DRB queue n (ie, dequeues the description information).

It should be noted that, since different logical channels have different priorities, when uplink authorization information is received through multiple logical channels, the terminal prioritizes the DRB queue corresponding to the high-priority logical channel for timeout detection. In some embodiments, both the PDCP entity and the MAC layer have read and write permissions for the DRB queue. After receiving the uplink authorization information, the LCP (Logical Channel Prioritization) module of the MAC layer reads the description information based on the logical channel priority and performs timeout detection.

The terminal detects whether the timeout has occurred based on the timeout timestamp of the PDCP SDU. If the timeout has occurred, step 404 is executed. If the timeout has not occurred, step 405 is executed.

Step 404: In response to the timeout timestamp indicating that the PDCP SDU is timed out, discard the PDCP SDU.

In a possible implementation manner, the description information includes not only the timeout timestamp but also the data address and data length of the PDCP SDU, and the terminal discarding the PDCP SDU may include the following steps.

1. Obtain the data address and data length of the PDCP SDU from the description information.

When it is determined that the PDCP SDU has timed out, the terminal further obtains the data address and data length from the description information of the PDCP SDU so as to release the storage space later. In some embodiments, the data address is the starting address of the PDCP SDU in the cache, and based on the data address and data length, the end address of the PDCP SDU in the cache can be determined.

2. Based on the data address and data length, the storage space occupied by the PDCP SDU is released.

The terminal deletes the PDCP SDU from the cache based on the data address and the data length, thereby releasing storage space for subsequent writing of a new PDCP SDU.

3. Remove the description information of the PDCP SDU from the DRB queue.

At the same time, the terminal removes the description information of the timed-out PDCP SDU from the DRB queue so as to subsequently write the description information of the newly received PDCP SDU.

Since the description information in the DRB queue is arranged in order, after detecting that the current PDCP SDU has timed out, the terminal continues to read the next description information from the DRB queue and repeats the above timeout detection process.

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

Step 405: In response to the timeout timestamp indicating that the PDCP SDU has not timed out, data processing is performed on the PDCP SDU, and the processed data is sent.

When the PDCP SDU has not timed out, the terminal further performs data processing on the PDCP SDU before sending, and then sends the processed data. The data processing before sending 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), etc., which is not limited in this embodiment.

Schematically, as shown in FIG. 5 , when the PDCP SDU has not timed out, the terminal performs data processing such as encryption on the PDCP SDU, thereby sending the processed data to a transmitter buffer (TXbuffer) for subsequent data transmission.

Since the description information in the DRB queue is arranged in order, after detecting that the current PDCP SDU has not timed out, the terminal does not need to execute the above timeout detection process and can directly send data based on the PDCP SDU (it is still necessary 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 implementing the above data discarding method, the interaction process between the upper layer in the terminal, the PDCP entity and the MAC layer is shown in FIG6 .

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

Step 602: The upper layer notifies the PDCP entity to set the timestamp.

Step 603: The PDCP entity reads the L3 buffer and calculates the timeout timestamp of the PDCP SDU based on the configured timeout duration and the current time.

Step 604: The PDCP entity writes the description information including the timeout timestamp into the target DRB queue and updates the write index of the DRB queue.

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 has timed out based on the timeout timestamp in the description information. If so, step 607 is executed; if not, step 608 is executed.

Step 607: The MAC layer discards the PDCP SDU, releases the L3 buffer occupied by the PDCP SDU, and updates the read index.

Step 608: The MAC layer reads the PDCP SDU that has not timed out and sends it to the bottom layer for uplink data transmission.

In this embodiment, when uplink authorization information is received and uplink data is about to be sent, the description information in the DRB queue is read, and whether the PDCP SDU has timed out is detected based on the timeout timestamp in the description information. This enables automatic discarding of the timed-out PDCP SDU and normal uplink transmission of the non-timed-out PDCP SDU, without setting a discard timer, which helps save processing resources.

In one possible scenario, when the terminal fails to receive uplink authorization information for a long time due to poor link quality or underlying errors, the solution for timeout detection based on uplink authorization information cannot be executed, resulting in a large number of timed-out PDCP SDUs not being discarded in time. Accordingly, when uplink authorization information is subsequently received, it takes a long time to perform timeout detection and discard. In order to avoid the backlog of timeout data in this scenario, in one possible implementation, the terminal can set a common check timer for each DRB queue, thereby using the detection timer to trigger the timing timeout detection. The following is an exemplary embodiment for illustration.

Please refer to FIG. 7, which shows a flow chart of a data discarding method provided by another exemplary embodiment of the present application. This embodiment is described by taking the method used in a terminal in the communication system shown in FIG. 1 as an example. The method includes:

Step 701, in response to the PDCP entity receiving a timestamp setting notification sent by an upper layer, obtaining a configured timeout duration, wherein the timestamp setting notification is sent by the upper layer when receiving an IP data packet.

Step 702: Based on the current time and the timeout duration, a timeout timestamp is set for the PDCP SDU via the PDCP entity.

The implementation of steps 701 to 702 may refer to steps 401 to 402, and will not be described in detail in this embodiment.

Schematically, as shown in FIG8 , after receiving the IP data packet, the upper layer 81 writes the IP data packet into the L3 buffer and sends a timestamp setting notification to the PDCP entity 82. After receiving the notification, the PDCP entity 82 reads the L3 buffer, sets a timeout timestamp for the PDCP SDU, and writes the description information including the timeout timestamp into the corresponding DRB queue.

Step 703, in response to the check timer reaching the timer duration, read the description information of the PDCP SDU in the DRB queue, the description information includes a timeout timestamp corresponding to the PDCP SDU, and the timer duration is less than the timeout duration configured by the PDCP entity.

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

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

Different from the timeout detection triggered by the uplink authorization information for a specific DRB, the timeout detection triggered by the check timer is for all DRBs that need to be timed out. Therefore, in one possible implementation, in response to the check timer reaching the timer duration, the terminal determines the target DRB queue corresponding to the target PDCP entity, which is the PDCP entity configured with the timeout mechanism, and then reads the description information of the PDCP SDU in each target DRB queue.

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

Schematically, as shown in Figure 8, when n DRB queues are set in the terminal and the PDCP entities corresponding to each DRB queue are set with a timeout mechanism, when the check timer reaches the timer length, the MAC layer 83 (or other modules in the terminal) reads the description information in the n DRB queues and performs a timeout detection.

Step 704: In response to the timeout timestamp indicating that the PDCP SDU is timed out, discard the PDCP SDU.

Similar to the above step 404, when the PDCP SDU times out, the terminal discards the PDCP SDU (the specific discarding process can refer to step 404). In a possible implementation, if the current PDCP SDU times out, the terminal continues to read the next description information in the DRB queue and updates the read index of the DRB queue until the timeout detection is stopped when the current PDCP SDU does not time out.

Illustratively, as shown in FIG8 , the MAC layer 83 discards the timed-out PDCP SDU, while the non-timed-out PDCP SDU continues to be stored in the DRB queue, waiting for uplink transmission when a UL grant is made.

Step 705, restart the inspection timer.

In a possible implementation, after each DRB queue completes the timeout detection, the terminal restarts the check timer to perform 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 each time according to the fixed timer duration. For example, the timer duration is 50 ms.

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

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

Among them, when the uplink frequency is higher or the uplink sending rate is faster, it indicates that the state of the uplink data transmission path is better. In order to avoid frequent periodic detection, a longer timer duration can be set, that is, the timer duration is positively correlated with the uplink authorization frequency and the uplink sending rate; on the contrary, when the terminal data buffer is larger, it indicates that the data uplink speed is slow and uplink data blocking is prone to occur. Therefore, a shorter timer duration can be set to clear the timed out data in time, that is, the timer duration is negatively correlated with the data buffer size.

Of course, the terminal may also dynamically adjust the timer duration based on other parameters other than the above parameters, and the embodiments of the present application are not limited to this.

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

In addition, in this embodiment, the terminal dynamically adjusts the timer duration based on factors such as uplink authorization frequency, uplink transmission rate, and data buffer size, thereby preventing uplink data blocking and avoiding waste of processing resources caused by too frequent activation of periodic detection.

The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

Please refer to FIG9 , which shows a structural block diagram of a data discarding device provided by an embodiment of the present application. The device may include:

A setting module 901 is used to set a timeout timestamp for a packet data convergence protocol service data unit PDCP SDU;

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

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

Optionally, the reading module 902 includes:

The first reading unit is used to read the description information of the PDCP SDU in the DRB queue in response to a media access control MAC layer receiving uplink authorization information.

Optionally, the first reading unit is specifically configured to:

In response to the MAC layer receiving the uplink grant information, determining a target DRB queue corresponding to a target logical channel from at least one DRB queue, the target logical channel being a logical channel for receiving the uplink grant information;

Read the description information of the PDCP SDU in the target DRB queue.

Optionally, the device further comprises:

The sending module is used for processing the PDCP SDU data in response to the timeout timestamp indicating that the PDCP SDU has not timed out, 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, wherein the timer duration is less than a timeout duration configured by the PDCP entity;

A restart unit is used to restart the inspection timer.

Optionally, the second reading unit is used to:

In response to the check timer reaching the timer duration, determining a target DRB queue corresponding to a target PDCP entity, the target PDCP entity being a PDCP entity configured with a timeout mechanism;

Read the description information of the PDCP SDU in each of the target DRB queues.

Optionally, the device further comprises:

An adjustment module, configured to adjust the timer duration based on a target parameter, wherein the target parameter includes at least one of an uplink authorization frequency, an uplink transmission rate, and a data buffer size;

The timer duration is positively correlated with the uplink authorization frequency and the uplink transmission rate, and the timer duration is negatively correlated with the data buffer size.

Optionally, the setting module 901 includes:

A first acquisition unit, configured to acquire a configured timeout duration in response to the PDCP entity receiving a timestamp setting notification sent by an upper layer, wherein the timestamp setting notification is sent by the upper layer when receiving an IP data packet;

A setting unit is used to set the timeout timestamp for the PDCP SDU through the PDCP entity based on the current time and the timeout duration.

Optionally, the discarding module 903 is used to:

In response to the timeout timestamp being less than the current time, it is determined that the PDCP SDU is timed out, and the PDCP SDU is discarded.

Optionally, the discarding module 903 includes:

A second acquiring unit, configured to acquire a data address and a data length of the PDCP SDU from the description information;

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

A removing unit is used to remove the description information of the PDCP SDU from the DRB queue.

To summarize, in the embodiments of the present application, a timeout timestamp is set for the PDCP SDU, and when the timeout detection condition is met, the description information of the PDCP SDU is obtained from the DRB queue, thereby determining whether the PDCP SDU has timed out based on the timeout timestamp in the description information, and then discarding the timed out PDCP SDU; by adopting the solution provided in the embodiments of the present application, there is no need to set a discard timer for the PDCP SDU, thus avoiding setting a large number of discard timers to occupy a large amount of processing resources, simplifying the timeout discard process of the PDCP SDU, and helping to reduce the complexity of problem detection and maintenance of the communication system.

FIG10 shows a schematic diagram of the structure of a terminal provided by an exemplary embodiment of the present application. 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. 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 a communication component, which may be a communication chip.

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

The memory 1004 may be used to store at least one instruction, and the processor 1001 may be used to execute the at least one instruction to implement each step in the above method embodiment.

In addition, the memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. The volatile or non-volatile storage device includes but is not limited to: a magnetic disk or an optical disk, an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a static random access memory (SRAM), a read-only memory (ROM), a magnetic memory, a flash memory, and a programmable read-only memory (PROM).

An embodiment of the present application further 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 described in the above embodiments.

According to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes a computer instruction, the computer instruction is stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the data discarding method provided in various optional implementations of the above aspects.

It should be understood that the "multiple" mentioned in this article refers to two or more. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the objects associated before and after are in an "or" relationship. In addition, the step numbers described in this article only illustrate a possible execution sequence between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order to the diagram. The embodiments of the present application are not limited to this.

The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims (13)

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

Setting a timeout time stamp for a service data unit PDCP SDU of a packet data convergence protocol, wherein the timeout time stamp is used for indicating a timeout time point of the PDCP SDU, the timeout time stamp is added into description information of the PDCP SDU, and the description information is added into a data radio bearer DRB queue, and a media access control MAC layer has read-write authority of the DRB queue;

Reading, by the MAC layer, the description information of the PDCP SDU in a DRB queue in response to a timeout detection condition being satisfied;

Discarding the PDCP SDU in response to the timeout timestamp indicating that the PDCP SDU is timeout.

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

And in response to the MAC layer receiving the uplink authorization information, 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 SDUs in the DRB queue in response to the MAC layer receiving uplink grant information comprises:

In response to the MAC layer receiving the uplink grant information, 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 grant information;

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

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

And responding to the overtime time stamp indicating that the PDCP SDU is not overtime, carrying out data processing on the PDCP SDU and transmitting the processed data.

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

responding to the fact that a checking timer reaches a timer duration, and reading the description information of the PDCP SDU in the DRB queue through the MAC layer, wherein the timer duration is smaller than a timeout duration configured by a PDCP entity;

Restarting the checking timer.

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

Determining a target DRB queue corresponding to a target PDCP entity in response to the checking timer reaching the timer duration, wherein the target PDCP entity is a PDCP entity configured with a timeout mechanism;

and reading the description information of the PDCP SDUs in each target DRB queue through the MAC layer.

7. The method of claim 5, wherein the method further comprises:

Adjusting the time length of the timer based on a target parameter, wherein the target parameter comprises at least one of uplink authorized frequency, uplink sending rate and data buffer size;

the timer duration and the uplink grant frequency and the uplink transmission rate are in a positive correlation, and the timer duration and the data buffer size are in a negative correlation.

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

Acquiring configured timeout duration in response to receiving a timestamp setting notification sent by an upper layer by a PDCP entity, wherein the timestamp setting notification is sent when an IP data packet is received by the upper layer;

And setting the overtime time stamp for the PDCP SDU by the PDCP entity based on the current time and the overtime time.

9. The method of any of claims 1 to 7, wherein discarding the PDCP SDU in response to the timeout timestamp indicating the PDCP SDU to timeout comprises:

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

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

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

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

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

11. A data discarding apparatus, the apparatus comprising:

A setting module, configured to set a timeout timestamp for a service data unit PDCP SDU of a packet data convergence protocol, where the timeout timestamp is used to indicate a timeout point of the PDCP SDU, the timeout timestamp is added to description information of the PDCP SDU, and the description information is added to a data radio bearer DRB queue, where a medium access control MAC layer has a read-write authority of the DRB queue;

a reading module, configured to read, by the MAC layer, the description information of the PDCP SDU in the DRB queue in response to satisfaction of a timeout detection condition;

and the discarding module is used for discarding the PDCP SDU in response to the overtime timestamp indicating that the PDCP SDU overtime.

12. A terminal comprising a processor and a memory, wherein the memory has stored therein at least one instruction that is 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 stored therein at least one program code loaded and executed by a processor to implement the data discarding method according to any one of claims 1 to 10.