Method and device used for connection failure prediction

Abstract

The invention discloses a method and device used for connection failure prediction. The communication node receives the first signaling; wherein the first signaling indicates a first threshold value; maintaining the first counter; wherein the step of maintaining the first counter comprises the following steps: if the first counter reaches the first threshold value, determining that the connection fails; the maintaining the first counter comprises: if the first counter reaches a second threshold, performing a connection failure prediction; the first counter is a counter, or the first counter is a timer; the first threshold value is different from the second threshold value. According to the scheme provided by the invention, the overhead of the UE is reduced while the mobility performance is improved.

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and in particular to a method and device for connection failure prediction. Background Art

[0002] For existing services or future services (such as XR), when the UE (User Equipment) is highly mobile or moves between high-density cells, it will lead to more unexpected handover failures (HOF), radio link failures (RLF), ping-pong, throughput loss or premature / late handovers. Considering the potential of AI (Artificial Intelligence) / ML (Machine Learning) algorithm-based mechanisms to implement proactive solutions and the relevant progress of RAN1 and RAN3 in AI / ML, 3GPP (the 3rd Generation Partnership Project) has passed the SI (Study Item) of "Study on AI / ML for mobility in NR" to study and evaluate the potential benefits and gains of AI / ML-assisted mobility for network-triggered L3-based handovers, including RLF prediction or HOF prediction. Summary of the invention

[0003] The inventors have found through research that since RLF prediction or HOF prediction is performed on the UE (User Equipment) side, while RLF prediction or HOF prediction improves mobility performance, it also brings additional power consumption, signaling and other overheads to the UE. Therefore, how to reduce the impact of RLF prediction or HOF prediction on the UE needs to be further enhanced.

[0004] In view of the above problems, the present application provides a solution. In the description of the above problems, the NR system is used as an example. The present application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) or 5G+ or 6G systems, and achieves technical effects similar to those of the NR system; further, although the present application provides a specific implementation method for RLF, the present application can also be used in scenarios such as HOF to achieve technical effects similar to those of RLF. Furthermore, adopting a unified design scheme for different scenarios can also help reduce hardware complexity and cost. Furthermore, although the original intention of the present application is for the Uu air interface, the present application can also be used for the PC5 port to achieve technical effects similar to those of the Uu air interface. Furthermore, although the original intention of the present application is for the terminal and base station scenario, the present application is also applicable to V2X (Vehicle-to-Everything) scenarios, communication scenarios between the terminal and the relay, and the relay and the base station, and achieves technical effects similar to those in the terminal and base station scenarios. Furthermore, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the IAB (Integrated Access and Backhaul) communication scenario, and achieves similar technical effects in the terminal and base station scenario. Furthermore, although the original intention of this application is for the terrestrial network (TN) scenario, this application is also applicable to the non-terrestrial network (NTN) communication scenario, and achieves similar technical effects in the TN scenario. In addition, the use of a unified solution for different scenarios can also help reduce hardware complexity and costs.

[0005] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the 3GPP specification protocol TS36 series.

[0006] As an example, the interpretation of the terms in the present application refers to the definition of the TS38 series of specification protocols of 3GPP.

[0007] As an example, the interpretation of the terms in the present application refers to the definition of the TS37 series of specification protocols of 3GPP.

[0008] As an embodiment, the interpretation of the terms in the present application refers to the definition of the 6G series of specification protocols of 3GPP.

[0009] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

[0010] The present application discloses a method used in a terminal, characterized by comprising:

[0011] receiving a first signaling, wherein the first signaling indicates a first threshold; if the first counter reaches the first threshold, determining that the connection fails;

[0012] If the first statistic reaches a second threshold, connection failure prediction is performed; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0013] As an embodiment, the first statistic device is a counter.

[0014] As an embodiment, the first counter is a timer.

[0015] As an embodiment, the candidate for the first counter is a counter.

[0016] As an embodiment, the candidate for the first counter is a timer.

[0017] As an embodiment, candidates for the first counter include a counter and a timer.

[0018] As an embodiment, the connection failure prediction is RLF prediction.

[0019] As an embodiment, the connection failure prediction is HOF prediction.

[0020] As an embodiment, the problem to be solved by the present application includes: how to reduce the impact of connection failure prediction on UE; the above method solves the above problem by introducing the execution condition of connection failure prediction.

[0021] As an embodiment, the problem to be solved by the present application includes: how to trigger connection failure prediction; the above method triggers the execution of connection failure prediction when the first statistic reaches the second threshold, thereby solving the above problem.

[0022] As an embodiment, the problems to be solved by the present application include: what characteristics does the first counter have; in the above method, if the first counter reaches the first threshold, it is determined that the connection fails, thereby solving the above problem.

[0023] As an embodiment, the problems to be solved by the present application include: what characteristics does the first counter have; in the above method, the first counter is a counter, thereby solving the above problem.

[0024] As an embodiment, the problems to be solved by the present application include: what characteristics does the first counter have; in the above method, the first counter is a timer, thereby solving the above problem.

[0025] As an embodiment, the above method uses a timer that determines a connection failure to trigger a connection failure prediction.

[0026] As an embodiment, the above method uses a counter that determines connection failure to trigger connection failure prediction.

[0027] As an embodiment, the above method uses a threshold of a counter different from that used to determine connection failure to trigger connection failure prediction.

[0028] As an embodiment, the above method uses a timer threshold different from the one used to determine the connection failure to trigger the connection failure prediction.

[0029] As an embodiment, the above method is simple to implement.

[0030] As an embodiment, the above method reduces standardization work.

[0031] As an embodiment, the above method reduces the impact of connection failure prediction on the UE.

[0032] As an embodiment, the above method makes the trigger condition more reasonable.

[0033] According to one aspect of the present application, it is characterized in that when the first counter reaches the second threshold, a first notification is sent; and the first notification is received;

[0034] The first notification triggers the execution of the connection failure prediction.

[0035] As an embodiment, the problem to be solved by the present application includes: when the first statistic reaches the second threshold, how to trigger the execution of connection failure prediction; in the above method, the terminal sends and receives the first notification, thereby solving the above problem.

[0036] As an embodiment, the above method introduces the first notification inside the terminal, which is simple to implement.

[0037] As an embodiment, the above method is conducive to standardization.

[0038] As an embodiment, the above method is conducive to realizing the separation of connection failure detection and connection failure prediction.

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

[0040] The method comprises:

[0041] In response to the first condition being satisfied, aborting the connection failure prediction;

[0042] The first condition depends on at least one of measurement or prediction.

[0043] As an embodiment, the first condition depends on a measurement.

[0044] As an embodiment, the first condition depends on prediction.

[0045] As an embodiment, the first condition relies on measurement and prediction.

[0046] As an embodiment, the problem to be solved by the present application includes: how to reduce unnecessary connection failure predictions; the above method solves the above problem by terminating the connection failure prediction.

[0047] As an embodiment, the problem to be solved by the present application includes: how to terminate the connection failure prediction; the above method terminates the connection failure prediction when the first condition is satisfied, thereby solving the above problem.

[0048] As an embodiment, the problem to be solved by the present application includes: how to determine the first condition; in the above method, the first condition relies on measurement or prediction, thereby solving the above problem.

[0049] As an embodiment, the above method allows the connection failure prediction to be terminated according to the first condition during the connection failure prediction process.

[0050] As an embodiment, the above method further reduces the impact of connection failure prediction on the UE.

[0051] As an embodiment, the above method determines the first condition by at least one of measurement or prediction, so that the condition for terminating the connection failure prediction is more reasonable.

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

[0053] The method comprises:

[0054] When the first condition is met, sending a second notification; receiving the second notification;

[0055] The second notification triggers the termination of the connection failure prediction.

[0056] As an embodiment, the problem to be solved by the present application includes: when the first condition is met, how to trigger the termination of the connection failure prediction; in the above method, the terminal sends and receives the second notification, thereby solving the above problem.

[0057] As an embodiment, the above method introduces the second notification inside the terminal, which is simple to implement.

[0058] As an embodiment, the above method is conducive to standardization.

[0059] As an embodiment, the above method is conducive to realizing the separation of connection failure detection and connection failure prediction.

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

[0061] The method comprises:

[0062] In response to predicting a connection failure, a second counter is operated; the second counter is a counter, or the second counter is a timer.

[0063] As an embodiment, the problem to be solved by the present application includes: predicting what to do after a connection failure; the above method solves the above problem by operating the first statistics meter.

[0064] As an embodiment, the operating the first counter makes it easier to detect connection failure.

[0065] As an embodiment, the above method avoids detecting the connection failure too late by operating the first counter.

[0066] As an embodiment, the operating the first counter makes it more difficult to detect a connection failure.

[0067] As an embodiment, the above method avoids premature detection of connection failure by operating the first counter.

[0068] As an embodiment, the operating the first counter prevents connection failure from being detected by the first counter.

[0069] As an embodiment, the above method avoids the first counter triggering detection of connection failure by operating the first counter.

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

[0071] The method comprises:

[0072] In response to the predicted connection failure, an RRC connection reestablishment is initiated.

[0073] As an embodiment, the problem to be solved by the present application includes: predicting how to operate after a connection failure; the above method solves the above problem by initiating RRC connection reconstruction.

[0074] As an embodiment, the above method avoids detecting the connection failure too late by initiating RRC connection reestablishment.

[0075] As an embodiment, the above method improves the mobility robustness.

[0076] As an embodiment, the above method improves service continuity.

[0077] As an embodiment, the above method shortens the interruption delay.

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

[0079] The method comprises:

[0080] In response to the predicted connection failure, whether to operate the second counter or initiate RRC connection reconstruction depends on the predicted time of occurrence of the connection failure; the second counter is a counter, or the second counter is a timer.

[0081] As an embodiment, the problem to be solved by the present application includes: predicting what to do after a connection failure; the above method solves the above problem by operating the first statistics meter or starting RRC connection reconstruction.

[0082] As an embodiment, the problem to be solved by the present application includes: how to determine whether to operate the first statistic or start RRC connection reconstruction after predicting the connection failure. The above method solves the above problem by operating the first statistic or starting RRC connection reconstruction depending on the predicted time of occurrence of the connection failure.

[0083] As an embodiment, the above method predicts the UE behavior after the connection failure through adaptive adjustment, which can avoid detecting the connection failure too early and also avoid detecting the connection failure too late.

[0084] As an embodiment, the above method takes into account the influence of the predicted occurrence time of the connection failure, so as to select a more appropriate UE behavior.

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

[0086] The method comprises:

[0087] receiving at least a first reference signal;

[0088] Wherein, the connection failure prediction depends on the at least first reference signal.

[0089] As an embodiment, the problem to be solved by the present application includes: how to perform connection failure prediction; in the above method, the connection failure prediction depends on the at least first reference signal, thereby solving the above problem.

[0090] As an embodiment, the above method is beneficial to combining connection failure prediction and connection failure detection.

[0091] As an embodiment, the above method reduces standardization work.

[0092] As an embodiment, the above method is simple to implement.

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

[0094] The predicted connection failure depends on at least one of the number of predicted synchronization indications or the number of predicted out-of-sync indications within a first time window; the predicted synchronization indication or the predicted out-of-sync indication depends on at least the first reference signal.

[0095] As an embodiment, the problems to be solved by the present application include: how to determine the predicted connection failure; in the above method, the predicted connection failure depends on at least one of the number of predicted synchronization indications or the number of predicted out-of-sync indications within the first time window, thereby solving the above problem.

[0096] As an embodiment, the above method improves the accuracy of prediction.

[0097] The present application discloses a method used in a base station, characterized by comprising:

[0098] Sending a first signaling; wherein the first signaling indicates a first threshold; if the first counter reaches the first threshold, the receiver of the first signaling determines that the connection has failed;

[0099] If the first statistic reaches a second threshold, the receiver of the first signaling performs connection failure prediction; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0100] According to one aspect of the present application, it is characterized in that when the first statistic reaches a second threshold, the receiver of the first signaling sends a first notification; the receiver of the first signaling receives the first notification; wherein the first notification triggers the execution of the connection failure prediction.

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

[0102] In response to a first condition being met, the receiver of the first signaling terminates the connection failure prediction; wherein the first condition depends on at least one of measurement or prediction.

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

[0104] When the first condition is met, the receiver of the first signaling sends a second notification; the receiver of the first signaling receives the second notification; wherein the second notification triggers the termination of the connection failure prediction.

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

[0106] In response to predicting a connection failure, the receiver of the first signaling operates a second counter; the second counter is a counter, or the second counter is a timer.

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

[0108] In response to predicting the connection failure, the recipient of the first signaling initiates RRC connection reestablishment.

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

[0110] sending at least a first reference signal;

[0111] Wherein, the connection failure prediction depends on the at least first reference signal.

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

[0113] The first signaling indicates the second threshold.

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

[0115] The first condition includes that the first statistic reaches a third threshold; and the first signaling indicates the third threshold.

[0116] The present application discloses a terminal, characterized in that it includes:

[0117] The terminal includes: one or more processors and a memory;

[0118] The memory is coupled to the one or more processors, and is used to store computer program codes, where the computer program codes include computer instructions. The one or more processors call the computer instructions to enable the terminal to execute the method used in the terminal.

[0119] The present application discloses a base station, characterized in that it includes:

[0120] The base station includes: one or more processors and a memory;

[0121] The memory is coupled to the one or more processors, and is used to store computer program codes, where the computer program codes include computer instructions, and the one or more processors call the computer instructions to enable the base station to perform the method used in the base station. BRIEF DESCRIPTION OF THE DRAWINGS

[0122] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0123] Figure 1 A flowchart of a terminal according to an embodiment of the present application is shown;

[0124] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0125] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0126] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0127] Figure 5 A wireless signal transmission flow chart according to an embodiment of the present application is shown;

