Control processing method and apparatus, and storage medium

Abstract

The present disclosure provides a control processing method and device, and a storage medium, wherein the control processing method comprises: in response to receiving a radio resource control (RRC) release message when performing a target process or performing the target process in a delay period, stopping or canceling the target process or RRC release process; wherein the delay period is a period from when the terminal receives the RRC release message to when the terminal delays for a specified time period to perform an RRC release related behavior, and the target process is a radio link failure (RLF) related process or an RRC reestablishment process. The present disclosure can reduce the impact of the RRC release process on the radio link failure (RLF) related process and the RRC reestablishment process, improve the reliability of the radio link, and thus improve the performance of the system.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the field of communications, and in particular, to a control processing method and apparatus, and a storage medium. BACKGROUND

[0002] In an RRC (Radio Resource Control) Release procedure, the terminal does not immediately perform subsequent procedures upon receiving an RRC Release message, but waits for a protocol-specified time period after receiving the RRC Release message, or performs subsequent operations when the terminal lower layer (lower than the RRC layer) indicates that the RRC Release message has been successfully confirmed (whichever is earlier).

[0003] However, during the protocol-specified processing delay or the time period for the lower layer confirmation message, the terminal may detect an RLF (Radio Link Failure) or RRC reestablishment. If the terminal performs an RRC Release related behavior during the RRC reestablishment procedure, it will cause the reestablishment to fail. In an NTN (Non-Terrestrial Networks), due to the large transmission delay, the delay time period of the RRC Release related behavior may need to be extended in the NTN, so the corresponding impact will be greater. SUMMARY

[0004] To overcome the problems in the related art, embodiments of the present disclosure provide a control processing method and apparatus, and a storage medium.

[0005] According to a first aspect of embodiments of the present disclosure, a control processing method is provided, which is applied to a terminal and includes:

[0006] In response to receiving a radio resource control (RRC) release message when performing a target procedure or performing the target procedure in a delay period, stopping or canceling the target procedure or the RRC release procedure;

[0007] The delay period is a time period from when the terminal receives the RRC release message to when the terminal delays a specified time period to perform an RRC release related behavior, and the target procedure is an RLF (Radio Link Failure) related procedure or an RRC reestablishment procedure.

[0008] Optionally, in response to receiving an RRC release message when performing a target procedure, stopping or canceling the target procedure includes:

[0009] stop or cancel the RLF-related procedure in response to receiving the RRC release message when detecting the RLF.

[0010] Optionally, the method further comprises:

[0011] continue the process after detecting the RLF in response to not receiving the RRC release message when detecting the RLF.

[0012] Optionally, in response to receiving a radio resource control (RRC) release message when performing a target procedure, the target procedure is stopped or cancelled, including:

[0013] in response to receiving the RRC release message when starting a specified timer, the specified timer is not started, wherein the specified timer is a timer corresponding to the RLF-related procedure.

[0014] Optionally, the response to receiving the RRC release message when starting a specified timer includes:

[0015] in response to receiving the RRC release message when a starting condition corresponding to the specified timer is met, the specified timer is not started.

[0016] Optionally, the method further comprises:

[0017] in response to not receiving the RRC release message when starting a specified timer, the specified timer is started, wherein the specified timer is a timer corresponding to the RLF-related procedure.

[0018] Optionally, the response to not receiving the RRC release message when starting a specified timer includes:

[0019] in response to not receiving the RRC release message when a starting condition corresponding to the specified timer is met, the specified timer is started.

[0020] Optionally, in response to receiving a radio resource control (RRC) release message when performing a target procedure, the target procedure is stopped or cancelled, including:

[0021] in response to receiving the RRC release message when performing a physical layer problem detection in an RRC connected state, the physical layer problem detection procedure is stopped or cancelled.

[0022] Optionally, the method further comprises:

[0023] in response to not receiving the RRC release message when performing a physical layer problem detection, the physical layer problem detection procedure is continued.

[0024] Optionally, in response to receiving a radio resource control (RRC) release message while performing a target procedure, stopping or canceling the target procedure, comprises:

[0025] stopping a specified timer in response to receiving the RRC release message while the specified timer is running; wherein the specified timer is a timer corresponding to the RLF-related procedure.

[0026] Optionally, in response to receiving a radio resource control (RRC) release message while performing a target procedure, stopping or canceling the RRC release procedure, comprises:

[0027] stopping or canceling the RRC release procedure in response to detecting RLF while receiving the RRC release message.

[0028] Optionally, in response to performing a target procedure for a delay period, stopping or canceling the RRC release procedure, comprises:

[0029] stopping or canceling the RRC release procedure in response to detecting RLF within the delay period.

[0030] Optionally, the method further comprises:

[0031] performing the RRC release procedure in response to not detecting RLF before expiration of the delay period.

[0032] Optionally, the target procedure is a RLF-related procedure, and the radio link failure information contains indication information; wherein the indication information is used to indicate whether the terminal receives the RRC release message when detecting RLF.

[0033] Optionally, the indication information is of an enumerated type or a Boolean type.

[0034] Optionally, in response to receiving a radio resource control (RRC) release message while performing a target procedure, stopping or canceling the target procedure, comprises:

[0035] not starting the RRC reestablishment procedure in response to not meeting any condition for starting the RRC reestablishment or receiving the RRC release message.

[0036] Optionally, the method further comprises:

[0037] starting the RRC reestablishment procedure in response to meeting any condition for starting the RRC reestablishment and not receiving the RRC release message.

[0038] Optionally, in response to performing a target procedure for a delay period, stopping or canceling the radio resource control (RRC) release procedure, comprises:

[0039] stop or cancel the RRC release procedure in response to the RRC re-establishment procedure being initiated before the delay period expires.

[0040] Optionally, the method further comprises:

[0041] Optionally, the method further comprises:

[0042] Optionally, the method further comprises:

[0043] Optionally, the method further comprises:

[0044] Optionally, the method further comprises:

[0045] Optionally, the method further comprises:

[0046] According to a second aspect of embodiments of the present disclosure, a control processing apparatus is provided, the apparatus being applied to a terminal and comprising:

[0047] a control module configured to stop or cancel a target procedure or a radio resource control (RRC) release procedure in response to receiving an RRC release message while executing the target procedure or executing the target procedure in a delay period;

[0048] wherein the delay period is a time period from when the terminal receives the RRC release message to when the terminal delays for a specified time duration to execute an RRC release related behavior, and the target procedure is a radio link failure (RLF) related procedure or an RRC re-establishment procedure.

[0049] According to a third aspect of embodiments of the present disclosure, a computer readable storage medium is provided, the storage medium storing a computer program, the computer program being configured to execute any of the control processing methods described above.

[0050] According to a fourth aspect of embodiments of the present disclosure, a control processing apparatus is provided, comprising:

[0051] a processor;

[0052] a memory for storing processor executable instructions;

[0053] wherein the processor is configured to execute any of the control processing methods described above.

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

[0055] In the embodiments of the present disclosure, when the terminal receives the RRC release message during the execution of the target process, the terminal can stop or cancel the target process or the RRC release process. Alternatively, when the terminal executes the target process during the delay period, the terminal can also stop or cancel the target process or the RRC release process. The delay period is a period of time from when the terminal receives the RRC release message to when the terminal delays for a specified time period to execute the RRC release related behavior, and the target process is a radio link failure (RLF) related process or an RRC reestablishment process. The present disclosure can reduce the impact of the RRC release process on the radio link failure (RLF) related process and the RRC reestablishment process, improve the reliability of the radio link, and thus improve the system performance.

[0056] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0057] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0058] Figure 1 FIG. 1 is a schematic diagram of an RRC release process according to an exemplary embodiment.

[0059] Figures 2A-2B FIG. 2 is a schematic diagram of an RRC reestablishment process according to an exemplary embodiment.

[0060] Figure 3 FIG. 3 is a schematic diagram of a control processing method flow according to an exemplary embodiment.

[0061] Figure 4 FIG. 4 is another schematic diagram of a control processing method flow according to an exemplary embodiment.

[0062] Figure 5 FIG. 5 is another schematic diagram of a control processing method flow according to an exemplary embodiment.

[0063] Figure 6 FIG. 6 is another schematic diagram of a control processing method flow according to an exemplary embodiment.

[0064] Figure 7 FIG. 7 is another schematic diagram of a control processing method flow according to an exemplary embodiment.

[0065] Figure 8 FIG. 8 is another schematic diagram of a control processing method flow according to an exemplary embodiment.

[0066] Figure 9 is another control processing method flowchart diagram according to an exemplary embodiment.

[0067] Figure 10 is another control processing method flowchart diagram according to an exemplary embodiment.

[0068] Figure 11 is another control processing method flowchart diagram according to an exemplary embodiment.

[0069] Figure 12 is another control processing method flowchart diagram according to an exemplary embodiment.

[0070] Figure 13 is another control processing method flowchart diagram according to an exemplary embodiment.

[0071] Figure 14 is another control processing method flowchart diagram according to an exemplary embodiment.

[0072] Figure 15 is another control processing method flowchart diagram according to an exemplary embodiment.

[0073] Figure 16 is another control processing method flowchart diagram according to an exemplary embodiment.

[0074] Figure 17 is another control processing method flowchart diagram according to an exemplary embodiment.

[0075] Figure 18 is another control processing method flowchart diagram according to an exemplary embodiment.

[0076] Figure 19 is another control processing method flowchart diagram according to an exemplary embodiment.

[0077] Figure 20 is another control processing method flowchart diagram according to an exemplary embodiment.

[0078] Figure 21 is another control processing method flowchart diagram according to an exemplary embodiment.

[0079] Figure 22 is another control processing method flowchart diagram according to an exemplary embodiment.

[0080] Figure 23 is a control processing device block diagram according to an exemplary embodiment.

[0081] Figure 24 This is a schematic diagram of a control processing device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0082] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0083] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of at least one associated listed item.

[0084] It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0085] Before introducing the control and processing methods provided in this disclosure, let’s first introduce the RRC release process.

[0086] Reference Figure 1 As shown, the main purpose of the RRC release process is to release the RRC connection, including releasing established radio bearers and all radio resources; and to suspend the RRC connection only when establishing SRB2 (Signalling Radio Bearer 2) and at least one DRB (Data Radio Bearer), including suspending the established radio bearers. SRB2 is established after RRC reconfiguration and is used to carry NAS (Non-Access Stratum) signaling.

[0087] The network side switches the terminal to an idle state or an inactive state by initiating an RRC release procedure, or releases the terminal and redirects it to another frequency.

[0088] In the related art, a 60-millisecond delay is introduced for the RRC release procedure, and the RRC release message is delayed for processing to give sufficient time for sending HARQ (Hybrid Automatic Repeat reQuest) and RLC (Radio Link Control) acknowledgments, so that the network side knows that the RRC release message has been received by the terminal, and there is no state mismatch between the terminal and the network side.

