Method and apparatus for performing communication in a wireless communication system

The radio chain is solved by configuring the second timer provided by the secondary node (SN) for the user equipment (UE) in the wireless communication system, detecting the early secondary cell group (SCG) RLF and launching a failed process to the primary node (MN). The problem of service interruption for too long after the road failure has achieved rapid recovery.

CN113615255BActive Publication Date: 2024-12-06SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080013076.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-02-08
Filing Date
2020-02-07
Publication Date
2024-12-06
Estimated Expiration
2040-02-07

AI Technical Summary

Technical Problem

In wireless communication systems, the prior art is difficult to effectively detect early radio link failures (RLFs) and achieve rapid recovery, resulting in too long service interruption.

Method used

Receive a second timer measurement configuration provided by a secondary node (SN) through a user equipment (UE), configures a second timer associated with a secondary cell (PSCell) and compares it among the first timer and the second timer The secondary cell group (SCG) RLF is declared at the expiration earlier, thereby initiating the SCG failure process to the primary node (MN).

Benefits of technology

This method can minimize the bearer service interrupt time processed by SCG and achieve faster radio link recovery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113615255B_ABST
    Figure CN113615255B_ABST
Patent Text Reader

Abstract

Embodiments of the present invention disclose a method for handling RLF by a UE (100) in a wireless communication system. The method includes receiving a measurement configuration including a second timer (150) from an SN (300). In addition, the method includes configuring a second timer associated with a measurement report for a PSCell of the SN for the UE. In addition, the method includes starting the second timer when a corresponding measurement report is triggered while a first timer (140) for the PSCell is running. In addition, the method includes detecting the expiration of one of a first timer and a second timer for the PSCell. In addition, the method includes declaring an SCG RLF when the earlier of the first timer and the second timer expires. In addition, the method includes initiating an SCG failure procedure to the MN (300) when declaring the SCGRLF.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems, and more particularly, to a method and user equipment (UE) for detecting early radio link failure (RLF) and achieving faster recovery in New Radio (NR) of a wireless communication system. Background Art

[0002] In order to meet the increased demand for wireless data traffic since the deployment of the fourth generation (4G) communication system, efforts have been made to develop an improved fifth generation (5G) or quasi-5G communication system. 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-long term evolution (LTE) systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60 GHz bands) in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed for 5G communication systems. In addition, in 5G communication systems, improvements to system networks are being developed based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference elimination, and the like. In 5G systems, hybrid frequency shift keying (FSK) and Feher quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coded modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, which is a human-centered connected network in which humans generate and consume information, is now evolving into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of IoT technology and big data processing technology through connection with a cloud server, has emerged. Because technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" are required for IoT implementation, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently. This IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to multiple fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the integration and combination of existing information technology (IT) with various industrial applications.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communications can be implemented through beamforming, MIMO, and array antennas. Cloud RAN as an application of the above-mentioned big data processing technology can also be considered an example of the fusion of 5G technology and IoT technology.

[0005] As described above, according to the development of wireless communication systems, various services can be provided, and thus a method for easily providing such services is required. Summary of the invention

[0006] Technical issues

[0007] The main purpose of the embodiments of this document is to provide a method and UE for detecting early RLF in NR and achieving faster recovery.

[0008] Solution to the problem

[0009] Embodiments of the present invention disclose a method for handling RLF by a UE (100) in a wireless communication system. The method includes receiving a measurement configuration including a second timer (150) from an SN (300). In addition, the method includes configuring a second timer associated with a measurement report for a PSCell of the SN for the UE. In addition, the method includes starting the second timer when a measurement report is triggered while a first timer (140) for the PSCell is running. In addition, the method includes detecting the expiry of one of the first timer and the second timer for the PSCell. In addition, the method includes declaring an SCG RLF when the earlier of the first timer and the second timer expires. In addition, the method includes initiating an SCG failure procedure to the MN (300) when declaring the SCG RLF.

[0010] Beneficial Effects

[0011] By means of the method of the present application, the service interruption time of the bearers handled by the SCG is minimized. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The method is illustrated in the accompanying drawings, in which the same reference numerals indicate corresponding parts in the different drawings. The embodiments of the present invention will be better understood according to the following description with reference to the accompanying drawings, in which:

[0013] Figure 1a is a flow chart showing step-by-step operations for PSCell RLF and SCG failure indication in a MR-DC scenario according to the prior art, wherein the UE is configured with SRBs only on the MCG PCell;

[0014] Figure 1b is a flow chart showing step-by-step operations for PSCell RLF and SCG failure indication in a MR-DC scenario according to the prior art, wherein the UE is configured with SRB1, SRB2 on the MCG PCell and SRB3 on the SCG PSCell;

[0015] Figure 2a is a flow chart illustrating step-by-step operations for indicating an early SCG failure to a MN in an MR-DC scenario according to embodiments disclosed herein, wherein SRBs are configured only on the MCG, wherein the MCG and SCG cells may belong to one of the EUTRAN or NR;

[0016] Figure 2bis a flow chart illustrating a method for indicating an early SCG failure to a MN in an MR-DC scenario according to embodiments disclosed herein, wherein SRB1, SRB2 are configured on the MCG and SRB3 is configured on the SCG, wherein the MCG cell may belong to EUTRAN or NR, and the SCG cell belongs to NR;

[0017] Figure 3a is a flow chart illustrating step-by-step operations for attempting cell selection on LTE (or next priority RAT) upon expiration of T310 according to embodiments disclosed herein;

[0018] Figure 3b 1 is a flowchart showing step-by-step operations of RLF caused by not receiving a mobility from NR command or a handover to LTE command from the network due to expiration of T310 according to an embodiment disclosed herein;

[0019] Figure 4a is a flowchart illustrating step-by-step operations for enabling a UE to recover from a service interruption by allowing the UE to perform a connection establishment on a target cell faster than if T312 is not applied, according to an embodiment disclosed herein;

[0020] Figure 4b is a flow chart illustrating step-by-step operations for sending an RRC establishment request from a source eNB (LTE) to a target gNB (NR) upon expiration of T312 according to embodiments disclosed herein;

[0021] Figure 5a is a flowchart showing step-by-step operations of stopping T312 when a departure condition is met according to an embodiment disclosed herein;

[0022] Figure 5b is a flowchart showing step-by-step operations of restarting T312 when a leaving condition is met according to an embodiment disclosed herein;

[0023] Figure 6 is a schematic diagram of a UE for processing RLF in a wireless communication system according to an embodiment disclosed herein; and

[0024] Figure 7 is a flowchart illustrating a method for processing RLF in a wireless communication system according to an embodiment disclosed herein. Figure 8 is a diagram illustrating a base station according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] Best Mode for Carrying Out the Invention

[0026] Therefore, an embodiment of the present invention discloses a method for handling RLF in a wireless communication system. The method includes receiving, by a UE, a measurement configuration including a second timer from a secondary node (SN). In addition, the method includes configuring a second timer associated with a measurement report of a PSCell for the SN for the UE. In addition, the method includes starting a second timer by the UE when a corresponding measurement report is triggered while a first timer for the PSCell is running. In addition, the method includes detecting, by the UE, the expiration of one of a first timer and a second timer for the PSCell. In addition, the method includes declaring a secondary cell group (SCG) RLF by the UE when the earlier of the first timer or the second timer expires. In addition, the method includes initiating an SCG failure procedure by the UE to a master node (MN) when declaring the secondary cell group (SCG) RLF.

[0027] In an embodiment, further, the method includes notifying the master node of an SCG failure message by the UE via the primary cell group (MCG) link through SRB1 when declaring the SCG RLF. The SCG failure message includes a cause value corresponding to the failure type (as one of the expiration of the first timer and the expiration of the second timer). In addition, the method includes triggering, by the MN, recovery of the SCG radio link failure (RLF) based on the secondary cell group (SCG) failure message.

[0028] In an embodiment, further, the method includes setting, by the UE, the failure type to one of expiration of the first timer and expiration of the second timer.

[0029] In an embodiment, if the expiration of the first timer is before the expiration of the second timer, the UE sets the failure type to the expiration of the first timer, otherwise, if the expiration of the second timer is before the expiration of the first timer, the UE sets the failure type to the expiration of the second timer.

[0030] In an embodiment, the method further comprises receiving, by the UE from the SN, a measurement object and a report configuration comprising a second timer, wherein the second timer is associated with a measurement report for a PSCell of the SN.

[0031] In an embodiment, when the first timer for the PSCell is running, a trigger for a measurement report for the PSCell associated with a second timer is determined by the UE, and the second timer for the PScell ​​is started by the UE.

[0032] In an embodiment, the measurement report for the PSCell is sent to the secondary node (SN) through one of a signaling radio bearer type 1 (SRB1) and a signaling radio bearer type 3 (SRB3).

[0033] In an embodiment, SCG RLF is declared by the UE based on detection of expiration of an earlier one of the first timer or the second timer, and the other timer that has not expired is stopped.

[0034] In an embodiment, the SCG failure procedure is initiated by the UE based on the declaration of the SCG RLF.

[0035] In an embodiment, the first timer is a T310 timer, wherein the first timer is included during the SCG addition, and the second timer is a T312 timer, wherein the second timer is included in the measurement configuration from the SN.

[0036] In an embodiment, triggering recovery of the SCG RLF by the MN based on the SCG failure message includes receiving, by the UE, an RRC reconfiguration message from the master node via SRB1.

[0037] Therefore, an embodiment of the present invention discloses a UE for processing RLF in a wireless communication system. The UE includes a processor coupled to a memory. The processor receives a measurement configuration including a second timer from a secondary node (SN). The method includes configuring a second timer associated with a measurement report of a PSCell for the SN for the UE. In addition, when a corresponding measurement report is triggered while a first timer for the PSCell is running, the processor starts the second timer. The processor detects the expiration of one of the first timer and the second timer for the PSCell. The processor declares SCG RLF when the earlier of the first timer or the second timer expires. In addition, when declaring SCG RLF, the processor starts the SCG failure process.

[0038] When considered in conjunction with the following description and the accompanying drawings, these and other aspects of the embodiments herein will be better understood and appreciated. However, it should be understood that the following description, although indicating preferred embodiments and a plurality of specific details thereof, is provided by way of illustration and not limitation. Various changes and modifications may be made within the scope of embodiments of the present invention without departing from the spirit of the present invention, and embodiments of the present invention include all such modifications.

[0039] Invention Mode

[0040] The embodiments of this article and its various features and advantageous details are explained more comprehensively with reference to the non-limiting embodiments shown in the drawings and described in detail in the following description. The description of known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments of this article. In addition, the various embodiments described herein are not necessarily mutually exclusive, because some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" used herein refers to a non-exclusive "or". The examples used herein are merely to facilitate understanding of the manner in which the embodiments of this article can be practiced, and further enable those skilled in the art to practice the embodiments of this article. Therefore, these examples should not be interpreted as limiting the scope of the embodiments of this article.

[0041] As tradition in the art, embodiments can be described and illustrated according to the block of one or more functions described for execution.These blocks may be referred to as units or modules, etc. herein, and they are physically implemented by analog or digital circuits (such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc.), and may be optionally driven by firmware and software.For example, the circuit may be included in one or more semiconductor chips or may be included in substrate supports such as printed circuit boards.The circuit constituting the block may be implemented by dedicated hardware or by a processor (such as, one or more programmed microprocessors and associated circuits) or by a combination of dedicated hardware that performs some functions of the block and a processor that performs other functions of the block.Without departing from the scope of the present invention, each block of the embodiment may be physically divided into two or more discrete blocks that interact.Equally, without departing from the scope of the present invention, the block of the embodiment may be physically combined into more complex blocks.

[0042] The accompanying drawings are used to help easily understand various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. Therefore, except for those specifically set forth in the accompanying drawings, the present disclosure should be interpreted as extending to any variation, equivalents and substitutes. Although the terms first, second, etc. herein can be used to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another element.

[0043] In recent years, wireless communication technology has made some progress to meet the growing demand for broadband and the emergence of new applications and services. The second generation of wireless communication systems was developed to provide voice services in a mobile environment. The third generation further enhanced this by supporting data and voice in a mobile environment. In recent years, the fourth generation of wireless communication systems has been developed to provide high-speed broadband data in a mobile environment. However, the development of the fourth generation of communication systems (Long Term Evolution (LTE)) has been plagued by a lack of resources and methods to meet the growing demand for broadband and new use cases. Therefore, the fourth generation of communication systems is being further developed, and the fifth generation (New Radio (NR)) is being developed to meet this growing demand for broadband with enhanced mobile broadband (eMBB), while also supporting new use cases such as ultra-reliable low latency communication (URLLC) and massive machine type communication (mMTC).