[0128] Figure 6 A wireless signal transmission flow chart according to another embodiment of the present application is shown;

[0129] Figure 7 A wireless signal transmission flow chart according to another embodiment of the present application is shown;

[0130] Figure 8 A wireless signal transmission flow chart according to another embodiment of the present application is shown;

[0131] Fig. 9 A schematic diagram of a first counter according to an embodiment of the present application is shown;

[0132] Fig.10 A schematic diagram showing a prediction of a connection failure according to an embodiment of the present application is shown;

[0133] Fig.11A structural block diagram of a processing device used in a terminal according to an embodiment of the present application is shown;

[0134] Fig.12 A structural block diagram of a processing device used in a base station according to an embodiment of the present application is shown.

[0135] Fig.13 A flow chart showing a first state according to an embodiment of the present application;

[0136] Fig.14 A schematic diagram showing transmission of a first notification and a second notification according to an embodiment of the present application;

[0137] Fig.15 A schematic diagram of an intelligent model according to an embodiment of the present application is shown;

[0138] Fig.16 A schematic diagram showing deployment of intelligent functions in a RAN (Radio Access Network) domain according to an embodiment of the present application is shown;

[0139] Fig.17 A schematic diagram showing deployment of UE intelligent functions according to an embodiment of the present application is shown;

[0140] Fig.18 A flowchart based on artificial intelligence or machine learning according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0141] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0142] Example 1

[0143] Embodiment 1 illustrates a flow chart of a terminal according to an embodiment of the present application, as shown in the attached Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0144] In Example 1, the terminal in the present application receives a first signaling in step 101; wherein the first signaling indicates a first threshold; if the first statistic reaches the first threshold, it is determined that the connection has failed; wherein if the first statistic reaches a second threshold, a connection failure prediction is performed; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0145] As an embodiment, the first signaling indicating the first threshold means that: the first signaling explicitly indicates the first threshold.

[0146] As an embodiment, the first signaling indicating the first threshold means that: the first signaling implicitly indicates the first threshold.

[0147] As an embodiment, the first signaling indicating the first threshold means that: the first signaling configures the first threshold.

[0148] As an embodiment, the first signaling indicating the first threshold means that: the first signaling enables the first threshold.

[0149] As an embodiment, the first signaling is cell common.

[0150] As an embodiment, the first signaling is UE specific.

[0151] As an embodiment, the first signaling is RRC (Radio Resource Control) signaling.

[0152] As an embodiment, the first signaling includes RRC signaling and MAC (Medium Access Control) CE (Control Element).

[0153] As an embodiment, the first signaling includes RRC signaling and DCI (Downlink Control Information).

[0154] As an embodiment, the first signaling includes an RRC signaling, and the RRC signaling configures the first threshold.

[0155] As an embodiment, the first signaling includes an RRC signaling and a MAC CE, the one RRC signaling configures multiple thresholds, and the one MAC CE indicates the first threshold from the multiple thresholds.

[0156] As an embodiment, the first signaling includes an RRC signaling and a DCI, the one RRC signaling configures multiple thresholds, and the one DCI indicates the first threshold from the multiple thresholds.

[0157] As an embodiment, a t310 in the first signaling indicates the first threshold; the first statistic is T310.

[0158] As an embodiment, a t304 in the first signaling indicates the first threshold; the first statistic is T304.

[0159] As an embodiment, a T312-r16 in the first signaling indicates the first threshold; the first statistic is T312.

[0160] As an embodiment, a T316-r16 in the first signaling indicates the first threshold; the first statistic is T316.

[0161] As an embodiment, a preambleTransMax in the first signaling indicates the first threshold; and the first statistic is PREAMBLE_TRANSMISSION_COUNTER.

[0162] As an embodiment, a preambleTransMax-r16 in the first signaling indicates the first threshold; and the first statistic is PREAMBLE_TRANSMISSION_COUNTER.

[0163] As an embodiment, a maxRetxThreshold in the first signaling indicates the first threshold; and the first statistic is RETX_COUNT.

[0164] As an embodiment, the first statistics detector performs connection failure prediction for PCell (Primary Cell) or MCG (Master Cell Group).

[0165] As an embodiment, the first statistics device performs connection failure prediction for PCell or MCG; for PSCell (Primary SCGCell) or SCG (Secondary Cell Group).

[0166] As an embodiment, the first statistician performs connection failure prediction for PSCell or SCG.

[0167] As an embodiment, the first statistician performs connection failure prediction for the target PCell or the target MCG.

[0168] As an embodiment, the first counter is an incremental counter.

[0169] As an embodiment, the first counter counts down.

[0170] As an embodiment, the first counter is incremented.

[0171] As an embodiment, the first counter is counted down.

[0172] As an embodiment, the first statistic reaching the first threshold means that: the first statistic is not less than the first threshold.

[0173] As an embodiment, the first statistic reaching the first threshold means that the first statistic is equal to the first threshold.

[0174] As an embodiment, the first statistic reaching the first threshold means that the first statistic is not greater than the first threshold.

[0175] As an embodiment, the first counter is a timer.

[0176] As an embodiment, the first counter is a timer; the first counter counts down.

[0177] As an embodiment, the first statistician is T310.

[0178] As an embodiment, the first statistician is T312.

[0179] As an embodiment, the first statistician is T316.

[0180] As an embodiment, the first statistician is T304.

[0181] As an embodiment, the first statistic device is a counter.

[0182] As an embodiment, the first counter is a counter; the first counter counts incrementally.

[0183] As an embodiment, the first counter is PREAMBLE_TRANSMISSION_COUNTER.

[0184] As an embodiment, the first counter is RETX_COUNT.

[0185] As an embodiment, the candidates for the first counter only include timers.

[0186] As an embodiment, the candidates for the first counter only include counters.

[0187] As an embodiment, the candidates for the first statistic include a timer and a counter.

[0188] As an embodiment, the candidates for the first counter include LBT_COUNTER.

[0189] As an embodiment, the above method increases the execution probability of link failure prediction.

[0190] As an embodiment, in any case, the candidates for the first statistic do not include LBT_COUNTER.

[0191] As an embodiment, the above method takes into account the uncertain characteristics of unlicensed spectrum to avoid prediction errors.

[0192] As an embodiment, the first counter is a counter; candidates for the first counter include at least one of PREAMBLE_TRANSMISSION_COUNTER or RETX_COUNT.

[0193] As an embodiment, the candidates for the first statistic include at least one of T310 or T312 or T304 or T316.

[0194] As an embodiment, the candidates of the first statistic depend on the RRC configuration.

[0195] As an embodiment, the candidate of the first statistic depends on the UE implementation of the terminal.

[0196] As an embodiment, the candidates for the first statistic are determined by the terminal itself.

[0197] As an embodiment, the first statistic reaching the first threshold value refers to: the first statistic expires; wherein the first statistic is a timer.

[0198] As a sub-embodiment of the above embodiment, the first threshold is 0; the second threshold is greater than 0; and the first counter is a decremental timer.

[0199] As a sub-embodiment of the above embodiment, the first threshold is greater than 0; the second threshold is greater than 0; the first threshold is greater than the second threshold; and the first statistic is incremented.

[0200] As an embodiment, the first statistic reaching the second threshold means that the first statistic is not greater than the second threshold.

[0201] As a sub-embodiment of the above embodiment, the first counter is decreasing.

[0202] As a sub-embodiment of the above embodiment, the first statistic reaching the first threshold value refers to: the first statistic expires; wherein the first statistic is a timer.

[0203] As a sub-embodiment of the above embodiment, the first statistic reaching a first threshold value means that: the first statistic is not greater than the first threshold value; wherein, the first statistic is a timer.

[0204] As a sub-embodiment of the above embodiment, the first statistic reaching a first threshold value means that: the first statistic is not greater than the first threshold value; wherein, the first statistic is a counter.

[0205] As a sub-embodiment of the above embodiment, the not greater than is less than.

[0206] As a sub-embodiment of the above embodiment, the said is not greater than or equal to.

[0207] As a sub-embodiment of the above embodiment, the not greater than is equal to or less than.

[0208] As a sub-embodiment of the above embodiment, the first threshold is 0; and the second threshold is greater than 0.

[0209] As a sub-embodiment of the above embodiment, the first threshold is greater than 0; the second threshold is greater than 0; and the first threshold is less than the second threshold.

[0210] As an embodiment, the first statistic reaching the second threshold means that: the first statistic is not less than the second threshold.

[0211] As a sub-embodiment of the above embodiment, the first statistic is incremental.

[0212] As a sub-embodiment of the above embodiment, the first statistic reaching the first threshold value refers to: the first statistic expires; wherein the first statistic is a timer.

[0213] As a sub-embodiment of the above embodiment, the first statistic reaching a first threshold value means that: the first statistic is not less than the first threshold value; wherein, the first statistic is a timer.

[0214] As a sub-embodiment of the above embodiment, the first statistic reaching a first threshold value means that: the first statistic is not less than the first threshold value; wherein, the first statistic is a counter.

[0215] As a sub-embodiment of the above embodiment, the not less than is greater than.

[0216] As a sub-embodiment of the above embodiment, the not less than is equal to.

[0217] As a sub-embodiment of the above embodiment, the not less than is equal to or greater than.

[0218] As a sub-embodiment of the above embodiment, the first threshold is greater than 0; the second threshold is greater than 0; and the first threshold is greater than the second threshold.

[0219] As an embodiment, the first statistic preferentially reaches the second threshold between the second threshold and the first threshold.

[0220] As an embodiment, the second threshold is indicated by RRC signaling.

[0221] As an embodiment, the second threshold is indicated by the related information of the predicted connection failure.

[0222] As an embodiment, the second threshold is determined by the terminal.

[0223] As an embodiment, the second threshold is a default threshold.

[0224] As an embodiment, the second threshold is dedicated to the connection failure prediction.

[0225] As an embodiment, the second threshold is dedicated to the intelligent model used for the connection failure prediction.

[0226] As an embodiment, the second threshold is equal to the product of the maximum value of the first statistic and the first ratio.

[0227] As an embodiment, the second threshold is equal to the product of the first threshold and the first ratio.

[0228] As an embodiment, the first ratio is configurable.

[0229] As an embodiment, the first ratio is greater than 0 and less than 1.

[0230] As an embodiment, the first ratio is greater than 1.

[0231] As an embodiment, the first ratio is fixed.

[0232] As an embodiment, the first ratio is indicated by RRC signaling.

[0233] As an embodiment, the first ratio is indicated by the related information of the predicted connection failure.

[0234] As an embodiment, the first ratio is determined by the terminal.

[0235] As an embodiment, the first ratio is a default ratio.

[0236] As an embodiment, the first offset is dedicated to the connection failure prediction.

[0237] As an embodiment, the first offset is dedicated to the intelligent model used for the connection failure prediction.

[0238] As an embodiment, the first offset is equal to the difference between the first threshold and the first offset.

[0239] As an embodiment, the first offset is equal to the difference between the maximum value of the first statistic and the first offset.

[0240] As an embodiment, the first offset is configurable.

[0241] As an embodiment, the first offset is fixed.

[0242] As an embodiment, the first offset is indicated by RRC signaling.

[0243] As an embodiment, the first offset is indicated by the related information of the predicted connection failure.

[0244] As an embodiment, the first offset is determined by the terminal.

[0245] As an embodiment, the first offset is a default.

[0246] As an embodiment, the first offset is dedicated to the connection failure prediction.

[0247] As an embodiment, the first offset is dedicated to the intelligent model used for the connection failure prediction.

[0248] As an embodiment, the connection failure is a wireless connection failure.

[0249] As an embodiment, the connection failure is a connection failure at the RRC layer.

[0250] As an embodiment, the connection failure is RLF.

[0251] As an embodiment, the connection failure is HOF.

[0252] As an embodiment, the connection failure is a connection recovery failure.

[0253] As an embodiment, the determination of connection failure refers to the MCG being considered to have detected a radio link failure; and the first statistic is a timer.

[0254] As an embodiment, the determination of connection failure refers to the MCG being considered to have detected a radio link failure; and the first statistic is a counter.

[0255] As an embodiment, the determining of connection failure refers to determining MCG synchronous reconfiguration failure; the first statistic is T304.

[0256] As an embodiment, the determining of connection failure refers to determining MCG HOF; the first statistic device is T304.

[0257] As an embodiment, the determination of connection failure refers to determining MCG quick recovery failure; the first statistic is T316.

[0258] As an embodiment, when the first statistic reaches the second threshold, how the terminal determines to perform connection failure prediction depends on UE implementation.

[0259] As an embodiment, when the first statistic reaches the second threshold, how the terminal notifies the smart module 1501 in Embodiment 14 depends on UE implementation.

[0260] As an embodiment, the connection failure prediction is performed by an intelligent model of the terminal for the connection failure prediction.

[0261] As an embodiment, the connection failure prediction is performed by the terminal based on UE implementation.

[0262] As an embodiment, the connection failure prediction is performed by the terminal based on network configuration.

[0263] As an embodiment, the connection failure prediction is performed by the terminal based on UE implementation and network configuration.

[0264] As an embodiment, the connection failure prediction is based on the most recent measurement results.

[0265] As an embodiment, the connection failure prediction is based on previous measurement results.

[0266] As an embodiment, the connection failure prediction is based on information stored by the terminal.

[0267] As an embodiment, the connection failure prediction is based on information provided by the network.

[0268] As an embodiment, the connection failure prediction is RLF prediction.

[0269] As an embodiment, the connection failure prediction is HOF prediction.

[0270] As an embodiment, the connection failure prediction includes reasoning.

[0271] As an embodiment, the connection failure prediction includes training.

[0272] As an embodiment, the connection failure prediction includes training and inference.

[0273] As an embodiment, the connection failure prediction includes predicting link quality.

