Link recovery information reporting method and user equipment

Abstract

Provided in the present application are a link recovery information reporting method and a user equipment. The link recovery information reporting method comprises: a user equipment (UE) initiating a rapid master cell group (MCG) recovery process; executing a primary-secondary cell (PSCell) change process; and storing, in a self-optimization network (SON) report, link recovery information that includes a primary-secondary cell (PSCell) change used for indicating that a PSCell change has occurred in the rapid MCG recovery process.

Description

Link recovery information reporting method and user equipment Technical Field

[0001] The present disclosure relates to the technical field of wireless communications, and more particularly, to a method for reporting link recovery information in the event of a link failure in wireless communications and a corresponding user equipment. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is conducting a new research project for Release 18 technical standards (see non-patent literature: RP-221825: WID on further enhancement of data collection for SON (Self-Organizing Networks) / MDT (Minimization of Drive Tests) in NR standalone and MR-DC). The purpose of this research project is to further enhance the network data collection process in Release 17-based NR systems to better achieve self-organizing and self-optimizing networks and minimize drive tests. One of the specific technologies being studied is to implement a mobile performance optimization mechanism under the fast Master Cell Group (MCG) recovery mechanism.

[0003] This disclosure proposes a solution to the problem of how to implement link recovery information reporting under the fast MCG recovery mechanism in the NR system.

[0004] Summary of the Invention

[0005] The purpose of the embodiments of the present disclosure is to propose a solution to the problem of how to implement link recovery information reporting under the fast MCG recovery mechanism in the NR system. More specifically, the present disclosure proposes a solution to the problem of how to report link recovery information in the case of a change of primary and secondary cells when the fast MCG recovery process is performed in the NR system.

[0006] The present disclosure provides a link recovery information reporting method performed in a user equipment and a corresponding user equipment.

[0007] According to the first aspect of the present disclosure, a link recovery information reporting method is proposed, including: user equipment UE initiating a fast main cell group MCG recovery process; executing a main and auxiliary cell PSCell change process; saving link recovery information of the main and auxiliary cell PSCell change in a self-optimizing network SON report; wherein the link recovery information of the PSCell change includes one or more of the following information: first information, used to indicate that a PSCell change has occurred during the fast MCG recovery process; second information, used to record the time from the successful completion of the PSCell change to the T316 timeout during the fast MCG recovery process; third information, used to record the time from the successful completion of the PSCell change to the T316 stop during the fast MCG recovery process; fourth information, used to record the time used to execute the PSCell change process during the fast MCG recovery process; fifth information, used to indicate that a PSCell change failure has occurred during the fast MCG recovery process; sixth information, used to indicate that a PSCell change failure has occurred due to a random access failure of the SCG during the fast MCG recovery process.

[0008] In the link recovery information reporting method of the first aspect above, optionally, the time used in the PSCell change process is the time elapsed by the timer T304 associated with the PSCell change process,

[0009] In the link recovery information reporting method of the first aspect above, optionally, the successful completion of the PSCell change is the successful completion of the random access process to the target PSCell triggered by the PSCell change; the failure of the PSCell change is the timeout of the timer T304 associated with the PSCell change, or the UE's radio resource control RRC layer receives a random access failure indication from the bottom layer.

[0010] In the link recovery information reporting method of the first aspect above, optionally, during the fast MCG recovery process, timer T316 is running.

[0011] In the link recovery information reporting method of the first aspect above, optionally, the PSCell change occurs when a command for the PSCell change is received; and the command for the PSCell change is an RRC reconfiguration message containing a synchronization reconfiguration information element for the secondary cell group SCG or a mobility LTM cell change command for triggering the SCG based on layer 1 and layer 2 triggering.

[0012] In the link recovery information reporting method of the first aspect above, optionally, when a fast MCG recovery failure occurs due to expiration of the timer T316, the UE includes the second information in the SON report.

[0013] In the link recovery information reporting method of the first aspect above, optionally, when a response message is received during the fast MCG recovery process, the UE includes third information in the SON report; and the response message is an RRC reconfiguration message containing a synchronization reconfiguration information element for the MCG, or an RRC release message, or an LTM cell switch command for triggering the MCG.

