Wireless link data processing method and device and storage medium

Abstract

The invention relates to a method and device for processing radio link data and a storage medium, and the method comprises the steps: triggering radio link control (RRC) reconnection in a first cell where a terminal device currently resides under the condition that a first radio link is caused to be RLF due to the failure of a first random access channel (RACH) in the first cell; under the condition that the RRC reconnection is successful, determining whether to reconfigure a data radio bearer DRB for the terminal equipment; if the DRB is not reconfigured for the terminal equipment, searching a second cell in a preset range, and acquiring DRB configuration information from the second cell; and configuring the DRB for the terminal equipment based on the DRB configuration information. According to the method and the device, the conditions of network disconnection and insufficient uplink resources caused by the fact that the DRB is not reconfigured for the terminal equipment can be reduced; therefore, the stability of data transmission of the terminal equipment is improved, and the user experience is ensured.

Description

Technical Field

[0001] The present disclosure relates to the field of information technology, and in particular to a method, device, and storage medium for processing wireless link data. Background Art

[0002] Radio link failure (RLF) is a critical process that triggers radio resource control (RRC) re-establishment. RLF occurs when physical layer downlink out-of-synchronization (OOS) occurs, random access issues occur in the MAC, or the maximum number of automatic repeat request (ARQ) retransmissions is reached in the radio link control (RLC).

[0003] A data radio bearer (DRB) is a logical channel used to transmit data. It is established after the RRC connection is established. Therefore, when the RRC connection is reestablished, the established DRB still exists and does not need to be reestablished. However, during RRC reestablishment, the network side generally reconfigures the DRB. If the network side does not synchronize the DRB configuration information to the terminal device, the terminal device will continue to use the previous DRB, which can easily cause data problems, such as network disconnection and insufficient uplink resources allocated by the network. Summary of the Invention

[0004] To overcome the problems existing in the related art, the present disclosure provides a method, device and storage medium for processing wireless link data, so as to overcome the problems of network disconnection and insufficient uplink resources caused by failure to reconfigure DRB for terminal devices.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for processing radio link data is provided, the method comprising: when a terminal device causes a first RLF due to a RACH failure in a first cell currently residing, triggering an RRC reconnection in the first cell;

[0006] If the RRC reconnection is successful, determining whether to reconfigure the DRB for the terminal device;

[0007] If the DRB is not reconfigured for the terminal device, searching for a second cell within a preset range and obtaining DRB configuration information from the second cell;

[0008] Based on the DRB configuration information, configure DRB for the terminal device.

[0009] In some embodiments, when a first RLF is caused by a first RACH failure in a first cell currently camped on by the terminal device, triggering an RRC reconnection in the first cell includes:

[0010] When the first RLF is caused by a first RACH failure in the first cell currently being resided by the terminal device, triggering a first RRC reconnection in the first cell;

[0011] When the RRC reconnection is successful, determining whether to reconfigure a data radio bearer (DRB) for the terminal device includes:

[0012] In case the first RRC reconnection is successful, determine whether to reconfigure the data radio bearer DRB for the terminal device.

[0013] In some embodiments, when the first RRC reconnection is successful, determining whether to reconfigure a DRB for the terminal device includes:

[0014] When the first RRC reconnection is successful, determining a number of second RACH failures due to a preset reason;

[0015] When the number of failures is greater than or equal to a preset first threshold, controlling the terminal device to trigger a second RLF;

[0016] When the second RLF is successfully triggered, triggering a second RRC reconnection in the first cell;

[0017] If the second RRC reconnection is successful, determining whether to reconfigure a DRB for the terminal device;

[0018] The preset reason includes: the terminal device does not receive a random access response message or a contention resolution message.

[0019] In some embodiments, the method further comprises:

[0020] If the DRB is not reconfigured for the terminal device, the accumulated number of times the DRB is not reconfigured for the terminal device is updated.

[0021] In some embodiments, the method further comprises:

[0022] If the RRC reconnection is successful, determining whether the cumulative number of times that the first cell does not reconfigure the DRB for the terminal device is greater than or equal to a preset second threshold;

[0023] When the accumulated number of times is greater than or equal to the second threshold, the second cell is searched and DRB configuration information is acquired from the second cell.

[0024] In some embodiments, when the first RRC reconnection is successful, determining the number of second RACH failures due to a preset reason includes:

[0025] If the first RRC reconnection is successful, marking the first cell;

[0026] triggering the second RACH based on the flag and initializing the number of RACH failures;

[0027] A reason causing the second RACH failure is determined, and a number of failures resulting from the second RACH failure due to the preset reason is determined.

[0028] In some embodiments, the method further comprises:

[0029] If the first RRC reconnection is successful, determining whether the second RACH is successful;

[0030] If the second RACH is successful and the number of second RACH failures due to a preset reason is less than a preset first threshold, the number of second RACH failures is reset to 0.

[0031] According to a second aspect of an embodiment of the present disclosure, a device for processing wireless link data is provided, the device including:

[0032] A reconnection module, configured to trigger a radio link control RRC reconnection in a first cell where the terminal device is currently residing, when a first radio link failure RLF occurs due to a first random access RACH failure;

[0033] A determination module, configured to determine whether to reconfigure a data radio bearer (DRB) for the terminal device if the RRC reconnection is successful;