[0089] In addition, the terminal detecting RLF includes but is not limited to any one of the following cases: the first case, when the timer T310 expires in the PCell (Primary Cell) / PSCell (Primary Secondary Cell), it is determined that RLF is detected. The second case, when the timer T312 expires in the PCell / PSCell, it is determined that RLF is detected. The third case, when the timers T300, T301, T304, T311 and T319 are not running, the MCG (Master Cell group) MAC (Media Access Control) sends a random access problem indication; or when the SCG (Secondary Cell group) RLC indicates that the maximum number of retransmissions has been reached, it is determined that RLF is detected. The fourth case, when the MCG / SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that RLF is detected. The fifth case, if connected as an IAB (Integrated Access and Backhaul) node, after receiving a BH RLF indication on the BAP (Broadband Access Point) entity from the MCG / SCG, it is determined that RLF is detected. The sixth case, when the timer T304 is not running, the MCG MAC sends a consistent uplink LBT (Llisten Before Talk) failure indication; or the SCG MAC sends a consistent uplink LBT failure indication, it is determined that RLF is detected.

[0090] In addition, regarding the RRC reestablishment procedure, refer to Figure 2AAs shown in FIG. 1, the terminal can send an RRCReestablishmentRequest message to a network side device, such as a base station, and the network side device feeds back an RRCReestablishment message to the terminal when the RRC reestablishment is successful, and the terminal sends an RRCReestablishmentComplete message to the network side device after receiving the RRCReestablishment message.

[0091] Alternatively, referring to FIG. 2, the terminal can send an RRCReestablishmentRequest message to a network side device, such as a base station, and the network side device falls back to RRC establishment, i.e., the network side device feeds back an RRCSetup message to the terminal, and the terminal sends an RRCSetupComplete message to the network side device after receiving the RRCSetup message. Figure 2B

[0092] The RRC reestablishment procedure is to reestablish the RRC connection. The terminal in the connected state has activated AS (Access Stratum) security using SRB2 and at least one DRB setting, and can initiate the procedure to continue the RRC connection. If the network can find and verify the valid terminal context, or if the terminal context cannot be retrieved, and the network responds with an RRCSetup message, the connection reestablishment is successful. If the AS security has not been activated, the terminal will not start the procedure, but will directly transfer to the idle state with the release reason of "other". If the AS security has been activated, but SRB2 and at least one DRB have not been set, the terminal will not start the procedure, but will directly transfer to the idle state, which causes the RRC connection to fail.

[0093] To reduce the impact of the RRC release procedure on the radio link failure (RLF) related procedure and the RRC reestablishment procedure, the present disclosure provides the following control processing method.

[0094] The embodiment of the present disclosure provides a control processing method, referring to FIG. 3, a control processing method flowchart according to an embodiment can be used for a terminal, and the method can include the following steps. Figure 3 Figure 3 The method can include the following steps:

[0095] In step 301, in response to receiving a radio resource control (RRC) release message when performing a target procedure or performing the target procedure in a delay period, stopping or canceling the target procedure or the RRC release procedure.

[0096] ​​In the embodiments of the present disclosure, the delay period is a period of time from when the terminal receives the RRC release message to when the terminal delays for a specified duration to perform an RRC release related behavior, the target procedure is a radio link failure (RLF) related procedure or an RRC reestablishment procedure. The specified duration is a protocol agreed processing delay (generally 60 ms), or the shorter of the protocol specified processing delay (generally 60 ms) and the duration from when the terminal receives the RRCRelease message to when the lower layer (lower than the RRC layer) indicates a successful confirmation of receiving the RRC release message.

[0097] The RRC release related behavior includes, but is not limited to, at least one of the following: entering a non-connected state, including but not limited to entering an Idle state or entering an inactive state; stopping or starting a related timer, including but not limited to stopping timer T310, stopping timer T320, stopping timer T316, stopping timer T350, stopping timer T331, starting timer T320, starting or restarting timer T325; storing cell reselection priority information; determining the content of VarMeasIdleConfig; removing the CHO (Conditional HandOver) related configuration stored by the terminal if CHO is configured, and the like.

[0098] The RLF related procedure includes, but is not limited to, at least one of the following: RLF detection; physical layer problem detection; recovery of physical layer problems; RLM (Radio Link Monitoring); starting and stopping of a specified timer; RLF cause determination; RLF report content determination; and the like.

[0099] The RLF detection procedure includes, but is not limited to, the processing procedure after detecting RLF, the specified timer is a timer corresponding to the RLF related procedure, including but not limited to timer T310 and timer T312, and the like. The RLF report content determination includes, but is not limited to, determining the content of failure information. In one possible implementation, the RLF report content determination includes determining the content of varRLF-report.

[0100] The RRC reestablishment procedure includes, but is not limited to, starting RRC reestablishment and subsequent operations after starting RRC reestablishment, the subsequent operations including but not limited to cell selection, sending an RRC reestablishment request message, and the like.

[0101] In the above embodiments, the influence of the RRC release procedure on the radio link failure (RLF) related procedure and the RRC reestablishment procedure can be reduced, the wireless link reliability can be improved, and thus the system performance can be improved.

[0102] In some optional embodiments, the present disclosure also provides several other control processing methods.

[0103] In a possible implementation, the target procedure is continued in response to that the RRC release message is not received when the target procedure is performed.

[0104] The target procedure is a radio link failure (RLF) related procedure or a RRC reestablishment procedure.

[0105] The RLF related procedure includes, but is not limited to, at least one of the following: RLF detection; physical layer problem detection; physical layer problem recovery; RLM (Radio Link Monitoring); start and stop of a specified timer; RLF cause determination; RLF report content determination; and the like.

[0106] The RLF detection procedure includes, but is not limited to, a process after the RLF is detected, and the specified timer is a timer corresponding to the RLF related procedure, including, but not limited to, timer T310 and timer T312, and the like. The RLF report content determination includes, but is not limited to, determination of the content of failure information. In a possible implementation, the RLF report content determination includes determination of the content of varRLF-report.

[0107] The RRC reestablishment procedure includes, but is not limited to, start of the RRC reestablishment and subsequent operations after the RRC reestablishment is started, and the subsequent operations include, but are not limited to, cell selection, sending of a RRC reestablishment request message, and the like.

[0108] In another possible implementation, the RRC release procedure is continued in response to that the target procedure is not performed when the RRC release message is received.

[0109] The target procedure is a radio link failure (RLF) related procedure or a RRC reestablishment procedure.

[0110] The RLF related procedure includes, but is not limited to, at least one of the following: RLF detection; physical layer problem detection; physical layer problem recovery; RLM; start and stop of a specified timer; RLF cause determination; RLF report content determination; and the like.

[0111] The RLF detection procedure includes, but is not limited to, a process after the RLF is detected, and the specified timer is a timer corresponding to the RLF related procedure, including, but not limited to, timer T310 and timer T312, and the like. The RLF report content determination includes, but is not limited to, determination of the content of failure information. In a possible implementation, the RLF report content determination includes determination of the content of varRLF-report.

[0112] The RRC reestablishment procedure includes, but is not limited to, starting the RRC reestablishment and subsequent operations after the RRC reestablishment is started, and the subsequent operations include, but are not limited to, cell selection, sending an RRC reestablishment request message, and the like.

[0113] In another possible implementation, in response to the target procedure not being performed in the delay period, the RRC release procedure is continued to be performed.

[0114] In the embodiments of the present disclosure, the delay period is a time period from when the terminal receives the RRC release message to when the terminal delays performing an RRC release related behavior for a specified time length, the target procedure is a radio link failure (RLF) related procedure or an RRC reestablishment procedure, the specified time length is a protocol agreed processing delay (generally 60 ms), or a shorter time length of a protocol specified processing delay (generally 60 ms) and a time length from when the terminal receives the RRC release message to when a lower layer (lower than the RRC layer) indicates a successful confirmation of receiving the RRC release message, and the target procedure is a radio link failure (RLF) related procedure or an RRC reestablishment procedure.

[0115] The RLF related procedure includes, but is not limited to, at least one of the following: RLF detection; physical layer problem detection; recovery of the physical layer problem; RLM; starting and stopping of a specified timer; RLF cause determination; RLF report content determination; and the like.

[0116] The RLF detection procedure includes, but is not limited to, a processing procedure after the RLF is detected, the specified timer is a timer corresponding to the RLF related procedure, and includes, but is not limited to, timer T310 and timer T312, and the like. The RLF report content determination includes, but is not limited to, determining the content of the failure information. In a possible implementation, the RLF report content determination includes determining the content of varRLF-report.

[0117] The RRC reestablishment procedure includes, but is not limited to, starting the RRC reestablishment and subsequent operations after the RRC reestablishment is started, and the subsequent operations include, but are not limited to, cell selection, sending an RRC reestablishment request message, and the like.

[0118] In the above embodiments, the purpose of reducing the influence of the RRC release procedure on the radio link failure (RLF) related procedure and the RRC reestablishment procedure is also achieved, the wireless link reliability is improved, and the system performance is further improved.

[0119] In some optional embodiments, referring to Figure 4 , the method can include the following steps: Figure 4 is a control processing method flowchart according to an embodiment, which can be used for a terminal, and the method can include the following steps:

[0120] In step 401, in response to receiving the RRC release message when detecting the RLF, stop or cancel the RLF detection related procedure.

[0121] The RLF detection procedure includes but is not limited to the process after detecting the RLF. Receiving the RRC release message includes that the terminal has received the RRC release message.

[0122] The terminal detecting the RLF includes but is not limited to any one of the following cases: the first case, determining to detect the RLF when the timer T310 expires in the PCell / PSCell. The second case, determining to detect the RLF when the timer T312 expires in the PCell / PSCell. The third case, the MCG MAC sends a random access problem indication when the timers T300, T301, T304, T311 and T319 are not running; or determining to detect the RLF when the SCG RLC indicates that the maximum number of retransmissions has been reached. The fourth case, determining to detect the RLF when the MCG / SCG RLC indicates that the maximum number of retransmissions has been reached. The fifth case, if connected as an IAB node, determining to detect the RLF after receiving a BH RLF indication on the BAP entity from the MCG / SCG. The sixth case, determining to detect the RLF when the timer T304 is not running, the MCG MAC sends a consistent uplink LBT failure indication; or the SCG MAC sends a consistent uplink LBT failure indication.

[0123] The RLF related procedure includes but is not limited to at least one of the following: RLF detection; physical layer problem detection; recovery of physical layer problem; RLM (Radio Link Monitoring); start and stop of specified timer; RLF cause determination; RLF report content determination, etc.

[0124] The RLF detection procedure includes but is not limited to the process after detecting the RLF, the specified timer is the timer corresponding to the RLF related procedure, including but not limited to the timer T310 and the timer T312, etc. The RLF report content determination includes but is not limited to determining the content of the failure information. In one possible implementation, the RLF report content determination includes determining the content of varRLF-report.

[0125] In the above embodiment, if the terminal has received the RRC release message when detecting the RLF, the RLF detection related procedure can be stopped or cancelled, avoiding the influence of the RRC release procedure on the RLF detection related procedure, and improving the wireless link reliability.

