Method and apparatus for use in communication node for wireless communication

Abstract

The present application discloses a method and apparatus for use in communication node for wireless communication. The method comprises: a terminal determining that a wireless connection has failed; in response to determining that the wireless connection has failed, sending a first message by means of a first connection and starting a first timer, wherein the first message is used for a fast MCG recovery procedure, and the first timer is configured; along with the first timer, determining whether to set a first information block in a first variable, wherein the first variable comprises wireless connection information, and the first information block indicates elapsed time of the first timer; if the terminal supports an RLF report for the fast MCG recovery procedure and the first connection is an SCG, setting the first information block in the first variable; and if the terminal does not support an RLF report for the fast MCG recovery procedure or the first connection is not an SCG, not setting the first information block in the first variable.

Description

Method and apparatus in a communication node used for wireless communication

[0001] The present application claims priority from the Chinese Patent Application No. 202410977421.3 filed on July 19, 2024, and entitled "Method and apparatus in a communication node used for wireless communication", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to a transmission method and apparatus in a wireless communication system, and in particular to a method and apparatus for wireless link failure report storage. BACKGROUND

[0003] With the continuous development of wireless communication, the requirements for mobility, transmission delay and transmission capacity are becoming higher and higher, so technologies such as dual connectivity and carrier aggregation are introduced in the 3GPP standard to expand the communication bandwidth and provide users with higher rates. For example, in the dual connectivity (DC) technology, a user equipment (UE) can access two networks at the same time; in the multi-path (MP) scenario, the UE is configured with a direct path and an indirect path, and the UE can establish a connection with the network through both the direct path and the indirect path.

[0004] Self-organizing networks (SON) include network self-configuration and self-optimization. In order to optimize mobility performance, achieve fast handover and reduce communication interruption, existing protocols support the UE to store information related to wireless connection failure in the wireless link failure report after determining that a wireless connection failure has occurred, and to report the related stored information according to network instructions.

[0005] The network can inform the MN of a wireless link failure by starting a fast MCG failure recovery procedure to achieve fast MCG recovery to reduce link interruption time; after Release 18, the UE supports fast MCG failure recovery in two scenarios of dual connectivity and MP, and supports storing and reporting information in the wireless link failure report for the fast MCG recovery process. SUMMARY

[0006] After starting the fast MCG failure recovery procedure, the UE stores the cell identity of the SCG connected in the fast MCG failure recovery and other related information in the radio link failure report according to the specific MCG recovery situation; the inventors have found through research that if the MCG link connection is recovered through another path in the MP scenario, the storage of the related information of the fast MCG failure recovery in the radio link failure report has little value for network optimization and there is a problem of storage resource occupation; therefore, optimizing the storage condition of the related information in the radio link failure report in the fast MCG failure recovery scenario is a problem to be solved in this research.

[0007] To solve the above problems, the present application provides a solution. In the description of the above problems, NR system is taken as an example, and the present application is also applicable to, for example, LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) system or future 6G system scenario, and similar technical effects of the NR system are obtained; further, although the present application gives specific embodiments for the mobility of the RRC_CONNECTED state involved in handover, the present application can also be used in, for example, RRC_IDLE state or RRC_INACTIVE state scenario, and similar technical effects of the mobility of the RRC connection state are obtained. Further, the unified design scheme for different scenarios also helps to reduce hardware complexity and cost. Further, although the original intention of the present application is to target the Uu air interface, the present application can also be used for the PC5 interface, and similar technical effects of the Uu air interface are obtained. Further, although the original intention of the present application is to target the terminal and base station scenario, the present application is also applicable to the V2X (Vehicle-to-Everything) scenario, the communication scenario between the terminal and the relay, and the communication scenario between the relay and the base station, and similar technical effects in the terminal and base station scenario are obtained. Further, although the original intention of the present application is to target the terminal and base station scenario, the present application is also applicable to the IAB (Integrated Access and Backhaul) communication scenario, and similar technical effects in the terminal and base station scenario are obtained. Further, although the original intention of the present application is to target the TN (Terrestrial Network) scenario, the present application is also applicable to the NTN (Non-Terrestrial Network) communication scenario, and similar technical effects in the TN scenario are obtained.

[0008] As an embodiment, the explanation of the terms in the present application refers to the definition of the specification protocol TS38 series of 3GPP.

[0009] As an embodiment, the explanation of the terms in this application refers to the definition of the specification protocol TS 37 series of 3GPP.

[0010] It should be noted that the embodiments and features of the embodiments in any node and device of the present application can be applied to any other node and device without conflict. The embodiments and features of the embodiments of the present application can be combined with each other arbitrarily without conflict.

[0011] The present application discloses a method used in a terminal, characterized in that, comprising:

[0012] Determining that a wireless connection fails;

[0013] In response to the determination that the wireless connection fails, sending a first message through a first connection and starting a first timer; wherein the first message is for a fast MCG recovery procedure; the first timer is configured;

[0014] Wherein, along with the first timer, whether to set a first information block in a first variable depends on whether the first connection is an SCG and whether the terminal supports RLF reporting for a fast MCG recovery procedure; the first variable includes connection failure information; the first information block indicates the elapsed time of the first timer; wherein the whether to set the first information block in the first variable depends on whether the first connection is an SCG and whether the terminal supports RLF reporting for a fast MCG recovery procedure includes:

[0015] If the terminal supports RLF reporting for a fast MCG recovery procedure and the first connection is the SCG, set the first information block in the first variable;

[0016] If the terminal does not support RLF reporting for a fast MCG recovery procedure or the first connection is not the SCG, do not set the first information block in the first variable.

[0017] As an embodiment, the problem to be solved by the present application includes: the behavior of the UE after determining that the wireless connection fails.

[0018] As an embodiment, the problem to be solved by the present application includes: when to send the first message.

[0019] As an embodiment, the problem to be solved by the present application includes: when to start the first timer.

[0020] As an embodiment, the characteristics of the above method include: in response to the determination that the wireless connection fails, sending a first message through a first connection and starting a first timer.

[0021] As an embodiment, benefits of the above method include: reducing the interaction of configuration signaling.

[0022] As an embodiment, benefits of the above method include: improving the autonomy of the UE.

[0023] As an embodiment, the problem to be solved by the present application includes: when to determine whether to set the first information block in the first variable.

[0024] As an embodiment, the characteristics of the above method include: accompanying the first timer, determining whether to set the first information block in the first variable.

[0025] As an embodiment, benefits of the above method include: facilitating the configuration optimization of the value of the first timer.

[0026] As an embodiment, the problem to be solved by the present application includes: the condition for setting the first information block in the first variable.

[0027] As an embodiment, the characteristics of the above method include: accompanying the first timer, whether to set the first information block in the first variable depends on whether the first connection is SCG and whether the terminal supports RLF reporting for the fast MCG recovery process.

[0028] As an embodiment, benefits of the above method include: reducing unnecessary UE resource occupation.

[0029] As an embodiment, benefits of the above method include: facilitating UE power saving.

[0030] As an embodiment, the problem to be solved by the present application includes: how to understand whether to set the first information block in the first variable depends on whether the first connection is SCG and whether the terminal supports RLF reporting for the fast MCG recovery process.

[0031] As an embodiment, the characteristics of the above method include: if the terminal supports RLF reporting for the fast MCG recovery process and the first connection is the SCG, setting the first information block in the first variable.

[0032] If the terminal does not support RLF reporting for the fast MCG recovery process or the first connection is not the SCG, do not set the first information block in the first variable.

[0033] As an embodiment, benefits of the above method include: the condition for determining whether to set the first information block in the first variable is clear.

[0034] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0035] According to one aspect of the present application, the method comprises:

[0036] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0037] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0038] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0039] According to one aspect of the present application, the method comprises:

[0040] The method comprises:

[0041] receiving a second message;

[0042] stopping the first timer in response to the second message being received;

[0043] wherein the first timer is running when the second message is received; and the accompanying the first timer comprises the stopping the first timer.

[0044] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0045] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0046] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0047] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0048] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0049] As one embodiment, the method has the benefit of specifying the condition for determining not to set the first information block in the first variable.

[0050] As one embodiment, the method has the feature that the accompanying the first timer includes the stopping the first timer.

[0051] As one embodiment, the method has the benefit that the stopping the first timer is covered.

[0052] According to one aspect of the present application, features include that the terminal whether supports the RLF report for the fast MCG recovery procedure depends on whether the first connection is the SCG.

[0053] The method includes:

[0054] If the terminal does not support the RLF report for the fast MCG recovery procedure or the first connection is not the SCG, clearing the information included in the first variable.

[0055] As one embodiment, the problem to be solved by the present application includes how to handle the first variable if the terminal does not support the RLF report for the fast MCG recovery procedure or the first connection is not the SCG.

[0056] As one embodiment, the problem to be solved by the present application includes the condition of clearing the first variable.

[0057] As one embodiment, the method has the feature that if the terminal does not support the RLF report for the fast MCG recovery procedure or the first connection is not the SCG, clearing the information included in the first variable.

[0058] As one embodiment, the method has the benefit that the storage resource of the UE is saved.

[0059] As one embodiment, the method has the benefit that the efficiency of information storage is improved.

[0060] As one embodiment, the method has the benefit that the effective information is stored.

[0061] According to one aspect of the present application, features include that the terminal whether supports the RLF report for the fast MCG recovery procedure depends on whether the first connection is the SCG.

[0062] The terminal whether supports the RLF report for the fast MCG recovery procedure depends on whether the first connection is the SCG; wherein the terminal whether supports the RLF report for the fast MCG recovery procedure depends on whether the first connection is the SCG includes:

[0063] If at least the first connection is the SCG, the terminal supports the RLF report for the fast MCG recovery procedure.

[0064] If the first connection is not the SCG, the terminal does not support the RLF report for the fast MCG recovery procedure.

[0065] As an embodiment, the problem to be solved by the present application includes: whether the first connection is the SCG, and whether the terminal supports the RLF report for the fast MCG recovery procedure.

[0066] As an embodiment, the problem to be solved by the present application includes: whether the first connection is the SCG, and whether the terminal supports the RLF report for the fast MCG recovery procedure.

[0067] As an embodiment, the method has the characteristics that: if at least the first connection is the SCG, the terminal supports the RLF report for the fast MCG recovery procedure.

[0068] If the first connection is not the SCG, the terminal does not support the RLF report for the fast MCG recovery procedure.

[0069] As an embodiment, the method has the advantages that: in the case of knowing that the first connection is not the SCG, it is facilitated to deduce that the terminal does not support the RLF report for the fast MCG recovery procedure.

[0070] According to an aspect of the present application, it is characterized in that,

[0071] The first information block is conditionally present in the first variable; wherein the first information block being conditionally present in the first variable means:

[0072] If the terminal supports the RLF report for the fast MCG recovery procedure and the first connection is the SCG, the first information block is present in the first variable;

[0073] If the terminal does not support the RLF report for the fast MCG recovery procedure or the first connection is not the SCG, the first information block is not present in the first variable.

[0074] As an embodiment, the problem to be solved by the present application includes: how to understand that the first information block is conditionally present in the first variable.

[0075] As an embodiment, the problem to be solved by the present application includes: the condition under which the first information block is present in the first variable.

[0076] As an embodiment, the method has the characteristics that: if the terminal supports the RLF report for the fast MCG recovery procedure and the first connection is the SCG, the first information block is present in the first variable;

[0077] The first information block is absent in the first variable if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG.

[0078] As an embodiment, the benefits of the above method include: the condition that the first information block is present in the first variable is specified.

[0079] According to an aspect of the present application, the first connection is not the SCG includes that the first connection is a non-direct path.

[0080] As an embodiment, the problems to be solved by the present application include the specific scenario that the first connection is not the SCG.

[0081] As an embodiment, the features of the above method include that the first connection is not the SCG includes that the first connection is a non-direct path.

[0082] As an embodiment, the benefits of the above method include: limiting the scenario to that the first connection is a non-direct path.