[0044] NR is an Orthogonal Frequency Division Multiplexing (OFDM) based air interface designed to support a wide variety of 5G device types, services, deployments, and spectrum. The network monitors device behavior and provides the necessary resources to the mobile device (e.g., UE, etc.) to perform whatever operations it requires (data (uplink or downlink), call, etc.). The signal strength and quality experienced by the mobile device varies depending on the proximity of the mobile device to the gNB. UEs near the cell are expected to have better signal conditions than UEs far away from the gNB, i.e., cell edge conditions.

[0045] The network (i.e. RAN nodes) (gNodeB (gNB) in NR / eNB in ​​LTE) always maintains a context on a mobile device with which it is in an active RRC connection. At any point in time, the gNB can hand over the mobile device / UE from its control (i.e. source cell) to another gNB or another cell (i.e. target cell), thereby transferring the entire context of the particular device to the target cell. This decision is made by the network with the help of measurement reports about neighboring cells, optionally based on assistance received from the UE. (i.e. the gNB configures the mobile device to measure the signal conditions of the serving cell and neighboring cells which may belong to different gNBs). For the network, there are specific measurement criteria and specific reporting criteria, both of which are configured by the serving gNB itself. Due to a number of reasons such as weak signal conditions on the serving gNB, heavy load, etc., the serving gNB can hand over the device to a neighboring cell or target gNB, which can be done based on assistance received from the UE in the form of measurement reports.

[0046] The UE continuously monitors the quality of its radio link to ensure that the link is in a good enough condition to successfully receive any transmission from the base station and successfully transmit to the base station. When the UE identifies that the link quality is weakening, the radio resource management (RRM) function that performs radio link monitoring (RLM) at the physical (PHY) layer sends an out of sync indication to the upper layer (i.e., the RRC layer), thereby indicating the degradation of the radio link quality to the upper layer. Once the link degradation condition reaches the allowed limit (i.e., the configured threshold condition), the UE enters the outage state (i.e., poor radio conditions), that is, the UE experiences Qout (out of sync indication from the radio resource manager) due to a high block error rate. The current specification stipulates that the configured T310 timer is used in this state. At the expiration of the timer T310, the UE declares a radio link failure (RLF) and initiates a cell selection process to attempt to recover. The timer value is kept long enough to give the UE enough opportunity to recover from the outage state and recover to good radio link quality with the in sync indication from the PHY layer. On the other hand, the T310 timer is configured to be short enough to trigger recovery on another cell without significantly affecting user services, ie, to minimize service interruption time.

[0047] Typically, this outage state or a bad radio link state that satisfies Qout occurs when the UE moves toward the cell edge of the serving cell. Therefore, there is a high probability that there is a neighboring cell whose coverage the UE is entering. As a result, it is ideal that the network configures a handover that initiates a measurement report so that the network has enough time to process the measurement report, prepare the target cell for the handover, and provide a handover command before the radio link of the serving cell becomes too weak to correctly decode the handover command from the network. However, even after good network planning and network optimization, there are some practical situations where the direction and speed of each UE are different and the cell coverage is not optimal, in which case the above situation may become too complicated to propose a configuration that is ideal for all UEs in the cell. The reporting configuration for the configured measurements is set to not increase the signaling volume due to measurement reports. The network configures the measurement report so that an action must be taken based on the report from the UE. In most cases, this leads to a handover, so the network configures such measurements to be reported only when the UE needs to be handed over. This sometimes leads to an increased probability that the UE enters a Qout state before the measurement report is triggered (due to the unpredictability of the radio channel and other factors such as UE mobility and speed).

[0048] 3GPP studied the HetNet Mobility Enhancement of LTE and concluded that the handover performance in HetNet deployment is worse than that in homogeneous macro deployment. In dense HetNet environments, due to several factors including RLF recovery interruption and Qout during T310, more and more handovers and RLFs may cause the UE's service interruption time to become longer and longer. A short value of T310 configured for the UE may cause the UE to declare RLF before the measurement report is sent to the network. This type of configuration does not allow the UE to request a handover or recover from Qout. Therefore, the value of T310 is usually kept large. It may also happen that the UE has met the reporting criteria for the configured neighbor frequency and sends a measurement report to the network shortly after T310 is started at the UE. It is very likely that the network will prepare the target cell for the handover and send a handover command to the UE, but the unsynchronized UE may not be able to receive the handover command. Ultimately, the UE will declare RLF after the expiration of T310. However, the measurement report triggered by the UE is an indication that a neighboring cell with good radio conditions is available nearby. Therefore, a mechanism for fast handover failure recovery / early radio link failure detection is introduced with the configuration of the T312 timer, wherein the UE declares a radio link failure before the expiration of the T310 timer (i.e., at the expiration of the T312 timer). Such an early decision is made so that the UE is provided with sufficient opportunity to return to the synchronization state and the network is provided with sufficient opportunity to prepare for the handover with the target cell. The T312 timer is introduced and configured by the network to control the behavior that is expected to minimize the service interruption time. When the RLF timer T310 is running and the measurement report is triggered by the UE for the combination of the measurement object and the report configuration that requires the UE to use the behavior based on the T312 timer, the UE starts the timer T312. When T312 expires, the UE declares an early RLF process and attempts to restore the radio link. However, in a dual connectivity configuration, such early recovery is feasible in the primary cell group (MCG), but not in the secondary cell group (SCG). RLF on the SCG is also referred to as SCG failure, and these two terms can be used interchangeably in the following of this disclosure. Due to the flexibility of configuring dedicated radio bearers (DRBs) in the dual connectivity architecture supported in NR, the lower layers (i.e., RLC branches) can be flexibly configured in the MCG or SCG or both, and can be associated with a Packet Data Convergence Protocol (PDCP) entity terminated at the primary node or the secondary node. Therefore, if an SCG failure is encountered on a PSCell in an SCG, it makes sense to perform early recovery to minimize the service interruption time of the bearers handled by the SCG.

[0049] It would therefore be desirable to address the above-mentioned disadvantages or others, or at least provide a useful alternative.

[0050] Therefore, an embodiment of the present invention discloses a method for handling RLF in a wireless communication system. The method includes receiving, by a UE, a measurement configuration including a second timer from a secondary node (SN). In addition, the method includes configuring a second timer associated with a measurement report of a PSCell for the SN for the UE. In addition, the method includes starting a second timer by the UE when a corresponding measurement report is triggered while a first timer for the PSCell is running. In addition, the method includes detecting, by the UE, the expiration of one of a first timer and a second timer for the PSCell. In addition, the method includes declaring a secondary cell group (SCG) RLF by the UE when the earlier of the first timer or the second timer expires. In addition, the method includes initiating an SCG failure procedure by the UE to a master node (MN) when declaring the secondary cell group (SCG) RLF.

[0051] The proposed method can be used to detect early RLF and can achieve faster recovery in NR. The method can use RLF-TimersandConstants in spCellConfig for T312 in RRC reconfiguration. The method can be used to indicate the SCG failure cause due to expiration of T312.

[0052] The proposed method introduces a T312-based mechanism on PSCell for fast declaration of SCG failure. This can help achieve less service interruption time for bearers configured on SCG by speeding up SCG recovery based on a shorter T312 timer.

[0053] Based on the proposed method, when T312 expires for the PSCell (i.e., the secondary node of the NR PSCell), the UE does not perform the RRC re-establishment process, but sends an SCG failure message to the network. The SCG failure message includes a cause value corresponding to the expiration of T312. For the PSCell RLF, the RRC connection on the PCell (MN) is already good, but the data on the PSCell is lost. The UE attempts to recover the data on the SCG by automatically sending the cause of the failure without the need for the NW to query. The SCG failure message is sent to the primary node (i.e., MN) on SRB1 via the MCG link, regardless of whether the SCG measurement is configured via SRB1 or SRB3.

[0054] Various embodiments of the proposed method are adopted in 3GPP TS 38.331.

[0055] Referring now to the drawings and more particularly to Figures 2a to 7 , showing a preferred embodiment.

[0056] Figure 1a is a sequential flow chart illustrating a method for PSCell RLF and SCG failure indication in a MR-DC scenario according to the prior art, wherein the UE (100) is configured with SRB only on the MCG PCell.

[0057] More than one serving cell may be configured for a UE (100). This may be a carrier aggregation (CA) type of configuration, where all serving cells belong to the same cell group (CG) served by the same gNB, or a dual connectivity configuration, where serving cells may be from two different cell groups (CGs, i.e., MCG and SCG) served by two different gNBs. In the case of carrier aggregation, radio link monitoring (RLM) is performed only on the primary cell (PCell); and in dual connectivity,

[0058] In the DC case, radio link monitoring (RLM) is performed on the primary cell and the primary secondary cell (PSCell). PCell and PSCell are special cells, usually referred to as special cells, namely SpCell.

[0059] In an embodiment, the method can be used to detect RLF or perform SCG failure recovery on a PSCell (using T312 on PSCell / SCG). When the UE (100) is configured with LTE dual connectivity (i.e., LTE-DC), all measurement configurations and measurement reports are exchanged between the UE (100) and the eNB via signaling radio bearer 1 (SRB1). The master node (MN) is aware of the secondary node (SN) configurations and is able to understand them. The MN attaches the configuration received from the SN and sends it to the UE (100) in an RRC reconfiguration message. Any measurement report sent by the UE (100) will be terminated at the MN eNB.

[0060] However, with the introduction and development of NR technology, the way of handling SN configuration has changed. NR supports multiple deployment types based on dual connectivity, including EUTRA-NR dual connectivity (EN-DC) (where the MN is an LTE eNB connected to the EPC and the SN is an NR gNB); NR-RAN E-UTRA-NR dual connectivity (NGEN-DC) (where the MN is an LTE ng-eNB connected to the 5GC and the SN is an NR gNB); NR-E-UTRA dual connectivity (NE-DC) (where the MN is an NR gNB connected to the 5GC and the SN is an LTE ng-eNB); and NR-NR dual connectivity (NR-DC) (where the MN is an NR gNB connected to the 5GC and the SN is an NR gNB). These are collectively referred to as multi-radio dual connectivity (MR-DC). In MR-DC, when the signaling radio bearer (SRB) only exists on the MN, the SN configuration is transparent to the MN, but the MN cannot understand these configurations. The MN encapsulates the received SN configuration and sends it to the UE in a reconfiguration message (100). When the UE (100) is configured with an SRB3 hosted in the SN, that is, the UE (100) is configured with an independent SRB hosted by the MN and the SN, the SN configuration is not sent to the MN, and the SN directly sends an RRC reconfiguration message to the UE (100) on the SRB3. Therefore, the MN and the SN can send independent reconfiguration messages to the UE (100).

[0061] The UE (100) monitors RLM on both the PCell and PSCell. When the Qout condition is met, T310 is started for the cell and once T310 expires, RLF is declared. For measurement object-reporting configuration combinations that require the use of T312, timer-based early detection may be based on when the measurement report is triggered. In LTE, even in the case where the UE (100) is configured with dual connectivity operation (i.e., LTE DC configuration), the behavior based on T312 is only applied to the primary cell (PCell). In MR-DC, PSCell RLF detection is based on T310 itself, such as Figure 1a and 1b shown. Figure 1a The case of PSCell RLF and SCG failure indication in MR-DC scenario is shown, where UE (100) is configured with SRB only on MCG PCell. The SCG cell served by SN in MR-DC system can belong to either EUTRA or NR. Figure 1bThe case of PSCellRLF and SCG failure indication in MR-DC scenario is shown, where UE (100) is configured with SRB1, SRB2 on MCG PCell and SRB3 on SCG Pcell. In this case, the SCG cell belongs to NR.