[0126] In some optional embodiments, referring to Figure 5 , the method further includes the following steps. Figure 5is a control processing method flow chart according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0127] In step 501, in response to not receiving an RRC release message when detecting RLF, the process after detecting RLF is continued.

[0128] In the embodiments of the present disclosure, the terminal detecting RLF includes but is not limited to any one of the following cases: the first case, when the timer T310 expires in the PCell / PSCell, it is determined that RLF is detected. The second case, when the timer T312 expires in the PCell / PSCell, it is determined that RLF is detected. The third case, when the timers T300, T301, T304, T311 and T319 are not running, the MCG MAC sends a random access problem indication; or when the SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that RLF is detected. The fourth case, when the MCG / SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that RLF is detected. The fifth case, if connected as an IAB node, after receiving a BH RLF indication on the BAP entity from the MCG / SCG, it is determined that RLF is detected. The sixth case, when the timer T304 is not running, the MCG MAC sends a consistent uplink LBT failure indication; or the SCG MAC sends a consistent uplink LBT failure indication, it is determined that RLF is detected.

[0129] The process after detecting RLF includes but is not limited to at least one of the following: Report RLC failure (report RLC failure); store RLF information in VarRLF-report (wireless link failure report information); enter idle state; Report MCG RLF (report primary cell group radio link failure); start RRC reestablishment, etc.

[0130] In the above embodiments, if the terminal does not receive an RRC release message when detecting RLF, the process after detecting RLF can be continued, which also improves the reliability of the wireless link and has high availability.

[0131] In some optional embodiments, referring to Figure 6 , the method can include the following steps: Figure 6 is a control processing method flow chart according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0132] In step 601, in response to receiving an RRC release message when starting a specified timer, the specified timer is not started.

[0133] In the embodiments of the present disclosure, the specified timer is a timer corresponding to the RLF-related procedure, including but not limited to at least one of timers T310 and T312. Receiving the RRC release message includes that the terminal has received the RRC release message.

[0134] The RLF-related procedure is similar to the RLF-related procedure involved in the above embodiments, and will not be repeated here.

[0135] In the above embodiments, if the terminal has received the RRC release message when starting the specified timer, the specified timer is not started. The specified timer is a timer corresponding to the RLF-related procedure. Thus, the influence of the RRC release procedure on the RLF detection-related procedure is avoided, and the wireless link reliability is improved.

[0136] In some optional embodiments, referring to Figure 7 , the method can include the following steps: Figure 7 is a flow chart of a control processing method according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0137] In step 701, in response to receiving the RRC release message when the specified timer corresponding to the starting condition is met, the specified timer is not started.

[0138] In the embodiments of the present disclosure, the specified timer is a timer corresponding to the RLF-related procedure, including but not limited to at least one of timers T310 and T312. When the starting condition of the specified timer is met, receiving the RRC release message includes that the terminal has received the RRC release message, and the corresponding specified timer is not started.

[0139] The RLF-related procedure is similar to the RLF-related procedure involved in the above embodiments, and will not be repeated here.

[0140] In one possible implementation, when N310 consecutive out-of-sync indications of SpCell (including PCell and PSCell) are received from the lower layer of the terminal, the starting condition of timer T310 is met. If the terminal has received the RRC release message, the timer T310 is not started.

[0141] In another possible implementation, if the terminal meets the trigger condition of the configured measurement event, reportConfig is set to “true” in useT312, and timer T310 is running, i.e., the starting condition of timer T312 is met, and the terminal has received the RRC release message, the timer T312 is not started.

[0142] In the above embodiment, when the RRC release message is received when the start condition corresponding to the specified timer is met, the terminal can not start the specified timer. The specified timer is a timer corresponding to the RLF related process. Thus, the RRC release process does not affect the RLF detection related process, and the wireless link reliability is improved.

[0143] In some optional embodiments, referring to Figure 8 , Figure 8 is a control processing method flow chart according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0144] In step 801, the specified timer is started in response to that the RRC release message is not received when the specified timer is started.

[0145] In the embodiments of the present disclosure, the specified timer is a timer corresponding to the RLF related process, including but not limited to at least one of timers T310 and T312.

[0146] The RLF related process is similar to the RLF related process involved in the above embodiment, which will not be repeated here.

[0147] In the above embodiment, the terminal starts the specified timer if the RRC release message is not received when the specified timer is started. The specified timer is a timer corresponding to the RLF related process. Thus, the RRC release process does not affect the RLF detection related process, and the wireless link reliability is improved.

[0148] In some optional embodiments, referring to Figure 9 , Figure 9 is a control processing method flow chart according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0149] In step 901, the specified timer is started in response to that the RRC release message is not received by the terminal when the start condition corresponding to the specified timer is met.

[0150] In the embodiments of the present disclosure, the specified timer is a timer corresponding to the RLF related process, including but not limited to at least one of timers T310 and T312. When the start condition of the specified timer is met, the terminal does not receive the RRC release message, and then the corresponding specified timer is started.

[0151] The RLF related process is similar to the RLF related process involved in the above embodiment, which will not be repeated here.

[0152] In a possible implementation, when receiving N310 consecutive out-of-sync indications of SpCell from a lower layer of the terminal, a starting condition of starting a timer T310 is met, and if the terminal does not receive an RRC release message, the timer T310 is started.

[0153] In another possible implementation, if the terminal meets a triggering condition of a configured measurement event, useT312 in reportConfig is set to "true", and a timer T310 is running, that is, a starting condition of starting a timer T312 is met, and the terminal does not receive an RRC release message, the timer T312 is started.

[0154] In the above embodiments, when a starting condition corresponding to a specified timer is met, and an RRC release message is not received, the terminal can start the specified timer. The specified timer is a timer corresponding to an RRLF-related process. In this way, the influence of the RRC release process on the RRLF detection-related process is avoided, and the wireless link reliability is improved.

[0155] In some optional embodiments, the present disclosure adds at least one of a new starting condition and a new stopping condition for a specified timer. The specified timer is a timer corresponding to an RRLF-related process, including but not limited to at least one of timers T310 and T312. The RRLF-related process is similar to the RRLF-related process involved in the above embodiments, and will not be described here.

[0156] In the embodiments of the present disclosure, the new starting condition can be that an RRC release message is not received.

[0157] In a possible implementation, the new starting condition can be met at the same time as other starting conditions corresponding to the specified timer, that is, in the case that an RRC release message is not received and the original starting condition of the timer is met, the terminal starts the specified timer.

[0158] In the embodiments of the present disclosure, the new stopping condition can be that an RRC release message is received.

[0159] In a possible implementation, when the terminal receives an RRC release message, that is, in the case that the new stopping condition is met, the terminal can stop the specified timer.

[0160] In another possible implementation, when any one of the original stopping conditions of the specified timer is met, the terminal stops the specified timer.

[0161] In another possible implementation, when the terminal meets the new stopping condition or any one of the original stopping conditions, that is, when the terminal receives an RRC release message or meets any one of the original stopping conditions, the terminal stops the specified timer.

[0162] In the above embodiment, a new starting condition and / or a new stopping condition are provided for the specified timer, thereby avoiding the impact of the RRC release procedure on the RLF detection related procedure, and improving the wireless link reliability.

[0163] In some optional embodiments, as shown in Figure 10 , a control processing method flowchart according to an embodiment can be used for a terminal, and the method can include the following steps: Figure 10 , a control processing method flowchart according to an embodiment can be used for a terminal, and the method can include the following steps:

[0164] In step 1001, in response to receiving an RRC release message when performing physical layer problem detection in an RRC connected state, the physical layer problem detection procedure is stopped or cancelled.

[0165] In the embodiments of the present disclosure, the physical layer problem detection includes but is not limited to synchronous detection and / or asynchronous detection. Receiving the RRC release message includes that the terminal has received the RRC release message.

[0166] In the above embodiment, when the terminal receives the RRC release message when performing the physical layer problem detection in the RRC connected state, the terminal can stop or cancel the physical layer problem detection procedure. The impact of the RRC release procedure on the RLF detection related procedure is avoided, and the wireless link reliability is improved.

[0167] In some optional embodiments, as shown in Figure 11 , a control processing method flowchart according to an embodiment can be used for a terminal, and the method can include the following steps: Figure 11 , a control processing method flowchart according to an embodiment can be used for a terminal, and the method can include the following steps:

[0168] In step 1101, in response to not receiving an RRC release message when performing physical layer problem detection, the physical layer problem detection procedure is continued.

[0169] In the embodiments of the present disclosure, the physical layer problem detection includes but is not limited to synchronous detection and / or asynchronous detection.

[0170] In the above embodiment, when the terminal does not receive the RRC release message when performing the physical layer problem detection in the RRC connected state, the terminal can continue to perform the physical layer problem detection procedure. The purpose of avoiding the impact of the RRC release procedure on the RLF detection related procedure is also achieved, and the wireless link reliability is improved.

[0171] In some optional embodiments, as shown in Figure 12 , a control processing method flowchart according to an embodiment can be used for a terminal, and the method can include the following steps: Figure 12 , a control processing method flowchart according to an embodiment can be used for a terminal, and the method can include the following steps:

[0172] In step 1201, in response to receiving the RRC release message while the specified timer is running, the specified timer is stopped.

[0173] In the embodiments of the present disclosure, the specified timer is a timer corresponding to the RLF-related procedure, including but not limited to at least one of timers T310 and T312. The RLF-related procedure is similar to the RLF-related procedure involved in the above embodiments, and will not be repeated here.

[0174] In the embodiments of the present disclosure, the specified timer is a timer corresponding to the RLF-related procedure, including but not limited to at least one of timers T310 and T312. The RLF-related procedure is similar to the RLF-related procedure involved in the above embodiments, and will not be repeated here.

[0175] In one possible implementation, the terminal does not need to wait for the processing delay of the RRC release message to expire before stopping the specified timer. The processing delay is a protocol-specified processing delay, which is generally 60 ms.

[0176] In another possible implementation, the terminal does not need to wait for the terminal lower layer to indicate that the RRC release message has been successfully received before stopping the specified timer.

[0177] In another possible implementation, the terminal does not need to wait for the processing delay of the RRC release message to expire and the terminal lower layer to indicate that the RRC release message has been successfully received, whichever comes first, before stopping the specified timer. The processing delay is a protocol-specified processing delay, which is generally 60 ms.

[0178] In the above embodiments, if the terminal receives the RRC release message while the specified timer is running, the terminal can immediately stop the specified timer. This avoids the RRC release procedure from affecting the RLF detection-related procedure, thereby improving the reliability of the wireless link.

[0179] In some optional embodiments, the present disclosure adds a new stopping condition for the specified timer, specifically, the new stopping condition can include receiving the RRC release message. The specified timer is a timer corresponding to the RLF-related procedure, including but not limited to at least one of timers T310 and T312. The RLF-related procedure is similar to the RLF-related procedure involved in the above embodiments, and will not be repeated here.

[0180] In one possible implementation, when the new stopping condition is met, i.e., the RRC release message is received, the terminal can stop the corresponding specified timer.