[0083] According to an aspect of the present application, the method comprises:

[0084] The method comprises:

[0085] The third message is sent.

[0086] The third message includes at least part of the information in the first variable.

[0087] As an embodiment, the problems to be solved by the present application include how to indicate at least part of the information in the first variable.

[0088] As an embodiment, the features of the above method include: the third message is sent; and the third message includes at least part of the information in the first variable.

[0089] As an embodiment, the benefits of the above method include: multiplexing the existing protocol.

[0090] The present application discloses a method used in a base station, characterized in that,

[0091] The method comprises:

[0092] The third message is received; the sender of the third message determines that the wireless connection fails; in response to the determination that the wireless connection fails, the sender of the third message sends a first message through a first connection and starts a first timer; the first message indicates that the wireless connection fails; the first timer is configured;

[0093] wherein whether the sender of the third message sets a first information block in a first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure; the first variable comprises connection failure information; the third message comprises at least part of the information in the first variable; the first information block indicates an elapsed time of the first timer; wherein the whether the sender of the third message sets the first information block in the first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure comprises:

[0094] if the sender of the third message supports RLF reporting for a fast MCG recovery procedure and the first connection is the SCG, the sender of the third message sets the first information block in the first variable;

[0095] if the sender of the third message does not support RLF reporting for a fast MCG recovery procedure or the first connection is not the SCG, the sender of the third message does not set the first information block in the first variable.

[0096] According to an aspect of the present application, the accompanying the first timer comprises that the first timer expires.

[0097] According to an aspect of the present application, the sender of the third message receives a second message; in response to the second message being received, the sender of the third message stops the first timer; wherein the first timer is running when the second message is received; the accompanying the first timer comprises that the first timer is stopped.

[0098] According to an aspect of the present application, if the sender of the third message does not support RLF reporting for a fast MCG recovery procedure or the first connection is the non-direct path, the sender of the third message clears the information comprised in the first variable.

[0099] According to an aspect of the present application, the first information block comprises a first timer value.

[0100] whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure depends on whether the first connection is the SCG; wherein the whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure depends on whether the first connection is the SCG comprises:

[0101] if at least the first connection is the SCG, the sender of the third message supports RLF reporting for a fast MCG recovery procedure;

[0102] if the first connection is not the SCG, the first information block is not present in the first variable if the sender of the third message does not support RLF reporting for the fast MCG recovery procedure.

[0103] According to one aspect of the present application, it is characterized in that,

[0104] the first information block is conditionally present in the first variable; wherein the first information block is conditionally present in the first variable means that:

[0105] if the first connection is the SCG, the first information block is present in the first variable if the sender of the third message supports RLF reporting for the fast MCG recovery procedure;

[0106] if the first connection is not the SCG, the first information block is not present in the first variable if the sender of the third message does not support RLF reporting for the fast MCG recovery procedure.

[0107] According to one aspect of the present application, it is characterized in that, the first connection is not the SCG comprises: the first connection is a non-direct path.

[0108] According to one aspect of the present application, it is characterized in that,

[0109] the method comprises:

[0110] receiving a third message;

[0111] wherein the third message comprises at least part of the information in the first information block.

[0112] The present application discloses a terminal used for wireless communication, characterized in that,

[0113] comprises:

[0114] a first processor, determining a wireless connection failure;

[0115] in response to the determination of the wireless connection failure, sending a first message through a first connection and starting a first timer; wherein the first message is for a fast MCG recovery procedure; the first timer is configured;

[0116] wherein whether the first information block is set in the first variable in dependence of whether the first connection is an SCG and whether the terminal supports RLF reporting for fast MCG recovery procedure in association with the first timer, the first variable comprises connection failure information, the first information block indicates an elapsed time of the first timer, and wherein the whether the first information block is set in the first variable in dependence of whether the first connection is an SCG and whether the terminal supports RLF reporting for fast MCG recovery procedure comprises:

[0117] if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG, the first information block is set in the first variable;

[0118] if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG, the first information block is not set in the first variable.

[0119] A base station for wireless communication is disclosed, comprising:

[0120] comprising:

[0121] a second processor configured to receive a third message, wherein a sender of the third message determines a radio connection failure, and in response to the determining the radio connection failure, the sender of the third message transmits a first message via a first connection and starts a first timer, wherein the first message indicates the radio connection failure, and the first timer is configured to expire after a first time period, and

[0122] wherein whether the sender of the third message sets a first information block in a first variable in dependence of whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for fast MCG recovery procedure in association with the first timer, the first variable comprises connection failure information, the third message comprises at least part of the information in the first variable, the first information block indicates an elapsed time of the first timer, and wherein the whether the sender of the third message sets the first information block in the first variable in dependence of whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for fast MCG recovery procedure comprises:

[0123] if the sender of the third message supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG, the first information block is set in the first variable;

[0124] If the sender of the third message does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG, the first information block is not set in the first variable.

[0125] As an embodiment, compared with the conventional scheme, the present application has the following advantages:

[0126] -. It is beneficial to clarify the scenario of network optimization;

[0127] -. It is beneficial to save storage resources;

[0128] -. It is beneficial to network optimization and big data collection;

[0129] -. It is beneficial to improve the efficiency of information storage;

[0130] -. It is beneficial to optimize the fast MCG recovery procedure. BRIEF DESCRIPTION OF DRAWINGS

[0131] Other features, objects, and advantages of the present application will become more apparent from the following detailed description of non-limiting embodiments thereof as read in conjunction with the accompanying drawings:

[0132] Fig. 1 shows a flow chart of communication of a terminal according to an embodiment of the present application;

[0133] Fig. 2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0134] Fig. 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user and control planes according to an embodiment of the present application;

[0135] Fig. 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0136] Figs. 5a-5c show a flow chart of wireless signal transmission according to an embodiment of the present application;

[0137] Fig. 6 shows a schematic diagram of the accompanying the first timer including expiration of the first timer according to an embodiment of the present application;

[0138] Fig. 7 shows a schematic diagram of the accompanying the first timer including stopping the first timer according to an embodiment of the present application;

[0139] Fig. 8 shows a flow chart of clearing information included in the first variable according to an embodiment of the present application;

[0140] Fig. 9 shows a flow chart of judging whether the terminal supports RLF reporting for fast MCG recovery procedure according to an embodiment of the present application;

[0141] FIG. 10 shows a flowchart for determining whether the first information block exists in the first variable according to an embodiment of the present application;

[0142] FIG. 11 shows a diagram in which the first connection is not the SCG including that the first connection is a non-direct path according to an embodiment of the present application;

[0143] FIG. 12 shows a diagram in which the third message includes at least part of information in the first variable according to an embodiment of the present application;

[0144] FIG. 13 shows a structural block diagram of a processing device for a terminal according to an embodiment of the present application;

[0145] FIG. 14 shows a structural block diagram of a processing device for a base station according to an embodiment of the present application. DETAILED DESCRIPTION

[0146] The technical solutions of the present application will be further described in detail below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily without conflict.

[0147] Embodiment 1

[0148] Embodiment 1 shows a flowchart of communication of a terminal according to an embodiment of the present application, as shown in FIG. 1. In FIG. 1, each block represents a step, and it is particularly emphasized that the order of the blocks in the figure does not represent the time sequence between the steps represented.

[0149] In embodiment 1, the terminal in the present application determines that the wireless connection fails in step 101; sends a first message through a first connection and starts a first timer in step 102; wherein the first message is for a fast MCG recovery procedure; the first timer is configured; determines whether a first information block is set in a first variable in step 103; wherein the first variable includes connection failure information; the first information block indicates the elapsed time of the first timer;

[0150] Wherein, whether the first information block is set in the first variable depends on whether the first connection is the SCG and whether the terminal supports RLF reporting for a fast MCG recovery procedure, including:

[0151] If the terminal supports RLF reporting for a fast MCG recovery procedure and the first connection is the SCG, the first information block is set in the first variable;

[0152] If the terminal does not support RLF reporting for a fast MCG recovery procedure or the first connection is not the SCG, the first information block is not set in the first variable.

[0153] As one embodiment, the determining the radio connection failure means that a T310 corresponding to a PCell expires; and the PCell is a cell currently served by the MCG.

[0154] As one embodiment, the determining the radio connection failure means that a T312 corresponding to a PCell expires; and the PCell is a cell currently served by the MCG.

[0155] As one embodiment, the determining the radio connection failure means that a random access problem indication is received from an MCG MAC layer.

[0156] As one embodiment, the determining the radio connection failure means that a maximum retransmission number indication is received from an MCG RLC layer.

[0157] As one embodiment, the determining the radio connection failure means that an MCG RLF is detected.

[0158] As one embodiment, the determining the radio connection failure means that an MCG RLF is detected and transmissions of the MCG and the SCG are not suspended.

[0159] As one embodiment, the determining the radio connection failure means that an MCG RLF is detected and transmissions of the MCG and a first connection are not suspended, the first connection being not the SCG.

[0160] As one embodiment, the radio connection failure comprises a radio link failure (RLF).

[0161] As one embodiment, the radio connection failure is a radio link failure.

[0162] As one embodiment, when the radio connection failure is determined, a first message is transmitted through a first connection and a first timer is started.

[0163] As one embodiment, when at least the radio connection failure is determined, a first message is transmitted through a first connection and a first timer is started.

[0164] As one embodiment, the first connection is the MCG.

[0165] As one embodiment, the first connection is not the MCG.

[0166] As one embodiment, the first connection is the SCG.

[0167] As one embodiment, the first connection is not the SCG.

[0168] As one embodiment, the first message comprises MCGFailureInformation.

[0169] As one embodiment, the first message is MCGFailureInformation.

[0170] As one embodiment, the first message for the fast MCG recovery procedure comprises that the fast MCG recovery procedure comprises setting the first message.

[0171] As one embodiment, the first message for the fast MCG recovery procedure comprises that the fast MCG recovery procedure comprises sending the first message.

[0172] As one embodiment, the first message for the fast MCG recovery procedure comprises that content of the first message is set to comprise MCG failure cause.

[0173] As one embodiment, the first message for the fast MCG recovery procedure comprises that content of the first message is set to assist the fast MCG recovery procedure.

[0174] As one embodiment, the first message for the fast MCG recovery procedure comprises that sending of the first message is for the fast MCG recovery procedure.

[0175] As one embodiment, the first message for the fast MCG recovery procedure comprises that sending of the first message is for informing the network of the MCG radio connection failure.

[0176] As one embodiment, the first message is MCGFailureInformation message; the first timer is T316.

[0177] As one embodiment, the first timer is a timer dedicated to the first message.

[0178] As one embodiment, the first timer is started in conjunction with the sending of the first message.

[0179] As one sub-embodiment of the above embodiment, the first timer being started in conjunction with the sending of the first message means that the first timer is started when the sending of the first message is started.

[0180] As one sub-embodiment of the above embodiment, the first timer being started in conjunction with the sending of the first message means that the first timer is started when the first message is passed to a lower layer.

[0181] As one sub-embodiment of the above-mentioned embodiment, the first timer is started in response to the sending of the first message is referring to: starting the first timer in response to setting the first message.

[0182] As one sub-embodiment of the above-mentioned embodiment, the first timer is started in response to the sending of the first message is referring to: starting the first timer in response to setting the first message complete.

[0183] As one embodiment, the first timer is configured dependent on the first connection being configured.

[0184] As one sub-embodiment of the above-mentioned embodiment, the first timer being configured dependent on the first connection is referring to: the value of the first timer is configured if the first connection is configured.

[0185] As one sub-embodiment of the above-mentioned embodiment, the first timer being configured dependent on the first connection is referring to: the value of the first timer is valid if the first connection is configured.

[0186] As one sub-embodiment of the above-mentioned embodiment, the first timer being configured dependent on the first connection is referring to: the value of the first timer is valid if the first connection is not suspended.