[0274] As an embodiment, the connection failure prediction includes predicting a synchronization indication.

[0275] As an embodiment, the connection failure prediction includes predicting an out-of-sync indication.

[0276] As an embodiment, the connection failure prediction includes predicting whether a timer has expired.

[0277] As an embodiment, the connection failure prediction refers to predicting whether a connection failure will occur.

[0278] As an embodiment, the connection failure prediction refers to predicting the probability of a connection failure occurring.

[0279] As an embodiment, the connection failure prediction refers to predicting the time when the connection failure occurs.

[0280] As an embodiment, the connection failure prediction refers to a time interval during which a connection failure is predicted not to occur.

[0281] As an embodiment, the connection failure prediction refers to predicting the probability of connection failure occurring over time.

[0282] As an embodiment, for the terminal, AS security is activated, and at least one of SRB2 or at least one DRB or at least one multicast MRB is set; the execution of connection failure prediction is for MCG.

[0283] As an embodiment, for the terminal, T316 is not configured, or SCG transmission is suspended, or SCG is deactivated; the execution of connection failure prediction is for MCG.

[0284] As an embodiment, for the terminal, MCG transmission is suspended; and the execution of connection failure prediction is for SCG.

[0285] Example 2

[0286] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 Attached Figure 2The network architecture 200 is described. The network architecture 200 is a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system, or the network architecture 200 is a 5G+ network architecture, or the network architecture 200 is a 6G network architecture, or the network architecture 200 is a network architecture that 3GPP will continue to evolve in the future; the network architecture 200 may be called 5GS (5G System) / EPS (Evolved Packet System), or the network architecture 200 may be called 6GS (6G System); the network architecture 200 includes at least one of UE (User Equipment) 201, RAN (Radio Access Network) 202, core network 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220 and Internet service 230. The network architecture 200 can be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the network architecture 200 provides packet switching services, but it will be readily understood by those skilled in the art that the various concepts presented throughout this application can be extended to networks or other cellular networks that provide circuit switching services. 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 other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. The node 203 may 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 (transmitting and receiving node) or some other suitable term. The core network 210 is a 5GC (5G Core Network, 5G core network) / EPC (Evolved Packet Core), or, the core network 210 is a 6GC; the node 203 provides an access point to the core network 210 for the UE 201. Examples of UE 201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device.Those skilled in the art may also refer to UE201 as 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 communication 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 suitable term. Node 203 is connected to the core network 210 via an S1 / NG interface. The core network 210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF 213. MME / AMF / SMF 211 is a control node that processes signaling between UE201 and the core network 210. In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which is itself connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet Service 230. Internet Service 230 includes operator-corresponding Internet Protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

[0287] As an embodiment, the UE201 corresponds to the terminal in this application.

[0288] As an embodiment, the UE 201 is a user equipment (User Equipment, UE).

[0289] As an embodiment, the UE201 is a base station device (BaseStation, BS).

[0290] As an embodiment, the UE 201 is a relay device.

[0291] As an embodiment, the UE201 is a gateway device.

[0292] As an embodiment, the node 203 corresponds to the base station in this application.

[0293] As an embodiment, the node 203 is a base station device.

[0294] As an embodiment, the node 203 is a relay device.

[0295] As an embodiment, the node 203 is a gateway device.

[0296] As an embodiment, the user equipment supports intelligent functions.

[0297] As an embodiment, the user equipment supports an intelligent module.

[0298] As an embodiment, the user equipment supports an intelligent model.

[0299] As an embodiment, the user equipment supports an intelligent model for the connection failure prediction.

[0300] As an embodiment, the user equipment supports connection failure prediction.

[0301] As an embodiment, the user equipment supports RLF prediction and HOF prediction.

[0302] As an embodiment, the user equipment supports only one of RLF prediction and HOF prediction.

[0303] As an embodiment, the user equipment supports 3GPP Release 19.

[0304] As an embodiment, the user equipment supports 5G.

[0305] As an embodiment, the user equipment supports 6G.

[0306] As an embodiment, the user equipment supports Radio Link Monitoring (RLM).

[0307] As an embodiment, the user equipment supports switching.

[0308] As an embodiment, the user equipment supports CHO.

[0309] As an embodiment, the user equipment supports cell selection.

[0310] As an embodiment, the user equipment supports transmission of a non-terrestrial network (NTN).

[0311] As an embodiment, the user equipment supports transmission of a terrestrial network (Terrestrial Network).

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

[0313] As an embodiment, the user equipment includes a device supporting low-latency and high-reliability transmission.

[0314] As an embodiment, the user device may be a mobile terminal, which may be a mobile phone or an iPad or a computer or a watch or a ring; the user device may also be a wearable device, which may be a watch or a ring or a shoe or a hat or clothing or glasses, etc.; the user device may also be an aircraft; the user device may also be a vehicle-mounted terminal; the user device may also be a ship-mounted terminal; the user device may also be an Internet of Things terminal; the user device may also be an industrial Internet of Things terminal; the user device may also be a test device; the user device may also be a signaling tester; the user device may also be an IAB (Integrated Access and Backhaul)-MT.

[0315] As an embodiment, the base station device supports an intelligent model.

[0316] As an embodiment, the base station device supports intelligent functions.

[0317] As an embodiment, the base station device supports selection of an intelligent model.

[0318] As an embodiment, the base station device supports configuration of an intelligent model.

[0319] As an embodiment, the base station device supports configuration of connection failure prediction.

[0320] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0321] As an embodiment, the base station device supports transmission of a terrestrial network.

[0322] As an embodiment, the base station equipment includes a base transceiver station (Base Transceiver Station, BTS).

[0323] As an embodiment, the base station device includes a Node B (NodeB, NB); the Node B may be a gNB or an eNB or an ng-eNB or an en-gNB; the base station device may include a CU (Centralized Unit); the base station device may also include a DU (Distributed Unit); the base station device may also include a TRP (Transmitter Receiver Point).

[0324] As an embodiment, the base station device can be a macrocellular (Marco Cellular) base station or a microcell (Micro Cell) base station or a pico cell (Pico Cell) base station or a home base station (Femtocell); the base station device can also be a flight platform device or a satellite device; the base station device can also be a test device or a signaling tester; the base station device can also be a gateway device; the base station device can also be an IAB device; the IAB device includes at least one of IAB-node or IAB-donor or IAB-donor-CU or IAB-donor-DU or IAB-DU or IAB-MT.

[0325] As an embodiment, the relay device may include a relay; the relay may be an L3 relay or an L2 relay; the relay device may also include a router; the relay device may also include a switch; the relay device may also include a gateway device; the relay device may also include at least part of a user device; the relay device may also include at least part of a base station device.

[0326] Example 3

[0327] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture for the control plane 300 is shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY 301 in this article. Layer 2 (L2 layer) 305 is above PHY 301 and includes a MAC (Medium Access Control) sublayer 302, an 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 by encrypting data packets, and provides inter-zone mobility support. 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 (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a 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 of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). In the user plane 350, the radio protocol architecture is 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. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for mapping between QoS flows and data radio bearers (DRBs) to support service diversity.

[0328] As an example, Figure 3 The wireless protocol architecture in is applicable to the terminal described in this application.

[0329] As an example, Figure 3The wireless protocol architecture in is applicable to the base station described in this application.

[0330] As an embodiment, the first signaling in the present application is generated in the RRC306.

[0331] As an embodiment, the first signaling in the present application is generated by the MAC302 or MAC352.

[0332] As an embodiment, the first signaling in the present application is generated in the PHY301 or PHY351.

[0333] As an embodiment, the at least first reference signal in the present application is generated by the PHY301 or PHY351.

[0334] As an embodiment, the first notification is sent at a first designated protocol layer of the terminal.

[0335] As an embodiment, the second notification is sent at a first designated protocol layer of the terminal.

[0336] As an embodiment, the third notification is received at a first designated protocol layer of the terminal.

[0337] As an embodiment, the fourth notification is received at a first designated protocol layer of the terminal.

[0338] As an embodiment, the first specified protocol layer is the Figure 3 A protocol layer is shown.

[0339] As an embodiment, the first designated protocol layer is the RRC306.

[0340] As an embodiment, the first notification is received at a second designated protocol layer of the terminal.

[0341] As an embodiment, the second notification is received at a second designated protocol layer of the terminal.

[0342] As an embodiment, the third notification is sent at a second designated protocol layer of the terminal.

[0343] As an embodiment, the fourth notification is sent at a second designated protocol layer of the terminal.

[0344] As an embodiment, the second specified protocol layer is the Figure 3 A protocol layer is shown.

[0345] As an embodiment, the second specified protocol layer is the Figure 3 A protocol layer other than the one shown ( Figure 3 not included).

[0346] Example 4

[0347] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in the attached figure. Figure 4 shown. Figure 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.

[0348] 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.

[0349] The second communication 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 an antenna 420 .

[0350] In transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 layer. In transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of 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, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0351] In the transmission 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 corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves 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 the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the 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 may also be provided to L3 for L3 processing.

[0352] 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 the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission 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, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 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 symbol stream, and then provides it to the antenna 452.

[0353] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function 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 corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing 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 multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0354] As an embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 at least: receives a first signaling; wherein the first signaling indicates a first threshold; if the first statistic reaches the first threshold, determines that the connection has failed; wherein if the first statistic reaches a second threshold, performs a connection failure prediction; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0355] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: receiving a first signaling; wherein the first signaling indicates a first threshold; if the first statistic reaches the first threshold, determining that the connection has failed; wherein if the first statistic reaches a second threshold, performing a connection failure prediction; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0356] As an embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 410 at least: sends a first signaling; wherein the first signaling indicates a first threshold; if the first statistic reaches the first threshold, the receiver of the first signaling determines that the connection has failed; wherein if the first statistic reaches the second threshold, the receiver of the first signaling performs a connection failure prediction; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0357] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates an action when executed by at least one processor, and the action includes: sending a first signaling; wherein the first signaling indicates a first threshold; if the first statistic reaches the first threshold, the recipient of the first signaling determines that the connection has failed; wherein if the first statistic reaches the second threshold, the recipient of the first signaling performs a connection failure prediction; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0358] As an embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive the first signaling.

[0359] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send the first signaling.

[0360] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 is used to send at least a first reference signal.

[0361] As an embodiment, at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller / processor 475 is used to receive at least a first reference signal.

[0362] As an embodiment, the first communication device 450 corresponds to the terminal in this application.

[0363] As an embodiment, the second communication device 410 corresponds to the base station in this application.

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

[0365] As an embodiment, the first communication device 450 is a base station device.

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

[0367] As an embodiment, the first communication device 450 performs the connection failure prediction.

[0368] As an embodiment, optionally, the first communication device 450 includes the attached Fig.14 The smart module 1501 ( Figure 4 not included).

[0369] As an embodiment, optionally, the first communication device 450 includes the attached Fig.15 The third module in Figure 4 not included).

[0370] As an embodiment, optionally, the first communication device 450 includes the attached Fig.17 Reasoning function in 1806( Figure 4 not included).

[0371] As an embodiment, the second communication device 410 is a user equipment.

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

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

[0374] As an embodiment, optionally, the second communication device 410 assists in performing the connection failure prediction.

[0375] As an embodiment, optionally, the second communication device 410 includes the attached Fig.16 An inference function in Figure 4 not included).

[0376] As an embodiment, optionally, the second communication device 410 includes the attached Fig.17 Training function 1805 in the RAN domain Figure 4 not included).

[0377] Example 5

[0378] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0379] for Terminal U01In step S5101, a first signaling is received; wherein the first signaling indicates a first threshold; in step S5102, at least a first reference signal is received; in step S5103, whether the first statistic reaches a second threshold is determined; if the first statistic reaches the second threshold, step S5106 is executed, otherwise, step S5106 is not executed; in step S5104, when the first statistic reaches the second threshold, a first notification is sent; in step S5105, the first notification is received; wherein the first notification triggers the execution of connection failure prediction; in step S5106, connection failure prediction is executed; in step S5107, whether the first condition is satisfied; and In response to the first condition being met, execute step S5110, otherwise, do not execute step S5110; wherein, the first condition depends on at least one of measurement or prediction; in step S5108, when the first condition is met, send a second notification; in step S5109, receive the second notification; wherein, the second notification triggers the termination of the connection failure prediction; in step S5110, terminate the connection failure prediction; in step S5111, determine whether the first statistic reaches the first threshold; if the first statistic reaches the first threshold, execute step S5112, otherwise, do not execute step S5112; in step S5112, determine that the connection has failed.

[0380] for Base Station N02 In step S5201, a first signaling is sent; in step S5202, at least a first reference signal is sent.

[0381] In Embodiment 5, the first counter is a counter, or the first counter is a timer; and the first threshold value and the second threshold value are different.

[0382] As an embodiment, the base station N02 is the base station to which the service cell of the terminal U01 belongs.

[0383] As an embodiment, the base station N02 is the base station to which the PCell of the terminal U01 belongs.

[0384] As an embodiment, the base station N02 is the base station to which the PSCell of the terminal U01 belongs.

[0385] As an embodiment, the base station N02 is a MN (Master Node).

[0386] As an embodiment, the base station N02 is a SN (Secondary Node).

[0387] As an embodiment, the terminal U01 and the base station N02 are connected wirelessly.

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

[0389] As an embodiment, the terminal U01 and the base station N02 are connected via a Uu port.

[0390] As an embodiment, the terminal U01 and the base station N02 are connected via an IAB port.

[0391] As an embodiment, the terminal U01 and the base station N02 are connected via a PC5 interface.

[0392] As an embodiment, the first notification is an indication.

[0393] As an embodiment, the first notification is a notification.

[0394] As an embodiment, the first notification is a cross-layer indication.

[0395] As an embodiment, the first notification is a cross-entity indication.

