MÉTODO E DISPOSITIVO PARA OTIMIZAÇÃO DE ROBUSTEZ DA MOBILIDADE PARA RECUO DE VOZ EM SISTEMA DE COMUNICAÇÃO MÓVEL DE PRÓXIMA GERAÇÃO

By incorporating the ID of the reconnecting cell and time since RLF in RLF reports, the method addresses the lack of detailed information in existing systems, improving network optimization and mobility robustness in next-generation mobile communication systems.

BR112025024565A2Pending Publication Date: 2026-11-10SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
BR112025024565
Authority / Receiving Office
BR · BR
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-10
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In cases of voice recoil in next-generation mobile communication systems, the lack of detailed information in RLF reports hinders network optimization by operators managing base stations.

Method used

A method and device that enhance RLF reports by including the ID of the reconnecting cell and the time elapsed since the RLF, allowing terminals to store and transmit this information to the NR base station, facilitating improved network management.

Benefits of technology

Enables effective network operation by providing operators with crucial information for optimizing mobility robustness and enhancing network performance in the face of voice recoil events.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

The present invention relates to a method and device for mobility robustness optimization for voice fallback in a next generation mobile communication system, and specifically, to an operation and device in which a terminal, when making an RLF report, includes the ID of a cell to which the terminal reconnects and information about the time elapsed since the RLF.
Need to check novelty before this filing date? Find Prior Art

Description

1 / 86 METHOD AND DEVICE FOR OPTIMIZING MOBILITY ROBUSTNESS FOR VOICE RECOIL IN NEXT-GENERATION MOBILE COMMUNICATION SYSTEMS Technical Field

[0001] The disclosure refers to a method and device for optimizing mobility robustness for voice recall in a next-generation mobile communication system and, in particular, to an operation and device for including the ID of a cell to which a terminal reconnects and information associated with the time elapsed since an RLF, when generating an RLF report. Previous Technique

[0002] 5G mobile communication technologies define broad frequency bands that enable high transmission rates and new services, and can be implemented not only in bands below 6 GHz, such as 3.5 GHz, but also in bands above 6 GHz, known as millimeter waves, including 28 GHz and 39 GHz. Furthermore, the implementation of 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (e.g., 95 GHz to 3 THz bands) has been considered to achieve transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies, one-tenth of those of 5G mobile communication technologies.

[0003] In the early stages of the development of 5G mobile communication technologies, to support services and meet performance requirements related to Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low Latency Communications (URLLC), and Massive Machine-Like Communications (mMTC), Petition 870250103056, dated 11 / 11 / 2025, page 11 / 116 In 2 / 86 there was continuous standardization regarding beamforming and massive MIMO to mitigate radio wave path loss and increase transmission distances in millimeter waves, support for numerologies (e.g., operation with multiple subcarrier spacings) for efficient utilization of millimeter wave resources and dynamic operation of slot formats, initial access technologies to support multi-beam and broadband transmission, definition and operation of BWP (Bandwidth Part), new channel coding methods such as LDPC (Low Density Parity Check) code for transmitting large amounts of data and polar code for highly reliable transmission of control information, layer 2 preprocessing and network slicing to provide a dedicated network specialized for a specific service.

[0004] Currently, discussions are underway regarding the enhancement and improvement of the performance of initial 5G mobile communication technologies, considering the services that will be supported by 5G mobile communication technologies, and there has been standardization of the physical layer in relation to technologies such as V2X (Vehicle-to-Everything), which assists in determining the direction of autonomous vehicles based on information about the positions and states of the vehicles transmitted by them, aiming to increase user convenience; NR-U (New Unlicensed Radio), which aims to operate the system in compliance with various regulatory requirements in unlicensed bands; NR-U Power Saving; Non-Terrestrial Network (NTN), which is Petition 870250103056, dated 11 / 11 / 2025, page 12 / 116 3 / 86 direct communication between the user's device and the satellite to provide coverage in areas where communication with terrestrial networks is not available; and positioning.

[0005] Furthermore, there has been ongoing standardization in air interface architecture / protocol in relation to technologies such as the Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other sectors, IAB (Integrated Access and Backhaul) to provide a node for expanding the network service area, supporting a wireless backhaul link and an access link in an integrated manner, enhanced mobility, including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access to simplify random access procedures (2-step RACH for NR).There has also been ongoing standardization in system architecture / services toward a basic 5G architecture (e.g., service-based architecture or service-based interface) to combine Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) to receive services based on UE positions.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices, which has been increasing exponentially, will be increasingly connected to communication networks; consequently, it is expected that enhanced functionalities and performance will be needed in 5G mobile communication systems and integrated device operations. Petition 870250103056, dated 11 / 11 / 2025, page 13 / 116 4 / 86 connected. To achieve this goal, new research is planned in connection with Extended Reality (XR) to efficiently support AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and similar technologies, improve performance and reduce the complexity of 5G through the use of Artificial Intelligence (AI) and Machine Learning (ML), support AI services, support metaverse services and communication with drones.

[0007] Furthermore, the development of 5G mobile communication systems will serve as a basis for the development not only of new waveforms to provide coverage in the terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full-Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, lenses and metamaterial-based antennas to improve signal coverage in the terahertz band, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum) and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology to increase the frequency efficiency of 6G mobile communication technologies and enhance system networks, AI-based communication technology to implement system optimization using satellites and AI (Artificial Intelligence) from the design phase and internalizing end-to-end AI support functions,and next-generation distributed computing technology to implement services at levels of complexity that exceed the UE's operational capacity, utilizing resources from, Petition 870250103056, dated 11 / 11 / 2025, page 14 / 116 5 / 86 ultra-high-performance communication and computing. Disclosure Technical problem

[0008] In a case where a voice recoil occurs, as detailed information about it is not included in the RLF report information, an operator managing base stations may have difficulty optimizing the network, and therefore, this disclosure aims to solve the problem. Technical Solution

[0009] A method of operating a terminal in a wireless communication system, according to an embodiment, may include an operation of receiving, from an NR base station, an NR transfer command message containing information about the target radio access technology (RAT) configuration for LTE; an operation of selecting a suitable LTE cell when a suitable LTE cell is available and selecting an acceptable LTE cell when a suitable LTE cell is not available, in case an NR transfer failure is detected; an operation of entering idle RRC mode; an operation of executing an RRC connection establishment procedure with respect to the selected LTE cell;A storage operation for a time value from the transfer failure to reconnection and an ID of the LTE cell to which the RRC connection is made in the VarRLF-Report associated with the NR, when the LTE cell to which the RRC connection is made is a suitable LTE cell; and a storage operation for a time value from the transfer failure to reconnection in the; Petition 870250103056, dated 11 / 11 / 2025, page 15 / 116 6 / 86 VarRLF-Report associated with NR, when the LTE cell to which the RRC connection is made is an acceptable LTE cell.

[0010] When the LTE cell to which the RRC connection is made is an acceptable LTE cell, the ID of the LTE cell to which the RRC connection is made may not be stored in the VarRLF-Report associated with the NR.

[0011] The NR transfer command message may include a pointer to an alternate voice feature.

[0012] The terminal method may also include a storage operation, in the VarRLF-Report associated with the NR, of information indicating that the transfer is for a voice recoil.

[0013] The operation of storing the time value from transfer failure to reconnection, or the ID of the LTE cell to which the RRC connection is made in the VarRLF-Report associated with the NR, can be performed when the ID of an LTE cell is not stored in the VarRLF-Report associated with the NR.

[0014] The terminal can be a terminal that supports an inter-RAT RLF report.

[0015] The terminal method may also include an operation to establish an RRC connection with the NR base station after updating the VarRLF-Report associated with the NR in relation to the selected LTE cell, an operation to receive a terminal information request message from the NR base station, and an operation to transmit, to the NR base station, a terminal information response message, including the VarRLF-Report associated with the NR. Petition 870250103056, dated 11 / 11 / 2025, page 16 / 116 7 / 86

[0016] A terminal in a wireless communication system, according to another embodiment of the present description, may include a transceiver and a controller, and the controller may be configured to receive, from an NR base station, an NR transfer command message including information about the target radio access technology (RAT) configuration for LTE; select a suitable LTE cell when a suitable LTE cell is available; and select an acceptable LTE cell when no suitable LTE cell is available, in case an NR transfer failure is detected; enter an idle RRC mode; perform an RRC connection establishment procedure with respect to the selected LTE cell; store a time value from the transfer failure to reconnection and an ID of the LTE cell with which the RRC connection was made in the VarRLF-Report associated with the NR, when the LTE cell with which the RRC connection was made is a suitable LTE cell;and store a time value from the transfer failure until reconnection in the VarRLF-Report associated with the NR, when the LTE cell with which the RRC connection was made is an acceptable LTE cell. Advantageous effect

[0017] According to various disclosure methods, in relation to a voice recall, a terminal includes the ID of a cell to which the terminal reconnects and information associated with the time elapsed since an RLF when making an RLF report, so that an operator managing base stations can effectively operate a network based on the information. Petition 870250103056, dated 11 / 11 / 2025, p. 17 / 116 8 / 86 Description of the Drawings

[0018] FIG. 1 illustrates a structure of an LTE system according to an embodiment of the present disclosure; FIG. 2 illustrates a radio protocol structure of an LTE system according to a dissemination mode; FIG. 3 illustrates a structure of a next-generation mobile communication system, according to an embodiment of the present disclosure; FIG. 4 illustrates a radio protocol structure of a next-generation mobile communication system according to a dissemination mode; FIG. 5 is a flowchart of a process for updating radio link failure or transfer failure information in an RRC connection establishment procedure, after an RRC connection restoration procedure performed by a terminal fails in a next-generation mobile communication system, according to a disclosure embodiment; FIG. 6 is a flowchart of a process for updating radio link failure or transfer failure information in an RRC connection establishment procedure, after an RRC connection restoration procedure performed by a terminal fails in a next-generation mobile communication system, according to a disclosure embodiment; FIG. 7 is a flowchart of a process for updating radio link failure or transfer failure information in an RRC connection establishment procedure, following an RRC connection restoration procedure performed by a Petition 870250103056, dated 11 / 11 / 2025, page 18 / 116 9 / 86 terminal fails in a next-generation mobile communication system, according to a disclosure embodiment; FIG. 8 is a flowchart of a process for updating radio link failure or transfer failure information in an RRC connection establishment procedure, after an RRC connection restoration procedure performed by a terminal fails in a next-generation mobile communication system, according to a disclosure embodiment; FIG. 9 is a flowchart of a process in which a terminal transfers radio link fault information or transfer fault information to a base station in a next-generation mobile communication system, according to a disclosure embodiment; FIG. 10 is a flowchart of a process in which a terminal transfers radio link fault information or transfer fault information to a base station in a next-generation mobile communication system, according to a disclosure embodiment; FIG. 11 is a flowchart of a process for updating radio link failure or transfer failure information in an RRC connection establishment procedure, after an RRC connection restoration procedure performed by a terminal fails in a next-generation mobile communication system, according to a disclosure embodiment; FIG. 12 is a flowchart of a process for updating radio link failure or transfer failure information in an RRC connection establishment procedure, after a Petition 870250103056, dated 11 / 11 / 2025, page 19 / 116 10 / 86 RRC connection restoration procedure performed by a failed terminal in a next-generation mobile communication system, according to a disclosure embodiment; FIG. 13 is a block diagram of the internal structure of a terminal according to one disclosure modality; and FIG. 14 is a block diagram illustrating the configuration of an NR base station according to a dissemination modality. Method for Invention

[0019] The operating principle of the disclosure will be described in detail below, along with the attached drawings. In describing the disclosure below, a detailed description of the known functions or configurations incorporated in this document will be omitted where it is determined that such a description might unnecessarily obscure the subject matter of the disclosure. The terms that will be described below are defined taking into account the functions described in the disclosure, and may vary according to users, user intentions, or customizations. Therefore, the definitions of the terms should be based on the content of the entire specification.

[0020] In describing the disclosure below, a detailed description of the known functions or configurations incorporated herein will be omitted where it is determined that such description might render the subject matter of the disclosure unnecessarily obscure. The embodiments of the disclosure will be described herein with reference to the accompanying drawings.

[0021] In the following description, terms to identify nodes of Petition 870250103056, dated 11 / 11 / 2025, p. 20 / 116 11 / 86 access, terms relating to network entities, terms relating to messages, terms relating to interfaces between network entities, terms relating to various identifying information and the like are used illustratively for descriptive convenience. Therefore, the disclosure is not limited to the terms described below, and other terms relating to subjects with equivalent technical meanings may also be used.

[0022] In the following description, the terms and names defined in the standards of the Third Generation Partnership for Long-Term Evolution (3GPP LTE) project will be used for descriptive convenience. However, the disclosure is not limited to these terms and names and may be applied in the same way to systems that conform to other standards. In the disclosure, the term eNB may be used interchangeably with the term “gNB” for descriptive convenience. That is, a base station described as “eNB” may refer to “gNB.”

[0023] FIG. 1 illustrates a structure of an LTE system according to an embodiment of the present disclosure.

[0024] With reference to FIG. 1, as illustrated therein, a radio access network of an LTE system includes next-generation base stations (evolved B nodes, hereinafter ENBs, B nodes or base stations) 1-05, 1-10, 1-15 and 1-20, a mobility management entity (MME) 1-25 and a service gateway (S-GW) 1-30. A user device (hereinafter UE or terminal) 1-35 accesses an external network through ENBs 1-05 to 1-20 and S-GW 1-30. Petition 870250103056, dated 11 / 11 / 2025, page 21 / 116 12 / 86