[0181] In another possible implementation, when any of the other stopping conditions is met, i.e., any of the protocol-specified existing stopping conditions is met, the terminal stops the corresponding specified timer.

[0182] In another possible implementation, the terminal stops the corresponding specified timer in response to any one of the following: the terminal receives an RRC release message or any one of the existing stopping conditions agreed by the protocol.

[0183] In the above embodiment, a new stopping condition is added to the specified timer, and the implementation is simple and highly available.

[0184] In some optional embodiments, as shown in Figure 13 Figure 13 FIG. 13 is a flow chart of a control processing method according to an embodiment, which can be used in a terminal. The method can include the following steps:

[0185] In step 1301, the RLM procedure is stopped or cancelled in response to receiving an RRC release message after the wireless link monitoring (RLM) procedure is started.

[0186] In the embodiment of the present disclosure, the terminal can immediately stop the RLM procedure upon receiving the RRC release message.

[0187] In one possible implementation, the terminal can immediately stop the RLM procedure without waiting for the processing delay to expire. The processing delay is a processing delay agreed by the protocol, which is generally 60 milliseconds.

[0188] In another possible implementation, the terminal can immediately stop the RLM procedure without waiting for the lower layer to indicate that the RRC release message has been successfully received.

[0189] In another possible implementation, the terminal can immediately stop the RLM procedure without waiting for the earlier of the following: the processing delay to expire or the lower layer to indicate that the RRC release message has been successfully received.

[0190] The RLM procedure includes a monitoring and reporting procedure. The monitoring is to monitor the downlink radio link quality of the current cell, and the reporting is to indicate a synchronous / asynchronous state to a higher layer.

[0191] In the above embodiment, the impact of the RRC release procedure on the RLM procedure is reduced, the wireless link reliability is improved, and the system performance is further improved.

[0192] In some optional embodiments, as shown in Figure 14 Figure 14 FIG. 14 is a flow chart of a control processing method according to an embodiment, which can be used in a terminal. The method can include the following steps:

[0193] In step 1401, the RRC release procedure is stopped or cancelled in response to receiving an RRC release message when detecting an RLF. ​​

[0194] In the embodiments of the present disclosure, if the terminal has received the RRC release message when detecting the RLF, the terminal stops or cancels the subsequent RRC release related behavior.

[0195] The terminal detecting the RLF includes but is not limited to any one of the following cases: in the first case, when the timer T310 expires in the PCell / PSCell, it is determined that the RLF is detected. In the second case, when the timer T312 expires in the PCell / PSCell, it is determined that the RLF is detected. In the third case, when the timers T300, T301, T304, T311 and T319 are not running, the MCG MAC sends a random access problem indication; or when the SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that the RLF is detected. In the fourth case, when the MCG / SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that the RLF is detected. In the fifth case, if connected as an IAB node, after receiving the BH RLF indication on the BAP entity from the MCG / SCG, it is determined that the RLF is detected. In the sixth case, when the timer T304 is not running, the MCG MAC sends a consistent uplink LBT failure indication; or the SCG MAC sends a consistent uplink LBT failure indication, it is determined that the RLF is detected.

[0196] The RRC release related behavior includes but is not limited to at least one of the following: entering the non-connected state, including but not limited to entering the Idle or entering the inactive; stopping or starting the related timer, including but not limited to stopping the timer T310, stopping the timer T320, stopping the timer T316, stopping the timer T350, stopping the timer T331, starting the timer T320, starting or restarting the timer T325; storing the cell reselection priority information; determining the content of VarMeasIdleConfig; if the CHO is configured, removing the CHO related configuration stored by the terminal, etc.

[0197] In one possible implementation, the terminal can immediately stop or cancel the subsequent RRC release related behavior without waiting for the processing delay to expire. The processing delay is the processing delay agreed by the protocol, which is generally 60 milliseconds.

[0198] In another possible implementation, the terminal can immediately stop or cancel the subsequent RRC release related behavior without waiting for the terminal lower layer to indicate that the RRC release message has been successfully acknowledged.

[0199] In another possible implementation, the terminal can stop the specified timer at the earlier time of the processing delay of the RRC release message expiring and the terminal lower layer indicating that the RRC release message has been successfully acknowledged. The processing delay is the processing delay agreed by the protocol, which is generally 60 milliseconds.

[0200] In the above embodiments, when the terminal detects RLF, the RRC release message is received, and then the terminal can stop or cancel the RRC release process, reduce the influence of the RRC release process on the radio link failure (RLF) related process, improve the radio link reliability, and further improve the system performance.

[0201] In some optional embodiments, referring to Figure 15 Figure 15 FIG. 15 is a flow chart of a control processing method according to an embodiment, which can be used in a terminal. The method can include the following steps.

[0202] In step 1501, in response to detecting RLF within a delay period, the RRC release process is stopped or cancelled.

[0203] In the embodiments of the present disclosure, the delay period is a period from when the terminal receives the RRC release message to when the terminal delays a specified time length to perform the RRC release related behavior. The specified time length is a protocol agreed processing delay (generally 60 ms), or a shorter time length between a protocol agreed processing delay (generally 60 ms) and a time length from when the terminal receives the RRC release message to when the lower layer (lower than the RRC layer) indicates a successful confirmation of receiving the RRC release message.

[0204] In one possible implementation, the terminal starts when receiving the RRC release message, and when the protocol agreed processing delay (generally 60 ms) expires, within this period, once the terminal detects RLF, the terminal stops or cancels the RRC release process.

[0205] In another possible implementation, the terminal starts when receiving the RRC release message, and within a time length from when the terminal receives the RRC release message to when the lower layer (lower than the RRC layer) indicates a successful confirmation of receiving the RRC release message, once the terminal detects RLF, the terminal stops or cancels the RRC release process.

[0206] In another possible implementation, the terminal starts when receiving the RRC release message, and within a shorter time length between a protocol agreed processing delay (generally 60 ms) and a time length from when the terminal receives the RRC release message to when the lower layer (lower than the RRC layer) indicates a successful confirmation of receiving the RRC release message, once the terminal detects RLF, the terminal stops or cancels the RRC release process.

[0207] ​The terminal detecting the RLF includes, but is not limited to, any one of the following cases: in a first case, when the timer T310 expires in the PCell / PSCell, it is determined that the RLF is detected. In a second case, when the timer T312 expires in the PCell / PSCell, it is determined that the RLF is detected. In a third case, when the timers T300, T301, T304, T311 and T319 are not running, the MCG MAC sends a random access problem indication; or when the SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that the RLF is detected. In a fourth case, when the MCG / SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that the RLF is detected. In a fifth case, if connected as an IAB node, after receiving a BH RLF indication on the BAP entity from the MCG / SCG, it is determined that the RLF is detected. In a sixth case, when the timer T304 is not running, the MCG MAC sends a consistent uplink LBT failure indication; or the SCG MAC sends a consistent uplink LBT failure indication, it is determined that the RLF is detected.

[0208] In the above embodiment, if the terminal detects the RLF within the delay period, the RRC release process can be stopped or cancelled, the influence of the RRC release process on the radio link failure RLF related process is reduced, the radio link reliability is improved, and the system performance is further improved.

[0209] In some optional embodiments, referring to FIG. 1, a terminal 100 is shown, which can be used for implementing the embodiments of the present application. Figure 16 Figure 16 FIG. 1 is a flow chart of a control processing method according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0210] In step 1601, in response to not detecting the RLF before the delay period expires, the RRC release process is performed.

[0211] In the embodiments of the present disclosure, the delay period is a period from when the terminal receives the RRC release message to when the terminal delays for a specified duration to perform the RRC release related behavior. The specified duration is a protocol agreed processing delay (generally 60 milliseconds), or the shorter one of the protocol agreed processing delay (generally 60 milliseconds) and the duration from when the terminal receives the RRCRelease message to when the lower layer (lower than the RRC layer) indicates a successful acknowledgement of receiving the RRC release message.

[0212] In one possible implementation, from when the terminal receives the RRC release message to when the processing delay (generally 60 milliseconds) expires, if the terminal does not detect the RLF in this period, the terminal performs the RRC release process.

[0213] ​In another possible implementation, the terminal performs the RRC release procedure when the terminal does not detect the RLF in a period starting from when the terminal receives the RRC release message to when the lower layer of the terminal indicates that the RRC release message has been successfully received.

[0214] In another possible implementation, the terminal performs the RRC release procedure when the terminal does not detect the RLF in a period starting from when the terminal receives the RRC release message to the earlier of when the processing delay (generally 60 ms) expires and when the lower layer of the terminal indicates that the RRC release message has been successfully received.

[0215] The detection of the RLF by the terminal includes but is not limited to any one of the following cases: in a first case, the timer T310 expires in the PCell / PSCell, and it is determined that the RLF is detected. In a second case, the timer T312 expires in the PCell / PSCell, and it is determined that the RLF is detected. In a third case, the MCG MAC sends a random access problem indication when none of the timers T300, T301, T304, T311 and T319 is running; or the SCG RLC indicates that the maximum number of retransmissions has been reached, and it is determined that the RLF is detected. In a fourth case, the MCG / SCG RLC indicates that the maximum number of retransmissions has been reached, and it is determined that the RLF is detected. In a fifth case, if connected as an IAB node, it is determined that the RLF is detected after receiving a BH RLF indication on the BAP entity from the MCG / SCG. In a sixth case, the MCG MAC sends a consistent uplink LBT failure indication when the timer T304 is not running; or the SCG MAC sends a consistent uplink LBT failure indication, and it is determined that the RLF is detected. The performing of the RRC release related behavior includes but is not limited to at least one of the following: entering a non-connected state, including but not limited to entering Idle or entering inactive; stopping or starting a related timer, including but not limited to stopping the timer T310, stopping the timer T320, stopping the timer T316, stopping the timer T350, stopping the timer T331, starting the timer T320, starting or restarting the timer T325; storing cell reselection priority information; determining the content of VarMeasIdleConfig; if CHO is configured, removing the CHO related configuration stored by the terminal, and the like.

[0216] In the above embodiment, the terminal performs the RRC release procedure when the terminal does not detect the RLF in the delay period, which is simple to implement and has high availability.

[0217] In some optional embodiments, if the terminal receives the RRC release message when performing the RLF related procedure or performs the RLF related procedure in the delay period, the terminal can record the reception of the RRC release message in the radio link failure information. That is, the radio link failure information contains indication information, where the indication information is used to indicate whether the terminal receives the RRC release message when detecting the RLF.

[0218] In one possible implementation, the indication information can be stored in VarRLF-Report.

[0219] In another possible implementation, the indication information can be of an enumerated type or a Boolean type.

[0220] When the indication information is of the enumerated type, the optional value is "true", and when the indication information is "true", it is used to indicate that the terminal receives the RRC release message when detecting the RLF. When the indication information is empty, not configured, or "false", it is used to indicate that the terminal does not receive the RRC release message when detecting the RLF.

