Link failure information reporting method and user equipment

Abstract

The invention provides a link failure information reporting method and user equipment. The link failure information reporting method comprises the following steps: user equipment UE generates radio link failure of a main cell group MCG, and releases successful main and auxiliary cell addition change report SPR configuration configured by a main base station MN; initiating a rapid main cell group MCG recovery process; executing a PSCell change process of the primary and secondary cells; the self-optimization network SON report comprises the PSCell information of the source primary and secondary cells or the target PSCell information of the PSCell change occurring in the rapid MCG recovery process.

Description

Technical Field

[0001] The present disclosure relates to the technical field of wireless communications, and more specifically, 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 on 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 project is to further enhance the network data collection process in the NR system based on Release 17 to better achieve the purpose of self-organizing and self-optimizing the network and minimizing drive tests. The specific objectives of the research include realizing the mobile performance optimization mechanism under the fast master cell group (MCG) recovery mechanism and the self-optimization of the secondary cell group link mobility performance in the dual connection scenario.

[0003] The present disclosure proposes solutions to the problem of how to implement link failure information reporting under a fast MCG recovery mechanism in an NR system and the problem of link failure information reporting of a secondary cell group in a dual connection scenario. Summary of the invention

[0004] The purpose of the embodiments of the present disclosure is to propose a solution to the problem of link failure information reporting under the fast MCG recovery mechanism in the NR system and the problem of link failure information reporting of the secondary cell group in the dual connection scenario. More specifically, the present disclosure proposes a solution to the problem of link information reporting in the case of a change of primary and secondary cells when executing a fast MCG recovery process in the NR system and a solution to the problem of link failure information reporting when the secondary cell group change fails due to a listening failure.

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

[0006] According to the first aspect of the present disclosure, a link failure information reporting method is proposed, including: a main cell group MCG wireless link failure RLF occurs in a user equipment UE; a fast main cell group MCG recovery process is initiated; a primary and secondary cell PSCell change fails during the fast MCG recovery process; and link failure information of the primary and secondary cell PSCell change is saved in the RLF report; wherein the link failure information of the PSCell change includes one or more of the following information: a first fast MCG recovery failure information, which is a source PSCell identifier where the PSCell change occurs; and a second fast MCG recovery failure information, which is a target PSCell identifier where the PSCell change occurs.

[0007] In the link failure information reporting method of the first aspect above, optionally, when the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to the failure of synchronous reconfiguration of the secondary cell group SCG, the first fast MCG recovery failure information or the second fast MCG recovery failure information is included in the RLF report; or, when the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to the SCG random access problem and the timer T304 used for the SCG is running when the SCG failure is declared, the first fast MCG recovery failure information or the second fast MCG recovery failure information is included in the RLF report; or, when the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to the SCG's pre-call listen LBT failure and the timer T304 used for the SCG is running when the SCG failure is declared, the UE includes the first fast MCG recovery failure information or the second fast MCG recovery failure information in the RLF report.

[0008] In the link failure information reporting method of the first aspect above, optionally, the PSCell identifier is a global cell identifier GCI; or a physical cell identifier PCI and a carrier frequency.

[0009] In the link failure information reporting method of the first aspect above, optionally, if the UE determines that there is a successful PSCell addition change report SPR configuration configured by the main base station MN, the SPR configuration configured by the main base station MN is released.

[0010] According to the second aspect of the present disclosure, a link failure information reporting method is proposed, including: a secondary cell group SCG failure occurs in a user equipment UE; a fast secondary cell group SCG failure information process is initiated; the sending of an SCG failure information message SCGFailureInformation message is initiated; the SCG failure type is set to a pre-call listen LBT failure; and the content of the SCGFailureInformation message is set according to whether there is a timer T304 running when the SCG failure occurs.