[0062] In the example, at S102a, the SN (300) sends a measurement configuration to the MN (200). At S104a, the MN (200) sends a measurement configuration to the UE (100). At S106a, a data from SN bearer is established between the UE (100) and the SN (300). At S108a, the SN (300) sends an RRC reconfiguration to the MN (200). At S110a, the MN (300) sends an RRC reconfiguration to the UE (100). At S112a, the UE (100) detects the Qout of the PSCell. At S114a, the UE (100) starts a timer (i.e., T310) for the PSCell. At S116a, the UE (100) sends a measurement report to the MN (200) via a signaling radio bearer type 1 (SRB1) message. At S118a, the timer T310 expires, and at S120a, the UE (100) initiates a secondary cell group (SCG) failure procedure. At S112a, the UE (100) shares the SCG failure information with the MN (200). At S124a, the MN (200) initiates an SCG failure recovery action.

[0063] Figure 1b is a sequential flow chart showing step-by-step operations for PSCell RLF and SCG failure indication in an MR-DC scenario according to the prior art, wherein a UE (100) is configured with SRB1, SRB2 on the MCG PCell and with SRB3 on the SCG PSCell.

[0064] Combined with the above Figure 1a Describes Figure 1bFunctions and operations of. In the example, at S102b, the SN (300) sends a measurement configuration to the UE (100). At S104b, data from the SN bearer is established between the UE (100) and the SN (300). At S106b, the SN (300) sends an RRC reconfiguration to the UE (100). At S108b, the UE (100) detects the Qout of the PSCell. At S110b, the UE (100) starts a timer (i.e., T310) for the PSCell. At S112b, the UE (100) sends a measurement report to the SN (300) via an SRB3 message. At S114b, the timer expires, and at S116b, the UE (100) starts the SCG failure procedure. At S118b, the UE (100) shares the SCG failure information with the MN (200). At 120b, the MN (200) starts an SCG failure recovery action.

[0065] Figure 2a is a sequential flow chart showing step-by-step operations for indicating early SCG failure to a MN in an MR-DC scenario according to an embodiment disclosed herein, wherein SRBs are configured only on the MCG, wherein the MCG and SCG cells may belong to either EUTRAN or NR.

[0066] The mechanism of declaring RLF early provides the UE (100) with an opportunity to perform a fast recovery. T312 is only used when a measurement report is triggered for a measurement configuration that requires the use of T312. Typically, this is configured only for handovers that trigger the configuration. Therefore, if the UE (100) has triggered a measurement report, this means that the UE (100) is near a cell with better signal conditions, so that a handover of the ongoing service can be performed. When early RLF declaration based on T312 is adopted for the PCell, the UE (100) performs RRC re-establishment earlier (most likely on the target cell indicated in the measurement report) compared to the case where only T310 is used. Through RRC re-establishment, the target node retrieves the UE context from the old serving node and restores the control path and data path for the UE (100), thereby reducing the interruption to the UE (100) caused by RLF.

[0067] Similarly, T312 can be configured for the PSCell when measurement reporting is triggered for a measurement configuration that requires the use of T312. Typically, this is configured only for PSCell change trigger conditions. Therefore, if the UE (100) is configured with MR-DC operation, if measurement reporting is triggered for a PSCell change, this means that the UE (100) is near a cell that is in better signal conditions, so that a PSCell change can be performed to offload the DRBs handled by the serving PSCell. When an early RLF declaration based on T312 is adopted for the PSCell, the SCG failure is indicated to the MN when T312 expires (i.e., earlier than the time that would be reported if only T310 was used). This rapid reporting of SCG failure provides the MN node with an earlier opportunity to restore the data path configured on the SN where the UE (100) encounters a PSCell RLF or SCG failure. The MN can recover the DRB faster by reconfiguring all SN terminated PDU sessions or data radio bearers to MN terminated PDU sessions or data radio bearers, or by preparing another SN and reconfiguring these bearers to the new SN. Since the PDU session / data radio bearer relocation or reconfiguration occurs earlier than the expiration of T310, it helps to reduce the service interruption timer for the UE (100), thereby providing a better user experience. Figure 2a and Figure 2b PSCell RLM and SCG failure indication to the MN based on the T312 timer is shown. Figure 2a An early SCG failure indication to a MN in a MR-DC scenario is shown, where SRBs are configured only on the MCG, where the MCG and SCG cells can belong to either EUTRAN or NR. Figure 2b An early SCG failure indication to the MN in a MR-DC scenario is shown, where SRB1, SRB2 are configured on the MCG and SRB3 is configured on the SCG, where the MCG cell can belong to one of the EUTRAN or NR, and the SCG cell belongs to the NR.

[0068] In the example, at S202a, the SN (300) sends a measurement configuration to the MN (200), wherein the measurement configuration includes a T312 timer. At S204a, the MN (200) sends the measurement configuration to the UE (100). At 206a, data from the SN bearer is established between the UE (100) and the SN (300). At 208a, the SN (300) sends an RRC reconfiguration to the MN (200). At 210a, the MN (300) sends an RRC reconfiguration to the UE (100). At S212a, the UE (100) detects the Qout of the PSCell. At 214a, the UE (100) starts a timer (i.e., T310) for the PSCell. At S216a, the UE (100) sends a measurement report to the MN (200) via an SRB1 message. At 218a, the UE (100) starts a second timer (i.e., T312), and the second timer expires. At S220a, the UE (100) initiates an SCG failure process. At S222a, the UE (100) shares SCG failure information with the MN (200). At S224a, the MN (200) initiates an SCG failure recovery action.

[0069] Figure 2b is a sequential flow chart showing a step-by-step method for indicating early SCG failure to a MN in an MR-DC scenario according to an embodiment disclosed herein, wherein SRB1, SRB2 are configured on the MCG and SRB3 is configured on the SCG, wherein the MCG cell may belong to EUTRAN or NR, and the SCG cell belongs to NR.

[0070] In the SN RRC reconfiguration sent to the UE (100) (via the MN over SRB1 or directly via SRB3), the network configures the T312 timer value for the UE (100). This can be configured in one of the following ways:

[0071] 1. As part of the measurement configuration provided by the SN to the UE (100), or

[0072] 2. Via RRC Reconfiguration Container, in RLF-TimersAndConstants in spCellConfig.

[0073] In an embodiment, the method configures T312 as part of the measurement configuration. The T312 value is usually configured for an intra-RAT measurement object, which is configured to assist the network in triggering a PCell change procedure. However, even for measurement objects required for SCG change or PSCell change, the T312 value needs to be introduced.

[0074] Different deployment scenarios may require different handover preparation times. For example, the handover preparation time for intra-gNB PCell change on the Xn interface may be different from the handover preparation time based on inter-gNB PCell change, which may also be different based on the admission control process related to the service and load on the target cell. Therefore, it is not optimal to configure the same T312 value for all these cases. In order to effectively meet the desired goal of early RLF detection, different T312 values ​​can be configured for different measurement objects. Measurement objects and reporting configurations related to SCG changes or PSCell changes should also be allowed to be configured with a T312 timer.

[0075] The T312 value can be configured as part of a measurement object as shown below. In this case, the measurement object for which T312 is set will be related to the frequencies where a PSCell change can be performed. These are the frequencies served by the SN nodes deployed in the network.

[0076]

[0077] or

[0078]

[0079] The application of T312 for a specific measurement report is based on an indication of the need for T312 for the configured reporting configuration. T312 uses a generic IE that can be configured to be applied to any reporting configuration within an EventTriggerConfig, as shown below:

[0080]

[0081]

[0082] Alternatively, the use of T312 can be signaled as a measurement event specific configuration within EventTriggerConfig as shown below. The application of T312 can be configured independently for all events. Although the network can configure the main use case of T312 only for the situation presented in the figure below, the use of T312 is not limited to the figure below.

[0083]

[0084] In another embodiment, the method can be used to configure T312 in RRCReconfiguration using RLF-TimersandConstants in spCellConfig. In another method, the T312 value can be signaled as a UE-specific timer value and is independent of the measurement object. In this case, it is proposed that T312 is configured by the SN as part of the spCellConfig used in SCG modification, SCG change and SCG switching scenarios. The method for configuring T312 for a PSCell (or SCG) is as follows:

[0085]

[0086] In another embodiment, the method can be used to indicate the cause of SCG failure due to expiration of T312. Once RLF (i.e., SCG failure) occurs on the PSCell, the UE (100) initiates an action related to the SCG failure. The SCG failure information is sent to the MN to notify the network about the failure of the SCG link, thereby indicating to the network that recovery actions need to be performed. In addition, this failure information also carries a trigger or cause for this failure. Link failure due to expiration of T310 is different from link failure due to expiration of T312. The expiration of T310 will mean that the UE channel conditions become unsuitable and the UE channel cannot be maintained on the cell with the required quality. This does not reflect the existence of neighboring cells with potential PSCell changes to the network. The UE (100) sends results for all cells it detects in order to assist the network in the recovery process. However, the expiration of T312 will notify the network that the SCG link failure is caused by the deterioration of the quality of the serving PSCell, and also notify the network that there are neighboring cells with better signal conditions available nearby. The network may change the reporting configuration of these available neighbor cells in the future so that the measurement report can be sent before the T310 timer is started (before the serving cell channel deteriorates to this extent). In addition, it is also important for the network and operator to distinguish between RLFs in the network due to T312 expiration and due to T310 expiration so that the correct configuration can be made. From the network perspective, the corrective actions for T310 expiration and T312 expiration are different. Therefore, it is important that the network identifies these failures differently and therefore requires the UE (100) to clearly indicate these failures to the network. Therefore, in the case of SCG failure (PScell ​​RLF), the UE (100) should be provided with an RLF cause value indicating T312 expiration, as shown below:

[0087] For EN-DC and NGEN-DC, SCG failure due to T312 expiration:

[0088] 5.7.3.3 Determination of failure type for (NG) EN-DC

[0089] The UE shall set the SCG failure type (failureType) as follows:

[0090] 1> If the UE initiates the transmission of the SCGFailureInformationNR message due to the expiration of T310:

[0091] 2> Set failureType to t310-Expiry;

[0092] 1> Otherwise, if the UE initiates the transmission of the SCGFailureInformationNR message due to the expiration of T312:

[0093] 2> Set failureType to t312-Expiry;

[0094] 1> Otherwise, if the UE initiates the transmission of the SCGFailureInformationNR message to provide reconfiguration of synchronization failure information with the SCG:

[0095] 2>Set failureType to synchReconfigFailure-SCG;

[0096] 1> Otherwise, if the UE initiates the transmission of the SCGFailureInformationNR message to provide a random access problem indication from the SCG MAC:

[0097] 2> Set failureType to randomAccessProblem;

[0098] 1> Otherwise, if the UE initiates the transmission of the SCGFailureInformationNR message to provide an indication from the SCG RLC that the maximum number of retransmissions has been reached:

[0099] 2> Set failureType to rlc-MaxNumRetx;

[0100] 1> Otherwise, if the UE initiates a SRB3 IP check failure

[0101] Transmission of SCGFailureInformationNR message:

[0102] 2> Set failureType to srb3-IntegrityFailure;

[0103] 1> Otherwise, if the UE initiates transmission of the SCGFailureInformationNR message due to reconfiguration failure of the NR RRC reconfiguration message:

[0104] 2>Set failureType to scg-reconfigFailure.

[0105]

[0106] For NE-DC, SCG failure due to T312 expiration: The use of T314 is for illustration only. You can use T314 / T315 / T312, etc.

[0107] 5.6.13.x Transmission of SCG Failure Information to NE-DC

[0108] UEs should:

[0109] 1> If the SCG failure is due to the expiration of T313:

[0110] 2> Treat failureType as t313-Expiry;

[0111] 1> Otherwise, if the SCG failure is due to T314 expiration:

[0112] 2> Treat failureType as t314-Expiry;

[0113] 1> Otherwise, if the SCG failure was due to an indication from the SCG MAC that a random access problem was detected:

[0114] 2> Treat failureType as randomAccessProblem;

[0115] 1> Otherwise, if the SCG failure is due to an indication from the SCG RLC that the maximum number of retransmissions has been reached:

[0116] 2> Treat failureType as rlc-MaxNumRetx;

[0117] 1> Otherwise, if the SCG failure is due to a SCG change failure:

[0118] 2>Treat failureType as scg-ChangeFailure;

[0119] 1> Otherwise, if the SCG failure is due to exceeding the maximum uplink transmission timing difference:

[0120] 2> Include failureType and set it to maxUL-TimingDiff;

[0121] 1> Set the content of MeasResultSCG-FailureMRDC as follows:

[0122] 2> for each measObjectEUTRA for which a measId is configured and for which measurements are available;

[0123] 3> Include entries in measResultsFreqListEUTRA;

[0124] 3> If the serving cell is associated with measObjectEUTRA:

[0125] 4> Set measResultServingCell to include the available number of cells of interest and conform to the performance requirements in TS36.133

[16] ;

[0126] 3> set measResultNeighCellList to include the best measured cells, ordered so that the best cell is listed first, and based on the measurements collected until the UE detects failure (including an optional field for each cell where measurement results are available);

[0127] 1> Initiate the transmission of SCG failure information (i.e., failureType and MeasResultSCG-FailureMRDC) via the NR MCG embedded in NR RRCSCGFailureInformationEUTRA as specified in TS 38.331 [X, 5.7.x]

[0128]

[0129] For NR-DC, SCG failure due to T312 expiration:

[0130]

[0131] 5.7.3.3 Determination of failure type for NR-DC

[0132] The UE shall set the SCG failure type as follows:

[0133] 1> If the UE initiates the transmission of the SCGFailureInformationNR message due to the expiration of T310:

[0134] 2> Set failureType to t310-Expiry;

[0135] 1> Otherwise, if the UE initiates the transmission of the SCGFailureInformationNR message due to the expiration of T312:

[0136] 2> Set failureType to t312-Expiry;

[0137] 1> Otherwise, if the UE initiates the transmission of the SCGFailureInformationNR message to provide reconfiguration of synchronization failure information with the SCG:

[0138] 2>Set failureType to synchReconfigFailure-SCG;

[0139] 1> Otherwise, if the UE initiates the transmission of the SCGFailureInformationNR message to provide a random access problem indication from the SCG MAC:

[0140] 2> Set failureType to randomAccessProblem;

[0141] 1> Otherwise, if the UE initiates the transmission of the SCGFailureInformationNR message to provide an indication from the SCG RLC that the maximum number of retransmissions has been reached:

[0142] 2> Set failureType to rlc-MaxNumRetx;

[0143] 1> Otherwise, if the UE initiates a SRB3 IP check failure

[0144] Transmission of SCGFailureInformationNR message:

[0145] 2> Set failureType to srb3-IntegrityFailure;

[0146] 1> Otherwise, if the UE initiates transmission of the SCGFailureInformationNR message due to reconfiguration failure of the NR RRC reconfiguration message:

[0147] 2>Set failureType to scg-reconfigFailure.

[0148] In an embodiment, the method may be used to process timer T312 in NR standalone operation (3GPP TS 38.331). In the NR standalone scenario, the network may configure T312 in one of the following procedures described above:

[0149] 1. As a measurement object specific configuration within a measurement configuration from the gNB, or

[0150] 2. As a UE-specific configuration in RRCReconfiguration using RLF-TimersAndConstants in spCellConfig

[0151] If T312 is configured for the UE (100), and measurement reporting is triggered when T310 is run for a measurement object and report configuration configured with T312, timer T312 is started as follows.

[0152] 5.5.4 Measurement report trigger

[0153] 5.5.4.1 Overview

[0154] If security has been successfully activated, the UE shall:

[0155] 1>For each measId included in measIdList in VarMeasConfig:

[0156] …

[0157] 2> If reportType is set to eventTriggered, and if the entry conditions applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) are met for one or more applicable cells for all layer 3 filtered measurements made during the timeToTrigger defined for the event in VarMeasConfig, and VarMeasReportList does not include a measurement report entry for that measId (first cell triggering event):

[0158] 3> Include the measurement report entry of the measId in VarMeasReportList;

[0159] 3> Set numberOfReportsSent of the measId defined in VarMeasReportList to 0;

[0160] 3> Include the concerned cell(s) of the measId in the cellsTriggeredList defined in VarMeasReportList;

[0161] 3> If the UE supports T312, and if useT312 is included for this event, and if T310 is running;

[0162] 4> If T312 is not running

[0163] 5> Start timer T312 with the value configured in the corresponding measObject

[0164] 3> Initiate the measurement reporting process as specified in 5.5.5;

[0165] 2> Otherwise, if reportType is set to eventTriggered, and if the entry conditions applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) are met for all layer 3 filtered measurements made during the timeToTrigger defined for the event in VarMeasConfig for one or more applicable cells not included in cellsTriggeredList (subsequent cell triggered events):

[0166] 3> Set numberOfReportsSent of the measId defined in VarMeasReportList to 0;

[0167] 3> Include the concerned cell(s) of the measId in the cellsTriggeredList defined in VarMeasReportList;

[0168] 3> If the UE supports T312, and if useT312 is included for this event, and if T310 is running;

[0169] 4> If T312 is not running

[0170] 5> Start timer T312 with the value configured in the corresponding measObject

[0171] 3> Initiate the measurement reporting process as specified in 5.5.5;

[0172] In an embodiment, when a handover command or a reconfiguration with synchronization message is received from the network, or when the UE (100) initiates a reestablishment message, or when the UE (100) recovers from a lower layer problem, the timer T312 is stopped as follows:

[0173] 5.3.5.5.2 Reconfiguration with synchronization

[0174] The UE shall do the following to perform reconfiguration with synchronization.

[0175] 1> If security is not activated, perform the actions specified in 5.3.11 when entering RRC_IDLE with release cause "other", and the process ends when the release cause is "other";

[0176] 1> If running, stop the timer T310 for the corresponding SpCell;

[0177] 1> If for PCell, reconfigurationWithSync is received

[0178] 2> If running, stop timer T312 for Pcell;

[0179] 1>Start timer T304 for the corresponding SpCell, the timer value is set to t304, and the timer value is included in reconfigurationWithSync;

[0180] …

[0181] or

[0182] 5.3.5.5.2 Reconfiguration with synchronization

[0183] The UE shall do the following to perform reconfiguration with synchronization.

[0184] 1> If security is not activated, perform the actions specified in 5.3.11 when entering RRC_IDLE with release cause "other", and the process ends when the release cause is "other";

[0185] 1> If running, stop the timer T310 for the corresponding SpCell;

[0186] 1> If running, stop the timer T312 for the corresponding SpCell;

[0187] 1>Start timer T304 for the corresponding SpCell, and set the timer value to t304, which is included in reconfigurationWithSync;

[0188] …

[0189] 5.3.7 RRC Connection Reestablishment

[0190] 5.3.7.2 Initialization

[0191] The UE initiates the process when one of the following conditions is met:

[0192] 1> According to 5.3.10, when a radio link failure of the MCG is detected; or

[0193] 1> upon reconfiguration with synchronization failure of the MCG, in accordance with subclause 5.3.5.8.3; or

[0194] 1> upon failure of removal from NR in accordance with subclause 5.4.3.5; or

[0195] 1> upon an integrity check failure indication from lower layers on SRB1 or SRB2, unless an integrity check failure is detected on the RRCReestablishment message; or

[0196] 1> According to subclause 5.3.5.8.2, when RRC connection reconfiguration fails.

[0197] At the initialization of the procedure, the UE shall:

[0198] 1> If it is running, stop timer T310;

[0199] 1> If it is running, stop timer T312;

[0200] 1> If it is running, stop timer T304;

[0201] …

[0202] 5.3.10.2 Recovery from physical layer problems

[0203] When N311 consecutive "In Sync" indications are received from lower layers for the SpCell while T310 is running, the UE shall:

[0204] 1> Stop the timer T310 for the corresponding SpCell.

[0205] 1> When N311 consecutive "in sync" indications are received on PCell, stop timer T312 for PCell if it is running

[0206] or

[0207] 5.3.10.2 Recovery from physical layer problems

[0208] When N311 consecutive "In Sync" indications are received from lower layers for the SpCell while T310 is running, the UE shall:

[0209] 1> Stop the timer T310 for the corresponding SpCell;

[0210] 1> Stop timer T312 for the corresponding SpCell

[0211] When T312 expires, the UE (100) declares a radio link failure (RLF) and initiates radio link failure recovery using the re-establishment procedure as follows:

[0212] 5.3.10.3 Detection of radio link failure

[0213] UEs should:

[0214] 1>When T310 in PCell expires; or

[0215] 1>When T312 in PCell expires, or

[0216] 1> When T300, T301, T304, T311 and T319 are not running, in case of a random access problem indication from the MCG MAC; or

[0217] 1> In case of an indication from the MCG RLC that the maximum number of retransmissions has been reached:

[0218] 2> If CA replication is configured and activated; and for the corresponding logical channel, allowedServiceCells only includes (multiple) SCells:

[0219] 3> Initiate the Failure Information procedure as specified in 5.7.5 to report the RLC failure.

[0220] 2> Otherwise:

[0221] 3> Consider the radio link failure (ie RLF) to be detected for MCG;

[0222] 3> If AS security is not activated:

[0223] 4> Perform the actions specified in 5.3.11 when entering RRC_IDLE, and the release reason is "other";

[0224] 3> Otherwise, if AS security has been activated, but SRB2 and at least one DRB have not been established:

[0225] 4> Perform the actions specified in 5.3.11 when entering RRC_IDLE, and the release reason is "RRC connection failure";

[0226] 3> Otherwise:

[0227] 4> Initiate the connection reestablishment process as specified in 5.3.7.

[0228] In an embodiment, the method may be used to handle T312 in (NG)EN-DC operation. In (NG)EN-DC operation (3GPP TS 36.331), in (NG)EN-DC configuration or on LTE PCell / MCG when the UE (100) is configured to operate in (NG)EN-DC, the configuration of T312 may be provided based on the existing signaling mechanism provided in the LTE specification (as part of the measurement configuration). The configuration and value of T312 are provided as part of the measurement object configuration, while the application of T312 is provided as part of the reporting configuration. LTE (3GPP TS 36.331) already supports early RLF declaration or fast handover recovery mechanism based on T312 on PCell. If T312 is configured for the UE (100) on the MCG, and measurement reporting is triggered when T310 is run for the measurement object and reporting configuration configured with T312, timer T312 is started as follows:

[0229] 5.5.4 Measurement report trigger

[0230] 5.5.4.1 Overview

[0231] If security has been successfully activated, the UE shall:

[0232] 1>For each measId in measIdList included in VarMeasConfig

[0233] …

[0234] 2> If triggerType is set to event, and if the corresponding reportConfig does not include numberOFTriggeringCells, and if the entry condition applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) is met for one or more applicable cells after 3-layer filtering for all measurements made during the timeToTrigger defined for the event in VarMeasConfig, and VarMeasReportList does not include a measurement report entry for the measId (the first cell triggering event):

[0235] 3> Include the measurement report entry of the measId in VarMeasReportList;

[0236] 3> Set numberOfReportsSent of the measId defined in VarMeasReportList to 0;

[0237] 3> Include the concerned cell(s) of the measId in the cellsTriggeredList defined in VarMeasReportList;

[0238] 3> If the UE supports T312, and if useT312 is included for this event, and if T310 is running;

[0239] 4> If T312 is not running

[0240] 5> Start timer T312 with the value configured in the corresponding measObject

[0241] 3> Initiate the measurement reporting process as specified in 5.5.5;

[0242] 2> If triggerType is set to event, and if the corresponding reportConfig does not include numberOFTriggeringCells, and if the entry condition applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) is met for one or more applicable cells not included in cellsTriggeredList for all layer 3 filtered measurements made during timeToTrigger defined for the event in VarMeasConfig (subsequent cell triggered event):

[0243] 3> Set numberOfReportsSent of the measId defined in VarMeasReportList to 0;

[0244] 3> Include the concerned cell(s) of the measId in the cellsTriggeredList defined in VarMeasReportList;

[0245] 3> If the UE supports T312, and if useT312 is included for this event, and if T310 is running;

[0246] 4> If T312 is not running

[0247] 5> Start timer T312 with the value configured in the corresponding measObject

[0248] 3> Initiate the measurement reporting process as specified in 5.5.5;

[0249] When there is a handover command from the network, or when the UE (100) initiates a reestablishment message, or when the UE (100) recovers from a lower layer problem, the timer T312 stops as shown below:

[0250] 5.3.5.4 Receipt of RRCConnectionReconfiguration (Switch) including MobilityControlInfo by UE

[0251] If the RRCConnectionReconfiguration message includes MobilityControlInfo and the UE is capable of complying with the configuration included in this message, the UE shall:

[0252] 1> If it is running, stop timer T310;

