WO2023179677A1

WO2023179677A1 - Radio link failure information reporting method, and user equipment

Info

Publication number: WO2023179677A1
Application number: PCT/CN2023/083113
Authority: WO
Inventors: 常宁娟; 刘仁茂
Original assignee: 夏普株式会社; 常宁娟
Priority date: 2022-03-25
Filing date: 2023-03-22
Publication date: 2023-09-28
Also published as: CN116847390A

Abstract

Provided in the present disclosure are a radio link failure information reporting method, and a user equipment. The method is an RLF information reporting method when a user equipment (UE) executes, after an RLF occurs in an MCG, a fast MCG recovery mechanism using an SCG. The method comprises the following steps: when an RLF occurs in an MCG, a UE initiating an MCG failure information flow, starting a timer T316, and sending an MCG failure information message to a base station by means of an SCG path; the UE receiving an RRC reconfiguration message of a handover command from the base station, executing synchronous reconfiguration to synchronize the RRC reconfiguration message with a target cell, and starting a timer T304; and when an HOF occurs, that is, when continuous failures occur with the RLF being followed by the HOF, the UE not recording the present HOF event in an RLF report variable, and storing, in the RLF report variable, information corresponding to an RLF event, and reporting the information to the base station.

Description

Wireless link failure information reporting method and user equipment

Technical field

The present disclosure relates to the field of wireless communication technology, and more specifically, the present disclosure relates to a wireless link failure information reporting method and corresponding user equipment when a primary cell group link is quickly restored.

Background technique

The 3rd Generation Partnership Project (3GPP) RAN#94 plenary meeting approved a new research project for the Release 18 technical standard (see non-patent document: RP-213553: New WID on further enhancement of data collection for SON(Self-Organising Networks)/MDT(Minimization of Drive Tests)in NR and EN-DC). The research purpose of this project is to enhance the network data collection process in the NR system based on the network self-optimization mechanism of version 17, so as to better realize the purpose of self-organizing self-optimizing network and minimizing drive testing. One of the specific technologies studied is an enhanced method for realizing failure information reporting under the fast primary cell group recovery mechanism.

This disclosure proposes a solution to the problem of how to implement failure information reporting under the fast primary cell group recovery mechanism in the NR system in version 18.

Contents of the invention

The purpose of the embodiments of the present disclosure is to propose a solution to the problem of how to implement failure information reporting in the NR system. More specifically, the present disclosure proposes a solution to the problem of recording failure information after the UE performs a fast Master Cell Group (MCG) recovery process in the NR system. Embodiments of the present disclosure provide a failure information reporting method executed in user equipment, corresponding user equipment, and a communication system.

According to the first aspect of the present disclosure, a wireless link failure information reporting method is proposed, in which the user equipment UE executes a fast MCG recovery mechanism using the secondary cell group SCG after a wireless link failure RLF occurs in the primary cell group MCG. RLF information report in case The reporting method includes the following steps:

When RLF occurs in MCG, the UE initiates the MCG failure information process, starts timer T316, and sends the MCG failure information message to the base station through the SCG path;

The UE receives the RRC reconfiguration message of the handover command from the base station, performs synchronization reconfiguration, synchronizes to the target cell, and starts timer T304;

When a handover failure HOF occurs, that is, when consecutive failures occur first in RLF and then HOF, the UE does not record this HOF event in the RLF report variable, but saves the information corresponding to the RLF event in the RLF report variable and reports it to the base station. .

According to the second aspect of the present disclosure, a wireless link failure information reporting method is proposed, in which the user equipment UE executes a fast MCG recovery mechanism using the secondary cell group SCG after a wireless link failure RLF occurs in the primary cell group MCG. The RLF information reporting method in this situation includes the following steps:

When a handover failure HOF occurs, that is, when consecutive failures occur first in RLF and then HOF, the UE records the information corresponding to the consecutive failures in the RLF report variable and reports it to the base station.

In the above wireless link failure information reporting method, preferably,

When a HOF occurs, if the corresponding handover process is initiated for fast MCG recovery, the UE saves the first information in the RLF report variable, and the first information is used to record this HOF and the previous RLF event. the time between.