[0014] In the link recovery information reporting method of the first aspect above, optionally, the link information reporting method further includes: the UE receives a UEInformationRequest message from the network side, the UEInformationRequest message carries an indication / request for requesting the UE to report the saved SON report; and the UE includes the content of the saved SON report containing one or more of the first information to the sixth information in a UEInformationResponse message, and sends the UEInformationResponse message to the network side.

[0015] In the link recovery information reporting method of the first aspect above, optionally, the SON report is an RLF report; and the UE saves information in the RLF report in a variable VarRLF-Report.

[0016] According to a second aspect of the present disclosure, a user equipment (UE) is proposed, comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, execute the link recovery information reporting method described in the context. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

[0018] FIG1 is a schematic flow chart showing a link recovery information reporting method in Embodiment 1 of the present disclosure.

[0019] FIG2 is a schematic flow chart showing a link recovery information reporting method in Embodiment 2 of the present disclosure.

[0020] FIG3 is a block diagram showing a user equipment UE involved in the present disclosure.

[0021] In the drawings, the same or similar structures are marked with the same or similar reference numerals. DETAILED DESCRIPTION

[0022] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description of exemplary embodiments of the disclosure, taken in conjunction with the accompanying drawings.

[0023] In this disclosure, the terms "include" and "including" and their derivatives are intended to include but not limit; the term "or" is inclusive, meaning and / or. The terms "if", "if", "in the case of" and "when" are interchangeable.

[0024] In this specification, the various embodiments described below for describing the principles of the present disclosure are merely illustrative and should not be construed in any way as limiting the scope of the disclosure. The following description with reference to the accompanying drawings is intended to assist in a comprehensive understanding of the exemplary embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes a variety of specific details to aid understanding, but these details should be considered merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, for the sake of clarity and brevity, descriptions of well-known functions and structures have been omitted. In addition, throughout the drawings, the same reference numerals are used for similar functions and operations.

[0025] The following text takes the / NR mobile communication system and its subsequent evolutionary versions as example application environments to specifically describe multiple implementations according to the present disclosure. However, it should be noted that the present disclosure is not limited to the following implementations, but is applicable to many other wireless communication systems. Unless otherwise specified, the concepts of cell and base station can be replaced with each other; cell, beam, and transmission point (TRP) can be interchanged. A handover command and a radio resource control (RRC) message containing a handover command are equivalent, and refer to an RRC message or a configuration in an RRC message that triggers the UE to perform a handover. A handover configuration refers to all or part of the configuration in a handover command. Cancellation, release, deletion, clearing, and clearing can be replaced. Execution, use, and application can be replaced. Configuration and reconfiguration can be replaced. Monitoring (monitor) and detection (detect) can be replaced. Initiate (initiate) and trigger (trgger) can be replaced.

[0026] In the present disclosure, handover refers to the change of the primary cell triggered or configured by the network side. The handover command is used to trigger the UE to perform handover. In the NR system, the traditional handover command is an RRC reconfiguration message containing a synchronous reconfiguration (Reconfigurationwithsync) information element for the primary cell group MCG. In this case, handover can also be referred to as synchronous reconfiguration of the MCG. After the NR system of version 18 introduced the cell switch mechanism of layer 1 and layer 2 triggered mobility (L1 / L2-triggered mobility, LTM), handover also includes the cell switch of LTM. In LTM, the handover command used to trigger the cell change is a medium access control (Medium Access Control) control element (CE) for LTM cell switch. The processes used for primary cell change in the present disclosure can be collectively referred to as PCell change.

[0027] The following describes processes or concepts in the prior art to which this disclosure relates.

[0028] Dual Connectivity:

[0029] In order to improve the data transmission efficiency of the UE, the UE establishes links with two base stations at the same time, that is, the radio resources used by the UE are provided by different schedulers located in the two base stations. The radio access between the two base stations and the UE can be the same or different standards (Radio Access Technology, RAT), such as both are NR, or one is NR and the other is LTE, also known as Evolved Universal Terrestrial Radio Access (E-UTRA). Among the two base stations, one is called the Master Node (MN) or MgNB, MeNB, and the service cell group under the Master Node is called the Master Cell Group (MCG); the other is called the Secondary Node (SN) or SgNB, SeNB, and the service cell group under the Secondary Node is called the Secondary Cell Group (SCG). When the Master Node is LTE and the Secondary Node is NR, the DC is called EN-DC (using the 4G core network) or NGEN-DC (using the 5G core network); when both the Master Node and the Secondary Node are NR, the DC is called NR-DC. MCG consists of a primary cell (PCell) and optionally one or more secondary cells (SCell). PCell operates on the primary frequency, and the UE performs the initial connection establishment process or the connection re-establishment process through the primary frequency. SCG consists of a PSCell and optionally one or more SCells. PSCell refers to the SCG cell to which the UE performs random access when performing the synchronization reconfiguration process or the SCG addition process. PCell and PSCell are also collectively referred to as special cells SpCell. When DC is configured, the DRB and SRB of the UE are supported to be configured as split bearers. Split SRB supports transmission through both MCG and SCG paths. When not configured as split SRB, SRB1 and SRB2 are transmitted through the MCG path. In addition, when DC is configured, SRB3 can also be established for the SN, which is mainly used to transmit the configuration associated with the SCG between the SN and the UE. The establishment and release of SRB3 are determined by the SN, and the configuration of split SRB for SRB3 is not supported. The UE can configure split SRB1 and SRB3 at the same time.

[0030] Fast MCG link recovery mechanism:

[0031] The dual link and carrier aggregation enhancement project of version 16 (see document RP-190452) introduces a fast MCG link recovery mechanism. In the fast MCG link recovery mechanism, when a radio link failure (RLF) occurs in the UE's MCG or the UE fails to perform a handover process (HOF) (i.e., the MCG timer T304 times out), if the UE is configured with timer T316 (i.e., fast MCG link recovery is enabled) and the link quality of the secondary cell group SCG is good (i.e., no RLF occurs, timer T310 is not running or is not in the PSCell addition and change process (i.e., T04 corresponding to the PSCell is not running), or the SCG is not suspended, or the SCG is not in a deactivated state), at this time, both the MCG and the SCG are not in a suspended (or interrupted) state or the timer T316 is not running, then the UE initiates the MCG failure information process, starts the timer T316, and returns to the SCG through the SCG path (such as split SRB1 or SRB3) sends an MCG failure information (MCGFailureInformation) message containing an information report on the MCG link failure to the master base station instead of directly triggering the RRC connection re-establishment process. In the MCG failure information process, the UE will suspend the transmission of the MCG path, such as suspending the transmission on the MCG side corresponding to all SRBs and DRBs except SRB0, and reset the MAC entity corresponding to the MCG, and wait for the response from the network side during the operation of timer T316. The master base station that receives the MCG failure information RRC message can send an RRC reconfiguration message containing a synchronous reconfiguration information element to the UE to trigger the UE to switch to a new cell or send an RRC release message to release the UE's RRC connection. After receiving the above-mentioned RRC reconfiguration message or RRC release message, the UE stops T316 and performs corresponding operations according to the received response message (RRC reconfiguration message or RRC release message). If the received message is an RRC reconfiguration message containing a synchronous reconfiguration information element, the UE performs a switch to the target cell; if the received message is an RRC release message, the UE releases the RRC connection and leaves the RRC connection state. If T316 times out, the UE initiates an RRC re-establishment procedure. In this disclosure, the MCG failure information procedure / mechanism and the fast MCG recovery procedure / mechanism and the fast MCG link recovery procedure / mechanism are equivalent.

[0032] Wireless link failure reporting mechanism:

[0033] In the NR system, the UE will generate and save a radio link failure report (RLF Report) when a radio link failure (RLF) or handover failure (HOF) occurs, and save the radio link failure information in the UE variable VarRLF-Report. Generally, the UE only saves the RLF information of the most recent connection failure (RLF or HOF) in the RLF report. After restoring the connection with the network side (such as through the RRC re-establishment process or the RRC establishment process for establishing a new connection), the UE can inform the network side through an RRC message that there is a valid radio link failure report (such as indicated by the rlf-InfoAvailable information element). After receiving the indication, the network side can request the UE to report its saved radio link failure report through an RRC message (such as the rlf-ReportReq information element in the UE information request UEInformationRequest message to indicate the request). The UE will report the saved radio link failure report (rlf-Report information element in the UE information response UEInformationResponse message) to the network side in the response RRC message. The radio link failure report obtained by the network side is used for network optimization, such as network coverage and mobility robustness optimization. The radio link failure report contains information related to the link failure, including the identifier and measurement results of the source cell, target cell or neighbor cell when the link failure occurs, location information, link failure type (RLF or HOF), RLF reason, the time from connection failure to RLF report reporting (recorded as timeSinceFailure information element), the time from the last receipt of the handover command (handover initiation or handover execution) to the connection failure (recorded as timeConnFailure information element), the time between the next UE entering the RRC connection state after the connection failure and the re-establishment process fails (recorded as timeUntilReconnection information element), RRC re-establishment cell identifier, random access process information performed before the link failure, etc. RLF and HOF are collectively referred to as connection failure or link failure. The random access process information included in the RLF report refers to the random access common information, including the reference downlink frequency information associated with the random access process (such as the absolute frequency of Point A, subcarrier spacing, bandwidth location information locationAndBandwidth, etc.) and the RA information associated with each random access attempt arranged in chronological order.

[0034] Link recovery information reporting based on fast MCG recovery

[0035] As mentioned in the background technology section, one of the research projects of SON version 18 is the optimization of mobile robustness based on fast MCG recovery. In the conclusion reached by the current 3GPP working group, the UE records the link recovery related information corresponding to the fast MCG recovery process in the RLF report. The scenarios of mobile robustness optimization of fast MCG recovery under discussion include: Scenario 1: The UE fails to successfully initiate the fast MCG recovery process when MCG RLF occurs, such as because the SCG link is unavailable (SCG is in deactivation state, or SCG is suspended, or there is an ongoing PSCell addition and change process, etc.), the UE cannot initiate the fast MCG recovery process; Scenario 2: The UE initiates the fast MCG recovery process after MCG RLF occurs, and starts the T316 timer. During the T316 operation, before receiving the response message from the network side (such as RRC reconfiguration or RRC release), an SCG failure occurs, such as SCG RLF caused by link channel quality; Scenario 3: The UE has MCG After RLF, a fast MCG recovery process is initiated, the T316 timer is started, and a fast MCG recovery failure occurs due to T316 timeout; Scenario 4: After MCGRLF occurs, the UE initiates a fast MCG recovery process, starts the T316 timer, and successfully receives a response message from the base station such as RRC reconfiguration before T316 times out. The UE performs a handover to the target cell according to the RRC reconfiguration. In this scenario, T316 does not time out but is about to time out, so Scenario 4 is also understood as a situation where the fast MCG recovery process is close to failure. Regarding the mobility optimization in the above scenarios, the conclusion reached by the RAN2 working group is that the UE will record one or more fast MCG recovery information and report it to the network side for the network side to optimize the mobility performance of the fast MCG recovery function. This fast MCG recovery information includes: T316 timeout indication, T316 duration (the time between sending the MCG failure information MCGFailureInformation message and receiving the RRC response message, such as the RRC reconfiguration message), SCG failure indication, and whether the SCG failure was caused by a random access reason, the number of RLC retransmissions reached, or timer T310 expired. The UE records this information in the RLF report.

[0036] During the fast MCG recovery process, during the operation of T316, if the UE receives an RRC reconfiguration message sent by the SCG containing synchronous reconfiguration for the SCG, the UE performs synchronous reconfiguration of the SCG (PSCell change). Before the synchronous reconfiguration of the SCG is completed, the UE cannot receive the fast MCG recovery response message sent by the MCG through the SCG link. If the SCG synchronous reconfiguration is successfully completed, the UE can send an MCGFailureInformation message through the new PSCell or SCG link after the PSCell change, or receive the fast MCG recovery response message (such as RRC reconfiguration or RRC release) sent by the MCG through the new PSCell or SCG link after the SCell change. If the SCG synchronous reconfiguration fails, the UE initiates the RRC re-establishment process, stops T316, and ends the fast MCG failure process. From the above, it can be seen that if the PSCell change process occurs during the fast MCG recovery process, because the UE cannot receive any message from the MCG through the SCG link during the PSCell change, it will delay the UE's reception of the fast MCG recovery impact message from the MCG. This may lead to the failure of the fast MCG recovery process or delay its success, such as entering the RRC re-establishment process after the PSCell change fails or entering the aforementioned scenario 3 or scenario 4 due to the delay of the PSCell change. Therefore, how to enhance the mobile robustness optimization problem of fast MCG recovery in the scenario where a PSCell change occurs during the fast MCG recovery process becomes an issue of concern in this disclosure.