[0034] an acquisition module, configured to search for a second cell within a preset range and acquire DRB configuration information from the second cell if the DRB is not reconfigured for the terminal device;

[0035] A configuration module is configured to configure DRB for the terminal device based on the DRB configuration information.

[0036] In some embodiments, the reconnection apparatus is configured to trigger a first RRC reconnection in the first cell when the terminal device causes the first RLF due to a first RACH failure in the first cell currently camped on;

[0037] The determining device is configured to determine whether to reconfigure the data radio bearer DRB for the terminal device when the first RRC reconnection is successful.

[0038] In some embodiments, the determining means is configured to determine, when the first RRC reconnection is successful, a number of failures resulting in the second RACH failure due to a preset reason;

[0039] The reconnection module is configured to control the terminal device to trigger a second RLF when the number of failures is greater than or equal to a preset first threshold; and trigger a second RRC reconnection in the first cell when the second RLF is successfully triggered;

[0040] The determining means is configured to determine whether to reconfigure a DRB for the terminal device if the second RRC reconnection is successful;

[0041] The preset reason includes: the terminal device does not receive a random access response message or a contention resolution message.

[0042] In some embodiments, the apparatus further comprises:

[0043] The updating module is configured to update the accumulated number of times that the DRB is not reconfigured for the terminal device if the DRB is not reconfigured for the terminal device.

[0044] In some embodiments, the determining module is configured to determine, when the RRC reconnection is successful, whether the cumulative number of times that the first cell does not reconfigure the DRB for the terminal device is greater than or equal to a preset second threshold;

[0045] The acquisition module is configured to search for the second cell and acquire DRB configuration information from the second cell when the accumulated number of times is greater than or equal to the second threshold.

[0046] In some embodiments, the apparatus further comprises:

[0047] a marking module, configured to mark the first cell when the first RRC reconnection is successful;

[0048] an initialization module configured to trigger the second RACH based on the flag and initialize the number of RACH failures;

[0049] The determining module is configured to determine a reason causing the second RACH failure, and determine a number of failures resulting from the preset reason causing the second RACH failure.

[0050] In some embodiments, the determining module is configured to determine whether the second RACH is successful if the first RRC reconnection is successful;

[0051] The resetting module is configured to reset the number of second RACH failures to 0 if the second RACH succeeds and the number of second RACH failures due to a preset reason is less than a preset first threshold.

[0052] According to a third aspect of an embodiment of the present disclosure, a device for processing wireless link data is provided, including:

[0053] processor;

[0054] a memory configured to store processor-executable instructions;

[0055] The processor is configured to implement the steps of any one of the wireless link data processing methods in the first aspect when executing.

[0056] According to the fourth aspect of an embodiment of the present disclosure, a non-temporary computer-readable storage medium is provided. When the instructions in the storage medium are executed by a processor of a wireless link data processing device, the device is capable of executing any one of the wireless link data processing methods described in the first aspect above.

[0057] The technical solutions provided by the embodiments of the present disclosure may have the following beneficial effects:

[0058] In the present disclosure, after the RRC reconnection is successful, the terminal device first determines whether to reconfigure the DRB for the terminal device. If the DRB is not reconfigured for the terminal device, it searches for the second cell within the preset range, obtains the DRB configuration information in the second cell, and configures the DRB for the terminal device based on the DRB configuration information. In this way, the network disconnection and insufficient uplink resources caused by the failure to reconfigure the DRB for the terminal device can be reduced; thereby improving the stability of the terminal device's data transmission and ensuring the user experience.

[0059] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0061] Figure 1 The flow chart of a method for processing wireless link data according to an exemplary embodiment is shown as follows Figure 1 ;

[0062] Figure 2 This is a diagram showing that the network side has not reconfigured DRB for the terminal device;

[0063] Figure 3 The flow chart of a method for processing wireless link data according to an exemplary embodiment is shown as follows Figure 2 ;

[0064] Figure 4 The flow chart of a method for processing wireless link data according to an exemplary embodiment is shown as follows Figure 3 ;

[0065] Figure 5 This is a block diagram of a device for processing wireless link data according to an exemplary embodiment;

[0066] Figure 6 FIG. 6 is a hardware structure block diagram of a device 600 for processing wireless link data according to an exemplary embodiment. DETAILED DESCRIPTION

[0067] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0068] Figure 1 The flow chart of a method for processing wireless link data according to an exemplary embodiment is shown as follows Figure 1 ,like Figure 1 As shown, the method can be applied to a terminal device, and the method mainly includes the following steps:

[0069] In step 101, when a first radio link failure (RLF) occurs in a first cell in which the terminal device is currently residing due to a first random access channel (RACH) failure, the terminal device triggers a radio link control (RRC) reconnection in the first cell;

[0070] In step 102, if the RRC reconnection is successful, determine whether to reconfigure the DRB for the terminal device;

[0071] In step 103, if the DRB is not reconfigured for the terminal device, searching for a second cell within a preset range and obtaining DRB configuration information from the second cell;

[0072] In step 104, a DRB is configured for the terminal device based on the DRB configuration information.

[0073] Here, terminal devices may include mobile terminals, fixed terminals, or vehicle-mounted terminals, for example, mobile phones, tablet computers, virtual reality (VR) devices, augmented reality (AR) devices, drones, 3D game consoles, monitoring systems, personal digital assistants (PDAs), wearable devices, smart speakers, digital recorders, electronic toys, etc.