[0025] In FIG. 1, ENBs 1-05 to 1-20 each correspond to a conventional B node in a UMTS system. The ENBs are connected to UE 1-35 via a radio channel and perform more complex functions than conventional B nodes. In the LTE system, since all user traffic, including real-time services such as Voice over IP (VoIP) via Internet Protocol, is served through a shared channel, a device is needed to collect state information, such as temporary storage states, available transmission power states, and channel states of the UEs, and perform scheduling accordingly, with ENBs 1-05 to 1-20 responsible for this function. In general, one ENB controls multiple cells. For example, to implement a transfer rate of 100 Mbps, the LTE system uses orthogonal frequency division multiplexing (hereinafter referred to as OFDM) as the radio access technology in a bandwidth of, for example, 20 MHz.Furthermore, the next-generation mobile communication system employs an adaptive modulation and coding scheme (hereinafter referred to as AMC) to determine a modulation scheme and channel coding rate according to a UE's channel state. The S-GW 1-30 is a device that provides a data carrier and generates or removes a data carrier under the control of the MME 1-25. The MME is a device responsible for various control functions, as well as a mobility management function for a UE, and is connected to multiple base stations.

[0026] FIG. 2 illustrates a radio protocol structure of Petition 870250103056, dated 11 / 11 / 2025, page 22 / 116 13 / 86 an LTE system according to a disclosure modality.

[0027] With reference to FIG. 2, a radio protocol of an LTE system includes a Packet Data Convergence Protocol (PDCP) 2-05 or 2-40, a Radio Link Control (RLC) 2-10 or 2-35, and a Medium Access Control (MAC) 2-15 or 2-30 on each side of the UE and ENB. The Packet Data Convergence Protocol (PDCP) 2-05 or 2-40 is responsible for operations such as IP header compression / reconstruction. The main functions of PDCP are summarized below: Header compression and decompression: ROHC only; User data transfer; Sequential delivery of upper-layer PDUs in the PDCP restoration procedure for RLC AM; For carriers split into DC (support for RLC AM only): Routing of PDCP PDUs for transmission and reordering of PDCP PDUs for reception; Duplicate detection of lower-layer SDUs in the PDCP restoration procedure for RLC AM; Retransmission of PDCP SDUs during transfer and, for DC-split carriers, of PDCP PDUs during the PDCP data recovery procedure, for RLC AM; Encryption and decryption; Timer-based SDU discard on uplink.

[0028] The 2-10 or 2-35 radio link control (hereinafter referred to as RLC) reconfigures a PDCP protocol data unit (PDU) to a size appropriate for performing an ARQ operation, etc. The main functions of the RLC are summarized as follows: Petition 870250103056, dated 11 / 11 / 2025, page 23 / 116 14 / 86 follow: Transfer of upper-layer PDUs; Error correction via ARQ (for AM data transfer only); Concatenation, segmentation and reassembly of RLC SDUs (for UM and AM data transfer only); Resegmentation of RLC data PDUs (for AM data transfer only); Reordering of RLC data PDUs (for UM and AM data transfer only); Duplicate detection (for UM and AM data transfer only); Protocol error detection (for AM data transfer only); Discard RLC SDU (for UM and AM data transfer only); RLC restoration.

[0029] The MAC 2-15 or 2-30 is connected to multiple RLC layer devices configured on a single terminal, multiplexing RLC PDUs into one MAC PDU and demultiplexing one MAC PDU into RLC PDUs. The main functions of the MAC are summarized below: Mapping between logical channels and transport channels; Multiplexing / demultiplexing of MAC SDUs belonging to one or more logical channels in / from transport blocks (TB) delivered to / from the physical layer in transport channels; Escalation information report; Petition 870250103056, dated 11 / 11 / 2025, page 24 / 116 15 / 86 Error correction via HARQ; Priority treatment between logical channels of an EU; Prioritization of treatment among EUs through dynamic scheduling; MBMS service identification; Selection of transport format; Filling.

[0030] A physical layer 2-20 or 2-25 performs channel encoding and data modulation operations from the upper layer, thus obtaining OFDM symbols and transmitting them through a radio channel, or demodulating OFDM symbols received through the radio channel, decoding them in the channel and transmitting them to the upper layer.

[0031] FIG. 3 illustrates a structure of a next-generation mobile communication system, according to an embodiment of the present disclosure.

[0032] With reference to FIG. 3, as illustrated therein, a radio access network of a next-generation mobile communication system (hereinafter NR or 5G) includes a next-generation base station (new radio node B, hereinafter NR gNB or NR base station) 3-10 and a new radio core network (NR CN) 3-05. A user terminal (new radio user equipment, hereinafter NR UE or NR terminal) 3-15 accesses an external network via NR gNB 3-10 and NR CN 3-05.

[0033] The NR gNB 3-10 can be connected to the NR UE 3-15 via a radio channel and provide exceptional services compared to a conventional B node. In the communication system Petition 870250103056, dated 11 / 11 / 2025, page 25 / 116 In next-generation 16 / 86 mobile, since all user traffic is served through a shared channel, a device is needed to collect state information, such as temporary storage status, available transmission power levels, and UE channel states, and perform scheduling accordingly, and the gNB 3-10 NR serves as that device. Generally, a single gNB NR controls multiple cells. To implement ultra-high-speed data transfer beyond current LTE, the next-generation mobile communication system may have a bandwidth greater than the existing maximum bandwidth, may employ orthogonal frequency-division multiplexing (hereinafter referred to as OFDM) as radio access technology, and may additionally integrate beamforming technology.Furthermore, the next-generation mobile communication system employs an adaptive modulation and coding scheme (hereinafter referred to as AMC) to determine a modulation scheme and channel coding rate according to a UE's channel state. The NR CN 3-05 performs functions such as mobility support, carrier configuration, and QoS configuration. The NR CN 3-05 is a device responsible for various control functions, as well as a mobility management function for a UE (User Equipment), and can be connected to multiple base stations. Additionally, the next-generation mobile communication system can interoperate with the existing LTE system, and the NR CN is connected to an MME 3-25 via a network interface. The MME is connected to an eNB 3-30, which is a base station. Petition 870250103056, dated 11 / 11 / 2025, page 26 / 116 17 / 86 existing.

[0034] FIG. 4 illustrates a radio protocol structure of a next-generation mobile communication system according to a disclosure modality.

[0035] FIG. 4 illustrates the structure of a radio protocol for a next-generation mobile communication system to which disclosure is applicable.

[0036] With reference to FIG. 4, a radio protocol of a next-generation mobile communication system includes an NR SDAP 4-01 or 4-45, an NR PDCP 4-05 or 4-40, an NR RLC 4-10 or 435 and an NR MAC 4-15 or 4-30 on each side of the UE and the NR base station.

[0037] The main functions of the NR SDAP 4-01 or 4-45 may include some of the functions below: Data transfer from the user's plan; Mapping between a QoS stream and a DRB for both DL and UL; Mark the QoS flow ID in both DL and UL packets; Reflective QoS flow mapping for DRB to SDAP UL PDUs.

[0038] With regard to the SDAP layer device, the UE can be configured, via an RRC message, to use the SDAP layer device header or SDAP layer device functions for each PDCP layer device, each carrier or each logical channel, and if an SDAP header is configured, the 1-bit indicator of NAS reflective QoS configuration and the Petition 870250103056, dated 11 / 11 / 2025, page 27 / 116 The 18 / 86 AS stratum reflective QoS configuration indicator in the SDAP header can be specified so that the UE can update or reconfigure the mapping information related to the QoS flow and the uplink and downlink data carrier. The SDAP header may include QoS flow ID information indicating the QoS. QoS information can be used for data processing priority, scheduling information, etc., to ensure the proper functioning of services.

[0039] The main functions of NR PDCP 4-05 or 4-40 may include some of the functions below: Header compression and decompression: ROHC only; User data transfer; Sequential delivery of top-tier PDUs; Out-of-sequence delivery of top-tier PDUs; Reordering of PDCP PDU for reception; Duplicate detection of lower-layer SDUs; PDCP SDU relay; Encryption and decryption; Timer-based SDU discard on uplink.

[0040] NR PDCP device reordering refers to a function of reordering PDCP PDUs received from a lower layer in an order based on PDCP sequence numbers (SNs), and may include a data transfer function to a higher layer according to a reordered order, may include a direct data transfer function without considering the order, may include a function of reordering the order to register Petition 870250103056, dated 11 / 11 / 2025, p. 28 / 116 19 / 86 Lost PDCP PDUs may include a function to report the status of lost PDCP PDUs to a transmission side, or it may include a function to request the retransmission of lost PDCP PDUs.

[0041] The main functions of the NR RLC 4-10 or 4-35 may include some of the functions below: Transfer of upper-layer PDUs; Sequential delivery of top-tier PDUs; Out-of-sequence delivery of top-tier PDUs; Error correction via ARQ; Concatenation, segmentation, and reassembly of RLC SDUs; Re-segmentation of RLC data PDUs; Reordering of RLC data PDUs; Duplicate detection; Protocol error detection; Disposal of RLC SDU; RLC restoration.

[0042] Sequential delivery of the NR RLC device refers to the function of successively delivering RLC SDUs received from the lower layer to the upper layer. It may include a function to reassemble and deliver multiple received RLC SDUs in which an original RLC SDU has been segmented. It may also include the function to reorder received RLC PDUs with reference to the RLC sequence number (SN) or the PDCP sequence number (SN). It may also include the function to register RLC PDUs lost as a result of reordering, and it may also include the function to report the status of lost RLC PDUs to the transmitting side. Petition 870250103056, dated 11 / 11 / 2025, p. 29 / 116 20 / 86 It may also include the function of requesting the retransmission of lost RLC PDUs; it may also include a function that, if a lost RLC SDU exists, successively delivers only the RLC SDUs prior to the lost SDU to the upper layer; it may also include the function that, if a predetermined timer has expired, even if there is a lost RLC SDU, successively delivers all RLC SDUs received before the start of the timer to the upper layer; it may include a function that, if a predetermined timer expires, even if there is a lost RLC SDU, successively delivers all RLC SDUs received up to the present to the upper layer.Furthermore, the NR RLC device can process RLC PDUs in the order they are received (regardless of sequence number order, in the order they arrive) and deliver them to the PDCP device regardless of order (out-of-sequence delivery). In the case of segments, it can receive segments stored in temporary storage or that will be received later, reconfigure them into a complete RLC PDU, process it, and deliver it to the PDCP device. The NR RLC layer may not include any concatenation function, which can be performed in the NR MAC layer or replaced by a multiplexing function of the NR MAC layer.

[0043] The out-of-sequence delivery of the NR RLC device refers to the function of instantly delivering RLC SDUs received from the lower layer to the upper layer, regardless of the order; it may include the function of, if multiple RLC SDUs are received in which an original RLC SDU has been segmented, reassembling and delivering them; and it may also include the Petition 870250103056, dated 11 / 11 / 2025, page 30 / 116 21 / 86 function to store the RLC serial number (SN) or PDCP serial number (SN) of received RLC PDUs and record RLC PDUs lost as a result of reordering.

[0044] The NR MAC 14-15 or 4-30 can be connected to multiple NR RLC layer devices configured in a single UE, and the main functions of the NR MAC may include some of the functions below: Mapping between logical channels and transport channels; Multiplexing / demultiplexing of MAC SDUs; Escalation information report; Error correction via HARQ; Priority treatment between logical channels of an EU; Prioritization of treatment among EUs through dynamic scheduling; MBMS service identification; Selection of transport format; Filling.

[0045] An NR 4-20 or 4-25 physical layer can perform channel encoding and data modulation operations from the upper layer, thus obtaining OFDM symbols and transmitting them through a radio channel, or demodulating OFDM symbols received through the radio channel, decoding them in the channel and transmitting them to the upper layer.

[0046] FIG. 5 is a flowchart of a process for updating radio link fault information or transfer fault information in a connection-establishing procedure (RRC), following a connection-reestablishing procedure. Petition 870250103056, dated 11 / 11 / 2025, page 31 / 116 22 / 86 RRC performed by a UE failure in a next-generation mobile communication system, according to a disclosure modality.

[0047] With reference to FIG. 5, a UE 5-01 can be in an RRC connected mode (RRC_CONNECTED) setting up an RRC connection with an operating NR 5-02 base station 5-05.

[0048] In operation 5-10, UE 5-01 can transmit a UE CapabilityInformation message to base station 5-02. An indicator associated with an acceptable cell can be included in the message, and this can be an indicator associated with cells other than a suitable VarRLF-Report cell. Additionally, the message can include UE CapabilityInformation associated with the ability to store information other than a suitable VarRLF-Report cell.

[0049] In operation 5-15, UE 5-01 may detect a radio link failure (RLF) or a transfer failure may occur (transfer failure or reconfiguration with synchronization failure) due to a predetermined reason. For example, UE may detect an RLF when a T310 timer expires for a currently connected 5-02 primary cell (PCell), or a transfer failure may occur when a T304 timer expires, even though UE receives an RRC message (e.g., RRCReconfiguration or MobilityFromNRCommand) indicating that transfer is required from the currently connected primary cell.