[0396] As an embodiment, the first notification is within the terminal U01.

[0397] As an embodiment, the first notification is sent and received in the terminal U01.

[0398] As an embodiment, the first notification activates an intelligent model for predicting the connection failure.

[0399] As an embodiment, the first notification enables an intelligent model for the connection failure prediction.

[0400] As an embodiment, the first notification indicates parameters of the intelligent model used for the connection failure prediction.

[0401] As an embodiment, the parameters of the intelligent model for connection failure prediction include an identifier of the intelligent model for connection failure prediction.

[0402] As an embodiment, the parameters of the intelligent model for connection failure prediction include the type of the intelligent model for connection failure prediction.

[0403] As an embodiment, the parameters of the intelligent model for connection failure prediction include the current value of the first statistic.

[0404] As an embodiment, the first notification triggering the execution of the connection failure prediction means that: the first notification requests the execution of the connection failure prediction.

[0405] As an embodiment, the first notification triggering the execution of the connection failure prediction means that: the first notification indicates the execution of the connection failure prediction.

[0406] As an embodiment, the first notification triggering the execution of the connection failure prediction means: when the first notification is received, the connection failure prediction is executed.

[0407] As an embodiment, when the first condition is met, how the terminal U01 determines to terminate the connection failure prediction depends on UE implementation.

[0408] As an embodiment, when the first condition is met, how the terminal U01 notifies the smart module 1501 in Embodiment 14 depends on UE implementation.

[0409] As an embodiment, the suspension is stopping.

[0410] As an embodiment, the suspension is termination.

[0411] As an embodiment, the suspension is a pause.

[0412] As an embodiment, the suspension is a suspend.

[0413] As an embodiment, the first condition-dependent measurement means that the first condition depends on the first statistician.

[0414] As an embodiment, the first condition being dependent on the first statistic means that: the first condition includes that the first statistic does not reach the second threshold.

[0415] As an embodiment, the first condition being dependent on the first statistic means that: the first condition includes the first statistic reaching a third threshold.

[0416] As an embodiment, the third threshold is greater than the second threshold.

[0417] As an embodiment, the third threshold is smaller than the second threshold.

[0418] As an embodiment, the third threshold is the first threshold.

[0419] As an embodiment, the first conditional dependency prediction means that the first conditional dependency is used for an intelligent model for predicting the connection failure.

[0420] As an embodiment, the first condition being dependent on the intelligent model used for the connection failure prediction means that: the first condition includes that the intelligent model used for the connection failure prediction is updated.

[0421] As an embodiment, the first condition being dependent on the intelligent model used for the connection failure prediction means that: the first condition includes that the intelligent model used for the connection failure prediction is reconfigured.

[0422] As an embodiment, the first condition being dependent on the intelligent model used for the connection failure prediction means that: the first condition includes that the intelligent model used for the connection failure prediction is deactivated.

[0423] As an embodiment, the first condition-dependent measurement means that: the first condition includes considering that the MCG is detected to have a radio link failure.

[0424] As an embodiment, the first condition-dependent measurement means that: the first condition includes T310 being stopped.

[0425] As an embodiment, the first condition-dependent measurement means that the first condition includes T312 being stopped.

[0426] As an embodiment, the first condition-dependent measurement means that: the first condition includes switching failure.

[0427] As an embodiment, the first condition-dependent measurement means that the first condition includes T304 being stopped.

[0428] As an embodiment, the second notification is an indication.

[0429] As an embodiment, the second notification is a notification.

[0430] As an embodiment, the second notification is a cross-layer indication.

[0431] As an embodiment, the second notification is a cross-entity indication.

[0432] As an embodiment, the second notification is within the terminal U01.

[0433] As an embodiment, the second notification is sent and received in the terminal U01.

[0434] As an embodiment, the second notification deactivates the intelligent model used for the connection failure prediction.

[0435] As an embodiment, the second notification disables the intelligent model used for the connection failure prediction.

[0436] As an embodiment, the second notification indicates an identifier of an intelligent model used for the connection failure prediction.

[0437] As an embodiment, the second notification indicates the type of intelligent model used for the connection failure prediction.

[0438] As an embodiment, the second notification triggering the termination of the connection failure prediction means that the second notification requests the termination of the execution of the connection failure prediction.

[0439] As an embodiment, the second notification triggering the termination of the connection failure prediction means that the second notification instructs to terminate the execution of the connection failure prediction.

[0440] As an embodiment, the second notification triggering the termination of the connection failure prediction means: when the second notification is received, the connection failure prediction is terminated.

[0441] As an embodiment, along with the termination of the connection failure prediction, the intelligent model of the connection failure prediction is reset.

[0442] As an embodiment, along with the termination of the connection failure prediction, at least part of the information of the connection failure prediction is cleared.

[0443] As an embodiment, accompanying the termination of the connection failure prediction, at least a portion of the cache of the connection failure prediction is cleared.

[0444] As an embodiment, the above method avoids the impact on subsequent connection failure predictions.

[0445] As an embodiment, the receiving of at least a first reference signal includes: receiving the first reference signal at each available reception opportunity of each reference signal in the at least first reference signal.

[0446] As an embodiment, the receiving at least a first reference signal includes: receiving the first reference signal at at least one available reception opportunity of each reference signal in the at least first reference signal.

[0447] As an embodiment, an available reception opportunity of a reference signal is a time-frequency resource configured for the reference signal.

[0448] As an embodiment, an available reception opportunity for a reference signal is a time-frequency resource that is configured for the reference signal and does not overlap with a designated time-frequency resource.

[0449] As a sub-embodiment of the above embodiment, the designated time-frequency resources include an active measurement gap.

[0450] As a sub-embodiment of the above embodiment, the priority of transmission on the designated time-frequency resources is higher than that of the one reference signal.

[0451] As an embodiment, the sender of the at least first reference signal is the cell for which the connection failure prediction is targeted.

[0452] As an embodiment, the at least first reference signal is a physical layer signal.

[0453] As an embodiment, the at least first reference signal is a reference signal (Reference Signal).

[0454] As an embodiment, any reference signal among the at least first reference signals is used for connection failure prediction.

[0455] As an embodiment, any reference signal among the at least first reference signals is used for RLM (Radio Link Monitoring).

[0456] As an embodiment, any reference signal among the at least first reference signals is used for RLM and connection failure prediction.

[0457] As an embodiment, the at least first reference signal is of downlink (DL).

[0458] As an embodiment, the at least first reference signal is of a sidelink (Sidelink, SL).

[0459] As an embodiment, the at least first reference signal is periodic.

[0460] As an embodiment, the at least first reference signal is semi-continuous.

[0461] As an embodiment, the at least first reference signal includes a synchronization signal (SynchronizationSignal).

[0462] As an embodiment, each reference signal in the at least first reference signal is an SSB (Synchronization Signal Block, or SS / PBCH).

[0463] As an embodiment, the at least first reference signal is a synchronization signal (SynchronizationSignal).

[0464] As an embodiment, each reference signal in the at least first reference signal is a CSI-RS (Channel State Information Reference Signal).

[0465] As an embodiment, the at least first reference signal is indicated by RRC signaling.

[0466] As an embodiment, the at least first reference signal is determined by the terminal U01.

[0467] As an embodiment, the at least first reference signal is the first reference signal.

[0468] As an embodiment, the at least first reference signal is a plurality of reference signals; the plurality of reference signals include at least the first reference signal.

[0469] As an embodiment, the at least first reference signal does not exceed M1 reference signals; and M1 is a positive integer.

[0470] As an embodiment, the M1 relies on L in TS 38.213 max .

[0471] As an embodiment, the M1 is N in TS 38.213 RLM .

[0472] As an embodiment, M1 is 2 or 4 or 8.

[0473] As an embodiment, M1 is not greater than 8.

[0474] As an embodiment, M1 is not greater than 16.

[0475] As an embodiment, the connection failure prediction includes predicting a link quality for the at least first reference signal.

[0476] As an embodiment, the connection failure prediction includes predicting a synchronization indication; the synchronization indication depends on the at least first reference signal.

[0477] As an embodiment, the connection failure prediction includes predicting the number of synchronization indications; the synchronization indications depend on the at least first reference signal.

[0478] As an embodiment, the connection failure prediction includes predicting an out-of-sync indication; the out-of-sync indication depends on the at least first reference signal.

[0479] As an embodiment, the connection failure prediction includes predicting the number of out-of-sync indications; the out-of-sync indications depend on the at least first reference signal.

[0480] As an embodiment, the connection failure prediction depends on the at least first reference signal.

[0481] As an embodiment, the connection failure prediction relies on a measurement result of the at least first reference signal.

[0482] As an embodiment, the input of the intelligent model for connection failure prediction includes measurement results for the at least first reference signal.

[0483] As an embodiment, the reasoning of the intelligent model for connection failure prediction relies on the measurement results for the at least first reference signal.

[0484] As an embodiment, the measurement result for the at least first reference signal includes: at least one measurement value for the at least first reference signal.

[0485] As an embodiment, the measurement result for the at least first reference signal includes: at least one measurement value for each reference signal in the at least first reference signal.

[0486] As an embodiment, the at least one measurement value is only one measurement value.

[0487] As an embodiment, the at least one measurement value is a plurality of measurement values.

[0488] As an embodiment, the multiple measurement values ​​are obtained at different times.

[0489] As an embodiment, the multiple measurements are obtained at the same time.

[0490] As an embodiment, the measurement value is RSRP (Reference Signal Receiving Power).

[0491] As an embodiment, the measurement value is RSRQ (Reference Signal Receiving Power).

[0492] As an embodiment, the measurement value is SINR (Signal to Interference plus Noise Ratio).

[0493] As an embodiment, the dashed box F5.1 is optional.

[0494] As an embodiment, the dotted box F5.1 does not exist.

[0495] As an embodiment, the dashed box F5.1 exists.

[0496] As an embodiment, step S5107 is optional.

[0497] As an embodiment, step S5107 does not exist.

[0498] As an embodiment, step S5107 exists.

[0499] As an embodiment, the dashed box F5.2 is optional.

[0500] As an embodiment, the dotted box F5.2 depends on the step S5107.

[0501] As an embodiment, the dotted box F5.2 does not exist, and the step S5107 exists.

[0502] As an embodiment, when the dotted box F5.2 exists, the step S5107 exists.

[0503] As an embodiment, optionally, the terminal U01 sends the first UE capability information (the attached Figure 5 Not shown); wherein, the first UE capability information indicates that the terminal U01 supports connection failure prediction.

[0504] As an embodiment, the “if the first statistic reaches a second threshold, perform connection failure prediction” relies on the first UE capability information indicating that the terminal U01 supports connection failure prediction.

[0505] As an embodiment, under the premise that the first UE capability information indicates that the terminal U01 supports connection failure prediction, if the first statistic reaches a second threshold, connection failure prediction is performed.

[0506] As an embodiment, the first UE capability information includes an RRC message; the one RRC message indicates that the terminal U01 supports connection failure prediction.

[0507] As an embodiment, the first UE capability information includes an RRC message and a MAC CE; the one RRC message indicates multiple UE capabilities; and the one MAC CE indicates that the terminal U01 supports connection failure prediction from the multiple UE capabilities.

[0508] As an embodiment, the RRC message is a UECapabilityInformation message.

[0509] As an embodiment, the RRC message is a UEAssistanceInformation message.

[0510] As an embodiment, the first UE capability information indicates the parameters of at least one intelligent model supported by the terminal U01; optionally, the parameter may be an identifier of the intelligent model, a type of the intelligent model, a function of the intelligent model, etc.

[0511] As a sub-embodiment of the above embodiment, one of the at least one intelligent model supported by the terminal U01 is an intelligent model used for the connection failure prediction.

[0512] As an embodiment, the first UE capability information indicates that the terminal U01 supports connection failure prediction, and the connection failure prediction includes RLF prediction and HOF prediction.

[0513] As an embodiment, the first UE capability information indicates that the terminal U01 supports connection failure prediction, and the connection failure prediction is RLF prediction.

[0514] As an embodiment, the first UE capability information indicates that the terminal U01 supports connection failure prediction, and the connection failure prediction is HOF prediction.

[0515] As an embodiment, the first UE capability information indicates RLF prediction from RLF prediction and HOF prediction; and the connection failure prediction is RLF prediction.

[0516] As an embodiment, the first UE capability information indicates a HOF prediction from among an RLF prediction and a HOF prediction; and the connection failure prediction is a HOF prediction.

[0517] As an embodiment, the first UE capability information indicates both RLF prediction and HOF prediction from among RLF prediction and HOF prediction; and the connection failure prediction is RLF prediction and HOF prediction.

[0518] As an embodiment, optionally, the terminal U01 receives the second message (the attached Figure 5 ); wherein the second message enables the connection failure prediction.

[0519] As an embodiment, the “if the first statistic reaches a second threshold, perform connection failure prediction” enables the connection failure prediction depending on the second message.

[0520] As an embodiment, under the premise that the second message enables the connection failure prediction, if the first statistic reaches a second threshold, the connection failure prediction is performed.

[0521] As an embodiment, the second message indicates the parameters of at least one enabled intelligent model; optionally, the parameter may be an identifier of the intelligent model, a type of the intelligent model, a function of the intelligent model, etc.

[0522] As a sub-embodiment of the above embodiment, the second message indicates that one of the at least one intelligent models enabled is an intelligent model used for the connection failure prediction.

[0523] As an embodiment, the second message includes an RRC message; the one RRC message enables the connection failure prediction.

[0524] As an embodiment, the second message includes a MAC CE; the one MAC CE enables the connection failure prediction.

[0525] As an embodiment, the second message includes a DCI; the DCI enables the connection failure prediction.

[0526] As an embodiment, the enabling includes enable.

[0527] As an embodiment, the enabling includes activating.