[0074] In some embodiments, as Figure 2 As shown, Figure 2 This is a diagram showing that the network side has not reconfigured DRB for the terminal device. Figure 2 As shown in the figure, after an RLF occurs, the terminal device will perform RRC reestablishment. If the network side does not reconfigure the DRB for the terminal device, data uplink anomalies will occur, affecting the user experience. Among them, the DRB is the channel for actual data transmission on the terminal device.

[0075] In an embodiment of the present disclosure, the terminal device performs a first RACH in the first cell in which it is currently located. If the first RACH fails and causes RLF, the terminal device can perform RRC reconnection in the first cell. If, after completing the RRC reestablishment, the first cell does not reconfigure the DRB for the terminal device, a neighboring cell (i.e., a second cell within a preset range) can be searched to reconfigure the DRB for the terminal device in the neighboring cell.

[0076] In some embodiments, when the terminal device fails to perform a first RACH in the first cell where it is currently residing, and the first RACH causes the terminal device to have an RLF, the terminal device may trigger an RRC reconnection.

[0077] In some embodiments, when the RRC reconnection triggered by the terminal device is successful, it can be determined whether the network side reconfigures the DRB for the terminal device. If the network side does not reconfigure the DRB for the terminal device, the terminal device can search for a second cell within a preset range and obtain DRB configuration information from the second cell.

[0078] In other implementations, when the RRC reconnection triggered by the terminal device is successful, it can be determined whether the network side has reconfigured the DRB for the terminal device. If the network side has reconfigured the DRB for the terminal device, no action is taken.

[0079] In the disclosed embodiments, the second cell within the preset range is a cell adjacent to the first cell. The second cell and the first cell can be different cells under the same base station, or different cells under different base stations. This is not specifically limited in the disclosed embodiments. When the second cell and the first cell are different cells under different base stations, the second cell must meet certain conditions, such as signal strength and frequency resources.

[0080] In some embodiments, the terminal device may configure a DRB for the terminal device based on the DRB configuration information obtained from the second cell.

[0081] It can be understood that after the terminal device obtains the DRB configuration information for configuring the DRB from the second cell, it can configure the DRB based on the DRB configuration information, and then use the configured DRB to transmit data to achieve communication between the terminal device and the network side (such as the base station).

[0082] In some embodiments, after the RRC reconnection is successful, the terminal device can send a request message for obtaining the DRB configuration information corresponding to the second cell to the network side to which the second cell belongs based on the RRC connection. In response to the request message, the network side sends the DRB configuration information to the terminal device so that the terminal device can configure the DRB based on the DRB configuration information.

[0083] In some embodiments, after obtaining DRB configuration information from the second cell, the terminal device may configure the DRB based on the DRB configuration information. At the same time, the terminal device switches (hands over) from the first cell to the second cell.

[0084] It is understandable that when the first cell does not reconfigure the DRB for the terminal device, the first cell will not be able to continue to provide services to the terminal device, that is, the terminal device will not be able to transmit data in the first cell. In order not to interrupt the ongoing services of the terminal device, the terminal device will switch to the second cell after obtaining the DRB configuration information from the second cell, and the second cell will continue to provide services to the terminal device, thereby achieving seamless coverage of the wireless network.

[0085] In an embodiment of the present disclosure, the DRB configuration information may include at least one of the following information or a combination thereof: service data adaptation protocol (SDAP) configuration information, packet data convergence protocol (PDCP) configuration information, radio link layer control protocol (RLC) configuration information, logical channel configuration information, RLC bearer configuration information, logical channel ID, DRB ID, and DRB configuration information identifier, etc.

[0086] In an embodiment of the present disclosure, the difference between the DRB configuration information provided by the first cell and the DRB configuration information provided by the second cell includes at least one of the following: SDAP, PDCP, RLC logical channel configuration information, RLC bearer configuration information, logical channel ID, DRB ID and DRB configuration information identifier.

[0087] In the embodiment of the present disclosure, after the RRC reconnection is successful, the terminal device first determines whether to reconfigure the DRB for the terminal device. If the DRB is not reconfigured for the terminal device, it searches for a second cell within a preset range, obtains DRB configuration information in the second cell, and configures the DRB for the terminal device based on the DRB configuration information. In this way, the network disconnection and insufficient uplink resources caused by the failure to reconfigure the DRB for the terminal device can be reduced; thereby improving the stability of the terminal device's data transmission and ensuring the user experience.

[0088] In some possible implementations, the terminal device triggers RRC reconnection in a first cell where it is currently residing, when the first RLF is caused by a first RACH failure, including: the terminal device triggers a first RRC reconnection in the first cell where it is currently residing, when the first RLF is caused by a first RACH failure; and determining whether to reconfigure DRB for the terminal device when the RRC reconnection is successful, including: determining whether to reconfigure DRB for the terminal device when the first RRC reconnection is successful.

[0089] It can be understood that after the first RACH triggered by the terminal device (i.e., the first RACH) fails and causes the first RLF (i.e., the first RLF), the first RRC reconnection (i.e., the first RRC reconnection) can be triggered in the first cell where it is currently located. When the first RRC reconnection is successful, it is determined whether the first cell has configured DRB for the terminal device; if the DRB is not reconfigured, the second cell within the preset range is searched, and the DRB configuration information is obtained from the second cell to reconfigure the DRB in the second cell.