[0011] In the link failure information reporting method of the second aspect above, optionally, if timer T304 is running when the SCG failure is declared, the UE performs one or more of the following operations: setting the RA information to the relevant information of the executed random access process; setting the failed cell identifier to the target PSCell identifier of the failed PSCell change; setting the previous cell identifier to the source PSCell identifier associated with the last received RRC reconfiguration message containing synchronous reconfiguration of the SCG. Otherwise, the UE performs one or more of the following operations: setting the failed cell identifier to the identifier of the PSCell where the SCG failure is declared; if the UE has received a radio resource control RRC reconfiguration message containing synchronous reconfiguration of the SCG before entering the PSCell where the SCG failure is declared, then setting the previous cell identifier to the source PSCell identifier associated with the last received RRC reconfiguration message containing synchronous reconfiguration of the SCG.

[0012] In the link failure information reporting method of the second aspect above, optionally, the timer T304 is a timer T304 for a secondary cell group SCG; when the timer T304 is running, the UE has an ongoing PSCell addition or change process.

[0013] According to a third 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 failure information reporting method described in the context. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] 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:

[0015] Figure 1 It is a schematic flow chart showing the link failure information reporting method in Embodiment 1 of the present disclosure.

[0016] Figure 2 It is a schematic flowchart showing the link failure information reporting method in Embodiment 2 of the present disclosure.

[0017] Figure 3It is a schematic flowchart showing the link failure information reporting method in Embodiment 3 of the present disclosure.

[0018] Figure 4 is a block diagram showing a user equipment UE involved in the present disclosure.

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

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

[0021] In the present disclosure, the terms "include" and "comprising" and their derivatives are intended to include but not be limited; the term "or" is inclusive, meaning and / or. The terms "if", "if", "in the case of" and "when" are interchangeable.

[0022] In this specification, the various embodiments described below for describing the principles of the present disclosure are merely illustrative and should not be interpreted in any way as limiting the scope of the disclosure. The following description with reference to the accompanying drawings is used to help fully understand 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 are omitted. In addition, throughout the accompanying drawings, the same reference numerals are used for similar functions and operations.

[0023] The following takes the NR mobile communication system and its subsequent evolutionary versions as example application environments, and specifically describes 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 more other wireless communication systems. Unless otherwise specified, the concepts of cell and base station can be interchanged; cell, beam (beamm), and transmission point (Transmission Point, TRP) can be interchanged. A switching command is equivalent to a radio resource control (Radio Resource Control, RRC) message containing a switching command, which refers to an RRC message or a configuration in an RRC message that triggers the UE to perform a switch. Cancellation, release, deletion, clearing, and clearing can be replaced. Execution, use, and application are replaceable. Configuration and reconfiguration can be replaced. Monitoring (monitor) and detection (detect) are replaceable. Initiate (initiate) and trigger (trgger) are replaceable.

