Information processing method and device, equipment, medium and product

By sending the number of consecutive timeouts of the reassembly timer to the PDCP entity through the RLC AM entity, dynamically adjusting the reordering timer value and triggering RLF, the problems of data transmission latency and resource waste under RLC AM are solved, and faster RRC reconstruction and resource optimization are achieved.

CN121940771APending Publication Date: 2026-04-28CHINA MOBILE COMM LTD RES INST +1
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-25
Publication Date
2026-04-28

AI Technical Summary

Technical Problem

In Radio Link Control Layer Acknowledgment Mode (RLC AM), data transmission delay and invalid retransmissions lead to resource waste, especially under poor channel conditions. Existing mechanisms result in excessively long reconstruction delays and severe resource waste.

Method used

The RLC AM entity sends information related to the number of consecutive timeouts of the reordering timer to the PDCP entity. The PDCP entity dynamically adjusts the value of the reordering timer based on this information and triggers a radio link failure (RLF) when the reordering timer times out, so as to quickly rebuild the RRC and avoid invalid retransmissions.

Benefits of technology

By dynamically adjusting the value of the reordering timer, the RRC reconstruction delay under poor channel conditions is reduced, and RLC retransmissions that waste resources are avoided.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121940771A_ABST
    Figure CN121940771A_ABST
Patent Text Reader

Abstract

Provided are an information processing method, apparatus, device, medium and product, the method comprising: a radio link control acknowledgement mode (RLC AM) entity sending first information to a packet data convergence protocol (PDCP) entity, the first information being related to the number of times of continuous timeout of a reconfiguration timer, the reconfiguration timer being a timer maintained by the PDCP entity, the first information being related to the number of times of continuous timeout of the reconfiguration timer; the first information is used for adjusting the value of a reordering timer, and the reordering timer is a timer maintained by the PDCP entity.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of wireless technology, and in particular to an information processing method, apparatus, device, medium and product. Background Technology

[0002] In related technologies, in Radio Link Control Acknowledged Mode (RLC AM), both the Radio Link Control (RLC) layer and the Packet Data Convergence Protocol (PDCP) layer at the receiving end maintain a receive window, which is associated with a corresponding timer. In RLC AM mode, after the receiving end's timer expires, data retransmission is triggered via status reporting; however, after the PDCP layer's timer expires, the data update window is directly discarded. If the PDCP layer's timer is configured too large, although the PDCP receive window will not slide before the RLC layer completes the maximum number of retransmissions, this will result in very large data transmission delays. If the PDCP layer's timer is configured too small, the PDCP layer will slide its window due to timer expiration before the RLC layer completes the maximum number of retransmissions, while the RLC layer continues retransmission. In this case, even if the PDCP subsequently receives the corresponding Service Data Unit (SDU) delivered by the RLC, it will be discarded directly. Therefore, retransmissions performed by the RLC layer after the reordering timer expires are wasteful and meaningless. In the current RLC AM protocol, the number of data retransmissions is recorded by the transmitter, and Radio Link Failure (RLF) is only triggered by the transmitter after reaching the maximum number of retransmissions. Under poor channel conditions, this inflexible mechanism can lead to significant reconstruction delays, because other SDUs may have already retransmitted many times before one SDU reaches the maximum number of retransmissions. Therefore, reducing data transmission delays and resource waste caused by invalid retransmissions under RLC AM is a problem that needs to be considered. Summary of the Invention

[0003] The purpose of this application is to provide an information processing method, apparatus, device, medium, and product to solve the problem of how to reduce data transmission latency and resource waste caused by invalid retransmissions under RLC AM.

[0004] To achieve the above objectives, embodiments of this application provide an information processing method, including:

[0005] The Radio Link Control Acknowledgment Mode (RLC AM) entity sends a first message to the Packet Data Convergence Protocol (PDCP) entity. The first message is related to the number of consecutive timeouts of the reordering timer, which is a timer maintained by the PDCP entity. The first message is used to adjust the value of the reordering timer, which is also a timer maintained by the PDCP entity.

[0006] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0007] Optionally, send first information to the Packet Data Convergence Protocol (PDCP) entity, including:

[0008] The first information is sent to the PDCP entity at preset intervals.

[0009] This application also provides an information processing method, including:

[0010] The PDCP entity obtains the first information sent by the RLC AM entity, which is related to the number of consecutive timeouts of the reassembly timer;

[0011] The PDCP entity adjusts the value of the reordering timer based on the first information;

[0012] The PDCP entity triggers a Radio Link Failure (RLF) if the reordering timer times out.

[0013] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0014] Optionally, based on the first information, the value of the reordering timer is adjusted, including:

[0015] According to the mapping relationship between the first preset value set and the second preset value set, the value of the reordering timer is adjusted to a target value. The target value is a preset value in the second preset value set that corresponds to the value of the first information. The first preset value set includes at least one first preset value of the first information, and the second preset value set includes at least one second preset value of the pre-configured reordering timer. The second preset value decreases as the first preset value increases.