[0253] 1> If it is running, stop timer T312;

[0254] …

[0255] 5.3.7 RRC Connection Reestablishment

[0256] 5.3.7.2 Initialization

[0257] The UE shall initiate the procedure only when AS security has been activated or for NB-IoT UEs supporting RRC connection reestablishment for control plane CIoT EPS optimization. The UE initiates the procedure when one of the following conditions is met:

[0258] 1> According to 5.3.11, when a radio link failure is detected; or

[0259] 1> According to 5.3.5.6, in case of handover failure; or

[0260] 1> in case of a failed migration from E-UTRA according to 5.4.3.5; or

[0261] 1> in case of an integrity check failure indication from the lower layer on SRB1 or SRB2; or

[0262] 1> According to 5.3.5.5, in the event of RRC connection reconfiguration failure; or

[0263] 1> According to TS38.331 [82, 5.3.5.5], in the event of RRC connection reconfiguration failure.

[0264] At the initialization of the procedure, the UE shall:

[0265] 1> If it is running, stop timer T310;

[0266] 1> If it is running, stop timer T312;

[0267] …

[0268] 5.3.11.2 Recovery from physical layer problems

[0269] When T310 is running and N311 consecutive PCell "in sync" indications are received from lower layers, the UE shall:

[0270] 1> Stop timer T310;

[0271] 1> If it is running, stop timer T312;

[0272] …

[0273] 5.4.3.3 Reception of MobilityFromEUTRACommand by UE

[0274] The UE shall be able to receive the MobilityFromEUTRACommand message and execute a cell change command to GERAN even if no previous UE measurements have been performed on the target cell.

[0275] UEs should:

[0276] 1> If it is running, stop timer T310;

[0277] 1> If it is running, stop timer T312;

[0278] When T312 expires, the UE declares a radio link failure (RLF) and initiates radio link failure recovery using the re-establishment procedure as follows:

[0279] 5.3.11.3 Detection of radio link failure

[0280] UEs should:

[0281] 1> upon expiry of T310; or

[0282] 1> upon expiry of T312; or

[0283] 1> When T300, T301, T304 and T311 are not running, in case of a random access problem indication from the MCG MAC; or

[0284] 1> In case of an indication from the MCG RLC that the maximum number of retransmissions has been reached for an SRB or DRB (sending is allowed on the PCell):

[0285] In an embodiment, the method may be used to process T312 on NRPS cell / SCG in (NG) EN-DC operation (3GPP TS 38.331). The network (i.e., SN) may configure T312 for the UE (100) in (NG) EN-DC operation mode via MCG (container in MCG reconfiguration message) via SRB1 or directly to the UE (100) via SRB3 by one of the following methods:

[0286] As a measurement object specific configuration within a measurement configuration from the gNB, or

[0287] As UE-specific configuration within RRCReconfiguration, using RLF-TimersandConstants in spCellConfig.

[0288] If T312 is configured for the UE (100), and measurement reporting is triggered when T310 is run for a measurement object and report configuration configured with T312, timer T312 is started as follows.

[0289] 5.5.4 Measurement report trigger

[0290] 5.5.4.1 Overview

[0291] If security has been successfully activated, the UE shall:

[0292] 1>For each measId included in measIdList in VarMeasConfig:

[0293] …

[0294] 2> If reportType is set to eventTriggered, and if the entry conditions applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) are met for one or more applicable cells for all layer 3 filtered measurements made during the timeToTrigger defined for the event in VarMeasConfig, and VarMeasReportList does not include a measurement report entry for that measId (first cell triggering event):

[0295] 3> Include the measurement report entry of the measId in VarMeasReportList;

[0296] 3> Set numberOfReportsSent of the measId defined in VarMeasReportList to 0;

[0297] 3> Include the concerned cell(s) of the measId in the cellsTriggeredList defined in VarMeasReportList;

[0298] 3> If the UE supports T312, and if useT312 is included for this event, and if T310 is running;

[0299] 4> If T312 is not running

[0300] 5> Start timer T312 with the value configured in the corresponding measObject

[0301] 3> Initiate the measurement reporting process as specified in 5.5.5;

[0302] 2> Otherwise, if reportType is set to eventTriggered, and if the entry conditions applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) are met for all layer 3 filtered measurements made during the timeToTrigger defined for the event in VarMeasConfig for one or more applicable cells not included in cellsTriggeredList (subsequent cell triggered events):

[0303] 3> Set numberOfReportsSent of the measId defined in VarMeasReportList to 0;

[0304] 3> Include the concerned cell(s) of the measId in the cellsTriggeredList defined in VarMeasReportList;

[0305] 3> If the UE supports T312, and if useT312 is included for this event, and if T310 is running;

[0306] 4> If T312 is not running

[0307] 5> Start timer T312 with the value configured in the corresponding measObject

[0308] 3> Initiate the measurement reporting process as specified in 5.5.5;

[0309] When a handover command or reconfiguration with synchronization message is received from the network, or when the UE (100) initiates a reestablishment message, or when the UE (100) recovers from a lower layer problem, the timer T312 stops as follows:

[0310] 5.3.5.5.2 Reconfiguration with synchronization

[0311] The UE shall do the following to perform reconfiguration with synchronization.

[0312] 1> If security is not activated, perform the actions specified in 5.3.11 when entering RRC_IDLE with release cause "other", and the process ends when the release cause is "other";

[0313] 1> If running, stop the timer T310 for the corresponding SpCell;

[0314] 1> For PSCell, if reconfigurationWithSync is received

[0315] 2> If it is running, stop timer T312;

[0316] 1>Start timer T304 for the corresponding SpCell, and set the timer value to t304, which is included in reconfigurationWithSync;

[0317] …

[0318] or

[0319] 5.3.5.5.2 Reconfiguration with synchronization

[0320] The UE shall do the following to perform reconfiguration with synchronization.

[0321] 1> If security is not activated, perform the actions specified in 5.3.11 when entering RRC_IDLE with release cause "other", and the process ends when the release cause is "other";

[0322] 1> If running, stop the timer T310 for the corresponding SpCell;

[0323] 1> If running, stop the timer T312 for the corresponding SpCell;

[0324] 1>Start timer T304 for the corresponding SpCell, and set the timer value to t304, which is included in reconfigurationWithSync;

[0325] …

[0326] 5.3.7 RRC Connection Reestablishment

[0327] 5.3.7.2 Initialization

[0328] The UE initiates the process when one of the following conditions is met:

[0329] 1> According to 5.3.10, when a radio link failure of the MCG is detected; or

[0330] 1> in case of reconfiguration with synchronization failure of the MCG according to subclause 5.3.5.8.3; or

[0331] 1> in the event of a failure to remove from NR in accordance with subclause 5.4.3.5; or

[0332] 1> in case of an integrity check failure indication from lower layers on SRB1 or SRB2, unless an integrity check failure is detected on the RRCReestablishment message; or

[0333] 1> According to subclause 5.3.5.8.2, in the event of RRC connection reconfiguration failure.

[0334] At the initialization of the procedure, the UE shall:

[0335] 1> If it is running, stop timer T310;

[0336] 1> If it is running, stop timer T312;

[0337] 1> If it is running, stop timer T304;

[0338] …

[0339] 5.3.10.2 Recovery from physical layer problems

[0340] When N311 consecutive "In Sync" indications are received from lower layers for the SpCell while T310 is running, the UE shall:

[0341] 1> Stop the timer T310 for the corresponding SpCell.

[0342] 1> When N311 consecutive "in sync" indications are received on PCell, stop timer T312 for PCell if it is running

[0343] or

[0344] 5.3.10.2 Recovery from physical layer problems

[0345] When N311 consecutive "In Sync" indications are received from lower layers for the SpCell while T310 is running, the UE shall:

[0346] 1> Stop the timer T310 for the corresponding SpCell;

[0347] 1> Stop timer T312 for the corresponding SpCell

[0348] 5.3.5.4 Release of secondary cell group

[0349] UEs should:

[0350] 1> As a result of SCG release triggered by E-UTRA

[0351] 2> If configured, reset SCG MAC;

[0352] 2> For each RLC bearer that is part of the SCG configuration:

[0353] 3> Perform the RLC bearer release procedure as specified in 5.3.5.5.3;

[0354] 2> Release SCG configuration;

[0355] 2> If it is running, stop the timer T310 for the corresponding SpCell;

[0356] 2> If it is running, stop the timer T312 for the corresponding SpCell;

[0357] 2> If it is running, stop the timer T304 for the corresponding SpCell;

[0358] When T312 expires, the UE (100) declares SCG radio link failure or SCG failure and initiates recovery using the SCG Failure Information procedure as follows:

[0359] 5.3.10.3 Detection of radio link failure

[0360] UEs should:

[0361] …

[0362] UEs should:

[0363] 1>When T310 in PSCell expires; or

[0364] 1>When T312 in PSCell expires; or

[0365] 1> in case of a Random Access Problem indication from the SCG MAC; or

[0366] 1> In case of an indication from the SCG RLC that the maximum number of retransmissions has been reached:

[0367] 2> If CA replication is configured and activated; and for the corresponding logical channel, allowedServiceCells only includes (multiple) SCells:

[0368] 3> Initiate the Failure Information procedure as specified in 5.7.5 to report the RLC failure.

[0369] 2> Otherwise:

[0370] 3> Consider the radio link failure to be detected for SCG (i.e. SCG-RLF);

[0371] 3> Initiate the SCG Failure Information procedure as specified in 5.7.3 to report the SCG radio link failure.

[0372] In an embodiment, the method may be used to process T312 in NE-DC operation. The method may be used to process T312 on NR MCG / PCell in NE-DC operation (3GPP TS 38.331). In NE-DC operation, the processing of T312 on NR MCG or PCell and the operation based on T312 state are similar to the NR independent operation described in the previous section. The same operations and procedures for measurement report triggering, starting, stopping and expiration of T312 apply here.

[0373] For the method of handling T312 on LTE SCG / PSCell in NE-DC operation (3GPP TS 36.331), LTE (3GPP TS 36.331) already supports early RLF declaration or fast switching recovery mechanism based on T312 on PCell. However, in NE-DC configuration, or when the UE is configured to operate in NE-DC, the LTE cell is configured as PSCell or SCG. Fast switching recovery or early RLF declaration on LTE as PSCell can be handled by using T312 or using T314 or T315. In LTE, T312 has been defined in specifications 3GPP TS 36.306 and 36.331 for handling early RLF declaration or fast switching recovery mechanism. However, this is a feature of the old version, and reusing the same feature for SCG recovery may cause backward compatibility issues. Therefore, a new timer T314 or T315 must be introduced in LTE to indicate support for early SCG RLF declaration and fast SCG handover recovery. Otherwise, T312 may be commonly used to control early RLF declaration on both MCG and SCG. In this case, a new UE capability needs to be sent to the network to indicate support for T312 on SCG so that the network knows that the UE also supports T312 operation on SCG. The following example using T312 is for illustration only, and the timer name may be different (e.g., T314 or T315). The configuration of T312 for the PSCell should be provided as part of the measurement configuration. The configuration and value of T312 are provided as part of the measurement object configuration, and the application of T312 is provided as part of the reporting configuration. If T312 is configured for the UE on the SCG, and a measurement report is triggered when T310 is run for the measurement object and reporting configuration configured with T312, timer T312 is started as shown below.

[0374] 5.5.4 Measurement report trigger

[0375] 5.5.4.1 Overview

[0376] If security has been successfully activated, the UE shall:

[0377] 1>For each measId in measIdList included in VarMeasConfig

[0378] …

[0379] 2> If triggerType is set to event, and if the corresponding reportConfig does not include numberOFTriggeringCells, and if the entry condition applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) is met for one or more applicable cells after 3-layer filtering for all measurements made during the timeToTrigger defined for the event in VarMeasConfig, and VarMeasReportList does not include a measurement report entry for the measId (the first cell triggering event):

[0380] 3> Include the measurement report entry of the measId in VarMeasReportList;

[0381] 3> Set numberOfReportsSent of the measId defined in VarMeasReportList to 0;

[0382] 3> Include the concerned cell(s) of the measId in the cellsTriggeredList defined in VarMeasReportList;

[0383] 3> If the UE supports T312, and if useT312 is included for this event, and if T310 is running;

[0384] 4> If T312 is not running

[0385] 5> Start timer T312 with the value configured in the corresponding measObject