[0024] 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 (Reconfiguration with sync) information element for the primary cell group MCG. At this time, handover, synchronous reconfiguration of MCG and synchronous reconfiguration of PSCell can be replaced. After the NR system of version 18 introduced the cell switch mechanism of layer 1 layer 2 triggered mobility (L1 / L2-triggered mobility, LTM), the handover also included 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 (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. The PSCell addition or change command is an RRC reconfiguration message that contains the synchronous reconfiguration (IReconfigurationwithsync) information element for the secondary cell group SCG. At this time, the PSCell addition or change, the synchronous reconfiguration of the SCG, and the synchronous reconfiguration of the PSCell can be replaced.

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

[0026] Dual Connectivity:

[0027] In order to improve the data transmission efficiency of UE, UE establishes links with two base stations at the same time, that is, the wireless resources used by UE are provided by different schedulers located in the two base stations. The wireless access between these two base stations and 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 these two base stations, one is called the master base station (Master Node, MN) or MgNB, MeNB, and the service cell group under the master base station is called the master cell group (Master Cell Group, MCG); the other is called the secondary base station (SecondaryNode, SN) or SgNB, SeNB, and the service cell group under the secondary base station is called the secondary cell group (Secondary Cell Group, SCG). When the master base station is LTE and the secondary base station is NR, the DC is called EN-DC (using 4G core network) or NGEN-DC (using 5G core network); when the master base station and the secondary base station are both NR, the DC is called NR-DC. MCG includes a primary cell (PCell) and optionally one or more secondary cells (SCell). PCell operates on the main frequency, and the UE performs the initial connection establishment process or the connection re-establishment process through the main frequency. SCG includes a PSCell and optionally one or more SCells. PSCell refers to the SCG cell where 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 two paths, MCG and SCG. 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 SRBl and SRB3 at the same time.

[0028] Successfully added PSCell change report

[0029] Successful PScell ​​addition & change Report (SPR) means that after a PSCell synchronous reconfiguration process is successfully completed, the UE saves the relevant information of the successfully completed synchronous reconfiguration event in the corresponding UE variable, and reports it to the network side for PSCell mobility robustness optimization.

[0030] The network side configures the SPR configuration, i.e., the triggering conditions of SPR (such as the threshold values ​​corresponding to T310, T312, and T304) to the UE. Only when one or more of the configured triggering conditions are met (such as when the PSCell synchronization reconfiguration command is received, the percentage of the running value of timer T310 (or timer T312) of the source PSCell / SCG and the configuration value of T310 (or T312) exceeds the configured corresponding threshold value, and the percentage of the running value of T304 and the configuration value of T304 when the PSCell synchronization reconfiguration is successfully completed exceeds the configured corresponding threshold value), the UE records the relevant information of the successful PSCell synchronization reconfiguration event in the SPR (such as the source PSCell identifier and measurement results, the target PSCell identifier and measurement results, the neighboring cell measurement results, and the SPR triggering cause, etc.). The trigger conditions related to the source PSCell cell, such as the T310 threshold value or the T312 threshold value, are configured by the source PSCell / SN to the UE, and the trigger conditions related to the target cell, such as the T304 threshold value, are configured by the target cell to the UE. The MN can configure the SPR configuration to the UE for the PSCell addition change process initiated by the MN; the SN can also configure the SPR configuration to the UE for the PSCell change process initiated by the SN.

[0031] Fast MCG link recovery mechanism:

[0032] 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 MCG of the UE or the UE fails to perform a handover process (HOF) (i.e., the timer T304 of the MCG 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). The master base station (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 the RRC re-establishment process. In the present disclosure, the MCG failure information process / mechanism, the fast MCG recovery process / mechanism, the fast MCG link recovery process / mechanism and the MCG recovery process are equivalent.

[0033] Wireless link failure reporting mechanism:

[0034] 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 in the primary cell group, and save the radio link failure information in the UE variable VarRLF-Report. In general, 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 (the 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 source cell, target cell or neighbor cell identification and measurement results, 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 failure of the re-establishment process (recorded as timeUntilReconnection information element), RRC re-establishment cell identification, 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 contained 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.

[0035] In the current NR system, the reporting of SCG failure information is implemented through the SCG failure information process. When one or more of the following conditions are met, if the MCG and SCG transmissions are not suspended at this time, the UE will initiate the SCG failure information process to report the failure of the SCG to the network side: monitoring the RLF of the SCG, monitoring the beam failure of the PSCell when the SCG is deactivated, the synchronization reconfiguration failure of the SCG, the SCG configuration failure, and the receipt of the integrity check failure indication associated with the SRB3 from the bottom layer. During the SCG failure process, the UE usually suspends the SCG transmission, resets the SCG MAC entity, stops the running timer T304, and sends an RRC message of SCGFailureInformation to the network side through the MCG link. According to the content of SCGFailureInformation, the MCG can send an RRC message containing the synchronization reconfiguration of the SCG to the UE, trigger the change of the PSCell, and restore the SCG link; or send an RRC message containing the release of the SCG link indication to the UE to release the SCG. In addition, the network side can also use the information in SCGFailureInformation for SCG mobility optimization. The information in SCGFailureInformation in R17 version includes: failure type, measurement result corresponding to the measurement configuration associated with SCG, measurement result corresponding to the measurement configuration associated with MCG, location information, failed PSCell identifier failedPSCellId, previous PSCell identifier previousPSCellId, timeSCGFailure indicating the time elapsed from receiving the RRC reconfiguration message of the most recent SCG synchronous reconfiguration, and information related to the random access process performed perRAInfoList.

[0036] Link failure information reporting based on fast MCG recovery

[0037] As described 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: After the UE MCG RLF occurs, the fast MCG recovery process is initiated and the T316 timer is started. During the operation of T316, 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. In the conclusion reached by the RAN2 working group, the UE will record one or more fast MCG recovery (failure) information and record it in the RLF report and report it to the network side for the network side to optimize the mobile performance of the fast MCG recovery function. These fast MCG recovery information include: T316 timeout indication, failed PSCell cell identifier, SCG failure indication and the cause of SCG failure.

[0038] As mentioned above, when fast MCG recovery fails, the UE records the reason for the fast MCG recovery failure in the RLF report. If the fast MCG recovery failure is caused by SCG failure, the UE will also record the failed PSCell identifier in the RLF report. When the reason for the failure of fast MCG recovery is SCG failure, and the SCG failure occurs during the PSCell addition or change process, how to set the failed PSCell identifier becomes a concern of the present disclosure. Furthermore, when a PSCell change occurs during the fast MCG recovery process, because the MCG is in a link failure RLF state at this time, if the UE has an SPR configuration configured by the MN at this time, then how to avoid the UE from recording the SPR information of the PSCell change process based on the SPR configuration configured by the MN is also a concern of the present disclosure. In addition, in the existing mechanism, when the SCG fails, the UE will record different failure information in the SCGFailureInformation when the SCG failure is due to a PSCell addition or change failure and when the SCG failure is caused by other reasons. In one case, the UE has a consistent uplink Listen Before Talk (LBT) failure, but the consistent uplink LBT failure occurs during the SCG synchronous reconfiguration process (that is, timer T304 for SCG is in running state). In this case, how to record the SCG failure information in SCGFailureInformation is also a problem that needs to be solved in the present disclosure.

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

[0040] Example 1

[0041] This embodiment provides a link failure information reporting method executed on a UE. Through the method described in this embodiment, when a PSCell synchronization reconfiguration failure occurs in the UE during a fast MCG recovery process or when / before initiating a fast MCG recovery process, the source PSCell identifier or the target PSCell identifier is included in the RLF report, so that the network side can know the source cell or target cell associated with the PSCell synchronization reconfiguration failure that occurs during the fast MCG recovery process or before initiating the fast MCG recovery process, and can more accurately determine the network status and the cause of the fast MCG recovery failure when the fast MCG recovery fails, which is used to optimize the mobility robustness in the fast MCG recovery scenario.

[0042] As an example, Figure 1is a schematic flow chart showing a link failure information reporting method in Embodiment 1 of the present disclosure, such as Figure 1 As shown, the link failure information reporting method in Embodiment 1 of the present disclosure may include the following steps.

[0043] Step 1: UE generates MCG RLF.

[0044] Step 2: The UE initiates a fast MCG recovery process (ie, MCG failure information process) and starts the corresponding timer T316.

[0045] Step 3: If an SCG failure occurs during the operation of timer T316, the UE considers that the fast MCG recovery process has failed and records one or more of the following information in the RLF report:

[0046] The first fast MCG recovery failure information is the source PSCell identifier where the SCG failure occurred;

[0047] The second fast MCG recovery failure information is the target PSCell identifier where the SCG failure occurred.

[0048] Preferably, when the SCG failure is caused by SCG synchronization reconfiguration failure or PSCell synchronization reconfiguration failure (that is, the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to SCG synchronization reconfiguration failure), the UE includes the above-mentioned first fast MCG recovery failure information or the second fast MCG recovery failure information in the RLF report.

[0049] Optionally, when the SCG failure is due to a random access problem of the SCG (i.e., the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to the SCG random access problem) and the timer T304 used for the SCG is running when the SCG failure is declared, or when the SCG failure is due to a persistent uplink LBT failure problem of the SCG (i.e., the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to the SCG's LBT failure) and the timer T304 used for the SCG is running when the SCG failure is declared, the UE includes the above-mentioned first fast MCG recovery failure information or the second fast MCG recovery failure information in the RLF report.

[0050] Optionally, when the UE supports RLF reporting for the fast MCG grayscale process, the UE includes the above-mentioned first fast MCG recovery failure information or second fast MCG recovery failure information in the RLF report.

[0051] Optionally, the source PSCell identifier is the global cell identity (global cell identity of the PSCell) of the source PSCell where the SCG synchronization reconfiguration process occurs; optionally, the source PSCell identifier is the physical cell identity (physical cell identity) and carrier frequency (carrier frequency) of the source PSCell where the SCG synchronization reconfiguration process occurs.

[0052] Optionally, the target PSCell identifier is the global cell identity of the PSCell where the SCG synchronization reconfiguration process occurs; optionally, the target PSCell identifier is the physical cell identity and carrier frequency of the target PSCell where the SCG synchronization reconfiguration process occurs.

[0053] The above example provides the implementation content when the SCG failure occurs during the fast MCG recovery process (i.e., the aforementioned scenario 2). In another example, when the SCG failure occurs before or when the fast MCG recovery process is initiated (i.e., the aforementioned scenario 1), the link failure information reporting method in this embodiment includes the following steps:

[0054] Step 1: UE has SCG failure.

[0055] Step 2: UE generates MCG RLF.

[0056] Step 3: Due to SCG failure, the SCG link is unavailable (in suspended state), the UE cannot initiate the fast MCG recovery process (i.e., MCG failure information process), resulting in the failure of the fast MCG recovery process (initiation), and the UE initiates the RRC re-establishment process.

[0057] Step 4: In step 3, the UE considers that the fast MCG recovery process fails, and records one or more of the following information in the RLF report:

[0058] The first fast MCG recovery failure information is the source PSCell identifier where the SCG failure occurred;

[0059] The second fast MCG recovery failure information is the target PSCell identifier where the SCG failure occurred.

[0060] Optionally, step 1 and step 2 may occur simultaneously.

[0061] Example 2

[0062] This embodiment proposes a link failure information reporting (corresponding SPR configuration management) method implemented on the UE. In this embodiment, when an MCG failure occurs, the UE releases the saved SPR configuration configured by the MN. The advantage of this is that it can prevent the UE from generating or saving unnecessary SPRs based on the SPR configuration configured by the MN when the PSCell is changed in the fast MCG recovery process initiated after the MCG failure. When the MCG is in a failed state, the UE is actually in a state of no main cell connection, then it is not necessary or appropriate to use the SPR configuration configured by the MCG at this time. Therefore, through this embodiment, it can be avoided that the UE generates or saves unnecessary SPRs based on the SPR configuration configured by the MN.

[0063] As an example, Figure 2 is a schematic flow chart showing a link failure information reporting method in Embodiment 2 of the present disclosure, such as Figure 2 As shown, the link failure information reporting method in Embodiment 2 of the present disclosure may include the following steps.

[0064] Step 1: UE generates MCG RLF.

[0065] Step 2: If there is an SPR configuration configured by the MN on the UE, the UE releases the SPR configuration configured by the MN.

[0066] Obviously, before step 1, the UE also receives the SPR configuration configured by the MN. That is, the UE receives the otherconfig information element configured by the MN and contained in the RRC message. If the otherconfig contains the SPR configuration (successPSCell-Config information element), the UE considers that the MN / MCG has configured the SPR configuration.

[0067] The SPR configuration refers to the configuration used by the UE to report successful PSCell addition or change information to the network side. Optionally, the SPCR configuration includes a T310 threshold value for PSCell, a T312 threshold value for PSCell, or a T304 threshold value for SCG. Optionally, the threshold value is a percentage threshold value. For example, the T310 threshold value for PSCell indicates the percentage threshold between the running value (elapsed value) of T310 for PSCell and the configured value of T310; the T312 threshold value for PSCell indicates the percentage threshold between the running value (elapsed value) of T312 for PSCell and the configured value of T312; the T304 threshold value for SCG indicates the percentage threshold between the running value (elapsed value) of T304 for SCG and the configured value of T304. The UE determines whether to record the relevant information of a PSCell addition and change process in the UE variable corresponding to the SPR according to the SPR configuration. For example, when the SPR configuration includes the T310 threshold value, it means that when the UE receives the PSCell change command and before the synchronous reconfiguration of the PSCell is executed (or when the PSCell change is initiated), the ratio of the running value of T310 of the source PSCell to the configuration value of T310 exceeds the configured threshold value, the UE considers that the SPR trigger condition is met. When the SPR configuration includes the T312 threshold value, it means that when the UE receives the PSCell change command and before the synchronous reconfiguration of the PSCell is executed (or when the PSCell change is initiated), the ratio of the running value of T312 of the source PSCell to the configuration value of T312 exceeds the configured threshold value, the UE considers that the SPR trigger condition is met. When the SPR configuration includes a T304 threshold value, it means that when the ratio of the running value of T304 to the configuration value of T304 included in the PSCell change command exceeds the configured threshold value, the UE considers that the SPR trigger condition is met. When the SPR trigger condition is met, the UE sets and saves the SPR information of the PSCell synchronization reconfiguration event.

[0068] Example 3

[0069] This embodiment proposes a link failure information reporting method implemented on the UE. In this embodiment, when the UE has an SCG failure due to a consistent uplink LBT failure, the UE determines how to set different link failure information in the SCGFailureInformation message according to whether the LBT failure occurs during the SCG synchronous reconfiguration process. Through this method, the network side can know whether the LBT failure occurs during the SCG synchronous reconfiguration process, and enhance the SCG mobility optimization problem according to different information in the SCGFailureInformation message.

[0070] As an example, Figure 3 is a schematic flow chart showing a link failure information reporting method in Embodiment 3 of the present disclosure, such as Figure 3 As shown, the link failure information reporting method in Embodiment 3 of the present disclosure may include the following steps.

[0071] Step 1: The UE encounters an SCG failure and initiates an SCG failure information process to report the SCG failure to the network side.

[0072] During the SCG failure information process, the UE initiates the sending of the SCGFailureInformation message.

[0073] Step 2: The UE sets the content of the SCGFailureInformation message as follows:

[0074] Contains the corresponding SCG failure reason or SCG failure type (identified by the failureType information element);

[0075] If the UE supports SCG failure (information reporting) for mobility robustness optimization, if the SCG failure type is set to LBT failure (identified by the scg-lbtFailure information element) and timer T304 is running when the SCG failure was declared, the UE performs one or more of the following operations:

[0076] Set the RA information (perRAInfoList information element) to the information related to the random access procedure performed;

[0077] Set the failed cell identifier (failedPSCellId information element) to the target PSCell identifier of the failed PSCell change;

[0078] Set the previous PSCellId to the source PSCell Id associated with the last received RRC reconfiguration message containing synchronous reconfiguration of the SCG;

[0079] Set the time information to the time that elapsed from the last executed RRC reconfiguration message containing SCG synchronization reconfiguration to the declaration of SCG failure.

[0080] Otherwise, i.e. if the SCG failure type is set to LBT failure (identified by the scg-lbtFailure information element) and timer T304 was not running when the SCG failure was declared, the UE performs one or more of the following operations:

[0081] Set the failed cell identity (failedPSCellId information element) to the identity of the PSCell where the SCG failure is declared;

[0082] If the UE has received an RRC reconfiguration message containing SCG synchronous reconfiguration before entering the PSCell that declares SCG failure, then the previous cell identifier (previousPSCellId) is set to the source PSCell identifier associated with the last received RRC reconfiguration message containing SCG synchronous reconfiguration; the time information is set to the time elapsed from the last executed RRC reconfiguration message containing SCG synchronous reconfiguration to the declaration of SCG failure.

[0083] Optionally, the timer T304 is T304 for SCG.

[0084] Optionally, the timer T304 being running refers to being in the process of SCG synchronous reconfiguration or the process of PSCell addition or change.

[0085] Optionally, the source PSCell identifier is a physical cell identity and a carrier frequency of the PSCell; optionally, the source PSCell identifier may also be a global cell identity of the source PSCell;

[0086] Optionally, the target PSCell identifier is a physical cell identifier and a carrier frequency of the target PSCell; optionally, the target PSCell identifier may also be a global cell identifier of the target PSCell.

[0087] Example 4

[0088] This embodiment illustrates the user equipment UE of the present disclosure. Figure 4 is a block diagram showing a user equipment UE involved in the present disclosure. Figure 4 As shown, the user equipment UE40 includes a processor 401 and a memory 402. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 402 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 memories, etc. The memory 402 stores program instructions. When the instructions are executed by the processor 401, the link failure information reporting method described in detail in the present invention may be executed.

[0089] The method of the present invention and the equipment involved have been described above in conjunction with the preferred embodiments. It will be appreciated by those skilled in the art that the method shown above is exemplary only. The method of the present invention 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 developed in the future and can be used for base stations, MMEs, or UEs, etc. The various identifiers shown above are exemplary only and not restrictive, and the present invention 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.

[0090] The program running on the device according to the present disclosure may be a program that enables a computer to implement the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU). The program or 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.

[0091] The program for realizing the functions of each embodiment of the present disclosure can be recorded on a computer-readable recording medium. The corresponding functions 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 recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.

[0092] The various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (e.g., monolithic or multi-chip integrated circuits). Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), 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.

[0093] In addition, the present disclosure is not limited to the above-mentioned 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.

[0094] As mentioned 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 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 changes can be made to the present disclosure within the scope of the claims, and the 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, the components with the same effect described in the above embodiments can be replaced by each other.

Claims

1. A link failure information reporting method, comprising: A radio link failure (RLF) occurs in the primary cell group (MCG) of the user equipment UE; Initiate a fast master cell group MCG recovery process; The primary and secondary cell PSCell change fails during the fast MCG recovery process; Save the link failure information of the primary and secondary cell PSCell change in the RLF report; The link failure information of the PSCell change includes one or more of the following information: The first fast MCG recovery failure information is the source PSCell identifier where the PSCell change occurred; The second fast MCG recovery failure information is the target PSCell identifier where the PSCell change occurred.

2. The link failure information reporting method according to claim 1, wherein: When the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to the failure of SCG synchronization reconfiguration, the first fast MCG recovery failure information or the second fast MCG recovery failure information is included in the RLF report; or When the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to SCG random access problem and the timer T304 for SCG is running when the SCG failure is declared, the first fast MCG recovery failure information or the second fast MCG recovery failure information is included in the RLF report; or When the fast MCG recovery failure cause mcgRecoveryFailure-Cause is set to the pre-call listening LBT failure of the SCG and the timer T304 used for the SCG is running when the SCG failure is declared, the UE includes the above-mentioned first fast MCG recovery failure information or the second fast MCG recovery failure information in the RLF report.

3. The link failure information reporting method according to claim 1, wherein: The PSCell identifier is a global cell identifier GCI; or Physical cell identifier PCI and carrier frequency.

4. The link failure information reporting method according to claim 1, wherein: If the UE determines that it is configured with the successful PSCell addition change report SPR configuration configured by the master base station MN, the SPR configuration configured by the master base station MN is released.

5. A link failure information reporting method, comprising: A secondary cell group (SCG) failure occurs in the user equipment UE; Initiate fast secondary cell group SCG failure information process; Initiate the sending of SCG failure information message SCGFailureInformation message; Set the SCG failure type to listen-before-call LBT failure; and set the content of the SCGFailureInformation message according to whether there is a timer T304 running when the SCG failure occurs.

6. The link failure information reporting method according to claim 5, wherein: If timer T304 is running when SCG failure is declared, the UE performs one or more of the following operations: The RA information is set to the information related to the random access procedure performed; Set the failed cell ID to the target PSCell ID of the failed PSCell change; Set the previous cell ID to the source PSCell ID associated with the last received RRC reconfiguration message containing SCG synchronization reconfiguration; Otherwise, the UE performs one or more of the following operations: Set the failed cell ID to the ID of the PSCell where the SCG failure is declared; If the UE has received a radio resource control RRC reconfiguration message containing SCG synchronization reconfiguration before entering the PSCell that declares SCG failure, the previous cell identifier is set to the source PSCell identifier associated with the last received RRC reconfiguration message containing SCG synchronization reconfiguration.

7. The link failure information reporting method according to claim 5 or 6, wherein: The timer T304 is a timer T304 for the secondary cell group SCG; When the timer T304 is running, the UE is in the process of adding or changing a PSCell.

8. A user equipment, comprising: processor; as well as A memory, wherein instructions are stored in the memory; When the instructions are executed by the processor, the user equipment executes the link failure information reporting method according to any one of claims 1-7.

Images