[0016] Optionally, the PDCP entity acquires the first information sent by the RLC AM entity, including:

[0017] The PDCP entity acquires the first information sent by the RLC AM entity at preset intervals.

[0018] This application also provides an information processing method, including:

[0019] The RLC AM entity sends first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer. The reassembly timer is a timer maintained by the PDCP entity.

[0020] The PDCP entity receives the first message sent by the RLC AM entity;

[0021] The PDCP entity adjusts the value of the reordering timer based on the first information. The reordering timer is a timer maintained by the PDCP entity.

[0022] The PDCP entity triggers RLF if the reordering timer times out.

[0023] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0024] This application embodiment also provides an information processing apparatus, the apparatus comprising:

[0025] The sending module is used to send first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer, which is a timer maintained by the PDCP entity. The first information is used to adjust the value of the reordering timer, which is also a timer maintained by the PDCP entity.

[0026] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0027] This application embodiment also provides an information processing apparatus, the apparatus comprising:

[0028] The receiving module is used to acquire the first information sent by the RLC AM entity, the first information being related to the number of consecutive timeouts of the reassembly timer;

[0029] The processing module is used to adjust the value of the reordering timer according to the first information; and to trigger a wireless link failure (RLF) if the reordering timer times out.

[0030] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0031] Optionally, the processing module is used for:

[0032] According to the mapping relationship between the first preset value set and the second preset value set, the value of the reordering timer is adjusted to a target value. The target value is a preset value in the second preset value set that corresponds to the value of the first information. The first preset value set includes at least one first preset value of the first information, and the second preset value set includes at least one second preset value of the pre-configured reordering timer. The second preset value decreases as the first preset value increases.

[0033] This application embodiment also provides an information processing apparatus, the apparatus comprising:

[0034] The sending module is used to send first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer. The reassembly timer is a timer maintained by the PDCP entity.

[0035] The receiving module is used to acquire the first information sent by the RLC AM entity, the first information being related to the number of consecutive timeouts of the reassembly timer;

[0036] The processing module is used to adjust the value of the reordering timer according to the first information; and to trigger a wireless link failure (RLF) if the reordering timer times out.

[0037] This application also provides an information processing device, including: a transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; when the processor executes the program or instructions, it implements the steps in the information processing method described above.

[0038] This application also provides a readable storage medium storing a program or instructions thereon, which, when executed by a processor, implement the steps in the information processing method described above.

[0039] This application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the steps in the information processing method described above.

[0040] The beneficial effects of the above technical solution in this application are as follows:

[0041] In this embodiment, the RLC AM entity sends first information to the PDCP entity. This first information is related to the number of consecutive timeouts of the reordering timer. The PDCP entity adjusts the value of the reordering timer based on the first information. If the reordering timer times out, the PDCP entity triggers a Radio Link Failure (RLF). By dynamically adjusting the value of the PDCP's reordering timer using the aforementioned first information, and thus, when channel conditions are determined to be poor based on the first information, dynamically adjusting the reordering timer value can trigger an RLF more quickly for subsequent RRC reconstruction. This reduces RRC reconstruction latency under poor channel conditions and avoids ineffective and resource-wasting RLC retransmissions. Attached Figure Description

[0042] Figure 1 This is a schematic diagram illustrating the operation of the recombination timer and the reordering timer in the embodiments of this application;

[0043] Figure 2 This is a timeout diagram of the recombination timer and reordering timer in the embodiments of this application;

[0044] Figure 3 This is one of the flowcharts illustrating the information processing method according to an embodiment of this application;

[0045] Figure 4 This is a second schematic flowchart of the information processing method according to an embodiment of this application;

[0046] Figure 5 This is the third flowchart illustrating the information processing method according to an embodiment of this application;

[0047] Figure 6 This is one of the schematic diagrams of the information processing device according to an embodiment of this application;

[0048] Figure 7 This is a second schematic diagram of the information processing device according to an embodiment of this application;

[0049] Figure 8 This is a third schematic diagram of the information processing device according to an embodiment of this application;

[0050] Figure 9 This is one of the structural block diagrams of the information processing device according to an embodiment of this application;

[0051] Figure 10 This is a second structural block diagram of the information processing device according to an embodiment of this application. Detailed Implementation

[0052] To make the technical problems, technical solutions and advantages of this application clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments.

[0053] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0054] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "and / or" in the specification and claims indicates at least one of the connected objects; for example, the scope of protection of "A and / or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0055] In the various embodiments of this application, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0056] In addition, the terms "system" and "network" are often used interchangeably in this article.

[0057] In the embodiments provided in this application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0058] To enable those skilled in the art to better understand the embodiments of this application, the following description will be provided first.