[0050] In operation 5-20, UE 5-01 can store radio link failure information (upon detecting an RLF) or information Petition 870250103056, dated 11 / 11 / 2025, page 32 / 116 23 / 86 Transfer Failure (when a transfer failure occurs) in VarRLF-Report. Specifically, the UE can store radio link failure information or transfer failure information in VarRLF-Report according to the following procedure: The EU should determine the content of the VarRLF-Report as follows: 1> Clear the information included in the VarRLF-Report, if any; 1> Define plmn-IdentityList to include the list of EPLMNs stored by UE (i.e., include RPLMN); 1> Define the measResultLastServCell to include the available cell-level RSRP, RSRQ, and SINR from the originating PCell (in case of an HO fault) or PCell (in case of an RLF fault) based on available SSB and CSI-RS measurements collected up to the time the UE detected the fault; 1> If measurement quantities based on SS / PBCH blocks are available: 2> Define rsIndexResults in measResultLastServCell to include all available measurement quantities from the source PCell (in case of HO failure) or PCell (in case of RLF), ordered so that the highest SS / PBCH block RSRP is listed first if SS / PBCH block RSRP measurement results are available; otherwise, the highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available; otherwise, the highest SS / PBCH block SINR is listed first. Petition 870250103056, dated 11 / 11 / 2025, p. 33 / 116 24 / 86 first, based on available SS / PBCH block-based measurements collected up to the time the UE detected the fault; 1> If measurement quantities based on CSI-RS are available: 2> Define the rsIndexResults in measResultLastServCell to include all available measurement quantities from the source PCell (in case of HO failure) or PCell (in case of RLF), ordered so that the largest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available; otherwise, the largest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available; otherwise, the largest CSI-RS SINR is listed first, based on available CSI-RS-based measurements collected up to the time the UE detected the failure; 1> Define the ssbRLMConfigBitmap and / or csi-rsRLMConfigBitmap in measResultLastServCell to include the radio link monitoring configuration of the source PCell (in case of HO failure) or the PCell (in case of RLF), if available; 1> For each of the configured measureObjectNR objects where measurements are available: 2> If SS / PBCH block-based measurement quantities are available: 3> Define measResultListNR in measResultNeighCells to include all available measurement quantities from the best-measured cells, other than the source PCell (in case of HO failure) or PCell (in case of RLF), ordered so that the cell with the highest SS / PBS block RSRP is listed. Petition 870250103056, dated 11 / 11 / 2025, p. 34 / 116 25 / 86 first if SS / PBCH block RSRP measurement results are available; otherwise, the cell with the highest SS / PBCH block RSRQ is listed first if SS / PBCH block RSRQ measurement results are available; otherwise, the cell with the highest SS / PBCH block SINR is listed first, based on available SS / PBCH block-based measurements collected up to the time the UE detected the fault; 4> For each neighboring cell included, include the optional fields that are available; NOTE 0a: For neighboring cells included in measResultListNR in measResultNeighCells, ordered based on SS / PBCH block measurement quantities, the UE also includes CSI-RS-based measurement quantities, if available. 2> If measurement quantities based on CSI-RS are available: 3> Define the measResultListNR in measResultNeighCells to include all available measurement quantities from the best-measured cells, other than the originating PCell (in case of HO failure) or PCell (in case of RLF), ordered so that the cell with the highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available; otherwise, the cell with the highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available; otherwise, the cell with the highest CSI-RS SINR is listed first, based on available CSI-RS-based measurements collected up to the time the UE detected the failure. Petition 870250103056, dated 11 / 11 / 2025, p. 35 / 116 26 / 86 radio link; 4> For each neighboring cell included, include the optional fields that are available; NOTE 0b: To order neighboring cells based on CSI-RS measurement quantities, UE includes measurements only for cells not already included in measResultListNR in measResultNeighCells to avoid overwriting measurements ordered based on SS / PBCH blocks. 2> For each neighboring cell, if any, included in measResultListNR in measResultNeighCells: 3> If the UE supports RLF-Report for conditional transfer and if the neighboring cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditionalReconfig at the time the failure is detected: 4> Define choConfig in MeasResult2NR for the execution condition for each measId within condTriggerConfig associated with the neighboring cell within MCG VarConditionalReconfig; 4> if the first entry of choConfig matches a satisfied execution condition at the time of the transfer failure or radio link failure; or 4> If the second entry of choConfig, if available, matches a satisfied execution condition at the time of the transfer failure or radio link failure: 5> Set firstTriggeredEvent to the condFirstEvent trigger condition corresponding to the first entry in choConfig, or to the condSecondEvent trigger condition. Petition 870250103056, dated 11 / 11 / 2025, p. 36 / 116 27 / 86 corresponds to the second entry of choConfig, regardless of which execution condition was met first in time; 5> Define timeBetweenEvents as the elapsed time between when the condition in choConfig that was met first was met, and when the condition in choConfig that was met second was met, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in choConfig were met; 1> For each of the configured EUTRA frequencies at which measurements are available: 2> Define the measResultListEUTRA in measResultNeighCells to include the cells with the best measurements, ordered so that the cell with the highest RSRP is listed first, if RSRP measurement results are available; otherwise, the cell with the highest RSRQ is listed first, based on measurements collected up to the time the UE detected the fault; 3> For each neighboring cell included, include the optional fields that are available; NOTE 1: Measured quantities are filtered by the L3 filter, as configured in the mobility measurement configuration. Measurements are based on the time-domain measurement feature constraint, if configured. Cells listed as excluded do not need to be reported. 1> Set the c-RNTI to the C-RNTI used in the source PCell (in case of HO failure) or PCell (in case of RLF); Petition 870250103056, dated 11 / 11 / 2025, p. 37 / 116 28 / 86 1> If the failure is detected due to a failed synchronization reconfiguration, as described in 5.3.5.8.3, set the fields in VarRLF-Report as follows: 2> Define connectionFailureType as hof; 2> If the UE supports RLF-Report for DAPS transfer and if any DAPS carrier was configured while T304 was running: 3> set lastHO-Type to daps; 3> If a radio link fault is detected in the originating PCell, in accordance with clause 5.3.10.3: 4> Set timeConnSourceDAPS-Failure to the time between the start of the DAPS transfer execution and the radio link failure detected on the source PCell while T304 was running; 4> Define the rlf-Cause for activation for detection of source radio link failure according to clause 5.3.10.4; 2> If the UE supports RLF-Report for conditional transfer and if the conditional transfer setting is available in MCG VarConditionalReconfig at the time the transfer fails: 3> If the UE executed a conditional transfer towards the target PCell according to the target PCell's condRRCReconfig: 4> Set timeSinceCHO-Reconfig to the elapsed time between the execution of the last RRCReconfiguration message including reconfigurationWithSync for the target PCell. Petition 870250103056, dated 11 / 11 / 2025, p. 38 / 116 29 / 86 conditional transfer failed, and the receipt on the originating PCell of the last conditionalReconfiguration including the condRRCReconfig from the PCell target of the failed conditional transfer; 3> Otherwise: 4> Define timeSinceCHO-Reconfig as the elapsed time between the execution of the last RRCReconfiguration message including reconfigurationWithSync to the target PCell of the failed transfer, and the receipt on the source PCell of the last conditionalReconfiguration including condRRCReconfig; 3> Define choCandidateCellList to include the global cell identity, if available, and otherwise the physical cell identity and carrier frequency of each of the target candidate cells for conditional transfer included in condRRCReconfig within MCG VarConditionalReconfig at the time of the failed transfer, excluding the target candidate cells included in measResultNeighCells; 2> If the UE supports RLF-Report for conditional transfer and if the last RRCReconfiguration message executed, including reconfigurationWithSync, refers to a conditional transfer: 3> set lastHO-Type to floor; 2> Set the nrFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell for transfer. Petition 870250103056, dated 11 / 11 / 2025, p. 39 / 116 30 / 86 faulty; 2> Include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message including reconfigurationWithSync was received; 2> Set timeConnFailure to the time elapsed since the execution of the last RRCReconfiguration message, including reconfigurationWithSync; 1> Otherwise, if the fault is detected due to NR fault mobility, as described in 5.4.3.5, set the fields in VarRLF-Report as follows: 2> Define connectionFailureType as hof; 2> If the last MobilityFromNRCommand referred to an inter-RAT transfer failure from NR to EUTRA, and if the UE supports Radio Link Failure Reporting for MRO EUTRA InterRAT (NR to EUTRA): 3> Set the failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell targeted for the failed transfer; 2> Include nrPreviousCell in previousPCellId and set it to the global cell identity and tracking area code of the PCell where the last MobilityFromNRCommand message was received; 2> Set timeConnFailure to the time elapsed since the initialization of the transfer associated with the last message. Petition 870250103056, dated 11 / 11 / 2025, p. 40 / 116 31 / 86 MobilityFromNRCommand; 1> Otherwise, if the fault is detected due to a radio link fault, as described in 5.3.10.3, set the fields in VarRLF-Report as follows: 2> Set connectionFailureType to rlf; 2> Define the rlf-Cause for enabling radio link failure detection according to clause 5.3.10.4; 2> Set the nrFailedPCellId in failedPCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where the radio link failure is detected; 2> If an RRCReconfiguration message including reconfigurationWithSync was received before the connection failure: 3> if the last RRCReconfiguration message executed, including reconfigurationWithSync, referred to an intra-NR transfer and was received while the user was connected to the PCell prior to the one they were connected to before connecting to the PCell where the radio link failure was detected; and 3> If the PCell in which the radio link failure was detected resulted from cell selection and the T311 was not running at the time of PCell selection: 4> Include the nrPreviousCell in previousPCellId and set it as the global cell identity and tracking area code of the PCell where the last RRCReconfiguration message was executed, including Petition 870250103056, dated 11 / 11 / 2025, p. 41 / 116 32 / 86 reconfigurationWithSync, was received; 4> if the last RRCReconfiguration message executed, including reconfigurationWithSync, referred to a DAPS transfer; 5> set lastHO-Type to daps; 4> Otherwise, if the last RRCReconfiguration message executed, including reconfigurationWithSync, referred to a conditional transfer: 5> set lastHO-Type to floor; 4> Set the timeConnFailure to the time elapsed since the execution of the last RRCReconfiguration message, including reconfigurationWithSync; 3> Otherwise, if the last RRCReconfiguration message, including reconfigurationWithSync, referred to a transfer to NR from E-UTRA and if UE supports Radio Link Failure Reporting to MRO EUTRA InterRAT: 4> include eutraPreviousCell in previousPCellId and set it as the global cell identity and tracking area code of the E-UTRA PCell where the last RRCReconfiguration message including reconfigurationWithSync was received embedded in the E-UTRA RRC MobilityFromEUTRACommand message, as specified in clause 5.4.3.3 of TS 36.331

[10] ; 4> Set timeConnFailure to the time elapsed since receiving the last RRCReconfiguration message, including Petition 870250103056, dated 11 / 11 / 2025, p. 42 / 116 33 / 86 a reconfigurationWithSync incorporated in the E-UTRA RRC MobilityFromEUTRACommand message, as specified in clause 5.4.3.3 of TS 36.331

[10] ; 2> If the conditional transfer configuration is available in MCG VarConditionalReconfig at the time the radio link failure is declared: 3> Define timeSinceCHO-Reconfig as the time elapsed between the detection of the radio link failure and the reception, on the originating PCell, of the last conditionalReconfiguration including the condRRCReconfig message; 3> Define choCandidateCellList to include the global cell identity, if available, and otherwise the physical cell identity and carrier frequency of each of all candidate cells for conditional transfer included in condRRCReconfig within MCG VarConditionalReconfig at the time of radio link failure, excluding candidate cells included in measResultNeighCells; 1> if connectionFailureType is rlf and rlf-Cause is set to randomAccessProblem or beamFailureRecoveryFailure; or 1> If connectionFailureType is hof and the failed transfer is an intra-RAT transfer: 2> Define ra-InformationCommon to include the information related to random access, as described in clause 5.7.10.5; 1> If available, set locationInfo as in 5.3.3.7. Petition 870250103056, dated 11 / 11 / 2025, p. 43 / 116 34 / 86

[0051] For reference, the EU may determine the rlf-Cause in accordance with the following procedure: The UE should define the rlf-Cause in VarRLF-Report as follows: 1> If the EU declares a radio link failure due to the expiration of T310: 2> set rlf-Cause to t310-Expiry; 1> Otherwise, if the UE declares a radio link failure due to an indication of a random MAC access problem from the MCG: 2> If the random access procedure was initiated for beam failure recovery: 3> Set rlf-Cause to beamFailureRecoveryFailure; 2> Otherwise: 3> Set the rlf-Cause to randomAccessProblem; 1> Otherwise, if the EU declares a radio link failure due to the MCG RLC reaching its maximum number of retransmissions: 2> Define rlf-Cause as rlc-MaxNumRetx; 1> Otherwise, if the EU declares a radio link failure due to consistent failures in the uplink LBT: 2> set rlf-Cause to lbtFailure; 1> Otherwise, if the IAB-MT declares a radio link failure due to receiving a BH RLF indication on the BAP entity: 2> set rlf-Cause to bh-rlfRecoveryFailure; 1> Otherwise, if the EU declares a radio link failure due to the expiration of T312: Petition 870250103056, dated 11 / 11 / 2025, p. 44 / 116 35 / 86 2> set rlf-Cause to t312-Expiry;

[0052] In operation 5-25, UE 5-01 can initiate an RRC connection restoration procedure. However, UE 5-01 may fail to successfully complete the procedure, failing due to a predetermined reason. For example, UE may operate a T311 timer when the RRC connection restoration procedure is initiated, but if UE fails to select a suitable NR cell before the T311 timer expires, the procedure may fail.

[0053] In operation 5-30, UE 5-01 can transition to an idle RRC mode (RRC_IDLE).

[0054] In operation 5-35, the UE 5-01 can camp in an acceptable NR 5-03 cell.