[0037] The following embodiments provide solutions to the above problems. Unless otherwise specified, the embodiments are not mutually exclusive and can be combined, or some concepts or definitions can be common among the embodiments.

[0038] Example 1

[0039] This embodiment provides a link recovery information reporting method executed on a UE. Through the method described in this embodiment, when a PSCell change occurs during a fast MCG recovery process, the UE records the corresponding PSCell change information and reports the information to the network side, so that the network side can be informed of the PSCell change during the fast MCG recovery process, and can more accurately determine the cause of the fast MCG recovery failure or the cause of the fast MCG recovery being delayed, which is used to optimize the mobility robustness in the fast MCG recovery scenario.

[0040] The following is a detailed description of the embodiment 1 of the present disclosure. Figure 1 is a schematic flow chart showing a link recovery information reporting method in the embodiment 1 of the present disclosure. As shown in Figure 1 , the link recovery information reporting method in the embodiment 1 of the present disclosure may include the following steps.

[0041] Step 101: The UE initiates a fast MCG recovery process.

[0042] As previously mentioned, when the UE detects an MCG RLF, if timer T316 is configured and the SCG link is available (the SCG is not in deactivated state, SCG transmission is not suspended, and there is no ongoing PSCell addition or change process), the UE initiates the fast MCG recovery procedure to perform link recovery. Therefore, it is clear that the UE has experienced an MCG link failure RLF before initiating the MCG recovery procedure.

[0043] Step 102: The UE includes one or more of the following information in the SON report:

[0044] The first information is used to indicate that a PSCell change has occurred during the fast MCG recovery process;

[0045] The second information is used to record the time from the successful completion of the PSCell change to the timeout of T316 when a PSCell change occurs during the fast MCG recovery process;

[0046] The third information is used to record the time elapsed from the successful completion of the PSCell change to the stop of T316 when a PSCell change occurs during the fast MCG recovery process;

[0047] The fourth information is used to record the time used to execute the PSCell change process when a PSCell change occurs during the rapid MCG recovery process, that is, the time run / experienced by the timer T304 associated with the PSCell change process, and the time from the start of the timer T304 to the stop or timeout of the timer T304. Optionally, the time information recorded in the fourth information is the time from the receipt of the PSCell change command to the completion of the PSCell change during the rapid MCG recovery process. The completion of the PSCell change may refer to the successful completion of the PSCell change, or it may refer to the failure of the PSCell change.

[0048] Optionally, the successful completion of the PSCell change means that the PSCell successfully accesses the target PSCell cell, for example, the random access process of the UE to the target PSCell triggered by the PSCell change is successfully completed.

[0049] Optionally, the PSCell change failure refers to the associated timer T304 expiring, or the UE's RRC layer receiving a random access failure (random access problem) indication from the bottom layer. The random access procedure is triggered by the PSCell change and executed on the target PSCell.

[0050] The fifth information is used to indicate that a PSCell change failure occurred during the fast MCG recovery process. Optionally, the fifth information indicates that the reason for the failure of the fast MCG recovery process is that a PSCell change failure occurred during the fast MCG recovery process.

[0051] The sixth information is used to indicate that a random access failure of the SCG (random access problem) occurred during the fast MCG recovery process, resulting in a failure of the PSCell change.

[0052] The seventh information is used to record the time elapsed from the successful completion of the PSCell change to the failure of the MCG recovery process when a PSCell change occurs during the fast MCG recovery process;

[0053] The eighth information is used to record the time elapsed from the successful completion of the PSCell change to the success of the fast MCG recovery process when a PSCell change occurs during the fast MCG recovery process;

[0054] The ninth information is used to indicate whether the PSCell change process occurring during the fast MCG recovery process is successful (successful or failed).

[0055] Optionally, the fast MCG recovery process is equivalent to the period when T316 is running or there is T316 running.