[0221] When the indication information is of the Boolean type, the optional value is "0" or "1", and when the indication information is "1", it is used to indicate that the terminal receives the RRC release message when detecting the RLF. When the indication information is "0", it is used to indicate that the terminal does not receive the RRC release message when detecting the RLF. Conversely, when the indication information is "0", it is used to indicate that the terminal receives the RRC release message when detecting the RLF. When the indication information is "1", it is used to indicate that the terminal does not receive the RRC release message when detecting the RLF.

[0222] In another possible implementation, the indication information can be stored in VarRLF-Report, and the indication information can be of an enumerated type or a Boolean type.

[0223] In another possible implementation, the indication information can be recorded in other failure information.

[0224] In another possible implementation, the indication information can be recorded in other failure information, and the indication information can be of an enumerated type or a Boolean type.

[0225] In another possible implementation, the indication information can be explicit indication information.

[0226] In another possible implementation, the indication information can be implicit indication information.

[0227] In another possible implementation, when the indication information is implicit indication information, the implicit indication information can be derived from other information stored or reported by the terminal.

[0228] The above are only exemplary descriptions. Implementations in which the indication information is recorded in other information stored or reported by the terminal, and the indication information adopts other types to indicate whether the terminal has received the RRC release message when detecting the RLF should also belong to the protection scope of the present disclosure.

[0229] In the above embodiments, the indication information indicating whether the terminal has received the RRC release message when detecting the RLF can be included in the radio link failure information, so as to facilitate the terminal to report the radio link failure information to the base station, and the base station can perform network resource optimization based on the indication information, and the availability is high.

[0230] In some optional embodiments, referring to Figure 17 , the method can include the following steps: Figure 17 is a control processing method flowchart according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0231] In step 1701, in response to any condition of starting RRC reestablishment not being met or the RRC release message being received, the RRC reestablishment process is not started.

[0232] In the embodiments of the present disclosure, the conditions of starting RRC reestablishment include, but are not limited to, at least one of the following:

[0233] Condition one, when MCG radio link failure is detected and t316 is not configured, it is determined that the condition of RRC reestablishment is met;

[0234] Condition two, when MCG radio link failure is detected and SCG transmission is suspended, it is determined that the condition of RRC reestablishment is met;

[0235] Condition three, when MCG radio link failure is detected in the PSCell change or PSCell addition process, it is determined that the condition of RRC reestablishment is met;

[0236] Condition four, when synchronization failure reconfiguration occurs in the MCG, it is determined that the condition of RRC reestablishment is met;

[0237] Condition five, when the movement is caused by NR failure, it is determined that the condition of RRC reestablishment is met;

[0238] Condition six, when the integrity check failure indication comes from the lower layer and is related to SRB1 or SRB2, unless the integrity check failure is detected in the RRC reestablishment message, it is determined that the condition of RRC reestablishment is met;

[0239] Condition seven, when RRC connection reconfiguration fails, it is determined that the condition for RRC reestablishment is met;

[0240] Condition eight, when MCG transmission is suspended and radio link failure of SCG is detected, it is determined that the condition for RRC reestablishment is met;

[0241] Condition nine, when MCG transmission is suspended and SCG synchronization failure reconfiguration is performed, it is determined that the condition for RRC reestablishment is met;

[0242] Condition ten, when MCG transmission is suspended, SCG change fails, it is determined that the condition for RRC reestablishment is met;

[0243] Condition eleven, SCG configuration failure occurs when MCG transmission is suspended, it is determined that the condition for RRC reestablishment is met;

[0244] Condition twelve, MCG is suspended and integrity check failure indication about SRB3 is received from SCG lower layer, it is determined that the condition for RRC reestablishment is met;

[0245] Condition thirteen, when T316 expires, it is determined that the condition for RRC reestablishment is met.

[0246] In the embodiments of the present disclosure, the terminal does not start the RRC reestablishment process in the case that any of the above conditions for starting the RRC reestablishment is not met.

[0247] Alternatively, the terminal does not start the RRC reestablishment process in the case that the RRC release message is received.

[0248] Alternatively, the terminal does not start the RRC reestablishment process in the case that any of the above conditions for starting the RRC reestablishment is not met or the RRC release message is received.

[0249] In one possible implementation, when the terminal detects MCG radio link failure and t316 is not configured, but the terminal receives the RRCRelease message, the RRC reestablishment process is not started

[0250] In another possible implementation, when the terminal detects MCG radio link failure, SCG transmission is suspended, but the UE receives the RRCRelease message, the reestablishment process is not started.

[0251] In the embodiments of the present disclosure, the RRC reestablishment process includes but is not limited to starting the RRC reestablishment and subsequent operations after the RRC reestablishment is started, and the subsequent operations include but are not limited to cell selection, sending an RRC reestablishment request message, etc.

[0252] In the above embodiments, the terminal can not start the RRC reestablishment procedure in the case that any condition for starting the RRC reestablishment is met or the RRC release message is received. The influence of the RRC release procedure on the RRC reestablishment procedure is reduced, the wireless link reliability is improved, and thus the system performance is improved.

[0253] In some optional embodiments, referring to FIG. 10, a flowchart of a control processing method is shown according to an embodiment, which can be used for a terminal. The method can include the following steps. Figure 18 Figure 18 In the above embodiments, the terminal can not start the RRC reestablishment procedure in the case that any condition for starting the RRC reestablishment is met or the RRC release message is received. The influence of the RRC release procedure on the RRC reestablishment procedure is reduced, the wireless link reliability is improved, and thus the system performance is improved.

[0254] In step 1801, the RRC reestablishment procedure is started in response to that any condition for starting the RRC reestablishment is met and the RRC release message is not received.

[0255] In the embodiments of the present disclosure, the terminal can start the RRC reestablishment procedure in the case that any condition for starting the RRC reestablishment is met and the RRC release message is not received.

[0256] The condition for starting the RRC reestablishment includes but is not limited to any condition provided in the above embodiments. Details are not described herein again. The RRC reestablishment procedure includes but is not limited to starting the RRC reestablishment and subsequent operations after the RRC reestablishment is started. The subsequent operations include but are not limited to cell selection, sending an RRC reestablishment request message, and the like.

[0257] In the above embodiments, the terminal can start the RRC reestablishment procedure in the case that any condition for starting the RRC reestablishment is met and the RRC release message is not received. The purpose of reducing the influence of the RRC release procedure on the RRC reestablishment procedure is achieved, the wireless link reliability is improved, and thus the system performance is improved.

[0258] In some optional embodiments, the present disclosure provides a new starting condition for the RRC reestablishment. The new starting condition can include that the RRC release message is not received.

[0259] In a possible implementation manner, the new starting condition can be met simultaneously with any one of the starting conditions for starting the RRC reestablishment provided in the above embodiments, that is, the terminal starts the RRC reestablishment procedure in the case that any starting condition for starting the RRC reestablishment is met and the RRC release message is not received.

[0260] In the above embodiments, the new starting condition is provided for the RRC reestablishment, the influence of the RRC release procedure on the RRC reestablishment procedure is reduced, and the usability is high.

[0261] In some optional embodiments, referring to FIG. 10, a flowchart of a control processing method is shown according to an embodiment, which can be used for a terminal. The method can include the following steps. Figure 19 Figure 19 ​​is a control processing method flow chart according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0262] In step 1901, in response to starting the RRC reestablishment procedure before the delay period expires, the RRC release procedure is stopped or cancelled.

[0263] The delay period is a period from when the terminal receives the RRC release message to when the terminal delays for a specified duration to perform the RRC release related behavior. The specified duration is a protocol agreed processing delay (generally 60 ms), or the shorter of the protocol specified processing delay (generally 60 ms) and the duration from when the terminal receives the RRC release message to when the lower layer (lower than the RRC layer) indicates successful confirmation of receiving the RRC release message.

[0264] In one possible implementation, from when the terminal receives the RRC release message to when the processing delay expires, if the terminal starts the RRC reestablishment procedure in this period, the terminal can stop or cancel the RRC release procedure.

[0265] In another possible implementation, from when the terminal receives the RRC release message to when the lower layer of the terminal indicates that the RRC release message has been successfully confirmed, if the terminal starts the RRC reestablishment procedure in this period, the terminal can stop or cancel the RRC release procedure.

[0266] In another possible implementation, from when the terminal receives the RRC release message to the earlier of when the processing delay expires and when the lower layer of the terminal indicates that the RRC release message has been successfully confirmed, if the terminal starts the RRC reestablishment procedure in this period, the terminal can stop or cancel the RRC release procedure.

[0267] In the above embodiments, the purpose of reducing the impact of the RRC release procedure on the RRC reestablishment procedure is achieved, the wireless link reliability is improved, and the system performance is further improved.

[0268] In some optional embodiments, referring to Figure 20 , and Figure 20 is a control processing method flow chart according to an embodiment, which can be used for a terminal. The method can include the following steps:

[0269] In step 2001, in response to any condition for starting the RRC reestablishment being met before the delay period expires, the RRC release procedure is stopped or cancelled.

[0270] The delay period is a time period from when the terminal receives the RRC release message to when the terminal delays for a specified time duration to perform an RRC release related behavior. The specified time duration is a protocol agreed processing delay (generally 60 ms) or a shorter time duration between a protocol specified processing delay (generally 60 ms) and a time duration from when the terminal receives the RRC release message to when a lower layer (lower than the RRC layer) indicates a successful confirmation of receiving the RRC release message.

[0271] In one possible implementation, from when the terminal receives the RRC release message to when the processing delay expires, if any condition for initiating the RRC reestablishment is met, the terminal can stop or cancel the RRC release procedure.

[0272] In another possible implementation, from when the terminal receives the RRC release message to when the terminal lower layer indicates a successful confirmation of receiving the RRC release message, if any condition for initiating the RRC reestablishment is met, the terminal can stop or cancel the RRC release procedure.

[0273] In another possible implementation, from when the terminal receives the RRC release message to an earlier time between when the processing delay expires and when the terminal lower layer indicates a successful confirmation of receiving the RRC release message, if any condition for initiating the RRC reestablishment is met, the terminal can stop or cancel the RRC release procedure.

[0274] In the above embodiments, the purpose of reducing the impact of the RRC release procedure on the RRC reestablishment procedure is achieved, the wireless link reliability is improved, and thus the system performance is improved.

[0275] In some optional embodiments, referring to Figure 21 Figure 21 is a control processing method flowchart according to an embodiment, which can be used for a terminal. The method can include the following steps.

[0276] In step 2101, in response to that the RRC reestablishment procedure is not initiated before the delay period expires, the RRC release procedure is continued to be performed.

[0277] The delay period is a time period from when the terminal receives the RRC release message to when the terminal delays for a specified time duration to perform an RRC release related behavior. The specified time duration is a protocol agreed processing delay (generally 60 ms) or a shorter time duration between a protocol specified processing delay (generally 60 ms) and a time duration from when the terminal receives the RRC release message to when a lower layer (lower than the RRC layer) indicates a successful confirmation of receiving the RRC release message.

[0278] ​In one possible implementation, from the time when the terminal receives the RRC release message to the time when the processing delay expires, if none of the conditions for initiating the RRC reestablishment is met, the terminal can continue to perform the RRC release procedure.