[0386] 3> Initiate the measurement reporting process as specified in 5.5.5;

[0387] 2> If triggerType is set to event, and if the corresponding reportConfig does not include numberOFTriggeringCells, and if the entry condition applicable to the event (i.e., the event corresponding to the eventId of the corresponding reportConfig in VarMeasConfig) is met for one or more applicable cells not included in cellsTriggeredList for all layer 3 filtered measurements made during timeToTrigger defined for the event in VarMeasConfig (subsequent cell triggered event):

[0388] 3> Set numberOfReportsSent of the measId defined in VarMeasReportList to 0;

[0389] 3> Include the concerned cell(s) of the measId in the cellsTriggeredList defined in VarMeasReportList;

[0390] 3> If the UE supports T312, and if useT312 is included for this event, and if T310 is running;

[0391] 4> If T312 is not running

[0392] 5> Start timer T312 with the value configured in the corresponding measObject

[0393] 3> Initiate the measurement reporting process as specified in 5.5.5;

[0394] When there is a handover command from the network, or when the UE initiates a reestablishment message, or when the UE recovers from a lower layer problem, timer T312 stops as shown below:

[0395] 5.3.5.4 Receipt of RRCConnectionReconfiguration (Switch) including MobilityControlInfo by UE

[0396] If the RRCConnectionReconfiguration message includes MobilityControlInfo and the UE is capable of complying with the configuration included in this message, the UE shall:

[0397] 1> If it is running, stop timer T310;

[0398] 1> If it is running, stop timer T312;

[0399] …

[0400] 5.3.7 RRC Connection Reestablishment

[0401] 5.3.7.2 Initialization

[0402] The UE shall initiate the procedure only when AS security has been activated or for NB-IoT UEs supporting RRC connection reestablishment for control plane CIoT EPS optimization. The UE initiates the procedure when one of the following conditions is met:

[0403] 1> According to 5.3.11, when a radio link failure is detected; or

[0404] 1> According to 5.3.5.6, in case of handover failure; or

[0405] 1> in case of a failed migration from E-UTRA according to 5.4.3.5; or

[0406] 1> in case of an integrity check failure indication from the lower layer on SRB1 or SRB2; or

[0407] 1> According to 5.3.5.5, in the event of RRC connection reconfiguration failure; or

[0408] 1> According to TS38.331 [82, 5.3.5.5], in the event of RRC connection reconfiguration failure.

[0409] At the initialization of the procedure, the UE shall:

[0410] 1> If it is running, stop timer T310;

[0411] 1> If it is running, stop timer T312 on PCell;

[0412] 1> If it is running, stop timer T313;

[0413] 1> If it is running, stop timer T312 on PSCell;

[0414] …

[0415] 5.3.11.2 Recovery from physical layer problems

[0416] When N311 consecutive PCell "in sync" indications are received from lower layers while T310 is running, the UE shall:

[0417] 1> Stop timer T310;

[0418] 1> If running, stop timer T312 for PCell;

[0419] 1> Stop timer T310;

[0420] 1> If running, stop timer T312 for PSCell;

[0421] …

[0422] 5.4.3.3 Reception of MobilityFromEUTRACommand by UE

[0423] The UE shall be able to receive the MobilityFromEUTRACommand message and execute a cell change command to GERAN even if no previous UE measurements have been performed on the target cell.

[0424] UEs should:

[0425] 1> If it is running, stop timer T310;

[0426] 1> If it is running, stop timer T312;

[0427] 5.3.10.10 SCG Reconfiguration

[0428] UEs should:

[0429] 1> If makeBeforeBreakSCG is configured:

[0430] 2> If it is running, stop timer T313;

[0431] 2> If it is running, stop timer T312;

[0432]

[0433]

[0434] When T312 expires, the UE declares SCG radio link failure or SCG failure and initiates recovery using the SCG Failure Information procedure as follows:

[0435] 5.3.11.3 Detection of radio link failure

[0436] …

[0437] In case of DC, the UE should:

[0438] 1> upon expiry of T310; or

[0439] 1>When T312 in PSCell expires,

[0440] 1> in case of a Random Access Problem indication from the SCG MAC; or

[0441] 1> In case of an indication from the SCG RLC that the maximum number of retransmissions has been reached for the SCG or split DRB (sending is allowed on the PSCell):

[0442] 2> Consider the radio link failure to be detected for SCG (i.e. SCG-RLF);

[0443] 2> Initiate the failure information procedure as specified in 5.6.13 to report the SCG radio link failure;

[0444] In case of CA PDCP duplication, the UE shall:

[0445] 1> In case of an indication from the RLC entity that the maximum number of retransmissions has been reached (sending is only allowed on SCell):

[0446] 2> Consider the radio link failure to be detected for RLC;

[0447] 2> Initiate the Failure Information procedure as specified in 5.6.21 to report the PDCP duplication failure;

[0448] Upon power off or detachment, the UE may discard the radio link failure information (ie, release the UE variable VarRLF-Report) 48 hours after detecting the radio link failure.

[0449]

[0450]

[0451] In an embodiment (NR-DC), the procedural text for NR SA from TS 38.331 applies to NR-MCG, and the procedural text for NR SCG from TS 38.331 applies. In an embodiment, the method of processing T312 in NR-DC operation, the method of processing T312 on NR MCG / PCell in NR-DC operation (3GPP TS 38.331), processing T312 on NR MCG or PCell in NR-DC operation, and the operation based on T312 state are similar to the NR independent operation described in the previous section. The same operations and procedures for measurement report triggering, starting, stopping, and expiration of T312 apply here.

[0452]

[0453] In an embodiment, the method of processing T312 on NR SCG / PSCell in NE-DC operation (3GPP TS 38.331), processing T312 on NR SCG or PSCell in NR-DC operation, and operations based on T312 status are similar to the processing of T312 on NR SCG when operating in (NG) EN-DC operation described in the previous section. The same operations and procedures for measurement report triggering, starting, stopping, and expiration of T312 apply here.

[0454] In the example, at S202b, the SN (300) sends a measurement configuration to the UE (100). At S204b, data from the SN bearer is established between the UE (100) and the SN (300). At S206b, the SN (300) sends an RRC reconfiguration to the UE (100). At S208b, the UE (100) detects the Qout of the PSCell. At S210a, the UE (100) starts a timer (i.e., T310) for the PSCell. At S212a, the UE (100) sends a measurement report to the SN (300) via an SRB3 message. At S214b, the UE (100) starts a second timer (i.e., T312), and the second timer expires and the first timer stops. At S216b, the UE (100) initiates an SCG failure procedure. At S218b, the UE (100) shares the SCG failure information with the MeNB (200). In S220b, the MeNB (200) initiates an SCG failure recovery action.

[0455] Figure 3a is a flow chart illustrating a method for attempting cell selection on LTE (or next priority RAT) upon expiration of T310 according to embodiments disclosed herein.

[0456] In an embodiment, a method may be used to detect RLF using T312 for IRAT measurement reporting. The method explained above is related to early SCG failure detection and indication in dual-connectivity scenarios. This feature is also useful in single-connectivity scenarios. Currently, early RLF detection based on T312 is mainly used for intra-RAT coverage boundaries. With the introduction of NR technology, existing LTE networks are expected to be upgraded to support NR operations. However, NR services are not available in every location. Early deployments of integrating NR on existing LTE networks were intended to provide NR services in selected areas. These deployments are hotspots that are used to provide improved broadband services to subscribers while maintaining existing LTE RF footprints to provide coverage when the UE leaves these NR available areas. Therefore, NR coverage is expected to be sparse. As a result, there will be situations where a UE in a connected state in NR cannot maintain a channel and there are no available NR neighboring cells. The UE eventually meets the Qout criteria and T310 is initiated. At the expiration of T310, the UE will first attempt to recover on NR, and the failure of this attempt will result in an attempt to select a cell on LTE (or the next priority RAT), such as Figure 3a shown.

[0457] In the example, at S302a, the UE (100) obtains measurement configuration from the source gNB (i.e., NR). At 304a, a data path and a control path are established between the UE (100) and the source gNB. At 306a, the UE (100) determines that Qout is satisfied for the serving cell. At S308a, a first timer (i.e., T310) is started for the serving cell. At S310a, the UE (100) sends an IRAT measurement report to the source gNB (i.e., NR). At S312a, T310 expires and the UE (100) declares RLF. At S314a, the UE (100) initiates a cell selection process. At S316a, the UE (100) does not select a suitable cell for NR, but selects an LTE cell. At S318a, the UE (100) sends an RRC connection request to the target eNB (i.e., LTE).

[0458] Figure 3b 1 is a flowchart illustrating a method according to an embodiment disclosed herein, in which a NR removal command or a handover to LTE command is not received from the network eventually due to expiration of T310, thereby causing RLF.

[0459] In the case where only LTE neighbor cells are available and the UE has triggered an IRAT measurement report for the LTE neighbor cells, the UE knows that there are LTE cells available nearby that are suitable for handling the service. However, since the UE is in an unsynchronized state, it may not receive a command to move out of NR or a command to switch to LTE from the network due to the expiration of T310, which eventually leads to RLF. If T312 is configured for the IRAT measurement object, the UE will start T312 once the IRAT reporting criteria are met and the measurement report is sent to the network. At the expiration of T312, the UE will declare an early RLF and attempt a faster recovery on the LTE cell. This recovery can be achieved by attempting an LTE cell search on the RLF declaration using the knowledge that the UE has identified that only LTE cells are within its coverage. Otherwise, RLF recovery can be attempted on NR first, and if no suitable cell is found, recovery can be attempted on the LTE cell. In this case, the UE will attempt to establish a connection by sending an RRC connection request message instead of performing RRC reestablishment on the LTE cell to attempt to establish a connection. The T312 configuration in NR for IRAT can use UE-specific timer value configuration as part of SIB1 carrying ue-timersAndconstants or use measurement object specific configuration as shown below:

[0460] T312 configuration using ue-timersAndConstants in SIB1:

[0461]

[0462] T312 configuration in IRAT measurement object configuration on NR (MeasObjectEUTRA):

[0463]

[0464] or

[0465]

[0466] Looking ahead, NR is expected to be deployed in heterogeneous deployments with two operating frequencies (FR1, i.e. below 6 GHz; FR2, i.e. above 6 GHz), with a large number of small pico cells deployed on FR2 and large macro cells deployed on FR1. There may be locations where only NR coverage is available and LTE cells are not suitable. In the future, operators may migrate LTE cells connected to EPC to eLTE cells that can operate with 5GC (5G core network, NR core network). In order for operators to maintain a single core network, support for EPC may be interrupted. In areas where there is no LTE coverage, NR coverage may be available. In addition, FR2 cells with small coverage and high bandwidth will be densely deployed to provide NR services and improved mobile broadband to users. These cells with small coverage will likely cover the gaps between other coverage areas. Therefore, a UE operating on LTE may only have neighboring NR cells that are suitable (under good signal conditions) and can provide services to the UE. Therefore, it is necessary to allow early RLF detection based on T312 for IRAT measurement reports as well. The T312 configuration in the LTE system shall support the IRAT NR measurement object as follows:

[0467] IRATNR report from EUTRAN serving cell:

[0468]

[0469] The UE (100) may be configured to apply a configuration based on T312 based on the application of the network configuration T312 in the report configuration IRAT measurements (i.e., events B1 and B2). There are different signaling options for application. The application of T312 for a specific measurement report is based on an indication of the need for T312 for the configured report configuration. For EUTRA report configuration when connected to an NR cell, T312 uses a generic IE that can be configured to be applied to any report configuration within EventTriggerConfig, as shown below:

[0470]

[0471] Alternatively, T312 usage can be signaled as a measurement event specific configuration within EventTriggerConfig as shown below:

[0472]

[0473] Similarly, for reporting configuration of NR frequencies when connected to EUTRA, T312 uses a generic IE that can be configured to be applied to any reporting configuration within ReportConfigInterRAT as shown below:

[0474]

[0475]

[0476] At 302b, the UE (100) obtains measurement configuration from the source gNB (i.e., LTE). At 304b, a data path and a control path are established between the UE (100) and the source gNB (i.e., LTE). At 306b, the UE (100) determines that Qout is satisfied for the serving cell. At 308b, a first timer (i.e., T310) is started for the serving cell. At 310b, the UE (100) sends an IRAT measurement report to the source gNB (i.e., LTE). At 312b, T310 expires and the UE (100) declares RLF. At 314b, the UE (100) initiates a cell selection process. At 316b, the UE (100) does not select an LTE cell, but selects an NR cell. At 318b, the UE (100) sends an RRC establishment request to the target eNB (NR).