[0187] As one sub-embodiment of the above-mentioned embodiment, the first connection being configured comprises: the related bearer of the first connection is configured.

[0188] As one sub-embodiment of the above-mentioned embodiment, the related bearer of the first connection is SRB1.

[0189] As one sub-embodiment of the above-mentioned embodiment, the related bearer of the first connection is SRB3.

[0190] As one sub-embodiment of the above-mentioned embodiment, the related bearer of the first connection is at least one of SRB1 and SRB3.

[0191] As one embodiment, the accompanying first timer is referring to: when the first timer starts.

[0192] As one embodiment, the accompanying first timer is referring to: in response to the first timer starting running.

[0193] As one embodiment, the accompanying first timer is referring to: during the first timer running.

[0194] As one embodiment, the accompanying first timer is referring to: when the first timer stops.

[0195] As one embodiment, the accompanying first timer refers to in response to the first timer being stopped.

[0196] As one embodiment, the accompanying first timer refers to when the first timer expires.

[0197] As one embodiment, the accompanying first timer refers to in response to the first timer expiring.

[0198] As one embodiment, the sending the first message depends on the first timer being configured and the first connection not being suspended.

[0199] As one embodiment, the sending the first message is when the first timer is configured and the first connection is not suspended.

[0200] As one embodiment, the sending the first message is when at least the first timer is configured and the first connection is not suspended.

[0201] As one embodiment, the sending the first message is if the first timer is configured and the first connection is not suspended.

[0202] As one embodiment, the setting the first information block in the first variable depending on whether the first connection is an SCG and whether the terminal supports RLF reporting for fast MCG recovery procedure refers to setting the first information block in the first variable when the first connection is the SCG and the terminal supports RLF reporting for fast MCG recovery procedure.

[0203] As one embodiment, the setting the first information block in the first variable depending on whether the first connection is an SCG and whether the terminal supports RLF reporting for fast MCG recovery procedure refers to setting the first information block in the first variable at least when the first connection is the SCG and the terminal supports RLF reporting for fast MCG recovery procedure.

[0204] As one embodiment, the setting the first information block in the first variable depending on whether the first connection is an SCG and whether the terminal supports RLF reporting for fast MCG recovery procedure refers to setting the first information block in the first variable only when the first connection is the SCG and the terminal supports RLF reporting for fast MCG recovery procedure.

[0205] As one embodiment, the whether to set the first information block in the first variable depends on whether the first connection is the SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure means that the first information block is not set in the first variable when the first connection is the SCG but the terminal does not support RLF reporting for the fast MCG recovery procedure.

[0206] As one embodiment, the whether to set the first information block in the first variable depends on whether the first connection is the SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure means that the first information block is not set in the first variable when the first connection is not the SCG and the terminal does not support RLF reporting for the fast MCG recovery procedure.

[0207] As one embodiment, the whether to set the first information block in the first variable depends on whether the first connection is the SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure means that the first information block is not set in the first variable when the first connection is not the SCG, regardless of whether the terminal supports RLF reporting for the fast MCG recovery procedure.

[0208] As one embodiment, the first connection being the SCG includes that the first connection is the SCG and the SCG is activated.

[0209] As one embodiment, the first connection being the SCG includes that the first connection is the SCG and the SCG is not suspended.

[0210] As one embodiment, the first variable includes VarRLF-Report.

[0211] As one embodiment, the first variable is VarRLF-Report.

[0212] As one embodiment, the first information block is RLF-Report.

[0213] As one embodiment, the first information block including connection failure information means that the first information block includes information of the MCG radio link failure.

[0214] As one embodiment, the first information block including connection failure information means that the first information block includes information of the fast MCG recovery procedure failure.

[0215] As one embodiment, the first information block including connection failure information means that the first information block includes information of the MCG radio link failure and information of the fast MCG recovery procedure failure.

[0216] As one embodiment, the first information block comprising connection failure information means that the first information block comprises information of the MCG radio link failure and comprises information of success of the fast MCG recovery procedure.

[0217] As one embodiment, the first information block indicating the elapsed time of the first timer depending on the first timer not expiring means that the elapsed time of the first timer is indicated in the first information block when the first timer is stopped.

[0218] As one embodiment, the first information block indicating the elapsed time of the first timer depending on the first timer not expiring means that the elapsed time of the first timer is indicated in the first information block when the first timer is stopped.

[0219] As one embodiment, the first information block indicating the elapsed time of the first timer depending on the first timer not expiring means that the elapsed time of the first timer is indicated in the first information block as a response of the first timer being stopped.

[0220] As one embodiment, the first information block comprises an elapsedTimeT316 field which is set to a value of the elapsed time of the first timer.

[0221] As one embodiment, the first information block comprises an elapsedTimeT316 field when the first timer is stopped.

[0222] As one embodiment, the first information block comprises an mcgRecoveryFailureCause field which indicates a cause of failure of the fast MCG recovery procedure.

[0223] As one embodiment, the first information block comprising an mcgRecoveryFailureCause field depending on the first timer expiring means that the mcgRecoveryFailureCause field is set to indicate the first timer expiring when the first timer expires.

[0224] As one embodiment, the first information block comprising an mcgRecoveryFailureCause field depending on the first timer expiring means that the mcgRecoveryFailureCause field is set to indicate the first timer expiring when the first timer expires.

[0225] As one embodiment, the first information block includes an mcgRecoveryFailureCause field, and the first timer expiring depends on the mcgRecoveryFailureCause field being set to indicate the first timer expiring.

[0226] As one embodiment, the first information block includes a pSCellId, and the identification of the one PSCell is a global cell identity of the PSCell or a physical cell identity and a carrier frequency of the PSCell.

[0227] As one embodiment, the first information block includes a pSCellId, and the first connection being the SCG depends on the pSCellId.

[0228] As one embodiment, the first information block includes a pSCellId, and the first connection being the SCG depends on the pSCellId means that the one PSCell is a PSCell of the SCG.

[0229] As one embodiment, the first information block being set in the first variable depends on whether the first connection is the SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure includes the first information block being set in the first variable if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG.

[0230] As one embodiment, the first information block being set in the first variable if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG includes the first information block being set in the first variable as a response to the fast MCG recovery procedure being completed when the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG; the first information block indicating an elapsed time of the first timer.

[0231] As one embodiment, the first information block being set in the first variable if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG includes the first information block being set in the first variable as a response to the fast MCG recovery procedure being completed when the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG; the first information block indicating a PSCellId of the SCG.

[0232] As one embodiment, the fast MCG recovery procedure completion refers to the first timer stopping.

[0233] As one embodiment, the fast MCG recovery procedure completion refers to receiving a first RRC message.

[0234] As one embodiment, the first RRC message is RRCRelease.

[0235] As one embodiment, the first RRC message is RRCReconfiguration.

[0236] As one embodiment, the first RRC message includes configuration information of at least one PCell.

[0237] As one embodiment, the first RRC message is for initiating radio link reconnection.

[0238] As one embodiment, the first RRC message is for initiating radio link switching.

[0239] As one embodiment, whether to set the first information block in the first variable depends on whether the first connection is SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure, comprising: if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, not setting the first information block in the first variable.

[0240] As one embodiment, if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, not setting the first information block in the first variable comprises: if the terminal does not support RLF reporting for the fast MCG recovery procedure, not setting the first information block in the first variable regardless of whether the first connection is the SCG.

[0241] As one embodiment, if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, not setting the first information block in the first variable comprises: if the first connection is not the SCG, not setting the first information block in the first variable regardless of whether the terminal supports RLF reporting for the fast MCG recovery procedure.

[0242] As one embodiment, the not setting the first information block in the first variable includes clearing the first information block in the first variable.

[0243] As one embodiment, the not setting the first information block in the first variable includes clearing the first information block in the first variable.

[0244] As one embodiment, the not setting the first information block in the first variable includes clearing all information blocks in the first variable.

[0245] As one embodiment, the not setting the first information block in the first variable includes releasing the first information block in the first variable.

[0246] As one embodiment, the not setting the first information block in the first variable includes releasing all information blocks in the first variable.

[0247] As one embodiment, the not setting the first information block in the first variable includes not setting the first variable.

[0248] As one embodiment, when the first timer is stopped, if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG, a first information block is set in VarRLF-Report, the first information block indicating elapsed time of the first timer and an identity of a PSCell of the SCG.

[0249] As one embodiment, in response to the first timer expiring, if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG, a first information block is set in VarRLF-Report, the first information block indicating an identity of a PSCell of the SCG and that the fast MCG recovery failure cause is the first timer expiring.

[0250] As one embodiment, when the first timer is stopped, if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG, a first information block is not set in VarRLF-Report.

[0251] As one embodiment, in response to the expiration of the first timer, the first information block is not set in VarRLF-Report if the terminal does not support the RLF report for the fast MCG recovery procedure or the first connection is not the SCG.

[0252] Embodiment 2

[0253] Embodiment 2 illustrates a diagram of a network architecture according to one embodiment of the application, as shown in FIG. 2. FIG. 2 illustrates a network architecture 200 for a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system. The 5G NR / LTE / LTE-A network architecture 200 can be referred to as a 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 includes a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5GC (5G Core Network, 5G Core) / EPC (Evolved Packet Core) 210, a HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and at least one of an Internet service 230. The 5GS / EPS can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the 5GS / EPS provides packet-switched services, however, one of skill in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The RAN includes a node 203 and other nodes 204. The node 203 provides user and control plane protocol terminations toward the UE 201. The node 203 can be connected to the other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. The node 203 can also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (Transmit Receive Point), or some other suitable terminology. The node 203 provides an access point to the 5GC / EPC 210 for a UE 201. Examples of UEs 201 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communication, satellite mobile communication, global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a drone, a flying vehicle, a narrowband internet of things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similar functional device.A UE 201 can also be called a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other terminology. The node 203 is connected to a 5GC / EPC 210 over an S1 / NG interface. The 5GC / EPC 210 includes a MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, a S-GW (Service Gateway) / UPF (User Plane Function) 212, and a P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that processes the signaling between the UE 201 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocal) packets are transferred through the S-GW / UPF 212, which itself is connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation as well as other functions. The P-GW / UPF 213 is connected to Internet services 230. The Internet services 230 include operator corresponding Internet protocol services, which can include the Internet, an intranet, IMS (IP Multimedia Subsystem), and packet switched streaming services, among others.

[0254] As one embodiment, the UE 201 corresponds to the terminal in the present application.

[0255] As one embodiment, the UE 201 is a user equipment (UE).

[0256] As one embodiment, the terminal is a user equipment.

[0257] As one embodiment, the UE 201 is a relay device.

[0258] As one embodiment, the node 203 corresponds to the base station in the present application.

[0259] As one embodiment, the node 203 is a base station device.

[0260] As one embodiment, the node 203 is a relay device.

[0261] As one embodiment, the node 203 is a gateway device.

[0262] Typically, the UE 201 is a user equipment and the node 203 is a base station device.

[0263] As one embodiment, the user equipment supports non-terrestrial network (NTN) transmission.

[0264] As one embodiment, the user equipment supports terrestrial network (TN) transmission.

[0265] As one embodiment, the user equipment supports dual connection (DC) transmission.

[0266] As one embodiment, the user equipment comprises an aerial vehicle.

[0267] As one embodiment, the user equipment comprises a vehicle terminal.

[0268] As one embodiment, the user equipment comprises a ship.

[0269] As one embodiment, the user equipment comprises an Internet of Things terminal.

[0270] As one embodiment, the user equipment comprises an industrial Internet of Things terminal.

[0271] As one embodiment, the user equipment comprises a device supporting low latency and high reliability transmission.

[0272] As one embodiment, the user equipment comprises a test device.

[0273] As one embodiment, the user equipment comprises a signaling tester.

[0274] As one embodiment, the user equipment comprises an IAB (Integrated Access and Backhaul)-MT.

[0275] As one embodiment, the user equipment supports report generation using AI (Artificial Intelligence) or machine learning.