[0090] In one example, a terminal device triggers a first RACH to request uplink resources in the first cell it currently resides in due to insufficient uplink resources. If the first RACH triggered by the terminal device fails, resulting in a first RLF, the terminal device performs a first RRC reconnection. If the first RRC reconnection succeeds, the network determines whether to reconfigure a DRB for the terminal device in the first cell. If the DRB is not reconfigured, the network searches for a second cell within a preset range and obtains DRB configuration information from the second cell to reconfigure the DRB in the second cell.

[0091] In another example, taking the case where the terminal device triggers the first RACH to apply for uplink resources in the first cell where it is currently located due to insufficient uplink, if the first RACH triggered by the terminal device fails and the first RACH does not cause RLF, the terminal device does not take any action.

[0092] In an embodiment of the present disclosure, when a terminal device experiences a first RLF due to a first RACH failure in a first cell in which it is currently residing, the terminal device triggers a first RRC reconnection in the first cell; after the first RRC reconnection succeeds, the terminal device determines whether the network side has reconfigured the DRB for the terminal device. If the network side has not reconfigured the DRB for the terminal device in the first cell, the terminal device searches for a second cell within a preset range to complete the configuration of the DRB in the second cell. In this way, after the RRC reconnection is triggered for the first time, the terminal device can configure the DRB in a neighboring second cell based on the fact that the network side has not reconfigured the DRB for the terminal device, thereby ensuring that the ongoing services of the terminal device are not interrupted and the operation quality of the network is guaranteed.

[0093] In some possible implementations, such as Figure 3 As shown, Figure 3 The flow chart of a method for processing wireless link data according to an exemplary embodiment is shown as follows Figure 2 , see Figure 3 As shown, when the first RRC reconnection is successful, determining whether to reconfigure the DRB for the terminal device may include:

[0094] In step 301, when the first RRC reconnection is successful, the number of second RACH failures due to a preset reason is determined;

[0095] In step 302, when the number of failures is greater than or equal to a preset first threshold, controlling the terminal device to trigger a second RLF;

[0096] In step 303, when the second RLF is successfully triggered, a second RRC reconnection is triggered in the first cell;

[0097] In step 304, if the second RRC reconnection is successful, determine whether to reconfigure the DRB for the terminal device;

[0098] The preset reason includes: the terminal device does not receive a random access response message or a contention resolution message.

[0099] In the embodiment of the present disclosure, the random access response message (MSG2) is one or more responses from the network side to the MSG1 preamble, and is used to provide further information and scheduling for MSG3. The contention resolution message (MSG4) is mainly used for contention resolution.

[0100] In some embodiments, after the first RRC reconnection, the terminal device can trigger RACH for the second time (i.e., the second RACH) in the first cell to apply for uplink resources; if the reason for the failure of the second RACH is that the terminal device does not receive a random access response message or a contention resolution message, the number of RACH failures is updated; if the reason for the failure of the second RACH is other reasons, the number of RACH failures is not updated; if the second RACH is successful, the number of RACH failures is reset to 0.

[0101] Among them, RRC is used to control the allocation and release of radio resources between the terminal device and the network side.

[0102] In some embodiments, the terminal device may obtain the number of second RACH failures caused by the terminal device not receiving a random access response message or a contention resolution message when the first RRC reconnection is successful.

[0103] In some embodiments, a counter can be used to update the number of RACH failures. For example, after completing the first RRC reconnection, the terminal device can trigger a second RACH (i.e., a second RACH) in the first cell to apply for uplink resources. If the second RACH fails, a first message is sent to the counter, where the first message indicates that the second RACH failed. The counter updates the number of RACH failures in response to the first message, so that the number of RACH failures increases by one.

[0104] In some embodiments, after obtaining the number of second RACH failures caused by preset reasons, the terminal device compares the number of second RACH failures with the numerical value of a preset first threshold. When the number of second RACH failures is greater than or equal to the preset first threshold, the terminal device actively triggers RLF (i.e., the second occurrence of RLF, also referred to as the second RLF).

[0105] It should be noted that the causes of the two RLFs occurring on the terminal device are different. The second RLF is actively triggered by the terminal device, while the first RLF is caused by the failure of the first RACH and is an RLF that occurs passively on the terminal device.

[0106] In some embodiments, upon successfully triggering the second RLF, the terminal device triggers a second RRC reconnection in the first cell.

[0107] It can be understood that the purpose of the terminal device triggering the second RLF is to perform RRC reconnection again (ie, the second RRC).

[0108] In some embodiments, when the second RRC reconnection is successful, the terminal device determines whether the network side reconfigures the DRB for the terminal device in the first cell.

[0109] It can be understood that after the second RRC reconnection, the terminal device can determine whether the network side has reconfigured DRB for it in the first cell. If DRB is not reconfigured in the first cell, the terminal device can search for the second cell within a preset range to reconfigure DRB in the second cell.

[0110] In an embodiment of the present disclosure, when the number of second RACH failures caused by preset reasons is greater than or equal to a preset first threshold, the terminal device actively triggers a second RLF to perform a second RRC reconnection, and obtains DRB configuration information from the first cell or the second cell based on the second RRC connection. That is, the terminal device can actively trigger a second RRC reconnection to obtain DRB configuration information by comparing the number of second RACH failures with the first threshold. In this way, the situation where the terminal passively waits for passive measures such as network scheduling and parameter configuration after the occurrence of the first RLF can be reduced, thereby ensuring the user experience when using the terminal device.

