Transmission recovery method and device, terminal equipment and chip module

Abstract

The invention relates to a transmission recovery method and device, terminal equipment and a chip module. The method comprises the following steps: in response to sending of an RRC connection reestablishment completion message, starting a recovery timer of a service bearer; the service bearer comprises a service signaling bearer and a service data bearer; and recovering the service bearer according to the recovery timer, and performing data transmission through the recovered service bearer. By adopting the method, the situation that the user data cannot be transmitted due to the fact that the service bearing SRB2 and the DRB are suspended for a long time can be avoided, and reliable transmission of the subsequent user data is ensured.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a transmission recovery method, apparatus, terminal equipment, and chip module. Background Technology

[0002] In mobile communication systems, RRC connections are the core foundation for signaling interaction and data transmission between user equipment (UE) and base stations. The protocol specifies the RRC connection reconstruction process. When a UE encounters abnormal situations such as radio link failure or handover failure, this process is triggered. It starts a T311 timer to search for available cells. After successfully finding a target cell, it suspends all radio bearers except SRB0 and starts a T301 timer to send a reconstruction request. If the UE receives a reconstruction response message from the base station before T301 times out, it will reconstruct SRB1 and resume its transmission. At this point, the RRC connection reconstruction process is considered successful. However, according to the protocol, SRB2 and all data radio bearers remain suspended and require subsequent RRC connection reconfiguration messages from the base station to complete reconstruction and restore transmission.

[0003] However, in practical applications, there are scenarios where the user equipment does not receive the reconfiguration message after the RRC connection is successfully re-established, causing SRB2 and all data radio bearers to be suspended for a long time, making it impossible to transmit subsequent user data and affecting the quality of communication services. Summary of the Invention

[0004] Therefore, it is necessary to provide a transmission recovery method, apparatus, terminal equipment, chip module, computer-readable storage medium, and computer program product that can prevent SRB2 and data radio bearers from being suspended for a long time and ensure the reliable transmission of subsequent user data.

[0005] Firstly, this application provides a transmission recovery method applied to the terminal side, comprising:

[0006] In response to the sending of the RRC connection reconstruction completion message, a recovery timer for the service bearer is started; the service bearer includes service signaling bearer and service data bearer;

[0007] The service bearer is restored according to the recovery timer, and data is transmitted through the restored service bearer.

[0008] In one embodiment, the step of restoring the service bearer according to the recovery timer and transmitting data through the restored service bearer includes:

[0009] Based on the RRC reconfiguration message received before the recovery timer expires, the recovery timer is stopped, and the transmission entity carrying the service is rebuilt; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity;

[0010] Data transmission is performed through the packet data convergence protocol entity and the radio link control entity.

[0011] In one embodiment, the step of restoring the service bearer according to the recovery timer and transmitting data through the restored service bearer includes:

[0012] If no RRC reconfiguration message is received after the recovery timer expires, a tracking area update message is sent to the network-side device, and the recovery timer is restarted.

[0013] The service bearer is restored according to the restart recovery timer, and data is transmitted through the restored service bearer.

[0014] In one embodiment, the step of restoring the service bearer according to the restarted recovery timer and transmitting data through the service bearer includes:

[0015] Based on the RRC reconfiguration message received before the restart recovery timer expires, the restart recovery timer is stopped, and the transmission entity carrying the service is rebuilt; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity;

[0016] Data transmission is performed through the packet data convergence protocol entity and the radio link control entity.

[0017] In one embodiment, the method further includes:

[0018] If the recovery timer expires after the restart and no RRC reconfiguration message is received, the system switches from the connected state to the idle state.

[0019] In one embodiment, the tracking area update message is sent via a basic signaling bearer, and the method further includes:

[0020] Start the first timer;

[0021] Based on the network-side device found before the first timer expires, the service bearer and the basic signaling bearer are suspended, an RRC connection reconstruction request is sent to the network-side device, and a second timer is started;

[0022] Based on the RRC connection reconstruction message received before the second timer expires, the basic signaling bearer is restored, and the RRC connection reconstruction complete message is sent to the network-side device through the basic signaling bearer.

[0023] Secondly, this application also provides a transmission recovery device, applied on the terminal side, comprising:

[0024] The startup module is used to start the service bearer recovery timer in response to the sending of the RRC connection reconstruction completion message; the service bearer includes service signaling bearer and service data bearer;

[0025] The transmission module is used to restore the service bearer according to the recovery timer and to transmit data through the restored service bearer.

[0026] Thirdly, this application also provides a terminal device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described in the first aspect above.

[0027] Fourthly, this application also provides a chip module, including a communication module, a power module, a storage module, and a chip, wherein:

[0028] The power module is used to provide power to the chip module;

[0029] The storage module is used to store data and instructions;

[0030] The communication module is used for internal communication within the chip module, or for communication between the chip module and external devices.

[0031] The chip is used to perform the steps of the method provided in the first aspect above.

[0032] Fifthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect above.

[0033] Sixthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in the first aspect above.