[0528] As an embodiment, the enabling includes enabling.

[0529] As an embodiment, the enabling includes making effective.

[0530] As an embodiment, the enabling includes triggering.

[0531] Example 6

[0532] Embodiment 6 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in the attached Figure 6 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0533] for Terminal U01 In step S6101, a connection failure is predicted; in step S6102, as a response to the prediction of the connection failure, a second counter is operated; the second counter is a counter, or the second counter is a timer.

[0534] As an embodiment, the second counter is operated as long as a connection failure is predicted.

[0535] As an embodiment, if a connection failure is predicted, the second statistics monitor is operated.

[0536] As an embodiment, the second statistics monitor is operated on the premise that at least a connection failure is predicted.

[0537] As an embodiment, in response to predicting a connection failure, operating the second counter is independent of the predicted time of occurrence of the connection failure.

[0538] As an embodiment, the connection failure is predicted by the terminal U01 based on UE implementation.

[0539] As an embodiment, the connection failure is predicted by the terminal U01 based on protocol regulations.

[0540] As an embodiment, the connection failure is predicted by an intelligent model.

[0541] As an embodiment, the connection failure is predicted by an intelligent model for connection failure prediction.

[0542] As an embodiment, the predicting of connection failure refers to: predicting N310 consecutive out-of-sync indications; N310 is a positive integer.

[0543] As an embodiment, the prediction of connection failure refers to: predicting that the number of consecutive out-of-sync indications will reach N310; and N310 is a positive integer.

[0544] As an embodiment, the predicting of connection failure means: predicting that the number of consecutive out-of-sync indications within the first time window will reach N310; and N310 is a positive integer.

[0545] As an embodiment, the prediction of connection failure refers to: predicting that T310 will expire.

[0546] As an embodiment, the prediction of connection failure refers to: predicting that T312 will expire.

[0547] As an embodiment, the prediction of connection failure refers to: predicting that either T310 or T312 will expire.

[0548] As an embodiment, the predicting of connection failure means: predicting that a connection failure will occur.

[0549] As an embodiment, the predicting of the connection failure refers to: predicting that a first indicator of the connection failure will reach a first threshold.

[0550] As an embodiment, the first indicator includes: BLER (Block Error Rate).

[0551] As an embodiment, the first indicator includes: RSRP.

[0552] As an embodiment, the first indicator includes: RSRQ.

[0553] As an embodiment, the first indicator includes: probability.

[0554] As an embodiment, the first indicator includes: credibility.

[0555] As an embodiment, the response to the predicted connection failure refers to: when the predicted connection failure is predicted.

[0556] As an embodiment, the response to the predicted connection failure refers to: once the predicted connection failure is predicted.

[0557] As an embodiment, the response as a predicted connection failure refers to: at least after the predicted connection failure is predicted.

[0558] As an embodiment, the second counter is a counter.

[0559] As an embodiment, the second counter is a timer

[0560] As an embodiment, the second statistic is the first statistic.

[0561] As an embodiment, the second statistic is not the first statistic.

[0562] As an embodiment, the first statistician is not T310; the second statistician is T310.

[0563] As a sub-embodiment of the above embodiment, the first counter is T312.

[0564] As a sub-embodiment of the above embodiment, the first counter is T304.

[0565] As a sub-embodiment of the above embodiment, the first counter is T316.

[0566] As a sub-embodiment of the above embodiment, the first counter is a counter.

[0567] As an embodiment, the second statistician is N311.

[0568] As an embodiment, the second statistician is N310.

[0569] As an embodiment, the operating the second counter is stopping the second counter; the second counter is a timer.

[0570] As an embodiment, the operating the second counter is changing the value of the second counter; the second counter is a timer.

[0571] As a sub-embodiment of the above embodiment, the change is an increase.

[0572] As a sub-embodiment of the above embodiment, the change is a reduction.

[0573] As a sub-embodiment of the above embodiment, the value of the second statistic is changed according to RRC configuration.

[0574] As a sub-embodiment of the above embodiment, the value of the second statistic is changed according to the predicted relevant information of the connection failure.

[0575] As a sub-embodiment of the above embodiment, the changing the value of the second statistic means including changing the current value of the second statistic.

[0576] As a sub-embodiment of the above embodiment, the changing the value of the second statistic means including changing the value of the second statistic at the next startup.

[0577] As an embodiment, the operating the second statistic is resetting the second statistic; the second statistic is a counter.

[0578] As an embodiment, within the time interval between the predicted connection failure and the predicted occurrence time of the connection failure, even if N310 consecutive out-of-sync indications are received, the first statistic is not started; the operation of the second statistic is to stop the second statistic; the second statistic is the first statistic; the first statistic is T310.

[0579] As a sub-embodiment of the above embodiment, the meaning of stopping includes not continuing timing.

[0580] As a sub-embodiment of the above embodiment, the meaning of stopping includes continuing the timing.

[0581] Example 7

[0582] Embodiment 7 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in the attached Figure 7 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0583] for Terminal U01 In step S7101, connection failure is predicted; in step S7102, RRC connection reconstruction is initiated in response to the predicted connection failure.

[0584] As an embodiment, the meanings of the prediction of connection failure and the response to the prediction of connection failure refer to Embodiment 6 and are not described in detail here.

[0585] As an embodiment, as long as connection failure is predicted, RRC connection reestablishment is initiated.

[0586] As an embodiment, if connection failure is predicted, RRC connection reestablishment is initiated.

[0587] As an embodiment, RRC connection reconstruction is initiated on the premise that at least connection failure is predicted.

[0588] As an embodiment, initiating RRC connection reestablishment as a response to a predicted connection failure is independent of the time at which the predicted connection failure occurs.

[0589] As an embodiment, connection failure is determined after the prediction of connection failure and before the initiation of RRC connection reconstruction.

[0590] As an embodiment, the connection failure is not determined after the prediction of the connection failure and before the initiation of RRC connection reestablishment.

[0591] As an embodiment, no legitimate event that triggers the determination of connection failure is detected within a time interval between the prediction of the connection failure and the initiation of RRC connection reestablishment.

[0592] As an embodiment, the legal event that triggers the determination of connection failure includes: T310 of PCell expires.

[0593] As an embodiment, the legal event that triggers the determination of connection failure includes: T312 of PCell expires.

[0594] As an embodiment, the legal events that trigger the determination of connection failure include: receiving a random access (Random Access) problem indication from the MCG MAC and T300, T301, T304, T311, T316 and T319 are not running and the SDT (Small Data Transmission) process is not in progress.

[0595] As an embodiment, the legal event that triggers the determination of connection failure includes: reaching the maximum number of RLC retransmissions and the SDT process is no longer in progress.

[0596] As an embodiment, the legal event that triggers the determination of connection failure includes: receiving a continuous uplink LBT (Listen Before Talk) failure indication from MCG MAC.

[0597] As an embodiment, the legal event that triggers the determination of connection failure includes: T304 of MCG expires.

[0598] Example 8

[0599] Embodiment 8 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in the attached Figure 8 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0600] for Terminal U01 In step S8101, a connection failure is predicted; in step S8102, whether the predicted occurrence time of the connection failure is earlier than the first time is determined; if the predicted occurrence time of the connection failure is earlier than the first time, step S8103(a) is executed; otherwise, step S8103(b) is executed; in step S8103(a), RRC connection reconstruction is started; in step S8103(b), a second counter is operated.

[0601] In Embodiment 8, as a response to predicting a connection failure, whether to operate the second counter or to initiate RRC connection reconstruction depends on the predicted time of occurrence of the connection failure; the second counter is a counter, or the second counter is a timer.

[0602] As an embodiment, the meanings of predicting the connection failure, the predicting the connection failure, the operating the second statistics meter and the initiating the RRC connection reconstruction response are referred to in Embodiment 6 and will not be repeated here.

[0603] As an embodiment, the first time is the expiration time of the first timer.

[0604] As an embodiment, the first timer is the first statistic; the first statistic is a timer.

[0605] As an embodiment, the first time is an expiration time of the first counter.

[0606] As an embodiment, the first timer is not the first counter.

[0607] As an embodiment, the first timer is T310; and T310 is running.

[0608] As an embodiment, the first timer is T312; and T312 is running.

[0609] As an embodiment, the first timer is the smaller of T310 and T312; both T310 and T312 are running.

[0610] As an embodiment, the first time is the time after a specified time interval has passed since the time when the connection failure was predicted.

[0611] As an embodiment, the specified time interval is configurable.

[0612] As an embodiment, the designated time interval is indicated by an RRC message.

[0613] As an embodiment, the specified time interval is indicated by the related information of the predicted connection failure.

[0614] As an embodiment, in response to predicting a connection failure, the second statistics monitor is operated, or RRC connection reconstruction is initiated.

[0615] As an embodiment, if the predicted occurrence time of the connection failure is later than the first time, the second statistics meter is operated; if the predicted occurrence time of the connection failure is earlier than the first time, RRC connection reconstruction is initiated.

[0616] As an embodiment, if the predicted occurrence time of the connection failure is later than the first time, the second statistics monitor is operated along with the time when the connection failure is predicted.

[0617] As an embodiment, if the predicted occurrence time of the connection failure is earlier than the first time, RRC connection reconstruction is initiated at the time when the connection failure is predicted.

[0618] As an embodiment, if the predicted occurrence time of the connection failure is earlier than the first time, RRC connection reconstruction is initiated along with the predicted occurrence time of the connection failure.

[0619] As an embodiment, if the predicted occurrence time of the connection failure is the first time, the second statistics monitor is operated.

[0620] As an embodiment, if the predicted occurrence time of the connection failure is the first time, RRC connection reconstruction is initiated.

[0621] Example 9

[0622] Example 9 illustrates a schematic diagram of a first counter according to an embodiment of the present application, as shown in the attached figure. Fig. 9 As shown in the attached Fig. 9 In the figure, the horizontal axis represents the value of the first statistic; the difference between the second threshold and the initial value is not greater than the difference between the first threshold and the initial value.

[0623] As an embodiment, the initial value is greater than the second threshold, and the second threshold is greater than the first threshold.

[0624] As an embodiment, the initial value is smaller than the second threshold, and the second threshold is smaller than the first threshold.

[0625] As an embodiment, the initial value is 0; and the second threshold is not greater than the first threshold.

[0626] As an embodiment, the initial value is the maximum value of the first statistic; and the second threshold is not less than the first threshold.

[0627] As an embodiment, if the first statistic is reset, the first statistic starts again from the initial value.

[0628] As an embodiment, if the first counter is stopped, the first counter remains unchanged before starting or restarting.

[0629] As an embodiment, if the first counter is started, the first counter starts timing or counting.

[0630] As an embodiment, if the first counter is not started, the first counter does not perform timing or counting.

[0631] As an embodiment, whether the first threshold and the second threshold are equal is configurable.

[0632] As an embodiment, it is a default that the first threshold and the second threshold are not equal.

[0633] As an embodiment, the first threshold and the second threshold are equal.

[0634] As an embodiment, the above method reduces the impact on the existing connection failure detection mechanism.

[0635] As an embodiment, the first threshold and the second threshold are not equal.

[0636] As an embodiment, the above method avoids triggering connection failure prematurely.

[0637] Example 10

[0638] Embodiment 10 illustrates a schematic diagram of predicting a connection failure according to an embodiment of the present application, as shown in the attached Fig.10 As shown in the attached Fig.10 In the figure, the horizontal axis represents time, t10.1 is the start time of the first time window, t10.2 is the end time of the first time window, the solid one-way arrow represents the predicted synchronization indication, the dotted one-way arrow represents the predicted out-of-sync indication, and every other prediction indication period corresponds to a prediction evaluation opportunity.

[0639] In embodiment 10, the predicted connection failure depends on at least one of the number of predicted synchronization indications or the number of predicted out-of-sync indications within a first time window; the predicted synchronization indication or the predicted out-of-sync indication depends on at least the first reference signal.

[0640] As an embodiment, the predicted out-of-synchronization indication depends on a predicted link quality for the at least first reference signal.

[0641] As an embodiment, the predicted link quality is RSRP.

[0642] As an embodiment, the predicted link quality is RSRQ.

[0643] As an embodiment, the predicted link quality is BLER.

[0644] As an embodiment, the predicted link quality is filtered by L1 or L3.

[0645] As an embodiment, the predicted link quality is unfiltered.

[0646] As an embodiment, the predicted link quality is a new quantity.

[0647] As an embodiment, if the predicted link quality for each of the at least first reference signals within a predicted out-of-sync evaluation period is worse than a first predicted out-of-sync threshold, an out-of-sync indication is predicted.

[0648] As an embodiment, the first predicted out-of-sync threshold is Q configured by rlmInSyncOutOfSyncThreshold out .

[0649] As an embodiment, the first predicted out-of-sync threshold is not a Q configured by rlmInSyncOutOfSyncThreshold. out .

[0650] As an embodiment, the predicted synchronization indication depends on a predicted link quality for the at least first reference signal.

[0651] As an embodiment, if the predicted link quality of at least one of the at least first reference signals within a predicted synchronization evaluation period is better than a first predicted synchronization threshold, a synchronization indication is predicted.

[0652] As an embodiment, the first predicted synchronization threshold is Q configured by rlmInSyncOutOfSyncThreshold in .

[0653] As an embodiment, the first predicted synchronization threshold is not the Q configured by rlmInSyncOutOfSyncThreshold. in .

[0654] As an embodiment, the prediction evaluation opportunity is only for the purpose of clarity of description and may not exist in actual applications.

[0655] As an embodiment, at each prediction evaluation opportunity, there is a predicted synchronization indication or a predicted out-of-sync indication.

[0656] As an embodiment, at a prediction evaluation time, there may be neither a predicted synchronization indication nor a predicted out-of-sync indication.