[0059] In the existing RLC AM mode, both the RLC layer and PDCP layer at the receiver maintain a receive window, which is associated with a corresponding timer. In RLC AM mode, when the receiver's timer expires, it triggers data retransmission through status reporting; while in PDCP mode, when the timer expires, it directly discards the data update window. These will be described in detail below:

[0060] (1) RLC AM receiver processing procedure:

[0061] The t-Reassembly timer for RLC AM is maintained by the receiver. The receiver also maintains the following four variables: ① RX_Next: This variable indicates the SN+1 of the most recently fully received Acknowledged Mode Data Protocol Data Unit (AMD PDU), initially set to 0 (this is the lower boundary of the receive window; its value is only updated after the corresponding SDU is correctly received); ② RX_Next_Highest: This variable indicates the SN+1 of the AMD PDU with the highest sequence number (SN) among the received AMD PDUs, initially set to 0; ③ RX_Highest_Status: This variable indicates the highest possible SN that can be indicated by ACK_SN when constructing the STATUS PDU, initially set to 0 (this is the lower bound of the reassembly timer's detection range; the receiver will only report ACK / NACK for SDUs prior to this variable); ④ RX_Next_Status_Trigger: This variable indicates the SN+1 of the AMD PDU that triggers the reassembly timer (this is the upper bound of the detection range).

[0062] The reassembly timer starts when one of the following conditions is met: ① RX_Next_Highest > RX_Next+1; ② RX_Next_Highest = RX_Next+1, but the corresponding SDU segment is missing. When t-Reassembly is enabled, RX_Next_Status_Trigger is set to the SN corresponding to RX_Next_Highest.

[0063] The reassembly timer stops and resets when one of the following conditions is met: ① RX_Next_Status_Trigger = RX_Next; ② RX_Next_Status_Trigger = RX_Next + 1, and the corresponding SDU has no missing segments; ③ The RX_Next_Status_Trigger variable falls outside the receive window due to other reasons (excluding the case where it is equal to RX_Next + AM_Window_Size), where AM_Window_Size represents the size of the AM receive window.

[0064] After the re - assembly timer expires, the following actions are performed: ① Update the RX_Highest_Status variable to point to the first RLC SDU with SN≥RX_Next_Status_Trigger that has not been received yet; ② Determine whether to start again.

[0065] After the re - assembly timer expires, the receiving end determines that the data not received within the detection range is lost. After the lower boundary RX_Highest_Status is updated, the receiving end triggers a status report to feedback the data reception situation. This includes NACK / ACK for the AMD PDUs for which the re - assembly timer detection is completed. The NACK contains the SN of the lost PDU, and the indicated range is: RX_Next≤SN<RX_Highest_Status. The ACK is set to the next non - received SN outside the NACK range, indicating that all except the NACK have been received before. If the STATUS PDU fed back by the receiving end indicates that an RLC SDU or RLC SDU segment is NACK (meaning unsuccessful transmission), the sending end of the AM RLC entity will re - transmit it until the maximum re - transmission count triggers RLF.

[0066] (2) PDCP receiving - end processing procedure;

[0067] The re - ordering timer (t - Reordering timer) of PDCP is maintained by the receiving end. The receiving end maintains the following variables: ① RX_DELIV: A status variable of COUNT type, representing the minimum COUNT value in the PDUs that have been stored in the receive buffer but not yet passed to the upper layer, that is, the lower - bound value of the window; ② RX_NEXT: This variable records the COUNT value of the next PDCP SDU expected to be received, that is, the COUNT value of the received SDU in the current buffer plus one; ③ RX_REORD: This variable indicates the upper - bound of the re - ordering range.

[0068] When RX_NEXT>RX_DELIV, update RX_REORD to RX_NEXT and start the re - ordering timer. When a PDCP SDU with a COUNT value equal to RX_DELIV is received, PDCP delivers the consecutive SDUs in the buffer to the upper layer and updates RX_DELIV to the first non - received COUNT value. During the running time of the timer, if RX_DELIV≥RX_REORD, stop and reset the re - ordering timer; if RX_DELIV<RX_REORD, it is determined as timeout.

[0069] If the reordering timer times out, the following steps are taken: ① Submit all SDUs with a COUNT value less than RX_REORD to the higher layer; ② Submit consecutive SDUs with a COUNT value greater than or equal to RX_REORD to the higher layer; ③ Update RX_DELIV to the COUNT value of the first PDCP SDU that has not yet been submitted to the upper layer, and this COUNT value must be greater than or equal to RX_REORD. In other words, SDUs not previously received with RX_REORD are completely discarded.

[0070] In the existing RLC AM mode, both the RLC layer and the PDCP layer at the receiver maintain a receive window, which is associated with a corresponding timer. In RLC AM mode, when the receiver's timer expires, it triggers data retransmission by providing a status report; while when the PDCP layer's timer expires, it directly discards the data update window.

[0071] Assuming the SN field length (sn-FieldLength) is 3 bits, the receive window length is 4.

[0072] Consider the following process:

[0073] The receiving end receives AMD PDUs with SNs of 1 and 3 successively, triggering the t-Reassembly timer and the t-Reordering timer. The positions of the variables are as follows: Figure 1 As shown.

[0074] t-Reassembly timer timeout, t-Reordering timer timeout, such as Figure 2 As shown. At this point, the RLC layer starts retransmitting, but the PDCP layer has already updated its window, so even if an SDU with SN=0 is submitted to it later, it will be discarded.

[0075] Existing problems:

[0076] (1) If the PDCP layer timer is configured too large, although the PDCP receive window will not slide before the RLC layer completes the maximum number of retransmissions, this will bring a very large data transmission delay.

[0077] (2) If the PDCP layer timer is configured too small, that is, before the RLC layer completes the maximum number of retransmissions, the PDCP layer will slide the window due to the timer timeout, while the RLC layer is still retransmitting. However, in this case, even if the PDCP subsequently receives the corresponding SDU submitted by the RLC, it will discard it directly. Therefore, after the t-Reordering timer times out, the retransmission performed by the RLC layer is a waste of resources and meaningless.

[0078] (3) In the current RLC AM protocol, the number of data retransmissions is recorded by the sender, and the RLF is only triggered by the sender after the maximum number of retransmissions is reached. When the channel conditions are poor, this inflexible mechanism will result in a very large reconstruction delay, because before a certain SDU reaches the maximum number of retransmissions, other SDUs may have already had many retransmissions.

[0079] Therefore, how to reduce data transmission latency and resource waste caused by invalid retransmissions under RLC AM is an issue that needs to be considered.

[0080] like Figure 3 As shown in the figure, this application provides an information processing method, including:

[0081] Step 301: The Radio Link Control Acknowledgment Mode (RLC AM) entity sends first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reordering timer, which is a timer maintained by the PDCP entity. The first information is used to adjust the value of the reordering timer, which is also a timer maintained by the PDCP entity.

[0082] The reassembly timer is the t-Reassembly timer mentioned above. The reordering timer is the t-Reordering timer.

[0083] In the embodiments of this application, the RLC AM entity and PDCP entity are the RLC AM entity and PDCP entity of the receiving device or receiving end, which is a terminal or network-side device.

[0084] The aforementioned first information is related to the number of consecutive timeouts of the recombination timer. This first information can reflect the channel quality. For example, the more consecutive timeouts within a certain period of time, the worse the channel quality.

[0085] In this embodiment, the RLC AM entity sends first information to the PDCP entity. This first information is related to the number of consecutive timeouts of the reordering timer. The PDCP entity adjusts the value of the reordering timer based on the first information. If the reordering timer times out, the PDCP entity triggers a Radio Link Failure (RLF). By dynamically adjusting the value of the PDCP's reordering timer using the aforementioned first information, and thus, when channel conditions are determined to be poor based on the first information, dynamically adjusting the reordering timer value can trigger an RLF more quickly for subsequent RRC reconstruction. This reduces RRC reconstruction latency under poor channel conditions and avoids ineffective and resource-wasting RLC retransmissions.

[0086] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0087] Optionally, send first information to the Packet Data Convergence Protocol (PDCP) entity, including:

[0088] The first information is sent to the PDCP entity at preset intervals.

[0089] In related technologies, the retransmission count is recorded individually for each SDU when the transmitting end. The Retransmission Response Function (RLF) is only triggered when a particular SDU reaches its maximum retransmission count. However, the receiving end's Retransmission Response Center (RLC) and Access Center (AM) entities cannot accurately know the retransmission count for a specific SDU. Therefore, recording the consecutive timeouts of the receiving end's t-Reassembly timer could be considered. When the timer times out consecutively, it can be determined that the receiving window has stalled, and channel quality is deteriorating. The time factor should also be considered, specifically the number of consecutive timeouts occurring at the receiving end within time T (the aforementioned preset period).

[0090] Therefore, this application embodiment considers configuring the RLC AM entity as follows:

[0091] a) Define a variable RX_Continuous_Expire, which records the number of consecutive timeouts of the t-Reassembly timer and is reset along with it when the t-Reassembly timer is reset.

[0092] b) Pre-configure the continuous number threshold value α (i.e., the preset threshold mentioned above), and define the variable RX_Accumulation_Expire (initial value is 0). When RX_Continuous_Expire>α, RX_Accumulation_Expire=RX_Accumulation_Expire+1.

[0093] The RX_Accumulation_Expire can be understood as the first piece of information mentioned above, and the RX_Continuous_Expire>α can be understood as the target event mentioned above.

[0094] c) Pre-configure period T, every period T, the RLC AM entity reports RX_Accumulation_Expire to the PDCP entity.