In the above wireless link failure information reporting method, preferably,

When a HOF occurs, if the corresponding handover process is initiated for fast MCG recovery, the UE saves the second information in the RLF report variable, and the second information is used to indicate that an RLF event occurred before the HOF. .

In the above wireless link failure information reporting method, preferably,

During the RRC connection establishment process, when the UE receives the RRC establishment message, if there is available RLF or HOF information saved in the RLF report variable, the current PLMN is included in the PLMN identification list saved in the RLF report variable, and RLF report variable The reconnection cell identifier has not been set. If the UE determines that the RLF report variable is associated with a continuous failure event, the UE sets the third information in the RLF report variable to be indicated by the failed cell identifier saved in the RLF report variable. The time elapsed since the connection failures experienced in the cell began.

In the above wireless link failure information reporting method, preferably,

The connection failure experienced in the cell indicated by the failed cell identifier is an RLF used to trigger a fast MCG recovery procedure.

In the above wireless link failure information reporting method, preferably,

If the UE receives the UE information request message, which contains instruction information for requesting the UE to report the RLF report saved on it, then the UE sets the fourth information in the RLF report variable to the time elapsed since the first failure, and include the RLF report information in the RLF report variable in the corresponding UE information response message.

In the above wireless link failure information reporting method, preferably,

When the UE receives the RRC connection reconfiguration message, if the RRC connection reconfiguration message is received as a response to the MCG failure information message, the UE sets the fifth information element in the RLF report variable to the value from the most recent RLF to the time the RRC is received. The time between connection reconfiguration messages.

In the above wireless link failure information reporting method, preferably, the following steps are also included:

The UE receives a UE information request message from the base station, which carries an instruction/request for requesting the UE to report the saved successful handover report;

The UE includes the contents of the saved successful handover report in the UE information response message and sends it to the base station.

According to a third aspect of the present disclosure, a user equipment UE is proposed, including: a processor; and a memory storing instructions; wherein the instructions execute the wireless link according to the context when executed by the processor. Failure information reporting method.

According to the above failure information reporting method and user equipment, the network side can learn the link failure situation in the entire process, thereby realizing the adjustment and optimization of mobility parameters.

Description of the drawings

For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following in conjunction with the accompanying drawings Description, where:

FIG. 1 is a flowchart illustrating a wireless link failure information reporting method performed by user equipment according to an embodiment of the present disclosure.

FIG. 2 is a flowchart illustrating a wireless link failure information reporting method performed by user equipment according to another embodiment of the present disclosure.

FIG. 3 is a block diagram showing user equipment UE according to the present disclosure.

In the drawings, the same or similar structures are identified with the same or similar reference signs.

Detailed ways

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 annexed drawings.

In this disclosure, the terms "include" and "contain" and their derivatives mean inclusion and not limitation; the term "or" is inclusive, meaning and/or.

In this specification, the various embodiments described below to describe the principles of the disclosure are illustrative only and should not be construed in any way to limit the scope of the disclosure. The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes various specific details to aid understanding, but these details should be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the disclosure. Additionally, descriptions of well-known functions and constructions are omitted for the sake of clarity and conciseness. Additionally, throughout the drawings, the same reference numerals are used for similar functions and operations.

The following uses the NR mobile communication system and its subsequent evolved versions as an example application environment to specifically describe multiple embodiments according to the present disclosure. However, it should be noted that the present disclosure is not limited to the following embodiments, but may be applicable to more other wireless communication systems. If there is no special explanation, in this disclosure, the concepts of cell and base station can be interchanged; handover refers to the change of the primary cell initiated by the network side, that is, the primary cell of the UE is changed from the source cell to the target cell, where the source cell and the target cell The cells can be the same cell or different cells. The source cell can also be called the source base station, or source beam (beam), source transmission point (Transmission point, TRP), source primary cell (Primary Cell, PCell),