[0657] As an embodiment, the length of the predicted synchronization evaluation period is equal to the length of the predicted desynchronization evaluation period.

[0658] As an embodiment, the length of the predicted synchronization evaluation period is not equal to the length of the predicted desynchronization evaluation period.

[0659] As an embodiment, the length of the predicted synchronization evaluation period is the length of the synchronization evaluation period.

[0660] As an embodiment, the length of the predicted synchronization evaluation period is not the length of the synchronization evaluation period.

[0661] As an embodiment, the length of the predicted indication period is equal to the length of the indication period.

[0662] As an embodiment, the length of the synchronization assessment period refers to T Evaluate_in_SSB .

[0663] As an embodiment, the length of the desynchronization assessment period refers to T Evaluate_out_SSB .

[0664] As an embodiment, the length of the synchronization evaluation period is equal to the length of the desynchronization evaluation period.

[0665] As an embodiment, the length of the synchronization evaluation period is not equal to the length of the desynchronization evaluation period.

[0666] As an embodiment, the above method may maintain the continuity of the predicted synchronization indication and / or the predicted out-of-synchronization indication based on the synchronization indication and / or the out-of-synchronization indication.

[0667] As an embodiment, the length of the predicted indication period is not equal to the length of the indication period.

[0668] As an embodiment, the above method is independent of the synchronization indication and / or the out-of-sync indication, making the prediction more flexible.

[0669] As an embodiment, this embodiment does not limit the position of the evaluation opportunity in the prediction indication period.

[0670] As an embodiment, the prediction evaluation timing is only for the purpose of clearly explaining that an evaluation is performed every other prediction indication period to determine whether there is a predicted out-of-sync indication or a predicted in-sync indication. In practical applications, no specific limitation is imposed.

[0671] As an embodiment, the prediction of the connection failure depends on the number of the predicted synchronization indications within a first time window.

[0672] As an embodiment, the absence of at least P2 consecutive predicted synchronization indications triggering the predicted connection failure within the first time window; P2 is a positive integer.

[0673] As an embodiment, the above method is simple to implement.

[0674] As an embodiment, the P2 is the difference between N311 and R2; and the R2 is the number of consecutive synchronization indications received at the time when the connection failure is predicted.

[0675] As an embodiment, P2 is smaller than N311.

[0676] As an embodiment, the above method uses P2 which is smaller than N311 to reduce the probability of predicting a connection failure.

[0677] As an embodiment, P2 is greater than N311.

[0678] As an embodiment, the above method provides a predicted fault tolerance using a P2 larger than N311.

[0679] As an embodiment, the P2 is N321.

[0680] As an embodiment, the predicted connection failure is triggered when the proportion of the predicted synchronization indications within the first time window is no higher than a threshold.

[0681] As a sub-embodiment of the above embodiment, the not higher than is less than.

[0682] As a sub-embodiment of the above embodiment, the not higher than is less than or equal to.

[0683] As a sub-embodiment of the above embodiment, the threshold is configurable.

[0684] As a sub-embodiment of the above embodiment, the threshold is a default one.

[0685] As a sub-embodiment of the above embodiment, the proportion of the predicted synchronization indications within the first time window refers to: the ratio of the number of the predicted synchronization indications within the first time window to the number of predicted indication cycles within the first time window.

[0686] As a sub-embodiment of the above embodiment, the proportion of the predicted synchronization indications within the first time window refers to: the ratio of the number of the predicted synchronization indications within the first time window to the number of the predicted out-of-sync indications within the first time window.

[0687] As an embodiment, the prediction of the connection failure depends on the number of the predicted out-of-sync indications within a first time window.

[0688] As an embodiment, the presence of at least P1 consecutive predicted out-of-sync indications within the first time window triggers the predicted connection failure; P1 is a positive integer.

[0689] As an embodiment, the P1 is smaller than N310.

[0690] As an embodiment, the above method uses P1 which is smaller than N310, which is beneficial for predicting connection failure earlier.

[0691] As an embodiment, P1 is greater than N310.

[0692] As an embodiment, the above method adopts P1 which is larger than N310 to avoid the influence of prediction error.

[0693] As an embodiment, the P1 is N310.

[0694] As an embodiment, the above method is simple to implement.

[0695] As an embodiment, the P1 is the difference between N310 and R1; and the R1 is the number of consecutive out-of-sync indications received at the time when the connection failure is predicted.

[0696] As an embodiment, the P1 is N320.

[0697] As an embodiment, the predicted connection failure is triggered when the proportion of the predicted out-of-sync indications within the first time window is not less than a threshold.

[0698] As a sub-embodiment of the above embodiment, the not less than is greater than.

[0699] As a sub-embodiment of the above embodiment, the not less than is greater than or equal to.

[0700] As a sub-embodiment of the above embodiment, the threshold is configurable.

[0701] As a sub-embodiment of the above embodiment, the threshold is a default one.

[0702] As a sub-embodiment of the above embodiment, the proportion of the predicted out-of-sync indications within the first time window refers to: the ratio of the number of the predicted out-of-sync indications within the first time window to the number of predicted indication cycles within the first time window.

[0703] As a sub-embodiment of the above embodiment, the proportion of the predicted out-of-sync indications within the first time window refers to: the ratio of the number of the predicted out-of-sync indications within the first time window to the number of the predicted synchronization indications within the first time window.

[0704] As an embodiment, the prediction of the connection failure depends on the predicted number of the synchronization indications and the predicted number of the out-of-sync indications within a first time window.

[0705] As an embodiment, the presence of at least P1 consecutive predicted out-of-sync indications within the second time window and the absence of at least P2 consecutive predicted synchronization indications within the first time window trigger the predicted connection failure; P1 is a positive integer; P2 is a positive integer; the start time of the first time window depends on the end time of the second time window.

[0706] As an embodiment, the first time window is implemented by a timer.

[0707] As an embodiment, the length of the first time window is indicated by the network.

[0708] As an embodiment, the length of the first time window is determined by the terminal.

[0709] As an embodiment, the first time window includes at least the P1 prediction indication periods.

[0710] As an embodiment, the length of the first time window is not less than (the P1-1) prediction indication periods.

[0711] As an embodiment, the length of the first time window is not less than (the P1-1) prediction indication periods and not greater than the P1 prediction indication period.

[0712] As an embodiment, the first time window includes at least the P2 prediction indication periods.

[0713] As an embodiment, the length of the first time window is not less than (the P2-1) prediction indication periods.

[0714] As an embodiment, the length of the first time window is not less than (the P2-1) prediction indication periods and not greater than the P2 prediction indication periods.

[0715] As an embodiment, the first time window includes at least (the P1 + the P2) prediction indication cycles.

[0716] As an embodiment, the first time window is not less than the remaining time of the first counter; the first counter is a timer.

[0717] As an embodiment, the first time window is the remaining time of the first counter; the first counter is a timer.

[0718] As an embodiment, the first time window is greater than the remaining time of the first counter; the first counter is a timer.

[0719] As an embodiment, the first time window includes the remaining time of the first statistic and at least one prediction indication period after the time when the first statistic expires; the first statistic is a timer.

[0720] As an embodiment, the length of the first time subwindow is equal to the value of T310.

[0721] As an embodiment, the first time subwindow is the predicted running time of T310.

[0722] As an embodiment, the P2 consecutive predicted synchronization indications correspond to P2 consecutive predicted synchronization evaluation periods.

[0723] As an embodiment, the P1 consecutive predicted out-of-step indications correspond to P1 consecutive predicted out-of-step evaluation periods.

[0724] Embodiment 11

[0725] Embodiment 11 illustrates a structural block diagram of a processing device used in a terminal according to an embodiment of the present application, as shown in the attached Fig.11 As shown in the attached Fig.11 In the embodiment, the processing device 1100 in the terminal includes a first receiver 1101 and a first processor 1102.

[0726] The first receiver 1101 receives a first signaling, wherein the first signaling indicates a first threshold; if the first statistic reaches the first threshold, it is determined that the connection fails.

[0727] In Embodiment 11, if the first statistic reaches a second threshold, connection failure prediction is performed; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0728] As an embodiment, the first processor 1102 determines that the connection fails if the first statistic reaches a first threshold.

[0729] As an embodiment, the first processor 1102 performs connection failure prediction if the first statistic reaches a second threshold.

[0730] As an embodiment, the first processor 1102 sends a first notification when the first statistic reaches the second threshold; receives the first notification; wherein the first notification triggers the execution of the connection failure prediction.

[0731] As an embodiment, the first processor 1102, in response to a first condition being satisfied, terminates the connection failure prediction; wherein the first condition depends on at least one of measurement or prediction.

[0732] As an embodiment, the first processor 1102 sends a second notification when the first condition is met; and receives the second notification; wherein the second notification triggers the termination of the connection failure prediction.

[0733] As an embodiment, the first processor 112 operates a second counter in response to predicting a connection failure; the second counter is a counter, or the second counter is a timer.

[0734] As an embodiment, the first processor 1102 initiates RRC connection reestablishment in response to predicting connection failure.

[0735] As an embodiment, the first processor 1102, as a response to predicting a connection failure, operates the second counter or initiates RRC connection reconstruction depending on the predicted time of occurrence of the connection failure; the second counter is a counter, or the second counter is a timer.

[0736] As an embodiment, the first receiver 1101 receives at least a first reference signal; wherein the connection failure prediction depends on the at least first reference signal.

[0737] As an embodiment, the prediction of the connection failure depends on at least one of the number of predicted synchronization indications or the number of predicted out-of-sync indications within a first time window; the predicted synchronization indication or the predicted out-of-sync indication depends on at least the first reference signal.

[0738] As an embodiment, the first processor 1102 includes a first transmitter.

[0739] As an embodiment, the first processor 1102 includes an attached Fig.15 The third module in; the third module executes the connection failure prediction.

[0740] As an embodiment, the first processor 1102 includes an attached Fig.14 The intelligent module 1501 in the embodiment of the present invention; the intelligent module 1501 executes the connection failure prediction.

[0741] As an embodiment, the first processor 1102 includes an attached Fig.17 The reasoning function 1806 in the connection failure prediction is performed by the reasoning function 1806.

[0742] As an embodiment, the first receiver 1102 includes the attached Figure 4 At least one of the antenna 452 or the receiver 454 or the multi-antenna receive processor 458 or the receive processor 456 or the controller / processor 459 or the memory 460 or the data source 467.

[0743] As an embodiment, the first receiver 1101 includes the attached Figure 4 At least an antenna 452 and a receiver 454.

[0744] As an embodiment, the first transmitter includes the attached Figure 4At least one of the antenna 452 or the transmitter 454 or the multi-antenna transmit processor 457 or the transmit processor 468 or the controller / processor 459 or the memory 460 or the data source 467.

[0745] As an embodiment, the first transmitter includes the attached Figure 4 At least antenna 452 and transmitter 454.

[0746] As an embodiment, the terminal includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the terminal to execute the method used in the terminal in the present application; the one or more processors and the memory include the first receiver and the first processor.

[0747] Example 12

[0748] Embodiment 12 illustrates a structural block diagram of a processing device used in a base station according to an embodiment of the present application, as shown in the attached figure. Fig.12 As shown in the attached Fig.12 In the example, the processing device 1200 in the base station includes a second transmitter 1201.

[0749] The second transmitter 1201 sends a first signaling, wherein the first signaling indicates a first threshold; if the first statistic reaches the first threshold, the receiver of the first signaling determines that the connection has failed.

[0750] In Embodiment 12, if the first statistic reaches a second threshold, the receiver of the first signaling performs connection failure prediction; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

[0751] As an embodiment, when the first statistic reaches a second threshold, the receiver of the first signaling sends a first notification; the receiver of the first signaling receives the first notification; wherein the first notification triggers the execution of the connection failure prediction.

[0752] As an embodiment, in response to a first condition being met, the receiver of the first signaling terminates the connection failure prediction; wherein the first condition depends on at least one of measurement or prediction.

[0753] As an embodiment, when the first condition is met, the receiver of the first signaling sends a second notification; the receiver of the first signaling receives the second notification; wherein the second notification triggers the termination of the connection failure prediction.

[0754] As an embodiment, in response to predicting a connection failure, the receiver of the first signaling operates a second statistic; the second statistic is a counter, or the second statistic is a timer.

[0755] As an embodiment, in response to predicting a connection failure, the recipient of the first signaling initiates RRC connection reestablishment.

[0756] As an embodiment, the second transmitter 1201 sends at least a first reference signal; wherein the connection failure prediction depends on the at least first reference signal.

[0757] As an embodiment, the first signaling indicates the second threshold.

[0758] As an embodiment, the first condition includes that the first statistic reaches a third threshold; and the first signaling indicates the third threshold.

[0759] As an embodiment, the processing device 1200 in the base station includes a second receiver.

[0760] As an embodiment, the processing device 1200 in the base station includes an attached Fig.15 The third module in.

[0761] As an embodiment, the processing device 1200 in the base station includes an attached Fig.17 Training function 1805 in the RAN domain.

[0762] As an embodiment, the processing device 1200 in the base station includes an attached Fig.17 The reasoning function in 1806.

[0763] As an embodiment, the processing device 1200 in the base station includes an attached Fig.16 An inference function, namely 1704 or 1706.

[0764] As an embodiment, the second transmitter 1201 includes the attached Figure 4 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.

[0765] As an embodiment, the second transmitter 1201 includes the attached Figure 4 At least antenna 420 and transmitter 418.

[0766] As an embodiment, the second receiver includes the attached Figure 4 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.

[0767] As an embodiment, the second receiver includes the attached Figure 4 At least an antenna 420 and a receiver 418.

[0768] As an embodiment, the base station includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the base station to execute the method described in the present application that is used in the base station; the one or more processors and the memory include the second transmitter 1201.

[0769] Embodiment 13