[0095] d) On the network side, in messages such as RRC Setup and RRC Reconfiguration, the threshold value α and period T are issued through RLC-Config.

[0096] In this embodiment, the RLC AM entity records the number of consecutive timeouts of the reordering timer and uses this to determine the channel quality, thereby dynamically changing the value of the t-Reordering timer after the next reset.

[0097] like Figure 4 As shown in the figure, this application provides an information processing method, including:

[0098] Step 401: The PDCP entity obtains the first information sent by the RLC AM entity, which is related to the number of consecutive timeouts of the reassembly timer.

[0099] In the embodiments of this application, the RLC AM entity and PDCP entity are the RLC AM entity and PDCP entity of the receiving device or receiving end, which is a terminal or network-side device.

[0100] The aforementioned first information is related to the number of consecutive timeouts of the recombination timer. This first information can reflect the channel quality. For example, the more consecutive timeouts within a certain period of time, the worse the channel quality.

[0101] Step 402: The PDCP entity adjusts the value of the reordering timer according to the first information;

[0102] Step 403: The PDCP entity triggers a Radio Link Failure (RLF) if the reordering timer times out.

[0103] In this embodiment, the PDCP entity obtains first information sent by the RLC AM entity, the first information being related to the number of consecutive timeouts of the reordering timer; based on the first information, the value of the reordering timer is adjusted; and if the reordering timer times out, a Radio Link Failure (RLF) is triggered. When channel conditions are determined to be poor based on the aforementioned first information, dynamically adjusting the value of the reordering timer allows for faster triggering of the RLF for subsequent RRC reconstruction, thereby reducing RRC reconstruction latency under poor channel conditions and avoiding ineffective and resource-wasting RLC retransmissions.

[0104] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0105] This first piece of information has been described in detail in the above-described method embodiments for the RLC AM entity side, and will not be repeated here.

[0106] Optionally, based on the first information, the value of the reordering timer is adjusted, including:

[0107] According to the mapping relationship between the first preset value set and the second preset value set, the value of the reordering timer is adjusted to a target value. The target value is a preset value in the second preset value set that corresponds to the value of the first information. The first preset value set includes at least one first preset value of the first information, and the second preset value set includes at least one second preset value of the pre-configured reordering timer. The second preset value decreases as the first preset value increases.

[0108] In this embodiment of the application, the first preset value set may also be at least one preset value range. Optionally, each preset value range corresponds to a second preset value.

[0109] Optionally, the PDCP entity acquires the first information sent by the RLC AM entity, including:

[0110] The PDCP entity acquires the first information sent by the RLC AM entity at preset intervals.

[0111] In this embodiment, the PDCP entity can dynamically adjust the value of the t-Reordering timer based on the RX_Accumulation_Expire reported by the RLC AM entity and the network conditions.

[0112] Therefore, consider configuring the PDCP entity as follows:

[0113] (1) A list of t-Reordering values ​​is pre-configured, arranged in ascending order, denoted as t-Reordering∈{t1,t2,…,∞}.

[0114] The list of t-Reordering values ​​is the second preset value set mentioned above. t-Reordering can be understood as the second preset value set mentioned above.

[0115] (2) Select the t-Reordering timer value based on the reported RX_Accumulation_Expire. The selection method is as follows: If N t-Reordering values ​​are configured, then RX_Accumulation_Expire can be divided into N segments, i.e., N first preset value intervals are determined. Thus, a mapping relationship is established between the N first preset value intervals and the N t-Reordering values. Based on this mapping relationship and the reported RX_Accumulation_Expire, the t-Reordering timer value is selected. Among them, as the value of the first preset value interval increases, the t-Reordering value decreases.

[0116] (3) When the t-Reordering timer of the PDCP entity corresponding to the RLC AM entity times out, the RLF is triggered directly.

[0117] (4) The network side sends the t-Reordering value list through PDCP-Config in messages such as RRCSetup and RRCReconfiguration.

[0118] In this embodiment of the application, under poor channel conditions, by dynamically adjusting the value of the t-Reordering timer, the RLF can be triggered more quickly to perform subsequent RRC re-establishment.

[0119] In the above scheme, a list of t-Reordering timers is pre-configured. At the receiving end, the RLC AM entity defines a variable to record the consecutive timeouts of the t-Reassembly timer. This is used to determine channel quality and dynamically adjust the t-Reordering timer value after the next reset. Simultaneously, an RLF is triggered after the t-Reordering timer expires. This reduces RRC reconstruction delay under poor channel conditions and avoids ineffective and resource-wasting RLC retransmissions.

[0120] like Figure 5 As shown, this application embodiment provides an information processing method, executed by a receiving device or receiving end, the method including:

[0121] Step 501: The RLC AM entity sends first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer. The reassembly timer is a timer maintained by the PDCP entity.