[0034] The aforementioned transmission recovery method, apparatus, terminal equipment, chip module, computer-readable storage medium, and computer program product, in response to the sending of the RRC connection reconstruction completion message, start a recovery timer for the service bearer. The service bearer includes service signaling bearer and service data bearer. The service bearer is restored according to the recovery timer, and data transmission is performed through the restored service bearer. After the RRC connection reconstruction is successful, a timer can be set for the RRC connection reconfiguration message sent by the network-side equipment. If the timer expires and the RRC connection reconfiguration message is not received, corresponding processing is performed to avoid the service bearers SRB2 and DRB being suspended for a long time, which would prevent user data from being transmitted and ensure the reliable transmission of subsequent user data. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 This is a flowchart illustrating a transmission recovery method in one embodiment;

[0037] Figure 2 This is a flowchart illustrating the transmission recovery method in another embodiment;

[0038] Figure 3 This is a flowchart illustrating the transmission recovery method in yet another embodiment;

[0039] Figure 4 This is a structural block diagram of a transmission recovery device in one embodiment;

[0040] Figure 5 This is an internal structure diagram of a terminal device in one embodiment;

[0041] Figure 6 This is an internal structure diagram of a chip module in one embodiment. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0043] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0044] Before introducing the specific embodiments of this application, the technical terms involved in this application will be explained:

[0045] LTE: Long Term Evolution, 4G wireless air interface technology;

[0046] UE: User Equipment;

[0047] DRB: Data Radio Bearer carrying user plane data;

[0048] SRB: Signaling Radio Bearer carrying control plane data;

[0049] SRB0: Signaling radio bearer established based on the common control channel. It is the first basic signaling bearer for terminal access to the network. It has no RRC layer configuration and is directly mapped by the physical layer or MAC layer.

[0050] SRB1: The master signaling radio bearer established based on the dedicated control channel is the core control signaling bearer between the terminal and the network after the RRC connection is established, and is configured and managed by the RRC layer.

[0051] SRB2: A secondary signaling radio bearer established based on a dedicated control channel. It is a supplementary bearer to SRB1 and is dedicated to carrying NAS layer signaling. It is configured by the RRC layer after SRB1.

[0052] RB: Resource Block;

[0053] T301: A dedicated timer for the UE to wait for the network side's reconstruction response after sending an RRC connection reconstruction request, used to monitor the timeliness of reconstruction signaling interactions;

[0054] T311: After the UE triggers the RRC connection re-establishment procedure, it is used to control the upper limit of the cell selection phase and determine the maximum allowed time for the UE to find a suitable cell during the re-establishment procedure.

[0055] PDCP: Packet Data Convergence Protocol;

[0056] RLC: Radio Link Control;

[0057] MAC: Medium Access Control;

[0058] RRC: Radio Resource Control;

[0059] NAS: Not Access Stratum;

[0060] NV: Non-Volatile Memory, the non-volatile memory inside a mobile phone;

[0061] RLF: Radio Link Failure;

[0062] TX: Transmitter, the sending end;

[0063] ACK: Acknowledge, confirmation response;

[0064] AT: Attention.

[0065] NV: Non-Volatile;

[0066] TAU: Tracking Area Update.

[0067] According to the 3GPP protocol, when an RLF is detected due to reasons such as physical layer anomaly, MAC layer random access failure, RLC layer uplink transmission reaching the maximum number of times, or PDCP layer integrity verification failure, an RRC connection reconstruction will be triggered. Alternatively, if the UE switches from the source base station to the target base station (including switching to an LTE cell or a cell of other standards) in RRC connected state and the entire handover process is not completed and the failure criteria are met, an RRC connection reconstruction will also be triggered. In addition, if the RRC connection reconfiguration fails due to reasons such as abnormal configuration parameters, an RRC connection reconstruction will also be triggered.

[0068] When any of the above scenarios occur, the current cell is considered to have a problem, requiring cell selection to search for the cell with the best signal in the current environment. To prevent indefinite searching, the UE starts a T311 timer. If this timer expires, the UE leaves the connected state and enters the idle state. If a good LTE cell is found, the UE will actively stop the T311 timer and perform some protocol-required operations, including suspending all RBs except SRB0. This is because an RRC Connection Reestablishment Request message will be sent later, which is sent on SRB0 and triggers the MAC layer's random access procedure.

[0069] To prevent subsequent process anomalies that could prevent normal termination, the UE starts a T301 timer. If this timer expires, the UE will leave the connected state and enter the IDLE state. If random access is normal before the T301 timeout and the UE receives an RRC Connection Reestablishment message from the base station, the UE will actively stop the T301 timer and perform some protocol-required operations, including rebuilding the PDCP and RLC entities of SRB1. Based on the rebuilt entities, SRB1 transmission is resumed. This is because the expected RRC Connection Reconfiguration message is received on SRB1, and SRB1 cannot be suspended. After the UE sends the RRC Connection Reestablishment Complete message, the RRC connection rebuilding process is considered successful. However, at this point, only SRB1 has resumed transmission; SRB2 and DRB remain suspended. SRB2 transmits NAS signaling, and DRB transmits user plane data, such as internet access packets, voice packets, and video packets. Therefore, as long as SRB2 and DRB remain suspended, the wireless access network cannot truly achieve "access".