[0770] Embodiment 13 illustrates a flowchart of the first state according to an embodiment of the present application, as shown in the attached Fig.13 Example 13 illustrates a schematic diagram of an intelligent model according to an embodiment of the present application, as shown in the attached Fig.13 shown.

[0771] for Terminal U01 In step S1401, a connection failure is predicted; in step S1402, a first state is triggered as a response to the prediction of the connection failure; in step S1403, any condition in a first condition set is met; in step S1404, the triggered first state is canceled as a response to any condition in the first condition set being met.

[0772] As an embodiment, after being triggered, the first state remains pending until the first state is cancelled.

[0773] As an embodiment, the pending means being triggered and not cancelled.

[0774] As an embodiment, the pending refers to: pending.

[0775] As an embodiment, the pending refers to being set.

[0776] As an embodiment, pending refers to being stored.

[0777] As an embodiment, the dashed box 14.1 is optional.

[0778] As an embodiment, the dashed box 14.1 does not exist.

[0779] As a sub-embodiment of the above embodiment, any condition in the first condition set is not satisfied.

[0780] As a sub-embodiment of the above embodiment, the first state is not cancelled.

[0781] As an embodiment, the dashed box 14.1 exists.

[0782] As a sub-embodiment of the above embodiment, at least one condition in the first condition set is satisfied.

[0783] As a sub-embodiment of the above embodiment, the first state is cancelled.

[0784] As an embodiment, one of the conditions in the first condition set includes that the predicted connection failure is predicted to be eliminated.

[0785] As an embodiment, one of the conditions in the first set of conditions includes initiating a switching process.

[0786] As an embodiment, one of the conditions in the first condition set includes entering the RRC_INACTIVE state.

[0787] As an embodiment, one of the conditions in the first condition set includes entering the RRC_IDLE state.

[0788] As an embodiment, one of the conditions in the first set of conditions includes that the intelligent model is deactivated.

[0789] As an embodiment, one of the conditions in the first condition set includes that the intelligent model is deleted.

[0790] As an embodiment, one of the conditions in the first set of conditions includes that the intelligent model is reconfigured.

[0791] As an embodiment, one condition in the first condition set includes at least one of the predicted connection failure being predicted to be eliminated, or initiating a switching process, or initiating RRC connection reconstruction, or entering the RRC_INACTIVE state, or entering the RRC_IDLE state, or the intelligent model being deactivated, or the intelligent model being deleted, or the intelligent model being reconfigured.

[0792] As an embodiment, the cancelling refers to: cancel.

[0793] As an embodiment, the cancellation refers to: release.

[0794] As an embodiment, the cancelling refers to: deleting (Delete).

[0795] As an embodiment, the cancelling refers to clearing.

[0796] As an embodiment, the cancellation means: no longer storing.

[0797] Embodiment 14

[0798] Embodiment 14 illustrates a schematic diagram of the transmission of the first notification and the second notification according to an embodiment of the present application, as shown in the attached figure. Fig.14 As shown, the terminal 1500 includes an intelligent module 1501 and a legacy module 1502 .

[0799] In Example 14, the legal module 1502 of the terminal 1500 sends a first notification when the first counter reaches the second threshold; the intelligent module 1501 of the terminal 1500 receives the first notification; wherein the first notification triggers the execution of the connection failure prediction.

[0800] In Example 14, the legal module 1502 of the terminal 1500 sends a second notification when the first condition is met; the intelligent module 1501 of the terminal 1500 receives the second notification; wherein the second notification triggers the termination of the connection failure prediction.

[0801] As an embodiment, the intelligent module 1501 of the terminal 1500 sends a third notification when predicting a connection failure; the legal module 1502 of the terminal 1500 receives the third notification; wherein the third notification indicates the predicted connection failure.

[0802] As an embodiment, the intelligent module 1501 of the terminal 1500 sends a fourth notification; the legal module 1502 of the terminal 1500 receives the fourth notification; wherein the fourth notification indicates that the predicted connection failure is eliminated.

[0803] As a sub-embodiment of the above embodiment, the above method avoids triggering unreasonable UE behavior by updating prediction information.

[0804] As a sub-embodiment of the above embodiment, the above method is beneficial to UE decision-making.

[0805] As a sub-embodiment of the above embodiment, the predicted connection failure elimination means: predicting that the connection failure will not occur at the predicted occurrence time of the connection failure.

[0806] As an embodiment, as a response to the first notification being received, an indication is sent to a lower layer; and the indication is received at the RRC sublayer.

[0807] As an embodiment, as a response to the first notification being received, an indication is sent to an upper layer; and the indication is received at the RRC sublayer.

[0808] As an embodiment, the one indication indicates the first notification.

[0809] As an embodiment, the one indication includes the first notification.

[0810] As an embodiment, the legal module is logical.

[0811] As an embodiment, the legal module is physical.

[0812] As an embodiment, the legal module determines that the connection fails if the first statistic reaches a first threshold.

[0813] As an embodiment, the legal module receives at least a first reference signal.

[0814] As an embodiment, the legal module operates the first counter in response to predicting a connection failure.

[0815] As an embodiment, the legal module, in response to predicting a connection failure, initiates RRC connection reestablishment.

[0816] As an embodiment, the legal module is a protocol entity.

[0817] As an embodiment, the legal module is an RRC protocol entity.

[0818] As an embodiment, the legal module is in the RRC sublayer.

[0819] As an embodiment, the legal module is at a higher layer than the RRC sublayer.

[0820] As an embodiment, the legal module is at a lower layer of the RRC sublayer.

[0821] As an embodiment, the legal module supports 3GPP Release 17.

[0822] As an embodiment, the legal module supports 3GPP Release 18.

[0823] As an embodiment, the legal module does not have either a training function or a reasoning function.

[0824] As an embodiment, the legal module is not an intelligent module.

[0825] As an embodiment, the intelligent module is a hardware.

[0826] As an embodiment, the intelligent module is a software.

[0827] As an embodiment, the intelligent module is a program.

[0828] As an embodiment, the smart module is a function.

[0829] As an embodiment, the intelligent module is a protocol entity.

[0830] As an embodiment, the intelligent module is an AI entity.

[0831] As an embodiment, the intelligent module is an ML entity.

[0832] As an embodiment, the intelligent module is an AI / ML entity.

[0833] As an embodiment, the intelligent module is logical.

[0834] As an embodiment, the smart module is physical.

[0835] As an embodiment, the intelligent module performs connection failure prediction.

[0836] As an embodiment, the intelligent module processes the at least one intelligent model.

[0837] As an embodiment, the intelligent module includes at least one of the second module or the third module in the intelligent model shown in Embodiment 15.

[0838] As an embodiment, the interface between the legal module and the smart module is defined by the 3GPP protocol.

[0839] As an embodiment, the interface between the legal module and the intelligent module is implemented based on UE.

[0840] As an embodiment, the interface between the legal module and the intelligent module is logical.

[0841] As an embodiment, the interface between the legal module and the smart module is physical.

[0842] Embodiment 15

[0843] Embodiment 15 illustrates a schematic diagram of an intelligent model according to an embodiment of the present application, as shown in the attached Fig.15 Attached Fig.15 It includes a first module, a second module, a third module, a fourth module and a fifth module.

[0844] In Example 15, in the attached Fig.15 In the intelligent model shown, the first module sends a first data set to the second module, the first module sends a second data set to the third module, the first module sends a third data set to the fifth module, the fifth module sends a first type of parameter group to the second module, the fifth module sends a second type of parameter group to the third module, the fifth module sends a third type of parameter group to the fourth module, the second module sends a fourth type of parameter group to the fourth module, and the fourth module sends a fifth type of parameter group to the third module.

[0845] As an embodiment, the first module, the second module, the third module, the fourth module and the fifth module in an intelligent model all belong to the terminal.

[0846] The above method avoids air interface signaling interaction and shortens transmission delay.

[0847] As an embodiment, any module among the first module, the second module, the third module, the fourth module and the fifth module in an intelligent model does not belong to the terminal.

[0848] The above method reduces the hardware complexity of the terminal.

[0849] As an embodiment, at least one of the first module, the second module, the third module, the fourth module and the fifth module in an intelligent model belongs to the terminal; and at least one of the first module, the second module, the third module, the fourth module and the fifth module belongs to a network node.

[0850] The above method balances the hardware complexity and transmission delay of the terminal.

[0851] As an embodiment, the first module is used for data collection.

[0852] As an embodiment, the first module is responsible for data collection.

[0853] As an embodiment, the first module has a data collection function.

[0854] As an embodiment, the second module has a training function.

[0855] As an embodiment, the training function is used for model training (Model Training).

[0856] As an embodiment, the training function is responsible for model training.

[0857] As an embodiment, the training function has a model training function.

[0858] As an embodiment, the training function performs model training.

[0859] As an embodiment, the second module performs validation.

[0860] As an embodiment, the second module performs testing.

[0861] As an embodiment, the second module generates model performance metrics.

[0862] As an embodiment, the second module is responsible for data preparation.

[0863] As an embodiment, the data preparation includes at least one of data pre-processing, cleaning, formatting, or transformation.

[0864] As an embodiment, the third module has a reasoning function.

[0865] As an embodiment, the inference function is used for inference.

[0866] As an embodiment, the reasoning function is responsible for reasoning.

[0867] As an embodiment, the fourth module is used for model storage (Model Storage).

[0868] As an embodiment, the fourth module has a model storage (Model Storage) function.

[0869] As an embodiment, the fourth module is responsible for storing the trained model.

[0870] As an embodiment, the fourth module is responsible for storing the trained model that can be used to perform reasoning processing.

[0871] As an embodiment, the fifth module is used for management.

[0872] As an embodiment, the fifth module is responsible for management.

[0873] As an embodiment, the fifth module has a management function.

[0874] As an embodiment, the fifth module manages the intelligent model.

[0875] As an embodiment, the first data set is training data (Training Data).

[0876] As an embodiment, the first data set is an input of the second module.

[0877] As an embodiment, the second data set is inference data.

[0878] As an embodiment, the second data set is an input of the third module.

[0879] As an embodiment, the third data set is monitoring data.

[0880] As an embodiment, the third data set is the input of the fifth module.

[0881] As an embodiment, the first parameter group includes monitoring output.

[0882] As an embodiment, the second type of parameter group includes management instructions.

[0883] As an embodiment, the second type of parameter group is used for fine-tuning operation of the inference function.

[0884] As an embodiment, the second parameter group includes an identifier of the model.

[0885] As an embodiment, the second type of parameter group is used to select a model.

[0886] As an embodiment, the second type of parameter group is used for switching models.

[0887] As an embodiment, the second type of parameter group is used to activate / deactivate the model.

[0888] As an embodiment, the second type of parameter group is used to fallback to the intelligent model.

[0889] As an embodiment, the third type of parameter group includes a model transfer request (Model Transfer Request).

[0890] As an embodiment, the third parameter group includes a model delivery request (Model DeliveryRequest).

[0891] As an embodiment, the fourth parameter group includes a trained model (Trained Model).

[0892] As an embodiment, the fourth parameter group includes an updated model (Updated Model).

[0893] As an embodiment, the fourth type of parameter group indicates the identification of the model.

[0894] As an embodiment, the fifth parameter group includes model transfer.

[0895] As an embodiment, the fifth parameter group includes model delivery.

[0896] As an embodiment, the fifth type of parameter group indicates the identification of the model.

[0897] As an embodiment, the first type of output does not exist.

[0898] As an embodiment, the first type of output exists.

[0899] As an embodiment, the second module sends the first type of output to the fifth module.

[0900] As an embodiment, the first type of output includes a monitoring output.

[0901] As an embodiment, the second type of output does not exist.

[0902] As an embodiment, the second type of output exists.

[0903] As an embodiment, the third module sends the second type of output to the fifth module.

[0904] As an embodiment, the second type of output includes inference output.

[0905] As an embodiment, the second type of output is used by the fifth module to monitor the performance of the AI / ML model.

[0906] As an embodiment, the second type of output indicates the result of executing the connection failure prediction.

[0907] As an embodiment, the second type of output indicates the predicted connection failure.

[0908] As an embodiment, the second type of output includes relevant information of the predicted connection failure.

[0909] As an embodiment, the second type of output includes the third notification.

[0910] As an embodiment, the second type of output includes the fourth notification.

[0911] As an embodiment, the first data set in the intelligent model is configured by a network.

[0912] As an embodiment, the first data set in the intelligent model is determined by the terminal.

[0913] As an embodiment, the first data set in the intelligent model includes storage data of the terminal; the storage data may come from the network, from the log of the terminal, or from other RAN nodes.

[0914] As an embodiment, the first data set in the intelligent model includes measurement information of the terminal; the measurement information may be the mobile state of the terminal, such as the mobile speed, or the number of cells switched within a given time interval, etc.; the measurement information may also be measurement results for reference signals, such as cell-level measurement results, or beam-level measurement results, or time domain measurement results, or frequency domain measurement results, or spatial domain measurement results, or a combination thereof.

[0915] As an embodiment, the first data set in the intelligent model includes measurement results for the at least first reference signal.

[0916] As an embodiment, the second data set in the intelligent model is configured by a network.

[0917] As an embodiment, the second data set in the intelligent model is determined by the terminal.

[0918] As an embodiment, the second data set in the intelligent model includes storage data of the terminal; the storage data may come from the network, from the log of the terminal, or from other RAN nodes.

[0919] As an embodiment, the second data set in the intelligent model includes measurement information of the terminal; the measurement information may be the mobile state of the terminal, such as the mobile speed, or the number of cells switched within a given time interval, etc.; the measurement information may also be measurement results for reference signals, such as cell-level measurement results, or beam-level measurement results, or time domain measurement results, or frequency domain measurement results, or spatial domain measurement results, or a combination thereof.