[0279] In another possible implementation, from the time when the terminal receives the RRC release message to the time when the lower layer of the terminal indicates that the RRC release message has been successfully acknowledged, if none of the conditions for initiating the RRC reestablishment is met, the terminal can continue to perform the RRC release procedure.

[0280] In another possible implementation, from the time when the terminal receives the RRC release message to the earlier time between the time when the processing delay expires and the time when the lower layer of the terminal indicates that the RRC release message has been successfully acknowledged, if none of the conditions for initiating the RRC reestablishment is met, the terminal can continue to perform the RRC release procedure.

[0281] In the above embodiments, the purpose of reducing the influence of the RRC release procedure on the RRC reestablishment procedure is achieved, the wireless link reliability is improved, and thus the system performance is improved.

[0282] In some optional embodiments, referring to Figure 22 , the method can comprise the following steps: Figure 22 is a flow chart of a control processing method according to an embodiment, which can be used for a terminal. The method can comprise the following steps:

[0283] In step 2201, in response to none of the conditions for initiating the RRC reestablishment being met before the delay period expires, the RRC release procedure is continued.

[0284] The delay period is a period from the time when the terminal receives the RRC release message to the time when the terminal delays for a specified duration to perform the RRC release related behavior. The specified duration is a protocol agreed processing delay (generally 60 ms), or the shorter duration between the protocol agreed processing delay (generally 60 ms) and the duration from the time when the terminal receives the RRC release message to the time when the lower layer (lower than the RRC layer) indicates that the RRC release message has been successfully acknowledged.

[0285] In one possible implementation, from the time when the terminal receives the RRC release message to the time when the processing delay expires, if none of the conditions for initiating the RRC reestablishment is met, the terminal can continue to perform the RRC release procedure.

[0286] In another possible implementation, from the time when the terminal receives the RRC release message to the time when the lower layer of the terminal indicates that the RRC release message has been successfully acknowledged, if none of the conditions for initiating the RRC reestablishment is met, the terminal can continue to perform the RRC release procedure.

[0287] In another possible implementation, from the time when the terminal receives the RRC release message to the time when the processing delay expires and the terminal lower layer indicates that the RRC release message has been successfully received, if none of the conditions for starting the RRC reestablishment is met during this period, the terminal can continue to perform the RRC release procedure.

[0288] In the above embodiments, the purpose of reducing the influence of the RRC release procedure on the RRC reestablishment procedure is achieved, the wireless link reliability is improved, and thus the system performance is improved.

[0289] The switching control method provided by the present disclosure is further illustrated as follows.

[0290] In the case of a target procedure being a radio link failure (RLF) related procedure, the switching control method comprises:

[0291] 1.1, in response to receiving a radio resource control (RRC) release message while performing the RLF related procedure or performing the RLF related procedure in a delay period, stopping or canceling the RLF related procedure; or

[0292] 1.2, in response to receiving a radio resource control (RRC) release message while performing the RLF related procedure or performing the RLF related procedure in a delay period, stopping or canceling the RRC release procedure. The RLF related procedure includes but is not limited to at least one of the following: RLF detection; physical layer problem detection; physical layer problem recovery; RLM (Radio Link Monitoring); start and stop of a specified timer; RLF cause determination; RLF report content determination, etc.

[0293] The RLF detection procedure includes but is not limited to the process after detecting the RLF, the specified timer is a timer corresponding to the RLF related procedure, including but not limited to timer T310 and timer T312, etc. The RLF report content determination includes but is not limited to determining the content of the failure information. In one possible implementation, the RLF report content determination includes determining the content of varRLF-report.

[0294] 2, for the above 1.1, when the terminal detects the RLF, it needs to determine whether an RRC release message has been received.

[0295] 2.1, when the terminal detects the RLF, if no RRC release message is received, the process after detecting the RLF is continued.

[0296] In one possible implementation, the process after detecting RLF includes, but is not limited to, at least one of the following: Report RLC failure; store RLF information in VarRLF-report; enter idle state; Report MCG RLF; initiate RRC re-establishment, etc.

[0297] 2.2, when the terminal detects RLF and receives an RRC release message, the terminal stops or cancels the RLF detection related process. The RLF detection process includes, but is not limited to, the process after detecting RLF. Receiving an RRC release message includes that the terminal has received an RRC release message.

[0298] 3, for the above 1.1, when the terminal starts a specified timer, it needs to determine whether an RRC release message has been received. The specified timer is a timer corresponding to the RLF related process, including but not limited to at least one of timers T310 and T312.

[0299] 3.1, when the terminal starts a specified timer, it does not receive an RRC release message, and then starts the specified timer.

[0300] 3.2, when the terminal starts a specified timer, it receives an RRC release message, and then does not start the specified timer.

[0301] In one possible implementation, when N310 consecutive out-of-sync indications of SpCell (including PCell and PSCell) are received from the lower layer of the terminal, and an RRC release message is not received, the specified timer T310 is started.

[0302] In another possible implementation, when N310 consecutive out-of-sync indications of SpCell (including PCell and PSCell) are received from the lower layer of the terminal, and an RRC release message is received, the specified timer T310 is not started.

[0303] In another possible implementation, if the trigger condition of the configured measurement event is met, reportConfig is set to "true", and timer T310 is running, the terminal does not receive an RRC release message, and then the specified timer T312 is started.

[0304] 4, for the above 1.1, when the terminal starts physical layer problem detection in RRC_CONNECTED (RRC connection state), it needs to determine whether an RRC release message has been received. The physical layer problem detection includes, but is not limited to, synchronization detection and / or asynchronous detection.

[0305] 4.1, When the terminal starts the physical layer problem detection, if the RRC release message is not received, the terminal continues the physical layer problem detection procedure.

[0306] 4.2, When the terminal starts the physical layer problem detection, if the RRC release message is received, the terminal stops or cancels the triggered physical layer problem detection procedure.

[0307] 5, For the above 1.1, when the terminal receives the RRC release message, if the specified timer is running, the terminal stops the specified timer. The specified timer is a timer corresponding to the RLF related procedure, including but not limited to at least one of timers T310 and T312.

[0308] In one possible implementation, when the terminal receives the RRC release message, if the specified timer is running, the terminal immediately stops the specified timer without waiting for the processing delay of the RRCRelease message to expire before stopping the specified timer. The processing delay is a protocol agreed processing delay, generally 60 milliseconds.

[0309] In another possible implementation, when the terminal receives the RRC release message, if the specified timer is running, the terminal immediately stops the specified timer without waiting for the terminal lower layer to indicate that the RRC release message has been successfully confirmed to be received before stopping the specified timer.

[0310] In another possible implementation, when the terminal receives the RRC release message, if the specified timer is running, the terminal immediately stops the specified timer without waiting for the earlier of the processing delay of the RRC release message to expire and the terminal lower layer to indicate that the RRC release message has been successfully confirmed to be received before stopping the specified timer. The processing delay is a protocol agreed processing delay, generally 60 milliseconds.

[0311] 6, For the above 1.1, when the terminal receives the RRC release message, the terminal stops or cancels the radio link monitoring (RLM) procedure. The RLM procedure includes monitoring and reporting procedures, monitoring refers to monitoring the radio link quality of the downlink of the current cell, and reporting refers to indicating the synchronous / asynchronous state to the higher layer.

[0312] In one possible implementation, when the terminal receives the RRC release message, the terminal immediately stops the RLM procedure, i.e. without waiting for the processing delay of the RRCRelease message to expire before stopping the RLM procedure. The processing delay is a protocol agreed processing delay, generally 60 milliseconds.

[0313] In another possible implementation, the terminal can immediately stop the RLM procedure without waiting for the lower layer to indicate that the RRC release message has been successfully confirmed to be received.

[0314] In another possible implementation, the terminal can immediately stop the RLM procedure without waiting for the processing delay to expire or the lower layer to indicate that the RRC release message has been successfully received.

[0315] 7. For the above 1.2, if the terminal receives an RRC message when it detects RLF, the terminal stops or cancels the RRC release procedure. The case in which the terminal detects RLF is similar to the case in which RLF is detected in the above embodiments, and thus is not described again here.

[0316] In one possible implementation, the terminal can immediately stop or cancel the subsequent RRC release related behavior without waiting for the processing delay to expire. The processing delay is a protocol agreed processing delay, which is generally 60 ms.

[0317] In another possible implementation, the terminal can immediately stop or cancel the subsequent RRC release related behavior without waiting for the terminal lower layer to indicate that the RRC release message has been successfully received.

[0318] In another possible implementation, the terminal can immediately stop the specified timer without waiting for the processing delay of the RRC release message to expire and the terminal lower layer to indicate that the RRC release message has been successfully received. The processing delay is a protocol agreed processing delay, which is generally 60 ms.

[0319] 8. For the above 1.2, the terminal needs to determine whether RLF is detected during the delay period.

[0320] 8.1. If the terminal does not detect RLF during the delay period, the terminal performs the RRC release procedure.

[0321] In one possible implementation, the terminal performs the RRC release procedure when the terminal receives the RRC release message, and the terminal does not detect RLF during a period from the time when the terminal receives the RRC release message to the time when the processing delay (generally 60 ms) expires.

[0322] In another possible implementation, the terminal performs the RRC release procedure when the terminal receives the RRC release message, and the terminal does not detect RLF during a period from the time when the terminal receives the RRC release message to the time when the terminal lower layer indicates that the RRC release message has been successfully received.

[0323] In another possible implementation, the terminal performs the RRC release procedure when the terminal receives the RRC release message, and the terminal does not detect RLF during a period from the time when the terminal receives the RRC release message to the earlier time of the time when the processing delay (generally 60 ms) expires and the time when the terminal lower layer indicates that the RRC release message has been successfully received.

[0324] 8.2, if the terminal detects RLF during the delay period, the terminal stops or cancels the RRC release procedure.

[0325] In one possible implementation, the terminal starts upon receiving the RRC release message, and upon detecting RLF, the terminal stops or cancels the RRC release procedure within the protocol specified processing delay (typically 60 ms).

[0326] In another possible implementation, the terminal starts upon receiving the RRC release message, and upon detecting RLF, the terminal stops or cancels the RRC release procedure within the time duration from the terminal receiving the RRCRelease message to the lower layer (lower than RRC layer) indicating successful acknowledgement of receiving the RRC release message.

[0327] In another possible implementation, the terminal starts upon receiving the RRC release message, and upon detecting RLF, the terminal stops or cancels the RRC release procedure within the shorter time duration between the protocol specified processing delay (typically 60 ms) expiration and the time duration from the terminal receiving the RRCRelease message to the lower layer (lower than RRC layer) indicating successful acknowledgement of receiving the RRC release message.

[0328] 9, the terminal can record in the failure information that the RRC release message is received.

[0329] 9.1, the failure information can contain indication information, wherein the indication information is used to indicate whether the terminal receives the RRC release message when detecting RLF.

[0330] In one possible implementation, the indication information can be stored in VarRLF-Report.

[0331] In another possible implementation, the indication information can be enumerated or Boolean.