[0055] In operation 5-40, UE 5-01 can perform an RRC connection establishment procedure to establish an RRC connection with the acceptable NR cell 5-03. That is, UE 501 can transmit an RRC connection establishment request message (RRCSetupRequest) to cell 5-03. In response to this, the cell can transmit an RRC connection establishment message (RRCSetup) to the UE in operation 5-45. In operation 5-46, the UE can transition to a connected RRC mode (RRC_CONNECTED) by applying RRCSetup. The UE can consider or determine the cell as a current PCell. In operation 5-48, the UE, according to the disclosure, can propose performing at least one of the proposed methods (i.e., one of the following methods or a combination of some or all of the methods) according to the following conditions: Petition 870250103056, dated 11 / 11 / 2025, page 45 / 116 36 / 86 - If radio link failure information or transfer failure information is included in the VarRLF-Report and a registered public land mobile network (PLMN) to which the UE registers is included in a plmn-IdentityList stored in the VarRLF-Report (if the UE has radio link failure information or transfer failure information available in the VarRLF-Report and if the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report), or if the UE has radio link failure information or transfer failure information included in the VarRLF-Report and an acceptable cell is an existing PCell. If reconnectCellId is not set in VarRLF-Report after a failure in the RRC connection restoration procedure (if reconnectCellId in VarRLF-Report is not set after the restoration fails). ♦ If the UE supports RLF-Report for conditional transfer and choCellId is set in VarRLF-Report (if the UE supports RLF-Report for conditional transfer and if chocellId in VarRLF-Report is set). • Method 1: The information associated with the elapsed time since a radio link failure or a transfer failure in the failedPCellId stored in VarRLF-Report can be defined in timeUntilReconnection in VarRLF-Report (set timeUntilReconnection in VarRLF-Report to the elapsed time since the radio link failure or transfer failure occurred in the failedPCellId stored in VarRLF-Report). • Method 2: The setting in timeUntilReconnection in VarRLF-Report may not be performed. Because the value is not Petition 870250103056, dated 11 / 11 / 2025, p. 46 / 116 37 / 86 defined, network optimization can be performed by identifying whether the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future. • Method 3: The information associated with the elapsed time since a radio link failure or a transfer failure in a failedPCellId stored in the VarRLF-Report can be set in a new timeUntilReconnection for an acceptable cell in the VarRLF-Report. Through the above, network optimization can be performed by identifying that the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future. ♦ Otherwise, • Method 5: The UE can set an elapsed time since the last radio link failure or transfer failure in timeUntilReconnection in VarRLF-Report (set timeUntilReconnection in VarRLF-Report to the elapsed time since the last radio link failure or transfer failure). • Method 6: The timeUntilReconnection setting in VarRLF-Report may not be performed. If the value is not set, network optimization can be performed by identifying whether the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future. • Method 7: The UE can set an elapsed time since the last radio link failure or transfer failure in a Petition 870250103056, dated 11 / 11 / 2025, p. 47 / 116 38 / 86 new timeUntilReconnection for an acceptable cell in the VarRLF-Report. Through the above, network optimization can be performed by identifying that the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future. ♦The UE can define a global cell identity and a tracking area code of the current PCell as nrReconnectCellId in the VarRLF-Report's reconnectCellId (set nrReconnectCellId in the VarRLF-Report's reconnectCellId for the global cell identity and tracking area code of the PCell). The UE can include, in the VarRLF-Report, an indicator showing that the corresponding cell is an acceptable cell. Alternatively, the UE can not define any information in the VarRLF-Report's reconnectCellId. Through the above, network optimization can be achieved by identifying that the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the UE's VarRLF-Report in the future.

[0056] Regarding the content proposed above, a base station can control which method the UE should apply according to a configuration. The UE can transmit a complete RRC (RRCSetupComplete) connection establishment message to the operating cell 5-50. The UE can transmit the VarRLF-Report to the appropriate cell 5-02 subsequently through a UE information procedure, and an operator managing an appropriate cell can optimize a network based on the corresponding information. For example, based on the timeUntilReconnection information, the operator can identify how long Petition 870250103056, dated 11 / 11 / 2025, page 48 / 116 39 / 86 refers to the time elapsed between a failed RRC connection and the UE, which has radio link failure information or transfer failure information in the VarRLF-Report, re-establishing an RRC connection with a predetermined cell. Thus, if the corresponding time is too long, the operator may operate a network by additionally providing a new cell or optimizing existing cells. Similarly, based on the reconnectCellId, the operator can identify a cell to which the UE subsequently connected, and this information can be used to determine whether it is necessary to provide an additional cell or to properly manage existing cells. Furthermore, if the reconnectCellId for an acceptable cell is set in the VarRLF-Report, the UE may not report the corresponding information for a suitable cell.An acceptable cell does not belong to an operator to which the UE has subscribed, and therefore, if the UE sends reconnectCellId to a subscribed operator, it will be providing network operation information from another operator.

[0057] FIG. 6 is a flowchart of a process for updating radio link failure information or transfer failure information in an RRC connection establishment procedure, after an RRC connection restoration procedure performed by a UE fails in a next-generation mobile communication system, according to a disclosure embodiment.

[0058] With reference to FIG. 6, a UE 6-01 can be in an RRC connected mode (RRC_CONNECTED) setting up an RRC connection with an operating NR 6-02 base station 6-05. Petition 870250103056, dated 11 / 11 / 2025, page 49 / 116 40 / 86

[0059] In operation 6-10, UE 6-01 can transmit a UE CapabilityInformation message to base station 6-02. This may be the same as the mode described above.

[0060] In operation 6-15, UE 6-01 may detect a radio link failure (RLF) or a transfer failure may occur (transfer failure or reconfiguration with synchronization failure) due to a predetermined reason. For example, UE may detect an RLF when a T310 timer expires for a currently connected 6-02 primary cell (PCell), or a transfer failure may occur when a T304 timer expires, even though UE receives an RRC message (e.g., RRCReconfiguration or MobilityFromNRCommand) indicating that transfer is required from the currently connected primary cell.

[0061] In operation 6-20, UE 6-01 can store radio link failure information (when detecting an RLF) or transfer failure information (when a transfer failure occurs) in VarRLF-Report. This may be the same as the mode described above.

[0062] In operation 6-25, UE 6-01 can initiate an RRC connection restoration procedure. However, UE 6-01 may fail to successfully complete the procedure due to a predetermined reason. For example, the UE may operate a T311 timer when the RRC connection restoration procedure is initiated, but if the UE fails to select a suitable NR cell before the timer... Petition 870250103056, dated 11 / 11 / 2025, page 50 / 116 41 / 86 If T312 expires, the procedure may fail.

[0063] In operation 6-30, UE 6-01 can transition to an idle RRC mode (RRC_IDLE).

[0064] In operation 6-35, UE 6-01 can camp in an acceptable LTE cell 6-03.

[0065] In operation 6-40, UE 6-01 can perform an RRC connection establishment procedure to establish an RRC connection with acceptable cell 6-03. That is, UE 6-01 can transmit an RRC connection establishment request message (RRCSetupRequest) to cell 6-03. In response to this, the cell can transmit an RRC connection establishment message (RRCSetup) to the UE in operation 6-45. In operation 6-46, the UE can transition to a connected RRC mode (RRC_CONNECTED) by applying RRCSetup. The UE can consider or determine the cell as a current PCell. In operation 6-48, the UE, according to the disclosure, can propose performing at least one of the proposed methods (i.e., one of the following methods or a combination of some or all of the methods) according to the following conditions: - If the UE supports an RLF report for an EUTRA MRO interRAT as defined in the TS 38.306 standard, the radio link failure information or transfer failure information is included in the VarRLF-Report of the TS 38.331 standard, and a registered public land mobile network (PLMN) to which the UE registers is included in the plmn-IdentityList stored in the VarRLF-Report of the TS 38.331 standard (if the UE supports RLF reporting for EUTRA MRO interRAT as defined in TS 38.306, and if the UE has Petition 870250103056, dated 11 / 11 / 2025, p. 51 / 116 42 / 86 radio link failure information or transfer failure information available in the TS 38.331 VarRLF-Report and if the RPLMN is included in the plmn-IdentityList stored in the TS 38.331 VarRLF-Report), or if the transfer failure information is included in the VarRLF-Report and an acceptable cell is a current PCell. If the reconnectCellId parameter is not set in the VarRLF-Report of the TS 38.331 standard, after a failure in the RRC connection re-establishment procedure (if the reconnectCellId parameter in the VarRLF-Report of TS 38.331 is not set after the connection re-establishment failure). ♦ Method 1: The UE can set an elapsed time since the last radio link failure or transfer failure in timeUntilReconnection in the VarRLF-Report of the TS 38.331 standard (set timeUntilReconnection in the VarRLF-Report of TS 38.331 to the elapsed time since the last radio link failure or transfer failure). ♦ Method 2: The timeUntilReconnection setting in the VarRLF-Report of the TS 38.331 standard cannot be performed. Since the value is not set, network optimization can be performed by identifying whether the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future. ♦ Method 3: The UE can define an elapsed time since the last radio link failure or transfer failure in a new 'timeUntilReconnection' parameter for an acceptable cell in the VarRLF-Report of the TS 38.331 standard. Through the above, Petition 870250103056, dated 11 / 11 / 2025, page 52 / 116 43 / 86 Network optimization can be performed by identifying that the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future. ♦The UE can define a global cell identity and a tracking area code of the current PCell as eutraReconnectCellId in the reconnectCellId of the VarRLF-Report of the TS 38.331 standard (set eutraReconnectCellId in reconnectCellId in the VarRLF-Report of TS 38.331 for the global cell identity and tracking area code of the PCell). The UE can include, in the VarRLF-Report, an indicator showing that the corresponding cell is an acceptable cell. Alternatively, the UE can not define any information in the reconnectCellId of the VarRLF-Report. Through the above, network optimization can be achieved by identifying that the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future.

[0066] Regarding the content proposed above, a base station can control which method the UE should apply according to a configuration. The UE can transmit a connection setup complete (RRCConnectionSetupComplete) message to the operating cell 6-50. The UE can transmit the VarRLF-Report to the appropriate cell 6-02 through a UE information procedure, and an operator managing an appropriate cell can optimize a network based on the corresponding information. For example, based on the timeUntilReconnection information, the operator can identify how much time has elapsed since a reconnection failure. Petition 870250103056, dated 11 / 11 / 2025, page 53 / 116 44 / 86 RRC connection until the UE, which has radio link failure information or transfer failure information in the VarRLF-Report, reconfigures an RRC connection with a predetermined cell. Thus, if the corresponding time is too long, the operator can operate a network by additionally providing a new cell or optimizing existing cells. Similarly, based on the reconnectCellId, the operator can identify a cell to which the UE subsequently connected, and this information can be used to determine whether it is necessary to provide an additional cell or to properly manage existing cells. Furthermore, if the reconnectCellId for an acceptable cell is set in the VarRLF-Report, the UE may not report the corresponding information for a suitable cell.An acceptable cell does not belong to an operator to which the UE has subscribed, and therefore, if the UE sends reconnectCellId to a subscribed operator, it will be providing network operation information from another operator.

[0067] FIG. 7 is a flowchart of a process for updating radio link failure information or transfer failure information in an RRC connection establishment procedure, after an RRC connection restoration procedure performed by a UE fails in a next-generation mobile communication system, according to a disclosure embodiment.

[0068] With reference to FIG. 7, a UE 7-01 can be in an RRC connected mode (RRC_CONNECTED) setting up an RRC connection with an LTE base station 7-02. The LTE base station can be connected to an operating EPC or 5GC 7-05. Petition 870250103056, dated 11 / 11 / 2025, page 54 / 116 45 / 86

[0069] In operation 7-10, UE 7-01 can transmit a UE CapabilityInformation message to base station 7-02. An indicator associated with an acceptable cell can be included in the message, and this can be an indicator associated with cells other than a suitable VarRLF-Report cell. Additionally, the message can include UE CapabilityInformation associated with the ability to store information other than a suitable VarRLF-Report cell.

[0070] In operation 7-15, UE 7-01 can detect a radio link failure (RLF) or a handover failure can occur due to a predetermined reason. For example, UE can detect an RLF when a T310 timer expires for a currently connected primary cell (PCell) 7-02, or a handover failure can occur when a T304 timer expires, even though UE receives an RRC message (e.g., RRCConnectionReconfiguration or MobilityFromEUTRACommand so that targetRAT-Type is set to nr) indicating that handover is required from the currently connected primary cell.