Source master cell group (Master Cell Group, MCG); the target cell can also be called the target base station, or target beam, target transmission point, target master cell PCell, and target cell group MCG. The source cell refers to the connected cell serving the UE before the handover process is initiated, that is, the cell that sends the Radio Resource Control (Radio Resource Control, RRC) message to the UE for triggering the handover process. The target cell refers to the cell indicated by the target cell identifier included in the handover command, or described as the cell that performs downlink synchronization and random access during the handover process. The handover command described in this disclosure is used to trigger the UE to perform handover. In the NR system, it is an RRC reconfiguration message containing a synchronization reconfiguration (Reconfiguration with sync) information element. Furthermore, it is a RRC reconfiguration message containing a synchronization reconfiguration (Reconfiguration with sync) for the main cell group MCG. Reconfigurationwithsync) information element of the RRC reconfiguration message. Therefore, handover may also be called synchronous reconfiguration or synchronous reconfiguration of MCG. In the LTE system, it is an RRC connection reconfiguration message containing a mobility control information (MobilityControlInfo) information element. Wherein, the synchronization reconfiguration information element or the mobility control information information element may include the configuration information of the target cell, such as the target cell identity, the target cell frequency, the public configuration of the target cell such as system information, and the configuration information used by the UE to access the target cell. Random access configuration, UE security parameter configuration in the target cell, UE radio bearer configuration in the target cell, etc. For convenience of description, in this disclosure, the RRC reconfiguration message and the RRC connection reconfiguration message are the same; the response message, the RRC reconfiguration complete message, is the same as the RRC connection reconfiguration complete message. The handover command is equivalent to the RRC message containing the handover configuration, and refers to the RRC message that triggers the UE to perform handover or the configuration in the RRC message. Cancel, Release, Delete, Empty and Clear can be replaced. Execution, use and application are interchangeable. Configuration and reconfiguration can be replaced. Monitor and detect are interchangeable. The RRC re-establishment message is the same as the RRC connection re-establishment message; similarly, the response message RRC re-establishment complete message is the same as the RRC connection re-establishment complete message.

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

Handover configuration in NR system:

In the NR system, the RRC reconfiguration message used for the handover command carries the RRC configuration from the target base station, including but not limited to the following RRC configuration (for details, please refer to Chapter 6.2.2 in 3GPP Technical Standard Protocol 38.331):

- Measurement configuration (measconfig information element): used to configure intra-frequency, inter-frequency and inter-radio access technology measurements performed by the UE. Such as measurement object configuration, measurement reporting configuration, measurement gap configuration, etc.

-Cell group configuration (cellGroupConfig information element), used to configure the primary cell group or secondary cell group. Including the Radio Link Control (RLC) bearer configuration (rlc-bearerToAddModList information element and rlc-bearerToreleaselist information element) and medium access control (Medium Access Control, MAC) configuration corresponding to the data radio bearer/signaling radio bearer (MAC-cellgroupconfig information element), physical layer configuration, secondary cell add/modify/release configuration, special cell (Special cell, SpCell) configuration, etc. Among them, the SpCell configuration includes cell index number, handover information (reconfigurationWithSync information element), wireless link failure related timer and constant configuration, wireless link detection (Radio Link Monitoring, RLM) configuration, special cell-specific configuration, etc. The reconfigurationwithsync information element is similar to the mobility control information in the LTE system and contains handover-related information to achieve mobility. It includes the serving cell configuration public information, the UE's cell radio network temporary identifier C-RNTI in the target cell, and the handover process monitoring timer. T304 configuration, random access-specific configuration for random access process to the target cell, etc.

- Non-access layer specific information (dedicatedInfoNASList information element).

-Radio bearer configuration (radiobearerConfig information element), used to configure the service data application protocol layer (Service Data Application Protocol, SDAP) of the data radio bearer (Data Radio Bearer, DRB) and/or the signaling radio bearer (Signaling Radio Bearer, SRB) ) and the Packet Data Convergence Protocol layer (Packet Data Convergence Protocol, PDCP).

-Master key update configuration (masterKeyupdate information element).

Handover process in NR system:

User mobility in the connected state is mainly realized through the handover process, which refers to the process in which the UE in the RRC connected state changes the serving cell (primary cell). The general handover process includes the following stages: Stage 1: Measurement stage. The UE measures the wireless link corresponding to the serving cell or neighboring cell based on the configured measurement configuration. When the configured measurement reporting conditions are met, the UE sends a measurement report to the base station. Phase 2: Switching preparation phase. base The station determines to trigger handover for the UE based on the received measurement report and other factors such as base station load. The source base station and the target base station obtain the handover command configured by the target base station through the handover preparation process. Phase 3: Switch execution phase. The source base station issues the handover command to the UE, and the UE that receives the handover command immediately applies the configuration of the handover command to perform handover. The UE detects the handover process through a timer T304. When the handover process is initiated, the UE starts the T304 timer; when the handover process is completed, the UE stops the timer T304; when T304 times out, the UE considers the handover failed.

Dual Connectivity:

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 at the two base stations. The wireless access between the two base stations and the UE can be of the same or different standards (Radio Access Technology, RAT), for example, both are NR, or one is NR and the other is LTE, also called evolved universal terrestrial wireless access (RAT). 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 serving cell group under the master base station is called the master cell group (MCG); the other is called the secondary base station ( Secondary Node, SN) or SgNB, SeNB, the serving cell group under the secondary base station is called the Secondary Cell Group (SCG). When the primary 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 primary base station and secondary base station are both NR, the DC is called NR-DC . MCG includes a primary cell (Primary Cell, PCell) and optionally one or more secondary cells (Secondary Cell, SCell). PCell works on the main frequency, and the UE performs the initial connection establishment process or connection re-establishment process through the main frequency. SCG contains a PSCell and optionally one or more SCells. PSCell refers to the SCG cell that 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 a DC is configured, the DRB and SRB of the UE are supported as split bearers. split SRB supports transmission through two paths: MCG and SCG. When applying the duplication sending mechanism, a copy of the RRC Protocol Data Unit (PDU) can also be transmitted on the MCG and SCG paths to improve the transmission rate or reliability. Split bearer can be for the uplink path or the downlink path. Supports configuring SRB1 and SRB2 as split SRB. For downlink, the network side can decide which path to choose to send data based on some criteria such as channel quality. For the uplink, the UE determines whether to use the MCG path or send on both paths according to the RRC signaling configuration on the network side. When not configured as split SRB, SRB1 and SRB2 are transmitted through the MCG path. In addition, when the DC is configured, SRB3 can also be established for the SN 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. Split SRB configuration for SRB3 is not supported. The UE can configure split SRB1 and SRB3 at the same time.

Wireless link failure reporting mechanism in the existing mechanism:

In the current LTE system and the version 16 NR system, the UE will generate and save a radio link failure report (RLF report) when a radio link failure (Radio Link Failure, RLF) or handover failure (Handover Failure, HOF) occurs. , and save the wireless link failure information in the UE variable VarRLF-Report. Under normal circumstances, the UE only saves the RLF report of the latest connection failure (RLF or HOF). That is to say, when a connection failure occurs, the UE will clear the last saved RLF report and then save the latest connection failure in the RLF report variable. Corresponding failure message. After resuming 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 that there is an available radio link failure report (such as rlf-InfoAvailable) through an RRC message. information element to indicate). After receiving the indication, the network side may request the UE to report its saved radio link failure report through an RRC message (such as the rlf-ReportReq information element in the UEInformationRequest message to indicate the request). The UE will report the saved radio link failure report (rlf-Report information element in the UEInformationResponse message) to the network side in the response RRC message. The wireless link failure report obtained by the network side is used for network optimization, such as network coverage and mobile robustness optimization. The wireless link failure report contains information related to the link failure, including the measurement results of the source cell, target cell or neighbor cell when the link failure occurred, location information, the identification of the primary cell where the link failure occurred, and the type of link failure ( RLF or HOF), RLF reason, the time elapsed from connection failure to RLF report reporting (recorded as timeSinceFailure information element), the time elapsed from the last receipt of a handover command (handover initiation or handover execution) to connection failure ( Recorded as timeConnFailure information element), the time between the connection failure and the next time the UE enters the RRC connection state after the re-establishment process fails. (denoted as timeUntilReconnection information element), RRC re-establishes the cell identity, etc. RLF and HOF are collectively referred to as connection failures.