[0332] When the indication information is enumerated, the optional value is "true", and when the indication information is "true", it is used to indicate that the terminal receives the RRC release message when detecting RLF. When the indication information is empty, not configured or "false", it is used to indicate that the terminal does not receive the RRC release message when detecting RLF.

[0333] When the indication information is of Boolean type, the optional values are "0" or "1", and when the indication information is "1", it indicates that the terminal has received an RRC release message when detecting RLF. When the indication information is "0", it indicates that the terminal has not received an RRC release message when detecting RLF. Conversely, when the indication information is "0", it indicates that the terminal has received an RRC release message when detecting RLF. When the indication information is "1", it indicates that the terminal has not received an RRC release message when detecting RLF.

[0334] In another possible implementation, the indication information can be stored in VarRLF-Report, and the indication information can be of enumeration type or Boolean type.

[0335] In another possible implementation, the indication information can be recorded in other failure information.

[0336] In another possible implementation, the indication information can be recorded in other failure information, and the indication information can be of enumeration type or Boolean type.

[0337] In another possible implementation, the indication information can be explicit indication information.

[0338] In another possible implementation, the indication information can be implicit indication information.

[0339] In another possible implementation, when the indication information is implicit indication information, the implicit indication information can be derived from the messages stored or reported by the terminal.

[0340] The above are only exemplary descriptions, and the implementation of recording the indication information in other information stored or reported by the terminal and using other types of indication information to indicate whether the terminal has received the RRC release message when detecting RLF should all belong to the protection scope of the present disclosure.

[0341] 10. The terminal detecting RLF mentioned above includes but is not limited to at least one of the following cases:

[0342] The first case is that when the timer T310 expires in the PCell / PSCell, it is determined that RLF is detected.

[0343] The second case is that when the timer T312 expires in the PCell / PSCell, it is determined that RLF is detected.

[0344] The third case, when the timers T300, T301, T304, T311 and T319 are not running, the MCG MAC sends a random access problem indication; or when the SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that RLF is detected.

[0345] The fourth case, when the MCG / SCG RLC indicates that the maximum number of retransmissions has been reached, it is determined that RLF is detected.

[0346] The fifth case, if connected as an IAB node, after receiving a BH RLF indication on the BAP entity from the MCG / SCG, it is determined that RLF is detected.

[0347] The sixth case, when the timer T304 is not running, the MCG MAC sends a consistent uplink LBT failure indication; or the SCG MAC sends a consistent uplink LBT failure indication, it is determined that RLF is detected.

[0348] In the above embodiments, the influence of the RRC release procedure on the radio link failure RLF related procedure is reduced, the wireless link reliability is improved, and the system performance is improved.

[0349] In the case of the target procedure being an RRC reestablishment procedure, the handover control method comprises:

[0350] 11.1, in response to receiving a radio resource control RRC release message when performing an RRC reestablishment procedure or performing an RRC reestablishment procedure in a delay period, not starting RRC reestablishment; or,

[0351] 11.2, in response to receiving a radio resource control RRC release message when performing an RRC reestablishment procedure or performing an RRC reestablishment procedure in a delay period, stopping or canceling the RRC release procedure.

[0352] 12, for 11.1, when the terminal needs to judge whether the RRC release message is received when evaluating the starting condition of starting RRC reestablishment.

[0353] 12.1, when any of the starting conditions is met and the terminal has not received the RRC release message, the RRC reestablishment procedure is performed.

[0354] 12.2, when any of the starting conditions is met and the terminal has received the RRC release message, the RRC reestablishment procedure is not performed.

[0355] 12.3, the starting conditions include but are not limited to at least one of the following:

[0356] Condition one, when MCG radio link failure is detected and t316 is not configured, it is determined that the condition of RRC reestablishment is met;

[0357] Condition two, the condition of RRC reestablishment is determined to be met when radio link failure of MCG is detected while SCG transmission is suspended;

[0358] Condition three, the condition of RRC reestablishment is determined to be met when MCG radio link failure is detected during PSCell change or PSCell addition procedure;

[0359] Condition four, the condition of RRC reestablishment is determined to be met when synchronous failure reconfiguration occurs in MCG;

[0360] Condition five, the condition of RRC reestablishment is determined to be met when NR failure causes mobility;

[0361] Condition six, the condition of RRC reestablishment is determined to be met when integrity check failure indication comes from lower layer and is related to SRB1 or SRB2, except when integrity check failure is detected in RRC reestablishment message;

[0362] Condition seven, the condition of RRC reestablishment is determined to be met when RRC connection reconfiguration fails;

[0363] Condition eight, the condition of RRC reestablishment is determined to be met when MCG transmission is suspended and radio link failure of SCG is detected;

[0364] Condition nine, the condition of RRC reestablishment is determined to be met when MCG transmission is suspended and SCG synchronous failure reconfiguration occurs;

[0365] Condition ten, the condition of RRC reestablishment is determined to be met when MCG transmission is suspended and PSCell change fails;

[0366] Condition eleven, the condition of RRC reestablishment is determined to be met when SCG configuration failure occurs while MCG transmission is suspended;

[0367] Condition twelve, the condition of RRC reestablishment is determined to be met when MCG is suspended and integrity check failure indication related to SRB3 comes from SCG lower layer;

[0368] Condition thirteen, the condition of RRC reestablishment is determined to be met when T316 expires.

[0369] 13. In 11.2, the terminal needs to determine whether the RRC reestablishment procedure is started during the delay period.

[0370] 13.1. If the RRC reestablishment procedure is not started during the delay period, the terminal continues to perform the RRC release procedure.

[0371] In one possible implementation, from the time when the terminal receives the RRC release message to the time when the processing delay expires, if the terminal does not start the RRC reestablishment procedure, the terminal can continue to perform the RRC release procedure.

[0372] In another possible implementation, from the time when the terminal receives the RRC release message to the time when the lower layer of the terminal indicates that the RRC release message has been successfully received, if the terminal does not start the RRC reestablishment procedure during this period, the terminal can continue to perform the RRC release procedure.

[0373] In another possible implementation, from the time when the terminal receives the RRC release message to the time when the lower layer of the terminal indicates that the RRC release message has been successfully received, if the terminal does not start the RRC reestablishment procedure during this period, the terminal can continue to perform the RRC release procedure.

[0374] 13.2, the terminal starts the RRC reestablishment procedure during the delay period, and the RRC release procedure is stopped or cancelled.

[0375] In one possible implementation, from the time when the terminal receives the RRC release message to the time when the delay period expires, if any condition for starting the RRC reestablishment is met during this period, the terminal can stop or cancel the RRC release procedure.

[0376] In another possible implementation, from the time when the terminal receives the RRC release message to the time when the lower layer of the terminal indicates that the RRC release message has been successfully received, if any condition for starting the RRC reestablishment is met during this period, the terminal can stop or cancel the RRC release procedure.

[0377] In another possible implementation, from the time when the terminal receives the RRC release message to the time when the lower layer of the terminal indicates that the RRC release message has been successfully received, if any condition for starting the RRC reestablishment is met during this period, the terminal can stop or cancel the RRC release procedure.

[0378] In the above embodiments, the purpose of reducing the influence of the RRC release procedure on the RRC reestablishment procedure is achieved, the wireless link reliability is improved, and the system performance is further improved.

[0379] Corresponding to the foregoing application function implementation method embodiments, the disclosure also provides application function implementation device embodiments.

[0380] Reference Figure 23 , Figure 23 is a control processing device block diagram according to an exemplary embodiment, the device is used for a terminal, comprising:

[0381] The control module 2301 is configured to stop or cancel the target procedure or the RRC release procedure in response to receiving a radio resource control (RRC) release message when the target procedure is performed or performing the target procedure during a delay period.

[0382] wherein the delay period is a time period from when the terminal receives the RRC release message to when the terminal delays performing an RRC release related behavior for a specified time duration, and the target procedure is a radio link failure, RLF, related procedure or an RRC reestablishment procedure.

[0383] In some optional embodiments, the control module comprises:

[0384] a first control submodule, configured to stop or cancel an RLF detection related procedure in response to detecting that the RRC release message is received when RLF is detected.

[0385] In some optional embodiments, the apparatus further comprises:

[0386] a first execution module, configured to continue performing a processing procedure after detecting RLF in response to detecting that the RRC release message is not received when RLF is detected.

[0387] In some optional embodiments, the control module comprises:

[0388] a second control submodule, configured to not start a specified timer in response to detecting that the RRC release message is received when the specified timer is started, wherein the specified timer is a timer corresponding to the RLF related procedure.

[0389] In some optional embodiments, the second control submodule is further configured to:

[0390] not start the specified timer in response to detecting that the RRC release message is received when a start condition corresponding to the specified timer is met.

[0391] In some optional embodiments, the apparatus further comprises:

[0392] a first start module, configured to start the specified timer in response to detecting that the RRC release message is not received when the specified timer is started, wherein the specified timer is a timer corresponding to the RLF related procedure.

[0393] In some optional embodiments, the first start module comprises:

[0394] a start submodule, configured to start the specified timer in response to detecting that the RRC release message is not received by the terminal when a start condition corresponding to the specified timer is met.

[0395] In some optional embodiments, the control module comprises:

[0396] The third control submodule is configured to stop or cancel the physical layer problem detection procedure in response to receiving the RRC release message while performing the physical layer problem detection in the RRC connected state.

[0397] In some optional embodiments, the apparatus further comprises:

[0398] The second execution module is configured to continue performing the physical layer problem detection procedure in response to not receiving the RRC release message while performing the physical layer problem detection.

[0399] In some optional embodiments, the control module comprises:

[0400] The fourth control submodule is configured to stop the specified timer in response to receiving the RRC release message while the specified timer is running; wherein the specified timer is a timer corresponding to the RLF related procedure.

[0401] In some optional embodiments, the control module comprises:

[0402] The fifth control submodule is configured to stop or cancel the RRC release procedure in response to receiving the RRC release message while detecting the RLF.

[0403] In some optional embodiments, the control module comprises:

[0404] The sixth control submodule is configured to stop or cancel the RRC release procedure in response to detecting the RLF within the delay period.

[0405] In some optional embodiments, the apparatus further comprises:

[0406] The third execution module is configured to perform the RRC release procedure in response to not detecting the RLF before the delay period expires.

[0407] In some optional embodiments, the target procedure is an RLF related procedure, and the indication information is contained in the radio link failure information; wherein the indication information is used to indicate whether the terminal receives the RRC release message while detecting the RLF.

[0408] In some optional embodiments, the indication information is of an enumeration type or a Boolean type.

[0409] In some optional embodiments, the control module comprises:

[0410] The seventh control submodule is configured to not start the RRC reestablishment procedure in response to not satisfying any condition for starting the RRC reestablishment or receiving the RRC release message.

[0411] In some optional embodiments, the apparatus further includes:

[0412] a second starting module, configured to start the RRC re-establishment procedure in response to any condition for starting RRC re-establishment being met and the RRC release message not being received.

[0413] In some optional embodiments, the control module includes:

[0414] an eighth control sub-module, configured to stop or cancel the RRC release procedure in response to the RRC re-establishment procedure being started before the delay period expires.

[0415] In some optional embodiments, the eighth control sub-module is further configured to:

[0416] stop or cancel the RRC release procedure in response to any condition for starting RRC re-establishment being met before the delay period expires.

[0417] In some optional embodiments, the apparatus further includes:

[0418] a fourth execution module, configured to continue to execute the RRC release procedure in response to the RRC re-establishment procedure not being started before the delay period expires.

[0419] In some optional embodiments, the fourth execution module is further configured to:

[0420] continue to execute the RRC release procedure in response to any condition for starting RRC re-establishment not being met before the delay period expires.

[0421] For the apparatus embodiments, since they are basically corresponding to the method embodiments, the relevant parts can be referred to the part of the description of the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the units described above as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., they can be located in one place, or also can be distributed on multiple network units. According to the actual needs, some or all of the modules can be selected to achieve the purpose of the present disclosure. Those skilled in the art can understand and implement without creative labor.

[0422] Correspondingly, the present disclosure also provides a computer readable storage medium, which stores a computer program for executing any of the above control processing methods.

[0423] Correspondingly, the present disclosure also provides a control processing apparatus, including:

[0424] a processor;

[0425] a memory for storing processor-executable instructions;

[0426] The processor is configured to perform any of the above-described control processing methods.

[0427] Figure 24 is a block diagram of a control processing apparatus 2400 according to an exemplary embodiment. The apparatus 2400 can be a terminal such as a mobile phone, a tablet computer, an e-book reader, a multimedia playback device, a wearable device, an in-vehicle user device, an iPad, a smart television, and the like.

[0428] Referring to Figure 24 The apparatus 2400 can include one or more of the following components: a processing component 2402, a memory 2404, a power supply component 2406, a multimedia component 2408, an audio component 2410, an input / output (I / O) interface 2412, a sensor component 2416, and a communication component 2418.

[0429] The processing component 2402 usually controls overall operations of the apparatus 2400, such as operations associated with displays, phone calls, data random accesses, camera operations, and recording operations. The processing component 2402 can include one or more processors 2420 to execute instructions to complete all or part of the steps of the above-described control processing methods. Further, the processing component 2402 can include one or more modules to facilitate interaction between the processing component 2402 and other components. For example, the processing component 2402 can include a multimedia module to facilitate the interaction between the multimedia component 2408 and the processing component 2402. For another example, the processing component 2402 can read executable instructions from the memory to implement the steps of a control processing method provided by any of the above-described embodiments.

[0430] The memory 2404 is configured to store various types of data to support operations of the apparatus 2400. Examples of these data include instructions for any application or method operating on the apparatus 2400, contact data, phonebook data, messages, pictures, videos, and the like. The memory 2404 can be implemented by any type of volatile or non-volatile storage devices 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 storage, flash memory, magnetic or optical disk.

[0431] The power supply component 2406 supplies electrical power for various components of the apparatus 2400. The power supply component 2406 can include a power supply management system, one or more power supplies, and other components associated with generating, managing, and distributing electrical power for the apparatus 2400.

[0432] The multimedia component 2408 includes a display for the device 2400 to provide an output interface for the user. In some embodiments, the multimedia component 2408 includes a front-facing camera and / or a rear-facing camera. When the device 2400 is in operation, the front-facing camera and / or the rear-facing camera can be used to receive external multimedia data. Each of the front-facing camera and the rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capability.

[0433] The audio component 2410 is configured to output and / or input audio signals. For example, the audio component 2410 includes a microphone (MIC) that is configured to receive an external audio signal when the device 2400 is in an operation 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 2404 or transmitted via the communication component 2418. In some embodiments, the audio component 2410 also includes a speaker for outputting audio signals.

[0434] The I / O interface 2412 provides an interface between the processing component 2402 and peripheral interface modules, which can be a keyboard, a click wheel, buttons, and so on. The buttons can include, but are not limited to, a home button, a volume button, a start button, and a lock button.

[0435] The sensor component 2416 includes one or more sensors for providing status assessments of various aspects of the device 2400. For example, the sensor component 2416 can detect an open / closed position of the device 2400, relative positioning of components, such as a display and a keypad of the device 2400, a change in position of the device 2400 or a component of the device 2400, the presence or absence of user contact with the device 2400, the orientation or acceleration / deceleration of the device 2400, and a temperature change of the device 2400. The sensor component 2416 can include a proximity sensor configured to detect the presence of a nearby object without any physical touch. The sensor component 2416 can further include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 2416 can also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0436] The communication component 2418 is configured to facilitate wired or wireless communication between the device 2400 and other devices. The device 2400 can access a wireless network based on a communication standard, such as Wi-Fi, 2G, 3G, 4G, 5G or 6G, or a combination thereof. In an exemplary embodiment, the communication component 2418 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 2418 further includes a Near Field Communication (NFC) module to facilitate close proximity 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.

[0437] In an exemplary embodiment, the device 2400 can 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, micro-controllers, microprocessors or other electronic elements, for performing any of the control processing methods described above.

[0438] In an exemplary embodiment, a non-transitory machine-readable storage medium including instructions, such as the memory 2404 including instructions, is also provided, which can be executed by the processor 2420 of the device 2400 to complete the information reporting method described above. 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 disc, and an optical data storage device, etc.

[0439] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the features disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure following, in general, the principles of the present disclosure and including such features to the extent that they are not disclosed in the prior art. The specification and examples are to be regarded as illustrative only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0440] It should be understood that the present disclosure is not limited to the precise structures described and shown in the drawings, and that various modifications and changes can be made to the embodiments without departing from the scope of the present disclosure. The scope of the present disclosure is limited only by the claims that follow.

Claims

1. A control processing method, characterized in that, The method is executed by a terminal and includes: In response to receiving a Radio Resource Control (RRC) release message during the execution of a target procedure or executing the target procedure during a delay period, the target procedure or the RRC release procedure is stopped or canceled; wherein, the delay period is the time period from when the terminal receives the RRC release message to when the terminal performs RRC release-related actions after a specified delay, and the target procedure is a Radio Link Failure (RLF) related procedure or an RRC reconstruction procedure; In response to executing the target process during the delay period, stopping or canceling the RRC release process includes any of the following: In response to the detection of RLF during the delay period, the RRC release process is stopped or canceled. In response to the initiation of the RRC reconstruction process before the expiration of the delay period, the RRC release process is stopped or canceled; Wherein, in response to receiving a Radio Resource Control (RRC) release message during the execution of the target process, stopping or canceling the target process includes any of the following: Upon receiving the RRC release message when an RLF is detected, the RLF detection process is stopped or canceled. If the RRC release message is received when the specified timer is started, the specified timer is not started; wherein, the specified timer is a timer corresponding to the RLF-related process; When the physical layer problem detection in the RRC connection state is received, the physical layer problem detection process is stopped or canceled. In response to receiving the RRC release message while the specified timer is running, the specified timer is stopped; wherein, the specified timer is the timer corresponding to the RLF-related procedure; Among them, in response to receiving a Radio Resource Control (RRC) release message during the execution of the target procedure, the RRC release procedure is stopped or canceled, including: Upon receiving the RRC release message when an RLF is detected, the RRC release process is stopped or canceled.

2. The method according to claim 1, characterized in that, The method further includes: If the RRC release message is not received when an RLF is detected, the processing procedure following the detection of the RLF continues.

3. The method according to claim 1, characterized in that, The response of not starting the specified timer when the RRC release message is received during the start of the specified timer includes: In response to receiving the RRC release message when the start condition corresponding to the specified timer is met, the specified timer is not started.

4. The method according to claim 1, characterized in that, The method further includes: In response to the failure to receive the RRC release message when the specified timer is started, the specified timer is started; wherein the specified timer is a timer corresponding to the RLF-related procedure.

5. The method according to claim 4, characterized in that, The step of starting the specified timer in response to not receiving the RRC release message when starting the specified timer includes: In response to the fact that the terminal has not received the RRC release message when the start condition corresponding to the specified timer is met, the specified timer is started.

6. The method according to claim 1, characterized in that, The method further includes: If the RRC release message is not received during the physical layer problem detection process, the physical layer problem detection process continues.

7. The method according to claim 1, characterized in that, The method further includes: If no RLF is detected before the expiration of the said delay period, the RRC release procedure is executed.

8. The method according to claim 1, characterized in that, The target process is an RLF-related process, and the wireless link failure information includes indication information; wherein, the indication information is used to indicate whether the terminal received the RRC release message when RLF was detected.

9. The method according to claim 8, characterized in that, The indication information is either an enumeration type or a Boolean type.

10. The method according to claim 1, characterized in that, In response to receiving a Radio Resource Control (RRC) release message during the execution of a target procedure, the target procedure is stopped or canceled, including: If any condition for initiating RRC reconstruction is not met or the RRC release message is received, the RRC reconstruction process is not initiated.

11. The method according to claim 1, characterized in that, The method further includes: The RRC reconstruction process is initiated in response to any condition for initiating RRC reconstruction being met and the RRC release message not being received.

12. The method according to claim 1, characterized in that, The response, which initiates the RRC reconstruction process before the expiration of the delay period, stops or cancels the RRC release process, including: In response to any condition for initiating RRC reconstruction being met before the expiration of the said delay period, the RRC release process is stopped or canceled.

13. The method according to claim 1, characterized in that, The method further includes: If the RRC reconstruction process is not initiated before the expiration of the delay period, the RRC release process continues.

14. The method according to claim 13, characterized in that, The response that the RRC reconstruction process is not initiated before the expiration of the delay period, and the RRC release process continues, includes: If any condition for initiating RRC reconstruction is not met before the expiration of the said delay period, the RRC release process continues.

15. A control processing device, characterized in that, The device is applied to a terminal and includes: The control module is configured to stop or cancel the target process or the RRC release process in response to receiving a Radio Resource Control (RRC) release message when executing the target process or during a delay period. The delay period is the time from when the terminal receives the RRC release message to when the terminal performs RRC release-related actions after a specified delay. The target process is a radio link failure (RLF) related process or an RRC reconstruction process. The control module is further configured as any one of the following: In response to the detection of RLF during the delay period, the RRC release process is stopped or canceled. In response to the initiation of the RRC reconstruction process before the expiration of the delay period, the RRC release process is stopped or canceled; The control module is further configured as any one of the following: Upon receiving the RRC release message when an RLF is detected, the RLF detection process is stopped or canceled. If the RRC release message is received when the specified timer is started, the specified timer is not started; wherein, the specified timer is a timer corresponding to the RLF-related process; When the physical layer problem detection in the RRC connection state is received, the physical layer problem detection process is stopped or canceled. Upon receiving the RRC release message when an RLF is detected, the RRC release process is stopped or canceled.

16. A computer-readable storage medium, characterized in that, The storage medium stores a computer program for executing the control processing method according to any one of claims 1-14.

17. A control processing device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to execute the control processing method according to any one of claims 1-14.

Images