[0071] In operation 7-20, UE 7-01 can store radio link failure information (when detecting an RLF) or transfer failure information (when a transfer failure occurs) in VarRLF-Report. Specifically, UE can store radio link failure information in VarRLF-Report according to the following procedure: 2> Store the following link failure information Petition 870250103056, dated 11 / 11 / 2025, p. 55 / 116 46 / 86 radio in VarRLF-Report (VarRLF-Report-NB in ​​NB-IoT) configuring its fields as follows: 3> Clear the information included in the VarRLF-Report (VarRLF-Report-NB in ​​NB-IoT), if any; 3> Define plmn-IdentityList to include the list of EPLMNs stored by UE (i.e., include RPLMN); 3> Define the measResultLastServCell to include the RSRP and RSRQ, if available, from the PCell based on measurements collected up to the time the UE detected the radio link failure; 3> Except for NB-IoT, set the measResultNeighCells to include the cells with the best measurement, in addition to the PCell, ordered so that the best cell is listed first, based on measurements collected up to the point where the UE detected a radio link failure, and define its fields as follows: 4> If the UE was configured to perform measurements for one or more EUTRA frequencies, include the measResultListEUTRA; 4> If the UE is configured to perform measurement reporting for one or more neighboring UTRA frequencies, include the measResultListUTRA; 4> If the UE has been configured to perform measurement reporting for one or more neighboring GERAN frequencies, include the measResultListGERAN; 4> If the UE has been configured to perform measurement reporting for one or more neighboring CDMA2000 frequencies, include the measResultsCDMA2000; Petition 870250103056, dated 11 / 11 / 2025, page 56 / 116 47 / 86 4> If the UE is configured to perform measurement reporting, unrelated to NR side link communication, for one or more neighboring NR frequencies, include the measResultListNR; 4> For each neighboring cell included, include the optional fields that are available; NOTE 1: Measured quantities are filtered by the L3 filter, as configured in the mobility measurement configuration. Measurements are based on the time-domain measurement feature constraint, if configured. Cells listed as excluded do not need to be reported. 3> Except for NB-IoT, if available, set the logMeasResultListWLAN to include the WLAN measurement results, in descending order of RSSI for the WLAN APs; 3> Except for NB-IoT, if available, set the logMeasResultListBT to include Bluetooth measurement results, in descending order of RSSI for Bluetooth signals; 3> If detailed location information is available, set the locationInfo content as follows: 4> include locationCoordinates; 4> Include horizontal velocity, if available; 3> Set the failedPCellId to the global cell identity, if available, and otherwise, except for NB-IoT, to the physical cell identity and carrier frequency of the PCell where the radio link failure was detected; Petition 870250103056, dated 11 / 11 / 2025, p. 57 / 116 48 / 86 3> Except for NB-IoT, set tac-FailedPCell to the trace area code, if available, of the PCell where the radio link failure is detected; 3> Except for NB-IoT, if an RRCConnectionReconfiguration message including mobilityControlInfo was received before the connection failure: 4> If the last RRCConnectionReconfiguration message, including mobilityControlInfo, referred to an intra-E-UTRA transfer: 5> Include the previousPCellId and set it as the global cell identity of the PCell where the last RRCConnectionReconfiguration message, including mobilityControlInfo, was received; 5> Set timeConnFailure to the time elapsed since receiving the last RRCConnectionReconfiguration message including mobilityControlInfo; 4> If the last RRCConnectionReconfiguration message, including mobilityControlInfo, referred to a transfer to E-UTRA from UTRA, and if UE supports Radio Link Failure Reporting to MRO Inter-RAT: 5> include previousNR-PCellId and set it to the global PCell cell identity where the last RRCConnectionReconfiguration message including mobilityControlInfo was received embedded in the NR RRC message, MobilityFromNRCommand message as specified in clause 5.4.3.3 of TS 38.331

[82] ; 5> Set timeConnFailure to the elapsed time. Petition 870250103056, dated 11 / 11 / 2025, p. 58 / 116 49 / 86 since receiving the last RRCConnectionReconfiguration message including the mobilityControlInfo embedded in the NR RRC message, MobilityFromNRCommand message as specified in clause 5.4.3.3 of TS 38.331

[82] ; 3> Except for NB-IoT, if the UE supports the QC1 indication in the Radio Link Failure Report and has a DRB for which QCI is 1: 4> include drb-EstablishedWithQCI-1; 3> Except for NB-IoT, set connectionFailureType to rlf; 3> Except for NB-IoT, set the c-RNTI to the C-RNTI used in PCell; 3> Except for NB-IoT, set rlf-Cause to enable radio link failure detection.

[0072] The UE can store transfer failure information in VarRLF-Report according to the following procedure: 3> Clear the information included in the VarRLF-Report, if any; 3> Define plmn-IdentityList to include the list of EPLMNs stored by UE (i.e., include RPLMN); 3> Define the measResultLastServCell to include the RSRP and RSRQ, if available, from the originating PCell based on measurements collected up to the point the UE detected the transfer failure, and in accordance with the following; 4> If the UE includes rsrqResult, include lastServCellRSRQ-Type; Petition 870250103056, dated 11 / 11 / 2025, p. 59 / 116 50 / 86 3> Define the measResultNeighCells to include the cells with the best measurements, in addition to the source PCell, ordered so that the best cell is listed first, based on the measurements collected up to the point where the UE detected the transfer failure, and define its fields as follows; 4> If the UE is configured to perform measurements for one or more EUTRA frequencies, include measResultListEUTRA; 4> If the UE includes rsrqResult, include rsrq-Type; 4> If the UE is configured to perform measurement reporting for one or more neighboring UTRA frequencies, include the measResultListUTRA; 4> If the UE has been configured to perform measurement reporting for one or more neighboring GERAN frequencies, include the measResultListGERAN; 4> If the UE has been configured to perform measurement reporting for one or more neighboring CDMA2000 frequencies, include the measResultsCDMA2000; 4> If the UE is configured to perform measurement reporting, unrelated to NR side link communication, for one or more neighboring NR frequencies, include the measResultListNR; 4> For each neighboring cell included, include the optional fields that are available; NOTE 2: Measured quantities are filtered by the L3 filter, as configured in the mobility measurement configuration. Measurements are based on the measurement resource constraint in Petition 870250103056, dated 11 / 11 / 2025, pp. 60 / 116 51 / 86 time domain, if configured. Cells listed as deleted do not need to be reported. 3> If available, set the logMeasResultListWLAN to include WLAN measurement results, in descending order of RSSI for WLAN APs; 3> If available, set the logMeasResultListBT to include Bluetooth measurement results, in descending order of RSSI for Bluetooth signals; 3> If detailed location information is available, set the locationInfo content as follows: 4> include locationCoordinates; 4> Include horizontal velocity, if available; 3> If the last RRCConnectionReconfiguration message, including mobilityControlInfo, referred to an intra-RAT transfer failure (E-UTRA to E-UTRA): 4> Set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of the PCell targeted for the failed transfer; 4> Include previousPCellId and set it to the global identity of the PCell cell where the last RRCConnectionReconfiguration message, including mobilityControlInfo, was received; 4> Set timeConnFailure to the time elapsed since receiving the last RRCConnectionReconfiguration message including mobilityControlInfo; Petition 870250103056, dated 11 / 11 / 2025, pp. 61 / 116 52 / 86 3> Otherwise, if the last MobilityFromEUTRA referred to an inter-RAT transfer failure from E-UTRA to NR: 4> Set the failedNR-PCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the PCell targeted for the failed transfer; 4> Include the previousPCellId and set it as the global cell identity of the PCell where the last MobilityFromEUTRACommand message was received; 4> Set timeConnFailure to the time elapsed since the last MobilityFromEUTRACommand message was received; 3> Define connectionFailureType as hof; 3> Set the c-RNTI to the C-RNTI used in the originating PCell;

[0073] In operation 7-25, UE 7-01 can initiate an RRC connection restoration procedure. However, UE 7-01 may fail to successfully complete the procedure, failing due to a predetermined reason. For example, the UE may operate a T311 timer when the RRC connection restoration procedure is initiated, but if the UE fails to select a suitable LTE cell before the T311 timer expires, the procedure may fail.

[0074] In operation 7-30, UE 7-01 can transition to an idle RRC mode (RRC_IDLE).

[0075] In operation 7-35, UE 7-01 can camp in an acceptable LTE cell 7-03. Petition 870250103056, dated 11 / 11 / 2025, pp. 62 / 116 53 / 86