[0070] Next, it is expected that an RRCConnectionReconfiguration message without mobility control information (mobilityControlInfo) will be received. This allows for the reconstruction of the PDCP and RLC entities of SRB2 and all DRBs, after which the transmission of SRB2 and all DRBs can be restored. If, due to abnormal base station procedures or radio interface reception, the UE does not receive the RRCConnectionReconfiguration message sent by the base station, SRB2 and DRBs will remain suspended because the reconstruction and recovery procedures have not been performed, resulting in failure of NAS signaling and user plane data transmission. This applies not only to data after the RRC connection reconstruction procedure but also to data before it. For example, if NAS sends a signaling message through SRB2, due to poor radio conditions and low uplink scheduling, the RLC TX may slowly transmit the message. Before the transmission is completed and an RLC status report ACK from the base station is received, the RLC TX will not give the PDCP TX a successful delivery indication. Consequently, the PDCP TX will not indicate to the higher layers that the NAS signaling was successfully transmitted. The higher-layer procedures may be waiting for an indication of the transmission status, whether it is successful or failed. As described above, if the higher layer does not receive a successful transmission indication, the RRC connection reconstruction process may be triggered due to the RLC retransmission reaching the maximum number of times. However, as also described above, because the UE may not receive the RRCConnectionReconfiguration message, the UE will not reconstruct SRB2 and will not send a failure indication to the higher layer, resulting in abnormal processes at the higher layer.

[0071] Therefore, if the RRC connection reconstruction process is successfully completed but the RRCConnectionReconfiguration message is not received, SRB2 and all DRBs will remain in a suspended state, affecting subsequent data transmission.

[0072] To address the aforementioned issues, the transmission recovery method provided in this application starts a service bearer recovery timer in response to the sending of an RRC connection reconstruction completion message. The service bearer includes service signaling bearers and service data bearers. The service bearer is restored according to the recovery timer, and data transmission is performed through the restored service bearer. After successful RRC connection reconstruction, a timer can be set for the RRC connection reconfiguration message sent by the network-side device. If the timer expires and the RRC connection reconfiguration message is not received, corresponding processing is performed to avoid the service bearers SRB2 and DRB being suspended for a long time, which would prevent user data from being transmitted and ensure the reliable transmission of subsequent user data.

[0073] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0074] In one exemplary embodiment, such as Figure 1 As shown, a transmission recovery method is provided. This embodiment illustrates the application of this method to a terminal, and includes the following steps:

[0075] Step S102: In response to the sending of the RRC connection reconstruction completion message, start the service bearer recovery timer; the service bearer includes service signaling bearer and service data bearer.

[0076] Among them, the service signaling bearer can be a control plane-dedicated bearer specifically used for transmitting control signaling related to user plane services, such as SRB2. The service data bearer can be a user plane-dedicated bearer specifically used for transmitting the actual valid data payload of user plane services, such as DRB. The service bearer can be a combination of control plane signaling bearers and user plane data bearers assembled between the terminal and the network to support the complete establishment, operation, and release of a certain user plane service, such as SRB2 and DRB. The recovery timer refers to the timer that waits for the base station to send an RRC connection reconfiguration message after the RRC connection is successfully re-established in order to restore the complete service bearer and avoid service interruption due to indefinite waiting.

[0077] Optionally, when the terminal sends an RRC connection reconstruction completion message to the base station, indicating that the RRC connection reconstruction process has been successfully completed, in order to avoid the terminal continuously failing to receive the RRC connection reconfiguration message sent by the base station, resulting in the service signaling bearer and service data bearer being suspended indefinitely, the terminal can start a recovery timer. For example, to avoid the UE continuously failing to receive the RRC connection reconfiguration message, resulting in the SRB2 and DRB being suspended indefinitely, the UE can start a non-standard timer after the RRC connection reconstruction process is successfully completed. This timer can be named, but is not limited to, Txxx timer, and the timer duration can be customized, for example, it can be a default of 3 seconds. This default value can be modified by issuing an AT command or directly in the NV storage area.

[0078] Step S104: Restore the service bearer according to the recovery timer, and transmit data through the restored service bearer.

[0079] Optionally, after the terminal starts the recovery timer, if it receives an RRC connection reconfiguration message from the base station before the recovery timer expires, the terminal stops the recovery timer and restores the service bearer, and performs data transmission through the restored service bearer; otherwise, if the recovery timer expires and the terminal still does not receive an RRC connection reconfiguration message from the base station, the terminal can actively trigger the base station to send an RRC connection reconfiguration message, and restore the service bearer when the base station sends the RRC connection reconfiguration message, and then perform data transmission through the restored service bearer. For example, after starting the Txxx timer, if an RRC connection reconfiguration message is received before the timeout, the terminal actively stops the timer, rebuilds the PDCP and RLC entities of SRB2 and all DRBs, and then resumes the transmission of SRB2 and all DRBs. Otherwise, if the Txxx timer expires and no RRC connection reconfiguration message is received, the terminal can send a NAS TAU message to the base station through SRB1 to try to trigger the base station to send an RRC connection reconfiguration message. If the RRC connection reconfiguration message sent by the base station is received, the PDCP and RLC entities of SRB2 and all DRBs can be rebuilt, and the transmission of SRB2 and all DRBs can be resumed. If the RRC connection reconfiguration message is still not received, the terminal can leave the connected state and enter the idle state.