Fast MCG link recovery mechanism:

In systems of version 15 and earlier, after the radio link failure (RLF) of the primary cell group occurs or the UE fails to perform the handover process (HandOver Failure, HOF) (i.e. T304 timeout), the UE will initiate an RRC connection reconnection. Establish procedures to re-establish/restore the connection to the network side. During the initiated RRC connection re-establishment process, the UE first performs a cell selection process to select a re-established cell and sends an RRC connection re-establishment request message to it. When the UE receives a response message that is an RRC connection reestablishment message, the UE reestablishes the RRC connection according to the configuration in the RRC connection reestablishment message, feeds back an RRC connection reestablishment completion message to the base station, and successfully ends the RRC connection reestablishment process.

A fast MCG link recovery mechanism was introduced in version 16. The so-called "fast" refers to restoring the link connection directly through the RRC connection re-establishment process. In the fast MCG link recovery mechanism, when RLF occurs in the UE's MCG, if the link quality of the UE's secondary cell group SCG is good (that is, RLF of the SCG link does not occur, and the timer T310 associated with the SCG is not running Either it is not in the PSCell change process (that is, the timer T304 corresponding to SCG is not running), or SCG is not suspended (not suspended), or SCG has not been deactivated. At this time, neither MCG nor SCG is suspended ( or interrupt) state or the timer T316 is not in the running state, the UE initiates the MCG failure information process, starts the timer T316, and sends the MCG failure information (MCGFailureInformation) containing MCG link failure related information through the SCG path (such as split SRB1 or SRB3). ) message is sent to the main 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 of all SRBs and DRBs on the MCG side except SRB0, reset the MAC entity corresponding to the MCG, and wait during the running of timer T316 Network side response. The master base station that receives the MCG failure information RRC message can send an RRC reconfiguration message containing a synchronized 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. This kind of The fast MCG link recovery mechanism/process can be applied to situations where MR-DC (Multi-Radio access technology Dual Connectivity) is configured, such as NE-DC (NR E-UTRA Dual Connectivity), EN-DC (E-UTRA NR Dual Connectivity), NR DC (New Radio Dual Connectivity), NGEN-DC (Next Generation-radio access network E-UTRA NR Dual Connectivity), LTE DC (intra-E-UTRAN DC), etc. In this disclosure, the MCG failure information process and the fast MCG link recovery process are the same; fast MCG recovery, fast MCG failure recovery and fast MCG link failure recovery are the same.

Consider a scenario where the UE executes the fast MCG recovery mechanism after RLF occurs on the MCG link. During this process, the UE receives a handover command from the network side and performs handover to the target cell according to the handover command. If this handover fails HOF, two consecutive connection failures occur during the entire process, first RLF and then HOF. In this scenario of continuous failures, according to the existing mechanism, the UE will only record the RLF report of the second failure, that is, the HOF. The failure information of the first RLF will be lost, which makes it impossible for the network side to know the link in the entire process. Failure conditions, which will bring inaccuracies to the adjustment and optimization of mobility parameters. Secondly, in the scenario of continuous failures, how to set the time-related information in the RLF report has also become a concern in this disclosure.

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 between the embodiments. .

Example 1:

This embodiment provides an RLF reporting method performed on the UE. In the scenario where continuous connection failures occur after executing the fast MCG recovery mechanism, when HOF occurs, the UE does not record the HOF event in the RLF report variable, which means that the UE does not clear the information saved in the RLF report variable. RLF report of a previous RLF event. In Embodiment 1, it is considered that the first connection failure RLF event has a higher priority, which means that the root cause of the entire process is the first connection failure RLF, so it is necessary to report changes in the RLF The information corresponding to the RLF event is saved in the volume and reported to the network side.

Specifically, when an MCG handover failure (synchronous reconfiguration failure) occurs, if the handover is not triggered for fast MCG recovery, the UE saves the handover failure information in the RLF report variable. The MCG switching failure refers to the timeout of the T304 timer associated with the MCG. The switching is not triggered for fast MCG recovery, and may also have the following expressions: for example, the switching command is not a response to the MCGFailureInformation message; or the timer T304 is not initiated because of the fast MCG recovery process; or The timer T304 is not initiated due to receipt of the RRC reconfiguration message in response to MCGFailureInformation; the associated RRC reconfiguration message is not a response to MCGFailureInformation. The fact that the RRC reconfiguration message is not a response to MCGFailureInformation means that the RRC reconfiguration message is not received when the T316 timer is running.

