Method and device used for wireless communication
By setting up information blocks containing connection type or identification after determining the wireless connection failure in the terminal, the problem of insufficient reporting of wireless link failure in the new air interface technology is solved, and the efficiency and accuracy of rapid recovery of MCG links is improved.
Patent Information
- Application Number
- CN202410979943.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-19
- Publication Date
- 2025-06-27
AI Technical Summary
In the new air interface technology, wireless link failure (RLF) remains one of the challenges faced by user equipment (UE), especially in the multi-path (MP) baseband link rapid recovery scenario, how to enhance RLF reporting has become a key technical issue.
After determining in the terminal that the wireless connection fails, the timer is started and the information block is set, which specifically includes: when the connection is SCG, the information block contains the identification of PSCell; when the connection is an indirect path, the information block contains the type or identification of the indirect path.
Improves the possibility of rapid recovery of MCG links, enhances the accuracy and completeness of RLF reports, simplifies follow-up operations, and reduces unnecessary delays.
Smart Images

Figure CN120224313A_ABST
Abstract
Description
Technical Field
[0001] This application relates to a transmission method and apparatus in a wireless communication system, and particularly to a method and apparatus for wireless connection failure. Background Art
[0002] The application scenarios of future wireless communication systems are becoming more and more diversified, and different application scenarios put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, it was decided at the 72nd plenary session of 3GPP (3rd Generation Partner Project) Radio Access Network (RAN) to conduct research on the New Radio (NR) (or 5G) new air interface technology. At the 75th plenary session of 3GPP RAN, the NR Work Item (WI) agenda was adopted, and the standardization work of NR began.
[0003] In the new air interface technology, Radio Link Failure (RLF) is still one of the challenges that User Equipment (UE) needs to face. In the prior art, once the UE experiences a radio link failure, the UE can report an RLF report to optimize the network coverage and improve the mobility robustness to reduce the impact of RLF.
[0004] Typically, the UE stores the information related to the latest RLF or handover failure (HOF), and indicates the availability of the RLF report during each subsequent radio resource control (RRC) connection re - establishment and cell handover, until the network obtains the RLF report or discards it 48 hours after the RLF.
[0005] In order to be able to adapt to diverse application scenarios and meet different requirements, 3GPP has been evolving the radio link failure technology. Summary of the Invention
[0006] In the 3GPP Release 16 version, after the Radio Link Failure (RLF) of the Master Cell Group (MCG), the MCG link can be restored through the Secondary Cell Group (SCG), supporting Fast MCG Link Recovery. In addition, when the Radio Link Failure (RLF) occurs to the User Equipment (UE), the radio link can also be restored through Conditional Handover (CHO). The applicant found through research that R18 supports fast MCG link recovery based on multi-path (MP). For fast MCG link recovery based on MP, how to enhance the RLF report has become one of the key technical issues.
[0007] In view of the above problems, this application provides a solution. In the above problem description, the Terrestrial Network (TN) scenario is taken as an example; this application is also applicable to scenarios such as non-terrestrial transmission, achieving technical effects similar to those in the Non-Terrestrial Network (NTN) scenario. In addition, adopting a unified solution for different scenarios helps to reduce the hardware complexity and cost.
[0008] It should be noted that, without conflict, the embodiments and features in any node of this application can be applied to any other node. Without conflict, the embodiments and features in the embodiments of this application can be combined with each other arbitrarily.
[0009] As an embodiment, the interpretation of the terms in this application refers to the definitions in the 3GPP specification protocol TS38 series.
[0010] As an embodiment, the interpretation of the terms in this application refers to the definitions in the 3GPP specification protocol TS36 series.
[0011] This application discloses a method applied to a terminal, including:
[0012] Determine that a radio connection fails;
[0013] In response to the determination that the radio connection fails, send a first message through a first connection and start a first timer; wherein, the first message indicates the radio connection failure; the first timer is configured;
[0014] Accompanying the first timer, set a first information block in a first variable; wherein, the first variable includes connection failure information;
[0015] Among them, the first information block depends on whether the first connection is an SCG or a non-direct path;
[0016] The first information block depending on whether the first connection is an SCG or a non-direct path includes:
[0017] When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0018] As an embodiment, in the above method, when the first connection is the non-direct path, the first information block does not include the first field.
[0019] As an embodiment, the first information block set by the above method can depend on an SCG or a non-direct path, increasing the technical means for recovering the MCG link, which is beneficial to improving the possibility of quickly recovering the MCG link.
[0020] As an embodiment, the first information block set by the above method depends on whether the first connection is an SCG or a non-direct path, fully considering the differences of different recovery paths, which is beneficial to reporting more information.
[0021] As an embodiment, the above method clarifies that when the first connection is the SCG, the first field is set to the identifier of the PSCell, which is beneficial to accurately obtaining the path information for quickly recovering the MCG link.
[0022] As an embodiment, the above method avoids the judgment error caused by unclear path adopted for quickly recovering the MCG link, which is beneficial to simplifying subsequent operations.
[0023] As an embodiment, the above method starts the first timer in a timely manner, which is beneficial to reducing unnecessary delay.
[0024] As an embodiment, the determination of wireless connection failure means: detecting MCG RLF.
[0025] As an embodiment, the determination of wireless connection failure means: considering that MCG is detected with RLF.
[0026] As an embodiment, the non-direct path is a sidelink (SL).
[0027] As an embodiment, the non-direct path is an N3C (Non-3GPP Connection).
[0028] As an embodiment, the non-direct path is either a sidelink or an N3C.
[0029] As an example, the first information block includes an elapsedTimeT316 field, and the elapsedTimeT316 field is set to the value of the elapsed time of the first timer.
[0030] As an example, the first message includes a FailureReportMCG field; the first timer is T316.
[0031] As an example, the first message includes an MCGFailureInformation message; the first timer is T316.
[0032] As an example, the first message is an MCGFailureInformation message ULInformationTransferMRDC message; the first timer is T316.
[0033] As an example, the first message is an MCGFailureInformation message; the first timer is T316.
[0034] As an example, the first variable is VarRLF-Report.
[0035] As an example, the wireless connection failure is a Radio Link Failure (RLF).
[0036] As an example, the first field is pSCellId, and the identifier of the PSCell is the global cell identity of the PSCell.
[0037] As an example, the first field is pSCellId, and the identifier of the PSCell is the physical cell identity and carrier frequency of the PSCell.
[0038] Specifically, according to one aspect of the present application, the accompaniment of the first timer includes: the expiration of the first timer.
[0039] As an example, the accompaniment of the first timer means: in response to the expiration of the first timer.
[0040] As an example, the accompaniment of the first timer means: when the first timer expires.
[0041] As an example, "accompanying the first timer" means: after the expiration of the first timer.
[0042] As an example, the above method further clarifies the time when the terminal sets the first information block, which is beneficial to determining the first connection on which the first information block depends, and further improves the accuracy of the first variable.
[0043] As an example, in response to the expiration of the first timer, the first information block does not include an elapsedTimeT316 field.
[0044] As an example, the method takes into account that the current protocol can implicitly indicate the expiration of the first timer, reducing signaling overhead.
[0045] As an example, in response to the expiration of the first timer, the first information block includes an elapsedTimeT316 field, and the elapsedTimeT316 field is set to the value of T316.
[0046] As an example, the method takes into account that it is beneficial to optimize the configuration of T316.
[0047] As an example, in response to the expiration of the first timer, the first information block includes the value of T316.
[0048] Specifically, according to one aspect of the present application, the method includes:
[0049] Receiving a second message;
[0050] In response to the reception of the second message, stopping the first timer;
[0051] Wherein, when the second message is received, the first timer is running; "accompanying the first timer" includes: stopping the first timer.
[0052] As an example, the method further clarifies the time to stop the first timer, which is beneficial to reducing the operating energy consumption of the terminal.
[0053] As an example, the method further clarifies the meaning of "accompanying the first timer", which is beneficial for the terminal to more accurately set the running time of the first timer.
[0054] As an example, in response to the reception of the second message, the first information block includes an elapsedTimeT316 field, and the elapsedTimeT316 field is set to the value of the elapsed time of the first timer.
[0055] As an embodiment, the second message includes an RRCReconfiguration message with reconfigurationwithSync for the PCell.
[0056] As an embodiment, the second message includes an RRCRelease message.
[0057] As an embodiment, the second message includes a MobilityFromNRCommand message.
[0058] As an embodiment, the second message includes any one of an RRCReconfiguration message with reconfigurationwithSync for the PCell, an RRCRelease message, or a MobilityFromNRCommand message.
[0059] As an embodiment, the second message is a ULInformationTransferMRDC message.
[0060] As an embodiment, the second message is an RRCReconfiguration message with reconfigurationwithSync for the PCell.
[0061] As an embodiment, the second message is an RRCRelease message.
[0062] As an embodiment, the second message is a MobilityFromNRCommand message.
[0063] As an embodiment, the second message is any one of an RRCReconfiguration message with reconfigurationwithSync for the PCell, an RRCRelease message, or a MobilityFromNRCommand message.
[0064] As an embodiment, accompanying the first timer means: as a response to the reception of the second message.
[0065] As an embodiment, accompanying the first timer means: when the first timer is stopped.
[0066] As an embodiment, accompanying the first timer means: as a response to the stopping of the first timer.
[0067] As an example, "accompanying the first timer" means: immediately following the stopping of the first timer.
[0068] As an example, "accompanying the first timer" means: after the stopping of the first timer.
[0069] Specifically, according to one aspect of the present application,
[0070] Whether the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0071] When the first connection is the non-direct path, the first information block includes a second field, and the second field indicates the non-direct path.
[0072] As an example, the method is beneficial to network optimization by increasing the information reporting of the non-direct path.
[0073] As an example, in response to receiving the second message, when the first connection is the non-direct path, the first information block includes an elapsedTimeT316 field, and the elapsedTimeT316 field is set to the value of the elapsed time of the first timer.
[0074] As an example, the above method is beneficial to optimizing the configuration of the first timer.
[0075] As an example, in response to receiving the second message, when the first connection is the non-direct path, the first information block does not include the elapsedTimeT316 field.
[0076] As an example, the above method takes into account the inaccuracy of the elapsed time of the first timer caused by the uncertainty of the non-direct path.
[0077] As an example, the above method reduces the information reporting that is not conducive to network optimization and reduces the signaling overhead.
[0078] Specifically, according to one aspect of the present application, the second field indicates the type of the non-direct path.
[0079] As an example, the method sets the type of the non-direct path, which is beneficial for the device to determine the non-direct path and simplifies the path determination process.
[0080] As an example, whether the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0081] When the first connection is the non-direct path and the non-direct path is a secondary link, the first information block includes a second field that indicates that the type of the non-direct path is a secondary link;
[0082] When the first connection is the non-direct path and the non-direct path is N3C, the first information block includes a second field that indicates that the type of the non-direct path is N3C.
[0083] As an embodiment, the second field indicates that the type of the non-direct path is a secondary link; wherein, the non-direct path is a secondary link.
[0084] As an embodiment, the second field indicates that the type of the non-direct path is N3C; wherein, the non-direct path is N3C.
[0085] As a sub-embodiment of the above embodiment, the second field indicates the type of the N3C.
[0086] As a sub-embodiment of the above embodiment, the second field indicates that the type of the N3C is WLAN.
[0087] As a sub-embodiment of the above embodiment, the second field indicates that the type of the N3C is WiFi.
[0088] As an embodiment, candidates for the type of the non-direct path include a secondary link.
[0089] As an embodiment, candidates for the type of the non-direct path include N3C.
[0090] As an embodiment, candidates for the type of the non-direct path include a secondary link and N3C.
[0091] Specifically, according to one aspect of the present application, the second field indicates the identifier of the non-direct path.
[0092] As an embodiment, the non-direct path is N3C.
[0093] As an embodiment, the identifier of the non-direct path is the physical identifier of N3C.
[0094] As an embodiment, the identifier of the non-direct path is the virtual identifier of N3C.
[0095] As an embodiment, the identifier of the non-direct path is the network identifier of N3C.
[0096] As an embodiment, the identifier of the non-direct path is the device identifier of N3C.
[0097] As an embodiment, the identification of the non-direct path is the interface identification of N3C.
[0098] The above method helps the nodes on both sides of the communication to keep the determination of the current path synchronized.
[0099] Specifically, according to one aspect of the present application, the dependence of the first information block on whether the first connection is an SCG or a non-direct path includes:
[0100] When the first connection is the non-direct path, the first information block does not include the first domain and the first information block does not include any domain indicating the non-direct path.
[0101] As an embodiment, the above method defines that when the first connection adopts the non-direct path, the first information block does not include the first domain, which helps to save radio interface resources.
[0102] As an embodiment, the dependence of the first information block on whether the first connection is an SCG or a non-direct path includes:
[0103] When the first connection is the SCG, the first information block includes a first domain, and the first domain is set as the identification of the PSCell; the PSCell belongs to the SCG;
[0104] When the first connection is the non-direct path, the first information block does not include the first domain and the first information block does not include any domain indicating the non-direct path.
[0105] As an embodiment, only when the first connection is the SCG, the first information block includes a first domain, and the first domain is set as the identification of the PSCell; the PSCell belongs to the SCG.
[0106] Specifically, according to one aspect of the present application, the terminal supports the RLF report for the fast MCG recovery process.
[0107] As an embodiment, the above method clarifies the characteristics of the terminal, the user equipment capabilities of the terminal.
[0108] As an embodiment, the terminal supports the RLF report for the fast MCG recovery process through the SCG.
[0109] As an embodiment, the terminal supports the RLF report for the fast MCG recovery process through the non-direct path.
[0110] As an example, on the premise that the terminal supports RLF reporting for the fast MCG recovery process, the first information block depends on whether the first connection is an SCG or a non-direct path.
[0111] As an example, if the terminal supports RLF reporting for the fast MCG recovery process, the first information block depends on whether the first connection is an SCG or a non-direct path.
[0112] As an example, if the terminal does not support RLF reporting for the fast MCG recovery process, clear the information included in the first variable.
[0113] Specifically, according to one aspect of the present application, the method includes:
[0114] Send a third message;
[0115] Wherein, the third message includes at least part of the information in the first information block.
[0116] As an example, the third message includes part of the information in the first information block.
[0117] As an example, the third message includes all of the information in the first information block.
[0118] As an example, sending at least part of the information in the first information block through the third message is beneficial to compatibility with existing protocols and realizes smooth evolution of technologies.
[0119] As an example, a UEInformationRequest message triggers the third message; wherein, the UEInformationRequest message includes an rlf-ReportReq field, and the rlf-ReportReq field is set to true; the third message is a UEInformationResponse message.
[0120] As an example, the third message is a UEAssistanceInformation message.
[0121] As an example, the third message is an RRCResumeRequest message.
[0122] As an example, the third message is an RRCReestablishmentRequest message.
[0123] The present application discloses a terminal, which includes: one or more processors and a memory;
[0124] The memory is coupled to the one or more processors, and the memory is configured to store computer program code including computer instructions, and the one or more processors invoke the computer instructions to cause the terminal to execute the above method.
[0125] To solve the above technical problem, the present application discloses a method used in a base station, including:
[0126] Receiving a third message; wherein, as a response to determining a radio connection failure by the sender of the third message, the sender of the third message sends a first message through a first connection and starts a first timer; along with the first timer, the sender of the third message sets a first information block in a first variable;
[0127] Wherein, the third message includes at least part of the information in the first information block; the first message indicates the radio connection failure; the first information block depends on whether the first connection is an SCG or a non-direct path; wherein, the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0128] When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0129] As an embodiment, the base station receives the first message.
[0130] Specifically, according to one aspect of the present application, the accompanying the first timer includes: the first timer expires.
[0131] Specifically, according to one aspect of the present application, the sender of the third message receives a second message; as a response to receiving the second message, the sender of the third message stops the first timer; wherein, when the second message is received, the first timer is running; the accompanying the first timer includes: stopping the first timer.
[0132] As an embodiment, the base station sends the second message.
[0133] Specifically, according to one aspect of the present application, the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0134] When the first connection is the non-direct path, the first information block includes a second field, and the second field indicates the non-direct path.
[0135] Specifically, according to one aspect of the present application, the second field indicates the type of the non-direct path.
[0136] Specifically, according to one aspect of the present application, the second field indicates the identification of the non-direct path.
[0137] Specifically, according to one aspect of the present application, the dependence of the first information block on whether the first connection is an SCG or a non-direct path includes:
[0138] When the first connection is the non-direct path, the first information block does not include the first field and the first information block does not include any field indicating the non-direct path.
[0139] Specifically, according to one aspect of the present application, the sender of the third message supports the fast MCG recovery process.
[0140] The present application discloses a base station, which includes: one or more processors and a memory;
[0141] The memory is coupled to the one or more processors, and 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 cause the base station to execute the method described above.
[0142] The present application discloses a terminal, including:
[0143] A first processor, which determines a wireless connection failure;
[0144] A first transmitter, in response to the determination of the wireless connection failure, sends a first message through a first connection and starts a first timer; wherein, the first message indicates the wireless connection failure; the first timer is configured;
[0145] The first processor, along with the first timer, sets a first information block in a first variable; wherein, the first variable includes connection failure information;
[0146] Wherein, the first information block depends on whether the first connection is an SCG or a non-direct path;
[0147] The dependence of the first information block on whether the first connection is an SCG or a non-direct path includes:
[0148] When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identification of the PSCell; the PSCell belongs to the SCG.
[0149] The present application discloses a base station, including:
[0150] A first receiver that receives a third message; wherein, as a response to determining a wireless connection failure by the sender of the third message, the sender of the third message sends a first message through a first connection and starts a first timer; along with the first timer, the sender of the third message sets a first information block in a first variable;
[0151] Wherein, the third message includes at least part of the information in the first information block; the first message indicates the wireless connection failure; the first information block depends on whether the first connection is an SCG or a non-direct path; wherein, the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0152] When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0153] As an embodiment, compared with the traditional solution, the present application has the following advantages:
[0154] The technical means for recovering the MCG link are increased, which is beneficial to improving the possibility of rapid recovery of the MCG link.
[0155] The differences between different recovery paths are fully considered, which is beneficial to reporting more information.
[0156] It is beneficial to accurately obtain the path information for rapid recovery of the MCG link.
[0157] It is beneficial to reduce unnecessary latency.
[0158] It is beneficial to simplify subsequent operations. Brief Description of the Drawings
[0159] By reading the detailed description of the non-restrictive embodiments with reference to the following drawings, other features, objects and advantages of the present application will become more apparent:
[0160] Figure 1 Shows a flowchart of a method used in a terminal according to an embodiment of the present application;
[0161] Figure 2 Shows a schematic diagram of a network architecture according to an embodiment of the present application;
[0162] Figure 3 Shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;
[0163] Figure 4 Shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;
[0164] Figure 5 Shows a transmission flowchart between a terminal N1 and a base station N2 according to an embodiment of the present application;
[0165] Figure 6 Shows a transmission flowchart between a terminal N1 and a base station N2 according to another embodiment of the present application;
[0166] Figure 7 Shows a flowchart for setting a first information block according to an embodiment of the present application;
[0167] Figure 8 Shows a transmission flowchart between a terminal N1 and a second node N2 and a third node N3 according to an embodiment of the present application;
[0168] Figure 9 Shows a transmission flowchart between a terminal N1 and a second node N2 and a third node N3 according to yet another embodiment of the present application;
[0169] Figure 10 Shows a flowchart of a method used in a base station according to an embodiment of the present application;
[0170] Figure 11 Shows a structural block of a processing device used in a terminal according to an embodiment of the present application;
[0171] Figure 12 Shows a structural block diagram of a processing device used in a base station according to an embodiment of the present application. Detailed implementation manners
[0172] The technical solutions of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, without conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily. Based on considerations such as performance, flexibility, complexity, overhead, and compatibility, those skilled in the art have the motivation to flexibly combine the embodiments in different drawings on the premise of non - contradiction.
[0173] Example 1
[0174] Embodiment 1 exemplifies a flowchart of a method used in a terminal according to an embodiment of the present application, as shown in the accompanying Figure 1 drawing. In the accompanying Figure 1 drawing, the terminal 100 is a terminal applicable to the method, or a terminal device. Each box represents a step. It should be particularly emphasized that the order of the boxes in the figure does not represent the chronological order between the represented steps.
[0175] In Embodiment 1, the terminal 100 determines that a wireless connection fails in step S101; in response to determining the wireless connection failure in step S102, a first message is sent via a first connection and a first timer is started; wherein, the first message indicates the wireless connection failure; the first timer is configured; in step S103, along with the first timer, a first information block is set in a first variable; wherein, the first variable includes connection failure information.
[0176] In Embodiment 1, the first information block depends on whether the first connection is an SCG or a non-direct path; that the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0177] When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0178] Typically, the terminal 100 is a UE.
[0179] As an embodiment, the terminal 100 is configured with split SRB1 (Signaling Radio Bearer 1).
[0180] As an embodiment, the terminal 100 is configured with SRB3 (Signaling Radio Bearer 3).
[0181] As an embodiment, the terminal 100 can maintain connections with multiple cells through dual connectivity. For example, the terminal 100 maintains connections with a first serving cell and a second serving cell through dual connectivity (not shown in the figure).
[0182] In one implementation, the dual connectivity includes MR-DC (Multi-Radio Dual Connectivity).
[0183] In one implementation, the dual connectivity includes NR DC (NR-NR Dual Connectivity). In one implementation, the dual connectivity includes Intra-E-UTRA DC.
[0184] In one implementation, the dual connectivity includes NE-DC (NR-E-UTRA Dual Connectivity).
[0185] In one implementation, the dual connectivity includes NGEN-DC (NG-RAN E-UTRA-NR DualConnectivity).
[0186] In one embodiment, the dual connection includes EN DC (E-UTRA-NR Dual Connectivity).
[0187] As an example, the first serving cell includes a primary cell (PCell), and the second serving cell includes a primary cell of a secondary cell group (Primary SCG Cell, PSCell).
[0188] As an example, the first serving cell includes a special cell (SpCell).
[0189] As an example, the first serving cell includes a secondary cell (SCell).
[0190] As an example, the first serving cell includes the serving cell of the terminal.
[0191] As an example, the first serving cell includes a master cell group (MCG).
[0192] As an example, the first serving cell includes a secondary cell group (SCG).
[0193] As an example, the first serving cell includes a cell of the MCG.
[0194] As an example, the first serving cell includes a cell of the SCG.
[0195] As an example, the serving base station of the first serving cell includes a master node (MN).
[0196] As an example, the serving base station of the first serving cell includes a secondary node (SN).
[0197] As an example, the terminal 100 is in a connected state.
[0198] As an example, neither the MCG nor the SCG transmission of the terminal 100 is suspended.
[0199] As an example, the SCG associated with the terminal 100 is not deactivated.
[0200] As an example, the terminal 100 is configured with a timer, such as the first timer. Specifically, in implementation, the first timer may be timer T316.
[0201] As an embodiment, determining that the wireless connection fails in step S101 means that the terminal 100 detects an RLF. In other words, an RLF occurs to the terminal 100.
[0202] As an embodiment, determining that the wireless connection fails in step S101 means that an MCG RLF is detected. In other words, an RLF occurs to the MCG.
[0203] In specific implementation, the terminal 100 can monitor the downlink quality according to the cell-specific reference signal to detect the downlink radio link quality of the MCG (such as the PCell), and estimate the downlink radio link quality.
[0204] In specific implementation, if the RSRP of the PCell measured by the terminal 100 is too low, for example, lower than a certain threshold, it can be determined that the wireless connection fails.
[0205] In specific implementation, if the PDCCH decoding fails due to the power signal quality (such as low RSRP and RSRQ), it can be determined that the wireless connection fails.
[0206] In specific implementation, if the PDSCH decoding fails due to the power signal quality (such as low RSRP and RSRQ), it can be determined that the wireless link fails.
[0207] As an embodiment, after the terminal 100 detects an MCG RLF, it can perform one or more of the following operations:
[0208] (1) Pause the MCG transmission of all SRBs, DRBs, and multicast MRBs, except for SRB0;
[0209] (2) Reset the MCG MAC;
[0210] (3) Stop the conditional reconfiguration evaluation for the CHO, if configured;
[0211] (4) Stop the conditional reconfiguration evaluation for the CPC or subsequent CPAC, if configured;
[0212] In step S102, in response to the wireless connection failure, the terminal 100 can send a first message based on the first connection and start the first timer, and the first timer starts timing.
[0213] As an embodiment, the wireless connection failure is a radio link failure (RLF).
[0214] In specific implementation, the first message can indicate the wireless connection failure. The first timer is a configured timer.
[0215] As an embodiment, the first message is an MCG failure message.
[0216] In specific implementation, the first message may be a message regarding RLF occurrence of the MCG.
[0217] As a typical embodiment, the first message is an MCG Failure Information message.
[0218] As an embodiment, the first timer may be, but is not limited to, one of timer T304, timer T310, timer T312, and timer T316, or may also be a combination of multiple timers.
[0219] Typically, the first timer is timer T316.
[0220] In specific implementation, the statement that the first timer is configured means that the terminal 100 is configured with the first timer.
[0221] In specific implementation, the statement that the first timer is configured means that the terminal 100 has obtained the configuration information of the first timer.
[0222] In specific implementation, the statement that the first timer is configured means that the terminal 100 has received the configuration information of the first timer.
[0223] In specific implementation, the statement that the first timer is configured means that the terminal 100 can start the first timer in a timely manner.
[0224] As an embodiment, the first connection may be a direct path or the non-direct path.
[0225] As an embodiment, the first connection may be an SCG or the non-direct path.
[0226] In specific implementation, the first connection is a connection based on SCG or a connection based on non-SCG.
[0227] In step S103, accompanying the first timer, the terminal 100 may generate the first variable.
[0228] As an embodiment, the first variable is an RLF report.
[0229] As a sub-embodiment, the first variable is Var RLF-Report.
[0230] In specific implementation, the first variable includes the first information block and connection failure information.
[0231] In specific implementation, the setting of the first information block depends on the first connection.
[0232] As an embodiment, the first information block depends on whether the first connection is an SCG.
[0233] As a sub - embodiment, the first information block depends on whether the first connection is an SCG or the non - direct path.
[0234] As an embodiment, the non - direct path is a sidelink (SL).
[0235] As an embodiment, the non - direct path is an N3C (Non - 3GPP Connection).
[0236] As an embodiment, the non - direct path is either a sidelink or an N3C.
[0237] As an embodiment, the first information block includes an elapsedTimeT316 field, and the elapsedTimeT316 field is set to the value of the elapsed time of the first timer.
[0238] In specific implementation, the terminal 100 supports RLF reporting for a fast MCG recovery process. The elapsedTimeT316 field in the first information block can be included in the RLF report, and the elapsedTimeT316 field is set to the value of the elapsed time of the first timer.
[0239] As an embodiment, the first field indicates the SCG primary and secondary cells (e.g., pSCell).
[0240] As an embodiment, the first field is pSCellId, and the identifier of the PSCell is the global cell identity of the PSCell.
[0241] As another embodiment, the first field is pSCellId, and the identifier of the PSCell is the physical cell identity and carrier frequency of the PSCell.
[0242] The above - mentioned embodiments have good compatibility and can accurately determine whether the MCG link recovery is completed through the SCG.
[0243] Example 2
[0244] Example 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the appendix Figure 2 as follows
[0245] appendix Figure 2Describes the network architecture 200. 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 will continue to evolve in the future by 3GPP; the network architecture 200 can be referred to as 5GS (5G System) / EPS (Evolved Packet System), or the network architecture 200 can be referred to as 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. However, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks that provide circuit switching services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides termination of user and control plane protocols towards UE 201. Node 203 can be connected to other nodes 204 via the Xn interface (e.g., backhaul) / X2 interface. Node 203 can also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (Transmitting and Receiving Point), or some other suitable term. The core network 210 is a 5GC (5G Core Network) / EPC (Evolved Packet Core), or the core network 210 is a 6GC; node 203 provides an access point to the core network 210 for UE 201. Examples of UE 201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, automobiles, wearable devices, or any other similar functional device.A person skilled in the art may also refer to the UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. The node 203 is connected to the core network 210 through the S1 / NG interface. The core network 210 includes an MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, an S-GW (Service Gateway) / UPF (User Plane Function) 212, and a P-GW (Packet Date Network Gateway) / UPF 213. The MME / AMF / SMF 211 is a control node that processes the signaling between the UE 201 and the core network 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocal) packets are transmitted through the S-GW / UPF 212, and the S-GW / UPF 212 is itself connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 is connected to the Internet service 230. The Internet service 230 includes carrier-corresponding Internet protocol services, which may specifically include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.
[0246] As an embodiment, the UE 201 corresponds to the terminal in the present application.
[0247] As an embodiment, the UE 201 is the terminal in the present application.
[0248] As an embodiment, the UE 201 is a user equipment (UE).
[0249] As an embodiment, the UE 201 is a relay device.
[0250] As an embodiment, the UE 201 is a gateway device.
[0251] As an example, the node 203 corresponds to the base station in the present application.
[0252] As an example, the node 203 is the base station in the present application.
[0253] As an example, the node 203 is a base station device.
[0254] As an example, the node 203 is a relay device.
[0255] As an example, the node 203 is a gateway device.
[0256] As an example, the user equipment supports 3GPP R18 and 3GPP R19.
[0257] As an example, the user equipment supports 5G.
[0258] As an example, the user equipment supports 6G.
[0259] As an example, the user equipment supports Radio Link Monitoring (RLM).
[0260] As an example, the user equipment supports handover.
[0261] As an example, the user equipment supports CHO.
[0262] As an example, the user equipment supports CPC.
[0263] As an example, the user equipment supports LTM.
[0264] As an example, the user equipment supports intra-CU LTM.
[0265] As an example, the user equipment supports inter-CU LTM.
[0266] As an example, the user equipment supports conditional LTM.
[0267] As an example, the user equipment supports event-triggered measurement reporting for LTM.
[0268] As an example, the user equipment supports the transmission of a Non-Terrestrial Network (NTN).
[0269] As an example, the user equipment supports the transmission of a terrestrial network.
[0270] As an example, the user equipment supports dual connection (DC) transmission.
[0271] As an example, the user equipment includes a device that supports low-latency and high-reliability transmission.
[0272] As an example, the user equipment may be a mobile terminal, and the mobile terminal may be a mobile phone, an iPad, a computer, a watch, or a ring; the user equipment may also be a wearable device, and the wearable device may be a watch, a ring, shoes, a hat, clothing, glasses, etc.; the user equipment may also be an aircraft; the user equipment may also be a vehicle-mounted terminal; the user equipment may also be a shipborne terminal; the user equipment may also be an Internet of Things terminal; the user equipment may also be a terminal of an industrial Internet of Things; the user equipment may also be a test device; the user equipment may also be a signaling tester; the user equipment may also be an IAB (Integrated Access and Backhaul)-MT.
[0273] As an example, the base station equipment supports the transmission in a non-terrestrial network.
[0274] As an example, the base station equipment supports the transmission of a terrestrial network.
[0275] As an example, the base station equipment includes a Base Transceiver Station (BTS).
[0276] As an example, the base station equipment includes a Node B (NB); the Node B may be a gNB, an eNB, an ng-eNB, or an en-gNB; the base station equipment may include a Centralized Unit (CU); the base station equipment may also include a Distributed Unit (DU); the base station equipment may also include a Transmitter Receiver Point (TRP).
[0277] As an example, the base station device may be a macro cellular base station, a micro cell base station, a pico cell base station, or a femtocell; the base station device may also be a flying platform device or a satellite device; the base station device may also be a test device or a signaling tester; the base station device may also be a gateway device; the base station device may also be an IAB device; the IAB device includes at least one of an IAB-node, an IAB-donor, an IAB-donor-CU, an IAB-donor-DU, an IAB-DU, or an IAB-MT.
[0278] As an example, 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 a part of a user equipment; the relay device may also include at least a part of a base station device.
[0279] Example 3
[0280] Embodiment 3 exemplifies a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to an embodiment of the present application, as shown in the appendix Figure 3 as follows.
[0281] Figure 3 It is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. Figure 3Show the radio protocol architecture of the control plane 300 for between a first communication node device (UE, gNB or RSU in V2X) and a second communication node device (gNB, UE or RSU in V2X), or between two UEs, with 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. Layer 1 will be referred to as PHY301 in this text. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first communication node device and the second communication node device, or between two UEs. L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, and these sublayers terminate at the second communication node device. 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 handover support for the first communication node device between the second communication node devices. 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 disordered reception due to HARQ. 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 between the first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second communication node device and the first communication node device. The radio protocol architecture of the user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer). For the radio protocol architecture for the first communication node device and the second communication node device in the user plane 350, the physical layer 351, the PDCP sublayer 354 in L2 layer 355, the RLC sublayer 353 in L2 layer 355, and the MAC sublayer 352 in L2 layer 355 are generally the same as the corresponding layers and sublayers in the control plane 300, 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 further includes an SDAP (Service Data Adaptation Protocol) sub-layer 356. The SDAP sub-layer 356 is responsible for the mapping between QoS flows and data radio bearers (DRBs) to support service diversity. Although not shown, the first communication node device may have several upper layers above the L2 layer 355, including a network layer (e.g., IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).
[0282] As an example, the Figure 3 radio protocol architecture in
[0283] As an example, the Figure 3 radio protocol architecture in
[0284] As an example, the higher layer refers to the layer above the physical layer.
[0285] As an example, the first message and the second message are generated in the RRC sub-layer 306.
[0286] As an example, the first message and the second message are sent through the PHY301 or the PHY351.
[0287] As an example, the third message is generated in the RRC sub-layer 306 and sent through the PHY301 or the PHY351.
[0288] Example 4
[0289] Example 4 illustrates a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as shown in Figure 4 shown. Figure 4 is a block diagram of a first communication device 410 and a second communication device 450 that communicate with each other in an access network.
[0290] The first communication device 410 includes a controller / processor 475, a memory 476, a receiving processor 470, a transmitting processor 416, a multi-antenna receiving processor 472, a multi-antenna transmitting processor 471, a transmitter / receiver 418, and an antenna 420.
[0291] The second 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.
[0292] In the transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 layer functionality. In the DL (DownLink), the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation for the second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the second 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 450, and constellation mapping 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 on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more parallel streams. The transmit processor 416 then maps each parallel stream to subcarriers, multiplexes the modulated symbols with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then uses the inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain O streams. Subsequently, the multi-antenna transmit processor 471 performs transmit analog precoding / beamforming operations 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 different antennas 420.
[0293] In the transmission from the first communication device 410 to the second communication device 450, at the second communication device 450, each receiver 454 receives signals via its respective antenna 452. Each receiver 454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream that is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 perform various signal processing functions of the L1 layer. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receivers 454. The receive processor 456 uses the fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receive analog precoding / beamforming operations 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 receive processor 456, where the reference signal will be used for channel estimation, and the data signal is recovered in the multi-antenna receive processor 458 for any parallel streams destined for the second communication device 450 after multi-antenna detection. The symbols on each parallel stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. Subsequently, the receive processor 456 decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the first communication device 410 on the physical channel. Subsequently, the upper layer data and control signals are provided to the controller / processor 459. The controller / processor 459 performs the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. In the DL, the controller / processor 459 provides demultiplexing between the transmission and the logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the core network. Subsequently, the upper layer data packets are provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 for L3 processing. The controller / processor 459 is also responsible for error detection using the acknowledgment (ACK) and / or negative acknowledgment (NACK) protocols to support HARQ operations.
[0294] In the transmission from the second communication device 450 to the first communication device 410, at the second communication device 450, a data source 467 is used to provide upper layer data packets to a controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmit function at the first communication device 410 described in the DL, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on the radio resource allocation of the first communication device 410, and implements L2 layer functions for the user plane and the control plane. The controller / processor 459 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the first communication device 410. A transmit processor 468 performs modulation mapping and channel coding processing, and a multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Subsequently, the transmit processor 468 modulates the generated parallel streams into multi-carrier / single-carrier symbol streams, and after passing through analog precoding / beamforming operations in the multi-antenna transmit processor 457, provides them to different antennas 452 via a transmitter 454. 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.
[0295] In the transmission from the second communication device 450 to the first communication device 410, the functions at the first communication device 410 are similar to the receive functions at the second communication device 450 described in the transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 jointly implement the functions of the L1 layer. A controller / processor 475 implements the L2 layer functions. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as a computer-readable medium. The controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the second communication device 450. The upper layer data packets from the controller / processor 475 may be provided to the core network. The controller / processor 475 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.
[0296] As an example, the second 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 being configured to be used with the at least one processor. The second communication device 450 is at least configured to: determine a wireless connection failure; in response to the determined wireless connection failure, send a first message via a first connection and start a first timer; wherein the first message indicates the wireless connection failure; the first timer being configured; along with the first timer, set a first information block in a first variable; wherein the first variable includes connection failure information;
[0297] wherein the first information block depends on whether the first connection is an SCG or a non-direct path; that the first information block depends on whether the first connection is an SCG or a non-direct path includes: when the first connection is the SCG, the first information block includes a first field, the first field being set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0298] As an example, the second communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: determining a wireless connection failure; in response to the determined wireless connection failure, sending a first message via a first connection and starting a first timer; wherein the first message indicates the wireless connection failure; the first timer being configured; along with the first timer, setting a first information block in a first variable; wherein the first variable includes connection failure information; wherein the first information block depends on whether the first connection is an SCG or a non-direct path; that the first information block depends on whether the first connection is an SCG or a non-direct path includes: when the first connection is the SCG, the first information block includes a first field, the first field being set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0299] As an example, the first 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 being configured to be used with the at least one processor. The first communication device 410 is at least configured to: receive a third message; wherein, as a responder determining a wireless connection failure for the sender of the third message, the sender of the third message sends a first message via a first connection and starts a first timer; along with the first timer, the sender of the third message sets a first information block in a first variable; wherein, the third message includes at least partial information in the first information block; the first message indicates the wireless connection failure; the first information block depends on whether the first connection is an SCG or a non-direct path; wherein, the first information block depending on whether the first connection is an SCG or a non-direct path includes: when the first connection is the SCG, the first information block includes a first field, the first field being set to an identifier of a PSCell; the PSCell belongs to the SCG.
[0300] As an example, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: receive a third message; wherein, as a responder determining a wireless connection failure for the sender of the third message, the sender of the third message sends a first message via a first connection and starts a first timer; along with the first timer, the sender of the third message sets a first information block in a first variable; wherein, the third message includes at least partial information in the first information block; the first message indicates the wireless connection failure; the first information block depends on whether the first connection is an SCG or a non-direct path; wherein, the first information block depending on whether the first connection is an SCG or a non-direct path includes: when the first connection is the SCG, the first information block includes a first field, the first field being set to an identifier of a PSCell; the PSCell belongs to the SCG.
[0301] As an example, the terminal includes the second communication device 450.
[0302] As an example, the terminal in Example 1 includes the second communication device 450.
[0303] As an example, the base station includes the first communication device 410.
[0304] As an example, some or all of {the antenna 452, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller / processor 459, the memory 460} are used to receive the second message; some or all of {the antenna 420, the transmitter 418, the transmitting processor 416, the multi-antenna transmitting processor 471, the controller / processor 475} are used to send the first message and the third message.
[0305] As an example, some or all of {the antenna 420, the receiver 418, the receiving processor 470, the multi-antenna receiving processor 472, the controller / processor 475, the memory 476} are used to receive the third message; some or all of {the antenna 452, the transmitter 454, the transmitting processor 468, the multi-antenna transmitting processor 457, the controller / processor 459, the memory 460, the data source 467} are used to send the second message.
[0306] Example 5
[0307] Embodiment 5 exemplifies a transmission flowchart between the terminal N1 and the base station N2 according to an embodiment of the present application; as shown in the appendix Figure 5 shown. In the appendix Figure 5 the base station N2 and the terminal N1 are communication nodes transmitting through the air interface. It should be noted that the sequence of the steps in the appendix Figure 5 is only a specific implementation manner, and on the premise of no conflict, the sequence of the steps can be adjusted. The path corresponding to the first connection is not shown in the appendix Figure 5
[0308] For the base station N2, receive the first message in step S5200; send the second message in step S5201; receive the third message in step S5202.
[0309] For the terminal N1, determine a wireless connection failure in step S5100; as a response to the determined wireless connection failure, send the first message through the first connection and start the first timer in step S5101; receive the second message in step S5102; stop the first timer and set the first information block in the first variable in step S5103; send the third message in step S5104.
[0310] Specifically, the first message indicates the wireless connection failure; the first timer is configured; the first variable includes connection failure information.
[0311] In specific implementation, when the terminal N1 detects an RLF, it determines that the wireless connection has failed. Specifically, the terminal N1 detects an MCG RLF. After that, in response to the determined wireless connection failure, the terminal N1 can send a first message indicating the wireless connection failure through the first connection and start timing the first timer. The first timer can be configured before step S5101.
[0312] Typically, the first timer is T316.
[0313] After the base station N2 receives the first message in step S5200, it can execute step S5201 to send the second message.
[0314] As an embodiment, the second message is an RRCReconfiguration message carrying reconfigurationwithSync for the PCell.
[0315] As an embodiment, the second message is an RRCRelease message.
[0316] As another embodiment, the second message is a MobilityFromNRCommand message.
[0317] As another embodiment, the second message is any one of an RRCReconfiguration message carrying reconfigurationwithSync for the PCell, an RRCRelease message, or a MobilityFromNRCommand message.
[0318] The terminal N1 receives the second message in step S5102. When receiving the second message, the first timer is still running.
[0319] After that, in response to receiving the second message, step S5103 can be executed to stop the first timer and set a first information block in the first variable.
[0320] In specific implementation, after receiving the second message, the terminal N1 can execute the operations of stopping the first timer and setting a first information block in the first variable together.
[0321] Alternatively, after receiving the second message, the terminal N1 can stop the first timer and immediately set a first information block in the first variable following the stop of the first timer.
[0322] Alternatively, after receiving the second message, the terminal N1 may stop the first timer and set the first information block in the first variable as a response to stopping the first timer.
[0323] Or, after receiving the second message, the terminal N1 may first stop the first timer and then set the first information block in the first variable.
[0324] This embodiment can reduce the latency of setting the first information block, which is beneficial to shortening the latency.
[0325] As an embodiment, the first information block depends on whether the first connection is an SCG or a non-direct path.
[0326] As an embodiment, the first information block depends on whether the first connection is an SCG or a non-direct path, including: when the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG; when the first connection is the non-direct path, the first information block includes a second field, and the second field indicates the non-direct path.
[0327] In one implementation, the first connection is an SCG. When the first connection is the SCG, the first information block includes a first field, and the first field is set to the SCG.
[0328] In one implementation, the first connection is an SCG. When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0329] In another implementation, the first connection is a non-direct path. When the first connection is the non-direct path, the first information block includes a second field, and the second field indicates the non-direct path.
[0330] As an embodiment, the first information block includes the first field and the second field.
[0331] In one implementation, the first information block depends on whether the first connection is an SCG or a non-direct path.
[0332] Specifically, when the first connection is the SCG, the first field of the first information block is set to the identifier of the PSCell; the PSCell belongs to the SCG; the second field is not set.
[0333] In specific implementation, when the first connection is the non-direct path, set the second field in the first information block to the non-direct path and do not set the first field.
[0334] As an implementation manner, the first field and the second field in the first information block are in the same field.
[0335] As an implementation manner, the first field and the second field in the first information block are in different fields.
[0336] As an example, the non-direct path is a sidelink (SL).
[0337] As an example, the non-direct path is N3C (Non-3GPP Connection).
[0338] As an example, the non-direct path is either the sidelink or N3C.
[0339] As an example, the first information block includes an elapsed time field, and the elapsed time field is set to the value of the elapsed time of the first timer.
[0340] As an example, the first information block includes an elapsed timing time field, and the elapsed timing time field is set to the value of the elapsed time of the first timer.
[0341] As a sub-example, the first information block includes an elapsedTimeT316 field, and the elapsedTimeT316 field is set to the value of the elapsed time of the first timer.
[0342] As an example, the first message is an MCGFailureInformation message; the first timer is T316.
[0343] As an example, the first variable is VarRLF-Report.
[0344] As an example, the first field is pSCellId, and the identifier of the PSCell is the global cell identity of the PSCell.
[0345] As a variant example, the first field is pSCellId, and the identifier of the PSCell is the physical cell identity and carrier frequency of the PSCell.
[0346] As an embodiment, the second field indicates the type of the non-direct path.
[0347] As an embodiment, whether the first information block depends on whether the first connection is an SCG or a non-direct path includes: when the first connection is the non-direct path and the non-direct path is a sidelink, the first information block includes a second field, and the second field indicates that the type of the non-direct path is a sidelink; when the first connection is the non-direct path and the non-direct path is N3C, the first information block includes a second field, and the second field indicates that the type of the non-direct path is N3C.
[0348] As an embodiment, the second field indicates that the type of the non-direct path is a sidelink; wherein, the non-direct path is a sidelink.
[0349] As an embodiment, the second field indicates that the type of the non-direct path is N3C; wherein, the non-direct path is N3C.
[0350] As a sub-embodiment of the above embodiment, the second field indicates the type of the N3C.
[0351] As a sub-embodiment of the above embodiment, the second field indicates that the type of the N3C is WLAN.
[0352] As a sub-embodiment of the above embodiment, the second field indicates that the type of the N3C is WiFi.
[0353] As an embodiment, candidates for the type of the non-direct path include a sidelink.
[0354] As an embodiment, candidates for the type of the non-direct path include N3C.
[0355] As an embodiment, candidates for the type of the non-direct path include a sidelink and N3C.
[0356] As an embodiment, the second field indicates the identifier of the non-direct path.
[0357] As an embodiment, the non-direct path is N3C.
[0358] As an embodiment, the identifier of the non-direct path is the physical identifier of the N3C.
[0359] As an embodiment, the identifier of the non-direct path is the virtual identifier of the N3C.
[0360] As an example, the identification of the non-direct path is the network identification of N3C.
[0361] As an example, the identification of the non-direct path is the device identification of N3C.
[0362] As an example, the identification of the non-direct path is the interface identification of N3C.
[0363] As an example, the first information block depending on whether the first connection is an SCG or a non-direct path includes: when the first connection is the non-direct path, the first information block does not include the first domain and the first information block does not include any domain indicating the non-direct path.
[0364] As an example, the first information block depending on whether the first connection is an SCG or a non-direct path includes: when the first connection is the SCG, the first information block includes a first domain, the first domain is set to the identification of the PSCell; the PSCell belongs to the SCG; when the first connection is the non-direct path, the first information block does not include the first domain and the first information block does not include any domain indicating the non-direct path.
[0365] As an example, the first connection is a direct path, the first information block includes a first domain, the first domain is set to the direct path, or the identification of the direct path.
[0366] As an example, only when the first connection is the SCG, the first information block includes a first domain, the first domain is set to the identification of the PSCell; the PSCell belongs to the SCG.
[0367] As an example, the terminal N1 supports the RLF report for the fast MCG recovery process.
[0368] As an example, the terminal N1 supports the RLF report for the fast MCG recovery process, the RLF report includes the first information block in the first variable. The first information block includes an elapsed timing time domain, the elapsed timing time domain is set to the value of the time elapsed by the first timer.
[0369] As a sub-example, the terminal N1 supports the RLF report for the fast MCG recovery process, the RLF report includes the first information block in the first variable. The first information block includes an elapsedTimeT316 domain, the elapsedTimeT316 domain is set to the value of the time elapsed by the first timer. Preferably, the first timer is T316.
[0370] As an example, on the premise that the terminal N1 supports RLF reporting for the fast MCG recovery process, the first information block depends on whether the first connection is an SCG or a non-direct path.
[0371] As an example, if the terminal supports RLF reporting for the fast MCG recovery process, the first information block depends on whether the first connection is an SCG or a non-direct path.
[0372] As an example, if the terminal does not support RLF reporting for the fast MCG recovery process, clear the information included in the first variable.
[0373] In specific implementation, the terminal N1 sends the third message in step S5104, and the third message includes at least part of the information in the first information block.
[0374] As an example, the third message is an RLF report.
[0375] In one implementation, the second message can trigger the third message.
[0376] As an example, the second message can be a UE information request message, such as a UEInformationRequest message, and the third message is a UEInformationResponse message. The UEInformationRequest message triggers the third message; wherein, the UEInformationRequest message includes an rlf-ReportReq field, and the rlf-ReportReq field is set to true.
[0377] In another implementation, the third message can be triggered by other messages other than the second message. The third message is a UEInformationResponse message.
[0378] As an example, a UEInformationRequest message triggers the third message; wherein, the UEInformationRequest message includes an rlf-ReportReq field, and the rlf-ReportReq field is set to true; the third message is a UEInformationResponse message.
[0379] As an example, the third message is a UEAssistanceInformation message.
[0380] As an embodiment, the third message is an RRC Resume Request message.
[0381] As an embodiment, the third message is an RRC Reestablishment Request message.
[0382] The base station N2 receives the third message in step S202. The process ends, or the process turns to the start of other signaling or data transmission.
[0383] The above embodiments can be better compatible with existing protocols and improve the accuracy of RLF reports. For the technical details of this embodiment, reference can also be made to the description in Embodiment 1.
[0384] Example 6
[0385] Embodiment 6 exemplifies the transmission process between the terminal N1 and the base station N2 according to another embodiment of the present application, as Figure 6 shown.
[0386] For the base station N2, it receives the first message in step S6200; and receives the third message in step S6201.
[0387] For the terminal N1, it determines a radio connection failure in step S6100; in response to the determined radio connection failure, it sends the first message through the first connection and starts the first timer in step S6101; in step S6102, when the first timer expires, it sets the first information block in the first variable; and sends the third message in step S6103.
[0388] Figure 6 For each message and term shown, step S6100, step S6101, and step S6200 can respectively refer to step S101, step S102, and step S200 in Embodiment 1 and step S5101, step S5102, step S5200 in Embodiment 5, step S6103 can refer to step S5104 in Embodiment 5, and step S6201 can refer to step S5202 in Embodiment 5, which will not be elaborated here.
[0389] It should be noted that the terminal N1 starts the first timer in step S6101, and the first timer expires in step S6102.
[0390] In response to the expiration of the first timer, the first information block is set in the first variable.
[0391] In this embodiment, after receiving the first message, the base station N2 does not send a signaling related to setting the first information block to the terminal N1.
[0392] As an example, after receiving the first message, base station N2 does not send signaling related to the first variable to terminal N1.
[0393] As an example, after receiving the first message, base station N2 does not send the second message to terminal N1.
[0394] The above embodiments do not need to transmit and receive the second message, which can effectively reduce signaling overhead and save power consumption.
[0395] In this embodiment, after receiving the first message, base station N2 sends the second message (not shown in the figure) to terminal N1, and terminal N1 does not receive the second message.
[0396] In this embodiment, after receiving the first message, base station N2 sends the second message (not shown in the figure) to terminal N1, and terminal N1 fails to decode the second message successfully.
[0397] As an example, it is set that the first information block is an operation performed by terminal N1 when the first timer expires.
[0398] As an example, if the first timer expires and terminal N1 supports RLF-Report for the fast MCG recovery process, terminal N1 may set the first field in the first information block to PSCell.
[0399] If the first timer expires and terminal N1 supports RLF-Report for the fast MCG recovery process, terminal N1 may set the first field in the first information block to PSCell or the identifier of the PSCell. The identifier of the PSCell is the global cell identifier of the PSCell.
[0400] As a sub-example, the first field is denoted as PSCell, and the first field is set to the identifier of the PSCell.
[0401] As a sub-example, the first field is denoted as PSCell, and the first field is set to pSCellId. The identifier of the PSCell is the physical cell identity and carrier frequency of the PSCell.
[0402] As an example, the first variable includes the mcgRecoveryFailureCause field and can be set to the expiration of the first timer.
[0403] As a sub - embodiment, the first variable includes the mcgRecoveryFailureCause field and can be set to t316 - expiry.
[0404] As an embodiment, the terminal N1 can initiate a connection re - establishment procedure.
[0405] Example 7
[0406] Embodiment 7 exemplifies a flowchart for setting the first information block according to an embodiment of the present application, as shown in the appendix Figure 7 as follows.
[0407] In Embodiment 7, the terminal determines in step S701 whether the first connection is an SCG or a non - direct path; if the first connection is an SCG, the terminal executes step S7021, that is, sets the first information block in the first variable, where the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG. If the first connection is the non - direct path, the terminal executes step S7022, that is, sets the first information block in the first variable, where the first information block includes a second field, and the second field indicates the non - direct path.
[0408] Specifically, step S701 is a sub - step in Embodiment 1, Embodiment 5, and Embodiment 6. For example, step S701 can be implemented in the operation of setting the first information block in the first variable.
[0409] As an embodiment, the first variable is an RLF report.
[0410] As a sub - embodiment, the first variable is VarRLF - Report.
[0411] In an embodiment, the third message may include the first variable.
[0412] In a sub - embodiment, the third message may include at least part of the information in the first variable.
[0413] In an embodiment, the third message may include the first information block.
[0414] In an embodiment, the third message may include at least part of the information in the first information block.
[0415] As an embodiment, the third message is a UEInformationResponse message.
[0416] As an example, the third message is a UE Assistance Information message.
[0417] As an example, the third message is an RRC Resume Request message.
[0418] As an example, the third message is an RRC Reestablishment Request message.
[0419] As an example, the first information block includes the first field.
[0420] As an example, the first field is denoted as PSCell.
[0421] As an example, the first field is SCG.
[0422] As a sub - example, the first field is the identifier of SCG. Specifically, in implementation, the identifier of SCG can be the identifier of PSCell, and the PSCell belongs to the SCG.
[0423] As a sub - example, the first field is pSCellId, and the identifier of the PSCell is the global cell identity of the PSCell.
[0424] As an example, the first field is pSCellId, and the identifier of the PSCell is the physical cell identity and carrier frequency of the PSCell.
[0425] As an example, the dependence of the first information block on whether the first connection is SCG or a non - direct path includes:
[0426] When the first connection is the non - direct path and the non - direct path is a secondary link, the first information block includes a second field, and the second field indicates that the type of the non - direct path is a secondary link; when the first connection is the non - direct path and the non - direct path is N3C, the first information block includes a second field, and the second field indicates that the type of the non - direct path is N3C.
[0427] As an example, the second field indicates that the type of the non - direct path is a secondary link; wherein, the non - direct path is a secondary link.
[0428] As an example, the second field indicates that the type of the non-direct path is N3C; wherein, the non-direct path is N3C.
[0429] As a sub-example of the above example, the second field indicates the type of the N3C.
[0430] As a sub-example of the above example, the second field indicates that the type of the N3C is WLAN.
[0431] As a sub-example of the above example, the second field indicates that the type of the N3C is WiFi.
[0432] As an example, candidates for the type of the non-direct path include sidelink.
[0433] As an example, candidates for the type of the non-direct path include N3C.
[0434] As an example, candidates for the type of the non-direct path include sidelink and N3C.
[0435] As an example, the second field indicates the identifier of the non-direct path.
[0436] As an example, the non-direct path is N3C.
[0437] As an example, the identifier of the non-direct path is the physical identifier of N3C.
[0438] As an example, the identifier of the non-direct path is the virtual identifier of N3C.
[0439] As an example, the identifier of the non-direct path is the network identifier of N3C.
[0440] As an example, the identifier of the non-direct path is the device identifier of N3C.
[0441] As an example, the identifier of the non-direct path is the interface identifier of N3C.
[0442] As an example, the non-direct path is sidelink (SL).
[0443] As an example, the non-direct path is N3C (Non-3GPP Connection).
[0444] As an example, the non-direct path is either sidelink or N3C.
[0445] As an example, if the terminal does not support reporting of RLF reports, the information included in the first variable may be cleared.
[0446] As an example, if the terminal does not support RLF reports for the fast MCG recovery process, the information included in the first variable is cleared.
[0447] Regarding each term and concept in this embodiment, reference may be made to the descriptions in Embodiments 1 to 7.
[0448] Example 8
[0449] Embodiment 8 exemplifies a transmission flowchart between a terminal N1, a second node N2, and a third node N3 according to an embodiment of the present application; as shown in the appendix Figure 8 As shown, both the second node N2 and the terminal N1, and the third node N3 and the terminal N1 are communication nodes that transmit through the air interface. The second node N2 and the third node N3 are serving cell maintaining base stations of the terminal N1.
[0450] As an example, the serving cell of the terminal N1 may include a primary cell (PCell).
[0451] As an example, the serving cell of the terminal N1 includes a primary cell of a secondary cell group (Primary SCG Cell, PSCell).
[0452] As an example, the serving cell of the terminal N1 includes a special cell (Special Cell, SpCell).
[0453] As an example, the serving cell of the terminal N1 includes a secondary cell (SCell).
[0454] As an example, the serving cell of the terminal N1 includes a master cell group (MCG).
[0455] As an example, the serving cell of the terminal N1 includes a secondary cell group (SCG).
[0456] As an example, the serving cell of the terminal N1 includes a cell of the MCG.
[0457] As an example, the serving cell of the terminal N1 includes a cell of the SCG.
[0458] As an example, the serving cell maintaining base station of the terminal N1 includes a master node (Master Node, MN).
[0459] As an example, the serving base station of the terminal N1 includes a secondary node (SN).
[0460] As an example, the second node N2 may be the master node of the terminal N1, and the third node N3 may be the secondary node of the terminal N1.
[0461] As an example, the second node N2 may be the base station of a cell in the MCG of the terminal N1, and the third node N3 may be the base station of a cell in the SCG of the terminal N1.
[0462] In Embodiment 8, the terminal N1 first detects that the link between the second node N2 and the terminal N1 has an RLF; then, the terminal may perform operation S1 to send a first message to the second node N2 through the third node N3. The third node N3 performs operation S2 to send the first message carried in operation S1 to the second node N2. Then, the second node N2 performs operation S3 to send a second message to the third node N3, and then the third node N3 performs operation S4 to send the second message to the terminal N1. Then, the terminal N1 may perform operation S5, for example, may send the third message to the second node N2.
[0463] As an example, the wireless connection recovery includes recovering MCG transmission.
[0464] As an example, the wireless connection recovery includes fast recovery of the MCG link.
[0465] It should be noted that operation S3 and operation S4 are optional operations, that is, the process of sending the second message from the second node N2 to the terminal N1 through the third node N3 is optional.
[0466] Operation S5 is also optional in some scenarios. For example, when the third message is a UEInformationResponse message, if the UE information request message from the second node N2 is not received, the terminal N1 may not send the third message.
[0467] As a sub - embodiment, if the UEInformationRequest message from the second node N2 is not received, the terminal N1 may not send the UEInformationResponse message.
[0468] As an example, after the wireless connection between the second node N2 and the terminal N1 is recovered, the second node N2 may perform operation S6 (not shown in the figure) to send signaling and data to the terminal N1. Or, the second node N2 and the terminal N1 may send signaling and data to each other (not shown in the figure).
[0469] In this embodiment, the first connection refers to a link connection through the third node N3.
[0470] In this embodiment, the first connection refers to a data (including signaling and other data) transmission link through the third node N3.
[0471] As a sub - embodiment, the first connection refers to a connection through the third node N3.
[0472] In specific implementation, the connection between the third node N3 and the second node N2 can be a wired connection.
[0473] In specific implementation, the connection between the third node N3 and the second node N2 can be a backhaul link.
[0474] As an embodiment, the first connection passing through the third node N3 is an SCG.
[0475] As a variant, the first connection passing through the third node N3 is a non - direct path.
[0476] In specific implementation, the non - direct path can refer to the relevant descriptions in Embodiments 1 to 7.
[0477] Regarding the description of the transmission process of the terminal N1, the second node N2, and the third node N3, reference can be made to the descriptions in Embodiments 1 to 7.
[0478] Example 9
[0479] Embodiment 9 exemplifies a transmission flow chart between the terminal N1, the second node N2, and the third node N3 according to an embodiment of the present application; as shown in the appendix Figure 9 as follows.
[0480] Embodiment 9 is similar to Embodiment 8, except that the terminal N1 performs operation S5 to send the third message to the fourth node N4. The fourth node N4 can transmit the third message to the second node N2.
[0481] In specific implementation, the fourth node N4 can transmit the third message to the second node N2 through a backhaul link.
[0482] As an embodiment, the third message can be the first variable.
[0483] As a sub - embodiment, the third message can be VarRLF - Report.
[0484] As a sub - embodiment, the third message may be part of the information in VarRLF - Report.
[0485] In one embodiment, the fourth node N4 is another node different from the second node N2.
[0486] In one embodiment, the fourth node N4 is a primary cell (PCell) node.
[0487] In a sub - embodiment, the fourth node N4 is a base station of a primary cell (PCell).
[0488] In one embodiment, the fourth node N4 is a special cell (SpCell) node.
[0489] In a sub - embodiment, the fourth node N4 is a base station of a special cell (SpCell).
[0490] In one embodiment, the fourth node N4 is a cell node of an MCG.
[0491] In a sub - embodiment, the fourth node N4 is a base station of a cell of an MCG.
[0492] In one embodiment, the fourth node N4 is an MN.
[0493] In specific implementation, the fourth node N4 may transmit the third message to the second node N2.
[0494] Example 10
[0495] Embodiment 10 exemplifies a flowchart of a method used in a base station according to an embodiment of the present application, as shown in the appendix Figure 10 shown. In the appendix Figure 10 In it, the base station 10200 executes step 10201 to receive a third message; wherein, as the sender of the third message determines a response to a radio connection failure, the sender of the third message sends a first message through a first connection and starts a first timer; along with the first timer, the sender of the third message sets a first information block in a first variable.
[0496] In a specific implementation, the third message includes at least part of the information in the first information block; the first message indicates the failure of the wireless connection; the first information block depends on whether the first connection is an SCG or a non-direct path; wherein, the first information block depending on whether the first connection is an SCG or a non-direct path includes: when the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0497] Typically, the sender of the third message is a terminal, for example, a UE.
[0498] As an embodiment, the base station 10200 may be the serving base station of the terminal.
[0499] As another embodiment, the base station 10200 is not the serving base station when the terminal determines the failure of the wireless connection.
[0500] As an embodiment, the base station 10200 may be the serving base station of the serving cell of the terminal.
[0501] As an embodiment, the base station 10200 receives the first message.
[0502] In a specific implementation, the base station 10200 may receive the first message before receiving the third message.
[0503] As an embodiment, the accompanying first timer refers to the expiration of the first timer.
[0504] In a specific implementation, when the first timer expires, the sender of the third message sets the first information block in the first variable.
[0505] In a specific implementation, the base station 10200 may send a second message after receiving the first message. It should be noted that sending the second message is an optional operation.
[0506] In a specific implementation, the sender of the third message receives the second message; in response to the reception of the second message, the sender of the third message stops the first timer; wherein, when the second message is received, the first timer is running; the accompanying the first timer includes: stopping the first timer.
[0507] As an embodiment, the first information block depending on whether the first connection is an SCG or a non-direct path includes:
[0508] When the first connection is the non-direct path, the first information block includes a second field, and the second field indicates the non-direct path.
[0509] As an embodiment, the second field indicates the type of the non-direct path.
[0510] As an embodiment, the second field indicates the identification of the non-direct path.
[0511] As an embodiment, whether the first information block depends on whether the first connection is an SCG or a non-direct path includes: when the first connection is the non-direct path, the first information block does not include the first field and the first information block does not include any field indicating the non-direct path.
[0512] As an embodiment, the sender of the third message supports the fast MCG recovery process.
[0513] As an embodiment, the sender of the third message indicates the fast recovery of the MCG link.
[0514] Those skilled in the art understand that the step S10201 can be regarded as an execution step corresponding to the steps in the above Figure 1 , Figure 5 , Figure 6 shown embodiments, and the two are complementary in terms of specific implementation principles and logics. Therefore, the communication method on the base station side can refer to the relevant descriptions of the Figure 1 , Figure 5 , Figure 6 and other embodiments shown in the drawings, which will not be elaborated here.
[0515] Example 11
[0516] Embodiment 11 exemplifies a structural block diagram of a processing device in a terminal according to an embodiment of the present application; as shown in the accompanying Figure 11 figure. In the accompanying Figure 11 figure, the processing device 1600 in the terminal includes a first processor 1601 and a first transmitter 1602.
[0517] In a specific implementation, the first processor 1601 determines a wireless connection failure; the first transmitter 1602, in response to the determined wireless connection failure, sends a first message through a first connection and starts a first timer; wherein, the first message indicates the wireless connection failure; the first timer is configured; the first processor 1601, along with the first timer, sets a first information block in a first variable; wherein, the first variable includes connection failure information.
[0518] In a specific implementation, the first information block depends on whether the first connection is an SCG or a non-direct path; that the first information block depends on whether the first connection is an SCG or a non-direct path includes: when the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0519] As an embodiment, the accompanying first timer includes: the first timer expires.
[0520] As an embodiment, the first processor 1601 receives a second message; in response to the reception of the second message, the first timer is stopped; when the second message is received, the first timer is running; the accompanying first timer includes: stopping the first timer.
[0521] As an embodiment, that the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0522] When the first connection is the non-direct path, the first information block includes a second field, and the second field indicates the non-direct path.
[0523] As an embodiment, the second field indicates the type of the non-direct path.
[0524] As an embodiment, the second field indicates the identifier of the non-direct path.
[0525] As an embodiment, that the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0526] When the first connection is the non-direct path, the first information block does not include the first field and the first information block does not include any field indicating the non-direct path.
[0527] As an embodiment, the terminal supports RLF reporting for a fast MCG recovery process.
[0528] As an embodiment, the first transmitter 1602 sends a third message; wherein, the third message includes at least partial information in the first information block.
[0529] As an embodiment, the first transmitter 1602 includes at least one of {antenna 420, receiver / transmitter 418, transmit processor 416, multi-antenna transmit processor 471, controller / processor 475, memory 476} in Embodiment 4.
[0530] As an example, the processor 1601 includes at least one of {antenna 420, receiver / transmitter 418, receive processor 470, transmit processor 416, multi-antenna receive processor 472, multi-antenna transmit processor 471, controller / processor 475, memory 476} in Embodiment 4.
[0531] For more information about the working principle and mode of operation of the processing device 1600, reference may be made to the relevant descriptions of the technical solutions shown above. Figures 1 to 9 They will not be elaborated here.
[0532] Example 12
[0533] Embodiment 12 illustrates a block diagram of a processing device for a base station according to an embodiment of the present application; as shown in the appendix. Figure 12 In the appendix, Figure 12 the processing device 1700 in the base station includes a first receiver 1701 and a first transmitter 1702.
[0534] In a specific implementation, the first receiver 1701 receives a third message; wherein, as a response to determining a radio connection failure by the sender of the third message, the sender of the third message sends a first message through a first connection and starts a first timer; along with the first timer, the sender of the third message sets a first information block in a first variable.
[0535] Wherein, the third message includes at least partial information in the first information block; the first message indicates the radio connection failure; the first information block depends on whether the first connection is an SCG or a non-direct path; wherein, the first information block depends on whether the first connection is an SCG or a non-direct path includes:
[0536] When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
[0537] The "along with the first timer" includes: the expiration of the first timer.
[0538] As an example, the sender of the third message receives a second message; as a response to the reception of the second message, the sender of the third message stops the first timer; wherein, when the second message is received, the first timer is running; the "along with the first timer" includes: the stopping of the first timer.
[0539] As an example, the first transmitter 1702 sends the second message.
[0540] As an example, the serving base station of the PSCell sends the second message.
[0541] As an example, the serving base station of the PCell sends the second message.
[0542] As an example, the base station sends the second message.
[0543] As an example, whether the first information block depends on whether the first connection is an SCG or an indirect path includes: when the first connection is the indirect path, the first information block includes a second field, and the second field indicates the indirect path.
[0544] As an example, the second field indicates the type of the indirect path.
[0545] As an example, the second field indicates the identifier of the indirect path.
[0546] As an example, whether the first information block depends on whether the first connection is an SCG or an indirect path includes: when the first connection is the indirect path, the first information block does not include the first field and the first information block does not include any field indicating the indirect path.
[0547] As an example, the sender of the third message supports the fast MCG recovery process.
[0548] As an example, the first receiver 1701 includes the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 attached to the present application Figure 4 as shown in the drawings.
[0549] As an example, the first receiver 1701 includes the antenna 452, the receiver 454, the multi-antenna receiving processor 458, and the receiving processor 456 attached to the present application Figure 4 as shown in the drawings.
[0550] As an example, the first receiver 1701 includes the antenna 452, the receiver 454, and the receiving processor 456 attached to the present application Figure 4 as shown in the drawings.
[0551] For more content about the working principle and working mode of the processing device 1700, reference can be made to the relevant descriptions of the technical solutions shown in the above Figures 1 to 8 、 Figure 10 and will not be elaborated here.
[0552] Those of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing 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 disc, etc. Optionally, all or part of the steps of the above embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiments can be implemented in the form of hardware or in the form of a software functional module. This application is not limited to any specific form of the combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, drones, communication modules on drones, remote control aircraft, aircraft, small aircraft, mobile phones, tablet computers, laptops, vehicle-mounted communication devices, transportation means, vehicles, RSU, wireless sensors, network cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers, and other wireless communication devices. The base station or system device in this application includes, but is not limited to, macrocell base stations, microcell base stations, small cell base stations, home base stations, relay base stations, eNB, gNB, TRP (Transmitter Receiver Point), GNSS, relay satellites, satellite base stations, aerial base stations, RSU (Road Side Unit), drones, test equipment, such as transceiver devices or signaling testers that simulate some functions of base stations, and other wireless communication devices.
[0553] Those skilled in the art should understand that the present invention can be implemented in other specified forms without departing from its core or basic characteristics. Therefore, the embodiments disclosed currently should be considered as descriptive rather than restrictive in any case. The scope of the invention is determined by the appended claims rather than the previous description, and all modifications within the equivalent meaning and scope thereof are considered to be included therein.
Claims
1. A method used in a terminal, characterized in that: include: Determine that the wireless connection has failed; In response to the determination that the wireless connection has failed, sending a first message via a first connection and starting a first timer; wherein the first message indicates that the wireless connection has failed; and the first timer is configured; Accompanying the first timer, setting a first information block in a first variable; wherein the first variable includes connection failure information; wherein the first information block depends on whether the first connection is an SCG or an indirect path; The first information block includes, depending on whether the first connection is an SCG or an indirect path: When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
2. The method according to claim 1, characterized in that The accompanying the first timer includes: the first timer expires.
3. The method according to claim 1, characterized in that The method comprises: receiving a second message; In response to receiving the second message, stopping the first timer; Wherein, when the second message is received, the first timer is running; and accompanying the first timer includes: stopping the first timer.
4. The method according to any one of claims 1 to 3, characterized in that The first information block includes, depending on whether the first connection is an SCG or an indirect path: When the first connection is the indirect path, the first information block includes a second field indicating the indirect path.
5. The method according to claim 4, characterized in that The second field indicates the type of the indirect path.
6. The method according to claim 4 or 5, characterized in that: The second field indicates an identifier of the indirect path.
7. The method according to any one of claims 1 to 3, characterized in that The first information block includes, depending on whether the first connection is an SCG or an indirect path: When the first connection is the indirect path, the first information block does not include the first field and the first information block does not include any field indicating the indirect path.
8. The method according to any one of claims 1 to 7, characterized in that The terminal supports RLF reporting for fast MCG recovery process.
9. The method according to any one of claims 1 to 8, characterized in that The method comprises: sending a third message; The third message includes at least part of the information in the first information block.
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 9.
11. A method used in a base station, characterized in that: include: receiving a third message; wherein, in response to the sender of the third message determining that the wireless connection has failed, the sender of the third message sends a first message through the first connection and starts a first timer; accompanying the first timer, the sender of the third message sets a first information block in a first variable; The third message includes at least part of the information in the first information block; the first message indicates that the wireless connection fails; the first information block depends on whether the first connection is an SCG or an indirect path; wherein the first information block depends on whether the first connection is an SCG or an indirect path and includes: When the first connection is the SCG, the first information block includes a first field, and the first field is set to the identifier of the PSCell; the PSCell belongs to the SCG.
12. The method according to claim 11, characterized in that The accompanying the first timer includes: the first timer expires.
13. The method according to claim 11, characterized in that The sender of the third message receives the second message; in response to the receipt of the second message, the sender of the third message stops the first timer; wherein, when the second message is received, the first timer is running; the accompanying the first timer includes: the stopping of the first timer.
14. The method according to any one of claims 11 to 13, characterized in that The first information block includes, depending on whether the first connection is an SCG or an indirect path: When the first connection is the indirect path, the first information block includes a second field indicating the indirect path.
15. The method according to claim 14, characterized in that The second field indicates the type of the indirect path.
16. The method according to claim 14 or 15, characterized in that The second field indicates an identifier of the indirect path.
17. The method according to any one of claims 11 to 13, characterized in that The first information block includes, depending on whether the first connection is an SCG or an indirect path: When the first connection is the indirect path, the first information block does not include the first field and the first information block does not include any field indicating the indirect path.
18. The method according to any one of claims 11 to 17, characterized in that The sender of the third message supports a fast MCG recovery process.
19. 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 18.