[0276] As one embodiment, the user equipment is a Massive-MIMO enabled terminal.

[0277] As one embodiment, the base station equipment supports transmission in a non-terrestrial network.

[0278] As one embodiment, the base station equipment supports transmission in a terrestrial network.

[0279] As one embodiment, the base station equipment comprises a Base Transceiver Station (BTS).

[0280] As one embodiment, the base station equipment comprises a NodeB (NB).

[0281] As one embodiment, the base station equipment comprises a gNB.

[0282] As one embodiment, the base station equipment comprises an eNB.

[0283] As one embodiment, the base station equipment comprises an ng-eNB.

[0284] As one embodiment, the base station equipment comprises an en-gNB.

[0285] As one embodiment, the base station equipment comprises a Centralized Unit (CU).

[0286] As one embodiment, the base station equipment comprises a Distributed Unit (DU).

[0287] As one embodiment, the base station equipment comprises a Transmitter Receiver Point (TRP).

[0288] As one embodiment, the base station equipment comprises a Marco Cellular base station.

[0289] As one embodiment, the base station equipment comprises a Micro Cell base station.

[0290] As one embodiment, the base station equipment comprises a Pico Cell base station.

[0291] As one embodiment, the base station equipment comprises a Femtocell.

[0292] As one embodiment, the base station equipment comprises a flying platform equipment.

[0293] As one embodiment, the base station device comprises a satellite device.

[0294] As one embodiment, the base station device comprises a test device.

[0295] As one embodiment, the base station device comprises a signaling tester.

[0296] As one embodiment, the base station device comprises a gateway device.

[0297] As one embodiment, the base station device comprises an IAB-node.

[0298] As one embodiment, the base station device comprises an IAB-donor.

[0299] As one embodiment, the base station device comprises an IAB-donor-CU.

[0300] As one embodiment, the base station device comprises an IAB-donor-DU.

[0301] As one embodiment, the base station device comprises an IAB-DU.

[0302] As one embodiment, the base station device comprises an IAB-MT.

[0303] As one embodiment, the base station device supports Massive-MIMO based transmission.

[0304] As one embodiment, the base station device supports decompression of CSI with AI model.

[0305] As one embodiment, the base station device supports mobility management with AI model.

[0306] Embodiment 3

[0307] Figure 3 is a diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300. Figure 3 shows three layers for the radio protocol architecture for the control plane 300: Layer 1, Layer 2, and Layer 3. Layer 1 (LI layer) is the lowest layer and implements various PHY (Physical layer) signal processing functions. The LI layer will be referred to as the PHY 301 herein. Layer 2 (L2 layer) 305 is above the PHY 301 and includes a MAC (Medium Access Control) sublayer 302, a RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security functions, such as ciphering of the data packets, and header compression. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and using RRC signaling to configure the lower layers. The radio protocol architecture for the user plane 350 includes Layer 1 (LI layer) and Layer 2 (L2 layer), which are substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in the L2 layer 355 in the user plane 350 is the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support diverse service

[0308] As one embodiment, the wireless protocol architecture in FIG. 3 is applicable to the terminal in the present application.

[0309] As one embodiment, the wireless protocol architecture in FIG. 3 is applicable to the base station in the present application.

[0310] As one embodiment, the first message in the present application is generated at the RRC 306.

[0311] As one embodiment, the first message in the present application is generated at the MAC 302 or the MAC 352.

[0312] As one embodiment, the first message in the present application is generated at the PHY 301 or the PHY 351.

[0313] As one embodiment, the second message in the present application is generated at the RRC 306.

[0314] As one embodiment, the second message in the present application is generated at the MAC 302 or the MAC 352.

[0315] As one embodiment, the second message in the present application is generated at the PHY 301 or the PHY 351.

[0316] As one embodiment, the third message in the present application is generated at the RRC 306.

[0317] As one embodiment, the third message in the present application is generated at the MAC 302 or the MAC 352.

[0318] As one embodiment, the third message in the present application is generated at the PHY 301 or the PHY 351.

[0319] Embodiment 4

[0320] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in FIG. 4. FIG. 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0321] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454, and an antenna 452.

[0322] The second communications device 410 includes a controller / processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter / receiver 418, and antennas 420.