[0111] In some possible implementations, if the DRB is not reconfigured for the terminal device, the accumulated number of times the DRB is not reconfigured for the terminal device is updated.

[0112] It can be understood that after the terminal device completes the RRC reconnection, it determines whether the first cell has reconfigured the DRB for the terminal device. If the first cell has not reconfigured the DRB for the terminal device, the cumulative number of times the DRB has not been reconfigured for the terminal device is counted and increased (i.e., updated).

[0113] In one example, assuming that before the cumulative number of times the DRB is not reconfigured for the terminal device is updated, the cumulative number is recorded as DRB_count=1. Then, when the first cell does not reconfigure the DRB for the terminal device, the cumulative number is updated to DRB_count=2.

[0114] In some embodiments, a counter may be used to update the cumulative number of times the DRB is not reconfigured for the terminal device. For example, after the terminal device completes the second RRC reconnection, it determines whether the first cell has reconfigured the DRB for the terminal device; when the first cell has not reconfigured the DRB for the terminal device, the counter sends second information to indicate that the first cell has not reconfigured the DRB for the terminal device; in response to the second information, the counter updates the cumulative number of times the DRB is not reconfigured for the terminal device, so that the cumulative number of times the DRB is not reconfigured for the terminal device increases by one.

[0115] In an embodiment of the present disclosure, the cumulative number of times that the DRB is not reconfigured for the terminal device is updated, so that when the cumulative number is greater than or equal to a second threshold, RRC reconnection is performed in a second cell that meets preset conditions (such as signal quality, frequency, number of beams, etc.), so that when the first cell does not reconfigure the DRB for the terminal device, the DRB is configured by obtaining the DRB configuration information of the second cell, so that the ongoing service of the terminal device will not be interrupted due to the inability of the first cell to provide services, thereby ensuring the stability of data transmission.

[0116] In some possible implementations, the method further includes: when the RRC reconnection is successful, determining whether the cumulative number of times that the first cell has not reconfigured the DRB for the terminal device is greater than or equal to a preset second threshold; when the cumulative number is greater than or equal to the second threshold, searching for the second cell and obtaining DRB configuration information from the second cell.

[0117] It can be understood that when the second RRC reconnection of the terminal device is successful, it is determined whether the cumulative number of times that the first cell has not reconfigured DRB for the terminal device is greater than or equal to a preset second threshold. If the cumulative number is greater than or equal to the second threshold, the terminal device directly searches for the second cell within the preset range to reconfigure DRB in the second cell.

[0118] In an embodiment of the present disclosure, when the cumulative number of times that the first cell fails to reconfigure the DRB for the terminal device is greater than or equal to a preset second threshold, it indicates that the first cell is likely unable to reconfigure the DRB for the terminal device. At this time, the attempt to reconfigure the DRB in the first cell can be abandoned, and the second cell within the preset range can be searched instead to achieve reconfiguration of the DRB in the second cell.

[0119] In some embodiments, the method further includes: when the RRC reconnection is successful, determining whether the cumulative number of times that the first cell has not reconfigured the DRB for the terminal device is greater than or equal to a preset second threshold; when the cumulative number is greater than or equal to the second threshold, searching for a cell that meets the preset conditions within a preset range; if there is no cell that meets the preset conditions, triggering a third RRC reconnection on the first cell.

[0120] In the embodiment of the present disclosure, the preset conditions may include but are not limited to signal quality, frequency, number of beams, etc.

[0121] It is understandable that there is no cell that meets the preset conditions within the preset range, which means that the only cell that can perform data transmission with the terminal device is the first cell. At this time, the terminal device will perform RRC reconstruction in the first cell for the third time.

[0122] In some possible implementations, determining the number of second RACH failures due to a preset reason when the first RRC reconnection is successful includes: marking the first cell when the first RRC reconnection is successful; triggering the second RACH based on the mark and initializing the number of RACH failures; determining a reason for the second RACH failure, and determining the number of second RACH failures due to the preset reason.

[0123] In some embodiments, after a first RACH failure results in a first RLF, a first RRC reconnection is triggered; after the first RRC reconnection succeeds, the first cell is marked, for example, the first cell is marked as rlf_cell.

[0124] In some embodiments, the terminal device may trigger RACH again (i.e., second RACH) in the first cell based on the above flag to apply for uplink resources, and initialize the number of RACH failures, for example, to rach_count=0.

[0125] In some embodiments, the terminal device may trigger RACH again (i.e., a second RACH) in the first cell based on the above flag to apply for uplink resources; and at the same time, initialize the cumulative number of times the first cell has not reconfigured a DRB for the terminal device. For example, the cumulative number of times the DRB has not been reconfigured for the terminal device is initialized to DRB_count=0.

[0126] In some embodiments, after initializing the number of RACH failures, it is determined whether the failure cause of the second RACH failure is failure to receive a random access response message or a contention resolution message. If it is the above failure cause, the number of second RACH failures caused by the above failure cause is determined.