[0477] Figure 4a is a flow chart illustrating a method according to an embodiment disclosed herein, of enabling a UE to recover from a service interruption by allowing the UE to perform a connection establishment on a target cell faster than if T312 is not applied.

[0478] After selecting a suitable cell on the target RAT (an LTE cell in case of expiration of T312 on NR, or an NR cell in case of expiration of T312 on LTE), the UE does not perform reestablishment because the target cell cannot retrieve the UE context, and the UE cannot reestablish the connection to the target RAT. As a result, the UE performs a new connection establishment. This method enables the UE to recover from a service interruption by allowing the UE to perform a connection establishment on the target cell faster than if T312 were not applied. This process is as follows Figure 4a shown.

[0479] In the example, at S402a, the UE (100) obtains a measurement configuration from a source gNB (i.e., NR). At S404a, a data path and a control path are established between the UE (100) and the source gNB. At S406a, the UE (100) determines that Qout is satisfied for the serving cell. At S408a, a first timer (i.e., T310) is started for the serving cell. At S410a, the UE (100) sends a measurement report to the source gNB (i.e., NR). At S412a, T310 expires, T310 stops, and the UE (100) declares RLF. At S414a, the UE (100) initiates a cell selection process. At S416a, the UE (100) does not select a suitable cell for NR, but selects an LTE cell. At 418a, the UE (100) sends an RRC connection request to the target eNB (i.e., LTE).

[0480] Figure 4b is a flow chart illustrating a method for sending an RRC establishment request from a source eNB (LTE) to a target gNB (NR) upon expiration of T312 according to an embodiment disclosed herein.

[0481] In the example, at 402b, the UE (100) obtains a measurement configuration from a source gNB (i.e., LTE). At 404b, a data path and a control path are established between the UE (100) and the source gNB (i.e., LTE). At 406b, the UE (100) determines that Qout is satisfied for the serving cell. At 408b, a first timer (i.e., T310) is started for the serving cell. At S410b, the UE (100) sends a measurement report to the source gNB (i.e., LTE). At S412b, T310 expires and the UE (100) declares RLF. At 414b, the UE (100) initiates a cell selection procedure. At 416b, the UE (100) does not select an LTE cell, but selects an NR cell. At 418b, the UE (100) sends an RRC establishment request to the target eNB.

[0482] Figure 5a is a flowchart illustrating a method of stopping T312 when an exit condition is met according to an embodiment disclosed herein.

[0483] In an embodiment, a method for processing T312 when the exit condition of the report configuration is met is shown. As previously described, once T310 is running on the UE and a measurement report is triggered for an event configured to use T312, T312 is started. When T312 expires, the UE declares an early RLF or SCG failure on the PCell (i.e., an early RLF on the PSCell) and attempts to recover. However, when T312 is running, the UE may meet the exit condition of the event that triggered the measurement report. This may be caused by an improvement in the signal conditions of the serving cell, or it may be caused by a deterioration in the signal conditions of the neighboring cell.

[0484] In an embodiment, the method can be used to stop T312 when the departure condition is met. If the departure condition is met due to an improvement in the serving cell condition, the UE is likely to return to the synchronization state and can further continue to operate on the serving cell. This situation occurs when the signal condition of the serving cell temporarily deteriorates due to any short-term fading or interference towards the cell edge, and not necessarily because the UE is moving towards the edge of the coverage of the serving cell and towards the coverage of the neighboring cell. The UE is likely to recover the signal condition and be able to maintain the radio link. In this case, the UE can receive a handover message from the network instead of declaring an early RLF and performing a recovery process. Therefore, it is proposed that the UE stops T312 when the UE meets the departure condition of the reporting configuration (for which the measurement report is sent to the network earlier (this is the MR that triggers the start of timer T312)).

[0485] Similarly, if the Leave condition is met due to deterioration of neighbor cell signal conditions, it is likely that the neighbor cell channel is not strong enough to handle the UE that was once connected to it. In this case, it is optimal to provide the UE with an increased chance of recovering the serving cell by monitoring the synchronization indication. If the Leave condition for a frequency has been met due to deterioration of neighbor cell signal conditions, there is no benefit in declaring early RLF and attempting a fast recovery because the neighbor cell may no longer be suitable. As a result, stopping T312 when the Leave condition is met will provide the UE with more opportunities to monitor synchronization from the serving cell, as well as monitor other neighbor cells that meet the measurement report entry condition, and T312 can be started.

[0486] Therefore, it may be beneficial for the UE if timer T312 is stopped when the exit condition for the measurement configuration started for T312 is met. When T310 is running and use-T312 is configured, the UE needs to ensure that no other measurement reports are sent to the network. If there are other measurement reports sent to the network while T310 is running, the UE will only stop T312 if this is the last measurement configured for T312 (no other measurement still meets the entry condition of the reported MR). Figure 5 shows the UE process based on stopping T312 when the exit condition is met.

[0487] In the example, at S502, the UE (100) in the connected state performs RLM. At S504, the UE (100) determines whether NT310 / Qout is satisfied? If NT310 / Qout is not satisfied, the method executes step 502a. If NT310 / Qout is satisfied, at S506a, the UE (100) starts T310. At S508a, the UE (100) monitors the synchronization indication. At S510a, the UE determines whether the MR is triggered by T312. If the MR is triggered by T312, at S512a, the UE (100) starts / restarts T310. If the MR is not triggered by T312, at S516a, the UE (100) monitors the synchronization indication.

[0488] At 514a, the UE (100) determines whether the MR leaves the condition. If the MR leaves the condition, then at S512a, the UE (100) starts / restarts T310. If the MR does not leave the condition, the method performs step S516a. At 518a, the UE (100) determines whether T312 has expired and whether T310 has expired. If T312 has not expired and T310 has not expired, the method performs step S508a. If T312 has expired and T310 has expired, then at S522a, the UE (100) declares RLF / SCG failure. At S524a, the method performs a recovery process.

[0489] Figure 5b is a flowchart illustrating a method of restarting T312 when a leaving condition is met according to an embodiment disclosed herein.

[0490] In the example, at S502b, the UE (100) in the connected state performs RLM. At S504b, the UE (100) determines whether NT310 / Qout is satisfied? If NT310 / Qout is not satisfied, the method executes step 502b. If NT310 / Qout is satisfied, at S506b, the UE (100) starts T310. At S508b, the UE (100) monitors the synchronization indication. At S510b, the UE determines whether the MR is triggered by T312. If the MR is triggered by T312, at S512b, the UE (100) starts / restarts T310. If the MR is not triggered by T312, at S518b, the UE (100) monitors the synchronization indication.

[0491] At 514b, the UE (100) determines whether the MR leaves the condition. If the MR leaves the condition, then at S516b, the UE (100) stops T312. If the MR does not leave the condition, the method performs step S518b. At 520b, the UE (100) determines whether T312 has expired and whether T310 has expired. If T312 has not expired and T310 has not expired, the method performs step S508b. If T312 has expired and T310 has expired, then at S522b, the UE (100) declares RLF / SCG failure. At S524b, the method performs a recovery process.

[0492] In an embodiment, a method may be used to restart T312 when a leaving condition is met. If the leaving condition is met due to an improvement in the serving cell condition, the UE needs to ensure that this is not an instantaneous change, because there is no time to trigger the associated configuration when monitoring the leaving criteria of the event. The serving cell measurement result may indicate improvement only during one measurement opportunity, and meet the entry criteria again in the next measurement opportunity, resulting in frequent fluctuation measurements at the UE. Stopping T312 during the first opportunity to meet the leaving criteria will cause the UE to start T312 at a later time point when the entry criteria are met again. This causes the UE to be in an out-of-sync state for longer than required, and may violate the goal of an early RLF declaration. If the serving cell signal condition has actually improved due to meeting the leaving condition, it provides the UE to continue normal operation and may return to a synchronized state. The probability of correctly receiving a handover command from the network will also increase. When the leaving condition is met, continuing T312 will give the UE less time and fewer opportunities to receive a handover message from the network and return to a synchronized state.

[0493] Similarly, if the leave criteria are met due to deterioration of neighbor cell signal conditions, the UE needs to ensure that this is not an instantaneous change as there is no time to trigger the associated configuration when monitoring the leave criteria for the event. The neighbor cell measurement results may indicate deterioration only during one measurement opportunity and the entry criteria may be met again in the next measurement opportunity, resulting in frequent fluctuating measurements at the UE. Stopping T312 during the first opportunity to meet the leave criteria will result in the UE starting T312 at a later point in time when the entry criteria are met again. This results in a delay in declaring RLF when the UE is in a state where a neighbor cell is available and the serving cell has not improved. This may also violate the goal of early RLF detection. If the neighbor cell signal conditions actually deteriorate, then continuing the timer will result in a state where the UE declares RLF but does not have any suitable cell to recover from. This also results in reducing the chances of the UE returning to synchronization with the serving cell, which may be more likely because there are no neighbor cells in that area.

[0494] Therefore, stopping T312 or continuing T312 during the event that the UE meets the departure condition of the measurement event that triggered the start of T312 does not seem to be the most appropriate solution, because it depends on the nature of the signal and channel conditions that caused those events. A more reasonable approach is to propose a method that provides a better probability of early RLF detection while reducing the probability of entering the error scenario that the UE will encounter by stopping or continuing T312. Therefore, it is proposed that the UE restarts T312 when the departure condition is first met. In this way, if the change in signal conditions is instantaneous, the UE will not have to restart the timer later and stay in a weak serving cell for a long time. If the change in measurement is actually caused by a change in signal conditions, then this increases the chance of receiving a handover message from the network, thereby providing an opportunity to continue service without interruption. Therefore, it may be beneficial to the UE if timer T312 is restarted when the departure condition for the measurement configuration that started T312 is met. When T310 is running and use-T312 is configured, the UE needs to ensure that no other measurement reports are sent to the network. If other measurement reports are sent to the network while T310 is running, the UE restarts T312 only if this is the last measurement configured for T312 (no other measurement still satisfies the entry conditions of the reported MR). Figure 5b The flow chart shows the sequence of the processes involved.

[0495] In either case where T312 is stopped or restarted when meeting criteria, the network must configure the report on leaving for the measurement reporting configuration that is required to use T312. This is necessary so that the network knows that the previously reported neighbor cells are not strong enough for handover. This way, when the event is met next time, the UE will report the measurement report to the network and the network can initiate the handover using the latest and most correct available measurements.

[0496] In an embodiment, a method is introduced to indicate support for T312 in MRDC and IRAT. The network node should know whether the UE supports T312-based operations only on MCG or only on SCG or both. The network node also needs to know whether the UE supports T312 operations for IRAT measurement reporting.

[0497] In an embodiment, a method for indicating to EUTRAN that the UE supports T312 or T314 or T315 timers for controlling early SCG RLF or SCG failure declarations is introduced for NE-DC. In LTE, T312 has been defined in specifications 3GPP TS 36.306 and 36.331 for handling early RLF declarations or fast switching recovery mechanisms. However, this is a feature of the old version, and reusing the same feature for SCG recovery may cause backward compatibility issues. Therefore, a new timer T314 or T315 must be introduced in LTE to indicate support for early SCG RLF declarations and fast SCG switching recovery. Otherwise, T312 may be commonly used to control early RLF declarations on both MCG and SCG. In this case, a new UE capability for indicating support for T312 on SCG needs to be sent to the network so that the network knows that the UE also supports T312 operation on SCG. The following example using T314 is for illustration only, and the timer name may be different (e.g., T312 or T315). As shown below, the UE capability is indicated to the network. The capability may also be indicated using a suffix / extension of the T312 capability (eg, T312-SCG).

[0498] In 3GPP TS 36.306:

[0499] 4.3.6.x timerT314-r16

[0500] As specified in TS 36.331 [5], this field defines whether the UE supports T314

[0501] In 3GPP TS 36.331:

[0502]