Obviously, before the handover fails, it also includes the UE receiving the RRC reconfiguration message of the handover command, performing synchronization reconfiguration, synchronizing to the target cell, and starting the timer T304.

That is, as shown in Figure 1, the wireless link failure information reporting method involved in Embodiment 1 includes the following steps:

S101: When RLF occurs in MCG, the UE initiates the MCG failure information process, initiates the MCG failure information process, starts the timer T316, and sends the MCG failure information message to the base station through the SCG path;

S102: The UE receives the RRC reconfiguration message of the handover command from the base station, performs synchronization reconfiguration, synchronizes to the target cell, and starts timer T304;

S103: When a handover failure HOF occurs, that is, when consecutive failures occur first in RLF and then HOF, the UE does not record this HOF event in the RLF report variable, but saves the information corresponding to the RLF event in the RLF report variable and reports it. to the base station.

Example 2:

This embodiment provides an RLF reporting method performed on the UE. In the scenario where continuous connection failures occur after executing the fast MCG recovery mechanism, the UE records the information corresponding to the continuous failures in the RLF report, so that the network side can obtain information related to the continuous failure events and make appropriate decisions on the network status. judgment, so as to reasonably adjust the corresponding shift Dynamic parameters such as measurement configuration, link detection parameters or switching parameter configuration, etc.

That is, as shown in Figure 2, the wireless link failure information reporting method involved in Embodiment 2 includes the following steps:

S201: When RLF occurs in MCG, the UE initiates the MCG failure information process, initiates the MCG failure information process, starts the timer T316, and sends the MCG failure information message to the base station through the SCG path;

S202: The UE receives the RRC reconfiguration message of the handover command from the base station, performs synchronization reconfiguration, synchronizes to the target cell, and starts timer T304;

S203: When a handover failure HOF occurs, that is, when consecutive failures occur first in RLF and then HOF, the UE records the information corresponding to the consecutive failures in the RLF report variable and reports it to the base station.

In one implementation, when HOF (the T304 timer corresponding to MCG times out) occurs, if the corresponding handover process is initiated for fast MCG recovery, the UE saves the first information in the RLF report variable, The first information is used to record the time between this HOF and the previous RLF event. The previous RLF event refers to the RLF event used to trigger the UE to perform the fast MCG recovery process or the RLF event of the MCG that occurred just before the fast MCG recovery process. The switching process is initiated for fast MCG recovery. It can also be stated that the switching command is received as a response to the MCGFailureInformation message or when the T316 timer is running. The switching command refers to the switching command associated with the HOF event or the most recently received switching command when the HOF event occurs.

In one implementation, when HOF (the T304 timer corresponding to MCG times out) occurs, if the corresponding handover process is initiated for fast MCG recovery, the UE saves the second information in the RLF report variable, The second information is used to indicate that an RLF event occurred before this HOF. The RLF event refers to an RLF event used to trigger the UE to perform a fast MCG recovery process or an RLF event of MCG that occurs just before the fast MCG recovery process. The second information is actually an RLF event occurrence indication. Furthermore, the second information may also be the reason for detecting the RLF event (RLF cause), such as T310 timer timeout, T312 timer timeout, random access problem, the maximum number of RLC retransmissions reached, or Beam failure, recovery failure, etc. The switching process is used to quickly Initiated to speed up MCG recovery, it can also be stated that the switching command is received as a response to the MCGFailureInformation message or when the T316 timer is running. The switching command refers to the switching command associated with the HOF event or the most recently received switching command when the HOF event occurs.