[0056] Optionally, the occurrence of the PSCell change may also be the execution of the PSCell change or the receipt of a command for the PSCell change. Optionally, the command for the PSCell change may be an RRC reconfiguration message containing a synchronization reconfiguration information element for the SCG or an LTM cell switch command MAC CE for triggering the LTM for the SCG. Optionally, the command for the PSCell change is received via a third signaling radio bearer (Signalling Radio Bearer 3, SRB3). The occurrence of the PSCell change is also equivalent to the timer T304 for the SCG being started or the timer T304 for the SCG being in a running state.

[0057] Optionally, when a PSCell change occurs during the fast MCG recovery process, the UE includes / sets one or more of the first to sixth information in the SON report. Therefore, between step 102 and step 101, the UE also receives a PSCell change command and performs a PSCell change process.

[0058] Optionally, when a fast MCG recovery failure occurs or a fast MCG recovery failure occurs due to a T316 timeout, the UE includes / sets second information in the SON report. Optionally, when the UE includes / sets T316 timeout information in the SON report, the UE includes / sets second information in the SON report. Optionally, the T316 timeout in the second information is equivalent to a fast MCG recovery process failure.

[0059] Optionally, when the UE receives a corresponding response message during the fast MCG recovery process, the UE includes a third information in the SON report. Optionally, the response message is an RRC reconfiguration message or an RRC release message containing a synchronization reconfiguration information element for the MCG. Optionally, the response message is an LTM cell switch command MAC CE for triggering the LTM of the MCG. When the UE receives the response message, the UE stops timer T316. Optionally, the UE stops timer T316 when initiating the RRC connection re-establishment process. Optionally, stopping T316 in the third information is equivalent to receiving a response message during the fast MCG recovery process.

[0060] Optionally, the SON report is an RLF report. The present disclosure does not limit the naming of the SON report.

[0061] Optionally, the UE saves various information / contents in the RLF report in the variable VarRLF-Report.

[0062] Example 2

[0063] This embodiment provides a method for reporting link recovery information executed on a UE. Using the method described in this embodiment, the UE can report the relevant information in the aforementioned embodiment to the base station in a link recovery information report, thereby providing the network with more accurate link recovery information. This embodiment provides a method for the UE to report the link recovery information report described in Example 1 through an RRC process.

[0064] The following describes embodiment 2 of the present disclosure in detail. FIG2 is a schematic flow chart showing a link recovery information reporting method in embodiment 2 of the present disclosure. As shown in FIG2 , the link recovery information reporting method in embodiment 2 of the present disclosure may include the following steps.

[0065] Step 201: The UE receives a UEInformationRequest message from the network side, which carries an instruction / request for requesting the UE to report a stored SON report.

[0066] Optionally, the SON report is an RLF report, and the indication / request for requesting the UE to report the stored SON report is an rlf-ReportReq information element set to true.

[0067] Optionally, the SON report is a successful handover report, and the indication / request for requesting the UE to report the stored SON report is a successHO-ReportReq information element set to true.

[0068] Step 202: The UE includes the content of the stored SON report in a UEInformationResponse message and sends the UEInformationResponse message to the network side. The SON report included in the RRC message includes one or more of the first to ninth information in the above-mentioned embodiment 1.

[0069] Optionally, the SON report is an RLF report, and the content of the SON report is included in an rlf-Report information element.

[0070] Optionally, the SON report is a successful handover report, and the content of the SON report is included in a successHO-Report information element.

[0071] Example 3

[0072] This embodiment illustrates the user equipment UE of the present disclosure. FIG3 is a block diagram of the user equipment UE involved in the present disclosure. As shown in FIG3 , the user equipment UE 30 includes a processor 301 and a memory 302. The processor 301 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 302 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory. The memory 302 stores program instructions. When the instructions are executed by the processor 301, the link recovery information reporting method described in detail in the present invention may be executed.

[0073] The method and related devices of the present disclosure have been described above in conjunction with preferred embodiments. Those skilled in the art will appreciate that the method shown above is merely exemplary. The method of the present disclosure is not limited to the steps and sequence shown above. The base station and user equipment shown above may include more modules, for example, modules that can be developed or will be developed in the future and can be used for the base station, MME, or UE, etc. The various identifiers shown above are merely exemplary and not restrictive, and the present disclosure is not limited to the specific information elements used as examples of these identifiers. Those skilled in the art may make many changes and modifications based on the teachings of the illustrated embodiments.