[0122] Step 501 has been described in detail in the method embodiment on the RLC AM entity side, and will not be repeated here.

[0123] Step 502: The PDCP entity obtains the first information sent by the RLC AM entity.

[0124] Step 503: The PDCP entity adjusts the value of the reordering timer according to the first information. The reordering timer is a timer maintained by the PDCP entity.

[0125] Step 504: The PDCP entity triggers RLF if the reordering timer times out.

[0126] Steps 502 and 504 have been described in detail in the method embodiments on the PDCP entity side, and will not be repeated here.

[0127] In this embodiment, the RLC AM entity sends first information to the PDCP entity. This first information is related to the number of consecutive timeouts of the reordering timer. The PDCP entity adjusts the value of the reordering timer based on the first information. If the reordering timer times out, the PDCP entity triggers a Radio Link Failure (RLF). By dynamically adjusting the value of the PDCP's reordering timer using the aforementioned first information, and thus, when channel conditions are determined to be poor based on the first information, dynamically adjusting the reordering timer value can trigger an RLF more quickly for subsequent RRC reconstruction. This reduces RRC reconstruction latency under poor channel conditions and avoids ineffective and resource-wasting RLC retransmissions.

[0128] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0129] This first piece of information has been described in detail in the above method embodiments and will not be repeated here.

[0130] Optionally, send first information to the Packet Data Convergence Protocol (PDCP) entity, including:

[0131] The first information is sent to the PDCP entity at preset intervals.

[0132] Optionally, based on the first information, the value of the reordering timer is adjusted, including:

[0133] According to the mapping relationship between the first preset value set and the second preset value set, the value of the reordering timer is adjusted to a target value. The target value is a preset value in the second preset value set that corresponds to the value of the first information. The first preset value set includes at least one first preset value of the first information, and the second preset value set includes at least one second preset value of the pre-configured reordering timer. The second preset value decreases as the first preset value increases.

[0134] Optionally, the PDCP entity acquires the first information sent by the RLC AM entity, including:

[0135] The PDCP entity acquires the first information sent by the RLC AM entity at preset intervals.

[0136] This application provides a method for configuring a PDCP entity t-Reordering timer. A t-Reordering timer list is pre-configured. A variable is defined in the receiver's RLC AM entity to record the number of consecutive timeouts of the t-Reassembly timer. This number is used to determine channel quality and dynamically change the t-Reordering timer value after the next reset. Simultaneously, an RLF is triggered after the t-Reordering timer expires. This reduces RRC reconstruction delay under poor channel conditions and avoids ineffective and resource-wasting RLC retransmissions.

[0137] like Figure 6 As shown in the figure, this application embodiment also provides an information processing apparatus, the apparatus comprising:

[0138] The sending module 601 is used to send first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer. The reassembly timer is a timer maintained by the PDCP entity. The first information is used to adjust the value of the reordering timer, which is also a timer maintained by the PDCP entity.

[0139] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0140] Optionally, the sending module is used to send the first information to the PDCP entity at preset intervals.

[0141] In this embodiment, the RLC AM entity sends first information to the PDCP entity. This first information is related to the number of consecutive timeouts of the reordering timer. The PDCP entity adjusts the value of the reordering timer based on the first information. If the reordering timer times out, the PDCP entity triggers a Radio Link Failure (RLF). By dynamically adjusting the value of the PDCP's reordering timer using the aforementioned first information, and thus, when channel conditions are determined to be poor based on the first information, dynamically adjusting the reordering timer value can trigger an RLF more quickly for subsequent RRC reconstruction. This reduces RRC reconstruction latency under poor channel conditions and avoids ineffective and resource-wasting RLC retransmissions.

[0142] like Figure 7 As shown in the figure, this application embodiment also provides an information processing apparatus, the apparatus comprising:

[0143] The receiving module 701 is used to obtain the first information sent by the RLC AM entity, the first information being related to the number of consecutive timeouts of the reassembly timer;

[0144] The processing module 702 is used to adjust the value of the reordering timer according to the first information; and to trigger a wireless link failure (RLF) if the reordering timer times out.

[0145] Optionally, the first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

[0146] Optionally, the processing module is used for:

[0147] According to the mapping relationship between the first preset value set and the second preset value set, the value of the reordering timer is adjusted to a target value. The target value is a preset value in the second preset value set that corresponds to the value of the first information. The first preset value set includes at least one first preset value of the first information, and the second preset value set includes at least one second preset value of the pre-configured reordering timer. The second preset value decreases as the first preset value increases.

[0148] Optionally, the receiving module is used to acquire the first information sent by the RLC AM entity at preset intervals.