In one implementation, during the RRC connection establishment process, when the UE receives an RRC establishment (RRCSetup) message in response to the RRC connection request (RRCSetupRequest) message, if there is an available RLF saved in the RLF report variable of the UE Or HOF information, the current registered Public Land Mobile Network (PLMN) is included in the PLMN identification list saved in the RLF report variable, and the reconnection cell identification (reconnectCellId information element) in the RLF report variable is also Not set. If the UE determines that the RLF report variable is associated with the aforementioned consecutive failure events that have executed fast MCG recovery, the UE sets the third information (timeUntilReconnection information element) in the RLF report variable to the value saved in the RLF report variable. The time elapsed since the connection failure experienced in the cell indicated by the failed cell identifier (failedPCellId information element) began. Preferably, the connection failure refers to RLF, which is used to trigger a fast MCG recovery process. In this implementation, the RRC establishment process is initiated by the UE after the RRC re-establishment process initiated after the fast MCG recovery process fails (the aforementioned continuous failure event) also fails, and is used for the UE to re-establish a connection with the network side.

In one implementation, the UE receives a UEinformationRequest message from the network side, which contains instruction information for requesting the UE to report the RLF report saved on it (the rlf-ReportReq information element is set to true), and the UE sets the RLF report variable The fourth information in is set to the time elapsed from the first failure, and the RLF report information in the RLF report variable is included in the response UEinformationResponse message. Preferably, the fourth information reuses the timeSinceFailure information element. The first failure refers to the first failed RLF among the consecutive failures in the aforementioned fast MCG recovery failure scenario. In another way, the fourth information is set to the time elapsed since the connection failure experienced in the cell indicated by the failed cell identification (failedPCellId information element) saved in the RLF report variable.

In one implementation, when the UE receives the RRC connection reconfiguration message, if the RRC connection reconfiguration message is received as a response to the MCGFailureInformation message , the UE sets the fifth information element in the RLF report variable to the time between the latest RLF and the receipt of the RRC connection reconfiguration message. Among them, the latest RLF is the RLF event that triggers the fast MCG recovery process or the RLF event that occurs just before the fast MCG recovery process. The reception of the RRC connection reconfiguration message may also refer to handover execution or handover initiation after receiving the RRC connection reconfiguration message.

Example 3:

This embodiment provides a RLF information reporting method executed on the UE. Through the method described in this embodiment, the UE can report relevant information to the base station in the RLF report to provide more accurate connection failure information to the network side. This embodiment is the method of Embodiment 1 and Embodiment 2 when the UE reports through the RRC process.

Step 1: The UE receives the UEInformationRequest message from the network side, which carries an instruction/request for requesting the UE to report the saved successful handover report.

Step 2: The UE includes the contents of the saved successful handover report in the UEInformationResponse message, and sends the UEInformationResponse message to the network side. The RLF report included in the RRC message includes one or more of the first to fifth information in the aforementioned embodiment.

Example 4:

This embodiment describes the user equipment UE of the present disclosure. FIG. 3 is a block diagram showing user equipment UE according to the present invention. As shown in Figure 3, the user equipment UE300 includes a processor 301 and a memory 302. The processor 301 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like. The memory 302 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Memory 302 stores program instructions. When this instruction is executed by the processor 301, the above-mentioned RLF information reporting method described in detail in the present invention can be executed.

The method and related equipment of the present disclosure have been described above in conjunction with preferred embodiments. Those skilled in the art will understand that the methods shown above are only exemplary. My Lord The method of opening is not limited to the steps and sequence shown above. The base station and user equipment shown above may include more modules, for example, may also include modules that may be developed or developed in the future and may be used for the base station, MME, or UE, and so on. The various identifications shown above are only illustrative and not restrictive, and the present disclosure is not limited to the specific information elements as examples of these identifications. Many changes and modifications may be made by those skilled in the art in light of the teachings of the illustrated embodiments.

The program running on the device according to the present disclosure may be a program that causes the 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 volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.

Programs for realizing the functions of each embodiment of the present disclosure may be recorded on a computer-readable recording medium. Corresponding functions can be realized by causing the computer system to read programs recorded on the recording medium and execute these programs. The so-called "computer system" here may be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices). The "computer-readable recording medium" may 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 readable by a computer.