[0920] As an embodiment, the second data set in the intelligent model includes measurement results for the at least first reference signal.

[0921] As an embodiment, the third data set in the intelligent model is configured by a network.

[0922] As an embodiment, the third data set in the intelligent model is determined by the terminal.

[0923] As an embodiment, the third data set in the intelligent model includes storage data of the terminal; the storage data may come from the network, from the log of the terminal, or from other RAN nodes.

[0924] As an embodiment, the third data set in the intelligent model includes measurement information of the terminal; the measurement information may be the mobile state of the terminal, such as the mobile speed, or the number of cells switched within a given time interval, etc.; the measurement information may also be the measurement result for the reference signal, such as the cell-level measurement result, or the beam-level measurement result, or the time domain measurement result, or the frequency domain measurement result, or the spatial domain measurement result, or a combination thereof.

[0925] As an embodiment, the third data set in the intelligent model includes measurement results for the at least first reference signal.

[0926] As an embodiment, connection failure prediction is performed by the intelligent model.

[0927] As an embodiment, the embodiment 15 is only used to illustrate that the present application can be used for intelligent models. The embodiment does not limit the application of the present application to non-intelligent operations, and the embodiment does not limit the application of the present application to other types of intelligent models to obtain and attach Fig.15 The smart model shown has comparable effects.

[0928] Example 16

[0929] Embodiment 16 illustrates a schematic diagram of intelligent function deployment of a RAN (Radio Access Network) domain according to an embodiment of the present application; Fig.16 As shown. The gNB in ​​Example 16 can be replaced by network equipment such as eNB or 6G base station.

[0930] The intelligent functions of the RAN domain include training (also called ML training, or AI training, or AI / ML training) functions, testing (also called ML testing, or AI testing, or AI / ML testing) functions, reasoning (also called ML reasoning, or AI reasoning, or AI / ML reasoning) functions, etc. The training function, the testing function, and the reasoning function can be deployed independently or co-located. The deployment of intelligent functions can be implemented through software, such as downloading and / or running executable files; it can also be implemented by combining software with hardware, such as accelerating specific computing units through hardware to increase computing speed or save power consumption.

[0931] For the training function, it can be deployed in a cross-domain management system or a domain-specific management system; the domain-specific management system is used to manage the RAN domain or the CN (Core Network) domain. For example, the training function for MDA (Management Data Analytics) can be deployed in MDAF (MDA function); the training for network data analysis can be deployed in NWDAF (Network Data Analytics Function), that is, the training function is MTLF (Model Training logical function).

[0932] The reasoning function can also be deployed in a cross-domain management system or a domain-specific management system; for example, the reasoning function is MDAF, or the reasoning function is AnLF (Analytics logical function) in NWDAF.

[0933] Similarly, testing capabilities can also be deployed in cross-domain management systems, or domain-specific management systems.

[0934] In Example 16, the training function 1702 of the RAN domain is located in the management function 1703 of the RAN domain; and the reasoning function is located in the base station, that is, the reasoning function 1704 is located in gNB1705, the reasoning function 1706 is located in gNB1707, and so on.

[0935] Attached Fig.16 In the example, the management of the reasoning functions of multiple base stations is completed by the RAN domain management function 1703, that is, data interaction with the RAN domain MnS (Management Service) consumer / cross-domain management 1701 (see the attached Fig.16 1708).

[0936] Optionally, the management of the reasoning function may also be completed by the base station itself, that is, each base station may independently perform data interaction with the RAN domain MnS consumer / cross-domain management 1701.

[0937] It should be noted that Example 16 is merely a non-restrictive implementation method; optionally, the training function of the RAN domain may also be deployed in the base station; or optionally, some base stations deploy the reasoning function and the training function of the RAN domain, while some base stations only deploy the reasoning function.

[0938] As an embodiment, a gNB (or base station) in Embodiment 16 is the base station described in the present application.

[0939] As an example, Fig.16 An inference function in performs connection failure prediction.

[0940] Embodiment 17

[0941] Embodiment 17 illustrates a schematic diagram of UE intelligent function deployment according to an embodiment of the present application; Fig.17 Attached Fig.17 The training function 1805 in the RAN domain is optional.

[0942] The UE intelligent function 1804 is deployed in the terminal of the present application, and the UE intelligent function 1804 includes a reasoning function 1806; the reasoning function 1806 uses an intelligent model (also called an AI model, or an ML model, or an AI / ML model) for reasoning; an intelligent model is usually trained before being used for AI / ML reasoning.

[0943] As an embodiment, the UE intelligent function 1804 includes a RAN domain training function 1805, and the RAN domain training function 1805 runs training data through an intelligent model to derive relevant losses, and adjusts the parameters of the intelligent model based on the calculated losses; the training includes at least one of ML initial training, ML re-training, and reinforcement learning.

[0944] The above embodiments can reduce the complexity of the base station, or save air interface resources caused by reporting training data; however, the above embodiments place high demands on the processing capability of the UE side.

[0945] Optionally, the UE intelligent function 1804 also includes a training function of the CN domain ( Fig.18 not included).

[0946] Optionally, the UE intelligent function 1804 further includes an intelligent deployment function: Fig.18 Not included, used to load intelligent models and data.

[0947] As an embodiment, the terminal indicates whether the training function (RAN domain or CN domain) is supported through capability reporting, and the capability reporting is RRC signaling, or NAS (Non-Access Stratum) signaling.

[0948] As an embodiment, the intelligent model and related metadata are loaded by the terminal from a network device or a remote server.

[0949] Optionally, the UE intelligent function 1804 is a MnS (Management Service) producer (Producer), providing data to the CN domain MnF (Management Function) 1801, and / or the RAN domain MnF1802, and / or the cross-domain management system 1803 for management or analysis (as shown by the double arrow 1507).

[0950] Optionally, the UE intelligent function 1804 is an MnS consumer (Consumer), which loads data from the CN domain MnF1801, and / or the RAN domain MnF1802, and / or the cross-domain management system 1803 for AI / ML-related management, such as management data requests, intelligent model activation, and / or intelligent model training, etc. (as shown by the double arrow 1807).

[0951] As an embodiment, the intelligent model is based on a neural network.

[0952] As an embodiment, the intelligent model is based on CNN (Conventional Neural Networks).

[0953] As an embodiment, the intelligent model is based on the Transformer architecture.

[0954] As an embodiment, the terminal in the present application includes an attached Fig.17 The reasoning function 1806 in.

[0955] As an embodiment, the first processor in the present application includes an attached Fig.17 The reasoning function 1806 in.

[0956] As an example, Figure 2 The UE 201 includes an attached Fig.17 The reasoning function 1806 in.

[0957] As an example, Figure 4 The first communication device 450 includes an attached Fig.17 The reasoning function 1806 in.

[0958] As an example, Fig.11 The first processor 1101 includes an attached Fig.17 The reasoning function 1806 in.

[0959] As an example, Fig.14 The smart module 1501 includes an attached Fig.17 The reasoning function 1806 in.

[0960] As an example, Fig.15 The third module includes the Fig.17 The reasoning function 1806 in.

[0961] As an example, Fig.17 The reasoning function 1806 in performs connection failure prediction.

[0962] Embodiment 18

[0963] Embodiment 18 illustrates a flowchart based on artificial intelligence or machine learning according to an embodiment of the present application; Fig.18 Attached Fig.18Including a third operation, a fourth operation, a fifth operation, a sixth operation and a seventh operation. In Example 18, the third operation and the fourth operation belong to the first stage, the fifth operation belongs to the second stage, the sixth operation belongs to the third stage, and the seventh operation belongs to the fourth stage. Fig.18 In the diagram, the lines with arrows indicate the sequence of the processes.

[0964] As an embodiment, the third operation includes AI / ML training, the fourth operation includes AI / ML testing, the fifth operation includes AI / ML emulation, the sixth operation includes AI / ML entity loading, and the seventh operation includes AI / ML inference.

[0965] As an embodiment, the first phase includes a training phase, the second phase includes an emulation phase, the third phase includes a deployment phase, and the fourth phase includes an inference phase.

[0966] As an embodiment, the first stage includes AI / ML model training.

[0967] As an embodiment, the first stage includes AI / ML model training and AI / ML testing.

[0968] As an embodiment, the AI / ML model training includes initial training and re-training of one or a group of AI / ML entities.

[0969] As an embodiment, the AI / ML model training relies on training data.

[0970] As an embodiment, the AI / ML model training includes AI / ML entity validation.

[0971] As an embodiment, the AI / ML entity verification is used to evaluate the performance of the AI / ML entity.

[0972] As an embodiment, the AI / ML entity verification relies on verification data.

[0973] As an example, if the result of AI / ML entity verification does not meet expectations, the AI / ML model will be retrained.

[0974] As an embodiment, the AI / ML testing includes testing the verified AI / ML entity to estimate the performance of the trained AI / ML model.

[0975] As an example, if the result of the AI / ML test meets expectations, the AI / ML entity proceeds to the next stage; otherwise the AI / ML model will be retrained.

[0976] As an embodiment, the AI / ML testing relies on test data.

[0977] As an embodiment, the second stage includes AI / ML simulation, which performs reasoning of AI / ML entities in a simulation environment.

[0978] As an embodiment, the AI / ML simulation estimates the performance of AI / ML entity reasoning in a simulation environment before using the AI / ML entity.

[0979] As an embodiment, the second stage is optional.

[0980] As an embodiment, the third stage includes AI / ML entity loading, and the AI / ML entity loading is to obtain the trained AI / ML entity to obtain the desired AI / ML reasoning function.

[0981] As an embodiment, the third stage is optional.

[0982] As an example, when the training function and the inference function are co-located, the third stage is no longer required.

[0983] As an embodiment, the fourth stage includes AI / ML reasoning.

[0984] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment 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 software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication, Machine Type Communication) terminals, eMTC (enhanced MTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system devices in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point) and other wireless communication devices.

[0985] The above is only a preferred embodiment of the present application and is not intended 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

1. A method used in a terminal, characterized in that: include: receiving a first signaling, wherein the first signaling indicates a first threshold; if the first counter reaches the first threshold, determining that the connection fails; If the first statistic reaches a second threshold, connection failure prediction is performed; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

2. The method according to claim 1, characterized in that The method comprises: When the first counter reaches the second threshold, sending a first notification; receiving the first notification; The first notification triggers the execution of the connection failure prediction.

3. The method according to claim 1 or 2, characterized in that: The method comprises: In response to the first condition being satisfied, aborting the connection failure prediction; The first condition depends on at least one of measurement or prediction.

4. The method according to claim 3, characterized in that The method comprises: When the first condition is met, sending a second notification; receiving the second notification; The second notification triggers the termination of the connection failure prediction.

5. The method according to any one of claims 1 to 4, characterized in that The method comprises: In response to predicting a connection failure, a second counter is operated; the second counter is a counter, or the second counter is a timer.

6. The method according to any one of claims 1 to 4, characterized in that The method comprises: In response to the predicted connection failure, an RRC connection reestablishment is initiated.

7. The method according to any one of claims 1 to 4, characterized in that The method comprises: In response to the predicted connection failure, whether to operate the second counter or initiate RRC connection reconstruction depends on the predicted time of occurrence of the connection failure; the second counter is a counter, or the second counter is a timer.

8. The method according to any one of claims 1 to 7, characterized in that The method comprises: receiving at least a first reference signal; Wherein, the connection failure prediction depends on the at least first reference signal.

9. The method according to claim 8, characterized in that The predicted connection failure depends on at least one of the number of predicted synchronization indications or the number of predicted out-of-sync indications within a first time window; the predicted synchronization indication or the predicted out-of-sync indication depends on at least the first reference signal.

10. A terminal, characterized in that: The terminal includes: one or more processors and a memory; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, where the computer program codes include computer instructions. The one or more processors call the computer instructions to enable the terminal to execute the method according to any one of claims 1 to 10.

11. A method used in a base station, characterized in that: include: Sending a first signaling; wherein the first signaling indicates a first threshold; if the first counter reaches the first threshold, the receiver of the first signaling determines that the connection has failed; If the first statistic reaches a second threshold, the receiver of the first signaling performs connection failure prediction; the first statistic is a counter, or the first statistic is a timer; the first threshold and the second threshold are different.

12. The method according to claim 11, characterized in that When the first statistic reaches the second threshold, the receiver of the first signaling sends a first notification; the receiver of the first signaling receives the first notification; wherein the first notification triggers the execution of the connection failure prediction.

13. The method according to claim 11 or 12, characterized in that: In response to a first condition being met, the receiver of the first signaling terminates the connection failure prediction; wherein the first condition depends on at least one of measurement or prediction.

14. The method according to claim 13, characterized in that When the first condition is met, the receiver of the first signaling sends a second notification; the receiver of the first signaling receives the second notification; wherein the second notification triggers the termination of the connection failure prediction.

15. The method according to any one of claims 11 to 14, characterized in that In response to predicting a connection failure, the receiver of the first signaling operates a second counter; the second counter is a counter, or the second counter is a timer.

16. The method for wireless communication according to any one of claims 11 to 14, characterized in that: In response to predicting the connection failure, the recipient of the first signaling initiates RRC connection reestablishment.

17. The method according to any one of claims 11 to 16, characterized in that sending at least a first reference signal; Wherein, the connection failure prediction depends on the at least first reference signal.

18. The method according to any one of claims 11 to 17, characterized in that The first signaling indicates the second threshold.

19. The method according to any one of claims 11 to 18, characterized in that The first condition includes that the first statistic reaches a third threshold; and the first signaling indicates the third threshold.

20. A base station, characterized in that: The base station includes: one or more processors and a memory; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, where the computer program codes include computer instructions, and the one or more processors call the computer instructions to enable the base station to perform the method according to any one of claims 11 to 21.

Images