[0076] In operation 7-40, UE 7-01 can perform an RRC connection establishment procedure to establish an RRC connection with the acceptable LTE cell 7-03. That is, UE 7-01 can transmit an RRC Connection Establishment Request message (RRCConnectionRequest) to cell 7-03. In response to this, the cell can transmit an RRC Connection Establishment message (RRCConnectionSetup) to the UE in operation 7-45. In operation 7-46, the UE can transition to a connected RRC mode (RRC_CONNECTED) by applying RRCConnectionSetup. The UE can consider or determine the cell as a current PCell. In operation 7-48, the UE, according to the disclosure, can propose performing at least one of the proposed methods (i.e., one of the following methods or a combination of some or all of the methods) according to the following conditions: - If radio link failure information or transfer failure information is included in the VarRLF-Report and a registered public land mobile network (PLMN) to which the UE registers is included in a plmn-IdentityList stored in the VarRLF-Report (if the UE has radio link failure information or transfer failure information available in the VarRLF-Report and if the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report), or if the UE has radio link failure information or transfer failure information in the VarRLF-Report and an acceptable cell is an existing PCell. If reconnectCellId is not set in VarRLF-Report after a connection restoration procedure failure Petition 870250103056, dated 11 / 11 / 2025, pp. 63 / 116 54 / 86 RRC (if reconnectCellId in VarRLF-Report is not set after the restore fails). ♦ Method 1: The UE can set an elapsed time since the last radio link failure or transfer failure in timeUntilReconnection in VarRLF-Report (set timeUntilReconnection in VarRLF-Report to the elapsed time since the last radio link failure or transfer failure). ♦ Method 2: The timeUntilReconnection setting in VarRLF-Report may not be performed. Since the value is not set, network optimization can be performed by identifying whether the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future. ♦ Method 3: The UE can set an elapsed time since the last radio link failure or transfer failure in a new `timeUntilReconnection` for an acceptable cell in the VarRLFReport. Through the above, network optimization can be performed by identifying that the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the UE's VarRLF-Report in the future. The UE can define a global cell identity and a tracking area code for the current PCell as eutraReconnectCellId in the VarRLF-Report's reconnectCellId (set eutraReconnectCellId in the VarRLF-Report's reconnectCellId for the global cell identity and tracking area code of the PCell). The UE can include, in the VarRLF-Report, a Petition 870250103056, dated 11 / 11 / 2025, pp. 64 / 116 The 55 / 86 indicator shows that the corresponding cell is an acceptable cell. Alternatively, the UE may not set any information in the VarRLF-Report's reconnectCellId. Through the above, network optimization can be performed by identifying that the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future.

[0077] Regarding the content proposed above, a base station can control which method the UE should apply according to a configuration. The UE can transmit an RRC Connection Setup Complete message to the operating cell 7-50. The UE can transmit the VarRLF-Report to the appropriate cell 7-02 via a UE information procedure, and an operator managing an appropriate cell can optimize a network based on the corresponding information. For example, based on the timeUntilReconnection information, the operator can identify how much time has elapsed from an RRC connection setup failure until the UE, which has radio link failure information or transfer failure information in the VarRLF-Report, reconfigures an RRC connection with a predetermined cell.Thus, if the corresponding time is too long, the operator may operate a network by additionally providing a new cell or optimizing existing cells. Similarly, based on the reconnectCellId, the operator can identify a cell to which the UE subsequently connected, and this information can be used to determine... Petition 870250103056, dated 11 / 11 / 2025, pp. 65 / 116 56 / 86 if it is necessary to provide an additional cell or properly manage existing cells. Furthermore, if the reconnectCellId for an acceptable cell is set in VarRLF-Report, the UE may not report the corresponding information for a suitable cell. An acceptable cell does not belong to an operator to which the UE has subscribed, and therefore, if the UE sends reconnectCellId for a subscribed operator, it will be providing network operation information from another operator.

[0078] FIG. 8 is a flowchart of a process for updating radio link failure information or transfer failure information in an RRC connection establishment procedure, after an RRC connection restoration procedure performed by a UE fails in a next-generation mobile communication system, according to a disclosure embodiment.

[0079] With reference to FIG. 8, an UE 8-01 can be in an RRC-connected mode (RRC_CONNECTED) establishing an RRC connection with an LTE base station 8-02. The LTE base station can be connected to an operating EPC or 5GC 8-05.

[0080] In operation 8-10, UE 8-01 can transmit a UE CapabilityInformation message to base station 8-02. An indicator associated with an acceptable cell can be included in the message, and it can be an indicator associated with cells other than a suitable VarRLF-Report cell. Additionally, the message can include UE CapabilityInformation associated with the ability to store information other than a suitable VarRLF-Report cell. Petition 870250103056, dated 11 / 11 / 2025, pp. 66 / 116 57 / 86

[0081] In operation 8-15, UE 8-01 can detect a radio link failure (RLF) or a handover failure can occur due to a predetermined reason. For example, UE can detect an RLF when a T310 timer expires for a currently connected 8-02 primary cell (PCell), or a handover failure can occur when a T304 timer expires, even though UE receives an RRC message (e.g., RRCConnectionReconfiguration or MobilityFromEUTRACommand so that targetRAT-Type is set to nr) indicating that handover is required from the currently connected primary cell.

[0082] In operation 8-20, UE 8-01 can store radio link failure information (when detecting an RLF) or transfer failure information (when a transfer failure occurs) in VarRLF-Report. This may be the same as the mode described above.

[0083] In operation 8-25, UE 8-01 can initiate an RRC reconnection procedure. However, UE 8-01 may fail to successfully complete the procedure, failing due to a predetermined reason. For example, the UE may operate a T311 timer when the RRC reconnection procedure is initiated, but if the UE fails to select a suitable LTE cell before the T311 timer expires, the procedure may fail.

[0084] In operation 8-30, UE 8-01 can transition to an idle RRC mode (RRC_IDLE).

[0085] In operation 8-35, the UE 8-01 can camp in a cell. Petition 870250103056, dated 11 / 11 / 2025, pp. 67 / 116 58 / 86 NR acceptable 8-03.

[0086] In operation 8-40, UE 8-01 can perform an RRC connection establishment procedure to establish an RRC connection with acceptable NR cell 8-03. That is, UE 801 can transmit an RRC connection establishment request message (RRCSetupRequest) to cell 8-03. In response to this, the cell can transmit an RRC connection establishment message (RRCSetup) to the UE in operation 8-45. In operation 8-46, the UE can transition to a connected RRC mode (RRC_CONNECTED) by applying RRCSetup. The UE can consider or determine the cell as a current PCell. In operation 8-48, the UE, according to the disclosure, can propose performing at least one of the proposed methods (i.e., one of the following methods or a combination of some or all of the methods) according to the following conditions: - If the UE supports an RLF report for an inter-RAT NR MRO defined in the TS 36.306 standard, radio link failure or transfer failure information is included in the TS 36.331 VarRLF Report, and a registered public land mobile network (PLMN) to which the UE registers is included in the plmn-IdentityList stored in the TS 36.331 VarRLF-Report (if the UE supports an RLF report for inter-RAT NR MRO as defined in TS 36.306, and if the UE has radio link failure or transfer failure information available in the TS 36.331 VarRLF-Report and if the RPLMN is included in the plmnIdentityList stored in the TS 36.331 VarRLF-Report), or if the UE supports an RLF report for an inter-RAT NR MRO defined Petition 870250103056, dated 11 / 11 / 2025, pp. 68 / 116 59 / 86 in the TS 36.306 standard, radio link failure information or transfer failure information is included in the VarRLFReport of the TS 36.331 standard, and an acceptable cell is a current PCell. If reconnectCellId is not defined in the VarRLF-Report of the TS 36.331 standard after a failure in the RRC connection re-establishment procedure (if reconnectCellId in VarRLFReport is not defined after the re-establishment failure). ♦ Method 1: The UE can set an elapsed time since a radio link failure or a transfer failure in timeUntilReconnection in the VarRLF-Report of the TS 36.331 standard (set timeUntilReconnection in the VarRLF-Report of TS 36.331 to the elapsed time since the last radio link failure or transfer failure). ♦ Method 2: The timeUntilReconnection setting in the VarRLF-Report of the TS 36.331 standard cannot be performed. Since the value is not set, network optimization can be performed by identifying whether the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the VarRLF-Report from the UE in the future. ♦ Method 3: The UE can define an elapsed time since the last radio link failure or transfer failure in a new 'timeUntilReconnection' parameter for an acceptable cell in the VarRLF-Report of the TS36.331 standard. Through the above, network optimization can be performed by identifying that the UE established an RRC connection with an acceptable cell when a suitable cell retrieves the UE's VarRLF-Report in the future. Petition 870250103056, dated 11 / 11 / 2025, pp. 69 / 116 60 / 86 The UE can define a global cell identity and a tracking area code of the current PCell as nrReconnectCellId in the reconnectCellId of the TS 36.331 VarRLF-Report (set nrReconnectCellId in reconnectCellId in the TS 36.331 VarRLF-Report for the global cell identity and tracking area code of the PCell). The UE can include, in the VarRLF-Report, an indicator showing that the corresponding cell is an acceptable cell. Alternatively, the UE can not define any information in the reconnectCellId of the VarRLF-Report. Through the above, network optimization can be achieved by identifying that the UE has established an RRC connection with an acceptable cell when a suitable cell retrieves the UE's VarRLF-Report in the future.

[0087] Regarding the content proposed above, a base station can control which method the UE should apply according to a configuration. The UE can transmit an RRC Setup Complete message to the operating cell 8-50. The UE can transmit the VarRLF-Report to the appropriate cell 8-02 via a UE information procedure, and an operator managing an appropriate cell can optimize a network based on the corresponding information. For example, based on the timeUntilReconnection information, the operator can identify how much time has elapsed from an RRC connection restoration failure until the UE, which has radio link failure information or transfer failure information in the VarRLF-Report, reconfigures an RRC connection with a predetermined cell. Thus, if the time Petition 870250103056, dated 11 / 11 / 2025, pp. 70 / 116 If the corresponding 61 / 86 is too long, the operator may operate a network by additionally providing a new cell or optimizing existing cells. Similarly, based on the reconnectCellId, the operator can identify a cell to which the UE subsequently connected, and this information can be used to determine whether it is necessary to provide an additional cell or to properly manage existing cells. Furthermore, if the reconnectCellId for an acceptable cell is set in VarRLF-Report, the UE may not report the corresponding information for a suitable cell. An acceptable cell does not belong to an operator to which the UE has subscribed, and therefore, if the UE sends reconnectCellId for a subscribed operator, it will be providing network operation information from another operator.

[0088] FIG. 9 is a flowchart of a process in which a UE transfers radio link fault information or transfer fault information to a base station in a next-generation mobile communication system, according to a disclosure embodiment.

[0089] With reference to FIG. 9, a UE 9-01 can be in an RRC connected mode (RRC_CONNECTED) setting up an RRC connection with an operating NR 9-02 base station 9-05.

[0090] In operation 9-10, base station 9-02 can transmit a UE Information Request message to UE 9-01 for which security has been successfully activated. The message may include rlfReportReq configured as true. Petition 870250103056, dated 11 / 11 / 2025, pp. 71 / 116 62 / 86

[0091] In operation 9-15, when rlf-ReportReq is set to true in the UE information request message received in operation 9-10, UE 9-01 can perform the following procedure and can transmit a UE information response message (UEInformationResponse) to base station 902. 2> If the UE has radio link failure information or transfer failure information available in the VarRLFReport, and if the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report: 3> Set timeSinceFailure in VarRLF-Report to the elapsed time since the last radio link failure or transfer failure in the NR; 3> Set the rlf-Report in the UEInformationResponse message with the value of rlf-Report in VarRLFReport; 3> Discard the rlf-Report from VarRLF-Report after successful delivery of the UEInformationResponse message confirmed by the lower layers; 2> Otherwise, if the UE is capable of reporting RLF between RATs, as defined in TS 38.306, and has radio link failure information or transfer failure information available in the VarRLF-Report of TS 36.331, and if RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report of TS 36.331: 3> set timeSinceFailure in the VarRLF-Report of TS 36.331

[10] to the elapsed time since the last link failure Petition 870250103056, dated 11 / 11 / 2025, pp. 72 / 116 63 / 86 radio or transfer failure on EUTRA; 3> define failedPCellId-EUTRA in the rlf-Report in the UEInformationResponse message to indicate the PCell in which the RLF was detected or the PCell of origin of the failed transfer in the VarRLF-Report of TS 36.331

[10] ; 3> Define measResult-RLF-Report-EUTRA in rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report of TS 36.331; 3> Discard the rlf-Report from the TS 36.331 VarRLF-Report after successful delivery of the UEInformationResponse message confirmed by the lower layers;

[0092] The RLF-Report included in the EU information response message may have an ASN.1 structure, as shown below. In this case, the EU may configure the RLF-Report by applying the method described above and may include it in the EU information response message. RLF-Report-r16::= CHOICE { nr-RLF-Report-r16 SEQUENCE { measResultLastServCell-r16 MeasResultRLFNR-r16, measResultNeighCells-r16 SEQUENCE { measResultListNR-r16 MeasResultList2NR-r16 OPTIONAL, measResultListEUTRA-r16 MeasResultList2EUTRA-r16 OPTIONAL} OPTIONAL, c-RNTI-r16 RNTI-Value, previousPCellId-r16 CHOICE { nrPreviousCell-r16 CGI-Info-Logging-r16, eutraPreviousCell-r16 CGI-InfoEUTRALogging} OPTIONAL, failedPCellId-r16 CHOICE { nrFailedPCellId-r16 CHOICE { Petition 870250103056, dated 11 / 11 / 2025, pp. 73 / 116 64 / 86 cellGlobalId-r16 CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-rl6}, eutraFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-InfoEUTRALogging, pci-arfcn-r16 PCI-ARFCN-EUTRA-r16}}, reconnectCellId-r16 CHOICE { nrReconnectCellId-r16 CGI-Info-Logging-r16, eutraReconnectCellId-r16 CGI-InfoEUTRALogging} OPCIONAL, timeUntilReconnection-r16 TimeUntilReconnection-r16 OPTIONAL, reestablishmentCellId-r16 CGI-Info-Logging-r16 OPTIONAL, timeConnFailure-r16 INTEGER (0..1023) OPTIONAL, timeSinceFailure-r16 TimeSinceFailure-r16, connectionFailureType-r16 ENUMERATED {rlf, hof}, rlf-Cause-r16 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, beamFailureRecoveryFailure, lbtFailure-r16, bh-rlfRecoveryFailure, t312-expiry-r17, spare1}, locationInfo-r16 LocationInfo-r16 OPTIONAL, noSuitableCellFound-r16 ENUMERATED {true} OPTIONAL, ra-InformationCommon-r16 RA-InformationCommon-r16 OPTIONAL, ..., [ [ csi-rsRLMConfigBitmap-v1650 BIT STRING (SIZE (96)) OPTIONAL ] ] , [ [ lastHO-Type-r17 ENUMERATED {cho, daps, spare2, spare1} OPTIONAL, timeConnSourceDAPS-Failure-r17 TimeConnSourceDAPS-Failure Petição 870250103056, de 11 / 11 / 2025, pág. 74 / 116 65 / 86 r17 OPTIONAL, timeSinceCHO-Reconfig-r17 TimeSinceCHO-Reconfig-r17 OPTIONAL, choCellId-r17 CHOICE { cellGlobalId-r17 CGI-Info-Logging-r16, pci-arfcn-r17 PCI-ARFCN-NR-r16} OPTIONAL, choCandidateCellList-r17 ChoCandidateCellList-r17 OPTIONAL ] ]}, eutra-RLF-Report-r16 SEQUENCE { failedPCellId-EUTRA CGI-InfoEUTRALogging, measResult-RLF-Report-EUTRA-r16 OCTET STRING, ..., [ [ measResult-RLF-Report-EUTRA-v1690 OCTET STRING OPTIONAL ] ]}}

[0093] FIG. 10 is a flowchart of a process in which a UE transfers radio link fault information or transfer fault information to a base station in a next-generation mobile communication system, according to a disclosure embodiment.

[0094] With reference to FIG. 10, a UE 10-01 can be in an RRC connected mode (RRC_CONNECTED) establishing an RRC connection with an operating LTE base station 10-02 10-05. An LTE base station connected to an EPC can be called an eNB, and an LTE base station connected to a 5GC can be called an ng-eNB.

[0095] In operation 10-10, base station 10-02 can Petition 870250103056, dated 11 / 11 / 2025, pp. 75 / 116 66 / 86 transmit an EU Information Request (UEInformationRequest) message to EU 10-01 for which security has been successfully activated. The message may include rlfReportReq configured as true.

[0096] In operation 10-15, when rlf-ReportReq is set to true in the UE information request message received in operation 10-10, UE 10-01 can perform the following procedure and can transmit a UE information response message (UEInformationResponse) to base station 1002. 1> If rlfReportReq is set to true and the UE has radio link failure information or transfer failure information available in VarRLF-Report (VarRLFReport-NB in ​​NB-IoT), and if RPLMN is included in plmnIdentityList stored in VarRLF-Report: 2> For NB-IoT, if the selected global cell identity is the same as reestablishmentCellId in VarRLFReport-NB: 3> Remove the reestablishmentCellId from VarRLF-Report-NB; 2> Set timeSinceFailure in VarRLF-Report (VarRLFReport-NB in ​​NB-IoT) to the time elapsed since the last radio link failure or transfer in E-UTRA; 2> Set the rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report (VarRLF-Report-NB in ​​NB-IoT); 2> Discard the rlf-Report from VarRLF-Report (VarRLF-ReportNB in ​​NB-IoT) after successful message delivery. Petition 870250103056, dated 11 / 11 / 2025, pp. 76 / 116 67 / 86 UEInformationResponse confirmed by lower layers;