[0080] The above-described transmission recovery method starts a recovery timer for the service bearer in response to the sending of the RRC connection reconstruction completion message. The service bearer includes service signaling bearer and service data bearer. The service bearer is restored according to the recovery timer, and data transmission is performed through the restored service bearer. After the RRC connection reconstruction is successful, a timer can be set for the RRC connection reconfiguration message sent by the network-side device. If the RRC connection reconfiguration message is not received after the timer expires, corresponding processing is performed to avoid the service bearers SRB2 and DRB being suspended for a long time, which would prevent user data from being transmitted and ensure the reliable transmission of subsequent user data.

[0081] In an exemplary embodiment, step S104 may specifically include: stopping the recovery timer based on the RRC reconfiguration message received before the recovery timer times out, and rebuilding the transmission entity of the service bearer; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity; and data transmission is performed through the packet data aggregation protocol entity and the radio link control entity.

[0082] The transmission entities include the PDCP entity and the RLC entity, which are the core functional entities of the user plane / control plane of the radio protocol stack. They are tightly coupled paired entities, with each bearer (SRB / DRB) being bound to a dedicated set of PDCP and RLC entities, responsible for the end-to-end processing and transmission of that bearer from the PDCP layer to the RLC layer. The RRC reconfiguration message is the RRCConnectionReconfiguration message.

[0083] Optionally, if an RRC connection reconfiguration message is received from the base station before the recovery timer expires, the terminal can stop the recovery timer and rebuild the PDCP and RLC entities, and then perform data transmission through the rebuilt PDCP and RLC entities. For example, if an RRCConnectionReconfiguration message is received from the base station before the Txxx timer expires, the UE actively stops the timer, rebuilds the PDCP and RLC entities of SRB2 and all DRBs, and resumes transmission of SRB2 and all DRBs after the PDCP and RLC entities are rebuilt.

[0084] In this embodiment, by stopping the recovery timer based on the RRC reconfiguration message received before the recovery timer expires, and rebuilding the transmission entity of the service bearer, data transmission is performed through the packet data aggregation protocol entity and the radio link control entity. SRB2 and DRB can be restored before the timer expires, thus achieving reliable transmission of user service data.

[0085] In an exemplary embodiment, step S104 may specifically include: sending a tracking area update message to the network-side device and restarting the recovery timer if no RRC reconfiguration message is received after the recovery timer expires; restoring the service bearer according to the restarted recovery timer and transmitting data through the restored service bearer.

[0086] Optionally, if the recovery timer expires and no RRC connection reconfiguration message is received from the base station, the terminal can send a non-access stratum tracking area update message to the base station to trigger the base station to send an RRC connection reconfiguration message. At this time, the terminal can restart the recovery timer to time the sending of the RRC connection reconfiguration message, and restore the service bearer based on the restarted recovery timer, thereby transmitting data through the restored service bearer. For example, if the Txxx timer expires and no RRCConnectionReconfiguration message is received from the base station, the UE can send a NAS TAU message to the base station via SRB1 to trigger the base station to send an RRCConnectionReconfiguration message and restart the Txxx timer. If the UE receives an RRCConnectionReconfiguration message from the base station before the Txxx timer expires, the UE stops the Txxx timer, rebuilds the PDCP and RLC entities of SRB2 and all DRBs, and resumes the transmission of SRB2 and all DRBs after the PDCP and RLC entities are rebuilt; otherwise, if the UE does not receive the RRCConnectionReconfiguration message from the base station before the Txxx timer expires, the terminal leaves the connected state and enters the idle state.

[0087] In this embodiment, if no RRC reconfiguration message is received after the recovery timer expires, a tracking area update message is sent to the network-side device, and the recovery timer is restarted. The service bearer is restored according to the restarted recovery timer, and data transmission is performed through the restored service bearer. This allows for corresponding processing when no RRC connection reconfiguration message is received from the base station after the timer expires, thus avoiding long-term suspension of SRB2 and DRB that could cause user service interruption.

[0088] In an exemplary embodiment, the steps described above for restoring the service bearer based on the restarted recovery timer and transmitting data through the service bearer may specifically include: stopping the restarted recovery timer based on the RRC reconfiguration message received before the restarted recovery timer expires, and rebuilding the transmission entity of the service bearer; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity; and transmitting data through the packet data aggregation protocol entity and the radio link control entity.

[0089] Optionally, if the terminal sends a NAS TAU message to the base station to trigger the base station to send an RRC connection reconfiguration message and restart the recovery timer, and if the terminal receives the RRC connection reconfiguration message from the base station before the restarted recovery timer expires, the terminal can stop the recovery timer, rebuild the PDCP and RLC entities of SRB2 and all DRBs, and restore the transmission of SRB2 and all DRBs after the PDCP and RLC entities have been rebuilt. For example, if the UE sends a NAS TAU message to the base station via SRB1 to trigger the base station to send an RRCConnectionReconfiguration message and restart the Txxx timer, and if the UE receives the RRCConnectionReconfiguration message from the base station before the Txxx timer expires, the UE stops the Txxx timer, rebuilds the PDCP and RLC entities of SRB2 and all DRBs, and restores the transmission of SRB2 and all DRBs after the PDCP and RLC entities have been rebuilt.

[0090] In this embodiment, by receiving an RRC reconfiguration message before the restart-based recovery timer expires, the restart-based recovery timer is stopped, and the transmission entity carrying the service is rebuilt. Data transmission is performed through the packet data aggregation protocol entity and the radio link control entity. If the RRC connection reconfiguration message sent by the base station is not received before the timer expires, the base station can be actively triggered to send an RRC connection reconfiguration message. Upon receiving the RRC connection reconfiguration message sent by the base station, service data transmission is restored, thus avoiding service interruption.