[0074] The program running on the device according to the present disclosure may be a program that controls a central processing unit (CPU) to enable a computer to implement the functions of the embodiments of the present disclosure. The program or the information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems.

[0075] The program for realizing each embodiment function of the present disclosure can be recorded on a computer-readable recording medium. The corresponding function can be realized by making a computer system read the program recorded on the recording medium and executing these programs. The so-called "computer system" herein can be a computer system embedded in the device, and can include an operating system or hardware (such as a peripheral device). "Computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a short-term dynamic storage program recording medium or any other recording medium that is computer-readable.

[0076] The various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (e.g., single-chip or multi-chip integrated circuits). The circuits designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above circuits may be digital circuits or analog circuits. In the case where new integrated circuit technologies have emerged to replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

[0077] Furthermore, the present disclosure is not limited to the above-described embodiments. Although various examples of the embodiments have been described, the present disclosure is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0078] As described above, the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above-mentioned embodiments, and the present disclosure also includes any design changes that do not deviate from the main purpose of the present disclosure. In addition, various modifications can be made to the present disclosure within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present disclosure. In addition, components with the same effect described in the above-mentioned embodiments can be replaced with each other.

Claims

1. A link recovery information reporting method, comprising: The user equipment UE initiates a fast master cell group MCG recovery process; Execute the primary and secondary cell PSCell change process; Save the link recovery information of the primary and secondary cell PSCell change in the self-optimizing network SON report; The link recovery information of the PSCell change includes one or more of the following information: The first information is used to indicate that a PSCell change has occurred during the fast MCG recovery process; The second information is used to record the time from the successful completion of the PSCell change to the T316 timeout during the fast MCG recovery process; The third information is used to record the time from the successful completion of the PSCell change to the stop of T316 during the fast MCG recovery process; The fourth information is used to record the time used to execute the PSCell change process during the fast MCG recovery process; The fifth message is used to indicate that a PSCell change failure occurred during the fast MCG recovery process; The sixth information is used to indicate that a PSCell change failure occurred due to a random access failure of the SCG during the fast MCG recovery process.

2. The link recovery information reporting method according to claim 1, wherein: The time taken for the PSCell change process is the time elapsed by the timer T304 associated with the PSCell change process.

3. The link recovery information reporting method according to claim 1, wherein: The successful completion of the PSCell change means that the random access process to the target PSCell triggered by the PSCell change is successfully completed; The PSCell change failure is caused by the timer T304 associated with the PSCell change timing out, or the radio resource control RRC layer of the UE receiving a random access failure indication from the bottom layer.

4. The link recovery information reporting method according to claim 1, wherein: During the fast MCG recovery process, timer T316 is running.

5. The link recovery information reporting method according to claim 1, wherein: The occurrence of the PSCell change is receiving a command for the PSCell change; and, The command for PSCell change is an RRC reconfiguration message containing a synchronization reconfiguration information element for a secondary cell group SCG or a mobility LTM cell change command for triggering a layer 1 and layer 2 triggered SCG.

6. The link recovery information reporting method according to claim 1, wherein: When fast MCG recovery failure occurs due to expiration of timer T316, the UE includes second information in the SON report.

7. The link recovery information reporting method according to claim 1, wherein: When receiving the response message in the fast MCG recovery procedure, the UE includes third information in the SON report; and The response message is an RRC reconfiguration message containing a synchronization reconfiguration information element for the MCG, or an RRC release message, or an LTM cell switch command for triggering the MCG.

8. The link recovery information reporting method according to claim 1, wherein: The link information reporting method further includes: The UE receives a UEInformationRequest message from the network side, where the UEInformationRequest message carries an indication / request for requesting the UE to report a stored SON report; and The UE includes the content of the stored SON report including one or more of the first information to the sixth information in a UEInformationResponse message, and sends the UEInformationResponse message to the network side.

9. The link recovery information reporting method according to claim 1 or claim 8, wherein: The SON report is a RLF report; the UE stores the information in the RLF report in the variable VarRLF-Report.

10. A user equipment, comprising: processor; as well as A memory, wherein instructions are stored in the memory; Wherein, when the instruction is executed by the processor, the user equipment executes the link recovery information reporting method according to any one of claims 1-9.

Images