[0097] The RLF-Report included in the EU information reply message may have an ASN. 1 structure, as shown below. In this case, the EU may configure the RLF-Report by applying the modality described above and may include it in the EU information reply message. RLF-Report-r9::= SEQUENCE { measResultLastServCell-r9 SEQUENCE { rsrpResult-r9 RSRP-Range, rsrqResult-r9 RSRQ-Range OPTIONAL}, measResultNeighCells-r9 SEQUENCE { measResultListEUTRA-r9 MeasResultList2EUTRA-r9 OPTIONAL, measResultListUTRA-r9 MeasResultList2UTRA-r9 OPTIONAL, measResultListGERAN-r9 MeasResultListGERAN OPTIONAL, measResultsCDMA2000-r9 MeasResultList2CDMA2000-r9 OPTIONAL} OPTIONAL, ..., [ [ locationInfo-r10 LocationInfo-r10 OPTIONAL, failedPCellId-r10 CHOICE { cellGlobalId-r10 CellGlobalIdEUTRA, pci-arfcn-r10 SEQUENCE { physCellId-r10 PhysCellId, carrierFreq-r10 ARFCN-ValueEUTRA}} OPTIONAL, Petition 870250103056, dated 11 / 11 / 2025, pp. 77 / 116 68 / 86 reestablishmentCellId-r10 CellGlobalIdEUTRA OPTIONAL, timeConnFailure-r10 INTEGER (0..1023) OPTIONAL, connectionFailureType-r10 ENUMERATED {rlf, hof} OPTIONAL, previousPCellId-r10 CellGlobalIdEUTRA ] ] OPTIONAL , [ [ failedPCellId-v1090 SEQUENCE { carrierFreq-v1090 ARFCN-ValueEUTRA-v9e0} OPCIONAL ] ] , [ [ basicFields-r11 SEQUENCE { c-RNTI-r11 C-RNTI, rlf-Cause-r11 ENUMERATED { randomAccessProblem, t310-Expiry, r12}, timeSinceFailure-r11 rlc-MaxNumRetx, t312-Expiry- TimeSinceFailure-r11} OPCIONAL, previousUTRA-CellId-r11 SEQUENCE { carrierFreq-r11 ARFCN-ValueUTRA, physCellId-r11 CHOICE { fdd-r11 PhysCellIdUTRA-FDD, tdd-r11 PhysCellIdUTRA-TDD}, cellGlobalId-r11 CellGlobalIdUTRA OPTIONAL} OPCIONAL, selectedUTRA-CellId-r11 SEQUENCE { carrierFreq-r11 ARFCN-ValueUTRA, Petição 870250103056, de 11 / 11 / 2025, pág. 78 / 116 69 / 86 physCellId-r11 CHOICE { fdd-r11 PhysCellIdUTRA-FDD, tdd-r11} PhysCellIdUTRA-TDD} ] ] , OPCIONAL SEQUENCE { TrackingAreaCode OPCIONAL, RSRQ-Range-v1250 RSRQ-Type-r12 MeasResultList2EUTRA-v1250 ENUMERATED {qci1} RSRP-Range-v1360 LogMeasResultListBT-r15 LogMeasResultListWLAN-r15 MeasResultCellListNR-r15 CellGlobalIdNR-r16 CHOICE { [[ failedPCellId-v1250 tac-FailedPCell-r12} measResultLastServCell-v1250 OPTIONAL, lastServCellRSRQ-Type-r12 OPTIONAL, measResultListEUTRA-v1250 OPTIONAL ] ] , [ [ drb-EstablishedWithQCI-1-r13 OPTIONAL ] ] , [ [ measResultLastServCell-v13 60 OPTIONAL ] ] , [ [ logMeasResultListBT-r15 OPTIONAL, logMeasResultListWLAN-r15 OPTIONAL ] ] , [ [ measResultListNR-r16 OPTIONAL, previousNR-PCellId-r16 OPTIONAL, failedNR-PCellId-r16 Petição 870250103056, de 11 / 11 / 2025, pág. 79 / 116 70 / 86 cellGlobalId CellGlobalIdNR-r16, pci-arfcn SEQUENCE { physCellId-r16 PhysCellIdNR-r15, carrierFreq-r16 ARFCN-ValueNR-r15}} OPTIONAL, reconnectCellId-r16 CHOICE { nrReconnectCellId CellGlobalIdNR-r16, eutraReconnectCellId SEQUENCE { cellGlobalId-r16 CellGlobalIdEUTRA, trackingAreaCode-EPC-r16 TrackingAreaCode OPTIONAL, trackingAreaCode-5GC-r16 TrackingAreaCode-5GC- r15 OPTIONAL}} OPTIONAL, timeUntilReconnection-r16 TimeUntilReconnection-r16 1 1 OPTIONAL ] ] [ [ , measResultListNR-v1640 SEQUENCE { carrierFreqNR-r16 ARFCN-ValueNR-r15} OPTIONAL, measResultListExtNR-r16 MeasResultFreqListNR-r16 ] ]} OPTIONAL RLF-Report-v9e0::= SEQUENCE { measResultListEUTRA-v9e0 MeasResultList2EUTRA-v9e0}

[0098] FIG. 11 is a flowchart of a process for updating radio link fault information or transfer fault information in a connection-establishing procedure (RRC), following a connection-reestablishing procedure. Petition 870250103056, dated 11 / 11 / 2025, pp. 80 / 116 71 / 86 RRC performed by a UE failure in a next-generation mobile communication system, according to a disclosure modality.

[0099] With reference to FIG. 1, a UE 11-01 can be in an RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with an NR 1-02 base station.

[0100] In operation 11-10, UE 11-01 can transmit a UE CapabilityInformation message to base station 11-02. An indicator associated with an acceptable cell can be included in the message, and this can be an indicator associated with cells other than a suitable VarRLF-Report cell. Additionally, the message can include UE CapabilityInformation associated with the ability to store information other than a suitable VarRLF-Report cell. In the message, capability information associated with whether it has the capacity to store information associated with a voice recoil and / or an emergency service recoil in the NR RLF report may be included.

[0101] In operation 11-15, UE 11-01 can receive a MobilityFromNRCommand message from base station 11-02. The targetRAT-Type configured for eutra can be included in the message. The voiceFallbackIndication can also be included in the message.

[0102] In operation 11-20, UE 11-01 can determine that an NR failure mobility occurs due to a predetermined reason. For example, if the connection to a target radio access technology is not successfully established (if UE fails to establish the connection to the access technology of Petition 870250103056, dated 11 / 11 / 2025, pp. 81 / 116 72 / 86 target radio), it is determined that a mobility of the NR failure occurred.

[0103] In operation 11-25, if the targetRAT-Type in the MobilityFromNRCommand received in operation 11-15 is set to eutra, and UE 11-01 supports a radio link failure report for an inter-RAT EUTRA MRO (if the targetRAT-Type in the received MobilityFromNRCommand is set to eutra and the UE supports Radio Link Failure Report for inter-RAT EUTRA MRO), UE 11-01 may store transfer failure information in the VarRLF-Report. This can be accomplished according to at least one of the modalities described above. Additionally, if voiceFallbackIndication is included in MobilityFormNRCommand, or if the NR procedure mobility is for an emergency service retreat, the UE may store an indicator indicating the same in the VarRLF-Report.

[0104] In operation 11-30, UE 11-01 may attempt to select an E-UTRA cell. For reference, if voiceFallbackIndication is included in MobilityFormNRCommand, or if the NR procedure mobility is for an emergency service retreat, UE may attempt to select an E-UTRA cell.

[0105] In operation 11-35, UE 11-01 can transition to an idle RRC mode (RRC_IDLE) when a suitable LTE cell 11-03 is selected.

[0106] In operation 11-40, UE 11-01 can perform an RRC connection establishment procedure with the appropriate LTE cell 11-03. That is, UE can transmit a message of Petition 870250103056, dated 11 / 11 / 2025, pp. 82 / 116 73 / 86 RRC ConnectionRequest is sent to the operating cell 11-40. In response, the cell can transmit an RRC Connection Setup message to the UE in operation 11-45. The UE can transition to a connected RRC mode in operation 11-46 and can consider the cell as a primary cell. When condition 1 is met and, consequently, condition 2 is also met, the UE can perform operation 1 in operation 11-50. Condition 1: - If the UE supports an RLF report for an EUTRA interRAT MRO defined in the TS 38.306 standard, radio link failure information or transfer failure information will be included in the VarRLF-Report of the TS 38.331 standard, and a registered public land mobile network (PLMN) to which the UE registers will be included in the plmn-IdentityList stored in the VarRLF-Report of the TS 38.331 standard (if the UE supports RLF reporting for EUTRA interRAT MRO as defined in TS 38.306, and if the UE has radio link failure information or transfer failure information available in the VarRLF-Report of TS 38.331 and if the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report of TS 38.331). Condition 2: - If reconnectCellId is not defined in the VarRLF-Report of the TS 38.331 standard and an EPS rollback for IMS voice is triggered via MobilityFromNRCommand or a rollback for emergency service is triggered via MobilityFromNRCommand (if reconnectCellId in Petition 870250103056, dated 11 / 11 / 2025, pp. 83 / 116 74 / 86 If the VarRLF-Report of TS 38.331 is not defined and the EPS rollback for IMS voice or the rollback for emergency services has been triggered in the NR via MobilityFromNRCommand (i.e., if the operation is performed by executing operations 11-30 and 11-35). Operation 1: - The UE can set an elapsed time since a radio link failure or a transfer failure in timeUntilReconnection in the VarRLF-Report of the TS 38.331 standard (set timeUntilReconnection in the VarRLF-Report of TS 38.331 to the elapsed time since the last radio link failure or transfer failure). - The UE can define a global cell identity and a tracking area code for the current PCell as eutraReconnectCellId in reconnectCellId of the VarRLF-Report of the TS 38.331 standard (set eutraReconnectCellId in reconnectCellId in the VarRLF-Report of TS 38.331 for the global cell identity and tracking area code of the PCell).

[0107] In operation 11-55, UE 11-01 can transmit a complete RRC connection setup message (RRCConnectionSetupComplete) to cell 11-03.

[0108] In operation 11-60, the UE can be in an RRC connected mode by setting up an RRC connection with the NR 1102 base station.

[0109] In operation 11-65, base station NR 11-02 can transmit a UE Information Request message to UE 11-01 for which security has been successfully activated. The message may include Petition 870250103056, dated 11 / 11 / 2025, page 84 / 116 75 / 86 ReportReq set to true.

[0110] In operation 11-70, UE 11-01 can transmit a UE Information Response message, including the RLF-Report, to base station NR 11-02. This can be done according to the method described above.

[0111] FIG. 12 is a flowchart of a process for updating radio link failure information or transfer failure information in an RRC connection establishment procedure, after an RRC connection restoration procedure performed by a UE fails in a next-generation mobile communication system, according to a disclosure embodiment.

[0112] With reference to FIG. 12, a UE 12-01 can be in an RRC connected mode (RRC_CONNECTED) setting up an RRC connection with an operating NR 12-02 base station 12-05.

[0113] In operation 12-10, UE 12-01 can transmit a UE CapabilityInformation message to base station 12-02. This can be done according to the method described above.

[0114] In operation 12-15, UE 12-01 can receive a MobilityFromNRCommand message from base station 12-02. In the message, the targetRAT-Type can be set to eutra. The voiceFallbackIndication can be included in the message.

[0115] In operation 12-20, UE 12-01 can determine that an NR failure mobility occurs due to a predetermined reason. For example, if the connection to a target radio access technology is not successfully established (if UE does not Petition 870250103056, dated 11 / 11 / 2025, pages 85 / 116 76 / 86 managing to establish a connection with the target radio access technology), it is determined that a mobility failure of NR occurred.

[0116] In operation 12-25, if the targetRAT-Type in the MobilityFromNRCommand received in operation 12-15 is set to eutra, and UE 12-01 supports a radio link failure report for an inter-RAT EUTRA MRO (if the targetRAT-Type in the received MobilityFromNRCommand is set to eutra and the UE supports Radio Link Failure Report for inter-RAT EUTRA MRO), UE 11-01 may store transfer failure information in the VarRLF-Report. This can be accomplished according to at least one of the modalities described above. Additionally, if voiceFallbackIndication is included in MobilityFormNRCommand, or if the NR procedure mobility is for an emergency service retreat, the UE may store an indicator indicating the same in the VarRLF-Report.

[0117] In operation 12-30, UE 12-01 may attempt to select an E-UTRA cell. For reference, if voiceFallbackIndication is included in MobilityFormNRCommand, or if the NR procedure mobility is for an emergency service retreat, UE may attempt to select an E-UTRA cell.

[0118] In operation 12-35, if no suitable LTE cell exists and an acceptable 12-03 cell that supports an emergency call is selected when an emergency call is in progress (if no suitable E-UTRA cell is available and an acceptable E-UTRA cell that supports an emergency call is selected) Petition 870250103056, dated 11 / 11 / 2025, pp. 86 / 116 77 / 86 emergency call is selected when the UE has an emergency call in progress), the UE 12-01 may transition to an idle RRC mode (RRC_IDLE).

[0119] In operation 12-40, UE 12-01 can perform an RRC connection establishment procedure with the acceptable LTE cell 12-03. That is, the UE can transmit an RRC ConnectionRequest message to the cell in operation 12-40. In response to this, the cell can transmit an RRC Connection Setup message to the UE in operation 12-45. The UE can transition to a connected RRC mode in operation 12-46 and can consider the cell as a primary cell. In this case, the UE may not store any information in the VarRLF-Report.Based on the above, when the base station retrieves an RLF-Report from the UE later, it can recognize that the UE has selected an acceptable E-UTRA cell that supports an emergency call if timeUntilReconnection and reconnectCellId do not exist and voiceFallbackIndication is included in MobilityFormNRCommand, or if an indicator showing that a mobility from the NR procedure is intended for a retreat to emergency services is included in the RLF-Report. Alternatively, when condition 1 is met and, consequently, condition 2 is also met, the UE can perform operation 1 in operation 12-50. Condition 1: - If the EU supports an RLF report for an EUTRA MRO inter Petition 870250103056, dated 11 / 11 / 2025, pp. 87 / 116 78 / 86 If the RAT defined in the TS 38.306 standard, radio link failure information or transfer failure information is included in the VarRLF-Report of the TS 38.331 standard, and a registered public land mobile network (PLMN) to which the UE registers is included in the plmn-IdentityList stored in the VarRLF-Report of TS 38.331 (if the UE supports RLF reporting for EUTRA MRO inter-RAT as defined in TS 38.306, and if the UE has radio link failure information or transfer failure information available in the VarRLF-Report of TS 38.331 and if the RPLMN is included in the plmn-IdentityList stored in the VarRLF-Report of TS 38.331), or if the UE supports RLF reporting for an EUTRA MRO inter-RAT defined in the TS 38.306 standard, and radio link failure information. or transfer failure information is included in the VarRLF-Report of the TS 38.331 standard. Condition 2: - If reconnectCellId is not defined in the VarRLF-Report of the TS 38.331 standard, and an EPS rollback to IMS voice is triggered via MobilityFromNRCommand or a rollback to emergency service is triggered via MobilityFromNRCommand (if reconnectCellId in the VarRLF-Report of TS 38.331 is not defined, and the EPS rollback to IMS voice or the rollback to emergency service has been triggered in NR via MobilityFromNRCommand, i.e., if the operation is performed by performing operations 12-30 and 12-35), or if an EPS rollback to IMS voice is triggered via MobilityFromNRCommand or a rollback to emergency service is triggered via MobilityFromNRCommand. Operation 1: Petition 870250103056, dated 11 / 11 / 2025, pp. 88 / 116 79 / 86 - The UE can define an elapsed time since a radio link failure or a transfer failure in timeUntilReconnection in the VarRLF-Report of the TS 38.331 standard (set timeUntilReconnection in the VarRLF-Report of TS 38.331 to the elapsed time since the last radio link failure or transfer failure). For reference, the timeUntilReconnection parameter can be a new field.