[0091] In an exemplary embodiment, the above-described transmission recovery method may further include: if the recovery timer based on the restart times out and no RRC reconfiguration message is received, switching from the connected state to the idle state.

[0092] Optionally, if the terminal sends a NAS TAU message to the base station to trigger the base station to send an RRC connection reconfiguration message and restarts the recovery timer, and the restarted recovery timer times out without receiving the RRC connection reconfiguration message from the base station, the terminal can switch from the connected state to the idle state. For example, if the UE sends a NASTAU message to the base station via SRB1 to trigger the base station to send an RRCConnectionReconfiguration message and restarts the Txxx timer, and the Txxx timer times out without receiving the RRCConnectionReconfiguration message from the base station, the UE can leave the connected state and enter the IDLE state.

[0093] In this embodiment, if the RRC reconfiguration message is not received after the restart-based recovery timer expires, the terminal switches from the connected state to the idle state. This allows the terminal to enter the idle state when the RRC connection reconfiguration message sent by the base station is not received in two timeouts. The access is then re-initialized in the idle state, ensuring network availability.

[0094] In an exemplary embodiment, the tracking area update message is sent via the basic signaling bearer. The above-described transmission recovery method may further include: starting a first timer; based on the network-side device searched before the first timer expires, suspending the service bearer and the basic signaling bearer, sending an RRC connection reconstruction request to the network-side device, and starting a second timer; based on the RRC connection reconstruction message received before the second timer expires, restoring the basic signaling bearer, and sending an RRC connection reconstruction completion message to the network-side device via the restored basic signaling bearer.

[0095] The basic signaling bearer can be SRB1. The first timer can be a T113 timer. The network-side equipment can be, but is not limited to, a base station. The second timer can be a T301 timer.

[0096] Optionally, the terminal can start a first timer; if the first timer expires and no network-side device is found, the terminal leaves the connected state and enters the idle state; otherwise, if a network-side device is found before the first timer expires, the terminal can stop the first timer, suspend the service bearer and basic signaling bearer, send an RRC connection reconstruction request to the network-side device, and start a second timer; if the second timer expires and no RRC connection reconstruction message is received from the network-side device, the terminal leaves the connected state and enters the idle state; otherwise, if an RRC connection reconstruction message is received from the network-side device before the second timer expires, the terminal can stop the second timer, restore the basic signaling bearer, and send an RRC connection reconstruction complete message to the network-side device through the restored basic signaling bearer. For example, after the RRC connection re-establishment process begins, the terminal can start the T311 timer. If the strongest cell is not found before the T311 timer expires, the terminal leaves the connected state and enters the idle state. Otherwise, if the strongest cell is found before the T311 timer expires, the terminal can stop the T311 timer, suspend SRB1, SRB2, and DRB, send an RRC connection re-establishment request to the found base station, and start the T301 timer. If the RRC connection re-establishment message is not received from the base station before the T301 timer expires, the terminal leaves the connected state and enters the idle state. Otherwise, if the RRC connection re-establishment message is received from the base station before the T301 timer expires, the terminal can stop the T301 timer, resume SRB1, and send an RRC connection re-establishment completion message to the base station through SRB1.

[0097] In this embodiment, by starting a first timer, based on the network-side device searched before the first timer expires, the service bearer and basic signaling bearer are suspended, and an RRC connection reconstruction request is sent to the network-side device. A second timer is started, based on the RRC connection reconstruction message received before the second timer expires, the basic signaling bearer is restored, and an RRC connection reconstruction completion message is sent to the network-side device through the basic signaling bearer. The timing can be adjusted during cell selection and RRC connection reconstruction, ensuring the reliable implementation of RRC connection reconstruction.

[0098] To facilitate a deeper understanding of the embodiments of this application by those skilled in the art, a specific example will be used for illustration below.

[0099] The 3GPP protocol describes the RRC connection re-establishment process. Cell selection is performed, and a T311 timer is started. If a high-quality LTE cell is found before the timer expires, the T311 timer is stopped, and all Resource Blocks (RBs), including DRBs and SRBs, are suspended (except for SRB0). A T301 timer is then started, and an RRCConnectionReestablishmentRequest message is sent. If an RRCConnectionReestablishment message is received before the T301 timer expires, the T301 timer is stopped, and the PDCP and RLC entities of SRB1 are rebuilt. After reconstruction, SRB1 transmission is resumed, and the RRC connection re-establishment process is considered successfully completed. At this point, SRB2 and all DRBs are still suspended. According to the protocol, only if an RRCConnectionReconfiguration message without mobilityControlInfo is received can the PDCP and RLC entities of SRB2 and all DRBs be rebuilt, and transmission of SRB2 and all DRBs be resumed. However, if the RRC connection reconstruction process is successfully completed but the RRCConnectionReconfiguration message is never received again, SRB2 and all DRBs will remain in a suspended state. To prevent this scenario and address the issue of SRB2 and all DRBs being suspended and thus affecting subsequent data transmission, this application introduces a protection procedure.