Various features or functional modules of the devices used in the above-described embodiments may be implemented or performed by circuits (eg, single-chip or multi-chip integrated circuits). Circuitry 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. A general-purpose processor can be a microprocessor or any existing processor, controller, microcontroller, or state machine. The above circuit may be a digital circuit or an analog circuit. When new integrated circuit technologies emerge 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.

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

As 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-described embodiment, and the present disclosure also includes any design changes that do not deviate from the gist 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. Furthermore, components having the same effect described in the above embodiments may be substituted for each other.

Claims

A radio link failure information reporting method is a method for reporting RLF information when the user equipment UE performs a fast MCG recovery mechanism using the secondary cell group SCG after a radio link failure RLF occurs in the primary cell group MCG, including the following step:

When RLF occurs in MCG, the UE initiates the MCG failure information process, starts timer T316, and sends the MCG failure information message to the base station through the SCG path;

The UE receives the RRC reconfiguration message of the handover command from the base station, performs synchronization reconfiguration, synchronizes to the target cell, and starts timer T304;

When a handover failure HOF occurs, that is, when consecutive failures occur first in RLF and then HOF, the UE does not record this HOF event in the RLF report variable, but saves the information corresponding to the RLF event in the RLF report variable and reports it to the base station. .
A radio link failure information reporting method is a method for reporting RLF information when the user equipment UE performs a fast MCG recovery mechanism using the secondary cell group SCG after a radio link failure RLF occurs in the primary cell group MCG, including the following step:

When RLF occurs in MCG, the UE initiates the MCG failure information process, starts timer T316, and sends the MCG failure information message to the base station through the SCG path;

The UE receives the RRC reconfiguration message of the handover command from the base station, performs synchronization reconfiguration, synchronizes to the target cell, and starts timer T304;

When a handover failure HOF occurs, that is, when consecutive failures occur first in RLF and then HOF, the UE records the information corresponding to the consecutive failures in the RLF report variable and reports it to the base station.
The wireless link failure information reporting method according to claim 2, wherein,

When a HOF occurs, if the corresponding handover process is initiated for fast MCG recovery, the UE saves the first information in the RLF report variable, and the first information is used to record this HOF and the previous RLF event. the time between.
The wireless link failure information reporting method according to claim 2, wherein,

When a HOF occurs, if the corresponding handover process is initiated for fast MCG recovery, the UE saves the second information in the RLF report variable, and the second information is used to indicate that an RLF event occurred before the HOF. .
The wireless link failure information reporting method according to claim 2, wherein,

During the RRC connection establishment process, when the UE receives the RRC establishment message, if there is available RLF or HOF information saved in the RLF report variable, the current PLMN is included in the PLMN identification list saved in the RLF report variable, and The reconnection cell identifier in the RLF report variable has not been set. If the UE determines that the RLF report variable is associated with a continuous failure event, the UE sets the third information in the RLF report variable to the failure stored in the RLF report variable. The time since the connection failures experienced in the cell indicated by the cell identity began.
The wireless link failure information reporting method according to claim 5, wherein,

The connection failure experienced in the cell indicated by the failed cell identifier is an RLF used to trigger a fast MCG recovery procedure.
The wireless link failure information reporting method according to claim 2, wherein,

If the UE receives the UE information request message, which contains instruction information for requesting the UE to report the RLF report saved on it, the UE sets the fourth information in the RLF report variable to the time elapsed since the first failure, and include the RLF report information in the RLF report variable in the corresponding UE information response message.
The wireless link failure information reporting method according to claim 2, wherein,

When the UE receives the RRC connection reconfiguration message, if the RRC connection reconfiguration message is received as a response to the MCG failure information message, the UE sets the fifth information element in the RLF report variable to the value from the most recent RLF to the time the RRC is received. The time between connection reconfiguration messages.
The wireless link failure information reporting method according to any one of claims 1 to 8, further comprising the following steps:

The UE receives a UE information request message from the base station, which carries an instruction/request for requesting the UE to report the saved successful handover report;

The UE includes the contents of the saved successful handover report in the UE information response message and sends it to the base station.
A user device including:

processor; and

memory, which stores instructions,

When executed by the processor, the instructions cause the user equipment to execute the wireless link failure information reporting method according to any one of claims 1 to 9.