[0149] In this embodiment, the PDCP entity obtains first information sent by the RLC AM entity, the first information being related to the number of consecutive timeouts of the reordering timer; based on the first information, the value of the reordering timer is adjusted; and if the reordering timer times out, a Radio Link Failure (RLF) is triggered. When channel conditions are determined to be poor based on the aforementioned first information, dynamically adjusting the value of the reordering timer allows for faster triggering of the RLF for subsequent RRC reconstruction, thereby reducing RRC reconstruction latency under poor channel conditions and avoiding ineffective and resource-wasting RLC retransmissions.

[0150] like Figure 8 As shown in the figure, this application embodiment also provides an information processing apparatus, the apparatus comprising:

[0151] The sending module 801 is used to send first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer. The reassembly timer is a timer maintained by the PDCP entity.

[0152] The receiving module 802 is used to obtain the first information sent by the RLC AM entity, the first information being related to the number of consecutive timeouts of the reassembly timer;

[0153] The processing module 803 is used to adjust the value of the reordering timer according to the first information; and to trigger a wireless link failure (RLF) if the reordering timer times out.

[0154] Optionally, the sending module is used to send the first information to the PDCP entity at preset intervals.

[0155] Optionally, the receiving module is used to acquire the first information sent by the RLC AM entity at preset intervals.

[0156] Optionally, the processing module is used to adjust the value of the reordering timer to a target value according to the mapping relationship between the first preset value set and the second preset value set. The target value is a preset value in the second preset value set that corresponds to the value of the first information. The first preset value set includes at least one first preset value of the first information, and the second preset value set includes at least one second preset value of the pre-configured reordering timer. The second preset value decreases as the first preset value increases.

[0157] It should be noted that this device is the same as the device described in the above method embodiments. All implementations of the above method embodiments can be applied to this device embodiment and achieve the same technical effect, which will not be repeated here.

[0158] This application provides an information processing device, such as... Figure 9 As shown, the device includes a transceiver 910, a processor 900, a memory 920, and a program or instructions stored in the memory 920 and executable on the processor 900; when the processor 900 executes the program or instructions, it implements the steps of the aforementioned information processing method. This information processing device can be an electronic device, such as a terminal, computer, or user equipment.

[0159] The transceiver 910 is used to receive and send data under the control of the processor 900.

[0160] Among them, Figure 9In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 900 and memory represented by memory 920 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 910 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, user interface 930 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0161] The processor 900 is responsible for managing the bus architecture and general processing, while the memory 920 can store the data used by the processor 900 during operation.

[0162] This application provides an information processing device, such as... Figure 10 As shown, it includes a transceiver 1010, a processor 1000, a memory 1020, and a program or instructions stored in the memory 1020 and executable on the processor 1000; when the processor 1000 executes the program or instructions, it implements the steps of the above-described information processing method.

[0163] The transceiver 1010 is used to receive and send data under the control of the processor 1000.

[0164] Among them, Figure 10 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1000) and memory (memory 1020). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1010 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. The processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 may store data used by the processor 1000 during operation.

[0165] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the steps in the information processing method described above and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0166] This application also provides a computer program product, including computer instructions. When executed by a processor, the computer instructions implement the various processes of the above-described information processing method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0167] The processor is the processor in the information processing device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0168] It should be further noted that the terminals described in this specification include, but are not limited to, smartphones, tablets, etc., and many of the functional components described are referred to as modules in order to more specifically emphasize the independence of their implementation.

[0169] In this embodiment, the module can be implemented in software so that it can be executed by various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of computer instructions, which may be constructed as objects, procedures, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but may include different instructions stored in different bits, which, when logically combined, constitute the module and achieve the module's intended purpose.

[0170] In practice, an executable code module can be a single instruction or many instructions, and can even be distributed across multiple different code segments, different programs, and across multiple memory devices. Similarly, operational data can be identified within the module and can be implemented in any suitable form and organized within any suitable type of data structure. This operational data can be collected as a single dataset or distributed across different locations (including different storage devices), and can exist, at least in part, solely as electronic signals within the system or network.

[0171] When a module can be implemented using software, considering the current level of hardware technology, modules that can be implemented in software can be implemented using hardware circuits by those skilled in the art to achieve the corresponding functions, without considering cost. These hardware circuits include conventional very-large-scale integrated circuits (VLSI) or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules can also be implemented using programmable hardware devices, such as field-programmable gate arrays, programmable array logic, and programmable logic devices.

[0172] The exemplary embodiments described above are with reference to the accompanying drawings. Many different forms and embodiments are feasible without departing from the spirit and teachings of this application. Therefore, this application should not be construed as limiting the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided to make this application complete and convey the scope of this application to those skilled in the art. In these drawings, component dimensions and relative dimensions may be exaggerated for clarity. The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. As used herein, unless clearly indicated otherwise, the singular forms “a,” “an,” and “the” are intended to include all such forms. It will be further understood that the terms “comprising” and / or “including”, when used in this specification, indicate the presence of the stated features, integers, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, integers, steps, operations, components, and / or groups thereof. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of the range and any subranges in between.