[0100] This application introduces a non-standard timer that starts after the successful completion of the RRC connection re-establishment procedure. The timer duration is customizable. If an RRCConnectionReconfiguration message is received before the timeout, the UE actively stops the timer. If the UE does not receive the RRCConnectionReconfiguration message from the base station by the timer expires, the designed protection procedure is entered. This procedure can involve the UE actively sending a NAS TAU message using SRB1 to try to trigger the base station to send the RRCConnectionReconfiguration message. If this fails, the UE locally releases and enters the IDLE state to prevent SRB2 and all DRBs from remaining suspended, which would affect data transmission. If subsequent data transmission is required, the RRC connection establishment procedure can be followed.

[0101] Thus, if the base station does not send a reconfiguration message after the RRC connection reconstruction process is successfully completed, the UE can detect the anomaly and enter the protection process, thereby not affecting subsequent data transmission.

[0102] In one exemplary embodiment, such as Figure 2 As shown, a transmission recovery method is provided. The UE introduces a timer, for example, named Txxx timer, which is first started after the RRC connection reconstruction process is successfully completed. The timer duration can be customized, for example, it can default to 3 seconds, and its default value can be modified via AT commands or NV. If an RRCConnectionReconfiguration message is received before the timeout, the UE actively stops the timer. If the timer expires, the UE actively sends a NAS TAU message via SRB1 to attempt to trigger whether the network will send an RRCConnectionReconfiguration message, and then starts the timer a second time. If an RRCConnectionReconfiguration message is received before the timeout, the UE actively stops the timer. If the timer still expires, the UE proceeds to leave the connected state and enter the IDLE state. Specifically, taking the application to a terminal as an example, this method includes the following steps:

[0103] Step 1: Start the T311 timer to begin the cell selection process;

[0104] Step 2: If the T311 timer expires and the cell with the strongest signal is not found, the cell enters the idle state; if the cell with the strongest signal is found before the T311 timer expires, the T311 timer is stopped, all RBs except SRB0 are suspended, an RRC connection re-establishment request message is sent to the base station, and the T301 timer is started.

[0105] Step 3: If the T301 timer expires and no RRC connection reconstruction message is received from the base station, the system enters the idle state; if the T301 timer expires and an RRC connection reconstruction message is received from the base station, the T301 timer is stopped, SRB1 is rebuilt and restored, an RRC connection reconstruction completion message is sent to the base station, and the Txxx timer is started for the first time.

[0106] Step 4: If an RRC connection reconfiguration message is received from the base station before the Txxx timer expires, stop the Txxx timer and rebuild and restore SRB2 and DRB;

[0107] Step 5: If the Txxx timer expires and the RRC connection reconfiguration message sent by the base station is not received, a NAS TAU message is sent to the base station via SRB1, and the Txxx timer is started for the second time.

[0108] Step 6: If an RRC connection reconfiguration message is received from the base station before the second Txxx timer expires, the Txxx timer is stopped, and SRB2 and DRB are rebuilt and restored; if no RRC connection reconfiguration message is received from the base station before the second Txxx timer expires, the system enters the idle state.

[0109] As described above, this method can prevent the UE from not receiving the RRC reconfiguration message after the RRC reconstruction process is successfully completed, which would prevent the data transmission from being restored and affect the transmission and reception of user plane data and NAS signaling, resulting in a poor user experience. This method can improve the robustness of the UE reconstruction process under LTE.

[0110] In one exemplary embodiment, such as Figure 3 As shown, a transmission recovery method is provided, which is illustrated using a terminal as an example. The method includes the following steps:

[0111] Step S301: Start the first timer;

[0112] Step S302: Based on the network-side device found before the first timer expires, suspend the service bearer and basic signaling bearer, send an RRC connection reconstruction request to the network-side device, and start the second timer;

[0113] Step S303: Based on the RRC connection reconstruction message received before the second timer expires, restore the basic signaling bearer and send the RRC connection reconstruction complete message to the network-side device through the basic signaling bearer;

[0114] Step S304: In response to the sending of the RRC connection reconstruction completion message, start the service bearer recovery timer; the service bearer includes service signaling bearer and service data bearer;

[0115] Step S305: Based on the RRC reconfiguration message received before the recovery timer expires, stop the recovery timer and rebuild the transmission entity of the service bearer; the transmission entity includes the packet data aggregation protocol entity and the radio link control entity; data transmission is performed through the packet data aggregation protocol entity and the radio link control entity;

[0116] Step S306: If no RRC reconfiguration message is received after the recovery timer expires, a tracking area update message is sent to the network-side device, and the recovery timer is restarted;

[0117] Step S307: Based on the RRC reconfiguration message received before the restart recovery timer expires, stop the restart recovery timer and rebuild the transmission entity carrying the service; the transmission entity includes the packet data aggregation protocol entity and the radio link control entity; data transmission is performed through the packet data aggregation protocol entity and the radio link control entity;

[0118] Step S308: If the recovery timer based on the restart times out and no RRC reconfiguration message is received, the system switches from the connected state to the idle state.

[0119] Optionally, during the RRC connection reconstruction process, the terminal can first start a first timer (T311). If the first timer expires and the network-side device with the strongest signal is not found, it enters an idle state. Otherwise, if the network-side device with the strongest signal is found before the first timer expires, the service bearer (SRB2+DRB) and the basic signaling bearer (SRB1) are suspended, an RRC connection reconstruction request is sent to the network-side device, and a second timer (T301) is started.