[0323] In the transmission from the second communications device 410 to the first communications device 450, upper layer packets from a core network are provided to the controller / processor 475 at the second communications device 410. The controller / processor 475 implements functionality of the L2 layer. In the transmission from the second communications device 410 to the first communications device 450, the controller / processor 475 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation for the first communications device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets, and signaling to the first communications device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the LI layer (i.e., physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communications device 410, and mapping of coded and interleaved data onto various signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding of the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. The transmit processor 416 then maps to each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time and / or frequency domain, and then performs an inverse fast Fourier transform (IFFT) to generate a time-domain multicarrier symbol stream for the physical channel. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides the radio frequency stream to the different antennas 420.

[0324] In transmissions from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its respective antenna 452. Each receiver 454 recovers information modulated onto an RF carrier and provides the recovered information at baseband as a stream of symbols to a receive processor 456. The receive processor 456 and a multiple access receiver processor 458 implement various signal processing functions of the Ll layer. The multiple access receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multiple access symbol streams from the receivers 454. The receive processor 456 converts the baseband multiple access symbol streams from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals are demultiplexed from the received symbol streams by the receive processor 456, with the reference signals to be used for channel estimation and the data signals to be recovered after multiple access detection in the multiple access receiver processor 458 for any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered by the receive processor 456 and used to generate soft decisions. The receive processor 456 then decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to a controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 can be associated with a memory 460 that stores program codes and data. The memory 460 can be referred to as a computer-readable medium. In transmissions from the second communication device 410 to the second communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals can also be provided to the L3 for L3 processing.

[0325] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to a controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmit function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations, implements L2 layer functionality for the user plane and control plane. The controller / processor 459 is also responsible for error detection, retransmission of lost packets, and signaling to the second communication device 410. A transmit processor 468 performs modulation mapping, channel coding processing, and a multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, and then the transmit processor 468 modulates the resulting spatial streams into multi-carrier / single-carrier symbol streams, which are then provided to different antennas 452 via transmitters 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency signal, and then provides the radio frequency signal to the antenna 452.

[0326] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the receive functions at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its respective antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement the functionality of the L1 layer. A controller / processor 475 implements the functionality of the L2 layer. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer data packets from the UE 450. Upper layer data packets from the controller / processor 475 can be provided to a core network.

[0327] As one embodiment, the first communication device 450 comprises: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the first communication device 450 at least to determine a radio connection failure; in response to the determining the radio connection failure, send a first message over a first connection and start a first timer; wherein the first message is for a fast MCG recovery procedure; the first timer is configured; wherein, in conjunction with the first timer, whether to set a first information block in a first variable depends on whether the first connection is an SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure; the first variable comprises connection failure information; the first information block indicates an elapsed time of the first timer; wherein the whether to set the first information block in the first variable depends on whether the first connection is an SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure comprises: if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG, set the first information block in the first variable; if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, do not set the first information block in the first variable.

[0328] As one embodiment, the first communication device 450 comprises: a memory storing a program of computer readable instructions to produce actions when executed by at least one processor, the actions comprising: determining a radio connection failure; in response to the determining the radio connection failure, sending a first message over a first connection and starting a first timer; wherein the first message is for a fast MCG recovery procedure; the first timer is configured; wherein, in conjunction with the first timer, whether to set a first information block in a first variable depends on whether the first connection is an SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure; the first variable comprises connection failure information; the first information block indicates an elapsed time of the first timer; wherein the whether to set the first information block in the first variable depends on whether the first connection is an SCG and whether the terminal supports RLF reporting for the fast MCG recovery procedure comprises: if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG, set the first information block in the first variable; if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, do not set the first information block in the first variable.

[0329] As an embodiment, the second communication device 410 comprises at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the second communication device 410 at least to receive a third message; wherein a sender of the third message determines a radio link failure; in response to the determining the radio link failure, the sender of the third message sends a first message over a first connection and starts a first timer; wherein the first message indicates the radio link failure; the first timer is configured; wherein, in conjunction with the first timer, whether the sender of the third message sets a first information block in a first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure; the first variable comprises connection failure information; the third message comprises at least part of the information in the first variable; the first information block indicates an elapsed time of the first timer; wherein the whether the sender of the third message sets the first information block in the first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure comprises: if the sender of the third message supports RLF reporting for a fast MCG recovery procedure and the first connection is the SCG, setting the first information block in the first variable; if the sender of the third message does not support RLF reporting for a fast MCG recovery procedure or the first connection is not the SCG, not setting the first information block in the first variable.

[0330] As one embodiment, the second communication device 410 comprises: a memory storing a computer readable program of instructions which, when executed by at least one processor, results in actions comprising: receiving a third message; wherein a sender of the third message determines a radio link failure; in response to the determining the radio link failure, the sender of the third message sends a first message over a first connection and starts a first timer; wherein the first message indicates the radio link failure; the first timer is configured; wherein, in conjunction with the first timer, whether the sender of the third message sets a first information block in a first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure; the first variable comprises connection failure information; the third message comprises at least part of the information in the first variable; the first information block indicates an elapsed time of the first timer; wherein the whether the sender of the third message sets the first information block in the first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure comprises: if the sender of the third message supports RLF reporting for a fast MCG recovery procedure and the first connection is the SCG, setting the first information block in the first variable; if the sender of the third message does not support RLF reporting for a fast MCG recovery procedure or the first connection is not the SCG, not setting the first information block in the first variable.

[0331] As one embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, the controller / processor 459 is configured to send the first message.

[0332] As one embodiment, at least one of the antenna 420, the receiver 418, the receive processor 470, the controller / processor 475 is configured to receive the first message.

[0333] As one embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 471, the controller / processor 475 is configured to send the second message.

[0334] As one embodiment, at least one of the antenna 452, the receiver 454, the receive processor 456, the controller / processor 459 is configured to receive the second message.

[0335] As one embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, the controller / processor 459 is configured to send the third message.

[0336] As an embodiment, the antenna 420, the receiver 418, at least one of the receiving processor 470, and the controller / processor 475 are configured to receive the third message.

[0337] As an embodiment, the first communication device 450 corresponds to a terminal in the present application.

[0338] As an embodiment, the second communication device 410 corresponds to a base station in the present application.

[0339] As an embodiment, the first communication device 450 is a user equipment.

[0340] As an embodiment, the first communication device 450 is a relay device.

[0341] As an embodiment, the second communication device 410 is a base station device.

[0342] As an embodiment, the second communication device 410 is a relay device.

[0343] Embodiment 5

[0344] Embodiment 5 illustrates a wireless signal transmission flowchart according to an embodiment of the present application, as shown in FIG. 5a-FIG. 5c. It is particularly pointed out that the sequence in this example does not limit the sequence of signal transmission and implementation in the present application.

[0345] In FIG. 5a, a flowchart is illustrated in which after the first message is sent, the first information block is not set in the first variable.

[0346] For the terminal U01, in step S5101a, a radio link failure is determined; in step S5102a, in response to the determination of the radio connection failure, a first message is sent through a first connection and a first timer is started; wherein the first message is for a fast MCG recovery procedure; the first timer is configured; in step S5103a, the second message is received; in step S5104a, in response to receiving the second message, the first timer is stopped.

[0347] For the base station N02, in step S5201a, the first message is received; in step S5202a, the second message is sent.

[0348] As an embodiment, the terminal U01 is a UE.

[0349] As an embodiment, the terminal U01 is a 3GPP R19 supported UE.

[0350] As one embodiment, the terminal U01 is a 6G-capable UE.

[0351] As one embodiment, the terminal U01 is an AI model-capable UE.

[0352] As one embodiment, the terminal U01 is an ML inference-capable UE.

[0353] As one embodiment, the terminal U01 is not a UE.

[0354] As one embodiment, the terminal U01 and the base station N02 are connected via a wireless connection.

[0355] As one embodiment, the terminal U01 and the base station N02 are connected via a wired connection.

[0356] As one embodiment, the terminal U01 and the base station N02 are connected via a Uu interface.

[0357] As one embodiment, the terminal U01 and the base station N02 are connected via an IAB interface.

[0358] As one embodiment, the base station N02 is a maintaining base station of a current serving cell of the terminal U01.

[0359] As one embodiment, the base station N02 is a maintaining base station of a cell served by the terminal U01.

[0360] As one embodiment, the base station N02 is a maintaining base station of a cell served by the terminal U01 before completion of a fast MCG recovery procedure.

[0361] As one embodiment, the base station N02 is a maintaining base station of a cell served by the terminal U01 after completion of a fast MCG recovery procedure.

[0362] As one embodiment, the base station N02 is a maintaining base station of a PCell of the MCG.

[0363] As one embodiment, the terminal U01 determines a radio link failure.

[0364] As one embodiment, in response to the determination of the radio link failure, the terminal U01 sends a first message via a first connection and starts a first timer.

[0365] As one embodiment, the first connection is not the SCG.

[0366] As one embodiment, the first connection is not suspended at the time of sending the first message.

[0367] As one embodiment, the first connection is not indicated to change when the first connection sends the first message.

[0368] As one embodiment, the first connection is not indicated to add when the first connection sends the first message.

[0369] As one embodiment, the first connection is not indicated when the first connection sends the first message means that the terminal has not received an RRC message indicating before determining the radio connection failure.

[0370] As one embodiment, the first connection is not indicated when the first connection sends the first message means that information stored in the terminal related to the first connection is not activated before determining the radio connection failure.

[0371] As one embodiment, the first timer is started after the first message is set up.

[0372] As one embodiment, the first timer is started before the first message is sent.

[0373] As one embodiment, whether the first message is sent depends on whether the first timer is configured.

[0374] As one embodiment, whether the first message is sent depends on whether the first timer is configured comprises: if the first timer is not configured, the first message is not sent.

[0375] As one embodiment, whether the first message is sent depends on whether the first timer is configured comprises: when at least the first timer is configured, the first message is sent.

[0376] As one embodiment, whether the first message is sent depends on whether the first timer is configured comprises: only if the first timer is configured, the first message is sent.

[0377] As one embodiment, the virtual box F5.1a is optional.

[0378] As one embodiment, the virtual box F5.1a exists.

[0379] As one embodiment, the terminal U01 receives the second message.

[0380] As one embodiment, the receiving the second message depends on the first message being sent.

[0381] As one embodiment, the first message being sent triggers the second message.

[0382] As one embodiment, the second message is received in response to the first message being sent.

[0383] As one embodiment, the second message and the first message are both transmitted over the first connection.

[0384] As one embodiment, the sender of the second message and the recipient of the first message are the same.

[0385] As one embodiment, the first message is forwarded to the sender of the second message.

[0386] As one embodiment, the first message is forwarded to the sender of the second message over an Xn interface.

[0387] As one embodiment, the first message is forwarded to the sender of the second message over an X2 interface.

[0388] As one embodiment, the sender of the second message and the recipient of the first message are different.

[0389] As one embodiment, the terminal U01 stops the first timer.

[0390] As one embodiment, the first timer is stopped in response to receiving the second message.

[0391] As one embodiment, the second message indicates to stop the first timer.

[0392] As one embodiment, the first timer is stopped in response to the second message being applied.

[0393] As one embodiment, the reception of the second message triggers the stopping of the first timer.

[0394] As one embodiment, the terminal U01 considers the fast MCG recovery procedure to be completed in response to the first timer being stopped.

[0395] As one embodiment, the terminal U01 considers the fast MCG recovery procedure to be completed in response to the second message being received.

[0396] As one embodiment, the terminal U01 considers the fast MCG recovery procedure to be completed in response to the second message being successfully applied.

[0397] As one embodiment, the dashed box F5.1a is not present.

[0398] As one embodiment, the first timer expires.

[0399] As an embodiment, in response to the expiration of the first timer, the terminal U01 considers that the fast MCG recovery procedure fails.

[0400] As an embodiment, in response to the expiration of the first timer, the terminal U01 considers that the fast MCG recovery procedure fails.

[0401] In the figure 5b, a flow chart is illustrated, which sets the first information block in the first variable after sending the first message.

[0402] For the terminal U01, in the step S5101b, the radio link failure is determined; in the step S5102b, in response to the determination of the radio link failure, the first message is sent through the first connection and the first timer is started; wherein, the first message is for the fast MCG recovery procedure; the first timer is configured; in the step S5103b, the second message is received; in the step S5104b, in response to the reception of the second message, the first timer is stopped; in the step S5105b, it is judged whether the first information block is set in the first variable; in the step S5106b, the third message is sent, which indicates at least part of the information in the first variable.

[0403] For the base station N02, in the step S5201b, the third message is received.

[0404] For the base station N03, in the step S5301b, the first message is received; in the step S5302b, the second message is sent.

[0405] As an embodiment, the terminal U01 and the base station N03 are connected through the wireless connection.

[0406] As an embodiment, the terminal U01 and the base station N03 are connected through the wired connection.

[0407] As an embodiment, the terminal U01 and the base station N03 are connected through the Uu interface.

[0408] As an embodiment, the base station N02 is the maintenance base station of the serving cell of the terminal U01 after the completion of the fast MCG recovery procedure.

[0409] As an embodiment, the base station N03 is the maintenance base station of the current serving cell of the terminal U01.

[0410] As an embodiment, the base station N03 is the maintenance base station of the cell served by the terminal U01.

[0411] As one embodiment, the base station N03 and the base station N02 are connected over a wireless interface.

[0412] As one embodiment, the base station N03 and the base station N02 are connected over a wired interface.

[0413] As one embodiment, the base station N03 and the base station N02 are connected over an Xn interface.

[0414] As one embodiment, the base station N03 and the base station N02 are connected over an X2 interface.

[0415] As one embodiment, the base station N03 and the base station N02 are ideal backhaul.

[0416] As one embodiment, the base station N03 and the base station N02 are non-ideal backhaul.

[0417] As one embodiment, the base station N03 is not the base station N02.

[0418] As one embodiment, the base station N03 is an SN of the base station N02.

[0419] As one embodiment, the base station N02 is a PCell of the MCG.

[0420] As one embodiment, the base station N03 is a PSCell of the SCG.

[0421] As one embodiment, the third message is forwarded to the base station N02 by the base station N03.

[0422] As one embodiment, the terminal U01 determines a radio link failure.

[0423] As one embodiment, in response to the determining the radio connection failure, the terminal U01 sends the first message over the first connection and starts a first timer.

[0424] As one embodiment, the first connection is the SCG.

[0425] As one embodiment, the dashed box F5.1b is optional.

[0426] As one embodiment, the dashed box F5.1b is present.

[0427] As one embodiment, the terminal U01 receives the second message.

[0428] As one embodiment, the terminal U01 stops the first timer.

[0429] As one embodiment, the terminal U01 judges whether a first information block is set in the first variable.

[0430] As one embodiment, after stopping the first timer, the terminal U01 judges whether a first information block is set in the first variable.

[0431] As one embodiment, the dashed box F5.1b is absent.

[0432] As one embodiment, after the first timer expires, the terminal U01 judges whether a first information block is set in the first variable.

[0433] As one embodiment, the flowchart of the terminal U01 judging whether a first information block is set in the first variable is shown in Fig. 5c.

[0434] As one embodiment, the dashed box F5.2b is optional.

[0435] As one embodiment, the dashed box F5.2b is present.

[0436] As one embodiment, the terminal U01 sends a third message.

[0437] As one embodiment, the terminal U01 sending a third message is triggered by the behavior of the terminal.

[0438] As one embodiment, the sending of the third message depends on a first information block being set in the first variable.

[0439] As one embodiment, the third message is sent in response to a first information block being set in the first variable.

[0440] As one embodiment, the third message is sent when the setting of a first information block in the first variable is completed.

[0441] As one embodiment, the terminal U01 sending a third message depends on a network indication.

[0442] As one embodiment, the terminal U01 receives a network indication before sending the third message.

[0443] As one embodiment, the dashed box F5.2b is absent.

[0444] The flowchart of judging whether a first information block is set in the first variable is exemplified in Fig. 5c.

[0445] In step S5101c, it is determined whether the terminal supports RLF reporting for fast MCG recovery procedure; in step S5102c, it is determined whether the first connection is SCG; in step S5103c, if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is SCG, a first information block is set in a first variable.

[0446] As one embodiment, if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG, the first information block is set in the first variable.

[0447] As one embodiment, if the terminal supports RLF reporting for fast MCG recovery procedure but the first connection is not the SCG, the first information block is not set in the first variable.

[0448] As one embodiment, if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG, the first information block is not set in the first variable.

[0449] As one embodiment, if the terminal does not support RLF reporting for fast MCG recovery procedure, the first information block is not set in the first variable.

[0450] As one embodiment, the first connection is not the SCG, the first information block is not set in the first variable.

[0451] Embodiment 6

[0452] Embodiment 6 illustrates the schematic diagram of the accompanying the first timer including expiration of the first timer according to one embodiment of the present application, as shown in FIG. 6.

[0453] In embodiment 6, the accompanying the first timer includes: the first timer expires.

[0454] As one embodiment, the accompanying the first timer means: in response to expiration of the first timer.

[0455] As one embodiment, the accompanying the first timer means: when the first timer expires.

[0456] As one embodiment, the accompanying the first timer means: after the first timer expires.

[0457] As one embodiment, the accompanying the first timer means: determining expiration of the first timer.

[0458] As one embodiment, the accompanying the first timer means immediately following expiration of the first timer.

[0459] As one embodiment, the expiration of the first timer means that no network indication is received during the running of the first timer.

[0460] As one embodiment, the expiration of the first timer means that none of the following is received during the running of the first timer: RRCRelease message or RRCReconfiguration message with reconfigurationwithSync or MobilityFromNRCommand message.

[0461] As one embodiment, the expiration of the first timer means that RRC re-establishment procedure is not started during the running of the first timer.

[0462] As one embodiment, the value of the first timer depends on configuration information of the MCG.

[0463] As one embodiment, the value of the first timer is configured in response to the configuration information of the MCG being applied.

[0464] As one embodiment, the value of the first timer is configured when the configuration information of the MCG is applied.

[0465] As one embodiment, the value of the first timer is configured after the configuration information of the MCG is applied.

[0466] As one embodiment, starting the first timer depends on the fast MCG recovery procedure.

[0467] As one embodiment, the first timer is started in response to the fast MCG recovery procedure being initiated.

[0468] As one embodiment, the first timer is started when the fast MCG recovery procedure is initiated.

[0469] As one embodiment, the fast MCG recovery procedure fails in response to the expiration of the first timer.

[0470] As one embodiment, the first procedure is initiated in response to the expiration of the first timer.

[0471] As one embodiment, the fast MCG recovery procedure failing triggers setting a first information block in the first variable.

[0472] As one embodiment, the fast MCG recovery procedure failing triggers the first procedure.

[0473] As one embodiment, the first procedure is a connection re-establishment procedure.

[0474] As one embodiment, the first procedure is performing a cell reselection.

[0475] As one embodiment, in response to the expiration of the first timer, if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG, the first information block is set in the first variable; the first information block indicates the expiration of the first timer.

[0476] As one embodiment, in response to the expiration of the first timer, if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG, the first information block is set in the first variable; the first information block includes one pSCellId, the identification of the one PSCell is a global cell identity of a PSCell of the SCG or a physical cell identity and a carrier frequency of the PSCell.

[0477] As one embodiment, in response to the expiration of the first timer, the fast MCG recovery procedure fails.

[0478] As one embodiment, the fast MCG recovery procedure fails upon expiration of the first timer.

[0479] As one embodiment, in response to the failure of the fast MCG recovery procedure, if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG, the first information block is set in the first variable; the first information block indicates that the reason for the failure of the fast MCG recovery procedure is the expiration of the first timer.

[0480] As one embodiment, in response to the expiration of the first timer, if the terminal supports RLF reporting for the fast MCG recovery procedure, the first connection is not the SCG, the first information block is not set in the first variable.

[0481] As one embodiment, in response to the expiration of the first timer, if the terminal does not support RLF reporting for the fast MCG recovery procedure, the first information block is not set in the first variable.

[0482] As one embodiment, whether the terminal supports RLF reporting for the fast MCG recovery procedure depends on whether the first timer is configured.

[0483] As one embodiment, if the first timer is not configured, the terminal does not support RLF reporting for the fast MCG recovery procedure.

[0484] As one embodiment, the terminal does not support RLF reporting for the fast MCG recovery procedure when at least the first timer is not configured.

[0485] As one embodiment, whether the first message is sent depends on whether the first timer is configured.

[0486] As one embodiment, if the first timer is not configured, the first message is not sent.

[0487] As one embodiment, the first message is sent when at least the first timer is configured.

[0488] Embodiment 7

[0489] Embodiment 7 illustrates the accompanying the first timer includes the stopping the first timer according to one embodiment of the present application, as shown in FIG. 7.

[0490] In Embodiment 7, the first timer is stopped in response to the second message being received; wherein the first timer is running when the second message is received; the accompanying the first timer includes the stopping the first timer.

[0491] As one embodiment, the second message is an RRC message.

[0492] As one embodiment, the second message is a signaling below an RRC sublayer.

[0493] As one embodiment, the second message instructs the terminal to switch to another cell.

[0494] As one embodiment, the second message instructs the terminal to perform an RRC reconnection procedure.

[0495] As one embodiment, the second message is an RRCReconfiguration message carrying reconfigurationwithSync for a PCell.

[0496] As one embodiment, the second message is an RRCRelease message.

[0497] As one embodiment, the second message is a MobilityFromNRCommand message.

[0498] As one embodiment, the second message is any one of an RRCReconfiguration message carrying reconfigurationwithSync for a PCell or an RRCRelease message or a MobilityFromNRCommand message.

[0499] As one embodiment, the accompanying the first timer means as a response to the second message being received.

[0500] As one embodiment, the accompanying the first timer means when the first timer is stopped.

[0501] As one embodiment, the accompanying the first timer means as a response to the first timer being stopped.

[0502] As one embodiment, the accompanying the first timer means immediately following the first timer being stopped.

[0503] As one embodiment, the accompanying the first timer means after the first timer being stopped.

[0504] As one embodiment, as a response to the first timer being stopped, if the terminal supports the fast MCG recovery procedure and the first connection is the SCG, a first information block is set in the first variable, the first information block including one elapsedTimeT316 field, the one elapsedTimeT316 field being set to a value of a time elapsed by the first timer.

[0505] As one embodiment, as a response to the first timer being stopped, if the terminal supports the fast MCG recovery procedure and the first connection is the SCG, a first information block is set in the first variable, the first information block including one pSCellId, the identification of the one PSCell being a global cell identity of the PSCell or a physical cell identity and a carrier frequency of the PSCell.

[0506] As one embodiment, as a response to the first timer being stopped, if the terminal supports the fast MCG recovery procedure and the first connection is not the SCG, no first information block is set in the first variable.

[0507] As one embodiment, in response to the stopping of the first timer, a first block of information is not set in the first variable if the terminal does not support the fast MCG recovery procedure.

[0508] As one embodiment, in response to the receiving of the second message, transmission of the MCG is resumed; the second message is an RRCReconfiguration message carrying reconfigurationwithSync for a PCell.

[0509] As one embodiment, the PCell of the MCG is not a source PCell.

[0510] As one embodiment, in response to the receiving of the second message, a current RRC connection is released; the second message is an RRCRelease message.

[0511] As one embodiment, in response to the receiving of the second message, a current RRC connection is suspended; the second message is an RRCRelease message.

[0512] As one embodiment, in response to the receiving of the second message, an RRC_IDLE state is entered; the second message is an RRCRelease message.

[0513] As one embodiment, the response to the receiving of the second message means: immediately after the receiving of the second message.

[0514] As one embodiment, the response to the receiving of the second message means: after the receiving of the second message and a time interval.

[0515] As one sub-embodiment of the above embodiment, the time interval is 60 ms.

[0516] As one sub-embodiment of the above embodiment, the time interval is in ms.

[0517] As one sub-embodiment of the above embodiment, the time interval is in s.

[0518] As one sub-embodiment of the above embodiment, the time interval is default.

[0519] As one sub-embodiment of the above embodiment, the time interval is configurable.

[0520] As one embodiment, the response to the receiving of the second message means: when a lower layer indicates that the second message is successfully received.

[0521] As one embodiment, the response to the reception of the second message refers to when the second message is delivered to an RRC layer.

[0522] As one embodiment, the response to the reception of the second message refers to when configuration information in the second message is applied.

[0523] As one embodiment, the response to the reception of the second message refers to when the application of the configuration information in the second message is completed.

[0524] Embodiment 8

[0525] Embodiment 8 illustrates a flowchart of clearing information included in the first variable according to one embodiment of the present application, as shown in FIG. 8.

[0526] In step S8101, it is determined whether the terminal does not support RLF reporting for a fast MCG recovery procedure or whether the first connection is not the SCG. In step S8102, if the terminal does not support RLF reporting for a fast MCG recovery procedure or the first connection is not the SCG, information included in the first variable is cleared.

[0527] In embodiment 8, if the terminal does not support RLF reporting for a fast MCG recovery procedure or the first connection is not the SCG, information included in the first variable is cleared.

[0528] As one embodiment, the terminal not supporting RLF reporting for a fast MCG recovery procedure includes the terminal not having a capability to support RLF reporting for a fast MCG recovery procedure.

[0529] As one embodiment, the terminal not supporting RLF reporting for a fast MCG recovery procedure includes the terminal self-determining not to support RLF reporting for a fast MCG recovery procedure.

[0530] As one embodiment, the terminal not supporting RLF reporting for a fast MCG recovery procedure includes the terminal being configured not to support RLF reporting for a fast MCG recovery procedure.

[0531] As one embodiment, the terminal not supporting RLF reporting for a fast MCG recovery procedure includes the terminal not supporting a first storage parameter, accompanying the terminal not supporting the first storage parameter, the terminal not supporting RLF reporting for a fast MCG recovery procedure.

[0532] As one embodiment, the terminal not supporting the first storage parameter refers to the first storage parameter not being set.

[0533] As one embodiment, the terminal not supporting the first stored parameter means that the first stored parameter is not set to support.

[0534] As one embodiment, the terminal not supporting the first stored parameter means that the first stored parameter does not exist.

[0535] As one embodiment, the first stored parameter means UE-NR-Capability.

[0536] As one embodiment, the first stored parameter belongs to UE-NR-Capability.

[0537] As one embodiment, the first stored parameter means mcgRLF-RecoveryViaSCG.

[0538] As one embodiment, the first stored parameter means son-Parameters.

[0539] As one embodiment, the first stored parameter belongs to son-Parameters.

[0540] As one embodiment, the terminal not supporting RLF reporting for the fast MCG recovery procedure along with the terminal not supporting the first stored parameter means that the terminal does not support RLF reporting for the fast MCG recovery procedure if the terminal does not support the first stored parameter.

[0541] As one embodiment, the terminal not supporting RLF reporting for the fast MCG recovery procedure along with the terminal not supporting the first stored parameter means that the terminal does not support RLF reporting for the fast MCG recovery procedure as long as the terminal does not support the first stored parameter.

[0542] As one embodiment, the clearing the information included in the first variable means not setting a first information block in the first variable.

[0543] As one embodiment, the clearing the information included in the first variable means clearing all information included in the first variable.

[0544] As one embodiment, the clearing the information included in the first variable means clearing RLF information for the fast MCG recovery procedure in the first variable.

[0545] As one embodiment, the clearing the information included in the first variable means clearing the first information block in the first variable.

[0546] As one embodiment, the clearing the information included in the first variable refers to releasing the first variable.

[0547] As one embodiment, if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, the clearing the information included in the first variable refers to not clearing the information included in the first variable if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG.

[0548] As one embodiment, if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, the clearing the information included in the first variable refers to clearing the information included in the first variable if the terminal does not support RLF reporting for the fast MCG recovery procedure.

[0549] As one embodiment, if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, the clearing the information included in the first variable refers to clearing the information included in the first variable if the first connection is not the SCG.

[0550] As one embodiment, if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, the clearing the information included in the first variable refers to clearing the information included in the first variable if the terminal does not support RLF reporting for the fast MCG recovery procedure and the first connection is not the SCG.

[0551] As one embodiment, if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, the clearing the information included in the first variable refers to clearing the information included in the first variable if the terminal does not support RLF reporting for the fast MCG recovery procedure.

[0552] As one embodiment, if the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, the clearing the information included in the first variable refers to clearing the information included in the first variable if the first connection is not the SCG.

[0553] Embodiment 9

[0554] Embodiment 9 illustrates a flowchart of judging whether the terminal supports RLF reporting for the fast MCG recovery procedure according to one embodiment of the present application, as shown in FIG. 9.

[0555] In step S9101, it is judged whether the first connection is the SCG; in step S9102a, if the first connection is the SCG, the terminal supports RLF reporting for the fast MCG recovery procedure; in step S9102b, if the first connection is not the SCG, the terminal does not support RLF reporting for the fast MCG recovery procedure.

[0556] In embodiment 9, whether the terminal supports RLF reporting for the fast MCG recovery procedure depends on whether the first connection is the SCG; wherein whether the terminal supports RLF reporting for the fast MCG recovery procedure depends on whether the first connection is the SCG comprises:

[0557] If at least the first connection is the SCG, the terminal supports RLF reporting for the fast MCG recovery procedure;

[0558] If the first connection is not the SCG, the terminal does not support RLF reporting for the fast MCG recovery procedure.

[0559] As an embodiment, "if at least the first connection is the SCG, the terminal supports RLF reporting for the fast MCG recovery procedure" means that the terminal only supports RLF reporting for the fast MCG recovery procedure through the SCG.

[0560] As an embodiment, "if at least the first connection is the SCG, the terminal supports RLF reporting for the fast MCG recovery procedure" means that if at least the first connection is the SCG, it is assumed that the terminal supports RLF reporting for the fast MCG recovery procedure.

[0561] As an embodiment, "if at least the first connection is the SCG, the terminal supports RLF reporting for the fast MCG recovery procedure" means that the terminal supports RLF reporting for the fast MCG recovery procedure when at least the first connection is the SCG.

[0562] As an embodiment, "if at least the first connection is the SCG, the terminal supports RLF reporting for the fast MCG recovery procedure" means that the terminal can only support RLF reporting for the fast MCG recovery procedure on the premise that the first connection is the SCG.

[0563] As an embodiment, "if the first connection is not the SCG, the terminal does not support RLF reporting for the fast MCG recovery procedure" means that as long as the first connection is not the SCG, the terminal does not support RLF reporting for the fast MCG recovery procedure.

[0564] As one embodiment, "if the first connection is not the SCG, the terminal does not support RLF reporting for the fast MCG recovery procedure" means that the terminal does not support RLF reporting for the fast MCG recovery procedure through the SCG.

[0565] As one embodiment, "if the first connection is not the SCG, the terminal does not support RLF reporting for the fast MCG recovery procedure" means that the terminal does not support RLF reporting for the fast MCG recovery procedure through the non-direct path.

[0566] As one embodiment, if the first connection is the SCG, the terminal supports RLF reporting for the fast MCG recovery procedure; if the terminal supports RLF reporting for the fast MCG recovery procedure, the first information block is set in the first variable.

[0567] As one embodiment, if the first connection is not the SCG, the terminal does not support RLF reporting for the fast MCG recovery procedure; if the terminal does not support RLF reporting for the fast MCG recovery procedure, the first information block is not set in the first variable.

[0568] Embodiment 10

[0569] Embodiment 10 illustrates a flowchart of judging whether the first information block exists in the first variable according to one embodiment of the present application, as shown in FIG. 10.

[0570] In step S10101, it is judged whether the terminal supports RLF reporting for the fast MCG recovery procedure; in step S10102, it is judged whether the first connection is the SCG; in step S10102a, the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG, the first information block exists in the first variable; in step S10102b, the terminal does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, the first information block does not exist in the first variable.

[0571] In embodiment 10, the first information block is conditionally present in the first variable; wherein the first information block is conditionally present in the first variable means that:

[0572] if the terminal supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG, the first information block exists in the first variable;

[0573] The first information block is absent in the first variable if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG.

[0574] As one embodiment, the first information block is conditionally present in the first variable means that the storing of the first information block is optional.

[0575] As one embodiment, the first information block is conditionally present in the first variable means that the first information block is present in the first variable only if a storage condition is fulfilled.

[0576] As one embodiment, the first information block is conditionally present in the first variable means that the first information block is present in the first variable when a storage condition is fulfilled.

[0577] As one embodiment, the first information block is conditionally present in the first variable means that the first information block is present in the first variable if a storage condition is fulfilled.

[0578] As one embodiment, "the first information block is present in the first variable if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG" means that the first information block is not cleared in the first variable if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG.

[0579] As one embodiment, "the first information block is present in the first variable if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG" means that the first information block is set in the first variable if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG.

[0580] As one embodiment, "the first information block is present in the first variable if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG" means that the first information block is maintained in the first variable if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG.

[0581] As an embodiment, "the first information block is present in the first variable if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG" means that the first information block includes RLF information for fast MCG recovery procedure and the SCG information if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG.

[0582] As an embodiment, the first information block includes fast MCG recovery procedure information and the SCG information includes that the first information block includes elapsed time information of T316 in the fast MCG recovery procedure and pSCellId of PSCell of the SCG.

[0583] As an embodiment, the first information block includes fast MCG recovery procedure information and the SCG information includes that the first information block includes at least elapsed time information of T316 in the fast MCG recovery procedure and pSCellId of PSCell of the SCG.

[0584] As an embodiment, "the first information block is present in the first variable if the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG" means that the first information block is present in the first variable as long as the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG.

[0585] As an embodiment, "the first information block is not present in the first variable if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG" means that the first information block is not present in the first variable as long as the terminal does not support RLF reporting for fast MCG recovery procedure.

[0586] As an embodiment, "the first information block is not present in the first variable if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG" means that the first information block is not present in the first variable if the terminal does not support RLF reporting for fast MCG recovery procedure and the first connection is not the SCG.

[0587] As an embodiment, "the first information block is not present in the first variable if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG" means that the first information block is not present in the first variable as long as the first connection is not the SCG.

[0588] As one embodiment, the first information block being absent in the first variable comprises the first information block being cleared in the first variable.

[0589] As one embodiment, the first information block being absent in the first variable comprises the first information block not being set in the first variable.

[0590] As one embodiment, the first information block being absent in the first variable comprises the first information block not being maintained in the first variable.

[0591] Embodiment 11

[0592] Embodiment 11 illustrates a diagram of the first connection being non-SCG according to one embodiment of the present application, as shown in FIG. 11.

[0593] In embodiment 11, the first connection being non-SCG comprises the first connection being indirect path.

[0594] As one embodiment, the first connection being non-SCG means the first connection being indirect path.

[0595] As one embodiment, the first connection being non-SCG means at least the first connection being indirect path.

[0596] As one embodiment, the first connection being indirect path comprises the first connection being Sidelink (SL).

[0597] As one embodiment, the first connection being indirect path comprises the first connection being N3C (Non-3GPP Connection).

[0598] As one embodiment, the first connection being indirect path comprises the first connection being either of Sidelink or N3C.

[0599] As one embodiment, the first connection being indirect path depends on determining radio connection failure.

[0600] As one embodiment, the first connection being indirect path depending on determining radio connection failure means the first connection being indirect path if the determining radio connection failure is determining direct path radio connection failure.

[0601] As one embodiment, the first connection is a non-direct path dependent determined radio connection failure means that the determined radio connection failure is a determined direct path radio connection failure, and the first connection is a non-direct path.

[0602] As one embodiment, the first connection is a non-direct path dependent determined radio connection failure means that the terminal is configured with multi-path (MP) before the determined radio connection failure, and the first connection is a non-direct path.

[0603] As one embodiment, the terminal is configured with multi-path before the determined radio connection failure means that the terminal is configured with one direct path and one non-direct path before the determined radio connection failure.

[0604] As one embodiment, the terminal is configured with multi-path before the determined radio connection failure means that the terminal is configured with at least one direct path and one non-direct path before the determined radio connection failure.

[0605] As one embodiment, the terminal is configured with multi-path before the determined radio connection failure means that the terminal is configured with at least two paths before the determined radio connection failure.

[0606] As one embodiment, the terminal is configured with multi-path before the determined radio connection failure means that the terminal is configured with multi-path and the MCG connection before the determined radio connection failure.

[0607] As one embodiment, the first connection is a non-direct path dependent determined radio connection failure means that the determined radio connection failure is a determined direct path radio connection failure only, and the first connection is a non-direct path.

[0608] As one embodiment, the first connection is a non-direct path dependent determined radio connection failure means that the non-direct path is not indicated to change or addition when the determined radio connection failure, and the first connection is a non-direct path.

[0609] As one embodiment, the first connection is a non-direct path dependent determined radio connection failure means that the change or addition of the non-direct path is not running when the determined radio connection failure, and the first connection is a non-direct path.

[0610] Embodiment 12

[0611] Embodiment 12 illustrates a diagram of the third message including at least part of the information in the first variable according to one embodiment of the present application, as shown in FIG. 12.

[0612] In Embodiment 12, the third message includes at least part of the information in the first variable.

[0613] As one embodiment, one UEInformationRequest message triggers the third message; wherein the one UEInformationRequest message includes one rlf-ReportReq field, the one rlf-ReportReq field is set to true; the third message is a UEInformationResponse message.

[0614] As one embodiment, one UEInformationRequest message triggers the third message; the one UEInformationRequest message includes one rlf-ReportReq field, the one rlf-ReportReq field is set to true, the third message is a UEInformationResponse message; the third message includes one RLF-Report.

[0615] As one embodiment, the third message is a UEAssistanceInformation message.

[0616] As one embodiment, the third message is a RRCResumeRequest message.

[0617] As one embodiment, the third message is a RRCReestablishmentRequest message.

[0618] As one embodiment, the third message includes at least part of the information in the first variable means: the third message includes all the information in the first variable.

[0619] As one embodiment, the third message includes at least part of the information in the first variable means: the third message includes at least a first information block in the first variable.

[0620] As one embodiment, the third message includes at least part of the information in the first variable means: the third message includes a first information block in the first variable.

[0621] As one embodiment, the third message includes at least part of the information in the first variable means: the third message includes an RLF-report in the first variable.

[0622] As an embodiment, the third message including at least part of the information in the first variable means that the third message includes information in the first variable which is indicated by the network to report.

[0623] As an embodiment, the third message including at least part of the information in the first variable means that the third message includes information in the first variable which has a higher priority.

[0624] As an embodiment, the priority is based on network indication.

[0625] As an embodiment, the priority is based on terminal implementation.

[0626] As an embodiment, the information with higher priority is time information.

[0627] As an embodiment, the information with higher priority is measurement result.

[0628] As an embodiment, the third message is sent after the fast MCG recovery procedure is completed, the third message is a RRCReconfigurationComplete message, and the third message includes at least part of the information in the first variable.

[0629] As an embodiment, the third message is sent after the fast MCG recovery procedure is completed, the third message is a UEAssistanceInformation message, and the third message includes at least part of the information in the first variable.

[0630] As an embodiment, the third message is sent after the fast MCG recovery procedure is completed, the third message is a UEInformationResponse message, and the third message includes at least part of the information in the first variable.

[0631] As an embodiment, the third message is sent after the fast MCG recovery procedure is completed, the third message is a RRCResumeRequest message, and the third message includes at least part of the information in the first variable.

[0632] As an embodiment, the third message is sent after the fast MCG recovery procedure fails, the third message is a RRCReestablishmentRequest message, and the third message includes at least part of the information in the first variable.

[0633] As an embodiment, the terminal indicates availability of a first information block in the first variable after the fast MCG recovery procedure is completed; the third message is triggered by one UEInformationRequest message; the one UEInformationRequest message includes one rlf-ReportReq field, the one rlf-ReportReq field is set to true, the third message is a UEInformationResponse message; the third message includes one RLF-Report.

[0634] Embodiment 13

[0635] Embodiment 13 illustrates a structure block diagram of a processing apparatus in a terminal according to an embodiment of the present application; as shown in FIG. 13. In FIG. 13, the processing apparatus 1300 in the terminal includes a first processor 1301, a first receiver 1302 and a first transmitter 1303.

[0636] The first processor 1301 determines a radio connection failure;

[0637] In response to the determination of the radio connection failure, a first message is sent through a first connection and a first timer is started; wherein the first message is for a fast MCG recovery procedure; the first timer is configured;

[0638] In embodiment 13, whether a first information block is set in a first variable depends on whether the first connection is an SCG and whether the terminal supports RLF reporting for a fast MCG recovery procedure, accompanying the first timer; the first variable includes connection failure information; the first information block indicates an elapsed time of the first timer; wherein the whether the first information block is set in the first variable depends on whether the first connection is the SCG and whether the terminal supports the RLF reporting for the fast MCG recovery procedure includes:

[0639] If the terminal supports the RLF reporting for the fast MCG recovery procedure and the first connection is the SCG, the first information block is set in the first variable;

[0640] If the terminal does not support the RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG, the first information block is not set in the first variable.

[0641] As an embodiment, the terminal includes one or more processors and a memory;

[0642] The memory is coupled with the one or more processors, and the memory is configured to store computer program codes including computer instructions, and the one or more processors are configured to invoke the computer instructions to cause the terminal to perform the method in the terminal for wireless communication.

[0643] As one embodiment, the accompanying the first timer comprises: the first timer expires.

[0644] As one embodiment, the first receiver 1302 receives a second message; in response to the second message being received, the first timer is stopped;

[0645] As one embodiment, the first timer is running when the second message is received; the accompanying the first timer comprises: the stopping the first timer.

[0646] As one embodiment, if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG, the information included in the first variable is cleared.

[0647] As one embodiment, whether the terminal supports RLF reporting for fast MCG recovery procedure depends on whether the first connection is the SCG; wherein whether the terminal supports RLF reporting for fast MCG recovery procedure depends on whether the first connection is the SCG comprises:

[0648] If at least the first connection is the SCG, the terminal supports RLF reporting for fast MCG recovery procedure;

[0649] If the first connection is not the SCG, the terminal does not support RLF reporting for fast MCG recovery procedure.

[0650] As one embodiment, the first information block is conditionally present in the first variable; wherein the first information block is conditionally present in the first variable means:

[0651] If the terminal supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG, the first information block is present in the first variable;

[0652] If the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG, the first information block is not present in the first variable.

[0653] As one embodiment, the first connection is not the SCG comprises: the first connection is a non-direct path.

[0654] As one embodiment,

[0655] a first transmitter 1303, sending the third message;

[0656] wherein the third message comprises at least part of the information in the first variable.

[0657] As one embodiment, the first processor 1301 comprises the first receiver 1302.

[0658] As one embodiment, the first processor 1301 comprises the first transmitter 1303.

[0659] As one embodiment, the first processor 1301 comprises the first receiver 1302 and the first transmitter 1303.

[0660] As one embodiment, the first receiver 1302 comprises at least one of the antenna 452 or the receiver 454 or the multi-antenna receiving processor 458 or the receiving processor 456 or the controller / processor 459 or the memory 460 or the data source 467 in Figure 4 of the present application.

[0661] As one embodiment, the first receiver 1302 comprises at least the antenna 452 and the receiver 454 in Figure 4 of the present application.

[0662] As one embodiment, the first transmitter 1303 comprises at least one of the antenna 452 or the transmitter 454 or the multi-antenna transmitting processor 457 or the transmitting processor 468 or the controller / processor 459 or the memory 460 or the data source 467 in Figure 4 of the present application.

[0663] As one embodiment, the first transmitter 1303 comprises at least the antenna 452 and the transmitter 454 in Figure 4 of the present application.

[0664] As one embodiment, the first message is set by the first receiver 1302.

[0665] As one embodiment, the first message is set by the first transmitter 1303.

[0666] As one embodiment, the first message is set by the memory 460 in the first receiver 1302.

[0667] As one embodiment, the first message is set by the memory 460 in the first transmitter 1303.

[0668] As one example, the first message is set by a controller / processor 459 in the first receiver 1302.

[0669] As one example, the first message is set by a controller / processor 459 in the first transmitter 1303.

[0670] As one example, the third message is set by the first receiver 1302.

[0671] As one example, the third message is set by the first transmitter 1303.

[0672] As one example, the third message is set by a memory 460 in the first receiver 1302.

[0673] As one example, the third message is set by a memory 460 in the first transmitter 1303.

[0674] As one example, the third message is set by a controller / processor 459 in the first receiver 1302.

[0675] As one example, the third message is set by a controller / processor 459 in the first transmitter 1303.

[0676] Embodiment 14

[0677] Embodiment 14 illustrates a structural block diagram of a processing device in a base station according to an embodiment of the application; as shown in Figure 14. In Figure 14, the processing device 1400 in the base station includes a second processor 1401.

[0678] The second processor 1401 receives a third message; wherein the sender of the third message determines that a wireless connection fails; in response to the determination that the wireless connection fails, the sender of the third message sends a first message through a first connection and starts a first timer; wherein the first message indicates the wireless connection failure; the first timer is configured;

[0679] In embodiment 14, whether the sender of the third message sets a first information block in a first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure, accompanying the first timer; the first variable includes connection failure information; the third message includes at least part of the information in the first variable; the first information block indicates an elapsed time of the first timer; wherein the whether the sender of the third message sets the first information block in the first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for a fast MCG recovery procedure includes:

[0680] if the sender of the third message supports RLF reporting for a fast MCG recovery procedure and the first connection is the SCG, setting the first information block in the first variable;

[0681] if the sender of the third message does not support RLF reporting for a fast MCG recovery procedure or the first connection is not the SCG, not setting the first information block in the first variable.

[0682] As an embodiment, the base station comprises one or more processors and a memory;

[0683] The memory is coupled to the one or more processors, and the memory is configured to store computer program codes including computer instructions, and the one or more processors are configured to invoke the computer instructions to cause the base station to perform the method in the base station for wireless communication.

[0684] As an embodiment, the accompanying the first timer comprises that the first timer expires.

[0685] As an embodiment, the sender of the third message receives a second message; in response to the second message being received, the sender of the third message stops the first timer; wherein the first timer is running when the second message is received; the accompanying the first timer comprises that the first timer is stopped.

[0686] As an embodiment, if the sender of the third message does not support RLF reporting for a fast MCG recovery procedure or the first connection is the non-direct path, the sender of the third message clears the information included in the first variable.

[0687] As an embodiment, whether the sender of the third message supports RLF reporting for the fast MCG recovery procedure depends on whether the first connection is the SCG; wherein whether the sender of the third message supports RLF reporting for the fast MCG recovery procedure depends on whether the first connection is the SCG comprises:

[0688] the sender of the third message supports RLF reporting for the fast MCG recovery procedure if at least the first connection is the SCG;

[0689] the sender of the third message does not support RLF reporting for the fast MCG recovery procedure if the first connection is not the SCG.

[0690] As an embodiment, the first information block is conditionally present in the first variable; wherein the first information block is conditionally present in the first variable means:

[0691] the first information block is present in the first variable if the sender of the third message supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG;

[0692] the first information block is not present in the first variable if the sender of the third message does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG.

[0693] As an embodiment, the first connection is not the SCG comprises: the first connection is a non-direct path.

[0694] As an embodiment, the second processor 1401 receives the third message;

[0695] wherein the third message comprises at least part of the information in the first information block.

[0696] As an embodiment, the second processor 1401 comprises a second receiver.

[0697] As an embodiment, the second processor 1401 comprises a second transmitter.

[0698] As an embodiment, the second processor 1401 comprises a second receiver and a second transmitter.

[0699] As an embodiment, the second transmitter comprises at least one of the antenna 420 or the transmitter 418 or the multi-antenna transmit processor 471 or the transmit processor 416 or the controller / processor 475 or the memory 476 in FIG. 4.

[0700] As one embodiment, the second transmitter comprises at least one of the antenna 420 and the transmitter 418 in FIG. 4 of this application.

[0701] As one embodiment, the second receiver comprises at least one of the antenna 420 or the receiver 418 or the multi-antenna reception processor 472 or the reception processor 470 or the controller / processor 475 or the memory 476 in FIG. 4 of this application.

[0702] As one embodiment, the second receiver comprises at least one of the antenna 420 and the receiver 418 in FIG. 4 of this application.

[0703] As one embodiment, the second message is set by the second receiver.

[0704] As one embodiment, the second message is set by the second transmitter.

[0705] As one embodiment, the second message is set by the memory 476 in the second receiver.

[0706] As one embodiment, the second message is set by the memory 476 in the second transmitter.

[0707] As one embodiment, the second message is set by the controller / processor 475 in the second receiver.

[0708] As one embodiment, the second message is set by the controller / processor 475 in the second transmitter.

[0709] Those skilled in the art can understand that all or part of the steps in the foregoing method can be instructed by programs to the relevant hardware to complete, and the programs can be stored in a computer readable storage medium, such as a read-only memory, a hard disk, an optical disk or the like. Alternatively, all or part of the steps of the foregoing embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the foregoing embodiments can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in the present application include but are not limited to unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication devices, wireless sensors, network cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base station or system device in the present application includes but is not limited to macro cellular base stations, micro cellular base stations, home base stations, relay base stations, gNB (NR NodeB) NR NodeB, TRP (Transmitter Receiver Point) and other wireless communication devices.

[0710] The above only describes the preferred embodiments of the present application and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

A method used in a terminal, characterized in that comprises: determining a radio connection failure; in response to said determining a radio connection failure, sending a first message over a first connection and starting a first timer; wherein said first message is for a fast MCG recovery procedure; said first timer is configured; wherein, in conjunction with said first timer, whether a first information block is set in a first variable depends on whether said first connection is an SCG and whether said terminal supports RLF reporting for a fast MCG recovery procedure; said first variable comprises connection failure information; said first information block indicates an elapsed time of said first timer; wherein said whether a first information block is set in a first variable depends on whether said first connection is an SCG and whether said terminal supports RLF reporting for a fast MCG recovery procedure comprises: if said terminal supports RLF reporting for a fast MCG recovery procedure and said first connection is said SCG, said first information block is set in said first variable; if said terminal does not support RLF reporting for a fast MCG recovery procedure or said first connection is not said SCG, said first information block is not set in said first variable. The method according to claim 1, characterized in that said in conjunction with said first timer comprises: said first timer expires. The method according to claim 1, characterized in that said method comprises: receiving a second message; in response to said second message being received, stopping said first timer; wherein said first timer is running when said second message is received; said in conjunction with said first timer comprises: said stopping said first timer. The method according to any of claims 1-3, characterized in that said method comprises: if said terminal does not support RLF reporting for a fast MCG recovery procedure or first connection is not said SCG, clearing information included in said first variable. The method according to any of claims 1-4, characterized in that whether said terminal supports RLF reporting for a fast MCG recovery procedure depends on whether said first connection is said SCG; wherein said whether said terminal supports RLF reporting for a fast MCG recovery procedure depends on whether said first connection is said SCG comprises: if at least said first connection is said SCG, said terminal supports RLF reporting for a fast MCG recovery procedure; if said first connection is not said SCG, said terminal does not support RLF reporting for a fast MCG recovery procedure. The method according to any of claims 1-5, characterized in that said first information block is conditionally present in said first variable; wherein said first information block is conditionally present in said first variable means: if said terminal supports RLF reporting for a fast MCG recovery procedure and said first connection is said SCG, said first information block is present in said first variable; if said terminal does not support RLF reporting for a fast MCG recovery procedure or said first connection is not said SCG, said first information block is not present in said first variable. The first information block is not present in the first variable if the terminal does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG. The method of any of claims 1-6, wherein The first connection is not the SCG comprises that the first connection is a non-direct path. The method of any of claims 1-7, wherein The method comprises: sending a third message; wherein the third message comprises at least part of the information in the first variable. A terminal, comprising: one or more processors and a memory; the memory coupled to the one or more processors, the memory configured to store computer program code comprising computer instructions, the one or more processors configured to invoke the computer instructions to cause the terminal to perform the method of any of claims 1-8. A method used in a base station, comprising: receiving a third message; wherein a sender of the third message determines a radio connection failure; in response to the determining the radio connection failure, the sender of the third message sends a first message over a first connection and starts a first timer; wherein the first message indicates the radio connection failure; the first timer is configured to; wherein, in conjunction with the first timer, whether the sender of the third message sets a first information block in a first variable depends on whether the first connection is an SCG and whether the sender of the third message supports RLF reporting for fast MCG recovery procedure; the first variable comprises connection failure information; the third message comprises at least part of the information in the first variable; the first information block indicates an elapsed time of the first timer; wherein the whether the sender of the third message sets the first information block in the first variable depends on whether the first connection is the SCG and whether the sender of the third message supports RLF reporting for fast MCG recovery procedure comprises: setting the first information block in the first variable if the sender of the third message supports RLF reporting for fast MCG recovery procedure and the first connection is the SCG; not setting the first information block in the first variable if the sender of the third message does not support RLF reporting for fast MCG recovery procedure or the first connection is not the SCG. The method of claim 10, wherein the conjunction with the first timer comprises that the first timer expires. The method of claim 10, wherein the sender of the third message receives a second message; in response to the second message being received, the sender of the third message stops the first timer; wherein the first timer is running when the second message is received; the conjunction with the first timer comprises that the first timer is stopped. The method of any of claims 10-12, wherein ​ If the sender of the third message does not support RLF reporting for the fast MCG recovery procedure or the first connection is the non-direct path, the sender of the third message clears the information included in the first variable. The method of any of claims 10-13, wherein whether the sender of the third message supports RLF reporting for the fast MCG recovery procedure depends on whether the first connection is the SCG; wherein whether the sender of the third message supports RLF reporting for the fast MCG recovery procedure depends on whether the first connection is the SCG comprises: the sender of the third message supports RLF reporting for the fast MCG recovery procedure if at least the first connection is the SCG; the sender of the third message does not support RLF reporting for the fast MCG recovery procedure if the first connection is not the SCG. The method of any of claims 10-14, wherein the first information block is conditionally present in the first variable; wherein the first information block is conditionally present in the first variable means that: the first information block is present in the first variable if the sender of the third message supports RLF reporting for the fast MCG recovery procedure and the first connection is the SCG; the first information block is not present in the first variable if the sender of the third message does not support RLF reporting for the fast MCG recovery procedure or the first connection is not the SCG. The method of any of claims 10-15, wherein the first connection is not the SCG comprises that the first connection is a non-direct path. The method of any of claims 10-16, wherein the method comprises: receiving a third message; wherein the third message includes at least part of the information in the first information block. A base station, comprising: one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is configured to store computer program codes including computer instructions, and the one or more processors are configured to invoke the computer instructions to cause the base station to perform the method of any of claims 10-17.

Images