[0127] In the embodiment of the present disclosure, after the first RRC reconnection is successful, the first cell is marked, and then based on the mark, the second RACH is actively triggered to apply for uplink resources. That is, the mark is used as a condition for triggering the second RACH, which can control the time of the second RACH triggering and improve the probability of successful access.

[0128] In some possible implementations, the method further includes: if the first RRC reconnection is successful, determining whether the second RACH is successful; if the second RACH is successful and the number of failures of the second RACH due to preset reasons is less than a preset first threshold, resetting the number of failures of the second RACH to 0.

[0129] It can be understood that when the first RRC reconnection is successful, the terminal device can trigger the second RACH, and after completing the second RACH, determine whether the second RACH is successful. If the second RACH is successful, then determine whether the number of failures of the second RACH due to preset reasons is less than the preset first threshold. If it is less than the first threshold, the number of failures of the second RACH is reset to 0.

[0130] In some embodiments, after the first RRC reconnection is successful, the terminal device can trigger a second RACH to apply for uplink resources, and at the same time initialize the number of failures of the second RACH due to preset reasons (for example, rach_count=0). Then, it is determined whether the second RACH is successful. If the second RACH is successful, the terminal device further determines whether the number of failures of the second RACH due to preset reasons is less than a first threshold. If it is less than the first threshold, the number of failures of the second RACH due to preset reasons is reset to 0; if the number of failures of the second RACH due to preset reasons is less than the first threshold or greater than or equal to the first threshold, the terminal device actively triggers a second RLF to perform a second RRC reconstruction.

[0131] In the embodiment of the present disclosure, when the second RACH is successful and the number of failures of the second RACH due to preset reasons is less than the first threshold, the number of failures of the second RACH is reset to 0; in this way, when the RACH is performed next time, the RACH can still be performed based on the first RRC without triggering the second RLF, which can save energy consumption of the terminal device.

[0132] Figure 4 The flow chart of a method for processing wireless link data according to an exemplary embodiment is shown as follows Figure 3 ,like Figure 4 The specific operation process of the above-mentioned wireless link data processing method includes:

[0133] It should be noted that in Figure 4 In the figure, UE represents the terminal equipment, rlf_cell represents the first cell after identification, rach_count represents the number of RACH failures, DRB_count represents the cumulative number of DRBs, MSG2 represents the random access response message, MSG4 represents the contention resolution message, the preset first threshold is 3, and the preset second threshold is 3.

[0134] In step 401, the terminal device is normally stationed in the first cell.

[0135] In step 402, the terminal device applies for uplink resources through the first RACH in the first cell due to insufficient uplink resources.

[0136] In step 403, the first RACH of the terminal device fails, and it is determined whether the first RACH failure causes a first RLF.

[0137] In step 404, if the first RACH failure causes the terminal device to have a first RLF, the first cell is recorded as the RLF cell. After the first RACH failure causes the first RLF to occur, the terminal device immediately performs a first RRC reconnection in the first cell.

[0138] In step 405, the terminal device does not perform any action.

[0139] Specifically, if the first RACH failure causes the terminal device to have a first RLF, the terminal device will not take any action.

[0140] In step 406, it is determined whether the terminal device triggers the second RACH in the first cell to apply for uplink resources.

[0141] In addition, if the terminal device does not trigger the second RACH in the first cell, step 405 is executed.

[0142] In step 407, if the terminal device triggers the second RACH in the first cell, the number of RACH failures and the accumulated number of DRBs are initialized.

[0143] In step 408, it is determined whether the second RACH of the terminal device is successful.

[0144] In step 409, if the second RACH of the terminal device is unsuccessful, it is further determined whether the second RACH fails and whether the failure reason is that the random access response message or the contention resolution message is not received.

[0145] In step 410, if the second RACH fails and the reason for the failure is that the random access response message or the contention resolution message is not received, the number of RACH failures is updated.

[0146] In addition, if the RACH fails and the failure reason is other reasons, step 405 is executed.

[0147] In step 411, after the number of RACH failures is updated, it is determined whether the updated number of RACH failures is greater than or equal to a first threshold.

[0148] In step 412, if the updated number of RACH failures is greater than or equal to a first threshold, the terminal device actively performs a second RLF.

[0149] In step 413, based on the second RLF, the terminal device triggers a second RRC reconnection. After completing the second RRC reconnection, it is determined whether the network side has reconfigured the DRB for the terminal device in the first cell.

[0150] In step 414, if the network side does not reconfigure the DRB for the terminal device in the first cell, the accumulated number of DRBs is updated.

[0151] In addition, if the network side reconfigures the DRB for the terminal device in the first cell, step 405 is executed.

[0152] In step 415, it is determined whether the cumulative number of updated DRBs is greater than or equal to a preset second threshold.

[0153] In step 416, if the cumulative number of updated DRBs is greater than or equal to the preset second threshold, the terminal device directly searches for the second cell within the preset range after triggering RRC reconnection next time to reconfigure DRB in the second cell.

[0154] In step 417, if the terminal device fails to search for a cell that meets the preset conditions within the preset range, it continues to trigger the third RRC reconnection (ie, the third RRC) in the first cell.

[0155] In step 418, after executing step 408, if the second RACH of the terminal device is successful, it is further determined whether the number of RACH failures is less than a first threshold.

[0156] In step 419, if the number of RACH failures is less than the first threshold, the number of RACH failures is reset to 0.