[0173] The above description is the preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. An information processing method, characterized in that, include: The Radio Link Control Acknowledgment Mode (RLC AM) entity sends a first message to the Packet Data Convergence Protocol (PDCP) entity. The first message is related to the number of consecutive timeouts of the reordering timer, which is a timer maintained by the PDCP entity. The first message is used to adjust the value of the reordering timer, which is also a timer maintained by the PDCP entity.

2. The method according to claim 1, characterized in that, The first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

3. The method according to claim 1 or 2, characterized in that, Send the first message to the Packet Data Convergence Protocol (PDCP) entity, including: The first information is sent to the PDCP entity at preset intervals.

4. An information processing method, characterized in that, include: The PDCP entity obtains the first information sent by the RLC AM entity, which is related to the number of consecutive timeouts of the reassembly timer; The PDCP entity adjusts the value of the reordering timer based on the first information; The PDCP entity triggers a Radio Link Failure (RLF) if the reordering timer times out.

5. The method according to claim 4, characterized in that, The first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

6. The method according to claim 4 or 5, characterized in that, Based on the first information, adjust the value of the reordering timer, including: According to the mapping relationship between the first preset value set and the second preset value set, the value of the reordering timer is adjusted to a target value. The target value is a preset value in the second preset value set that corresponds to the value of the first information. The first preset value set includes at least one first preset value of the first information, and the second preset value set includes at least one second preset value of the pre-configured reordering timer. The second preset value decreases as the first preset value increases.

7. The method according to claim 4, characterized in that, The PDCP entity obtains the first information sent by the RLC AM entity, including: The PDCP entity acquires the first information sent by the RLC AM entity at preset intervals.

8. An information processing method, characterized in that, include: The RLC AM entity sends first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer. The reassembly timer is a timer maintained by the PDCP entity. The PDCP entity receives the first message sent by the RLC AM entity; The PDCP entity adjusts the value of the reordering timer based on the first information. The reordering timer is a timer maintained by the PDCP entity. The PDCP entity triggers RLF if the reordering timer times out.

9. The method according to claim 8, characterized in that, The first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

10. An information processing device, characterized in that, The device includes: The sending module is used to send first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer, which is a timer maintained by the PDCP entity. The first information is used to adjust the value of the reordering timer, which is also a timer maintained by the PDCP entity.

11. The apparatus according to claim 10, characterized in that, The first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

12. An information processing device, characterized in that, The device includes: The receiving module is used to acquire the first information sent by the RLC AM entity, the first information being related to the number of consecutive timeouts of the reassembly timer; The processing module is used to adjust the value of the reordering timer according to the first information; and to trigger a wireless link failure (RLF) if the reordering timer times out.

13. The apparatus according to claim 12, characterized in that, The first information is used to indicate the number of times a target event occurs within a preset period, wherein the target event is an event in which the number of consecutive timeouts of the recombination timer exceeds a preset threshold.

14. The apparatus according to claim 12 or 13, characterized in that, The processing module is used for: According to the mapping relationship between the first preset value set and the second preset value set, the value of the reordering timer is adjusted to a target value. The target value is a preset value in the second preset value set that corresponds to the value of the first information. The first preset value set includes at least one first preset value of the first information, and the second preset value set includes at least one second preset value of the pre-configured reordering timer. The second preset value decreases as the first preset value increases.

15. An information processing device, characterized in that, The device includes: The sending module is used to send first information to the Packet Data Convergence Protocol (PDCP) entity. The first information is related to the number of consecutive timeouts of the reassembly timer. The reassembly timer is a timer maintained by the PDCP entity. The receiving module is used to acquire the first information sent by the RLC AM entity, the first information being related to the number of consecutive timeouts of the reassembly timer; The processing module is used to adjust the value of the reordering timer according to the first information; and to trigger a wireless link failure (RLF) if the reordering timer times out.

16. An information processing device, comprising: A transceiver, a processor, a memory, and a program or instructions stored in the memory and executable on the processor; characterized in that, when the processor executes the program or instructions, it implements the steps of the information processing method as claimed in any one of claims 1 to 3, or implements the steps of the information processing method as claimed in any one of claims 4 to 7, or implements the steps of the information processing method as claimed in any one of claims 8 to 9.

17. A readable storage medium having a program or instructions stored thereon, characterized in that, When the program or instructions are executed by the processor, they implement the steps of the information processing method as described in any one of claims 1 to 3, or implement the steps of the information processing method as described in any one of claims 4 to 7, or implement the steps of the information processing method as described in any one of claims 8 to 9.

18. A computer program product, characterized in that, The method includes computer instructions that, when executed by a processor, implement the steps of the information processing method as described in any one of claims 1 to 3, or implement the steps of the information processing method as described in any one of claims 4 to 7, or implement the steps of the information processing method as described in any one of claims 8 to 9.