[0503] In an embodiment, a method for indicating to NR that UE supports T312 timer for controlling early RLF in NR SA and NR-DC scenarios. In an embodiment, a method for indicating to NR that UE supports T312 timer for controlling early SCG RLF or SCG failure declaration is introduced for (NG) EN-DC. There are two ways to indicate this capability to the network. One method is to indicate to the network as a normal IE indicating that T312 operation is supported on MCG and SCG. Another way to indicate to the network is as an independent support indication (separate IE) of T312 support for MCG and SCG. The two methods are as follows:

[0504]

[0505]

[0506]

[0507] or

[0508]

[0509]

[0510]

[0511]

[0512]

[0513] or

[0514]

[0515] In another embodiment, on NR, when IRAT EUTRAN based measurement reporting is triggered, the network needs to be informed about the UE's support for T312 based early RLF declaration.

[0516] Similarly, in LTE, when IRATNR based measurement reporting is triggered, the indication of UE capability for early RLF declaration based on IRAT T312 from NR to EUTRAN needs to inform the network about the UE's support for early RLF declaration based on T312 on LTE. This is shown below:

[0517] On NR (3GPP TS 38.331), T312 supports early RLF declaration when EUTRAN measurement reporting is triggered.

[0518]

[0519] or

[0520]

[0521] On LTE (3GPP TS 36.331), T312 supports early RLF declaration when EUTRAN measurement reporting is triggered.

[0522] 4.3.6.x timerT312-r16: As specified in TS 36.331 [5], this field defines whether the UE supports T312-based RLF when an NR measurement report is triggered.

[0523] Figure 6 The present invention is a schematic diagram of a UE (100) for handling RLF in a wireless communication system according to an embodiment disclosed herein. The UE (100) may be, for example, but not limited to, an unmanned aerial vehicle (UAV), an airplane, a cellular phone, a tablet, a smart phone, a laptop, a personal digital assistant (PDA), a global positioning system, a multimedia device, a video device, an Internet of Things (IoT) device, a smart watch, a game console, etc. Those skilled in the art may also refer to the UE (100) as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a mobile phone, a user agent, a mobile client, etc. The UE (100) includes a processor (110) having an SCG failure processing engine (110a), a communicator (120), a memory (130), a first timer (140), and a second timer (150). The processor (110) is coupled with the communicator (120), the memory (130), the first timer (140), and the second timer (150).

[0524] The SCG failure processing engine (110a) receives a measurement configuration including a second timer (150) from the SN (300). In addition, the SCG failure processing engine (110a) configures the second timer (150) associated with the measurement report for the PScell ​​for the UE (100). In addition, when the measurement report is triggered while the first timer (140) for the PSCell is running, the SCG failure processing engine (110a) starts the second timer (150). In addition, the SCG failure processing engine (110a) detects the expiration of one of the first timer (140) and the second timer (150) for the PSCell. In addition, upon expiration of the earlier of the first timer (140) and the second timer (150), the SCG failure processing engine (110a) declares an SCG RLF. In addition, when declaring the SCG RLF, the SCG failure processing engine (110a) initiates an SCG failure procedure to the MN (200).

[0525] In an embodiment, the processor (110) is configured to notify the master node (200) of an SCG failure message via a master cell group (MCG) link through SRB1 when declaring the SCG RLF. The SCG failure information includes a cause value corresponding to a failure type that is one of the expiration of the first timer (140) and the expiration of the second timer (150).

[0526] In an embodiment, the processor (110) is configured to set the failure type to one of expiration of a first timer and expiration of a second timer.

[0527] In an embodiment, if the expiration of the first timer (140) is before the expiration of the second timer (150), the processor (110) sets the failure type to the expiration of the first timer, otherwise, if the expiration of the second timer (150) is before the expiration of the first timer (140), the processor (110) sets the failure type to the expiration of the second timer.

[0528] In an embodiment, the processor (110) is configured to receive a measurement object and a report configuration including a second timer (150) from the SN (300). The second timer (150) is associated with a measurement report for a PSCell of the SN (300).

[0529] In an embodiment, SCG RLF is declared by stopping the first timer (140) based on detection of expiration of the second timer (150) for the PSCell. In an embodiment, SCG RLF is declared by stopping the second timer (150) based on detection of expiration of the first timer (150) for the PSCell.

[0530] In an embodiment, the first timer (140) is a T310 timer, wherein the first timer (140) is included during SCG addition, and the second timer (150) is a T312 timer, wherein the second timer (150) is included in the measurement configuration from the SN (300).

[0531] In an embodiment, the measurement report is sent to the SN (300) through one of SRB1 and SRB3.

[0532] The processor (110) is configured to execute instructions stored in the memory (130) and perform various processes. The communicator (120) is configured to communicate internally between internal hardware components and to communicate with external devices via one or more networks and / or MN (200) and MN (300).

[0533] The memory (130) stores instructions to be executed by the processor (110). The memory (130) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or various forms of electrically programmable memory (EPROM) or electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (130) may be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or propagating signal. However, the term "non-transitory" should not be interpreted as the memory (130) being non-removable. In some examples, the memory (130) may be configured to store a larger amount of information than the memory. In a specific example, the non-transitory storage medium may store data that changes over time (e.g., in a random access memory (RAM) or a cache).

[0534] although Figure 6 Various hardware components of the UE (100) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the UE (100) may include fewer or greater numbers of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present invention. One or more components may be combined to perform the same or substantially similar functions to handle RLF in a wireless communication system.

[0535] Figure 7 is a flow chart (S700) illustrating a method for handling RLF in a wireless communication system according to an embodiment disclosed herein. Operations (S702-S708) are performed by a processor (110).

[0536] At S702, the method includes receiving a measurement configuration including a second timer (150) from the SN (300). At S704, the method includes configuring a second timer (150) associated with a measurement report for the PSCell for the UE (100). At S706, the method includes starting the second timer (150) when a measurement report is triggered while a first timer (140) for the PSCell is running. At S708, the method includes detecting expiration of one of the first timer (140) and the second timer (150) for the PSCell. At S710, the method includes declaring an SCG RLF upon expiration of an earlier of the first timer (140) and the second timer (150). At S712, the method includes initiating an SCG failure procedure to the MN (200) when the SCG RLF is declared.

[0537] The embodiments disclosed herein may be implemented using at least one software program that runs on at least one hardware device and performs network management functions to control the elements.

[0538] The various actions, behaviors, blocks, steps, etc. in the flow chart (S700) can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, behaviors, blocks, steps, etc. can be omitted, added, modified, skipped, etc., without departing from the scope of the present invention.

[0539] Figure 8 is a diagram illustrating a base station 800 according to another embodiment of the present disclosure.

[0540] refer to Figure 8 , the base station 800 may include a processor 810, a transceiver 820, and a memory 830. However, not all components shown in the figure are required. The base station 800 may include: Figure 8 Furthermore, according to another embodiment, the processor 810, the transceiver 820, and the memory 830 may be implemented as a single chip.

[0541] The aforementioned components will now be described in detail.

[0542] The processor 810 may include one or more processors or other processing devices to control the proposed functions, processes and / or methods. The operations of the base station 800 may be implemented by the processor 810.

[0543] The processor 810 may obtain at least one timer information including a timer 312 for RLF on a secondary cell group (SCG). The processor 810 may control the transceiver to send control information including the obtained timer information. The processor 810 may control the transceiver to receive SCG failure information indicating expiration of the timer 312 as a cause of the RLF on the SCG based on the expiration of the timer 312 at the user equipment (UE).

[0544] The transceiver 820 may include an RF transmitter for up-converting and amplifying transmitted signals, and an RF receiver for down-converting the frequency of received signals. However, according to another embodiment, the transceiver 820 may be implemented by more or fewer components than those shown in the components.

[0545] The transceiver 820 may be connected to the processor 810 and transmit and / or receive signals. The signals may include control information and data. In addition, the transceiver 820 may receive signals through a wireless channel and output the signals to the processor 810. The transceiver 820 may transmit signals output from the processor 810 through a wireless channel.

[0546] The memory 830 may store control information or data included in the signal obtained by the base station 800. The memory 830 may be connected to the processor 810 and store at least one instruction or protocol or parameter for the proposed function, process and / or method. The memory 830 may include a read-only memory (ROM) and / or a random access memory (RAM) and / or a hard disk and / or a CD-ROM and / or a DVD and / or other storage devices.

[0547] The foregoing description of specific embodiments will fully reveal the general nature of the embodiments herein so that others can easily modify and / or adapt various applications of such specific embodiments by applying current knowledge without departing from the general concepts, and therefore, such adaptations and modifications should and are intended to be understood as falling within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the words or terms used herein are for descriptive purposes and not for limitation. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be implemented by modification within the spirit and scope of the embodiments described herein.

Claims

1. A method for processing a radio link failure RLF by a user equipment UE in a wireless communication system including a primary cell group MCG and a secondary cell group SCG, include: receiving a radio resource control (RRC) reconfiguration message including measurement configuration information associated with the SCG; When a first timer on a primary SCG cell PSCell is running, starting a second timer on the PSCell based on the measurement configuration information associated with the SCG; Based on expiration of the second timer on the PSCell, declaring a RLF of the SCG; as well as An SCG failure message is sent to the master node MN via signaling radio bearer 1 SRB 1, the SCG failure message including a cause value corresponding to the failure type being expiration of the second timer.

2. The method according to claim 1 also includes initiating a connection reestablishment procedure by the UE when the RLF of the SCG is considered and MCG transmission is suspended.

3. The method according to claim 1, wherein the RRC reconfiguration message is received via SRB 3 or via the SRB1.

4. The method according to claim 1, wherein The first timer is a T310 timer, and the second timer is a T312 timer.

5. A method for processing a radio link failure RLF by a base station in a wireless communication system including a primary cell group MCG and a secondary cell group SCG, include: Receiving an SCG failure message from a user equipment UE via signaling radio bearer 1 SRB 1; as well as identifying, from the SCG failure message, a cause value corresponding to a failure type of expiration of a second timer, wherein, based on the expiration of the second timer on the primary SCG cell PSCell, the RLF of the SCG is declared at the UE, and In a case where the first timer on the PSCell is running, the second timer is started based on measurement configuration information associated with the SCG included in a radio resource control RRC reconfiguration message. 6 . The method according to claim 5 , wherein the RRC reconfiguration message is sent to the UE via SRB 3 or via the SRB 1.

7. The method according to claim 5, in, The first timer is a T310 timer, and the second timer is a T312 timer.

8. A user equipment UE for processing a radio link failure RLF in a wireless communication system including a primary cell group MCG and a secondary cell group SCG, the UE include: Transceiver; as well as a processor coupled to the transceiver, and the processor is configured to: receiving a radio resource control (RRC) reconfiguration message including measurement configuration information associated with the SCG, In the case where the first timer on the primary SCG cell PSCell is running, starting a second timer on the PSCell based on the measurement configuration information associated with the SCG, Based on expiration of the second timer on the PSCell, declaring RLF of the SCG, and An SCG failure message is sent to the master node MN via signaling radio bearer 1 SRB 1, the SCG failure message including a cause value corresponding to the failure type being expiration of the second timer.

9. The UE of claim 8, further comprising initiating a connection reestablishment procedure if the RLF of the SCG is considered and MCG transmission is suspended.

10. The UE according to claim 8, wherein the RRC reconfiguration message is received via SRB 3 or via the SRB 1.

11. The UE according to claim 8, wherein The first timer is a T310 timer, and The second timer is a T312 timer.

12. A base station for processing a radio link failure RLF in a wireless communication system including a primary cell group MCG and a secondary cell group SCG, the base station include: Transceiver; as well as a processor coupled to the transceiver, and the processor is configured to: receiving a SCG failure message from a user equipment UE via signaling radio bearer 1 SRB 1, and identifying, from the SCG failure message, a cause value corresponding to a failure type of expiration of a second timer, wherein, based on the expiration of the second timer on the primary SCG cell PSCell, the RLF of the SCG is declared at the UE, and In a case where the first timer on the PSCell is running, the second timer is started based on measurement configuration information associated with the SCG included in a radio resource control RRC reconfiguration message.

13. The base station of claim 12, wherein a connection reestablishment procedure is initiated in a case where the RLF of the SCG is considered and MCG transmission is suspended.

14. The base station according to claim 12, wherein the RRC reconfiguration message is sent to the UE via SRB 3 or via the SRB 1.

15. The base station according to claim 12, in, The first timer is a T310 timer, and the second timer is a T312 timer.