[0120] If the RRC connection re-establishment message sent by the base station is not received before the second timer expires, the system enters the idle state. Otherwise, if the RRC connection re-establishment message sent by the base station is received before the second timer expires, the basic signaling bearer (SRB1) is restored, and the RRC connection re-establishment completion message is sent to the network-side device through the restored basic signaling bearer. The recovery timer (Txxx) is started for the first time.

[0121] If an RRC connection reconfiguration message is received from the base station before the recovery timer expires, the recovery timer is stopped, the PDCP entity and RLC entity are rebuilt, and data is transmitted through the rebuilt PDCP entity and RLC entity; otherwise, if no RRC connection reconfiguration message is received from the base station before the recovery timer expires, the terminal can send a Tracking Area Update (NAS TAU) message to the network-side device and start the recovery timer (Txxx) a second time.

[0122] If an RRC connection reconfiguration message is received from the base station before the restarted recovery timer expires, the recovery timer is stopped, the PDCP entity and RLC entity are rebuilt, and data transmission is performed through the rebuilt PDCP entity and RLC entity; otherwise, if the restarted recovery timer expires before an RRC connection reconfiguration message is received from the base station, the terminal can switch from connected state to idle state.

[0123] The above-described transmission recovery method can set a timer for the RRC connection reconfiguration message sent by the network-side device after the RRC connection is successfully rebuilt. If the RRC connection reconfiguration message is not received after the timer expires, corresponding processing is performed to avoid the service bearer SRB2 and DRB being suspended for a long time, which would prevent user data from being transmitted and ensure the reliable transmission of subsequent user data.

[0124] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0125] Based on the same inventive concept, this application also provides a transmission recovery apparatus for implementing the transmission recovery method described above. This apparatus can be applied to or integrated into a chip or chip module, for example. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more transmission recovery apparatus embodiments provided below can be found in the limitations of the transmission recovery method described above, and will not be repeated here.

[0126] In one exemplary embodiment, such as Figure 4 As shown, a transmission recovery device is provided, comprising: a startup module 402 and a transmission module 404, wherein:

[0127] The startup module 402 is used to start the service bearer recovery timer in response to the sending of the RRC connection reconstruction completion message; the service bearer includes service signaling bearer and service data bearer;

[0128] The transmission module 404 is used to restore the service bearer according to the recovery timer and to transmit data through the restored service bearer.

[0129] In an exemplary embodiment, the transmission module 404 is further configured to stop the recovery timer and rebuild the transmission entity carrying the service based on the RRC reconfiguration message received before the recovery timer expires; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity; data transmission is performed through the packet data aggregation protocol entity and the radio link control entity.

[0130] In an exemplary embodiment, the transmission module 404 is further configured to send a tracking area update message to the network-side device and restart the recovery timer if no RRC reconfiguration message is received after the recovery timer expires; restore the service bearer according to the restarted recovery timer, and perform data transmission through the restored service bearer.

[0131] In an exemplary embodiment, the transmission module 404 is further configured to stop the restarted recovery timer and rebuild the transmission entity carrying the service based on the RRC reconfiguration message received before the restarted recovery timer expires; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity; data transmission is performed through the packet data aggregation protocol entity and the radio link control entity.

[0132] In an exemplary embodiment, the above-described transmission recovery device further includes a switching module, used to switch from the connected state to the idle state if the recovery timer expires after the restart and no RRC reconfiguration message is received.

[0133] In an exemplary embodiment, the transmission recovery device further includes a request module for starting a first timer; suspending the service bearer and the basic signaling bearer based on the network-side device found before the first timer expires, sending an RRC connection reconstruction request to the network-side device, and starting a second timer; restoring the basic signaling bearer based on the RRC connection reconstruction message received before the second timer expires, and sending an RRC connection reconstruction completion message to the network-side device through the basic signaling bearer.

[0134] Regarding the modules / units included in the various devices and products described in the above embodiments, they can be software modules / units, hardware modules / units, or a combination of both. For example, for various devices and products applied to or integrated into a chip, all of their modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits; for various devices and products applied to or integrated into a chip module, all of their modules / units can be implemented using hardware methods such as circuits, and different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0135] In one exemplary embodiment, a terminal device is provided, the internal structure of which can be as follows: Figure 5As shown, the terminal device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a transmission recovery method. The display unit of the terminal device forms a visually visible image and can be a display screen, projection device, or virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the terminal device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the terminal device, or external keyboards, touchpads, or mice, etc.

[0136] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the solution of this application and does not constitute a limitation on the terminal device to which the solution of this application is applied. A specific terminal device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0137] In one exemplary embodiment, a terminal device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0138] Based on the same inventive concept, this application also provides a chip, including a processor and a communication interface; the communication interface is used to receive or send data; the processor is configured to cause the chip to perform the following steps:

[0139] In response to the sending of the RRC connection reconstruction completion message, a recovery timer for the service bearer is started; the service bearer includes service signaling bearer and service data bearer;

[0140] The service bearer is restored according to the recovery timer, and data is transmitted through the restored service bearer.

[0141] In one embodiment, the processor is configured to cause the chip to perform the following steps:

[0142] Based on the RRC reconfiguration message received before the recovery timer expires, the recovery timer is stopped, and the transmission entity carrying the service is rebuilt; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity;

[0143] Data transmission is performed through the packet data convergence protocol entity and the radio link control entity.

[0144] In one embodiment, the processor is configured to cause the chip to perform the following steps:

[0145] If no RRC reconfiguration message is received after the recovery timer expires, a tracking area update message is sent to the network-side device, and the recovery timer is restarted.

[0146] The service bearer is restored according to the restart recovery timer, and data is transmitted through the restored service bearer.

[0147] In one embodiment, the processor is configured to cause the chip to perform the following steps:

[0148] Based on the RRC reconfiguration message received before the restart recovery timer expires, the restart recovery timer is stopped, and the transmission entity carrying the service is rebuilt; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity;

[0149] Data transmission is performed through the packet data convergence protocol entity and the radio link control entity.

[0150] In one embodiment, the processor is configured to cause the chip to perform the following steps:

[0151] If the recovery timer expires after the restart and no RRC reconfiguration message is received, the system switches from the connected state to the idle state.

[0152] In one embodiment, the processor is configured to cause the chip to perform the following steps:

[0153] Start the first timer;

[0154] Based on the network-side device found before the first timer expires, the service bearer and the basic signaling bearer are suspended, an RRC connection reconstruction request is sent to the network-side device, and a second timer is started;

[0155] Based on the RRC connection reconstruction message received before the second timer expires, the basic signaling bearer is restored, and the RRC connection reconstruction complete message is sent to the network-side device through the basic signaling bearer.

[0156] It is understood that the chip involved in the embodiments of this application may be a field-programmable gate array (FPGA), may include an application-specific integrated circuit (ASIC), may be a system on chip (SoC), may be a central processor unit (CPU), may be a network processor (NP), may be a digital signal processor (DSP), may be a microcontroller unit (MCU), may be a programmable logic device (PLD), or other integrated chips, etc.

[0157] Based on the same inventive concept, this application also provides a chip module, such as... Figure 6 As shown, the chip module includes a communication module, a power module, a storage module, and a chip. Among them:

[0158] The power module is used to provide power to the chip module; the storage module is used to store data and instructions; the communication module is used for internal communication within the chip module, or for communication between the chip module and external devices; this chip corresponds to the chip in the above chip embodiment.

[0159] The implementation method of this chip module can be found in the relevant content of the above chip embodiment, and will not be repeated here.

[0160] In one exemplary embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above-described method embodiments.

[0161] In one exemplary embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0162] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0163] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0164] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0165] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A transmission recovery method, characterized in that, Applied to the terminal side, the method includes: In response to the sending of the RRC connection reconstruction completion message, a recovery timer for the service bearer is started; the service bearer includes service signaling bearer and service data bearer; The service bearer is restored according to the recovery timer, and data is transmitted through the restored service bearer.

2. The method of claim 1, wherein, The step of restoring the service bearer according to the recovery timer and transmitting data through the restored service bearer includes: Based on the RRC reconfiguration message received before the recovery timer expires, the recovery timer is stopped, and the transmission entity carrying the service is rebuilt; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity; Data transmission is performed through the packet data convergence protocol entity and the radio link control entity.

3. The method according to claim 1, characterized in that, The step of restoring the service bearer according to the recovery timer and transmitting data through the restored service bearer includes: If no RRC reconfiguration message is received after the recovery timer expires, a tracking area update message is sent to the network-side device, and the recovery timer is restarted. The service bearer is restored according to the restart recovery timer, and data is transmitted through the restored service bearer.

4. The method according to claim 3, characterized in that, The step of restoring the service bearer according to the restarted recovery timer and transmitting data through the service bearer includes: Based on the RRC reconfiguration message received before the restart recovery timer expires, the restart recovery timer is stopped, and the transmission entity carrying the service is rebuilt; the transmission entity includes a packet data aggregation protocol entity and a radio link control entity; Data transmission is performed through the packet data convergence protocol entity and the radio link control entity.

5. The method according to claim 3, characterized in that, The method further includes: If the recovery timer expires after the restart and no RRC reconfiguration message is received, the system switches from the connected state to the idle state.

6. The method according to claim 3, characterized in that, The tracking area update message is sent via a basic signaling bearer, and the method further includes: Start the first timer; Based on the network-side device found before the first timer expires, the service bearer and the basic signaling bearer are suspended, an RRC connection reconstruction request is sent to the network-side device, and a second timer is started; Based on the RRC connection reconstruction message received before the second timer expires, the basic signaling bearer is restored, and the RRC connection reconstruction complete message is sent to the network-side device through the basic signaling bearer.

7. A transmission recovery device, characterized in that, Applied to the terminal side, the device includes: The startup module is used to start the service bearer recovery timer in response to the sending of the RRC connection reconstruction completion message; the service bearer includes service signaling bearer and service data bearer; The transmission module is used to restore the service bearer according to the recovery timer and to transmit data through the restored service bearer.

8. A terminal device, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A chip module, characterized in that, This includes communication modules, power modules, storage modules, and chips, among which: The power module is used to provide power to the chip module; The storage module is used to store data and instructions; The communication module is used for internal communication within the chip module, or for communication between the chip module and external devices. The chip is used to perform the steps of the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images