[0157] In step 419, if the number of RACH failures is greater than or equal to the first threshold, a second RLF is actively triggered.

[0158] According to the technical solution of the embodiment of the present disclosure, after the terminal device successfully reconnects to the RRC, it first determines whether to reconfigure the DRB for the terminal device. If the DRB is not reconfigured for the terminal device, it searches for a second cell within a preset range, obtains DRB configuration information in the second cell, and configures the DRB for the terminal device based on the DRB configuration information. In this way, the network disconnection and insufficient uplink resources caused by the failure to reconfigure the DRB for the terminal device can be reduced, thereby improving the stability of the data transmission of the terminal device and ensuring the user experience.

[0159] Furthermore, the technical solution of the disclosed embodiment does not violate the communication standard protocol, does not require any modification to the standard protocol, and does not cause network-side anomalies, making the technical solution simpler. In addition, during the standard test script process, there will be no problem of failing the test due to protocol violations.

[0160] Figure 5 FIG. 1 is a block diagram of a device for processing wireless link data according to an exemplary embodiment. Figure 5 As shown, the wireless link data processing device 500 is applied to a terminal device and mainly includes:

[0161] The reconnection module 501 is configured to trigger a radio link control RRC reconnection in the first cell where the terminal device is currently residing, when a first radio link failure RLF occurs due to a first random access RACH failure;

[0162] The determination module 502 is configured to determine whether to reconfigure a data radio bearer (DRB) for the terminal device if the RRC reconnection is successful;

[0163] An acquisition module 503 is configured to search for a second cell within a preset range and acquire DRB configuration information from the second cell if the DRB is not reconfigured for the terminal device;

[0164] The configuration module 504 is configured to configure the DRB for the terminal device based on the DRB configuration information.

[0165] In some embodiments, the reconnection device 501 is configured to trigger a first RRC reconnection in the first cell when the terminal device causes the first RLF due to a first RACH failure in the first cell currently camped;

[0166] The determining device 502 is configured to determine whether to reconfigure a data radio bearer DRB for the terminal device when the first RRC reconnection is successful.

[0167] In some embodiments, the determining means 502 is configured to determine, when the first RRC reconnection is successful, the number of failures resulting in the second RACH failure due to a preset reason;

[0168] The reconnection module 501 is configured to control the terminal device to trigger a second RLF when the number of failures is greater than or equal to a preset first threshold; and trigger a second RRC reconnection in the first cell when the second RLF is successfully triggered;

[0169] The determining means 502 is configured to determine whether to reconfigure a DRB for the terminal device if the second RRC reconnection is successful;

[0170] The preset reason includes: the terminal device does not receive a random access response message or a contention resolution message.

[0171] In some embodiments, the apparatus 500 further includes:

[0172] The updating module is configured to update the accumulated number of times that the DRB is not reconfigured for the terminal device if the DRB is not reconfigured for the terminal device.

[0173] In some embodiments, the determining module 502 is configured to determine, when the RRC reconnection is successful, whether the cumulative number of times that the first cell does not reconfigure the DRB for the terminal device is greater than or equal to a preset second threshold;

[0174] The acquisition module 503 is configured to search for the second cell and acquire DRB configuration information from the second cell when the accumulated number of times is greater than or equal to the second threshold.

[0175] In some embodiments, the apparatus 500 further includes:

[0176] a marking module, configured to mark the first cell when the first RRC reconnection is successful;

[0177] an initialization module configured to trigger the second RACH based on the flag and initialize the number of RACH failures;

[0178] The determining module 502 is configured to determine a reason causing the second RACH failure, and determine a number of times the second RACH fails due to the preset reason.

[0179] In some embodiments, the determining module 502 is configured to determine whether the second RACH is successful if the first RRC reconnection is successful;

[0180] The resetting module is configured to reset the number of second RACH failures to 0 if the second RACH succeeds and the number of second RACH failures due to a preset reason is less than a preset first threshold.

[0181] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0182] Figure 61 is a hardware block diagram illustrating a wireless link data processing apparatus 600 according to an exemplary embodiment. For example, apparatus 600 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a tablet device, a personal digital assistant, a wearable device, or the like.

[0183] Reference Figure 6 , the apparatus 600 may include one or more of the following components: a processing component 602 , a memory 604 , a power component 606 , a multimedia component 608 , an audio component 610 , an input / output (I / O) interface 612 , a sensor component 614 , and a communication component 616 .

[0184] The processing component 602 generally controls the overall operation of the device 600, such as operations associated with display, phone calls, data communications, camera operation, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the above-described method. In addition, the processing component 602 may include one or more modules to facilitate interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate interaction between the multimedia component 608 and the processing component 602.

[0185] The memory 604 is configured to store various types of data to support operations on the device 600. Examples of such data include instructions for any application or method operating on the device 600, contact data, phone book data, messages, pictures, videos, etc. The memory 604 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.

[0186] The power supply component 606 provides power to the various components of the device 600. The power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device 600.

[0187] The multimedia component 608 includes a screen that provides an output interface between the device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front camera and / or a rear camera. When the device 600 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.

[0188] The audio component 610 is configured to output and / or input audio signals. For example, the audio component 610 includes a microphone (MIC), which is configured to receive external audio signals when the device 600 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 604 or transmitted via the communication component 616. In some embodiments, the audio component 610 also includes a speaker for outputting audio signals.