[0120] For reference, the decision to perform operation 1 or not to store any information in VarRLF-Report can be determined based on the base station configuration.

[0121] In operation 12-55, UE 12-01 can transmit a complete RRC connection setup message (RRCConnectionSetupComplete) to cell 12-03.

[0122] In 12-60 operation, the UE can be in an RRC connected mode by setting up an RRC connection with the NR 1202 base station.

[0123] In operation 12-65, base station NR 12-02 can transmit a UE information request message (UEInformationRequest) to UE 12-01 for which security has been successfully activated. The message may include rlfReportReq configured as true.

[0124] In operation 12-70, UE 12-01 can transmit a UE Information Response message, including the RLF-Report, to base station NR 12-02. This can be done according to the method described above.

[0125] FIG. 13 is a block diagram of the internal structure. Petition 870250103056, dated 11 / 11 / 2025, pp. 89 / 116 80 / 86 of an EU according to a disclosure method.

[0126] As illustrated in the drawing, the UE includes a radio frequency (RF) processor 13-10, a baseband processor 13-20, a storage 13-30 and a controller 1340.

[0127] The RF processor 13-10 performs a function for transmitting or receiving signals through a wireless channel, such as signal band conversion, amplification, or similar. That is, the RF processor 13-10 converts an uplink baseband signal supplied by the baseband processor 13-20 into an RF band signal to transmit the RF band signal through an antenna, and converts a downlink RF band signal received through the antenna into a baseband signal. For example, the RF processor 13-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), and the like. Although only a single antenna is illustrated in the drawing, the UE may include multiple antennas. Furthermore, the RF processor 13-10 may include a plurality of RF chains. Additionally, the RF processor 13-10 may perform beamforming.For beamforming, the 13-10 RF processor can control the phase and size of each of the signals transmitted or received through a plurality of antennas or antenna elements. Furthermore, the RF processor can perform MIMO and receive multiple layers when performing a MIMO operation.

[0128] The 13-20 baseband processor performs a function Petition 870250103056, dated 11 / 11 / 2025, pp. 90 / 116 81 / 86 conversion between a baseband signal and a bit stream according to the physical layer standard of a system. For example, in the case of data transmission, the 1320 baseband processor encodes and modulates a transmission bit stream to produce complex symbols. Furthermore, in the case of data reception, the 13-20 baseband processor restores a reception bit stream by demodulating and decoding a baseband signal provided by the 13-10 RF processor. For example, according to an orthogonal frequency division multiplexing (OFDM) scheme, in the case of data transmission, the 13-20 baseband processor produces complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then performs an inverse fast Fourier transform (IFFT) and cyclic prefix insertion (CP) operation to set the OFDM symbols.Furthermore, in the case of data reception, the 13-20 baseband processor divides a baseband signal provided by the 13-10 RF processor into OFDM symbol units, reconstructs the subcarrier-mapped signals via a Fast Fourier Transform (FFT), and then performs demodulation and decoding to reconstruct a received bitstream.

[0129] The 13-20 baseband processor and the 13-10 RF processor transmit and receive signals as described above. Thus, the 13-20 baseband processor and the 13-10 RF processor may be referred to as a transmitter, receiver, transceiver, or communication unit. Furthermore, at least one of the 13-20 baseband processors and the 13-10 RF processor Petition 870250103056, dated 11 / 11 / 2025, pp. 91 / 116 82 / 86 may include a plurality of communication modules to support different multiple radio access technologies. Furthermore, at least one of the 13-20 baseband processors and the 13-10 RF processor may include different communication modules to process signals from different frequency bands. For example, the different radio access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), and the like. Additionally, the different frequency bands may include a super high frequency (SHF) band (e.g., 2.5 Hz, 5 Hz) and a millimeter wave (mm) band (e.g., 60 GHz).

[0130] Storage 13-30 can store data such as a basic program, an application program, and configuration information for UE operation. In particular, storage 13-30 can store information related to a second access node that performs wireless communication using a second radio access technology. Additionally, storage 13-30 can provide data stored in it according to a request from controller 13-40.

[0131] The 13-40 controller can control the overall operation of the UE. For example, the 13-40 controller can perform the transmission or reception of signals through the 13-20 baseband processor and the 13-10 RF processor. In addition, the 13-40 controller can write and read data in the 1340 storage. For this purpose, the 13-40 controller may include at least one processor. For example, the 13-40 controller may include a communication processor (CP) that performs the control of Petition 870250103056, dated 11 / 11 / 2025, pp. 92 / 116 83 / 86 communication and an application processor (AP) that controls a higher layer, such as an application program.

[0132] FIG. 14 is a block diagram that illustrates the configuration of an NR base station according to a modality.

[0133] As illustrated in the drawing, the base station may include an RF processor 14-10, a baseband processor 14-20, a backhaul communication unit 14-30, a storage unit 14-40 and a controller 14-50.

[0134] The 14-10 RF processor performs a function for transmitting or receiving signals through a wireless channel, such as signal band conversion, amplification, or similar. That is, the 14-10 RF processor converts an uplink baseband signal supplied by the 14-20 baseband processor into an RF band signal to transmit the RF band signal through an antenna, and converts a downlink RF band signal received through the antenna into a baseband signal. For example, the 14-10 RF processor may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. Although only a single antenna is illustrated in the drawing, the first access node may include multiple antennas. Furthermore, the 14-10 RF processor may include a plurality of RF chains. Additionally, the 14-10 RF processor may perform beamforming.For beamforming, the 14-10 RF processor can control the phase and size of each of the signals transmitted or received through a plurality of antennas or antenna elements. The RF processor can perform a link-based MIMO operation. Petition 870250103056, dated 11 / 11 / 2025, pp. 93 / 116 84 / 86 descending transmission of one or more layers.

[0135] The 14-20 baseband processor performs a conversion function between a baseband signal and a bit stream, according to the physical layer standard of an early radio access technology. For example, in the case of data transmission, the 14-20 baseband processor encodes and modulates a transmission bit stream to produce complex symbols. Furthermore, in the case of data reception, the 14-20 baseband processor restores a reception bit stream by demodulating and decoding a baseband signal provided by the 14-10 RF processor. For example, according to the OFDM scheme, in the case of data transmission, the 14-20 baseband processor can produce complex symbols by encoding and modulating a transmission bit stream, mapping the complex symbols to subcarriers, and then performing an IFFT operation and CP insertion to configure the OFDM symbols.Furthermore, in the case of data reception, the 14-20 baseband processor divides a baseband signal provided by the 14-10 RF processor into OFDM symbol units, restores the signals mapped to the subcarriers through FFT operation, and performs demodulation and decoding to restore a received bit stream. The 14-20 baseband processor and the 14-10 RF processor transmit and receive signals as described above. Thus, the 14-20 baseband processor and the 14-10 RF processor can be referred to as a transmitter, receiver, transceiver, communication unit, or wireless communication unit.

[0136] The 14-30 backhaul communication unit can Petition 870250103056, dated 11 / 11 / 2025, pp. 94 / 116 85 / 86 provide an interface for communicating with other nodes on a network. That is, the 1430 backhaul communication unit can convert a bit stream transmitted from the primary base station to another node, for example, a secondary base station, a central network, and the like, into a physical signal, and can convert a physical signal received from the other node into a bit stream.

[0137] The 14-40 storage device stores data such as a basic program, an application program, and configuration information for the operation of the primary base station. In particular, the 14-40 storage can store information associated with a carrier allocated to a connected UE, a measurement result reported by a connected UE, and the like. Furthermore, the 14-40 storage can store information that is a criterion for determining whether multiple accesses should be provided to a UE or whether such access should be interrupted. Additionally, the 14-40 storage can provide data stored within it according to a request from the 14-50 controller.

[0138] The 14-50 controller can control the overall operation of the primary base station. For example, the 14-50 controller can perform signal transmission or reception via the 14-20 baseband processor and the 14-10 RF processor, or via the 14-30 backhaul communication unit. In addition, the 14-50 controller can write and read data in the 1440 storage. For this purpose, the 14-50 controller may include at least one processor. Petition 870250103056, dated 11 / 11 / 2025, pages 95 / 116 86 / 86

[0139] The embodiments of the present invention described and illustrated in the descriptive report and drawings are merely specific examples presented to facilitate the explanation of the technical content of the embodiments of the invention and to aid in the understanding of the embodiments, and are not intended to limit the scope of the embodiments of the disclosure. It will be evident to those skilled in the art that, in addition to the embodiments set forth in this document, other variants based on the technical idea of ​​the disclosure may be implemented. Petition 870250103056, dated 11 / 11 / 2025, pp. 96 / 116

Claims

1 / 5 CLAIMS 1. A method of operating a terminal in a wireless communication system, the method CHARACTERIZED in that it comprises: receiving, from an NR base station, an NR transfer command message including information in which a target radio access technology (RAT) is configured for LTE; in the event that an NR transfer failure is detected, selecting a suitable LTE cell in the event that an acceptable LTE cell is available and selecting an acceptable LTE cell in the event that an acceptable LTE cell is not available; entering idle RRC mode; performing an RRC connection establishment procedure with respect to the selected LTE cell; in the event that the LTE cell to which the RRC connection is made is a suitable LTE cell, storing a time value from the transfer failure to reconnection, and an ID of the LTE cell to which the RRC connection is made in the VarRLF-Report associated with the NR;And in the case where the LTE cell to which the RRC connection is made is an acceptable LTE cell, store a time value from the transfer failure to the reconnection in the VarRLF-Report associated with the NR.

2. Method, according to claim 1, CHARACTERIZED in that in the case where the LTE cell to which the RRC connection is made is an acceptable LTE cell, the ID of the LTE cell Petition 870250103056, dated 11 / 11 / 2025, page 97 / 116 2 / 5 to which the RRC connection is made is not stored in the VarRLFReport associated with the NR.

3. Method according to claim 1, CHARACTERIZED in that the NR transfer command message comprises an indicator for a voice recoil.

4. Method, according to claim 3, CHARACTERIZED in that it further comprises storing, in the VarRLF-Report associated with the NR, information indicating that the transfer is for a voice recoil.

5. Method, according to claim 1, CHARACTERIZED by the fact that the storage of the time value from the transfer failure to the reconnection or the ID of the LTE cell to which the RRC connection is made in the VarRLF-Report associated with the NR is performed in the case where the ID of an LTE cell is not stored in the VarRLF-Report associated with the NR.

6. Method according to claim 1, CHARACTERIZED in that the terminal is a terminal that supports an inter-RAT RLF report.

7. Method, according to claim 1, CHARACTERIZED in that it further comprises: establishing an RRC connection with the NR base station after updating the VarRLF-Report associated with the NR in relation to the selected LTE cell; receiving a terminal information request message from the NR base station; and transmitting to the NR base station a terminal information reply message comprising the VarRLF-Report associated with the NR.

8. Terminal operating in a wireless communication system, the terminal CHARACTERIZED by the fact that it comprises: a transceiver; and a controller, wherein the controller is configured to: receive, from an NR base station, an NR transfer command message comprising information in which a target radio access technology (RAT) is configured for LTE; in the event that a failure of an NR transfer is detected, select a suitable LTE cell in the event that an acceptable LTE cell is available and select an acceptable LTE cell in the event that an acceptable LTE cell is not available; enter idle RRC mode; perform an RRC connection establishment procedure in relation to the selected LTE cell;If the LTE cell to which the RRC connection is made is a suitable LTE cell, store a time value from the transfer failure to the reconnection and an ID of the LTE cell to which the RRC connection is made in the VarRLF-Report associated with the NR; and if the LTE cell to which the RRC connection is made is an acceptable LTE cell, store a time value from the transfer failure to the reconnection in the VarRLF-Report associated with the NR. Petition 870250103056, dated 11 / 11 / 2025, pp. 99 / 116 4 / 5; 9. Terminal, according to claim 8, CHARACTERIZED in that the controller is configured to, in the case where the LTE cell to which the RRC connection is made is an acceptable LTE cell, omit the storage of the ID of the LTE cell to which the RRC connection is made in the VarRLF-Report associated with the NR.

10. Terminal, according to claim 8, CHARACTERIZED in that the NR transfer command message comprises an indicator for a voice recoil.

11. Terminal, according to claim 10, CHARACTERIZED in that the controller is further configured to store, in the VarRLF-Report associated with the NR, information indicating that the transfer is for a voice callback.

12. Terminal, according to claim 8, CHARACTERIZED in that the controller is further configured to store the time value from transfer failure to reconnection or the ID of the LTE cell to which the RRC connection is made in the VarRLFReport associated with the NR, in the case where the ID of an LTE cell is not stored in the VarRLF-Report associated with the NR.

13. Terminal, according to claim 8, CHARACTERIZED in that the terminal is a terminal that supports an inter-RAT RLF report.

14. Terminal, according to claim 8, CHARACTERIZED in that the controller is further configured to: establish an RRC connection with the NR base station after updating the VarRLF-Report associated with the NR with respect to the selected LTE cell; receive a terminal information request message from the NR base station; and transmit to the NR base station a terminal information response message comprising the VarRLF-Report associated with the NR.