[0189] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as a keyboard, click wheel, buttons, etc. These buttons may include but are not limited to: a home button, volume buttons, a start button, and a lock button.

[0190] The sensor assembly 614 includes one or more sensors for providing various aspects of the status assessment of the device 600. For example, the sensor assembly 614 can detect the open / closed state of the device 600, the relative positioning of components, such as the display and keypad of the device 600. The sensor assembly 614 can also detect changes in the position of the device 600 or a component of the device 600, the presence or absence of user contact with the device 600, the orientation or acceleration / deceleration of the device 600, and temperature changes of the device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 614 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0191] The communication component 616 is configured to facilitate wired or wireless communication between the device 600 and other devices. The device 600 can access a wireless network based on a communication standard, such as Wi-Fi, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component 616 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 also includes an NFC module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0192] In an exemplary embodiment, the apparatus 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-described method.

[0193] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 604 including instructions, which can be executed by the processor 620 of the apparatus 600 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0194] A non-transitory computer-readable storage medium, when instructions in the storage medium are executed by a processor of a first terminal, enables the first terminal to perform a method for processing wireless link data, the method comprising:

[0195] When the terminal device causes a first RLF due to a first RACH failure in a first cell currently residing, triggering an RRC reconnection in the first cell;

[0196] If the RRC reconnection is successful, determining whether to reconfigure the DRB for the terminal device;

[0197] If the DRB is not reconfigured for the terminal device, searching for a second cell within a preset range and obtaining DRB configuration information from the second cell;

[0198] Based on the DRB configuration information, configure DRB for the terminal device.

[0199] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0200] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for processing wireless link data, characterized in that: The method comprises: When the terminal device causes a first radio link failure RLF due to a first random access RACH failure in the first cell currently residing, triggering a radio link control RRC reconnection in the first cell; If the RRC reconnection is successful, determining whether to reconfigure a data radio bearer (DRB) for the terminal device; If the DRB is not reconfigured for the terminal device, searching for a second cell within a preset range and obtaining DRB configuration information from the second cell; Based on the DRB configuration information, configure DRB for the terminal device.

2. The method according to claim 1, characterized in that When a first RACH failure causes a first RLF in a first cell in which the terminal device is currently residing, triggering an RRC reconnection in the first cell includes: When the first RLF is caused by a first RACH failure in the first cell currently being resided by the terminal device, triggering a first RRC reconnection in the first cell; When the RRC reconnection is successful, determining whether to reconfigure a data radio bearer (DRB) for the terminal device includes: In case the first RRC reconnection is successful, determine whether to reconfigure the data radio bearer DRB for the terminal device.

3. The method according to claim 2, characterized in that The determining whether to reconfigure a DRB for the terminal device when the first RRC reconnection succeeds includes: When the first RRC reconnection is successful, determining a number of second RACH failures due to a preset reason; When the number of failures is greater than or equal to a preset first threshold, controlling the terminal device to trigger a second RLF; When the second RLF is successfully triggered, triggering a second RRC reconnection in the first cell; If the second RRC reconnection is successful, determining whether to reconfigure a DRB for the terminal device; The preset reason includes: the terminal device does not receive a random access response message or a contention resolution message.

4. The method according to claim 1, wherein The method further comprises: If the DRB is not reconfigured for the terminal device, the accumulated number of times the DRB is not reconfigured for the terminal device is updated.

5. The method according to claim 1, wherein The method further comprises: If the RRC reconnection is successful, determining whether the cumulative number of times that the first cell does not reconfigure the DRB for the terminal device is greater than or equal to a preset second threshold; When the accumulated number of times is greater than or equal to the second threshold, the second cell is searched and DRB configuration information is acquired from the second cell.

6. The method according to claim 3, characterized in that The determining, when the first RRC reconnection is successful, a number of second RACH failures due to a preset reason includes: If the first RRC reconnection is successful, marking the first cell; triggering the second RACH based on the flag and initializing the number of RACH failures; A reason causing the second RACH failure is determined, and a number of failures resulting from the second RACH failure due to the preset reason is determined.

7. The method according to claim 2, characterized in that The method further comprises: If the first RRC reconnection is successful, determining whether the second RACH is successful; If the second RACH is successful and the number of second RACH failures due to a preset reason is less than a preset first threshold, the number of second RACH failures is reset to 0.

8. A device for processing wireless link data, characterized in that: The device comprises: A reconnection module, configured to trigger a radio link control RRC reconnection in a first cell where the terminal device is currently residing, when a first radio link failure RLF occurs due to a first random access RACH failure; A determination module, configured to determine whether to reconfigure a data radio bearer (DRB) for the terminal device if the RRC reconnection is successful; an acquisition module, configured to search for a second cell within a preset range and acquire DRB configuration information from the second cell if the DRB is not reconfigured for the terminal device; A configuration module is configured to configure DRB for the terminal device based on the DRB configuration information.

9. A device for processing wireless link data, characterized in that: include: processor; a memory configured to store processor-executable instructions; The processor is configured to implement the steps of any one of the wireless link data processing methods in claims 1 to 7 when executing.

10. A non-transitory computer-readable storage medium, when instructions in the storage medium are executed by a processor of a device for processing wireless link data, enables the device to perform the method for processing wireless link data according to any one of claims 1 to 7.

Images